CN101005416A - Cross department flow coodinate method based service rule - Google Patents
Cross department flow coodinate method based service rule Download PDFInfo
- Publication number
- CN101005416A CN101005416A CN 200610011222 CN200610011222A CN101005416A CN 101005416 A CN101005416 A CN 101005416A CN 200610011222 CN200610011222 CN 200610011222 CN 200610011222 A CN200610011222 A CN 200610011222A CN 101005416 A CN101005416 A CN 101005416A
- Authority
- CN
- China
- Prior art keywords
- cooperation
- flow
- rule
- business rule
- flow process
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The method includes steps: cooperation point issuance step, each dept. of participating in cooperation issues cooperation points in operation flow to shared space; step of building cooperation region, based on need of task, authorized user create cooperation region; step of selecting cooperation points, the user creating the cooperation region selects dept. joining cooperation region, and selects cooperation points in operation flow of the selected dept. to cooperation region; step of defining rules, the user creating the cooperation region defines operational rules; flow conversion step, based on operational rules to convert operation flow in each dept. to software flow; cooperation step, each dept. joining cooperation runs software flow alone, mutual cooperation is realized caused by internal operational rules; disintegration step, when software flows of all dept. in cooperation region is end of run, cooperation completes, and cooperation region is disintegrated.
Description
Technical field
The present invention relates to technical field of the computer network, particularly a kind of trans-departmental flow process Synergistic method based on business rule.
Background technology
Rapid development of network technology makes breaks the border, region between the tissue, and shared resource, dynamic construction Virtual Organization are with the collaborative problem solving possibility that becomes of carrying out.Yet, at different organization internals, because the difference of information technology that adopts such as platform, operating system, database, application development tool etc. has caused the existence of a large amount of information islands, resource-sharing and cooperative problem solyint between being unfavorable for organizing.Grid provides one to overlap infrastructure at by flexible, safe and collaborative resource-sharing in individual and the dynamic virtual tissue formed, can shield the information island between the tissue, makes organically to integrate between the different tissues.Yet, between the tissue except needing the sharing of resource, also often need be collaborative mutually between the operation flow of a plurality of departments.
At present exist a few thing to solve the cooperative problem solyint of striding between the organization flow, typically worked as RosettaNet ebXML, CrossFlow, DynaFlow, BPEL4WS etc.Yet these solutions or be the close coupling of core, or adopt one to stride organization work stream the application of different enterprises is coupled together with one or several large and medium-sized enterprise.Yet the settling mode that exists is a kind of tightly coupled mode for the cooperation between the enterprise at present, is unfavorable for according to demand the dynamically situation of cooperation, lacks flexibility, can not be according to the partner of mission requirements Dynamic Selection cooperation.And in a plurality of departments inside of cooperating with each other, all can there be operation flow and the management strategy of self in each department, and is by a workflow that the difficulty that all participants' flow process integrates is also bigger.Use tightly coupled mode to come the operation flow of integrated different departments, also be unfavorable for the expansion and the evolution of each department's interior business flow process.Cooperation relation between software level definition affiliate flow process also needs a large amount of software knowledges, causes construction cycle of using long.
Therefore, a kind of trans-departmental flow process Synergistic method based on business rule has been proposed.The operation flow of each department is described in service layer, make service layer separate with software view, and by the cooperation rule between the definition operation flow, immediately be converted to software flow, the loose coupling of cooperation relation between the different departments flow process be can realize effectively, the autonomy and the evolution of different department service flow processs are beneficial to.
Summary of the invention
Under grid environment, according to the difference of task, need a plurality of departments of Dynamic Selection to participate in, cooperation mutually finish the work jointly, and this cooperation relation is very flexible between a plurality of departments.The present invention is intended to:
1. the dissemination method of department service process ability is provided, makes different departments the operation flow ability description externally can be issued, to participate in cooperation.
2. provide cover coordinated regions to create and the business rule define method cooperation relation between the operation flow of describing different departments on the service layer.
3. provide a cover from operation flow, be transformed into software flow according to business rule, and the method for software flow cooperation when operation.
The objective of the invention is to overcome the deficiency that exists in the background technology, provide methodology to come cooperation relation between the loose definition flow process, and cooperation when realizing operation.
According to the solution of the present invention, a kind of trans-departmental flow process Synergistic method based on business rule has been proposed, may further comprise the steps: cooperation point issuance step, the cooperation point in each department's issuing service flow process that participates in cooperating is to the communal space; The coordinated regions foundation step according to mission requirements, has the user of authority to create coordinated regions; Step of selecting cooperation, the establishment user of coordinated regions selects to add the department of coordinated regions, and will choose the cooperation point in the operation flow of department to be selected into coordinated regions; The rule definition step, the establishment user definition business rule of coordinated regions; The flow process switch process is converted to software flow with the operation flow of each department according to business rule; The cooperation step, each participates in department's isolated operation software flow of cooperation, owing to inherent business rule is realized mutual cooperation; Breakdown procedure, the software flow end of run of all departments in coordinated regions, cooperation is finished, and disintegrate in coordinated regions.
It is task-driven that described coordinated regions make up.
It is dynamic that described cooperation point is selected, and can independently by the creator of coordinated regions select or select through consultation.
Described coordinated regions comprise the resource of using in role, personnel and the operation flow running of cooperation point, business rule, the execution of participation operation flow.
Described coordinated regions are supported the department that participates in cooperating dynamically to add and are withdrawed from.
The use business rule defines the cooperation relation between the different department service flow processs, and business rule comprises logic rules, monitoring rule and data circulation rule.
Described operation flow and business rule are the service-oriented personnel, with platform independence, do not comprise the details of software view.
Be loosely-coupled between the described operation flow, business rule defines as required.
Described operation flow is instant the generation to software flow.
Compared with prior art, effect of the present invention is embodied in:
1) operation flow in professional hierarchy description department makes full use of the benefit of bringing towards end user programming, isomerism, the complexity of shielding bottom Workflow system.
2) coordinated regions are supported affiliate's adding and are withdrawed from, and embody the opening of cooperation.
3) create coordinated regions as required, dynamically select the affiliate according to the ability of service, partner selection mode flexibly is that Virtual Organization's execution provides support.
4) the use business rule defines the cooperation relation between the different department service flow processs, realizes the loose couplings between the department service flow process.
5) operation flow of different departments generates software flow immediately according to business rule, dynamic interaction when realizing operation.
The present invention can be widely used in IT application in enterprises, and E-Government and ecommerce etc. support to stride the resource-sharing and the dynamic cooperation work of organizational boundary, belong to computer application field.
Description of drawings
By the detailed description below in conjunction with accompanying drawing, above-mentioned and other aspects, feature and advantage of the present invention will become more apparent.In the accompanying drawing:
Fig. 1 is the life cycle schematic diagram of coordinated regions of the present invention.
Fig. 2 is of the present invention based on the collaborative flow chart of the trans-departmental flow process of business rule.
Fig. 3 A and 3B are concrete application examples of the present invention.
Embodiment
Below in conjunction with accompanying drawing the present invention is specified.Be noted that described embodiment only is for illustrative purposes, rather than limitation of the scope of the invention.
At first, the notion that the present invention relates to is described:
● collaborative space: be used for the operation flow ability description of issue this department of department and select affiliate's cooperative problem solyint according to mission requirements.Be divided into two departments: the communal space and coordinated regions.
● the communal space: each department is published to the ability that the operation flow of this department provides in the communal space.The department service flow process only needs the issue cooperation point when issue.The cooperation point information of all department's issues is present in the space.Department can allow all departments check information releasing in issue cooperation point information, also can directed issue, and only allows the department of authority check.
● cooperation point: be the task node in the operation flow, when selected adding coordinated regions, can define cooperation relation thereon.
● coordinated regions: coordinated regions are the zones that make up as required at task.Coordinated regions are task-driven, create when task arrives, and disintegrate after the task termination.In collaborative space, can there be a plurality of coordinated regions, a department can add a plurality of coordinated regions simultaneously.
● business rule: describe the rule that concerns between the cooperation point of different department service flow processs, comprise logic rules, data circulation rule and monitoring rule.
● logic rules: define the constraint in logic that must satisfy when carrying out between the cooperation point of operation flow of different departments, this constraint mainly is the precedence relationship that node must satisfy on carrying out.
● data circulation rule: define the data circulation constraint when carrying out between the cooperation point of operation flow of different departments.Stipulated the relation between the input of the output of the cooperation point in the operation flow and the cooperation point in other operation flows in the data circulation constraint.
● monitoring rule: the definition user is to the monitoring to the cooperation point in other operation flows of the monitoring of the cooperation point in the operation flow in the coordinated regions and the cooperation point in the operation flow.Be divided into absolute time rule and relative time rule.
● the absolute time rule: the definition user is to the monitoring of the cooperation point in the operation flow in the coordinated regions.This rule definition the cooperation point in the monitored operation flow must before official hour, finish.
● relative time monitoring rule: this rule is mainly used in cooperation point in the operation flow to the monitoring of the cooperation point of other operation flows, and the cooperation point in the monitoring business flowpath must be finished before certain time after carrying out with respect to the cooperation point in the monitored operation flow.
Fig. 1 is the life cycle schematic diagram of coordinated regions of the present invention.Its step is as follows:
(1) in initial condition, the operation flow of different departments is separate, and the mode that can use the mouse holder to drag makes up the operation flow of each department.
(2) task is arrived, and has the user of authority to create coordinated regions, and selects relevant participant.
(3) cooperation relation between the cooperation point in definition coordinated regions participant's the operation flow.
(4) each participant's operation flow is converted to software flow respectively, and independent operating begins cooperation.
(5) cooperation finishes, and disintegrates in coordinated regions, and the operation flow of department is got back to initial state again.
Fig. 2 is the flow chart of the trans-departmental flow process Synergistic method based on business rule of the present invention, and its step is as follows:
Cooperation point in department's issue collaboration service flow process that step SP1. participates in cooperating: want that the operation flow that the department that participates in cooperating will participate in cooperating is published in the communal space, and specify the cooperation point in the flow process.The communal space is in charge of the cooperation point information of the operation flow of each department's issue; Whether can specify during the issue cooperation point is directed issue.If do not adopt directed issue, the somebody of cooperation point information institute of issue can check.If adopt directed issue, the user who only has authority just can check cooperation point information.
Step SP2. creates coordinated regions according to mission requirements: next interim when task, and associated user's dynamic creation coordinated regions of authority are arranged, and set the association attributes of coordinated regions;
The user of step SP3. establishment coordinated regions selects the participant of coordinated regions: the founder of coordinated regions selects the participant according to the requirement to the participant by mode autonomous or that consult.The founder who is applicable to coordinated regions from master mode is to the clearer and more definite situation of participant.Negotiation mode then is applicable to has certain qualification to the participant, but indeterminate concrete participant's situation also; After determining a participant, coordinated regions are created the user cooperation point in participant's the operation flow are chosen in the coordinated regions.
According to present embodiment, above-mentioned steps SP3 can comprise following substep:
(1) in the communal space, searches and professional relevant department and cooperation point thereof; (2) founder of coordinated regions decision is the autonomous cooperation point of selecting or consult to select; (3) if autonomous the selection, the founder of coordinated regions need obtain the agreement of choosing the department under the cooperation point by other modes; If consult to select, then system start-up negotiations process, the cooperation point in the department service flow process of definite final participation cooperation; (4) determine all cooperation points that need participate in after, cooperation point in the coordinated regions is selected to finish.
Step SP4. coordinated regions are created the user and are used business rule definition cooperation relation: the cooperation relation between the cooperation point of the participant's that definition step SP3 selects operation flow.Business rule comprises logic rules, monitoring rule, data circulation rule etc., in the process of definition business rule, need the rule of adding be detected, if the rule that increases newly causes conflict, and the new rule of adding of cancellation then.
According to present embodiment, above-mentioned steps SP4 can comprise following substep:
(1) between the cooperation point of two selected operation flows, increases business rule; (2) search for the business rule that has added, judge whether newly-increased rule exists conflict, and conflict comprises: two cooperation points belong to same operation flow or the new business rule generation ring that adds; (3) if new rule of adding produces with the rule that has existed conflicts, then cancel the interpolation of current rule, otherwise add newly-increased rule.Certainly, the judgment criterion of given relevant conflict is an example, and those of ordinary skills can recognize the judgment criterion of other relevant conflicts, and these schemes also should be considered as included in the scope of the present invention.
The operation flow that step SP5. will choose the participant in the coordinated regions is converted to software flow respectively: according to the business rule of step SP4 definition, the operation flow of each department uses polymerization methods to be converted to software flow immediately respectively.
Each department's software flow isolated operation of step SP6., realize cooperation mutually: each department moves the software flow that generates in this department respectively, because software flow has comprised cooperation relation, thereby can realize cooperation.
After all participants' process flow operation was finished in the step SP7. coordinated regions, disintegrate in coordinated regions: behind the software flow end of run of all participants in the coordinated regions, the coordinated regions task was finished, and the cooperation relation between the different departments finishes.Become separate entity between the department again.The operation flow of a department can participate in the cooperation of a plurality of coordinated regions.After cooperation was finished, each participant's flow process jumped to the state of step SP2, waited for participating in other coordinated regions.
Fig. 3 A and 3B are concrete application examples of the present invention.
With reference to figure 3A and 3B, suppose to have two operation flow a and b, these two operation flows belong to different departments respectively.In a subtask, need between the operation flow a of these two departments and the b cooperation mutually to finish.In order to cooperate, operation flow a is cooperation point a1, a2, and a3 is published to the communal space, and operation flow b is cooperation point b1, b2, b3 is published to the communal space, and is chosen in the coordinated regions respectively.Cooperation relation requires b1 to finish before a1, and the output of a3 passes to the input of b3, and b2 will finish in 12 hours after a2 carries out.According to top collaborative demand, shown in the cooperation relation Fig. 3 B between operation flow a and the b.After defining the cooperation relation between operation flow a and the b, the operation flow a of different departments and b will be converted to software flow by polymerization respectively, and in the process of conversion, software flow has comprised above-mentioned cooperation rule.After conversion finished, the software flow isolated operation of each department owing to comprised cooperation relation, was cooperated during operation.
In above-mentioned exemplary embodiments, each step and substep are exemplary, those of ordinary skills can determine final actual step according to actual conditions, and the implementation method of each step and substep also is diversified, all should comprise within the scope of the present invention.
Although illustrated and described the present invention at exemplary embodiments, it should be appreciated by those skilled in the art, under the situation that does not break away from the spirit and scope of the present invention, can carry out various other change, replacement and interpolations.Therefore, the present invention should not be understood that to be limited to above-mentioned particular instance, and should be limited by claims.
Claims (11)
1. trans-departmental flow process Synergistic method based on business rule may further comprise the steps:
Cooperation point issuance step, the cooperation point in each department's issuing service flow process that participates in cooperating is to the communal space;
The coordinated regions foundation step according to mission requirements, has the user of authority to create coordinated regions;
Step of selecting cooperation, the establishment user of coordinated regions selects to add the department of coordinated regions, and will choose the cooperation point in the operation flow of department to be selected into coordinated regions;
The rule definition step, the establishment user definition business rule of coordinated regions;
The flow process switch process is converted to software flow with the operation flow of each department according to business rule;
The cooperation step, each participates in department's isolated operation software flow of cooperation, owing to inherent business rule is realized mutual cooperation;
Breakdown procedure, the software flow end of run of all departments in coordinated regions, cooperation is finished, and disintegrate in coordinated regions.
2. the trans-departmental flow process Synergistic method based on business rule according to claim 1 is characterized in that in cooperation point issuance step the operation flow of each department is to make up by the mode that the mouse holder is dragged.
3. the trans-departmental flow process Synergistic method based on business rule according to claim 1 is characterized in that in the foundation step of coordinated regions, and the establishment user of coordinated regions independently or through consultation selects the operation flow of the department of participation cooperation.
4. the trans-departmental flow process Synergistic method based on business rule according to claim 3 is characterized in that described coordinated regions support the dynamic adding of all departments and withdraw from.
5. the trans-departmental flow process Synergistic method based on business rule according to claim 1 is characterized in that in described rule definition step, and business rule comprises logic rules, monitoring rule and data circulation rule.
6. the trans-departmental flow process Synergistic method based on business rule according to claim 1 is characterized in that in the flow process switch process the instant structure of support software aspect flow process.
7. the trans-departmental flow process Synergistic method based on business rule according to claim 6 is characterized in that in the flow process switch process, realizes separating and the instant generation of software flow of service layer and software view.
8. the trans-departmental flow process Synergistic method based on business rule according to claim 1 is characterized in that in the flow process switch process, and the operation flow of different departments is converted to software flow by polymerization respectively.
9. the trans-departmental flow process Synergistic method based on business rule according to claim 1 is characterized in that described step of selecting cooperation comprises following substep:
In the communal space, search and professional relevant cooperation point;
The establishment user decision of coordinated regions is the autonomous cooperation points of selecting or consult to select;
If autonomous the selection, the establishment user of coordinated regions obtains the agreement of the department under the selected cooperation point by other modes;
If consult to select, then system start-up negotiations process, the cooperation point in all departments' operation flow of definite final participation cooperation;
After determining all cooperation points that need, described step of selecting cooperation is finished.
10. according to the trans-departmental flow process Synergistic method based on business rule of claim 1, it is characterized in that described rule definition step comprises following substep:
Between the cooperation point of two selected operation flows, increase business rule;
The business rule that search has been added judges whether newly-increased rule exists conflict; And
Conflict if new rule of adding produces with the rule that has existed, then cancel the interpolation of current rule, otherwise add newly-increased rule.
11. according to the trans-departmental flow process Synergistic method based on business rule of claim 10, it is characterized in that described conflict comprises: two cooperation points belong to same operation flow or the new business rule generation ring that adds.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100112229A CN100488141C (en) | 2006-01-18 | 2006-01-18 | Cross department flow coodinate method based service rule |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100112229A CN100488141C (en) | 2006-01-18 | 2006-01-18 | Cross department flow coodinate method based service rule |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101005416A true CN101005416A (en) | 2007-07-25 |
| CN100488141C CN100488141C (en) | 2009-05-13 |
Family
ID=38704297
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100112229A Expired - Fee Related CN100488141C (en) | 2006-01-18 | 2006-01-18 | Cross department flow coodinate method based service rule |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100488141C (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104036336A (en) * | 2013-03-06 | 2014-09-10 | 南京邮电大学 | Dynamic body synergy method for supply chain systems |
| CN104537482A (en) * | 2014-12-18 | 2015-04-22 | 华南理工大学 | Restaurant O2O cloud platform system based on supply chain management |
| CN104992301A (en) * | 2015-07-24 | 2015-10-21 | 广州支点网络科技有限公司 | Flow circulation control method and apparatus for project management of beyond enterprise/organization |
| CN105139103A (en) * | 2015-07-24 | 2015-12-09 | 广州支点网络科技有限公司 | Method and apparatus for controlling process circulation of project management and terminal device |
| CN105608522A (en) * | 2015-12-10 | 2016-05-25 | 浪潮通用软件有限公司 | Method and device for realizing cross-organization workflow |
| CN111291091A (en) * | 2020-02-07 | 2020-06-16 | 北京神州泰岳智能数据技术有限公司 | Data processing method and device and data processing system |
| CN112597309A (en) * | 2020-12-25 | 2021-04-02 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | Detection system for identifying microblog data stream of sudden event in real time |
| CN112651715A (en) * | 2020-12-29 | 2021-04-13 | 太极计算机股份有限公司 | Cross-organization business collaborative flow map construction method, device and equipment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2004258622A1 (en) * | 2003-07-08 | 2005-01-27 | Us Lynx Llc | An automated publishing system that facilitates collaborative editing and accountability through virtual document architecture |
| US6934631B2 (en) * | 2003-08-13 | 2005-08-23 | Trimble Navigation Limited | Method for standard positioning service and precise positioning service cooperative operation |
| CN1588391A (en) * | 2004-08-20 | 2005-03-02 | 中国科学院计算技术研究所 | Application dynamic union organization method based on service strategy |
-
2006
- 2006-01-18 CN CNB2006100112229A patent/CN100488141C/en not_active Expired - Fee Related
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104036336A (en) * | 2013-03-06 | 2014-09-10 | 南京邮电大学 | Dynamic body synergy method for supply chain systems |
| CN104537482A (en) * | 2014-12-18 | 2015-04-22 | 华南理工大学 | Restaurant O2O cloud platform system based on supply chain management |
| CN104992301A (en) * | 2015-07-24 | 2015-10-21 | 广州支点网络科技有限公司 | Flow circulation control method and apparatus for project management of beyond enterprise/organization |
| CN105139103A (en) * | 2015-07-24 | 2015-12-09 | 广州支点网络科技有限公司 | Method and apparatus for controlling process circulation of project management and terminal device |
| CN105608522A (en) * | 2015-12-10 | 2016-05-25 | 浪潮通用软件有限公司 | Method and device for realizing cross-organization workflow |
| CN111291091A (en) * | 2020-02-07 | 2020-06-16 | 北京神州泰岳智能数据技术有限公司 | Data processing method and device and data processing system |
| CN112597309A (en) * | 2020-12-25 | 2021-04-02 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | Detection system for identifying microblog data stream of sudden event in real time |
| CN112651715A (en) * | 2020-12-29 | 2021-04-13 | 太极计算机股份有限公司 | Cross-organization business collaborative flow map construction method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100488141C (en) | 2009-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100488141C (en) | Cross department flow coodinate method based service rule | |
| US6631354B1 (en) | Deriving and running workload manager enclaves from workflows | |
| JP4599364B2 (en) | Automated workflow service system | |
| Rusinkiewicz et al. | Towards a cooperative transaction model-The cooperative activity model | |
| Zeising et al. | Towards a common platform for the support of routine and agile business processes | |
| US20040148299A1 (en) | Automated workflow composable action model | |
| CN102096600B (en) | Information processor and resource scheduling method and program | |
| US20040148213A1 (en) | Automated workflow constraints | |
| Xu et al. | Resource allocation vs. business process improvement: How they impact on each other | |
| CN105321045A (en) | Service process formal model construction method and system | |
| Lins et al. | PACAs: process-aware conversational agents | |
| CN101960420B (en) | Method for managing resource in computing environment | |
| Yildiz et al. | Centralized versus decentralized conversation-based orchestrations | |
| CN101393620A (en) | Model for human activity description | |
| Bernus et al. | Fast tracking ICT infrastructure requirements and design, based on enterprise reference architecture and matching reference models | |
| Gebhart et al. | Supporting service design decisions | |
| Leymann et al. | Business process management standards | |
| Kravtsov et al. | Service-based Resource Brokering for Grid-Based Data Mining. | |
| CN101739259A (en) | Production method and device of service software | |
| Baïna et al. | Dynamic interconnection of heterogeneous workflow processes through services | |
| Joeris et al. | Flow. Net-Workflow Support for Inter-Organizational Engineering and Production Processes | |
| Peng et al. | MDO: framework for context-aware process mobility in building-maintenance domain | |
| Schroth | A Reference Model for Seamless Cross-Organizational Collaboration in the Public Sector. | |
| Stevens | UML and Concurrency | |
| Stoilov et al. | E-business workflow modeling and execution tools |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090513 Termination date: 20190118 |