CN103116606A - Data storage structure - Google Patents
Data storage structure Download PDFInfo
- Publication number
- CN103116606A CN103116606A CN2013100178527A CN201310017852A CN103116606A CN 103116606 A CN103116606 A CN 103116606A CN 2013100178527 A CN2013100178527 A CN 2013100178527A CN 201310017852 A CN201310017852 A CN 201310017852A CN 103116606 A CN103116606 A CN 103116606A
- Authority
- CN
- China
- Prior art keywords
- module
- node
- back end
- parameter
- attribute
- 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
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data storage structure. A tree structure composed of a plurality of data nodes is arranged on a storage module of user side equipment based on a TR 098 protocol, a plurality of modules such as a name module, a attribute module, a writing module, a restart module, a return example sequence number module, a return parameter value module and a subordinate data node module are arranged on each data node, wherein each module marks uniquely one data node regulated in the TR 098 protocol, thus a robust and effective data base is established, and so that operations such as establishment and inquire of a parameter node through the TR 098 protocol are facilitated.
Description
Technical field
The present invention relates to a kind of storage organization, relate in particular to a kind of data store organisation.
Background technology
In domestic network system, of a great variety due to user side equipment (such as gateway, set-top box etc.), and dispose and disperse, cause above-mentioned user side equipment in installation, operating business configuration change of later stage and/or break down in the time of to safeguard, all needing by management interface, equipment to be configured or to diagnose.
The user side equipment of present stage all can be provided at administration configuration interface and the interface of LAN side, therefore traditional way be the maintainer of operator visit install or commissioning device after, do the work of some equipment configurations or fault diagnosis by LAN side management interface, the obvious operational efficiency of this man-to-man manual service mode is not high and need to spend a large amount of manpowers.
At present, along with carrying out of operator's family network service, need to be placed in user family having a large amount of equipment, will cause a large amount of human costs if adopt the past manual type to carry out maintenance and management to these equipment, and the appearance of TR-069 be just in order to solve such difficult problem.
TR-069 is one of technical manual of being developed by DSL forum (www.dslforum.org), its full name is " CPE wide area network management agreement ", it provides general framework and the agreement that home network device in next generation network is managed configuration, is used for from network side, the equipment such as the gateway of home network, router, set-top box being carried out the remote centralized management.
In the defined framework of TR-069, mainly comprise two types of logical devices: managed subscriber equipment (CPE) and management server (ACS), namely at family's net environment, the equipment that need to be configured and manage from network side, general is all the equipment directly related with Operator Specific Service, such as home gateway, set-top box, IP phone terminal etc., and the work such as all configurations relevant to subscriber equipment, diagnosis, upgrading are completed by unified management server ACS.
For subscriber equipment, TR-069 mainly completes following operational motion:
(1) subscriber equipment configuration and dynamic business configuration automatically.For ACS, each subscriber equipment can be to oneself making sign (such as model, version etc.) in agreement, according to the rule that can set, ACS can issue configuration to some special user equipments, also can issue configuration to a certain group of subscriber equipment, be the configuration information that CPE can be in start be asked ACS afterwards automatically, ACS also can initiatively initiate configuration in the moment that needs arbitrarily; Can realize " zero configuration installation " function of subscriber equipment by above-mentioned action of configuration, also can realize the dynamic change from the network controls service parameter.
(2) to the software of subscriber equipment, the management of firmware.The agreement of TR-069 provides the function that the software in subscriber equipment, firmware are managed and download, it is the version number that ACS can identify subscriber equipment, whether determine the software version of remote update subscriber equipment, and can learn whether success after renewal is completed; For example: when subscriber equipment need to load new software when realizing new business function, or current software is when existing the bug that must repair, and can realize upgrading to the telemanagement of subscriber equipment by above-mentioned function.
(3) state and the performance of subscriber equipment are monitored.The agreement of TR-069 has also defined the means that ACS monitors state and the performance of subscriber equipment, as by detecting some general performance parameters, can reflect the duty of current user equipment; In addition, the agreement of TR-069 also provides the grammer of standard, and operator can pass through the extra parameter of this syntactic definition.
(4) to the diagnosis of communication failure.The agreement of TR-069 has also defined the ability of user side autodiagnosis and report, for example under the indication of ACS, the operations such as connectedness between providing a little of user side and Network, bandwidth can be provided by ping or other means user side, and testing result is returned to ACS, be that operator passes through at far-end operation, just can simply locate the equipment failure of subscriber complaint, and be correspondingly processed.
Owing to will completing above-mentioned all operations and function, all need to be based on the database in terminal device, i.e. stalwartness, database efficiently have very important impact for the agreement of TR-069 to operational motions such as the establishment of parameter node, inquiries.
Chinese patent (application number: 200510097937.6) disclose a kind of date storage method, by first back end is set in the first memory block, second back end has been set in the second memory block; Consist of an element in a plurality of elements of first a flat table at least one flat table in the second memory block during described the second back end, and the step that the first back end is set is included in link two tuples of storage in this node; And then realize realizing data link in not supporting the specific purpose processor of memory address pointer, thereby reduce the requirement to poke data requisite space.
Chinese patent (application number: a kind of method that 201110025142.X) discloses constructing tree structural directory in database, by set up the general bibliographic structure module that is used for describing tree structure in database, configuration module with the associated information of node in this general description tree structure, with when building tree structure, first deposit the associated information of tree structure that to set up in described bibliographic structure module and configuration module, and in conjunction with the information of depositing in bibliographic structure module and configuration module, build a tree-structured directory that comprises specifying information, and then realization reduces redundant datas a large amount of in data space, make brother's information table can conveniently adapt to various taxonomic structures, to improve the utilization factor of the storage spaces such as hard disk and/or buffer memory, strengthen Systems balanth.
Although disclose the relevant information of how to carry out the data storage and setting up tree form data structure in above-mentioned document, but all less than an open relevant stalwartness, the tree data storehouse efficiently of how building, and based on the relevant information of the agreement related data structures of TR-069.
Summary of the invention
For the problem of above-mentioned existence, the invention provides a kind of data store organisation, be applied on the memory module in TR-069 agreement user side equipment, wherein,
Be provided with a plurality of back end on described memory module;
Each described back end is top layer back end or middle layer back end or bottom data node;
The described bottom data node of part is connected with described top layer back end by described middle layer back end, and all the other described bottom data nodes directly are connected with described top layer back end, jointly consist of a tree structure.
Above-mentioned data store organisation, wherein, described back end comprises a plurality of Object nodes, a plurality of parameter node and Multi-instance node, each described Object node is root object node or medium object node;
Described top layer back end is the root object node;
Each described bottom data node is the parameter node;
Each described middle layer back end is example node or medium object node.
Above-mentioned data store organisation, wherein, each described back end includes title module, attribute module, writing module, restarts module, returns to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module;
Described title module comprises this data section point of general and parameter values scope;
According to described data section point of general described parameter values scope, attribute module, writing module be set, restart module, return to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module.
Above-mentioned data store organisation, wherein, described title module also comprises the title of this back end;
Described data section point of general is Object node or example node or parameter node;
When described data section point of general was Object node or example node, the value of described parameter values scope was empty.
Above-mentioned data store organisation wherein, when described data section point of general is Object node or example node, described writing module, is restarted module, return parameters value module and described return parameters value module and all is set to sky;
When described data section point of general was the parameter node, the described instance number module of returning was set to sky.
Above-mentioned data store organisation, wherein, when described data section point of general was the parameter node, described return parameters value module was returned to the value of this parameter node according to the title of the parameter node of appointment, and when makeing mistakes, returns to error code.
Above-mentioned data store organisation, wherein, when described data section point of general is the parameter node, described return parameters settings module finds this parameter node according to the title of setup parameter node, the value of value for setting of this parameter node is set, and when makeing mistakes, returns to error code.
Above-mentioned data store organisation, wherein,
Described writing module is the read-write properties of this back end, and described to restart module be that described user side equipment is restarted attribute;
When described data section point of general was the parameter node, described writing module represented whether this back end can be write, and describedly restarted after module represents to revise this back end, and whether described user side equipment restarts.
Above-mentioned data store organisation, wherein, a long-distance management system is connected with described user side equipment;
Described attribute module comprises parameter attribute module and object properties module;
Described parameter attribute module comprises notification type and rewriting attribute, and described object properties module comprises access attribute and the embodiment of subordinate number;
When described data section point of general is Object node or example node, described parameter attribute module is set to sky, described access attribute represents the access rights of this back end, the described embodiment of subordinate number represents the number of the embodiment node that connects under this back end, and describedly returns to the value that the instance number module is returned to the number of this embodiment node;
When described data section point of general was the parameter node, described object properties module was set to sky, and described notification type represents whether the value of this back end notifies described long-distance management system, the rewriting authority of described this back end of rewriting attribute representation after changing;
Wherein, described notification type comprises and does not notify described long-distance management system, the described long-distance management system of proactive notification and passively notify described long-distance management system three types.
Above-mentioned data store organisation, wherein, described subordinate back end module comprises subordinate's back end information;
When this back end was the low layer back end, described subordinate back end information was set to sky.
Compared with the prior art, beneficial effect of the present invention is:
by on based on the memory module of the user side equipment of TR098 agreement, the tree structure body that is made of a plurality of back end being set, and each back end is all arranged the title module, attribute module, writing module, restart module, return to example sequence number module, return parameters value module, a plurality of modules such as return parameters settings module and subordinate's back end module, and each above-mentioned module is unique back end of stipulating in the TR098 agreement that indicates all, and then set up a stalwartness, efficient database, so that the agreement of TR-069 is to the establishment of parameter node, the operations such as inquiry.
Description of drawings
Fig. 1 is the tree structure schematic diagram of data store organisation in the embodiment of the present invention;
Fig. 2 is the modular structure schematic diagram of back end in the embodiment of the present invention;
Fig. 3 is the structure schematic diagram of back end in the embodiment of the present invention.
Embodiment
The invention will be further described below in conjunction with schematic diagram and concrete operations embodiment.
A kind of data store organisation of the present invention, be mainly used on the storage mediums such as the memory module of user side equipment in the TR-069 agreement such as hard disk, mainly by in this memory module, a plurality of back end being set, and each above-mentioned back end is top layer back end or middle layer back end or bottom data node.
Wherein, part bottom data node is connected with the top layer back end by the middle layer back end, and remaining bottom data node directly is connected with the top layer back end, with common formation one tree structure.
Preferably, above-mentioned a plurality of back end comprise a plurality of Object nodes, a plurality of parameter node and Multi-instance node, and each Object node is root object node or medium object node, be that the top layer back end is the root object node, the bottom data node is the parameter node, and the middle layer back end is example node or medium object node.
Each above-mentioned back end includes title module, attribute module, writing module, restarts module, returns to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module; The title module comprises this data section point of general and parameter values scope, and according to this data section point of general parameters numerical range, attribute module, writing module, restart module, return to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module.
Wherein, a long-distance management system is connected with user side equipment, and attribute module comprises parameter attribute module and object properties module; The parameter attribute module comprises notification type and rewriting attribute, and the object properties module comprises access attribute and the embodiment of subordinate number.
Preferably, the data section point of general is Object node or example node or parameter node, and the title module also comprises the title of this back end, and writing module is the read-write properties of this back end, and restarting module is that user side equipment is restarted attribute.
When the data section point of general is Object node or example node, the value of parameter values scope is empty, and above-mentioned writing module, restart module, return parameters value module and return parameters value module and the parameter attribute module all is set to sky, access attribute represents the access rights of this back end, subordinate's embodiment number represents the number of the embodiment node that connects under this back end, and returns to the value that the instance number module is returned to the number of this embodiment node.
When the data section point of general was the parameter node, return parameters value module was returned to the value of this parameter node according to the title of the parameter node of appointment, and when makeing mistakes, returns to error code; Return parameters settings module finds this parameter node according to the title of setup parameter node, the value of value for setting of this parameter node is set, and when makeing mistakes, returns to error code; Writing module represents whether this back end can be write; Restart after module represents to revise this back end, whether user side equipment restarts; The object properties module is set to sky, and notification type represents whether the value of this back end notifies long-distance management system after changing, rewrites the rewriting authority of this back end of attribute representation.
Wherein, notification type comprises and does not notify long-distance management system, proactive notification long-distance management system and passive notice long-distance management system.
Preferably, subordinate's back end module comprises subordinate's back end information, and when this back end was the low layer back end, the information of subordinate's back end was set to sky.
Fig. 1 is the tree structure schematic diagram of data store organisation in the embodiment of the present invention, as shown in Figure 1, a kind of data store organisation of the present invention comprises the root object node, Object node X, Object node Y, example node 1, example node 2, parameter node A, the parameter Node B, parameter node C, parameter node D, parameter node E, a plurality of back end such as parameter node F and parameter node G, and these a plurality of back end connect and compose a tree structure successively, be the root object node respectively with parameter node A, Object node X and Object node Y, Object node X also is connected with the example node with example node 1 respectively and is connected, example node 1 also is connected with parameter node C with the parameter Node B respectively, example node 2 also is connected with parameter node E with parameter node D respectively, and Object node Y also is connected with parameter node G with parameter node F respectively, to consist of a tree structure.
Wherein, the root object node is the top layer back end, Object node X, Object node Y, example node 1 and example node 2 are the middle layer back end, and parameter node A, parameter Node B, parameter node C, parameter node D, parameter node E, parameter node F and parameter node G are the bottom data node.
Fig. 2 is the modular structure schematic diagram of back end in the embodiment of the present invention, as shown in Figure 2, each above-mentioned back end (root object node, Object node X, Object node Y, example node 1, example node 2, parameter node A, parameter Node B, parameter node C, parameter node D, parameter node E, parameter node F or parameter node G) include title module, attribute module, writing module, restart module, return to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module; The title module comprises this data section point of general and parameter values scope, and according to this data section point of general parameters numerical range, attribute module, writing module, restart module, return to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module.
Fig. 3 is the structure schematic diagram of back end in the embodiment of the present invention, as shown in Figure 3, each above-mentioned back end is the Cpe_Para_t structure, and the equal unique back end (as parameter node, example node and/or Object node etc.) stipulated in the agreements such as TR098 of representing accurately of each thresholding in this Cpe_Para_t structure.
Wherein, thresholding Para_Sub_tps(title module) be the Para_Sub_t structure, and this thresholding comprises the CHAR*name(title of this back end), the CHAR*type(type), the INT32low(parameter value), the maximal value of DWORD hihg(parameter) and DWORD len(string length); The type of above-mentioned back end is boolean, string, unsignedInt or dateTime etc., when if this data section point of general is the boolean type, the maximal value of parameter value is 1, if this data section point of general is string, parameter value is the maximum length of its character string, if this data section point of general is unsignedInt, parameter value is the maximal value of signless integer.
Thresholding Para_Adm_t*padm(attribute module) be the Para_Adm_t structure, and this thresholding comprises Para_Adm_t pa structure (parameter attribute module) and Cpe_MObjAttr_t ma structure (object properties module).
Above-mentioned Para_Adm_t pa structure comprises BYTE nc (notification type) and the DWORD acl (rewriting attribute) of this back end; When the value of the nc in BYTE nc was 0, when expression was changed when the value of this back end (parameter node), CPE did not notify long-distance management system; When the value of nc is 1, when expression is changed when the value of this back end (parameter node), the passive notice long-distance management system of CPE (incidentally the Varying parameters of this data section point value being circulated a notice of to long-distance management system at the inform message); When if the value of nc is 2, represent when the value of this back end (parameter node) changes CPE proactive notification long-distance management system (long-distance management system of notice immediately of the variation of this data section point value); Wherein, DWORD acl(rewrites attribute) in the position bit of acl represent that this back end (parameter node) can only be rewritten by whom, as arrange can only could rewrite this back end by long-distance management system value accordingly the bit of acl be 1.
Above-mentioned Cpe_MObjAttr_t ma structure is used for the attribute of expression multi-instance object, specifically comprise BOOL accessable(access attribute) and BYTE max_ins (embodiment of subordinate number), above-mentioned accessable represents whether this back end (Object node or example node) can access, and max_ins represents that this back end has the number of total what examples.
In addition, thresholding BOOT writale(writing module) represent whether this back end (parameter node) can be write, if writale is that 1 this back end of expression is read-write, if writale is that 0 this back end of expression is only readable; Thresholding BOOT reboot(is restarted module) represent whether this back end (parameter node) wants restarting equipment (user side equipment such as router etc.) after accessed; Thresholding INT16 (* r2i) (int index) (returning to the instance number module) is a function pointer, and this function pointer returns to the maximum instance number of this back end (Object node or example node), as this back end have two example nodes this function pointer return to numerical value 2.
Thresholding CHAR* (* r2t) (Cpe_Arg_t*, Cpe_Error_t*) (return parameters value module) is also a function pointer, this function pointer returns to the value of this parameter node under this parameter name according to the parameter name of appointment, and when mistake occurring, returns to error code; Thresholding INT16 (* t2r) (Cpe_Arg_t*, Cpe_Error_t*) (return parameters settings module) is also a function pointer, this function pointer is followed the parameter node that finds appointment according to parameter name and value, and the value of this parameter node is set to corresponding value, and when mistake occurring, return to error code; Thresholding struct cpe_t*child(subordinate back end module) next stage that points to this back end is the Cpe_Para_t structure, so that all back end are consisted of a tree as shown in Figure 1.
A kind of data store organisation of the present embodiment, mainly to come the defined parameters tree with the array of Cpe_Para_t structure, and all properties of a parameter node is set in the Cpe_Para_t structure, for example: parameter or the pathname of revising the parameter node, whether this back end can be write is whether its value can arrange by ACS, whether report ACS when the value of back end due to what non-TR069 agreement changed, and the mode that reports is active reporting or passive report etc.; in addition, also be provided with the interface of several call back functions, INT16 described above (* r2i) (int index) call back function is mainly used in reading several examples under this back end, and CHAR* (* r2t) (Cpe_Arg_t*, Cpe_Error_t*) call back function is used for reading the value of this back end (parameter node) or is used for adding a parameter node instance, above-mentioned INT16 (* t2r) (Cpe_Arg_t*, Cpe_Error_t*) call back function is mainly used in arranging the value of this back end or is used for the example of a parameter node of deletion.
Below just search function as example take parameter, be described in detail:
This function prototype is:
Cpe_Para_t*cpe_locateParameter(CHAR*name,
Cpe_Para_t*parentCp,
Para_Type_e*type,
Cpe_Arg_t*carg)
Wherein, name is the title (or pathname) of the parameter node searched; Function input parameter, parentCp represent that superior node or the NULL(of the parameter node searched represent to begin to search from root node); Function input parameter, type represent the type (PARA_TYPE_NORMAL or PARA_TYPE_OBJECT) of parameter node; Function output parameter, carg are the function output parameter; Function returns to a pointer that points to the parameter node, by can complete any operation to the parameter node database to the operation of Cpe_Para_t structure.
in sum, a kind of data store organisation of the present invention, by on based on the memory module of the user side equipment of TR098 agreement, the tree structure body that is made of a plurality of back end being set, and each back end is all arranged the title module, attribute module, writing module, restart module, return to example sequence number module, return parameters value module, a plurality of modules such as return parameters settings module and subordinate's back end module, and each above-mentioned module is unique back end of stipulating in the TR098 agreement that indicates all, and then set up a stalwartness, efficient database, so that the agreement of TR-069 is to the establishment of parameter node, the operations such as inquiry.
Above specific embodiments of the invention are described in detail, but the present invention is not restricted to specific embodiment described above, it is just as example.To those skilled in the art, any equivalent modifications and alternative also all among category of the present invention.Therefore, not breaking away from impartial conversion and the modification of having done under the spirit and scope of the present invention, all should contain within the scope of the invention.
Claims (10)
1. a data store organisation, be applied to it is characterized in that on the memory module in TR-069 agreement user side equipment,
Be provided with a plurality of back end on described memory module;
Each described back end is top layer back end or middle layer back end or bottom data node;
The described bottom data node of part is connected with described top layer back end by described middle layer back end, and all the other described bottom data nodes directly are connected with described top layer back end, jointly consist of a tree structure.
2. data store organisation according to claim 1, is characterized in that, described back end comprises a plurality of Object nodes, a plurality of parameter node and Multi-instance node, and each described Object node is root object node or medium object node;
Described top layer back end is the root object node;
Each described bottom data node is the parameter node;
Each described middle layer back end is example node or medium object node.
3. data store organisation according to claim 2, it is characterized in that, each described back end includes title module, attribute module, writing module, restarts module, returns to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module;
Described title module comprises this data section point of general and parameter values scope;
According to described data section point of general described parameter values scope, attribute module, writing module be set, restart module, return to example sequence number module, return parameters value module, return parameters settings module and subordinate's back end module.
4. data store organisation according to claim 3, is characterized in that, described title module also comprises the title of this back end;
Described data section point of general is Object node or example node or parameter node;
When described data section point of general was Object node or example node, the value of described parameter values scope was empty.
5. data store organisation according to claim 4, is characterized in that, when described data section point of general is Object node or example node, described writing module, restarts module, return parameters value module and described return parameters value module and all be set to sky;
When described data section point of general was the parameter node, the described instance number module of returning was set to sky.
6. data store organisation according to claim 5, it is characterized in that, when described data section point of general was the parameter node, described return parameters value module was returned to the value of this parameter node according to the title of the parameter node of appointment, and when makeing mistakes, return to error code.
7. data store organisation according to claim 5, it is characterized in that, when described data section point of general is the parameter node, described return parameters settings module finds this parameter node according to the title of setup parameter node, the value of value for setting of this parameter node is set, and when makeing mistakes, return to error code.
8. data store organisation according to claim 5, is characterized in that,
Described writing module is the read-write properties of this back end, and described to restart module be that described user side equipment is restarted attribute;
When described data section point of general was the parameter node, described writing module represented whether this back end can be write, and describedly restarted after module represents to revise this back end, and whether described user side equipment restarts.
9. data store organisation according to claim 5, is characterized in that, a long-distance management system is connected with described user side equipment;
Described attribute module comprises parameter attribute module and object properties module;
Described parameter attribute module comprises notification type and rewriting attribute, and described object properties module comprises access attribute and the embodiment of subordinate number;
When described data section point of general is Object node or example node, described parameter attribute module is set to sky, described access attribute represents the access rights of this back end, the described embodiment of subordinate number represents the number of the embodiment node that connects under this back end, and describedly returns to the value that the instance number module is returned to the number of this embodiment node;
When described data section point of general was the parameter node, described object properties module was set to sky, and described notification type represents whether the value of this back end notifies described long-distance management system, the rewriting authority of described this back end of rewriting attribute representation after changing;
Wherein, described notification type comprises and does not notify described long-distance management system, the described long-distance management system of proactive notification and passively notify described long-distance management system three types.
10. data store organisation according to claim 3, is characterized in that, described subordinate back end module comprises subordinate's back end information;
When this back end was the low layer back end, described subordinate back end information was set to sky.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013100178527A CN103116606A (en) | 2013-01-17 | 2013-01-17 | Data storage structure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013100178527A CN103116606A (en) | 2013-01-17 | 2013-01-17 | Data storage structure |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103116606A true CN103116606A (en) | 2013-05-22 |
Family
ID=48414980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2013100178527A Pending CN103116606A (en) | 2013-01-17 | 2013-01-17 | Data storage structure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103116606A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103916404A (en) * | 2014-04-23 | 2014-07-09 | 北京淦蓝润和信息技术有限公司 | Data management method and system |
| CN104158692A (en) * | 2014-08-25 | 2014-11-19 | 烽火通信科技股份有限公司 | Method of implementing configuration and management of data of home gateway based on XML (Extensible Markup Language) |
| CN108650551A (en) * | 2014-09-26 | 2018-10-12 | 青岛海信宽带多媒体技术有限公司 | A kind of parameter operation method of set-top box |
| CN110084564A (en) * | 2019-04-24 | 2019-08-02 | 李振 | ICE framework for item data management |
| CN112579570A (en) * | 2020-12-16 | 2021-03-30 | 中国辐射防护研究院 | Nuclear environment data storage method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101127630A (en) * | 2006-08-15 | 2008-02-20 | 华为技术有限公司 | Method, device and system for managing object instant |
| CN101753564A (en) * | 2008-12-02 | 2010-06-23 | 阿尔卡特朗讯公司 | A module and associated method for TR-069 object management |
| EP2216937A1 (en) * | 2009-02-10 | 2010-08-11 | Alcatel Lucent | Alarm notification between customer premises equipment and a remote management server |
-
2013
- 2013-01-17 CN CN2013100178527A patent/CN103116606A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101127630A (en) * | 2006-08-15 | 2008-02-20 | 华为技术有限公司 | Method, device and system for managing object instant |
| CN101753564A (en) * | 2008-12-02 | 2010-06-23 | 阿尔卡特朗讯公司 | A module and associated method for TR-069 object management |
| EP2216937A1 (en) * | 2009-02-10 | 2010-08-11 | Alcatel Lucent | Alarm notification between customer premises equipment and a remote management server |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103916404A (en) * | 2014-04-23 | 2014-07-09 | 北京淦蓝润和信息技术有限公司 | Data management method and system |
| CN104158692A (en) * | 2014-08-25 | 2014-11-19 | 烽火通信科技股份有限公司 | Method of implementing configuration and management of data of home gateway based on XML (Extensible Markup Language) |
| CN104158692B (en) * | 2014-08-25 | 2018-04-17 | 烽火通信科技股份有限公司 | The method that home gateway data configuration management is realized based on XML |
| CN108650551A (en) * | 2014-09-26 | 2018-10-12 | 青岛海信宽带多媒体技术有限公司 | A kind of parameter operation method of set-top box |
| CN110084564A (en) * | 2019-04-24 | 2019-08-02 | 李振 | ICE framework for item data management |
| CN110084564B (en) * | 2019-04-24 | 2021-07-02 | 李振 | ICE architecture for project data management |
| CN112579570A (en) * | 2020-12-16 | 2021-03-30 | 中国辐射防护研究院 | Nuclear environment data storage method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103281197B (en) | A kind of ForCES collocation method based on NETCONF | |
| CN100484039C (en) | Network management apparatus and network management method | |
| CN103116606A (en) | Data storage structure | |
| CN108234307A (en) | Network method, network equipment and non-transitory computer-readable storage media | |
| CN108199897A (en) | A kind of OPC UA multiserver polymerizations for supporting cache management | |
| CN105634829B (en) | A kind of network device management method | |
| CN101540700A (en) | Configuration linkage method, system, terminal and network equipment management server | |
| US7730091B2 (en) | Systems, methods and computer products for database cluster modeling | |
| CN101009591A (en) | Method and system for configuring network devices through an operations support system interface | |
| CN102567932A (en) | Method, device and system for managing comprehensive resources | |
| CN102013998B (en) | Tr-069 protocol-based management method for realizing home network | |
| Hong et al. | Netgraph: An intelligent operated digital twin platform for data center networks | |
| Mogul et al. | Experiences with modeling network topologies at multiple levels of abstraction | |
| CN101776996A (en) | Construction implementation method of object-based configuration management system in communication system | |
| CN107179977B (en) | Database Full-automatic monitoring system based on mpm models | |
| CN108848132A (en) | A kind of distribution scheduling station system based on cloud | |
| CN103036934A (en) | Wide area network clustered deployment system and method based on mirror image | |
| US20070124455A1 (en) | Method and apparatus for providing multiple vendor support to remotely monitored devices | |
| CN103685572A (en) | Method and system for building data center management platform based on SOA (service-oriented architecture) | |
| CN101771557A (en) | Method for managing object instance and alias and equipment | |
| KR100995198B1 (en) | Network management system capable of editing and managing objects graphically, and supporting various network appratuses | |
| CN100401684C (en) | Method for implementing network management layer to information managing by element management layer | |
| CN100558178C (en) | Data-erasure method and terminal | |
| CN101820354B (en) | Collocation method based on TNDS (Total Network Data System) object, terminal equipment and server | |
| CN102006178A (en) | SNMP-based network management method and 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130522 |