CN107395428A - Version file upgrade method, device, server and client device - Google Patents
Version file upgrade method, device, server and client device Download PDFInfo
- Publication number
- CN107395428A CN107395428A CN201710685295.4A CN201710685295A CN107395428A CN 107395428 A CN107395428 A CN 107395428A CN 201710685295 A CN201710685295 A CN 201710685295A CN 107395428 A CN107395428 A CN 107395428A
- Authority
- CN
- China
- Prior art keywords
- file
- version
- version file
- broadcast message
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000012544 monitoring process Methods 0.000 claims description 34
- 238000012545 processing Methods 0.000 claims description 21
- 230000032683 aging Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 7
- 238000012360 testing method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
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/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a kind of version file upgrade method, device, server and client device.Version file upgrade method is applied to server side and client-side.Wherein, the version file upgrade method applied to server side includes：Monitor the file increase event under version file catalogue；When listening to file increase event, judge whether increased file is version file；If version file, then generation includes the broadcast message of the filename of version file；The broadcast message is broadcasted, so that the client for receiving the broadcast message carries out the upgrading of version file according to file name.Version file upgrade method, device, server and the client device provided by the embodiment of the present application, it is possible to increase version file upgrades ageing.And busy poll is avoided, the pressure of server can be mitigated.
Description
Technical Field
The present application relates to the field of automated testing technologies, and in particular, to a method and an apparatus for upgrading a version file, a server, and a client device.
Background
In an automatic test, in order to ensure the accuracy of a test result, version files need to be updated in time.
The version file is typically maintained under a version file directory in the server. In the related technology, a client sends a query instruction to a server at a certain time interval in a timing polling mode, queries the latest version file in a version file directory, compares the latest version file with the existing version file, and downloads the version file and upgrades the version if the latest version file is different from the existing version file. However, the timing polling method requires that the client continuously queries the server within the timeout period, and the version files are compared after each query, which is inefficient. In addition, when multiple clients poll the server at the same time, the server is over stressed and inefficient.
Disclosure of Invention
The application provides a version file upgrading method, a version file upgrading device, a server and client equipment. The timeliness of version file upgrading can be improved, and the pressure of a server can be relieved.
According to a first aspect of an embodiment of the present application, a version file upgrade method is provided. The method is applied to a server side, and comprises the following steps: monitoring file increasing events under a version file directory; when a file adding event is monitored, judging whether the added file is a version file or not; if the version file is the version file, generating a broadcast message containing the file name of the version file; and broadcasting the broadcast message so as to enable the client receiving the broadcast message to upgrade the version file according to the file name.
Further, the determining whether the added file is a version file includes:
acquiring a first file extension of the added file and a second file extension of the version file; judging whether the first file extension name is consistent with the second file extension name; and if the file is consistent, determining that the added file is a version file, otherwise, determining that the added file is not a version file.
Further, the generating a broadcast message containing the file name of the version file includes:
acquiring a file path of the version file, wherein the file path at least comprises a version name and a download path of the version file; removing the version name and the download path in the file path, and adding a download protocol and an IP address to obtain a processing path; and generating a broadcast message containing the file name of the version file according to the processing path.
Further, the broadcasting the broadcast message includes:
generating one or more broadcast channels from a parent directory of the processing path; broadcasting the broadcast message on the one or more broadcast channels.
According to a second aspect of the embodiments of the present application, a version file upgrade method is provided. The method is applied to a client side, and comprises the following steps:
monitoring the broadcast message of the server according to the set monitoring path; if a broadcast message containing the file name of the version file is monitored, downloading the version file from the server according to the file name; and upgrading the version according to the version file.
Furthermore, there are multiple monitoring paths, and the multiple monitoring paths respectively correspond to multiple broadcast channels of the server.
According to a third aspect of the embodiments of the present application, there is provided a version file upgrade apparatus. The device is applied to the server side, and comprises:
the file adding event monitoring unit is used for monitoring file adding events in the version file directory; the judging unit is used for judging whether the added file is a version file or not when the file adding event monitoring unit monitors the file adding event; a broadcast message generating unit configured to generate a broadcast message including a file name of the version file when the judging unit judges that the added file is the version file; and the broadcasting unit is used for broadcasting the broadcast message so as to upgrade the version file according to the file name by the client side receiving the broadcast message.
According to a fourth aspect of the embodiments of the present application, there is provided a version file upgrade apparatus. The apparatus is applied to a client side, and the apparatus includes: the broadcast message monitoring unit is used for monitoring the broadcast message of the server according to the set monitoring path; a version file downloading unit, configured to download the version file from the server according to the file name when the broadcast message monitoring unit monitors the broadcast message that includes the file name of the version file; and the version file upgrading unit is used for upgrading the version according to the version file.
According to a fifth aspect of embodiments herein, there is provided a server. The method comprises the following steps: one or more processors; and a memory communicatively coupled to the one or more processors, wherein the memory has stored therein instructions executable by the one or more processors, the instructions being executable by the one or more processors to enable the one or more processors to perform the above-described version file upgrade method applied to the server side.
A sixth aspect according to embodiments of the present application provides a client device. The method comprises the following steps: one or more processors; and a memory communicatively coupled to the one or more processors, wherein the memory has stored therein instructions executable by the one or more processors, the instructions being executable by the one or more processors to enable the one or more processors to perform the above-described version file upgrade method applied to the client side.
According to the version file upgrading method, the version file upgrading device, the server and the client device, file adding events in a version file directory are monitored in real time through the server side, and a broadcast message is generated when the added files are version files. And the client side can conveniently and timely upgrade the version according to the new version file, and the timeliness is higher. And the client side does not need to send a query instruction to the server, so that the pressure of the server can be relieved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
Fig. 1 is a flowchart illustrating a version file upgrade method applied to a server side according to an exemplary embodiment of the present application;
FIG. 2 is a flow diagram of one embodiment of the steps for generating a broadcast message in the embodiment shown in FIG. 1;
FIG. 3 is a flowchart illustrating a version file upgrade method applied to a client side according to an exemplary embodiment of the present application;
fig. 4 is a block diagram illustrating a configuration of a version file upgrading apparatus applied to a server side according to an exemplary embodiment of the present application;
fig. 5 is a block diagram illustrating a structure of another version file upgrading apparatus applied to a server side according to an exemplary embodiment of the present application;
fig. 6 is a block diagram illustrating a structure of a version file upgrading apparatus applied to a client side according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The following describes a version file upgrading method, device, server and client device in detail with reference to the accompanying drawings. The features of the following examples and embodiments may be combined with each other without conflict.
In the prior art, when upgrading a version file, a certain time interval is generally set at a client side, and the client side sends a query instruction to a version server at a certain time interval to query the latest version file of a specified path in the server and compare the latest version file with an existing version file. And if the comparison results are different, judging that the latest version file in the server is the newly added version file. The client downloads the newly added version file from the server and carries out version upgrading. In the prior art, a certain time interval needs to be set, so that the timeliness of version file updating cannot be guaranteed. Moreover, the query needs to be continuously performed within the overtime time, and the comparison of the version files needs to be performed after each query, so that the logic is complex. In addition, if a plurality of clients poll the server at the same time, the server is over stressed and the efficiency is low.
Based on this, the embodiment of the present application provides an improved version file upgrading method.
As shown in fig. 1, fig. 1 is a flowchart of a version file upgrading method provided in an exemplary embodiment of the present application, where the method is applied to a server side, and the method may include the following steps:
in step 11, a file addition event under the version file directory is listened to.
In this embodiment of the present application, the version file may be stored in a file system of the server, and the version file may be stored in each directory in the file system according to a device type, a product model, and the like. The server can monitor file addition events under a version file directory in the file system through a change notification mechanism of the file system.
In step 12, when a file addition event is monitored, whether the added file is a version file is judged.
In an optional embodiment, when determining whether the added file is a version file, a first file extension of the added file and a second file extension of the version file may be obtained first. Then, whether the first file extension and the second file extension are consistent or not is judged. And if the first file extension is consistent with the second file extension, determining that the added file is a version file, otherwise, determining that the added file is not the version file.
If the judgment result in this step is yes, it indicates that the added file is a version file, step 13 is entered, otherwise, it indicates that the added file is not a version file, and this step is continued.
In step 13, a broadcast message containing the file name of the version file is generated.
In an alternative embodiment, this step includes substep 131, substep 132, and substep 133, as shown in FIG. 2. Wherein,
in sub-step 131, a file path of the version file is obtained, the file path including at least a version name and a download path of the version file.
The file path may be a storage path of the version file in the file system, the storage path may be related to a download protocol used by the server, for example, the download protocol used by the server is an FTP protocol, and the file path of the version file may be "/home/user/FTP/device type/product model/phase/version number/version name".
In sub-step 132, the version name and the download path in the file path are removed, and the download protocol and the IP address are added to obtain a processing path.
The resulting processing path after processing is "ftp:// version server IP/device type/product model/phase/version number".
In sub-step 133, a broadcast message containing the file name of the version file is generated according to the processing path.
The file name of the version file of the present embodiment may be the processing path plus a version name, such as "ftp:// version server IP/device type/product model/phase/version number/version name".
In step 14, the broadcast message is broadcasted, so that the client receiving the broadcast message upgrades the version file according to the file name.
In an alternative embodiment, a broadcast channel may be generated based on the parent directory of the processing path. For example, a broadcast channel may be generated from any primary parent directory of the processing path, and a broadcast message containing the file name of the version file may be broadcast in the broadcast channel.
In another alternative embodiment, multiple broadcast channels may be generated from the parent directory of the processing path. Specifically, one broadcast channel may be generated according to each level of parent directory of the processing path. Such as: the processing path is "ftp:// version server IP/device type/product model/phase/version number". The generated broadcast channel 1 is { ftp:// version server IP/device type/product model/phase/version number/}. Broadcast channel 2 is: { ftp:// version server IP/device type/product model/phase/}, broadcast channel 3 is: { ftp:// version server IP/device type/product model/} and so on. A broadcast message containing the file name of the version file is then broadcast in each broadcast channel. Therefore, the method and the device are suitable for monitoring paths with different depths on the client side, and the efficiency of monitoring the broadcast message by the client side is improved.
In another optional embodiment, the server may include a version server and a message queue server, where the version server is configured to monitor a file addition event in a version file directory, and when an added file is a version file, generate a broadcast message containing a file name of the version file, and send the broadcast message to the message queue server for broadcasting, so that a client receiving the broadcast message upgrades the version file according to the file name.
According to the version file upgrading method, file adding events in the version file directory are monitored in real time through the server side, and a broadcast message is generated when the added files are version files. And the client side can conveniently and timely upgrade the version according to the new version file, and the timeliness is higher.
As shown in fig. 3, fig. 3 is a flowchart of a version file upgrade method provided by an exemplary embodiment of the present application, where the method is applied to a client side, and the method may include the following steps:
in step 31, the broadcast message of the server is monitored according to the set monitoring path.
In an alternative embodiment, the listening path may be one, and the listening path corresponds to a broadcast channel of the server. For example, when the broadcast channel is { ftp:// version server IP/device type/product model/phase/version number/}, the listening path may be set to: ftp:// version server IP/device type/product model/phase/version number/". That is, the set monitoring path is consistent with the broadcast channel of the server, so that the client can monitor the broadcast message in the broadcast channel of the server according to the monitoring path.
In another alternative embodiment, there may be a plurality of listening paths, and the plurality of listening paths respectively correspond to a plurality of broadcast channels of the server. For example, when the broadcast channel 1 is { ftp:// version server IP/device type/product model/phase/version number/}, the broadcast channel 2 is: { ftp:// version server IP/device type/product model/phase/}, broadcast channel 3 is: { ftp:// version server IP/device type/product model/}. Listening path 1 may be set to: ftp:// version server IP/device type/product model/phase/version number/", listening path 2 is: ftp:// version server IP/device type/product model/phase/", listening path 3 is: ftp:// version server IP/device type/product model/"and so on. Therefore, the client can monitor the broadcast messages in a plurality of broadcast channels of the server, and the efficiency of monitoring the broadcast messages is improved.
It should be noted that the file path, the broadcast channel, and the listening path in the embodiment of the present application are only examples, and may be determined according to specific situations in practical applications.
In step 32, if a broadcast message containing the file name of the version file is listened to, the version file is downloaded from the server according to the file name.
Specifically, the version file may be downloaded according to a download protocol and an IP address in a file name of the version file.
In step 33, version upgrade is performed according to the version file.
In the embodiment of the application, when the client side monitors the broadcast message of the server, the version of the device to be tested can be upgraded according to the broadcast message, and the timeliness of version file upgrading is ensured. And the inquiry command is not sent to the server, so that busy polling is avoided, and the pressure of the server can be relieved. Meanwhile, multiple comparisons of version files are avoided, and the logic operation of the client is simplified.
Corresponding to the embodiment of the version file upgrading method, the application also provides an embodiment of a version file upgrading device.
As shown in fig. 4, fig. 4 is a block diagram of a version file upgrading apparatus 40 according to an exemplary embodiment of the present application, where the apparatus 40 is applied to a server side, and the apparatus 40 includes:
and a file addition event monitoring unit 41, configured to monitor a file addition event in the version file directory.
A judging unit 42, configured to judge whether the added file is a version file when the file addition event monitoring unit 41 monitors the file addition event.
A broadcast message generating unit 43, configured to generate a broadcast message containing a file name of the version file when the judging unit 42 judges that the added file is the version file.
And the broadcasting unit 44 is configured to broadcast the broadcast message, so that the client receiving the broadcast message upgrades the version file according to the file name.
In an alternative embodiment, the determining unit 42 is configured to obtain a first file extension of the added file and a second file extension of the version file; judging whether the first file extension name is consistent with the second file extension name; and if the file is consistent, determining that the added file is a version file, otherwise, determining that the added file is not a version file.
As shown in fig. 5, fig. 5 is a block diagram of another version file upgrading apparatus 40 according to an exemplary embodiment of the present application. In the present embodiment, the broadcast message generating unit 43 includes: a file path acquisition sub-unit 431, a processing path determination sub-unit 432, and a broadcast message generation sub-unit 433.
The file path obtaining subunit 431 is configured to obtain a file path of the version file, where the file path at least includes a version name and a download path of the version file.
The processing path determining subunit 432 is configured to remove the version name and the download path in the file path, and add the download protocol and the IP address to obtain a processing path.
The broadcast message generating subunit 433 is configured to generate a broadcast message including a file name of the version file according to the processing path.
In an alternative embodiment, the broadcast unit 44 is configured to generate one or more broadcast channels according to the parent directory of the processing path; and broadcasting the broadcast message on the one or more broadcast channels.
The version file upgrading apparatus 40 according to the embodiment of the present application monitors a file addition event in a version file directory in real time by the file addition event monitoring unit 41, and generates a broadcast message when the determination unit 42 determines that the added file is a version file. And the client side can conveniently and timely upgrade the version according to the new version file, and the timeliness of the version file upgrade is ensured.
As shown in fig. 6, fig. 6 is a block diagram of a version file upgrading apparatus 60 according to an exemplary embodiment of the present application, where the apparatus 60 is applied to a client side, and the apparatus 60 includes: a broadcast message listening unit 61, a version file downloading unit 62, and a version file upgrading unit 63.
The broadcast message monitoring unit 61 is configured to monitor the broadcast message of the server according to the set monitoring path. The version file downloading unit 62 is configured to download the version file from the server according to the file name when the broadcast message listening unit 61 listens for the broadcast message containing the file name of the version file. The version file upgrade unit 63 is configured to perform version upgrade according to the version file.
In an alternative embodiment, there may be a plurality of listening paths, and the plurality of listening paths respectively correspond to a plurality of broadcast channels of the server.
According to the version file upgrading device 60 in the embodiment of the application, when the broadcast message monitoring unit 61 monitors the broadcast message of the server, the version file can be downloaded according to the broadcast message to upgrade the version of the device to be tested, so that the timeliness of version file upgrading is guaranteed. And the inquiry command is not required to be sent to the server side, so that busy polling is avoided, and the pressure of the server can be relieved. Meanwhile, multiple comparisons of the version files at the client side are avoided, and the logic operation of the client is simplified.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
An embodiment of the present application further provides a server, including: one or more processors; and a memory communicatively coupled to the one or more processors. Wherein the memory has stored therein instructions executable by the one or more processors to enable the one or more processors to perform the version file upgrade method of the embodiment shown in fig. 1.
An embodiment of the present application further provides a client device, including: one or more processors; and a memory communicatively coupled to the one or more processors. Wherein the memory has stored therein instructions executable by the one or more processors to enable the one or more processors to perform the version file upgrade method of the embodiment shown in fig. 3.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A version file upgrading method is applied to a server side, and is characterized by comprising the following steps:
monitoring file increasing events under a version file directory;
when a file adding event is monitored, judging whether the added file is a version file or not;
if the version file is the version file, generating a broadcast message containing the file name of the version file;
and broadcasting the broadcast message so as to enable the client receiving the broadcast message to upgrade the version file according to the file name.
2. The method of claim 1, wherein the determining whether the added file is a version file comprises:
acquiring a first file extension of the added file and a second file extension of the version file;
judging whether the first file extension name is consistent with the second file extension name;
and if the file is consistent, determining that the added file is a version file, otherwise, determining that the added file is not a version file.
3. The method of claim 1, wherein generating the broadcast message containing the filename of the version file comprises:
acquiring a file path of the version file, wherein the file path at least comprises a version name and a download path of the version file;
removing the version name and the download path in the file path, and adding a download protocol and an IP address to obtain a processing path;
and generating a broadcast message containing the file name of the version file according to the processing path.
4. The method of claim 3, wherein the broadcasting the broadcast message comprises:
generating one or more broadcast channels from a parent directory of the processing path;
broadcasting the broadcast message on the one or more broadcast channels.
5. A version file upgrading method applied to a client side is characterized by comprising the following steps:
monitoring the broadcast message of the server according to the set monitoring path;
if a broadcast message containing the file name of the version file is monitored, downloading the version file from the server according to the file name;
and upgrading the version according to the version file.
6. The method of claim 5, wherein there are a plurality of the listening paths, and the plurality of the listening paths correspond to a plurality of broadcast channels of the server, respectively.
7. A version file upgrading device, which is applied to a server side, is characterized by comprising:
the file adding event monitoring unit is used for monitoring file adding events in the version file directory;
the judging unit is used for judging whether the added file is a version file or not when the file adding event monitoring unit monitors the file adding event;
a broadcast message generating unit configured to generate a broadcast message including a file name of the version file when the judging unit judges that the added file is the version file;
and the broadcasting unit is used for broadcasting the broadcast message so as to upgrade the version file according to the file name by the client side receiving the broadcast message.
8. A version file upgrade apparatus, applied to a client side, the apparatus comprising:
the broadcast message monitoring unit is used for monitoring the broadcast message of the server according to the set monitoring path;
a version file downloading unit, configured to download the version file from the server according to the file name when the broadcast message monitoring unit monitors the broadcast message that includes the file name of the version file;
and the version file upgrading unit is used for upgrading the version according to the version file.
9. A server, comprising: one or more processors; and
a memory communicatively coupled to the one or more processors, wherein,
the memory has stored therein instructions executable by the one or more processors to enable the one or more processors to perform the version file upgrade method of any one of claims 1 to 4.
10. A client device, comprising: one or more processors; and
a memory communicatively coupled to the one or more processors, wherein,
the memory has stored therein instructions executable by the one or more processors to enable the one or more processors to perform the version file upgrade method of claim 5 or claim 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710685295.4A CN107395428A (en) | 2017-08-11 | 2017-08-11 | Version file upgrade method, device, server and client device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710685295.4A CN107395428A (en) | 2017-08-11 | 2017-08-11 | Version file upgrade method, device, server and client device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107395428A true CN107395428A (en) | 2017-11-24 |
Family
ID=60355420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710685295.4A Pending CN107395428A (en) | 2017-08-11 | 2017-08-11 | Version file upgrade method, device, server and client device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107395428A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111352847A (en) * | 2020-03-09 | 2020-06-30 | 中国邮政储蓄银行股份有限公司 | Real-time debugging method and system for mobile application terminal |
| CN112527529A (en) * | 2020-12-18 | 2021-03-19 | 天津中新智冠信息技术有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN113132123A (en) * | 2019-12-30 | 2021-07-16 | 中兴通讯股份有限公司 | Method, device, equipment and storage medium for quickly distributing and installing versions |
| CN114024786A (en) * | 2022-01-04 | 2022-02-08 | 杭州趣链科技有限公司 | Message broadcasting method and device, computer equipment and storage medium |
| CN114461240A (en) * | 2021-06-30 | 2022-05-10 | 荣耀终端有限公司 | Software upgrading method, software upgrading system and electronic equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101060427A (en) * | 2006-04-19 | 2007-10-24 | 华为技术有限公司 | A system and method for realizing the remote software updating |
| CN101304617A (en) * | 2008-06-20 | 2008-11-12 | 深圳华为通信技术有限公司 | Method, apparatus and system as well as server for upgrading optical network terminal |
| CN101646263A (en) * | 2009-09-07 | 2010-02-10 | 中兴通讯股份有限公司 | Upgrading method of built-in data card and system |
| WO2010148739A1 (en) * | 2009-06-22 | 2010-12-29 | 中兴通讯股份有限公司 | Terminal device and upgrade method and system thereof |
| CN105335190A (en) * | 2015-10-12 | 2016-02-17 | 广州视睿电子科技有限公司 | Automatic upgrading method and device for application software in local area network |
| CN106155750A (en) * | 2016-07-29 | 2016-11-23 | 腾讯科技（深圳）有限公司 | The loading method of a kind of resource file and device |
| US20170034309A1 (en) * | 2014-04-16 | 2017-02-02 | Huawei Technologies Co., Ltd. | Software upgrade method and terminal |
-
2017
- 2017-08-11 CN CN201710685295.4A patent/CN107395428A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101060427A (en) * | 2006-04-19 | 2007-10-24 | 华为技术有限公司 | A system and method for realizing the remote software updating |
| CN101304617A (en) * | 2008-06-20 | 2008-11-12 | 深圳华为通信技术有限公司 | Method, apparatus and system as well as server for upgrading optical network terminal |
| WO2010148739A1 (en) * | 2009-06-22 | 2010-12-29 | 中兴通讯股份有限公司 | Terminal device and upgrade method and system thereof |
| CN101646263A (en) * | 2009-09-07 | 2010-02-10 | 中兴通讯股份有限公司 | Upgrading method of built-in data card and system |
| US20170034309A1 (en) * | 2014-04-16 | 2017-02-02 | Huawei Technologies Co., Ltd. | Software upgrade method and terminal |
| CN105335190A (en) * | 2015-10-12 | 2016-02-17 | 广州视睿电子科技有限公司 | Automatic upgrading method and device for application software in local area network |
| CN106155750A (en) * | 2016-07-29 | 2016-11-23 | 腾讯科技（深圳）有限公司 | The loading method of a kind of resource file and device |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113132123A (en) * | 2019-12-30 | 2021-07-16 | 中兴通讯股份有限公司 | Method, device, equipment and storage medium for quickly distributing and installing versions |
| CN111352847A (en) * | 2020-03-09 | 2020-06-30 | 中国邮政储蓄银行股份有限公司 | Real-time debugging method and system for mobile application terminal |
| CN112527529A (en) * | 2020-12-18 | 2021-03-19 | 天津中新智冠信息技术有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN112527529B (en) * | 2020-12-18 | 2022-11-08 | 天津中新智冠信息技术有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN114461240A (en) * | 2021-06-30 | 2022-05-10 | 荣耀终端有限公司 | Software upgrading method, software upgrading system and electronic equipment |
| CN114461240B (en) * | 2021-06-30 | 2023-04-14 | 荣耀终端有限公司 | Software upgrading method, software upgrading system and electronic equipment |
| CN114024786A (en) * | 2022-01-04 | 2022-02-08 | 杭州趣链科技有限公司 | Message broadcasting method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107395428A (en) | Version file upgrade method, device, server and client device | |
| CN112261118B (en) | Multimedia data anomaly detection method, terminal and server | |
| CN109905286B (en) | Method and system for monitoring running state of equipment | |
| CN104066077A (en) | OTA downloading and upgrading method and device thereof | |
| CN104811979B (en) | Method for testing pressure based on FOTA upgrading and device | |
| CN104123360A (en) | Application recommendation data acquisition method, device and system and electronic device | |
| CN106657259B (en) | Routing server and routing service method for server cluster | |
| CN107483567B (en) | Distributed log searching method and system | |
| CN109358876A (en) | A kind of version synchronization method and device, equipment, storage medium | |
| CN106339273A (en) | Application program restoration method, terminal and server | |
| CN108255708B (en) | Method, device, storage medium and equipment for accessing production file in test environment | |
| CN112035129A (en) | Method and device for driver installation and upgrade and computer equipment | |
| CN105530323B (en) | File upgrading method, related equipment and system | |
| CN104468248B (en) | Service performance monitoring method, reverse proxy server, statistical analysis server and system | |
| CN112631687A (en) | Configuration method, device and equipment of service cluster | |
| CN113377399A (en) | Non-stop system drilling verification method and device | |
| CN112039718A (en) | Upgrade status detection method, server, device and storage medium | |
| CN110727441A (en) | Method, system and storage medium for installing flash agent | |
| CN110839061B (en) | Data distribution method, device and storage medium | |
| CN113032281A (en) | Method and device for acquiring code coverage rate in real time | |
| CN113535203B (en) | Server upgrading method, device, equipment and storage medium | |
| CN104268189B (en) | Evaluate the method and device of application | |
| CN105653446A (en) | Automated test method and system for mobile terminal | |
| CN113485864B (en) | Abnormality detection, abnormality analysis method, abnormality detection device, abnormality analysis device, electronic apparatus, and storage medium | |
| CN112073322B (en) | Discovery method and device of network tester |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20171124 |
|
| RJ01 | Rejection of invention patent application after publication |