CN106130751A - A kind of upgrade status data administrator, system and method - Google Patents
A kind of upgrade status data administrator, system and method Download PDFInfo
- Publication number
- CN106130751A CN106130751A CN201610370021.1A CN201610370021A CN106130751A CN 106130751 A CN106130751 A CN 106130751A CN 201610370021 A CN201610370021 A CN 201610370021A CN 106130751 A CN106130751 A CN 106130751A
- Authority
- CN
- China
- Prior art keywords
- upgrade
- state data
- data
- upgrading
- statistical
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Environmental & Geological Engineering (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a kind of upgrade status data administrator, system and method, whether the method, by obtaining upgrade status data, stores upgrade status data in normal point of table or exception table beyond Preset Time according to calling time in upgrade status data；Again the upgrade status data stored in exception table are stored according to preset rules in normal point of table of its correspondence, and lost efficacy normally dividing table statistic behavior in point table index table to be labeled as statistics；The normal point table being labeled as statistics inefficacy is carried out upgrade status data statistics processing.Ensure that the upgrade status data in escalation process are possibly stored in normal point of table of its correspondence, thus improve integrity and the accuracy of the storage of upgrade status data, also improve the accuracy of upgrade status data statistics simultaneously.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to an upgrade status data management apparatus, system, and method.
Background
With The rapid development of mobile communication and mobile internet, The holding amount of mobile terminals is increasing continuously, so that a great amount of Firmware Over-The-Air (FOTA) upgrades performed by users of mobile terminals, and upgrade status data of user terminals collected by a FOTA system is also increasing greatly. In this case, reporting of part of the upgrade state data is relatively delayed, and the upgrade state data adopts a policy of storing sub-tables according to a threshold, and when the system is in a continuous large concurrency state, because the amount of the generated upgrade state data is large, the sub-tables easily reach the threshold in a short time, a new sub-table is generated by a Message-Oriented Middleware (MOM) Middleware, so that in the process of upgrading the terminal, the upgrade state data generated by one-time upgrading cannot be stored in the corresponding sub-table, which causes the accuracy of storing the upgrade state data to be reduced, and further causes statistical distortion of the upgrade state data.
Disclosure of Invention
The invention mainly aims to provide an upgrade state data management device, a system and a method, aiming at solving the problems that the upgrade state data cannot be stored at a corresponding position, so that the accuracy of the stored upgrade state data is reduced, and the statistical distortion of the upgrade state data is caused.
To achieve the above object, an embodiment of the present invention provides an upgrade status data management apparatus, including:
the data storage processing module is used for acquiring the upgrade state data and storing the upgrade state data into the normal sub-table or the abnormal table according to whether the reporting time of the upgrade state data exceeds the preset time;
the data write-back processing module is used for writing back the upgrade state data stored in the abnormal table to a normal sub-table corresponding to the upgrade state data according to a preset rule, and marking the statistical state of the normal sub-table in a sub-table index table as statistical failure;
and the data statistical processing module is used for performing upgrade state data statistical processing on the normal sub-tables marked as statistical failure.
Wherein, the data storage processing module is further configured to: before storing the upgrade state data into the exception table, judging whether the exception table has data with the same session identity as the upgrade state data;
when data with the same session identity identification as the upgrading state data does not exist in the abnormal table, analyzing packet searching time from the session identity identification corresponding to the upgrading state data, and correspondingly storing the packet searching time and the upgrading state data into the abnormal table;
and when the data with the same session identification as the upgrading state data exists in the exception table, storing the increment of the upgrading state data relative to the same session identification data to the corresponding position in the exception table.
Wherein, the session identification information sequentially comprises: a current server network protocol field, a current timestamp field, a 5-bit random character field, a 1-bit random number manufacturer field, a terminal model field and a packet searching time field.
Wherein, the data write-back processing module is further configured to: matching the package searching time corresponding to the upgrading state data in the abnormal table with preset time so as to determine a normal sub-table corresponding to the upgrading state data; and storing the upgrading state data into the normal branch table.
Further, an embodiment of the present invention provides an upgrade status data management system, including the upgrade data management apparatus.
Further, an embodiment of the present invention further provides an upgrade status data management method, including:
acquiring upgrade state data, and storing the upgrade state data into a normal sub-table or an abnormal table according to whether the reporting time of the upgrade state data exceeds the preset time;
writing the upgrade state data stored in the abnormal table back to a normal sub-table corresponding to the upgrade state data according to a preset rule, and marking the statistical state of the normal sub-table in a sub-table index table as statistical failure;
and carrying out upgrading state data statistics processing on the normal sub-tables marked as statistical failure.
Before storing the upgrade state data into the exception table, the method further includes: judging whether the abnormal table has the data with the same session identity as the upgrading state data or not;
when data with the same session identity identification as the upgrading state data does not exist in the abnormal table, analyzing packet searching time from the session identity identification corresponding to the upgrading state data, and correspondingly storing the packet searching time and the upgrading state data into the abnormal table;
and when the data with the same session identification as the upgrading state data exists in the abnormal table, storing the increment of the upgrading state data relative to the same session identification data to the corresponding package searching time position in the abnormal table.
Wherein, the session identification information sequentially comprises: a current server network protocol field, a current timestamp field, a 5-bit random character field, a 1-bit random number manufacturer field, a terminal model field and a packet searching time field.
Wherein, upgrade the status queue processing apparatus and writes back the upgrade status data in the abnormal table to its corresponding normal sub-table according to the preset rule, including: matching the package searching time corresponding to the upgrading state data in the abnormal table with preset time so as to determine a normal sub-table corresponding to the upgrading state data in the abnormal table; and storing the upgrading state data into the normal branch table.
Wherein, the upgrading state data statistical processing is carried out on the normal sub-tables marked as statistical failure, and the method comprises the following steps:
and after the upgrade state data statistical record corresponding to the normal sub-table marked as statistical failure is eliminated, performing upgrade state data statistical processing on the normal sub-table.
According to the upgrade state data management device, system and method provided by the embodiment of the invention, the upgrade state data is acquired, whether the reporting time of the upgrade state data exceeds the preset time is judged, and the upgrade state data is stored in the normal sub-table or the abnormal table according to the judgment result; then storing the upgrade state data in the abnormal table into a corresponding normal sub-table according to a preset rule, and marking the statistical state of the normal sub-table in a sub-table index table as statistical failure; and then carrying out upgrading state data statistical processing on the normal sub-tables marked as statistical failure. The upgrading state data in the upgrading process can be stored in the corresponding normal sub-tables, so that the completeness and the accuracy of the upgrading state data storage are improved, and meanwhile, the accuracy of upgrading state data statistics is improved.
Drawings
FIG. 1 is a schematic diagram of a server implementing a preferred embodiment of the present invention;
FIG. 2 is a schematic diagram of a FOTA system implementing a preferred embodiment of the present invention;
FIG. 3 is a flow chart of the upgrading data of the FOTA system for implementing the preferred embodiment of the present invention;
FIG. 4 is a schematic diagram of sub-table generation in the middleware of the FOTA system according to the preferred embodiment of the present invention;
FIG. 5 is a diagram of an upgrade status data management apparatus according to a first embodiment of the present invention;
fig. 6 is a schematic diagram of an upgrade status data management system according to a first embodiment of the present invention;
FIG. 7 is a flowchart of an upgrade status data management method according to a second embodiment of the present invention;
fig. 8 is a flowchart of storage processing performed on upgrade status data in the upgrade status data management system according to the third embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.
As shown in fig. 1, in order to implement the structure diagram of an optional server according to various embodiments of the present invention, the server at least includes: an Input Output (IO) bus 11, a processor 12, a memory 13, a memory 14, and a communication device 15. Wherein,
the input/output (IO) bus 11 is connected to other components (the processor 12, the storage 13, the memory 14, and the communication device 15) of the server to which it belongs, and provides a transmission line for the other components.
The processor 12 typically controls the overall operation of the server to which it belongs. For example, processor 12 performs computations, validation, etc. The processor 12 may be a Central Processing Unit (CPU), among others.
The memory 13 stores processor-readable, processor-executable software code containing instructions for controlling the processor 12 to perform the functions described herein (i.e., software execution functions).
The memory 14, which is generally a semiconductor memory unit, includes a Random Access Memory (RAM), a Read Only Memory (ROM), and a CACHE memory (CACHE), of which RAM is the most important memory. The memory 14 is one of the important components in the computer, and is a bridge for communicating with the CPU12, and the operation of all programs in the computer is performed in the memory, and functions to temporarily store the operation data in the CPU12 and the data exchanged with an external storage such as a hard disk, and as long as the computer is in operation, the CPU12 transfers the data to be operated to the memory for operation, and after the operation is completed, the CPU12 transfers the result, and the operation of the memory also determines the stable operation of the computer.
The communication device 15, typically comprising one or more components, allows radio communication between a server to which it belongs and a wireless communication system or network.
Fig. 2 is a schematic diagram of a FOTA system for implementing various embodiments of the present invention, please refer to fig. 2, the FOTA system at least includes the following subsystem modules: FOTA client 31, i.e. a terminal; the FOTA server 32, which may be the server shown in fig. 1, communicates with other devices such as a terminal and a Redis (key-value database ) cluster 33 in the system through the communication device 15 during the upgrade process, stores other data such as upgrade status data sent from the terminal through the storage 13, and completes the upgrade process through the coordination and cooperation of the processor 12 and the memory; a Redis cluster 33, i.e., a Redis distributed cache system; MOM middleware 34, the MOM middleware 34 may be distributed delayed asynchronous persistence middleware; a database 35, i.e., a data storage system; a background operation management system 36, i.e., a data statistics query system; an operator 37. Specifically, as shown in fig. 3, after the FOTA server 321 and the FOTA server 322 receive the upgrade status data sent by the terminal, the upgrade status data is stored in the database 35 through the processing of the Redis cluster 33 and the MOM middleware 34. In addition, as shown in fig. 4, when the FOTA system is in a continuous large concurrency state, because the generated upgrade state data amount is large, the sub-table easily reaches the threshold value in a short time, the MOM middleware 34 may regulate the distributed file storage database (mongodb) in the database 35 to generate a new sub-table, and store the subsequent upgrade state data.
The various embodiments described herein may be implemented in a computer-readable medium using, for example, computer software, hardware, or any combination thereof. The software code may be implemented by a software application (or program) written in any suitable programming language.
Based on the FOTA upgrade data flow of the FOTA system and the terminal, in order to make those skilled in the art better understand the solution of the present invention, the technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of embodiments of the present invention, but not all embodiments; it should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The first embodiment is as follows:
the present embodiment provides an upgrade status data management apparatus, please refer to fig. 5, which specifically includes a data storage processing module 41, configured to obtain upgrade status data, and store the upgrade status data in a corresponding normal sub-table or abnormal table according to whether a reporting time of the upgrade status data exceeds a preset time; the data write-back processing module 42 is configured to write back the upgrade state data stored in the abnormal table to the corresponding normal sub-table according to a preset rule, and mark a statistical state of the normal sub-table in the sub-table index table as statistical failure; and the data statistical processing module 43 is configured to perform upgrade state data statistical processing on the normal sub-tables marked as statistical failure. The function of the data storage processing module 41 provided in this embodiment may be specifically implemented by a data persistence processing device in the MOM middleware 34, the function of the data write-back processing module 42 may be specifically implemented by an upgrade status queue processing device in the MOM middleware 34, and the function of the data statistics processing module 43 may be specifically implemented by the background operation management system 36.
Specifically, the data storage processing module 41 is configured to obtain the upgrade status data from the server, determine whether the reporting time of the upgrade status data exceeds a preset time, and store the upgrade status data in the corresponding normal sub-table or the abnormal table according to the determination result, and includes: in the upgrading process, the terminal sends upgrading state data to be fed back to the FOTA server 32, and the FOTA server 32 stores the upgrading state data sent by the terminal in the storage 13 and then performs subsequent processing under the regulation and control of the processor 12 and the memory 14. The data storage processing module 41 obtains the upgrade status data from the FOTA server 32, and after obtaining the upgrade status data, first determines whether the upgrade status data is the first upgrade interaction data, and if the upgrade status data is not the first upgrade interaction data, determines whether the reporting time of the upgrade status data exceeds a preset time. If the upgrade status data is the first upgrade interaction data, determining whether the upgrade status data is protocol interaction ERROR data, specifically determining whether the upgrade status data is protocol interaction ERROR data by determining whether the upgrade status data carries a protocol interaction ERROR identifier, for example, determining whether a protocol interaction ERROR identifier FOTA _ ERROR character string exists in an information prefix in a returned information (resultMsg) field, if so, determining that the upgrade status data is protocol interaction ERROR data, and storing the upgrade status data in an upgrade status ERROR table; and when the protocol interaction ERROR identifier FOTA _ ERROR character string does not exist, further judging whether the reporting time exceeds the preset time. The preset time is the time for which the normal sub-table currently performing data storage allows upgrading of the state data storage.
Further, the data storage processing module 41 is further configured to: when the reporting time does not exceed the preset time, storing the upgrading state data into the corresponding normal sub-table; and when the reporting time exceeds the preset time, storing the upgrading state data into an abnormal table.
Specifically, if the reporting time of the upgrade state data does not exceed the preset time, adding the branch name field of the current normal branch table to the upgrade state data, and storing the upgrade state data in the current normal branch table in which data is being stored; and if the preset time is exceeded, storing the upgrading state data into an exception table, wherein the exception table is used for storing all upgrading state data with the reporting time exceeding the preset time.
Further, the data storage processing module 41 is further configured to: before the upgrade state data is stored in the exception table, whether data with the same session identity (sessionID) as the upgrade state data exists in the exception table is judged, if not, the package searching time is analyzed from the session identity corresponding to the upgrade state data, and the package searching time and the upgrade state data are correspondingly stored in the exception table.
Specifically, if the reporting time of the upgrade state data exceeds the preset time and the upgrade state data needs to be stored in the exception table, it is first determined whether data with the sessionID same as the upgrade state data exists in the exception table, and if so, the increment of the upgrade state data is stored in the exception table; if the upgrade status data does not exist, the upgrade status data is stored in an exception table, the package searching time corresponding to the upgrade status data is analyzed from the sessionID, and the package searching time is simultaneously stored in the position corresponding to the upgrade status data in the exception table.
Further, sessionID, i.e. session identification information, sequentially includes: a current server network protocol (IP) field, a current timestamp field, a 5-bit random character field, a 1-bit random number manufacturer field, a terminal model field, and a packet search time field.
Specifically, in the whole process of the terminal interacting with the FOTA server 32, the unique identifier is sessionID, that is, in all upgrade states: searching for the package, downloading, upgrading and sessionID are the same, so that when the upgrading state data is required to be stored in the corresponding normal sub-table, the corresponding normal sub-table can be found no matter whether the reporting time is overtime or not when the upgrading state data is required to be reported, and then the correct upgrading state is updated, so that the accuracy of the native upgrading state data is ensured. In the current sub-table storage strategy, the index table stores the time points of the upgrade status recorded at the beginning and the end of the current sub-table, so that these 2 time-related fields can be used as the update processing positioning marks of the upgrade status, and the current sessionID generation algorithm is: base64 (current server IP-current timestamp-5 bit random character-1 bit random number), i.e. the corresponding identification of the location of the sublist is missing in the current sessionID. The upgrade status data upgrade device provided in this embodiment optimizes the sessionID generation algorithm, and improves the algorithm as follows: base64 (current server IP-current timestamp-5 bit random characters-1 bit random numbers-manufacturer-terminal model-package searching time), the optimized sessionID can still be used as a unique identifier in the upgrade interaction process.
Further, the data write-back processing module is further configured to match package searching time corresponding to the upgrade state data stored in the exception table with preset time, so as to determine a normal sub-table corresponding to the upgrade state data in the exception table; and storing the upgrading state data into the normal branch table.
Specifically, in order to ensure the accuracy of storing the upgrade state data, the upgrade state data stored in the exception table needs to be stored in the corresponding normal sub-table, and the specific process includes: and when the system is in an idle state and abnormal data exist in the abnormal table, matching the packet searching time corresponding to the upgrading state data stored in the abnormal table with preset time so as to determine the corresponding normal sub-table. Determining the sub-table corresponding to the upgrade state data stored in the exception table may be to first obtain a minimum packet searching time and a maximum packet searching time of all packet searching times in the exception table, where for example, if the minimum packet searching time is a and the maximum packet searching time is b, the time range [ a, b ] is used as a write-back time range, that is, a data range for performing subsequent write-back processing. And then acquiring an index record list with the start time and the end time within the write-back time range from the sub-table index table. When the system is idle, acquiring a branch table name and start and end time in an index record list, acquiring an upgrade state data list in the time range of the start and the end of the packet search from an abnormal table, judging whether the upgrade state data in the upgrade state data list has the same sessionID data in a normal branch table corresponding to the branch table name or not, and updating the upgrade state data increment to the normal branch table when the upgrade state data exists; when the upgrade status data does not exist, adding the upgrade status data into the normal branch table; and then marking the index record of the normal sub-table storing the upgrading state data in the abnormal table in the sub-table index table as statistical failure.
The data statistics processing module 43 performs the upgrade status data statistics processing on the normal sub-table marked as the statistical failure, including: and after the upgrade state data statistical record corresponding to the normal sub-table marked as statistical failure is eliminated, performing upgrade state data statistical processing on the normal sub-table. The upgrade state statistical data includes statistical intermediate data corresponding to the branch names of the normal branch tables storing the upgrade state data and the statistical state of the statistical processing intermediate table corresponding to the data between the statistics. And after the statistical record of the upgrade state data is cleared, acquiring a normal sub-table list in an unpasteurized state from the sub-table index table, and performing data statistical processing.
The upgrade state data statistics device provided in this embodiment determines whether the reporting time of the upgrade state data exceeds a preset time after the upgrade state data is acquired through the data storage processing module, and stores the upgrade state data in the normal sublist or the abnormal sublist according to the determination result; then the data write-back processing module stores the upgrade state data in the abnormal table into a corresponding normal table, and marks the statistical state of the normal sub-table in a sub-table index table as statistical failure; when the upgrade state data needs to be subjected to statistical processing, the data statistical processing module is used for carrying out statistical processing on the upgrade state data of the normal sub-tables marked as statistical failure. The upgrading state data in the upgrading interaction process can be stored in the corresponding normal sub-table, so that the completeness and the accuracy of the upgrading state data storage are improved, and meanwhile, the accuracy of upgrading state data statistics is improved.
The upgrade state data statistical system provided in this embodiment, after obtaining the upgrade state data through the upgrade state data management device, determines whether the reporting time of the upgrade state data exceeds a preset time, and stores the upgrade state data into the normal sublist or the abnormal sublist according to the determination result; then writing the upgrade state data in the abnormal table back to the corresponding normal table, and marking the statistical state of the normal sub-table in the sub-table index table as statistical failure; and when the upgrade state data needs to be subjected to statistical processing, performing the statistical processing on the upgrade state data of the normal sub-table marked as the statistical failure. The upgrading interactive data can be stored in the corresponding normal sub-table, so that the completeness and the accuracy of the upgrading state data storage are improved, and the accuracy of upgrading state data statistics is improved.
Example two:
the present embodiment provides an upgrade status data management method, please refer to fig. 7, which includes:
step S101, obtaining upgrade state data, and storing the upgrade state data into a normal sub-table or an abnormal table according to whether the reporting time of the upgrade state data exceeds the preset time.
Specifically, after receiving upgrade state data sent by a server, it is first determined whether the upgrade state data is first upgrade interaction data, and if the upgrade state data is not the first upgrade interaction data, it is determined whether the reporting time of the upgrade state data exceeds a preset time. If the upgrade status data is the first upgrade interaction data, determining whether the upgrade status data is protocol interaction ERROR data, specifically determining whether the upgrade status data is protocol interaction ERROR data by determining whether the upgrade status data carries a protocol interaction ERROR identifier, for example, determining whether a protocol interaction ERROR identifier FOTA _ ERROR character string exists in an information prefix in a returned information (resultMsg) field, if so, determining that the upgrade status data is protocol interaction ERROR data, and storing the upgrade status data in an upgrade status ERROR table; and when the FOTA _ ERROR character string does not exist, further judging whether the reporting time exceeds the preset time. The preset time is the time for which the normal sub-table currently performing data storage allows upgrading of the state data storage.
Further, judging whether the reporting time of the upgrade state data exceeds a preset time, and storing the upgrade state data into a normal sub-table or an abnormal table according to a judgment result, including: when the reporting time does not exceed the preset time, storing the upgrading state data into the corresponding normal sub-table; and when the reporting time exceeds the preset time, storing the upgrading state data into an abnormal table.
Specifically, if the reporting time of the upgrade state data does not exceed the preset time, adding the branch name field of the current normal branch table to the upgrade state data, and storing the upgrade state data in the current normal branch table in which data is being stored; and if the preset time is exceeded, storing the upgrading state data into an exception table, wherein the exception table is used for storing all upgrading state data with the reporting time exceeding the preset time.
Further, before storing the upgrade status data in the exception table, the method further includes: judging whether the abnormal table has data of the same session identity as the upgrading state data, if not, analyzing the package searching time from the session identity corresponding to the upgrading state data, and correspondingly storing the package searching time and the upgrading state data into the abnormal table; and when the upgrade state data exists, storing the increment of the upgrade state data relative to the same session identification data into the corresponding package searching time position in the exception table.
Specifically, if the reporting time of the upgrade state data exceeds the preset time and the upgrade state data needs to be stored in the exception table, it is first determined whether data with the sessionID same as the upgrade state data exists in the exception table, and if so, the increment of the upgrade state data is stored in the exception table; if the upgrade status data does not exist, the upgrade status data is stored in an exception table, the package searching time corresponding to the upgrade status data is analyzed from the sessionID, and the package searching time is simultaneously stored in the position corresponding to the upgrade status data in the exception table.
Further, sessionID, i.e. session identification information, sequentially includes: a current server IP field, a current timestamp field, a 5-bit random character field, a 1-bit random number manufacturer field, a terminal model field and a packet searching time field.
Specifically, in the whole process of the terminal interacting with the FOTA server 32, the unique identifier is sessionID, that is, in all upgrade states: searching for the package, downloading, upgrading and sessionID are the same, so that when the upgrading state data is required to be stored in the corresponding normal sub-table, the corresponding normal sub-table can be found no matter whether the reporting time is overtime or not when the upgrading state data is required to be reported, and then the correct upgrading state is updated, so that the accuracy of the native upgrading state data is ensured. In the current sub-table storage strategy, the index table stores the time points of the upgrade status recorded at the beginning and the end of the current sub-table, so that these 2 time-related fields can be used as the update processing positioning marks of the upgrade status, and the current sessionID generation algorithm is: base64 (current server IP-current timestamp-5 bit random character-1 bit random number), i.e. the corresponding identification of the location of the sublist is missing in the current sessionID. The upgrade status data upgrade device provided in this embodiment optimizes the sessionID generation algorithm, and improves the algorithm as follows: base64 (current server IP-current timestamp-5 bit random characters-1 bit random numbers-manufacturer-terminal model-package searching time), the optimized sessionID can still be used as a unique identifier in the upgrade interaction process.
And step S102, rewriting the upgrade state data in the abnormal table into the corresponding normal sub-table according to a preset rule, and marking the normal sub-table as a statistical failure normal sub-table.
Specifically, in order to store all the upgrade state data in the corresponding normal sub-table, the upgrade state data in the abnormal table needs to be stored in the corresponding normal sub-table.
Further, the step of writing back the upgrade state data in the abnormal table to the corresponding normal sub-table according to a preset rule includes: matching the package searching time corresponding to the upgrading state data in the abnormal table with preset time so as to determine a normal sub-table corresponding to the upgrading state data in the abnormal table; and storing the upgrading state data into the normal branch table.
Specifically, in order to ensure the accuracy of storing the upgrade state data, the upgrade state data stored in the exception table needs to be stored in the corresponding normal sub-table, and the specific process includes: and starting an operation condition monitor of the upgrading state queue processor by a master node of the MOM middleware, and when the system is in an idle state and abnormal data exists in the abnormal table, matching the packet searching time corresponding to the upgrading state data stored in the abnormal table with preset time so as to determine the corresponding normal sub-table. Determining the sub-table corresponding to the upgrade state data stored in the exception table may be to first obtain a minimum packet searching time and a maximum packet searching time of all packet searching times in the exception table, where for example, if the minimum packet searching time is a and the maximum packet searching time is b, the time range [ a, b ] is used as a write-back time range, that is, a data range for performing subsequent write-back processing. And then acquiring an index record list with the start time and the end time within the write-back time range from the sub-table index table. When the system is idle, acquiring a branch table name and start and end time in an index record list, acquiring an upgrade state data list in the time range of the start and the end of the packet search from an abnormal table, judging whether the upgrade state data in the upgrade state data list has the same sessionID data in a normal branch table corresponding to the branch table name or not, and updating the upgrade state data increment to the normal branch table when the upgrade state data exists; when the upgrade status data does not exist, adding the upgrade status data into the normal branch table; and then marking the index record of the normal sub-table storing the upgrading state data in the abnormal table in the sub-table index table as statistical failure.
And step S103, the upgrading state data statistical device carries out upgrading state data statistical processing on the normal sub-tables marked as statistical failure.
Specifically, the upgrade status data statistics device performs upgrade status data statistics on the normal sub-table marked as statistical failure, and includes: and after the upgrade state data statistical record corresponding to the normal sub-table marked as statistical failure is eliminated, performing upgrade state data statistical processing on the normal sub-table. The upgrade state statistical data includes statistical intermediate data corresponding to the branch names of the normal branch tables storing the upgrade state data and the statistical state of the statistical processing intermediate table corresponding to the data between the statistics. And after the statistical record of the upgrade state data is cleared, acquiring a normal sub-table list in an unpasteurized state from the sub-table index table, and performing data statistical processing.
In the upgrade status data statistical system method provided by this embodiment, by acquiring the upgrade status data, the upgrade status data is stored in the normal sublist or the abnormal sublist according to whether the reporting time of the upgrade status data exceeds the preset time; then storing the upgrade state data in the abnormal table into a corresponding normal table, and marking the statistical state of the normal sub-table in a sub-table index table as statistical failure; and when the upgrade state data needs to be subjected to statistical processing, performing the statistical processing on the upgrade state data of the normal sub-table with invalid statistics. The upgrading interactive data can be stored in the corresponding normal sub-table, so that the completeness and the accuracy of the upgrading state data storage are improved, and the accuracy of upgrading state data statistics is improved.
Example three:
the present embodiment describes the upgrade status data management method step by step in detail, and specifically includes:
firstly, adjusting a session ID generation algorithm of the FOTA protocol server, and configuring the session ID to the upgrading session.
Specifically, in the whole process of the FOTA client interacting with the FOTA server, the unique identifier is sessionID, that is, in all upgrade states: searching for the package, downloading, upgrading and sessionID are the same, one of the problems of accuracy is solved, namely when upgrading state data is reported, corresponding sub-tables can be found no matter whether the updating state data is overtime or not, then correct updating processing of the upgrading state is carried out, and accuracy of native upgrading state data is guaranteed. In the current sub-table storage strategy, the index table stores the time points of the upgrade status recorded at the beginning and the end of the current sub-table, so that these 2 time-related fields can be used as the update processing positioning marks of the upgrade status, and the current sessionID generation algorithm is: base64 (current server IP-current timestamp-5 bit random character-1 bit random number), the corresponding identification of the location of the sublist is missing in the current sessionID. Optimizing the generation algorithm of sessionID, and improving the algorithm into: base64base64 (current server IP-current timestamp-5 bit random characters-1 bit random numbers-vendor-terminal model-package search time). The uniqueness is ensured by the part processed by base64 (current server IP-current timestamp-5 bits of random characters-1 bits of random numbers), so that the uniqueness is still ensured by the optimized overall sessionID, which can be used as a unique identifier. Therefore, the optimized overall sessionID still ensures uniqueness and can still be used as a unique identifier. And the sub-table corresponding to each piece of upgrading state data can be accurately positioned through the sessionID, the upgrading state data cannot be lost, the accuracy of storing the upgrading state data is ensured, and the statistics of the upgrading state data is more accurate.
Secondly, adjusting the data persistence processing logic of the MOM middleware to store the upgrade state data, where the processing flow refers to fig. 8, and specifically includes:
step S201, obtaining upgrade status data;
specifically, the MOM middleware acquires upgrade status data sent by the terminal from the FOTA server, where the upgrade status data includes upgrade protocol interaction start data, upgrade protocol interaction completion data, and upgrade download callback data, and after the upgrade protocol interaction start data and the upgrade protocol interaction completion data are merged in the MOM middleware, insertion persistence processing is performed. And upgrade download callback data, because in the actual process, it is the reported data after waiting for the completion of downloading, so there is a delay relatively, and the upgrade status data adopts the strategy of performing sub-table storage according to the threshold, as shown in fig. 3, when the system is in a continuous large concurrency condition, because the amount of the generated upgrade status data is large, the sub-table easily reaches the threshold in a short time, the MOM middleware generates a new sub-table, and the terminal does not report the last download return data in the process of downloading the upgrade package, when the download is completed, after the data is reported, because the sub-table where the corresponding first 2 upgrade status data are located cannot be located, the corresponding upgrade status data is lost, so that the accuracy of the stored data is reduced, and the statistical distortion of the upgrade data is caused. Therefore, in the storage process of the upgrade state data, a strategy needs to be formulated to store the three times of interactive data in the one-time upgrade processing process into the corresponding sub-tables, so as to ensure the integrity and accuracy of the upgrade state data storage.
Step S202, judging whether the upgrade state data is the first interactive data, if so, jumping to step S203; if not, jumping to step S205;
specifically, after the upgrade state data is acquired, it is first determined whether the upgrade state data is the first upgrade interaction data, and if the upgrade state data is not the first upgrade interaction data, it is determined whether the reporting time of the upgrade state data exceeds a preset time. If the upgrade status data is the first upgrade interaction data, judging whether the information prefix in the resultMsg field has a FOTA _ ERROR character string.
Step S203, judging whether the FOTA _ ERROR identification character string exists or not, and if so, jumping to step S204; if not, jumping to step S205;
specifically, whether a FOTA _ ERROR character string exists in an information prefix in a resultMsg field is judged to determine whether the upgrade state data is protocol interaction ERROR data, and if the FOTA _ ERROR character string exists, the upgrade state data is stored in an upgrade state ERROR table when the upgrade state data is protocol interaction ERROR data; and when the FOTA _ ERROR character string does not exist, further judging whether the reporting time exceeds the preset time.
Step S204, storing the route to an upgrade state error table;
specifically, when the upgrade status data is protocol interaction error data, the upgrade status data is stored in the upgrade status error table.
Step S205, judging whether the reporting time exceeds the preset time, if not, jumping to step S206; if not, jumping to step S208;
specifically, the preset time is the time allowed by the normal sublist currently performing data storage to update the state data storage. If the reporting time of the upgrade state data does not exceed the preset time, adding the sub-table name field of the current normal sub-table to the upgrade state data and storing the upgrade state data in the current normal sub-table in which data is being stored; and if the preset time is exceeded, storing the upgrading state data into an exception table, wherein the exception table is used for storing all upgrading state data with the reporting time exceeding the preset time.
Step S206, acquiring corresponding branch table names from the backtracking queue, and jumping to step S207;
specifically, when the upgrade status data is stored in the normal branch table, the corresponding branch table name is obtained from the backtracking queue.
And step S207, adding the current branch table name field, and writing the upgrade state data into the corresponding support branch table together.
Step S208, routing the write operation to an exception table; then, jumping to step S209;
specifically, when the reporting time of the upgrade status data exceeds the preset time, the storage process is routed to the exception table.
Step S209, analyzing the sessionID, analyzing the packet searching time, and jumping to step S210;
specifically, if the reporting time of the upgrade state data exceeds the preset time and the upgrade state data needs to be stored in the exception table, the write operation is routed to the exception table, and the sessionID corresponding to the upgrade state data is analyzed to obtain the package searching time.
Step S210, judging whether the upgrade state data of the sessionID exists in the abnormity, and if so, jumping to step S211; if not, jumping to step S212;
specifically, before storing the upgrade state data in the exception table, it is first determined whether data identical to sessionID of the upgrade state data exists in the exception table, and if so, the upgrade state data is only incrementally stored in the exception table; when the update state data does not exist, the update state data and the corresponding package searching time need to be set in an exception table.
Step S211, updating and persisting the upgrade state data increment into an exception table;
step S212, newly adding and persisting the upgrade state data and the package searching time into an exception table.
Specifically, the upgrade status data and the package searching time corresponding to the upgrade status data are stored in the exception table according to the corresponding relationship and serve as one record in the exception table.
By the method, the normal upgrade state data and the upgrade state data with abnormal delay are stored separately, and the integrity of the upgrade state data storage of the system is guaranteed.
Thirdly, write back processing is carried out on the upgrade state data with delay exception, namely, the upgrade state data in the exception table is written back to the corresponding normal sub-table, and the processing process specifically comprises the following steps:
step S301, a master node of the MOM middleware starts an operation state monitor of an upgrade state queue processor;
specifically, the master node of the MOM middleware starts an operation status listener of the upgrade state queue processor, detects whether the system is idle, and performs subsequent data write-back processing.
Step S302, judging whether the system is in an idle state, and if so, jumping to step S303; if not, returning to the step S301;
specifically, the system accident is judged to be in an idle state, namely whether the upgrading process of the terminal is finished is judged; and when the upgrade process is finished, the write-back process of the upgrade state data is analyzed.
Step S303, judging whether the abnormal table has data, if so, jumping to step S304; if not, returning to the step S301;
specifically, whether upgrade state data are stored in an exception table in the upgrade process is judged, and if yes, write-back processing is required; if not, the write-back processing is not needed.
Step S304, acquiring the minimum packet searching time and the maximum packet searching time of the abnormal data, delimiting the data range of the current write-back, and jumping to the step S305;
specifically, the minimum packet searching time and the maximum packet searching time of the upgrade state data are obtained, the data range of the write-back is defined, and if the minimum packet searching time is a and the maximum packet searching time is b, the write-back range is [ a, b ].
Step S305, acquiring an index record list of the start time and the end time in the write-back time range, and traversing the index record list;
specifically, the sub-table index records with the start time and the end time within the write-back range are searched in the sub-table index table to obtain a sub-table index record list, and then subsequent write-back processing is performed.
Step S306, judging whether the sub-table index record list has non-traversed data, if so, jumping to step S307; if not, returning to the step S301;
specifically, whether records corresponding to the normal sub-table exist in the sub-table index record list or not are judged, and data write-back processing is not performed.
Step S307, judging whether the system is in an idle state, and if so, jumping to step S308; if not, returning to the step S301;
specifically, when the system is determined to be in an idle state, subsequent write-back processing is performed.
Step S308, the branch table name and the start and end time of the index record are obtained, and the step S309 is skipped;
specifically, one index record in the index record list is selected, and then the branch table name in the index record, and the start time and the end time in the branch table name are obtained.
Step S309, obtaining the upgrading state data list of the start and time range, and traversing the list;
specifically, corresponding to the start time and the end time in the index record, the upgrade state data of the package searching time in the start time and the end time is obtained in the exception table.
Step S310, judging whether the upgrading state data list has non-traversal data, if yes, jumping to step S311; if not, jumping to step S314;
specifically, it is determined that all the upgrade status data corresponding to the index record in the abnormal table are found, so as to ensure that all the upgrade status data searched in the abnormal table can be stored in the corresponding normal sub-table.
Step S311, judging whether the same sessionID data exists in the normal sub-table, if yes, jumping to step S312; if not, jumping to step S313;
specifically, when the data in the abnormal table is stored in the corresponding normal sub-table, it is first determined whether there is data in the normal sub-table, which has the same sessionID as the upgrade status data.
Step S312, updating the upgrade status data increment to a normal sublist, and returning to step S310;
specifically, when data with the sessionID same as that of the upgrade state data exists in the normal branch table, the increment of the upgrade state data is stored in the corresponding normal branch table.
Step 313, newly adding the upgrade status data to the sublist, and returning to step 310;
specifically, when data with the sessionID same as the upgrade state data does not exist in the normal sublist, the upgrade state data is stored in the corresponding normal sublist.
Step S314, mark the sub-table index record as statistical failure.
Specifically, after the write-back processing is performed on the normal sub-table, the stored data is changed, and the statistical state of the upgrade state data stored in the abnormal table in the sub-table index table needs to be marked as statistical failure, and the data statistical processing is performed again.
Step S4, recalculating the upgrade status data that has been written back, where the recalculating process specifically includes:
step S401, starting a background operation management system, starting a timing task, and jumping to step S402;
specifically, after the write-back processing of the upgrade status data in the exception table is completed, the data statistics data needs to be performed again on the normal sub-table subjected to the write-back processing.
Step S402, obtaining a list of list names with invalid statistical results in a corresponding list index table of the original data table, and jumping to step S403;
specifically, a list of branch table names with a statistical state of failure is obtained from the branch table index table, and the branch table corresponding to the branch table name is a normal branch table which needs to be subjected to data statistics again.
Step S403, circularly reading the list of sub-list names with invalid statistical results in sequence;
specifically, the sub-table name list with invalid statistical results is read in sequence in a circulating manner to recalculate the records in the sub-table name list one by one.
Step S404, judging whether the list name list has non-traversed data, if so, jumping to step S405; if not, jumping to step S409;
specifically, the data statistics processing is carried out again on the normal tables corresponding to the branch table names in the branch table name list.
Step S405, acquiring a service intermediate report list, and traversing the statistical processing intermediate report list in sequence;
specifically, business intermediate statistical data of the normal sub-table corresponding to the sub-table name is obtained.
Step S406, judging whether the business intermediate report list has non-traversed data, if so, jumping to step S407; if not, returning to the step S404;
in particular, it is ensured that all data in the service intermediate report list is cleared.
Step S407, clearing the statistical intermediate data belonging to the branch table name of the business intermediate report, and jumping to step S408;
specifically, when the upgrade status data transmitted from the normal sub-table changes, it indicates that the corresponding statistical intermediate data in the intermediate business report is incorrect, and at this time, the statistical intermediate data belonging to the sub-table name in the intermediate business report needs to be removed.
Step S408, clearing the statistical state of the statistical processing intermediate table of the sub-table index record;
specifically, after the statistical intermediate data are removed, the statistical state of the statistical processing intermediate table corresponding to the normal sub-table in the index table is respectively obtained.
Step S409, according to each service intermediate table, acquiring a sub-table list in a sub-table index table, wherein the sub-table list is not in a statistical state, and jumping to step S410;
specifically, after the wall finishes the statistical information related to the normal branch table, the normal branch table in the non-statistical state is obtained, and data statistical processing is started.
In step S410, timing data statistical processing is performed.
Through the processing, the correction of the statistical processing of the terminal upgrading state data is completed, and the upgrading state data collection accuracy of the user mobile terminal is greatly improved.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only for the preferred embodiment of the present invention and is not intended to limit the scope of the present invention, and all equivalent structures or equivalent flow transformations, or direct or indirect operations, which are made by using the contents of the present specification and the accompanying drawings
The method is used in other related technical fields, and the same principle is included in the protection scope of the invention.
Claims (10)
1. An upgrade status data management apparatus, comprising:
the data storage processing module is used for acquiring the upgrade state data and storing the upgrade state data into a normal sub-table or an abnormal table according to whether the reporting time of the upgrade state data exceeds the preset time;
the data write-back processing module is used for writing back the upgrade state data stored in the abnormal table into a normal sub-table corresponding to the upgrade state data according to a preset rule, and marking the statistical state of the normal sub-table in a sub-table index table as statistical failure;
and the data statistics processing module is used for performing upgrade state data statistics processing on the normal sub-tables marked as statistics failure.
2. The upgrade status data management apparatus according to claim 1, wherein the data storage processing module is further configured to:
before the upgrade state data is stored in the abnormal table, judging whether the abnormal table has data with the same session identity as the upgrade state data;
when data with the same session identity as the upgrading state data does not exist in the abnormal table, analyzing packet searching time from the session identity corresponding to the upgrading state data, and correspondingly storing the packet searching time and the upgrading state data into the abnormal table;
and when the data with the same session identification as the upgrading state data exists in the exception table, storing the increment of the upgrading state data relative to the same session identification data to the corresponding position in the exception table.
3. The upgrade status data management apparatus according to claim 2, wherein the session identification information sequentially comprises: a current server network protocol field, a current timestamp field, a 5-bit random character field, a 1-bit random number manufacturer field, a terminal model field and a packet searching time field.
4. The upgrade state data management apparatus according to claim 2 or 3, wherein the data write-back processing module is further configured to:
matching the package searching time corresponding to the upgrading state data in the abnormal table with preset time so as to determine a normal sub-table corresponding to the upgrading state data;
and storing the upgrading state data into the normal branch table.
5. An upgrade status data management system, comprising: the upgrade status data management apparatus of any one of claims 1 to 4.
6. An upgrade status data management method, comprising:
acquiring upgrade state data, and storing the upgrade state data into a normal sub-table or an abnormal table according to whether the reporting time of the upgrade state data exceeds the preset time;
writing the upgrade state data stored in the abnormal table back to a normal sub-table corresponding to the upgrade state data according to a preset rule, and marking the statistical state of the normal sub-table in a sub-table index table as statistical failure;
and carrying out upgrading state data statistics processing on the normal sub-tables marked as statistical failure.
7. The upgrade status data management method according to claim 6, prior to storing the upgrade status data in the exception table, further comprising: judging whether the abnormal table has the data with the same session identity as the upgrading state data or not;
when data with the same session identity as the upgrading state data does not exist in the abnormal table, analyzing packet searching time from the session identity corresponding to the upgrading state data, and correspondingly storing the packet searching time and the upgrading state data into the abnormal table;
and when the data with the same session identification as the upgrading state data exists in the abnormal table, storing the increment of the upgrading state data relative to the same session identification data to the corresponding package searching time position in the abnormal table.
8. The upgrade status data management method according to claim 7, wherein the session identification information sequentially includes: a current server network protocol field, a current timestamp field, a 5-bit random character field, a 1-bit random number manufacturer field, a terminal model field and a packet searching time field.
9. The upgrade state data management method according to claim 7 or 8, wherein writing back the upgrade state data in the exception table to a normal sub-table corresponding to the upgrade state data according to a preset rule includes:
matching the package searching time corresponding to the upgrading state data in the abnormal table with preset time so as to determine a normal sub-table corresponding to the upgrading state data;
and storing the upgrading state data into the normal branch table.
10. The statistical method of upgrade state data according to claim 9, wherein the statistical processing of upgrade state data for the normal partial table marked as statistical failure comprises:
and after the upgrade state data statistical record corresponding to the normal sub-table marked as statistical failure is cleared, performing upgrade state data statistical processing on the normal sub-table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610370021.1A CN106130751B (en) | 2016-05-27 | 2016-05-27 | A kind of upgrade status data administrator, system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610370021.1A CN106130751B (en) | 2016-05-27 | 2016-05-27 | A kind of upgrade status data administrator, system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106130751A true CN106130751A (en) | 2016-11-16 |
| CN106130751B CN106130751B (en) | 2019-05-17 |
Family
ID=57270790
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610370021.1A Active CN106130751B (en) | 2016-05-27 | 2016-05-27 | A kind of upgrade status data administrator, system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106130751B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107133302A (en) * | 2017-04-28 | 2017-09-05 | 努比亚技术有限公司 | Realize method, system, terminal and the computer-readable recording medium of data consistency |
| CN108494859A (en) * | 2018-03-28 | 2018-09-04 | 烽火通信科技股份有限公司 | The synchronous method and system of network data |
| CN111045363A (en) * | 2019-12-16 | 2020-04-21 | 北京中大科慧科技发展有限公司 | Intelligent operation and maintenance management and control cloud platform of information communication network |
| CN114866530A (en) * | 2022-03-28 | 2022-08-05 | 深圳优地科技有限公司 | Method and apparatus for downloading upgrade data package, and computer storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1949718A (en) * | 2005-10-14 | 2007-04-18 | 摩托罗拉公司 | FOTA supplying method |
| CN101083580A (en) * | 2006-05-30 | 2007-12-05 | 华为技术有限公司 | Method for obtaining electronic business guide update of mobile terminal and server and terminal |
| CN101610501A (en) * | 2009-07-16 | 2009-12-23 | 中兴通讯股份有限公司 | Device firmware upgrade system and method, device management server and portable terminal |
| US20090320012A1 (en) * | 2008-06-04 | 2009-12-24 | Mediatek Inc. | Secure booting for updating firmware over the air |
| US20130111461A1 (en) * | 2011-11-01 | 2013-05-02 | Michael Zubas | Coordinating Firmware Over-The-Air Updates For Mobile Devices Utilizing Presence Information |
| CN103309709A (en) * | 2013-06-08 | 2013-09-18 | 华为终端有限公司 | Firmware upgrading method, device and communication equipment |
| CN104836680A (en) * | 2015-03-27 | 2015-08-12 | 努比亚技术有限公司 | Firmware over-the-air (FOTA) upgrade processing method and FOTA upgrade processing system |
| CN104866339A (en) * | 2015-04-27 | 2015-08-26 | 努比亚技术有限公司 | Distributed persistent management method, system and device of FOTA data |
-
2016
- 2016-05-27 CN CN201610370021.1A patent/CN106130751B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1949718A (en) * | 2005-10-14 | 2007-04-18 | 摩托罗拉公司 | FOTA supplying method |
| CN101083580A (en) * | 2006-05-30 | 2007-12-05 | 华为技术有限公司 | Method for obtaining electronic business guide update of mobile terminal and server and terminal |
| US20090320012A1 (en) * | 2008-06-04 | 2009-12-24 | Mediatek Inc. | Secure booting for updating firmware over the air |
| CN101610501A (en) * | 2009-07-16 | 2009-12-23 | 中兴通讯股份有限公司 | Device firmware upgrade system and method, device management server and portable terminal |
| US20130111461A1 (en) * | 2011-11-01 | 2013-05-02 | Michael Zubas | Coordinating Firmware Over-The-Air Updates For Mobile Devices Utilizing Presence Information |
| CN103309709A (en) * | 2013-06-08 | 2013-09-18 | 华为终端有限公司 | Firmware upgrading method, device and communication equipment |
| CN104836680A (en) * | 2015-03-27 | 2015-08-12 | 努比亚技术有限公司 | Firmware over-the-air (FOTA) upgrade processing method and FOTA upgrade processing system |
| CN104866339A (en) * | 2015-04-27 | 2015-08-26 | 努比亚技术有限公司 | Distributed persistent management method, system and device of FOTA data |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107133302A (en) * | 2017-04-28 | 2017-09-05 | 努比亚技术有限公司 | Realize method, system, terminal and the computer-readable recording medium of data consistency |
| CN108494859A (en) * | 2018-03-28 | 2018-09-04 | 烽火通信科技股份有限公司 | The synchronous method and system of network data |
| CN108494859B (en) * | 2018-03-28 | 2020-07-14 | 烽火通信科技股份有限公司 | Network data synchronization method and system |
| CN111045363A (en) * | 2019-12-16 | 2020-04-21 | 北京中大科慧科技发展有限公司 | Intelligent operation and maintenance management and control cloud platform of information communication network |
| CN111045363B (en) * | 2019-12-16 | 2021-01-05 | 北京中大科慧科技发展有限公司 | Intelligent operation and maintenance management and control cloud platform of information communication network |
| CN114866530A (en) * | 2022-03-28 | 2022-08-05 | 深圳优地科技有限公司 | Method and apparatus for downloading upgrade data package, and computer storage medium |
| CN114866530B (en) * | 2022-03-28 | 2024-04-19 | 深圳优地科技有限公司 | Method, device and computer storage medium for downloading upgrade data packet |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106130751B (en) | 2019-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10225145B2 (en) | Method and device for updating client | |
| CN106130751B (en) | A kind of upgrade status data administrator, system and method | |
| CN109829287A (en) | Api interface permission access method, equipment, storage medium and device | |
| CN113132267A (en) | Distributed system, data aggregation method and computer readable storage medium | |
| CN110543324B (en) | Plug-in increment updating method and device for application program | |
| CN109840103B (en) | Method and device for updating application program container and storage medium | |
| CN111176706A (en) | Terminal upgrading method and device, electronic equipment and storage medium | |
| CN110990350B (en) | Log analysis method and device | |
| CN114090074A (en) | Operating environment configuration method and device, storage medium and electronic device | |
| CN114338630A (en) | Domain name access method, device, electronic device, storage medium and program product | |
| CN113434293A (en) | Method and apparatus for processing repeat request, storage medium, and electronic apparatus | |
| CN113535206B (en) | Multi-version code upgrading method and system | |
| CN107239303B (en) | Application program update package generation method and device and application program update method and device | |
| AU2021204609A1 (en) | Cluster management method and apparatus, electronic device and storage medium | |
| CN112947991A (en) | Method and device for acquiring version difference code file, computer equipment and medium | |
| CN117235017A (en) | Data upgrading method, device, equipment and storage medium | |
| CN113434525B (en) | Method and device for updating cached data, storage medium and electronic device | |
| CN116414898A (en) | Database access method and device, electronic equipment and storage medium | |
| CN112416401B (en) | Data updating method, device and equipment | |
| CN106371867B (en) | Financial equipment software updating method and system | |
| CN118276887A (en) | Set top box cross-system upgrading method and device, set top box and storage medium | |
| CN115982122A (en) | Data migration method, device and equipment and computer readable storage medium | |
| CN106201606A (en) | software distribution method and system | |
| CN114466387A (en) | Method and device for updating configuration file of base station, storage medium and electronic device | |
| CN111290804A (en) | A service configuration system and service configuration method, device and configuration server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |