CN105320541A - Network system and software update method - Google Patents
Network system and software update method Download PDFInfo
- Publication number
- CN105320541A CN105320541A CN201510731504.5A CN201510731504A CN105320541A CN 105320541 A CN105320541 A CN 105320541A CN 201510731504 A CN201510731504 A CN 201510731504A CN 105320541 A CN105320541 A CN 105320541A
- Authority
- CN
- China
- Prior art keywords
- router
- sent
- update software
- end device
- border
- 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
Landscapes
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a network system. The network system comprises, a terminal apparatus, a first router, a second router, a first border router, a second border router and a server. First update software is respectively transmitted to the first border router and the second border router by the server via the Internet; the first update software is transmitted to the first router via the first border router, and the first update software is transmitted to the second router via the second border router; the first update software is transmitted to the terminal apparatus via the first router, and the first update software is transmitted to the terminal apparatus via the second router; the terminal apparatus determines whether version information of the two pieces of update software received from the first router and the second router is the same; if the version information of the two pieces of update software received from the first router and the second router is the same, the terminal apparatus executes an update program of the first update software; and if the version information of the two pieces of update software received from the first router and the second router is different, the terminal apparatus stops the update program of the first update software.
Description
Technical field
The present invention about a kind of network system and Oftware updating method, espespecially a kind of can via network correctly and immediately carry out network system and the Oftware updating method of software upgrading.
Background technology
Internet of Things (InternetofThings, IoT) be one based on information supporting bodies such as world-wide web, conventional telecommunications nets, allow the actual network interconnected of all general physics objects that can be independently addressable.Internet of Things is generally wireless network, and can reach 1 thousand to five thousand, so Internet of Things may comprise 500 million to an one gigabit object due to the device around everyone.On Internet of Things, real object online can connect by applying electronic label by everyone, and Internet of Things can be found their particular location.Can machine, device, personnel be managed concentratedly, be controlled with centralized computer by Internet of Things, also can carry out remote control to home devices, automobile, and location searching, prevent article stolen.Along with the renewal speed of hardware is more and more fast, software also must be constantly updated to support new hardware.Flourish and the demand of accompaniment networking, how for numerous electronic installation, via network correctly and immediately carry out software upgrading, just becomes an important topic in network design.
Summary of the invention
An object of the present invention be to provide a kind of can via network correctly and immediately carry out network system and the Oftware updating method of software upgrading, to solve the problem.
In order to achieve the above object, on the one hand, the invention provides a kind of network system, comprise end device, the first router, the second router, the first border router, the second boundary router and server, this first router couples this end device; This second router couples this end device; This first border router couples this first router; This second boundary router couples this second router; This server, forms communication by world-wide web and this first border router and this second boundary router; Wherein, the first update software is sent to this first border router and this second boundary router via this world-wide web by this server respectively; This first update software is sent to this first router by this first border router, and this first update software is sent to this second router by this second boundary router; This first update software is sent to this end device by this first router, and this first update software is sent to this end device by this second router; Whether this end device judges from this first router identical with the version information of two these the first update software that this second router receives; When this first router is identical with the version information of two these the first update software that this second router receives, this end device performs the refresh routine of this first update software; When the version information of two these the first update software received from this first router and this second router is different, this end device stops the refresh routine of this first update software.
Preferably, this end device perform or stop this first update software refresh routine after, renewal message is sent to respectively this first router and this second router; This renewal message is sent to this first border router by this first router, and this renewal message is sent to this second boundary router by this second router; This renewal message is sent to this server via this world-wide web by this first border router, and this renewal message is sent to this server via this world-wide web by this second boundary router; This server judges that whether the version information of two these renewal messages received with this second boundary router from this first border router is identical; When this first border router is identical with the version information of two these renewal messages that this second boundary router receives, this server records this renewal message in data bank; When the version information of two these renewal messages received from this first border router and this second boundary router is different, this server does not record this renewal message.
Preferably, this first border router separately couples this second router, and this second router separately couples this first router; Second update software is sent to this first border router via this world-wide web by this server; When line when between this first border router and this first router breaks, this second update software is sent to this second router by this first border router; This second update software is sent to this first router by this second router; This second update software is sent to this end device by this first router; This end device performs the refresh routine of this second update software after receiving this second update software.
Preferably, after this end device performs the refresh routine of this second update software, renewal message is sent to this first router; This renewal message is sent to this second router by this first router; This renewal message is sent to this first border router by this second router; This renewal message is sent to this server via this world-wide web by this first border router; This server records this renewal message in data bank.
Preferably, the connection when between this second router and this end device disconnects and connection between this second boundary router and this Internet disconnects time, the 3rd update software is sent to this first border router via this world-wide web by this server; 3rd update software is sent to this first router by this first border router; 3rd update software is sent to this end device by this first router; After this end device receives the 3rd update software, perform the refresh routine of the 3rd update software.
Preferably, when this end device is in park mode, the 3rd update software is held in waiting list by this first router; When this end device is waken up from this park mode, the 3rd update software is sent to this end device by this waiting list by this first router.
Preferably, renewal message is sent to this first router after performing the refresh routine of the 3rd update software by this end device; This renewal message is sent to this first border router by this first router; This renewal message is sent to this server via this world-wide web by this first border router; This server records this renewal message in data bank.
Preferably, peripheral device couples this end device and the 4th update software is sent to this end device; After this end device receives the 4th update software, perform the refresh routine of the 4th update software; Renewal message is sent to this first router after performing the refresh routine of the 4th update software by this end device; This renewal message is sent to this first border router by this first router; This renewal message is sent to this server via this world-wide web by this first border router; This server records this renewal message in data bank.
On the other hand, the invention provides a kind of Oftware updating method, comprise:
First update software is sent to the first border router and the second boundary router via world-wide web by server respectively;
This first update software is sent to the first router by this first border router, and this first update software is sent to the second router by this second boundary router;
This first update software is sent to end device by this first router, and this first update software is sent to this end device by this second router;
Whether this end device judges from this first router identical with the version information of two these the first update software that this second router receives;
When this first router is identical with the version information of two these the first update software that this second router receives, this end device performs the refresh routine of this first update software; And
When the version information of two these the first update software received from this first router and this second router is different, this end device stops the refresh routine of this first update software.
Preferably, separately comprise:
This end device perform or stop this first update software refresh routine after, renewal message is sent to respectively this first router and this second router;
This renewal message is sent to this first border router by this first router, and this renewal message is sent to this second boundary router by this second router;
This renewal message is sent to this server via this world-wide web by this first border router, and this renewal message is sent to this server via this world-wide web by this second boundary router;
This server judges that whether the version information of two these renewal messages received with this second boundary router from this first border router is identical;
When this first border router is identical with the version information of two these renewal messages that this second boundary router receives, this server records this renewal message in data bank; And
When the version information of two these renewal messages received from this first border router and this second boundary router is different, this server does not record this renewal message.
Preferably, separately comprise:
Second update software is sent to this first border router via this world-wide web by this server;
When line when between this first border router and this first router breaks, this second update software is sent to this second router by this first border router;
This second update software is sent to this first router by this second router;
This second update software is sent to this end device by this first router; And
This end device performs the refresh routine of this second update software after receiving this second update software.
Preferably, separately comprise:
After this end device performs the refresh routine of this second update software, renewal message is sent to this first router;
This renewal message is sent to this second router by this first router;
This renewal message is sent to this first border router by this second router;
This renewal message is sent to this server via this world-wide web by this first border router; And
This server records this renewal message in data bank.
Preferably, separately comprise:
3rd update software is sent to this first border router via this world-wide web by this server;
3rd update software is sent to this first router by this first border router;
3rd update software is sent to this end device by this first router; And
After this end device receives the 3rd update software, perform the refresh routine of the 3rd update software.
Preferably, separately comprise:
When this end device is in park mode, the 3rd update software is held in waiting list by this first router; And when this end device is waken up from this park mode, the 3rd update software is sent to this end device by this waiting list by this first router.
Preferably, separately comprise:
Renewal message is sent to this first router after performing the refresh routine of the 3rd update software by this end device;
This renewal message is sent to this first border router by this first router;
This renewal message is sent to this server via this world-wide web by this first border router; And
This server records this renewal message in data bank.
Preferably, separately comprise:
Peripheral device couples this end device and the 4th update software is sent to this end device;
After this end device receives the 4th update software, perform the refresh routine of the 4th update software;
Renewal message is sent to this first router after performing the refresh routine of the 4th update software by this end device;
This renewal message is sent to this first border router by this first router;
This renewal message is sent to this server via this world-wide web by this first border router; And
This server records this renewal message in data bank.
In sum, network system provided by the invention and Oftware updating method, update software is sent to end device via different border routers and router by server system respectively, end device only when judging that the version information of the update software received from different routers is identical, just can perform the refresh routine of update software; Otherwise end device, when judging that the version information of the update software received from different routers is different or only have from single router reception update software, just can stop the refresh routine of update software.By this, can via network correctly and immediately carry out software upgrading, and then prevent other people from arbitrarily end device is carried out to the software upgrading of mistake.
Accompanying drawing explanation
Fig. 1 is the functional block diagram of network system according to an embodiment of the invention;
Fig. 2 is the partial process view of Oftware updating method according to an embodiment of the invention;
Fig. 3 is the partial process view of Oftware updating method according to an embodiment of the invention;
Fig. 4 is the functional block diagram of network system according to another embodiment of the present invention;
Fig. 5 is the process flow diagram of Oftware updating method according to another embodiment of the present invention;
Fig. 6 is the functional block diagram of network system according to another embodiment of the present invention;
Fig. 7 is the process flow diagram of Oftware updating method according to another embodiment of the present invention;
Fig. 8 couples the functional block diagram of the end device of the network system described in Fig. 6 for a peripheral device;
Fig. 9 is the process flow diagram of Oftware updating method according to another embodiment of the present invention.
Embodiment
For making there is further understanding to object of the present invention, structure, feature and function thereof, embodiment is hereby coordinated to be described in detail as follows.
Refer to Fig. 1 to Fig. 3, Fig. 1 is the functional block diagram of network system 1 according to an embodiment of the invention, Fig. 2 is the partial process view of Oftware updating method according to an embodiment of the invention, and Fig. 3 is the partial process view of Oftware updating method according to an embodiment of the invention.Oftware updating method in Fig. 2 and Fig. 3 is applicable to the network system 1 in Fig. 1.
As shown in Figure 1, network system 1 comprises end device 10, the first router (router) 12, the second router 14, first border router (borderrouter) 16, the second boundary router one 8 and server (server) 20.The first router 12 couples end device 10, and the second router 14 also couples end device 10.First border router 16 couples the first router 12, and the second boundary router one 8 couples the second router 14.Server 20 passes through world-wide web (Internet) 3 and the first border router 16 and the second boundary router one 8 and forms communication.In this embodiment, end device 10 can be mobile phone, household appliances, computer or other electronic installation, depending on practical application.In addition, the structure of router, border router and server forms and action principle can be reached easily by those skilled in the art, does not repeat them here.
When existing in server 20 in order to carry out the first update software of software upgrading to end device 10, the first update software first can be sent to the first border router 16 and the second boundary router one 8 (the step S10 in Fig. 2) via world-wide web 3 by server 20 respectively.The version information of the first update software, can be recorded in respectively in its data bank with the second boundary router one 8 by the first border router 16 after receiving the first update software respectively.Then, the first update software can be sent to the first router 12 by the first border router 16, and the first update software can be sent to the second router 14 (the step S12 in Fig. 2) by the second boundary router one 8.The version information of the first update software, after receiving the first update software respectively, can be recorded in its data bank by the first router 12 and the second router 14 respectively.Then, the first update software can be sent to end device 10 by the first router 12, and the first update software can be sent to end device 10 (the step S14 in Fig. 2) by the second router 14.Then, end device 10 can judge the version information of two the first update software received with the second router 14 from the first router 12 whether identical (the step S16 in Fig. 2).When end device 10 judges when the first router 12 is identical with the version information of two the first update software that the second router 14 receives, namely end device 10 can perform the refresh routine (the step S18 in Fig. 2) of the first update software.When end device 10 judges that the version information of two the first update software received from the first router 12 and the second router 14 is different, namely end device 10 can stop the refresh routine (the step S20 in Fig. 2) of the first update software.
Because server 20 is respectively the first update software is sent to end device 10 via the first different border routers 16, the second boundary router one 8 with the first router 12, the second router 14, end device 10 only when judging that the version information of the first update software received from different the first router 12, the second router 14 is identical, just can perform the refresh routine of the first update software; Otherwise, end device 10 is judging that the version information of the first update software received from different the first router 12, the second router 14 is different or only have from single router (such as, the first router 12 or the second router 14) receive the first update software when, just can stop the refresh routine of the first update software.By this, can via network correctly and immediately carry out software upgrading, and then prevent other people from arbitrarily end device 10 is carried out to the software upgrading of mistake.
In addition, after end device 10 performs or stops the refresh routine of the first update software, message can be upgraded by one further and be sent to the first router 12 and the second router 14 (the step S22 in Fig. 3) respectively.Then, renewal message can be sent to the first border router 16 by the first router 12, and renewal message can be sent to the second boundary router one 8 (the step S24 in Fig. 3) by the second router 14.Then, renewal message can be sent to server 20 via world-wide web 3 by the first border router 16, and renewal message can be sent to server 20 (the step S26 in Fig. 3) via world-wide web 3 by the second boundary router one 8.Then, server 20 two of can judge to receive from the first border router 16 and the second boundary router one 8 upgrade the version information whether identical (the step S27 in Fig. 3) of message.When server 20 judges that, when the first border router 16 is identical with the version information that two that the second boundary router one 8 receives upgrade message, namely server 20 can record this and upgrade message (the step S28 in Fig. 3) in its data bank.When two that judge to receive from the first border router 16 and the second boundary router one 8 when the server 20 version information upgrading message are different, server 20 does not just record this renewal message (the step S29 in Fig. 3).Above-mentioned renewal message can be and is updated successfully message or upgrades fail message, depending on the refresh routine of end device 10 whether successful execution first update software, when the refresh routine of end device 10 successful execution first update software, above-mentioned renewal message is for being updated successfully message, and server 20 can perform above-mentioned steps 28, and when the refresh routine of end device 10 unsuccessful execution first update software, above-mentioned renewal message is for upgrading fail message, and server 20 can perform above-mentioned steps S29.By this, the keeper of server 20 and/or the user of end device 10 can upgrade by this software upgrading state that message grasps end device 10.
Refer to Fig. 4 and Fig. 5, Fig. 4 is the functional block diagram of network system 1' according to another embodiment of the present invention, and Fig. 5 is the process flow diagram of Oftware updating method according to another embodiment of the present invention.Oftware updating method in Fig. 5 is applicable to the network system 1' in Fig. 4.The main difference part of network system 1' and above-mentioned network system 1 is, network system 1' does not comprise above-mentioned the second boundary router one 8, first border router 16 separately couples the second router 14, and the second router 14 separately couples the first router 12, as shown in Figure 4.In this embodiment, when existing in server 20 in order to carry out the second update software of software upgrading to end device 10, the second update software first can be sent to the first border router 16 (the step S30 in Fig. 5) via world-wide web 3 by server 20.The version information of the second update software, after reception second update software, can be recorded in its data bank by the first border router 16.Then, when the line that the first border router 16 finds between the first border router 16 and the first router 12 breaks, the second update software can be sent to the second router 14 (the step S32 in Fig. 5) by the first border router 16.Because the second router 14 couples the first router 12, therefore, the second update software can be sent to the first router 12 (the step S34 in Fig. 5) by the second router 14.The version information of the second update software, after reception second update software, can be recorded in its data bank by the first router 12.Then, the second update software can be sent to end device 10 (the step S36 in Fig. 5) by the first router 12.After end device 10 receives the second update software, the refresh routine (the step S38 in Fig. 5) of the second update software can be performed.
In other words, because the second router 14 couples the first router 12, even if the line between the first border router 16 and the first router 12 breaks, second update software is still sent to the first router 12 by the second router 14 by the first border router 16, by the first router 12, second update software is sent to end device 10 again, to carry out software upgrading to end device 10.
In addition, after end device 10 performs the refresh routine of the second update software, message (that is, be updated successfully message) can be upgraded by one further and be sent to the first router 12 (the step S40 in Fig. 5).Then, because the line between the first border router 16 and the first router 12 breaks, renewal message can be sent to the second router 14 (the step S42 in Fig. 5) by the first router 12.Then, renewal message can be sent to the first border router 16 (the step S44 in Fig. 5) by the second router 14.Then, renewal message can be sent to server 10 (the step S46 in Fig. 5) via world-wide web 3 by the first border router 16.Finally, namely server 20 can record this renewal message (the step S48 in Fig. 5) in its data bank.By this, the keeper of server 20 and/or the user of end device 10 can upgrade by this software upgrading state that message grasps end device 10.
Refer to Fig. 6 and Fig. 7, Fig. 6 is network system 1 according to another embodiment of the present invention " functional block diagram, Fig. 7 is the process flow diagram of Oftware updating method according to another embodiment of the present invention.Oftware updating method in Fig. 7 is applicable to the network system 1 in Fig. 6 ".Network system 1 " be with the main difference part of above-mentioned network system 1, network system 1 " do not comprise above-mentioned the second router 14 and the second boundary router one 8, as shown in Figure 6.Connection when the second router 14 in network system 1 and the connection disconnection between end device 10 and between the second boundary router one 8 and Internet 3 disconnects, network system 1 " do not comprise above-mentioned the second router 14 and the second boundary router one 8.In this embodiment, when existing in server 20 in order to carry out the 3rd update software of software upgrading to end device 10, the 3rd update software first can be sent to the first border router 16 (the step S50 in Fig. 7) via world-wide web 3 by server 20.The version information of the 3rd update software, after reception the 3rd update software, can be recorded in its data bank by the first border router 16.Then, the 3rd update software can be sent to the first router 12 (the step S52 in Fig. 7) by the first border router 16.The version information of the 3rd update software, after reception the 3rd update software, can be recorded in its data bank by the first router 12.Then, the 3rd update software can be sent to end device 10 (the step S54 in Fig. 7) by the first router 12.After end device 10 receives the 3rd update software, the refresh routine (the step S56 in Fig. 7) of the 3rd update software can be performed.
In other words, when the first router 12 and the first border router 16 are all in normal operating conditions, namely 3rd update software is sent to end device 10, to carry out software upgrading to end device 10 by the first border router 16 with the first router 12 by server 20.It should be noted that, when the 3rd update software is sent to end device 10 by the first router 12 and end device 10 is in a park mode, the 3rd update software first can be held in a waiting list (queue) by the first router 12.When end device 10 is waken up from park mode, the 3rd update software is sent to end device 10 by waiting list by the first router 12 again.
In addition, after end device 10 performs the refresh routine of the 3rd update software, message (that is, be updated successfully message) can be upgraded by one further and be sent to the first router 12 (the step S58 in Fig. 7).Then, renewal message can be sent to the first border router 16 (the step S60 in Fig. 7) by the first router 12.Then, renewal message can be sent to server 10 (the step S62 in Fig. 7) via world-wide web 3 by the first border router 16.Finally, namely server 20 can record this renewal message (the step S64 in Fig. 7) in its data bank.By this, the keeper of server 20 and/or the user of end device 10 can upgrade by this software upgrading state that message grasps end device 10.
Refer to Fig. 8 and Fig. 9, Fig. 8 couples the network system 1 described in Fig. 6 for a peripheral device 5 " the functional block diagram of end device 10, Fig. 9 is the process flow diagram of Oftware updating method according to another embodiment of the present invention.Oftware updating method in Fig. 9 is applicable to the network system 1 coupled with peripheral device 5 in Fig. 8 ".In this embodiment, a peripheral device 5 can be coupled end device 10 and one the 4th update software is sent to end device 10 (the step S70 in Fig. 9) from peripheral device 5 by user, as shown in Figure 8.After end device 10 receives the 4th update software, the refresh routine (the step S72 in Fig. 9) of the 4th update software can be performed.In other words, the present invention, except being undertaken except software upgrading by server 20 pairs of end devices 10, also directly can carry out software upgrading to end device 10 by peripheral device 5.It should be noted that, when the 4th update software is sent to end device 10 by the first router 12 and end device 10 is in park mode, the 4th update software first can be held in waiting list (queue) by the first router 12; When end device 10 is waken up from park mode, the 4th update software is sent to end device 10 by waiting list by the first router 12 again.It should be noted that, the network system 1 in Fig. 8 " can also the network system 1 in Fig. 1 or the network system 1' in Fig. 4 replace.In this embodiment, peripheral device 5 can be computer, server or other electronic installation, depending on practical application.
In addition, after end device 10 performs the refresh routine of the 4th update software, message (that is, be updated successfully message) can be upgraded by one further and be sent to the first router 12 (the step S74 in Fig. 9).Then, renewal message can be sent to the first border router 16 (the step S76 in Fig. 9) by the first router 12.Then, renewal message can be sent to server 10 (the step S78 in Fig. 9) via world-wide web 3 by the first border router 16.Finally, namely server 20 can record this renewal message (the step S80 in Fig. 9) in its data bank.By this, the keeper of server 20 and/or the user of end device 10 can upgrade by this software upgrading state that message grasps end device 10.It should be noted that, network system 1 when in Fig. 8 " when replacing with the network system 1 in Fig. 1 or the network system 1' in Fig. 4; after end device 10 performs the refresh routine of update software; further the mode upgrading message and be sent to server 20 is corresponded to step S40 shown in Fig. 3 or shown in Fig. 5 to step S48, the embodiment of the present invention does not repeat them here.
It should be noted that, the steering logic of the Oftware updating method described in the various embodiments described above can realize by Software for Design.Certainly, the various piece in steering logic or function all realize by the combination of software, hardware or software and hardware.
In sum, update software can be sent to end device via different border routers and router by server of the present invention respectively, end device only when judging that the version information of the update software received from different routers is identical, just can perform the refresh routine of update software; Otherwise end device, when judging that the version information of the update software received from different routers is different or only have from single router reception update software, just can stop the refresh routine of update software.By this, can via network correctly and immediately carry out software upgrading, and then prevent other people from arbitrarily end device is carried out to the software upgrading of mistake.In addition, when the line when between border router and core gateway breaks, update software is still sent to the core gateway coupled with end device by border router by other router, to carry out software upgrading to end device.Moreover, when update software is sent to end device by router and end device is in park mode, update software first can be held in waiting list by router, and when end device is waken up from park mode, update software is sent to end device by waiting list by router again.What is more, peripheral device also can be coupled end device by user, directly to carry out software upgrading to end device by peripheral device.
The present invention is described by above-mentioned related embodiment, but above-described embodiment is only enforcement example of the present invention.Must it is noted that the embodiment disclosed limit the scope of the invention.On the contrary, change done without departing from the spirit and scope of the present invention and retouching, all belong to scope of patent protection of the present invention.
Claims (16)
1. a network system, is characterized in that, comprises:
End device;
The first router, couples this end device;
The second router, couples this end device;
First border router, couples this first router;
The second boundary router, couples this second router; And
Server, forms communication by world-wide web and this first border router and this second boundary router;
Wherein, the first update software is sent to this first border router and this second boundary router via this world-wide web by this server respectively; This first update software is sent to this first router by this first border router, and this first update software is sent to this second router by this second boundary router; This first update software is sent to this end device by this first router, and this first update software is sent to this end device by this second router; Whether this end device judges from this first router identical with the version information of two these the first update software that this second router receives; When this first router is identical with the version information of two these the first update software that this second router receives, this end device performs the refresh routine of this first update software; When the version information of two these the first update software received from this first router and this second router is different, this end device stops the refresh routine of this first update software.
2. network system as claimed in claim 1, is characterized in that, after this end device performs or stops the refresh routine of this first update software, renewal message is sent to respectively this first router and this second router; This renewal message is sent to this first border router by this first router, and this renewal message is sent to this second boundary router by this second router; This renewal message is sent to this server via this world-wide web by this first border router, and this renewal message is sent to this server via this world-wide web by this second boundary router; This server judges that whether the version information of two these renewal messages received with this second boundary router from this first border router is identical; When this first border router is identical with the version information of two these renewal messages that this second boundary router receives, this server records this renewal message in data bank; When the version information of two these renewal messages received from this first border router and this second boundary router is different, this server does not record this renewal message.
3. network system as claimed in claim 1, it is characterized in that, this first border router separately couples this second router, and this second router separately couples this first router; Second update software is sent to this first border router via this world-wide web by this server; When line when between this first border router and this first router breaks, this second update software is sent to this second router by this first border router; This second update software is sent to this first router by this second router; This second update software is sent to this end device by this first router; This end device performs the refresh routine of this second update software after receiving this second update software.
4. network system as claimed in claim 3, is characterized in that, after this end device performs the refresh routine of this second update software, renewal message is sent to this first router; This renewal message is sent to this second router by this first router; This renewal message is sent to this first border router by this second router; This renewal message is sent to this server via this world-wide web by this first border router; This server records this renewal message in data bank.
5. network system as claimed in claim 1, it is characterized in that, connection when between this second router and this end device disconnects and connection between this second boundary router and this Internet disconnects time, the 3rd update software is sent to this first border router via this world-wide web by this server; 3rd update software is sent to this first router by this first border router; 3rd update software is sent to this end device by this first router; After this end device receives the 3rd update software, perform the refresh routine of the 3rd update software.
6. network system as claimed in claim 5, it is characterized in that, when this end device is in park mode, the 3rd update software is held in waiting list by this first router; When this end device is waken up from this park mode, the 3rd update software is sent to this end device by this waiting list by this first router.
7. the network system as described in claim 5 or 6, is characterized in that, renewal message is sent to this first router after performing the refresh routine of the 3rd update software by this end device; This renewal message is sent to this first border router by this first router; This renewal message is sent to this server via this world-wide web by this first border router; This server records this renewal message in data bank.
8. network system as claimed in claim 1, it is characterized in that, peripheral device couples this end device and the 4th update software is sent to this end device; After this end device receives the 4th update software, perform the refresh routine of the 4th update software; Renewal message is sent to this first router after performing the refresh routine of the 4th update software by this end device; This renewal message is sent to this first border router by this first router; This renewal message is sent to this server via this world-wide web by this first border router; This server records this renewal message in data bank.
9. an Oftware updating method, is characterized in that, comprises:
First update software is sent to the first border router and the second boundary router via world-wide web by server respectively;
This first update software is sent to the first router by this first border router, and this first update software is sent to the second router by this second boundary router;
This first update software is sent to end device by this first router, and this first update software is sent to this end device by this second router;
Whether this end device judges from this first router identical with the version information of two these the first update software that this second router receives;
When this first router is identical with the version information of two these the first update software that this second router receives, this end device performs the refresh routine of this first update software; And
When the version information of two these the first update software received from this first router and this second router is different, this end device stops the refresh routine of this first update software.
10. Oftware updating method as claimed in claim 9, is characterized in that, separately comprise:
This end device perform or stop this first update software refresh routine after, renewal message is sent to respectively this first router and this second router;
This renewal message is sent to this first border router by this first router, and this renewal message is sent to this second boundary router by this second router;
This renewal message is sent to this server via this world-wide web by this first border router, and this renewal message is sent to this server via this world-wide web by this second boundary router;
This server judges that whether the version information of two these renewal messages received with this second boundary router from this first border router is identical;
When this first border router is identical with the version information of two these renewal messages that this second boundary router receives, this server records this renewal message in data bank; And
When the version information of two these renewal messages received from this first border router and this second boundary router is different, this server does not record this renewal message.
11. Oftware updating methods as claimed in claim 9, is characterized in that, separately comprise:
Second update software is sent to this first border router via this world-wide web by this server;
When line when between this first border router and this first router breaks, this second update software is sent to this second router by this first border router;
This second update software is sent to this first router by this second router;
This second update software is sent to this end device by this first router; And
This end device performs the refresh routine of this second update software after receiving this second update software.
12. Oftware updating methods as claimed in claim 11, is characterized in that, separately comprise:
After this end device performs the refresh routine of this second update software, renewal message is sent to this first router;
This renewal message is sent to this second router by this first router;
This renewal message is sent to this first border router by this second router;
This renewal message is sent to this server via this world-wide web by this first border router; And
This server records this renewal message in data bank.
13. Oftware updating methods as claimed in claim 9, is characterized in that, separately comprise:
3rd update software is sent to this first border router via this world-wide web by this server;
3rd update software is sent to this first router by this first border router;
3rd update software is sent to this end device by this first router; And
After this end device receives the 3rd update software, perform the refresh routine of the 3rd update software.
14. Oftware updating methods as claimed in claim 13, is characterized in that, separately comprise:
When this end device is in park mode, the 3rd update software is held in waiting list by this first router; And
When this end device is waken up from this park mode, the 3rd update software is sent to this end device by this waiting list by this first router.
15. Oftware updating methods as described in claim 13 or 14, is characterized in that, separately comprise:
Renewal message is sent to this first router after performing the refresh routine of the 3rd update software by this end device;
This renewal message is sent to this first border router by this first router;
This renewal message is sent to this server via this world-wide web by this first border router; And
This server records this renewal message in data bank.
16. Oftware updating methods as claimed in claim 9, is characterized in that, separately comprise:
Peripheral device couples this end device and the 4th update software is sent to this end device;
After this end device receives the 4th update software, perform the refresh routine of the 4th update software;
Renewal message is sent to this first router after performing the refresh routine of the 4th update software by this end device;
This renewal message is sent to this first border router by this first router;
This renewal message is sent to this server via this world-wide web by this first border router; And
This server records this renewal message in data bank.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510731504.5A CN105320541B (en) | 2015-11-02 | 2015-11-02 | Network system and Oftware updating method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510731504.5A CN105320541B (en) | 2015-11-02 | 2015-11-02 | Network system and Oftware updating method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105320541A true CN105320541A (en) | 2016-02-10 |
| CN105320541B CN105320541B (en) | 2018-08-24 |
Family
ID=55247966
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510731504.5A Expired - Fee Related CN105320541B (en) | 2015-11-02 | 2015-11-02 | Network system and Oftware updating method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105320541B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1271888A (en) * | 2000-05-15 | 2000-11-01 | 倚天资讯股份有限公司 | Method for updating software by bidirectional wireless transmission |
| CN1553314A (en) * | 2003-05-30 | 2004-12-08 | 英业达股份有限公司 | Automatic updating method and system for programs of server |
| CN1784038A (en) * | 2004-12-01 | 2006-06-07 | 倚天资讯股份有限公司 | Program down loading updating system and method |
| CN1987784A (en) * | 2005-12-22 | 2007-06-27 | 佛山市顺德区顺达电脑厂有限公司 | Method for active software renewing for digital device through computer system |
-
2015
- 2015-11-02 CN CN201510731504.5A patent/CN105320541B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1271888A (en) * | 2000-05-15 | 2000-11-01 | 倚天资讯股份有限公司 | Method for updating software by bidirectional wireless transmission |
| CN1553314A (en) * | 2003-05-30 | 2004-12-08 | 英业达股份有限公司 | Automatic updating method and system for programs of server |
| CN1784038A (en) * | 2004-12-01 | 2006-06-07 | 倚天资讯股份有限公司 | Program down loading updating system and method |
| CN1987784A (en) * | 2005-12-22 | 2007-06-27 | 佛山市顺德区顺达电脑厂有限公司 | Method for active software renewing for digital device through computer system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105320541B (en) | 2018-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101515926B (en) | Device management method for device management system | |
| CN102546760B (en) | The method of equipment control and terminal, device, system | |
| WO2016090846A1 (en) | Network version upgrade method and apparatus | |
| CN105843895A (en) | EhCache-based data querying and synchronizing method, device and system | |
| CN102918803A (en) | Techniques for managing devices not directly accessible to device management server | |
| CN103514016A (en) | Method and device for upgrading system version and base station controller | |
| CN102739681A (en) | Method and device for login control to log in server | |
| CN102487522B (en) | Management method and gateway device of terminal devices | |
| CN107168752A (en) | A kind of firmware upgrade method based on Element management system | |
| CN102571446A (en) | Method, device and system for upgrading network device | |
| CN106558126B (en) | A kind of gate inhibition's key code management method and system | |
| CN102083244A (en) | Mobile value added service system based on embedded type virtual machine mode | |
| CN105790976B (en) | Realize that virtual network function describes the method and system of Automatic Update of File | |
| CN111010429A (en) | Method and system for managing equipment running state based on platform of Internet of things | |
| CN102902579B (en) | Processing system for functional assembly | |
| CN101163048A (en) | Method of implementing centralized network management | |
| CN102571418B (en) | Method for equipment management | |
| CN104104701A (en) | Online service configuration updating method and system | |
| CN104869129B (en) | A kind of application management method, equipment and system | |
| CN103327133A (en) | Method and device for updating geographic position information | |
| CN101340286A (en) | Session connection initiating method and apparatus | |
| CN105320541A (en) | Network system and software update method | |
| CN103118092A (en) | Method and device for realizing single login | |
| TWI540512B (en) | Network system and software updating method | |
| CN103002564B (en) | Wireless Internet access method, radio networking device, server and wireless networking system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20180824 Termination date: 20201102 |