CN100471136C - Configuration rule detecting method and device - Google Patents
Configuration rule detecting method and device Download PDFInfo
- Publication number
- CN100471136C CN100471136C CNB2007100801071A CN200710080107A CN100471136C CN 100471136 C CN100471136 C CN 100471136C CN B2007100801071 A CNB2007100801071 A CN B2007100801071A CN 200710080107 A CN200710080107 A CN 200710080107A CN 100471136 C CN100471136 C CN 100471136C
- Authority
- CN
- China
- Prior art keywords
- constraint
- dependent
- relation
- configuration
- inspection
- 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
Abstract
The invention discloses one set rules testing method, which comprises the following steps: dividing the combination relationship into three kinds as subject self inner constraint, different kind of subject relation constraint and same subject relation constraint; in subject generation of set, executing constant test on inner constraint; when the dependent at least subject generates change, one part of dependent ones executes subject constant test. The invention also discloses one set rules test device.
Description
Technical field
The present invention relates to the network device management technology, particularly a kind of configuration rule detecting method and device.
Background technology
When using various network device to provide various network services, need be configured the network equipment as the user.Usually, the network manager is ready to configuration data in network element management device (EM, Element Manager) side, and is issued to network device unit (NE, Network Element are called for short network element) by the mode of batch configuration or in the mode that data are recovered.Network element must be checked the validity and the consistency of configuration data before the configuration of updating the equipment according to these configuration datas, in case the network element management device side is because management or factor such as realization issue illegal data, the normal operation of network element is brought dangerous influence.The rule of configuration data being carried out validity and consistency check is called configuration rule, and correspondingly, the inspection that the validity and the consistency of configuration data are carried out is called the configuration rule inspection.There are two kinds in the prior art and are configured the method that rule is checked, introduced respectively below.
First method: use object constraint language (OCL, Object Constraint Language) to describe configuration rule.This method at first needs configuration data is carried out the objectification modeling, and on the basis of object model the invariant of precondition, postcondition and the object of description object configuration operation; Develop the OCL translater then, it is translated into object codes such as JAVA, SQL or C++, the code after will translating at last is with the code compilation run of goal systems.
Consider that from aspect of performance there is following shortcoming in this configuration rule detecting method:
1, because OCL language itself has only provided a kind of complete grammer that is used to describe constraint based on invariant, do not consider the efficiency that rule is checked, the efficient that makes configuration rule check is very low.For example, have a National People's Congress among the expression employee as follows at least in 50 years old invariant:
inv:selt.employee->select(p|p.age>50)->notEmpty()
Being translated into false code will be following form:
Each member p in my employee's set of For
If (p.age〉50) then puts into interim S set with p
End for；
S.size()>0；
On the one hand, the performance of above-mentioned translation is obviously not as following form:
Each member p in my employee's set of For
if(p.age>50)then return OK；
End for；
And the adjustment optimization of this intelligence is difficult in realization automatically in the translation process; On the other hand, the object invariant is the rule that the whole life of object all must satisfy, because OCL itself does not consider the execution opportunity that the object invariant is checked, so, if above-mentioned rule is not optimized, then all will trigger the inspection of this invariant to any modification of object model, its performance loss will be very huge.
2, this method requires OCL is translated into object code and integrated with destination software systems.Mapping and transformational relation between this translation process requirements definition object code and the OCL data type, definition can be corresponding with the OCL syntactic element the object data access interface, this will increase the indirect of data visit and conversion requirement, cause the reduction of configuration rule checking efficiency.
Second method: the invariant that configuration rule is divided into precondition, postcondition and the object of object configuration operation according to the thought of OCL, and use common programming language, for example C, C++ or JAVA language development are compiled into a dynamic link library (DLL) with these regular codes of checking then.Rule checks the visit of data is undertaken by standardized interface in advance that the realization of this interface is checked that by rule the user of DLL registers when initialization DLL.
Though this method has used C, C++ or JAVA language to realize that this method also is based on the thought of OCL, does not propose effective solution with regard to the efficient that how to improve the configuration rule inspection.
As seen from the above analysis, the efficient of existing configuration rule detecting method is lower.
Summary of the invention
In view of this, in the disclosed configuration rule detecting method of the embodiment of the invention, provide a kind of method that improves the configuration rule checking efficiency.
In the disclosed configuration rule testing fixture of the embodiment of the invention, provide a kind of device that improves the configuration rule checking efficiency.
For achieving the above object, the technical scheme of the embodiment of the invention specifically is achieved in that
A kind of configuration rule detecting method, the rule of described configuration rule for configuration data is carried out validity and consistency check, this method is divided into three kinds with the restriction relation between the managed object in the network element system: relation constraint between the internal constraint of object self, inhomogeneity object and the relation constraint between homogeneous object;
When object generation configuration change, the internal constraint of described object self is carried out the invariant inspection;
By at least one object instance generation configuration change of dependent the time, the relation constraint between described inhomogeneity object is carried out the invariant inspection by the dependent or by the side among the dependent.
A kind of configuration rule testing fixture, the rule of described configuration rule for configuration data is carried out validity and consistency check, described configuration rule testing fixture is used for the object of processing net element system, and this device comprises: internal constraint is checked the relation constraint inspection module between module and inhomogeneity object;
Described internal constraint is checked module, is used for when the object generation configuration change of network element system, and the internal constraint of object self is carried out the invariant inspection;
Relation constraint between described inhomogeneity object is checked module, is used for by at least one object instance generation configuration change of dependent the time, and the relation constraint between the inhomogeneity object is carried out the invariant inspection.
As seen from the above technical solution, the embodiment of the invention is by classifying to restriction relation, and by definition configuration dependence, make after each configuration change, the configuration rule inspection only is confined to exist on the object relationship that disposes dependence, has avoided the traversal inspection to all objects in the model.And, realize the execution ownership that the configuration dependence is checked by agreement, avoided existing two same dependences of object rechecking of dependence, improved the efficient that configuration rule is checked.
Description of drawings
Fig. 1 is the configuration dependence model schematic diagram between the object in the embodiment of the invention.
Fig. 2 carries out the execution schematic flow sheet that invariant is checked for the configuration change operation to object A in the embodiment of the invention.
Fig. 3 carries out the execution schematic flow sheet that invariant is checked for the configuration change operation to object B in the embodiment of the invention.
Fig. 4 is the composition structural representation of configuration rule testing fixture in the embodiment of the invention.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further detail.
The present invention is primarily aimed at existing configuration rule based on invariant and checks scheme, proposes to improve the configuration rule detecting method of configuration rule checking efficiency.
According to the definition of OCL, the object invariant is meant: to all essential at any time constraint of satisfying of similar all object instances, also can be understood as the rule that object all must satisfy in whole life.
If do not consider checking efficiency, follow the notion of object invariant, a kind of mode of simple general-purpose is finished after any configuration operation exactly, all the invariant inspection of all configuration objects in the network element is carried out one time, is expressed as form with pseudo-code:
For (each object in allocation models)
{
The execution invariant is checked;
The failure of if (checking failure) return configuration operation;
}
The success of return configuration operation;
If the number of objects that the hypothesis network element has been created is 10000, the invariant of each object has 5, (all deposit data of suppose object model are in database for the inspection time of implementation average out to 0.1ms of every invariant, and the memory database that serviceability is the highest, be that index and data are all in internal memory, do not need access hard disk, 0.1ms for from 10000 records, finding the time of a record that mates with querying condition), the operation of each modification object model only need consume 5s for the executing rule inspection so.And owing to the mass data renewal of network element generally can influence or interrupting service, the user has higher performance requirement to this process, for example in base station system, require the network element per second can carry out configuration operation more than 30 (the wall scroll configuration operation is that the additions and deletions to a configuration object change operation), in the aforesaid way, each revises the operation of object model only for the executing rule inspection just needs to consume 5s, does not reach the performance requirement that per second is carried out operation more than 30 far away.
The configuration rule inspection is exactly to check the configuration change of user to configuration object, guarantees that the configuration change of being done meets the restriction relation between the types of objects.In order to improve the efficient that configuration rule is checked, and guarantee that the configuration rule inspection can cover all restriction relations comprehensively, the present invention is on the basis of analyzing managed object (MO) allocation models, with the restriction relation between the MO, be that invariant has been divided into three classes, and taked different invariant test modes according to the different characteristics of this three classes restriction relation.Three class restriction relations are defined as follows:
1, the internal constraint of object self: this restriction relation is the internal constraint relation of certain object instance self.For example, the restriction relation between the different attribute etc. in the span of object properties, object.
2, the relation constraint between the inhomogeneity object: this restriction relation is the interconnection constraint relation that exists between the different object that disposes dependence.For example, the object A attribute that depends on object B must satisfy some condition, object A depends on number restriction of object B etc.
3, the relation constraint between homogeneous object: this restriction relation is the restriction relation between same type, the different object instance.For example.Certain attribute of the maximum example number of object of the same type, object of the same type is necessary unique etc.
For the internal constraint of above-mentioned object self, when object generation configuration change, carry out the invariant inspection of object self.Because the invariant inspection of object self only relates to the constraint inspection of object self attributes, other data (promptly not needing accessing database) that do not need the access object allocation models, execution efficient is higher, therefore, to optimize the execution obtained optimization effect on opportunity of this class restriction relation be conspicuous to technical solution of the present invention.Here, configuration change is meant the operation that object is increased, deletes or revises.
For the relation constraint between above-mentioned inhomogeneity object, by at least one object instance generation configuration change of dependent the time, the relation constraint between described inhomogeneity object is carried out the invariant inspection by the dependent or by the side among the dependent.
Fig. 1 is the configuration dependence model schematic diagram between the object in the embodiment of the invention.Referring to Fig. 1, A, B, C represent three class MO, and the unidirectional arrow among the figure represents to dispose dependence.The semanteme of configuration dependence is: if A configuration depends on B, then explanation is when the one or more object instance generation configuration change of B, and the configuration constraint that may destroy between A and the B concerns; At this moment, except the internal constraint invariant of B being carried out object self is checked, also must check, could guarantee the consistency of whole allocation models like this relation constraint between the inhomogeneity object of A and B.
In order to realize that the relation constraint between inhomogeneity object shown in Figure 1 is carried out high efficiency configuration rule inspection, the present invention's agreement: when existing a configuration to rely between two objects, this configuration dependence is carried out the invariant inspection by the dependent or by the side in relying on.This pact is effectively avoided the dependent surely and is all carried out the inspection of repetition by dependent both sides.
Simultaneously, for simplicity, the present invention specifies a name for each configuration dependence, is decided to be approximately＜source〉＜target 〉.For example, B depends on the configuration dependence of A, is expressed as the arrow that B points to A in the drawings, called after ba.Invariant inspection according to its configuration dependence of top agreement can be realized by B, also can be realized by A.
Based on above-mentioned classification to restriction relation, and the definition to the configuration dependence shown in Figure 1, can check that interfaces are to realize the configuration rule inspection for three invariants of each MO shown in being defined as follows:
class MOItf
{
……
Bool inner_invarant (); The internal constraint inspection of // object self
Bool asso_invarant (ASSO_NAME asso); Relation constraint inspection between // inhomogeneity object
Bool class_invarant (); Relation constraint inspection between // homogeneous object
……
}
In the above-mentioned false code, ASSO_NAME represents the incidence relation name, and for example, ab shown in Figure 1, ba and ca are the incidence relation name.
Be that example is to being illustrated the opportunity that the present invention carries out the inspection of object invariant with object model shown in Figure 1 and configuration dependence below.
Fig. 2 carries out the execution schematic flow sheet that invariant is checked for the configuration change operation to object A in the embodiment of the invention.Referring to Fig. 2, ENV represents execution environment, MIB is a management information bank, attribute list is represented the attribute list that configuration change is related, all configuration change operations to MO all show as the operation of ENV to MIB, and these configuration change operations comprise increase (Create), modification (Modify) and deletion (Delete) as shown in the figure.
To being described as follows of execution flow process shown in Figure 2:
The 1st step: ENV issues configuration change at object A to MIB, and these configuration changes may comprise the increase of some attribute of object A, deletion or modification.
The 2nd step: MIB is configured change to object A.
The 3rd step: MIB notify object A carries out the internal constraint inspection of object self.
In this step, can use the internal constraint inspection of interface function inner_invarant () the realization object self in the above-mentioned false code.
The 4th step:, therefore, need the relation constraint inspection between the inhomogeneity object between object A and the object B in this step because the object B configuration depends on object A.As previously mentioned, this inspection can realize by the dependent, also can be by being realized by the dependent, and here, to be embodied as example by the dependent, therefore, MIB notify object B carries out the relation constraint inspection between inhomogeneity object between object A and the object B.
In this step, can use the internal constraint inspection of interface function asso_invarant () the realization object self in the above-mentioned false code, parameter is ba.
The 5th goes on foot: this step is similar with the 4th step, because object C configuration depends on object A, therefore, the relation constraint inspection between the inhomogeneity object between MIB notify object C execution object A and the object C.
So far, finish the execution flow process that invariant shown in Figure 2 is checked.
According to the thought identical with Fig. 2, the execution schematic flow sheet that invariant is checked is carried out in the configuration change operation to object B that can obtain as shown in Figure 3.To being described as follows of flow process shown in Figure 3:
The 1st step: ENV issues configuration change at object B to MIB, and these configuration changes may comprise the increase of some attribute of object B, deletion or modification.
The 2nd step: MIB is configured change to object B.
The 3rd step: MIB notify object B carries out the internal constraint inspection of object self.
In this step, can use the internal constraint inspection of interface function inner_invarant () the realization object self in the above-mentioned false code.
The 4th step: because object A configuration depends on object B, therefore, the relation constraint inspection between the inhomogeneity object between MIB notify object A execution object A and the object B.
In this step, can use the internal constraint inspection of interface function asso_invarant () the realization object self in the above-mentioned false code, parameter is ab.
So far, finish the execution flow process that invariant shown in Figure 3 is checked.
Embodiment to configuration rule testing fixture of the present invention describes below.
Fig. 4 is the composition structural representation of configuration rule testing fixture in the embodiment of the invention.Referring to Fig. 4, this device comprises: internal constraint is checked the relation constraint inspection module 402 between module 401 and inhomogeneity object.
Wherein, internal constraint is checked module 401, is used for when object generation configuration change, and the internal constraint of object self is carried out the invariant inspection;
Relation constraint between the inhomogeneity object is checked module 402, is used for by at least one object instance generation configuration change of dependent the time, and the relation constraint between the inhomogeneity object is carried out the invariant inspection.
In device shown in Figure 4, can further include the relation constraint module between homogeneous object, be used for the relation constraint between homogeneous object is carried out the invariant inspection.
As seen from the above-described embodiment, the embodiment of the invention is by classifying to restriction relation, and by definition configuration dependence, makes after each configuration change, the configuration rule inspection only is confined to exist on the object relationship that disposes dependence, has avoided the traversal inspection to all objects in the model.And, realize the execution ownership that the configuration dependence is checked by agreement, avoided existing two same dependences of object rechecking of dependence, improved the efficient that configuration rule is checked.
Be example with configuration dependence shown in Figure 1 below, the execution efficient of comparative illustration technical solution of the present invention and existing configuration rule detecting method.
Be assumed to be each type of A, B and C and respectively create 2 objects, adopt the required configuration rule of prior art scheme to check that number of times is as shown in table 1:
| Configuration constraint | Carry out number of times |
| A self invariant | 6 |
| B self invariant | 6 |
| C self invariant | 6 |
| ab | 6 |
| ba | 6 |
| ca | 6 |
Table 1
According to technical solution of the present invention, after dependence was optimized configuration rule inspection scheme according to invariant type and configuration, required configuration rule checked that number of times is as shown in table 2:
| Configuration constraint | Carry out number of times |
| A self invariant | 2 |
| B self invariant | 2 |
| C self invariant | 2 |
| ab | 2 |
| ba | 2 |
| ca | 2 |
Table 2
As seen, technical solution of the present invention checks that to reducing configuration rule the optimization efficiency of number of times is very tangible, and particularly when object type number in the system and the increase of object instance number, the gap of technical solution of the present invention and prior art scheme will rise rapidly.With the configuration object type and the example number parametrization of a network element, can find out the efficient ratio of optimizing front and back by formula.
Suppose object type number is M, and current all types object instance number is N, has a unidirectional configuration dependence between any two object types.The dependence that exist in the model this moment adds up to M (M-1)/2, and on average externally there is (M-1)/2 dependence in each object type, carries out the increase operation of single object on this basis.
The execution number of times of prior art is:
N+1.............................. (self invariant inspection number of times)
+ (N+1) M (M-1)/2............ (when each object is checked external incidence relation being checked a time)
＝(N+1)(1+M(M-1)/2)
＝O(N*M
2) (1)
Adopt technical solution of the present invention optimization execution number of times afterwards to be:
(1................................. self invariant inspection number of times)
+ M/2............................ (relation constraint between the inhomogeneity object is checked number of times)
＝1+M/2
＝O(M) (2)
In the above-mentioned formula, O () express time complexity.By (1) formula and (2) formula as seen, adopt technical solution of the present invention to optimize after, the time complexity of configuration rule inspection has reduced N*M doubly.In a typical network element system, possible M=100, N=10000 even more, this improved efficiency will be very tangible.
As seen from the above analysis, technical solution of the present invention is by distinguishing the type of invariant, definition configuration dependence, and determine different execution opportunitys for it according to the different characteristics of all kinds of invariants, greatly improved the efficient of checking based on the configuration rule of invariant, solved batch configuration performance demands.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.All any modifications of being done within the spirit and principles in the present invention, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1, a kind of configuration rule detecting method, the rule of described configuration rule for configuration data is carried out validity and consistency check, it is characterized in that this method is divided into three kinds with the restriction relation between the managed object in the network element system: relation constraint between the internal constraint of object self, inhomogeneity object and the relation constraint between homogeneous object;
When object generation configuration change, the internal constraint of described object self is carried out the invariant inspection;
By at least one object instance generation configuration change of dependent the time, the relation constraint between described inhomogeneity object is carried out the invariant inspection by the dependent or by the side among the dependent.
2, method according to claim 1 is characterized in that, the internal constraint of described object self is: the internal constraint relation of object instance self.
3, method according to claim 1 is characterized in that, the relation constraint between described inhomogeneity object is: have the interconnection constraint relation between the different object that disposes dependence.
4, method according to claim 1 is characterized in that, the relation constraint between described homogeneous object is: the restriction relation between same type, the different object instance.
5, method according to claim 3, it is characterized in that, described the time by at least one object instance generation configuration change of dependent, inspection comprises to the execution of the relation constraint between described inhomogeneity object invariant by the dependent or by the side among the dependent: when by at least one object instance generation configuration change of dependent, to being carried out the invariant inspection by dependent's self internal constraint, and by the dependent or by the side among the dependent to described by the inspection of the execution of the configuration dependence between dependent and dependent invariant.
6, according to each described method of claim 1 to 5, it is characterized in that described configuration change is: increase, deletion or retouching operation.
7, a kind of configuration rule testing fixture, the rule of described configuration rule for configuration data is carried out validity and consistency check, it is characterized in that, described configuration rule testing fixture is used for the object of processing net element system, and this device comprises: internal constraint is checked the relation constraint inspection module between module and inhomogeneity object;
Described internal constraint is checked module, is used for when the object generation configuration change of network element system, and the internal constraint of object self is carried out the invariant inspection;
Relation constraint between described inhomogeneity object is checked module, is used for by at least one object instance generation configuration change of dependent the time, from the dependent or by the side the dependent relation constraint between the inhomogeneity object is carried out the invariant inspection.
8, device according to claim 7 is characterized in that, described device further comprises the relation constraint module between homogeneous object;
Relation constraint module between described homogeneous object is used for the relation constraint between homogeneous object is carried out the invariant inspection.
9, according to claim 7 or 8 described devices, it is characterized in that described configuration change is: increase, deletion or retouching operation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007100801071A CN100471136C (en) | 2007-02-09 | 2007-02-09 | Configuration rule detecting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007100801071A CN100471136C (en) | 2007-02-09 | 2007-02-09 | Configuration rule detecting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101013966A CN101013966A (en) | 2007-08-08 |
| CN100471136C true CN100471136C (en) | 2009-03-18 |
Family
ID=38701266
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2007100801071A Expired - Fee Related CN100471136C (en) | 2007-02-09 | 2007-02-09 | Configuration rule detecting method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100471136C (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101272222B (en) * | 2008-05-06 | 2012-07-11 | 中兴通讯股份有限公司 | Restriction calibration method and device |
| EP2599006A4 (en) * | 2010-07-30 | 2014-03-05 | Hewlett Packard Development Co | Configuration management |
| US10866569B2 (en) * | 2017-06-14 | 2020-12-15 | Siemens Industry, Inc. | Fault detection and diagnostics rule selection |
| CN108804136B (en) * | 2018-05-31 | 2021-10-01 | 中国人民解放军国防科技大学 | Configuration item type constraint inference method based on name semantics |
| CN110968498B (en) * | 2018-09-30 | 2023-04-07 | 北京国双科技有限公司 | Code checking method and device |
| CN113114493B (en) * | 2021-04-02 | 2023-03-24 | 烽火通信科技股份有限公司 | Network element configuration constraint checking method and system |
-
2007
- 2007-02-09 CN CNB2007100801071A patent/CN100471136C/en not_active Expired - Fee Related
Non-Patent Citations (2)
| Title |
|---|
| Oracle数据完整性实验的控制方法. 刘建安.实验室研究与探索，第24卷第11期. 2005 |
| Oracle数据完整性实验的控制方法. 刘建安.实验室研究与探索，第24卷第11期. 2005 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101013966A (en) | 2007-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100471136C (en) | Configuration rule detecting method and device | |
| US7769704B2 (en) | Contextual pattern decoder engine | |
| US7523128B1 (en) | Method and system for discovering relationships | |
| US10025688B2 (en) | System and method for detecting data extrusion in software applications | |
| US20140282373A1 (en) | Automated business rule harvesting with abstract syntax tree transformation | |
| US20100088686A1 (en) | Programming language with extensible syntax | |
| CN104331366A (en) | Test case design efficiency promotion method and system | |
| US20100287214A1 (en) | Static Analysis Framework for Database Applications | |
| KR20110027821A (en) | Data logging in graph-based computations | |
| US9619215B2 (en) | Pre-compiler | |
| CN109241104B (en) | AISQL resolver in decision-making distributed database system and implementation method thereof | |
| CN107766353B (en) | Method and device for migrating statistical information of database | |
| CN112527774A (en) | Data center building method and system and storage medium | |
| CN108804136A (en) | Configuration item type constraint inference method based on name semantics | |
| Cabot et al. | Constraint support in MDA tools: A survey | |
| CN108255837A (en) | A kind of SQL resolvers and method | |
| US20030110175A1 (en) | Deploying predefined data warehouse process models | |
| CN109783638A (en) | A kind of user comment clustering method based on semi-supervised learning | |
| Wada et al. | Modeling turnpike frontend system: A model-driven development framework leveraging UML metamodeling and attribute-oriented programming | |
| Manousis et al. | Automating the adaptation of evolving data-intensive ecosystems | |
| Keim et al. | Trace link recovery for software architecture documentation | |
| US9652478B2 (en) | Method and apparatus for generating an electronic document schema from a relational model | |
| CN114328674A (en) | Data mining method and system based on intranet log behavior diagram | |
| CN106165369B (en) | System and method for supporting data type conversion in heterogeneous computing environment | |
| Hinrichs et al. | An ISO 9001: 2000 Compliant Quality Management System for Data Integration in Data Warehouse Systems. |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090318 Termination date: 20140209 |