CN101635722B - TR-069 savepoints - Google Patents
TR-069 savepoints Download PDFInfo
- Publication number
- CN101635722B CN101635722B CN2009101516986A CN200910151698A CN101635722B CN 101635722 B CN101635722 B CN 101635722B CN 2009101516986 A CN2009101516986 A CN 2009101516986A CN 200910151698 A CN200910151698 A CN 200910151698A CN 101635722 B CN101635722 B CN 101635722B
- Authority
- CN
- China
- Prior art keywords
- session
- rpc
- acs
- affairs
- savepoint
- 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.)
- Expired - Fee Related
Links
Images
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/0876—Aspects of the degree of configuration automation
-
- 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/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
- H04L12/2898—Subscriber equipments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
-
- 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/133—Protocols for remote procedure calls [RPC]
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention relates to TR-069 savepoints. A method for improving the security of actions performed by Remote Procedure Calls RPC invoked during a TR-069 Remote Management Protocol session between an Auto- Configuration Server ACS and a Customer Premises Equipment CPE of a DSL telecommunication system. The TR-069 session comprises several RPCs executing actions on parameters of an object model and the method comprises the steps of - starting a TR-069 session wherein RPCs are invoked; - opening a transactional TR-069 session or transaction whereby parameters of the object model handled by RPCs are protected through a SavePoint mechanism! - closing the transaction by the ACS; and either- committing the transaction via a StoreSavePoint RPC invoked by the ACS, or - rolling-back actions of RPCs via a RestoreSavePoint RPC also invoked by the ACS. If the transaction is not committed during a first TR-069 session, the CPE sends an Inform with an event code OpenSavePoint to the ACS during a next TR-069 session and the ACS may reply by including an additional field in the InformResponse to close the transaction.
Description
Technical field
The present invention relates to a kind of method of the fail safe for improvement of the action of being carried out by invoked remote procedure call RPC during the client device CPE of DSL telecommunication system and the TR-069 remote management protocol session between the Automatic Configuration Server ACS, described TR-069 session comprises that execution is about a plurality of described remote procedure call of the action of object model parameter.
Background technology
This method is well known in the prior art.The TR-069 remote management protocol comprises the object model that calls remote procedure call RPC thereon.
Remote management protocol is that the technical report TR-069 by DSL forum is configured to automatically at safety and other CPE management functions and the CPE WAN management agreement CWMP that defines.In other words, TR-069 be a kind of at CPE and comprise that safety in the common framework is configured to automatically and the Automatic Configuration Server ACS of other CPE management functions between the agreement that communicates.Technical report TR-069 and modification thereof are as being published on the following network address:
<http://www.broadband-forum.org/technical/trlist.php>。
Remote procedure call RPC is performed as atomic action, namely or be the RPC success and move in full force and effect, or RPC failure and last part change that remains unfulfilled up to carrying out RPC.For example, will can not influence object model under the situation of generation mistake during carrying out RPC such as SetParameterValues, SetParameterAttributes, AddObject.
Although the RPC atomicity has been protected the change that takes place in single RPC level, yet do not provide similar methods in session level.Yet, be necessary in the example that this discourse referent atomicity is described below:
-some parameter value change meetings are interrupted connectedness with ACS in irreversible mode, consequently CPE is for example inserted in the InternetGatewayDevice.ManagementServer object by ACS URL or the wrong ACS certificate that can not arrive by brick work (bricked);
-open service gateway initiative standard OSGi bundle (particularly under the situation of this machine of providing code) is brought service platform into labile state (high cpu load for example, internal memory overflow or connect interruption), because it is inappropriate for platform or operating software;
DSL configuration-mistake or unsuitable, IP route, fire compartment wall parameter etc.
In these cases, all RPC are successful execution, but the Pending The Entry Into Force of its session own.
Best existing solution is to provide some fail safes by the software/hardware WatchDog Timer.The purpose of WatchDog Timer restarts whole platform when detecting unsteadiness (being to be caused by CPU or kernel overload traditionally), solve the problem that this platform meets with to expect it.
Yet, in this case, the failure of typical house dog mechanism.CPE is by brick work, because wrong configuration parameter dump.Restart and to deal with problems, because harmful change is handled (committed) during the session of last once TR-069 remote management protocol, and does not predict the based on feedback link between fallback mechanism and TR-069 and the WatchDog Timer in the TR-069 agreement recessively.
Summary of the invention
The purpose of this invention is to provide a kind of method for improvement of the above-mentioned known type of the fail safe of invoked action during the session of TR-069 remote management protocol.
According to the present invention, this purpose is owing to described method comprises the following steps to be achieved:
Remote procedure call is wherein called in the session of-beginning TR-069 remote management protocol;
-open affairs TR-069 session, the parameter of the described object model of being handled by remote procedure call is protected by savepoint mechanism thus;
-close described affairs TR-069 session by described Automatic Configuration Server ACS;
And described method also comprises the following steps:
-handle described affairs TR-069 session by the StoreSavePoint RPC that is called by described Automatic Configuration Server, or
-come the action of rollback remote procedure call by the RestoreSavePoint RPC that is called by described Automatic Configuration Server.
Like this, if RPC success and action come into force fully, then the StoreSavePoint RPC that is called by ACS handles change and orders CPE to close affairs TR-069 session, only is called affairs after this session.All changes thereby maintenance continue.
On the other hand, if the RPC failure, the RestoreSavePoint RPC request CPE that is called by ACS returns the state of before having preserved by savepoint mechanism.All changes thereby do not finish.
As a result, stoped CPE during the session of TR-069 remote management protocol by brick work or locking.
Another feature embodiment of the present invention is to open described affairs TR-069 session recessively when the session of described TR-069 remote management protocol begins.
In this case, when the first remote procedure call RPC of TR-069 remote management protocol session when client device CPE is called, affairs TR-069 session is opened recessively.This means that from this moment each TR-069 session is affairs.
Another feature embodiment of the present invention be described affairs TR-069 session by the StartRecording RPC that is called by described Automatic Configuration Server ACS by dominance open.
This is to open method more flexibly than recessiveness when the TR-069 session begins.Automatic Configuration Server ACS notice client device CPE opens affairs TR-069 session, because the action that will carry out during the TR-069 session or change may be harmful to.
Another feature embodiment of the present invention be described affairs TR-069 session be by by described Automatic Configuration Server ACS during the session of described TR-069 remote management protocol or the normal savepoint that during the session of follow-up TR-069 remote management protocol, calls handle RPC and handle.
Like this, affairs TR-069 session or affairs are processed during the TR-069 remote management protocol session of setting up, and perhaps when dominance was handled in the TR-069 session that affairs are being moved, it must be processed in follow-up TR-069 session.
In modified characteristics embodiment of the present invention, described affairs TR-069 session is to handle RPC by the timing savepoint that is called by described Automatic Configuration Server ACS to handle, and described timing savepoint processing RPC has fixed the delay between TR-069 remote management protocol that set up and the follow-up session.
In order to make client device CPE avoid locking (lockout), next TR-069 session can be by being to be scheduled after calling determined given period by described Automatic Configuration Server ACS.
In preferred feature embodiment of the present invention, described Automatic Configuration Server ACS calls a plurality of timing savepoints and handles RPC during identical affairs TR-069 session, and each follow-up timing savepoint processing RPC has fixed than handling the shorter delay of delay that RPC fixed by the savepoint of timing formerly among described a plurality of timing savepoints processing RPC.
This nested savepoint system has realized the recovery of part.
Another feature embodiment of the present invention is when described affairs TR-069 session is not processed during a TR-069 remote management protocol session, described client device CPE during the session of next TR-069 remote management protocol, send have event code OpenSavePoint Inform to described Automatic Configuration Server ACS, and described Automatic Configuration Server ACS is contained among the InformResponse added field to close affairs TR-069 session and to handle a described TR-069 remote management protocol session.
When less than dominance ground processing transactions in the TR-069 session of operation, it must be processed in next TR-069 session.In this case, it is processed with the affairs wait that prompting ACS has change that CPE sends the Inform with new event code OpenSavePoint.ACS thus added field is contained among the InformResponse to close these affairs and handle before the TR-069 session.
Should be pointed out that ACS can trigger CPE and set up session by ConnectionRequest.In this case, CPE also should send the OpenSavePoint event code in Inform message.
Another feature embodiment of the present invention is that described savepoint mechanism is kept at the parameter value of the described object model of handling before any remote procedure call.
Like this, if affairs are not handled by StoreSavePoint RPC, then CPE should recover the savepoint of the supreme single treatment of its state.
Another feature embodiment of the present invention is that described savepoint mechanism preserves described parameter value by the client device CPE that described parameter value is stored in described DSL telecommunication system.
This makes server needn't store the change of each CPE and the rollback scene of support relative complex again.
Other features embodiment of the inventive method has been described in the appended claim.
Should be pointed out that the term that uses in the claim " comprises " should not being interpreted into is limited to the device of listing thereafter.Therefore, the scope of " equipment that comprises device A and B " this statement should not be limited to the equipment of only being made up of components A and B.It means in the equipment that only relevant with the present invention parts are A and B.
Similarly, should be pointed out that the term of yet using in the claims " coupling " only should not be interpreted as being limited to directly connection.Therefore, the scope of " device A is coupled to equipment B " this statement should not be limited to equipment or the system that the wherein output of device A is directly connected to the input of equipment B.It means between the input of the output of A and B and has the path that this path can be the path that comprises other equipment or device.
Description of drawings
With reference to the accompanying drawings, by below reading to the description of embodiment, above-mentioned and other purposes of the present invention and feature will become more obviously and the present invention itself will get the best understanding, wherein:
Fig. 1 shows according to of the present invention for improvement of the method for being called out the safety of performed action during the TR-069 session by the RPC that calls;
Fig. 2 shows the particular step of the method for Fig. 1; With
Fig. 3 shows the modification of particular step shown in Figure 2.
Embodiment
Method shown in Fig. 1 is used to improve the safety by the performed action of the remote procedure call RPC that calls during the session of TR-069 remote management protocol, only be called the TR-069 session after the described session, this session is to carry out between the client device CPE of DSL telecommunication system and Automatic Configuration Server ACS.This TR-069 session comprises that several execution are about the remote procedure call RPC of the action of the parameter of object model.
Remote procedure call RPC is performed as atomic action, namely or be that RPC success and action come into force fully, or RPC failure and last part change that remains unfulfilled up to carrying out RPC.For example, SetParameterValues, SetParameterAttributes, AddObject etc. will can not influence object model under situation about making a mistake during the execution RPC.
Although the RPC atomicity has been protected the change that occurs on the single RPC level, yet the invention provides the similar approach on the session level, because all RPC can successfully carry out in some cases, session itself is Pending The Entry Into Force also.
The basic thought of the safety of the action that improvement is called during the TR-069 session is to introduce TR-069 " savepoint ".The TR-069 savepoint can be described as the snapshot of catching in particular moment best, and wherein the TR-069 object model is counted as stable.
The TR-069 savepoint has following feature:
-they preferably are stored in cpe side, this normally under the request of ACS, if but in some cases ACS not initiate then initiated by CPE also be feasible, for example under the situation of ACS URL change;
-savepoint can be when beginning most, be set up during the TR-069 session or at the TR-069 conversation end time or between one or a more than TR-069 session;
-return to last savepoint can comprise the parameter value of change and the overwrite of attribute, and/or to the execution of destruction operation, for example for the RPC rollback as the download of " unloading ".
In addition, the TR-069 savepoint can be used to:
-current state (for example object model) of CPE is backuped;
-in order to make CPE needn't store savepoint again, they can be uploaded to the telefile server, and download back CPE after a while;
-dump configuration profile (profile), this comprises is arranged to one with bigger parameter sets, the SetParameterValue method of use standard will take the long time or consume too much processing or bandwidth, and the modification of this method can be that the profile of the picture OEM that provides in advance on the CPE is provided by the savepoint of carrying out action of configuration.
At last, return to last savepoint or accept new savepoint and should further be supported by the light weight affair mechanism, this supports the processing that dominance transaction or timer monitor.Timing Processing makes CPE to return stable savepoint under the situation of losing owing to change to the connection of ACS.
In detail, the processing of TR-069 savepoint is to be supported the following operation of this mechanism by the light weight affair mechanism; Mark among mark between the square brackets and Fig. 1 similar.
At first, affairs TR-069 session (after this being called affairs) is opened [100], and the parameter of the object model of being handled by remote procedure call RPC is protected by savepoint mechanism thus.
Automatic Configuration Server ACS calls the RPC on [110] client device cpe side then.
On the one hand, when ACS finishes [120] when calling RPC, it carries out [130] TR-069 transaction session.
On the other hand, if RPC failure [140], then ACS determines whether [150] return to stable state [being] or [denying] before.
The state [being] before if ACS determines to return to, then this ACS calls [160] RestoreSavePoint RPC.The RestoreSavePoint RPC request CPE that is called by ACS is retracted into the state of before having preserved by savepoint mechanism.All changes thereby do not finish and process is returned [170] to the RPC that is called at state [110] by ACS.
If ACS determines not return [denying], then process is returned [170] immediately to the RPC that is called at state [110] by ACS.
Finish the carrying out [130] of affairs for the decision [180] of whether handling change in this stage by ACS.
If the RPC success, then ACS determines to handle [being] and changes and call [190] StoreSavePoint RPC.Action thereby come into force fully, the StoreSavePointRPC that is called by ACS handles change and order CPE closes affairs TR-069 session.All changes thereby maintenance continue.TR-069 session thereby also termination [200].
If ACS determines not handle [denying] change, then the TR-069 session stops [200] immediately.
Should be pointed out that it must be stored in next session under savepoint is not stored in situation in that set up or the current TR-069 session.
By this savepoint mechanism, wherein prevent CPE during the TR-069 session by brick work or locking, introduce two new RPC:
-StoreSavePoint RPC: when ACS handled change and orders CPE to close affairs: all changes kept continuing; With
-RestoreSavePoint RPC: when ACS request CPE return the savepoint of last storage: all changes were not finished.
In the basic realization that TR-069 savepoint shown in Figure 2 is handled, affairs TR-069 session [100] is opened in the beginning [000] of TR-069 session recessively, namely when a RPC when CPE is called.This means that from now on each TR-069 session is businesslike.
Yet owing to always do not wish to open affairs together with the session of TR-069 remote management protocol, Fig. 3 shows a kind of method more flexibly, wherein preferably uses the dominance transaction tag.Wherein, ACS notice CPE opens [050] affairs, because the change that will carry out may be harmful to.In detail, affairs TR-069 session then by the StartRecording RPC that is called by Automatic Configuration Server ACS by dominance open [050].
Can realize two types processing:
-normal savepoint is handled: this is the aforesaid processing type of opening the affairs of being called by ACS about recessive and dominance, in this case, savepoint can be processed in the session of having set up, if affairs were not handled by dominance ground in the TR-069 session of operation when perhaps a session was established instantly, then savepoint can be processed; With
-regularly savepoint is handled: in order to prevent the CPE locking, next TR-069 session can be scheduled immediately, perhaps after date is scheduled when given, regularly savepoint is handled RPC and is called and fixed the delay of setting up between TR-069 session and next the TR-069 session by ACS, in other words, next TR-069 session after date when given is scheduled, and be to handle the delay that RPC determines by the timing savepoint this given period, and this has prevented that CPE is locked.
Preferably, Automatic Configuration Server ACS calls several timing savepoints and handles RPC during same affairs.Among these continuous or nested timing savepoints processing RPC each has all been fixed ratio by the regularly fixing shorter delay of delay of savepoint processing RPC formerly.This nested savepoint system has realized the recovery of part and has promoted fault detect.
Savepoint mechanism is kept at the parameter value of the object model of handling before any remote procedure call RPC.As a result, if affairs are not handled by StoreSavePoint RPC, then suspect and break down and CPE should recover the savepoint of the supreme single treatment of its state.
More generally, when affairs were not handled by dominance ground in the TR-069 session of operation, it must be processed in next TR-069 session.
This can for example handle one of delivery mechanism by the outer affairs of following session and realize.
When affairs TR-069 session is not processed during a TR-069 session remote management protocol session, client device CPE sends during next TR-069 session has the Inform of event code to Automatic Configuration Server ACS, for example OpenSavePoint waits for processed thereby prompting ACS has the affairs of change.ACS can answer by added field is covered among the InformResponse then, thereby closes these affairs and handle savepoint and a TR-069 session.
ACS can determine that also carrying out dominance by StoreSavePoint RPC handles, and perhaps carries out dominance by RestoreSavePoint RPC and handles after the assessment rollback.
Perhaps all parameters that are not object model all need by savepoint protected.In this case, can define new parameter attribute, for example the affairs of appointment or savepoint.Only its attribute parameter of being marked as affairs or savepoint should be considered in this fine and closely woven selection.
Savepoint must be stored in cpe side.The most tangible mode is to create a file at each savepoint on the file system that comprises parameter value, attribute etc.
Also can for the purpose of backup/restoration or when CPE runs out of space on the file system with these file loadings to the telefile server.
At last, savepoint mechanism can be kept at the historical record of the remote procedure call that calls during the affairs TR-069 session at cpe side, thereby can recover parameter where necessary.
Should be pointed out that at last above with regard to functional block description embodiments of the invention.According to the functional description to these pieces that provides above, the embodiment that how to utilize the known electronic element to make these pieces is apparent for the technical staff in design of electronic devices field.Therefore do not provide the detailed construction of the content of functional block.
Although described principle of the present invention in conjunction with specified device above, yet it should be clearly understood that this description only as an example and not as limitation of the scope of the invention, the scope of the invention is defined by the following claims.
Claims (5)
1. one kind for improvement of the method by the fail safe of the performed action of invoked remote procedure call RPC during the client device CPE of DSL telecommunication system and the TR-069 remote management protocol session between the Automatic Configuration Server ACS, described TR-069 session comprises that execution is about a plurality of described remote procedure call of the action of the parameter of object model
It is characterized in that described method comprises the following steps:
The session of-beginning TR-069 remote management protocol, wherein remote procedure call is called;
-open the affairs TR-069 session different with the session of described TR-069 remote management protocol, so that the parameter of the described object model of being handled by remote procedure call RPC is preserved by savepoint mechanism, and described savepoint mechanism is kept at the parameter value of described object model processed before any remote procedure call;
If-described remote procedure call success is then handled described affairs TR-069 session by the StoreSavePoint RPC that is called by described Automatic Configuration Server;
-close described affairs TR-069 session by described Automatic Configuration Server ACS; And
If-described remote procedure call failure then comes the action of rollback remote procedure call by the RestoreSavePoint RPC that is called by described Automatic Configuration Server; Wherein, described affairs TR-069 session is opened when the session of described TR-069 remote management protocol begins recessively;
Wherein, described affairs TR-069 session is to handle RPC by the timing savepoint that is called by described Automatic Configuration Server ACS to handle,
And described timing savepoint processing RPC has fixed the delay between TR-069 remote management protocol that set up and the follow-up session.
2. method according to claim 1,
It is characterized in that described Automatic Configuration Server ACS calls a plurality of timing savepoints and handles RPC during same affairs TR-069 session,
And each continuous timing savepoint is handled RPC and has been fixed than the regularly savepoint processing shorter delay of delay that RPC fixed formerly in being handled by described a plurality of timing savepoints.
3. method according to claim 1 and 2,
It is characterized in that, when described affairs TR-069 session is not processed during a TR-069 remote management protocol session, described client device CPE will have event code OpenSavePoint during next TR-069 remote management protocol session Inform sends to described Automatic Configuration Server ACS
And described Automatic Configuration Server ACS covers among the InformResponse added field to close described affairs TR-069 session and to handle a described TR-069 remote management protocol session.
4. method according to claim 1 is characterized in that, described savepoint mechanism is by preserving described parameter value on the client device CPE that described parameter value is stored in described DSL telecommunication system.
5. method according to claim 1 is characterized in that, described savepoint mechanism is kept at the historical record of invoked remote procedure call during the described affairs TR-069 session.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP08290727A EP2148470A1 (en) | 2008-07-25 | 2008-07-25 | TR-069 savepoints |
| EP08290727.0 | 2008-07-25 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101635722A CN101635722A (en) | 2010-01-27 |
| CN101635722B true CN101635722B (en) | 2013-09-04 |
Family
ID=40352236
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009101516986A Expired - Fee Related CN101635722B (en) | 2008-07-25 | 2009-07-22 | TR-069 savepoints |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US8127176B2 (en) |
| EP (1) | EP2148470A1 (en) |
| JP (1) | JP5567012B2 (en) |
| KR (1) | KR101529893B1 (en) |
| CN (1) | CN101635722B (en) |
| WO (1) | WO2010009903A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106533803A (en) * | 2016-12-21 | 2017-03-22 | 锐捷网络股份有限公司 | CPE (Customer Premise Equipment) configuration method and device based on TR069 protocol |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012007039A1 (en) * | 2010-07-15 | 2012-01-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for updating a user terminal |
| US10855734B2 (en) * | 2011-06-29 | 2020-12-01 | Interdigital Ce Patent Holdings | Remote management of devices |
| CN102761444B (en) * | 2012-07-26 | 2016-05-11 | 杭州华三通信技术有限公司 | A kind of configuration recovery method of user side equipment and device |
| CN105790983A (en) * | 2014-12-22 | 2016-07-20 | 中兴通讯股份有限公司 | Configuration method, device and system |
| US11477072B2 (en) * | 2019-09-17 | 2022-10-18 | OpenVault, LLC | System and method for prescriptive diagnostics and optimization of client networks |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1203487A (en) * | 1997-06-19 | 1998-12-30 | 新时代通讯股份有限公司 | Wireless communication system and method utilizing wireline switches |
| US6490610B1 (en) * | 1997-05-30 | 2002-12-03 | Oracle Corporation | Automatic failover for clients accessing a resource through a server |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5027269A (en) * | 1989-04-27 | 1991-06-25 | International Business Machines Corporation | Method and apparatus for providing continuous availability of applications in a computer network |
| US6816873B2 (en) * | 2001-05-15 | 2004-11-09 | International Business Machines Corporation | Method for managing distributed savepoints across multiple DBMS's within a distributed transaction |
| US7206826B1 (en) * | 2001-10-25 | 2007-04-17 | Sprint Communications Company L.P. | Configuration recovery after gateway failure |
| US8112394B2 (en) * | 2005-10-14 | 2012-02-07 | Oracle International Corporation | Long-lived data transactions |
-
2008
- 2008-07-25 EP EP08290727A patent/EP2148470A1/en not_active Withdrawn
-
2009
- 2009-07-01 US US12/458,137 patent/US8127176B2/en not_active Expired - Fee Related
- 2009-07-20 KR KR1020117001596A patent/KR101529893B1/en active IP Right Grant
- 2009-07-20 JP JP2011519089A patent/JP5567012B2/en not_active Expired - Fee Related
- 2009-07-20 WO PCT/EP2009/005567 patent/WO2010009903A1/en active Application Filing
- 2009-07-22 CN CN2009101516986A patent/CN101635722B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6490610B1 (en) * | 1997-05-30 | 2002-12-03 | Oracle Corporation | Automatic failover for clients accessing a resource through a server |
| CN1203487A (en) * | 1997-06-19 | 1998-12-30 | 新时代通讯股份有限公司 | Wireless communication system and method utilizing wireline switches |
Non-Patent Citations (1)
| Title |
|---|
| the Broadband Froum.TR-069 CPE WAN Management Protocol v1.1.《TR-069 CPE WAN Management Protocol v1.1》.2007, * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106533803A (en) * | 2016-12-21 | 2017-03-22 | 锐捷网络股份有限公司 | CPE (Customer Premise Equipment) configuration method and device based on TR069 protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| KR101529893B1 (en) | 2015-06-18 |
| US8127176B2 (en) | 2012-02-28 |
| WO2010009903A1 (en) | 2010-01-28 |
| JP5567012B2 (en) | 2014-08-06 |
| CN101635722A (en) | 2010-01-27 |
| JP2011529283A (en) | 2011-12-01 |
| EP2148470A1 (en) | 2010-01-27 |
| US20100023806A1 (en) | 2010-01-28 |
| KR20110042061A (en) | 2011-04-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101635722B (en) | TR-069 savepoints | |
| US8812628B2 (en) | Method and system for remote configuration of a device | |
| US9049253B2 (en) | Resetting / restarting SIP endpoint devices | |
| CN102521099A (en) | Process monitoring method and process monitoring system | |
| CN101202688B (en) | Policy-based management method for remote management of home devices | |
| CN109246057A (en) | Message forwarding method, device, repeater system, storage medium and electronic equipment | |
| CN108984466A (en) | The exchange method of BMC and server OS, system | |
| CN109800571A (en) | Event-handling method and device and storage medium and electronic device | |
| CN107395717A (en) | A kind of method that free time time-out applied to O＆M auditing system disconnects automatically | |
| CN102025728A (en) | Scheduling method under client-side/server-side architecture and server | |
| CN108093005B (en) | Management method and system for interface abnormal call | |
| EP3313039A1 (en) | Home gateway, communication management method and communication system thereof | |
| CN103078865A (en) | Network server communication model based on transmission control protocol (TCP) | |
| CN111865721B (en) | Method, system and storage medium for preventing transaction loss after abnormal node communication | |
| EP1484859B1 (en) | Control method with opaque user identifier administration for complete delivering of a multi-server service | |
| CN101145965A (en) | A method and device for automatic login to telecommunication network management | |
| CN111209171B (en) | Closed loop handling method and device for security risk and storage medium | |
| CN110166528B (en) | Method and device for preventing node change notification from being lost and computer equipment | |
| CN113765780A (en) | Portable operation and maintenance gateway based on Internet of things | |
| US8234487B2 (en) | Server apparatus and startup control method | |
| CN1770759B (en) | Method for holding uniformity of media gateway controller and resource state on media gateway | |
| CN101699785B (en) | Method for taking equipment loading into effect, equipment and remote loading system | |
| CN103166947B (en) | Information processor and information processing method | |
| EP3550931B1 (en) | Use of a user equipment connected to a mobile network, in which the user equipment uses an access point name for home operator services | |
| CN113259404B (en) | Industrial communication middleware based on TCP/IP protocol and use method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130904 Termination date: 20200722 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |