CN1945530B - Arranging system and method for module having dependence - Google Patents
Arranging system and method for module having dependence Download PDFInfo
- Publication number
- CN1945530B CN1945530B CN200610138332A CN200610138332A CN1945530B CN 1945530 B CN1945530 B CN 1945530B CN 200610138332 A CN200610138332 A CN 200610138332A CN 200610138332 A CN200610138332 A CN 200610138332A CN 1945530 B CN1945530 B CN 1945530B
- Authority
- CN
- China
- Prior art keywords
- plug
- unit
- deployment
- dependence
- information
- 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 provides the deployment systems and methods which have dependent relation modules to solve the problems, such as unnecessary steps, thin packaging granularity, unrealizable modularization, and bad maintainability. The invention includes plug and plug deployment. The plug is used to encapsulate document concourse of complex application. The plug deployment designates the deployment range and deploy plug. The invention realizes modular deployment and greatly improves the maintainability of the system through plug mechanism.
Description
Technical field
The present invention relates to the deployment of components technology of computer software fields, relate in particular to the deployment of components of application system with dependence assembly.
Background technology
Along with the expansion of operation scale, the expansion of the operation scope of business, enterprise more needs multiple function can be provided, and supports multiple business, the large scale system that degree of integration is higher.A kind of large scale system that network management system in the field of telecommunications comes to this, network management system need provide miscellaneous functions such as topology, alarm, performance, configuration, signaling tracing, safety, daily record, tactical management.A large-scale application system often is made of the dozens of functional module, and each functional module is made up of to the dozens of application component several again, and therefore large-scale application system must comprise hundreds of application component.
The application component that coding is finished must can use for the user through disposing this step.Deployment is packed application component exactly and is placed in the application server according to certain form; When disposing, deployment services need be provided with using assembly.Currently used deployment mechanisms is based on the application component aspect, is example with J2EE (application and development of Java enterprise): in J2EE, application component often breaks into the bag (jar, war, ear etc.) of different-format and disposes; Therefore in the J2EE standard, the maximum deployment unit that can provide is exactly ear, and ear can only provide the simplified package to war and jar, and such deployment way more is adapted to simple compact applications system.For the application system of complexity, often need to relate to the application component of some other types, for example MBean, data source etc., the encapsulation category that these have all exceeded ear needs the deployer to pass through dedicated management interface manual configuration and deployment; In addition, if also have dependence between the application component on disposing, the deployer often has to take some special measures to be handled.Similarly situation also is same the existence in other architecture environment.
This shows, adopt present deployment way, the deployer need carry out extensive work, and may also need different deployment implementing measures at different system in order to guarantee a system deployment success; Not only increased workload and work difficulty, and the deployment of the modularization of system can't realize also.Such mode has been brought a lot of problems, causes the maintainability of system to reduce greatly, even system occurs because the difficult in maintenance and situation of scrapping.
Summary of the invention
In order to overcome above-mentioned defective, the object of the present invention is to provide a kind of deployment system with dependence assembly mould blocking, effectively solve loaded down with trivial details, the difficult in maintenance problem of large-scale application system deploying step.
For achieving the above object, a kind of deployment system with dependence assembly of the present invention comprises: plug-in unit and plug-in unit are disposed device;
Described plug-in unit is used to encapsulate the file set of complicated applications, the set of the file set file that to be all files of software module of complicated applications and modular unit generate in the runtime, and this plug-in unit is also supported dependence, and this dependence represents that service that this plug-in unit utilizes other plug-in units to provide finishes the function of oneself;
Described plug-in unit is disposed device and is used to specify scope that plug-in unit need dispose and plug-in unit is disposed.
Further, described plug-in unit has plug-in unit self-described information, and the self-described information of this plug-in unit comprises: plug-in unit sign, plug-in version, this plug-in unit relied on the same group in the name of other plug-in units.
Further, described plug-in unit self-described information adopts file or database mode to store.
Further, above-mentioned deployment system also comprises: overall system deployment information, this overall system deployment information are used for the scope and the sequencing of plug-in unit group on disposing of the plug-in unit that descriptive system will dispose.
Further, described overall system deployment information adopts file or database mode to store.
Further, above-mentioned deployment system also comprises resolver, described resolver is used for resolution system general plan information and one group of plug-in unit self-described information, finish determining of deployment scope, and put out a plug-in unit dependence chained list on the global sense in order, according to this chained list, call plug-in unit successively and dispose the deployment that device is finished plug-in unit then.
For achieving the above object, a kind of dispositions method with dependence assembly comprises the steps:
(1) reading system general plan information, wherein, the overall system deployment information is used for the scope and the sequencing of plug-in unit group on disposing of the plug-in unit that descriptive system will dispose, plug-in unit is used to encapsulate the file set of complicated applications, the set of the file set file that to be all files of software module of complicated applications and modular unit generate in the runtime, and plug-in unit is also supported dependence, and dependence represents that service that this plug-in unit utilizes other plug-in units to provide finishes the function of oneself;
(2) the overall system deployment information by obtaining in the analytical procedure (1) draws the plug-in unit tabulation of being disposed;
(3) the plug-in unit tabulation by obtaining in the analytical procedure (2) draws the dependence between the plug-in unit group;
(4) if the plug-in unit that will dispose exists and this plug-in unit that will dispose has self-described information, then read the self-described information of this plug-in unit that will dispose, and judge according to this self-described information whether other plug-in units that this plug-in unit relies on exist, if do not exist, unusually withdraw from, if exist, go out local dependence tabulation according to the self-described finish message of this plug-in unit;
(5) according to the local dependence tabulation of putting in order out in the step (4), and the dependence between the plug-in unit group that obtains in the integrating step (3), overall dependence tabulation put out in order;
(6) call plug-in unit one by one according to the overall dependence tabulation that obtains in the step (5) and dispose device, plug-in unit is disposed.
Further, described overall system deployment information adopts file or database mode storage; The self-described information of described plug-in unit adopts file or database mode storage.
The deployment that the present invention is based on plug-in unit is a kind of novel deployment mechanisms, only need revise the overall system deployment information, just can easily realize other deployment of functional module (group) level and go deployment; Overall system deployment information form is simply clear and definite, can allow the deployer be easy to define the functional module scope that needs deployment; Can realize general plan that complication system is disposed by the overall system deployment information; By introducing Plugin Mechanism, the following deployment of plug-in unit is safeguarded by module developer, and the application deployment person just only needs other deployment of functional module (group) level in the system that is responsible for; Plug-in unit (PAR) has self descriptiveness, can describe local dependency relationships, the dependence that the deployment personnel only consider higher level (between the functional module group); Plug-in unit (PAR) is a kind of mode of packing and disposing, but it has surmounted packing again and dispose, and can specify some catalogue (for example: the catalogue at resource file place) not dispose below the PAR; On realizing functional module structure, keep can not increasing the time overhead of system deployment again in the cohesion;
This method effectively reduces the complicacy of system deployment, realizes the modularization deployment; And implement simply, directly perceived, different role (developer, deployer, system operator) only needs to be concerned about configuration file seldom, greatly reduces these roles' technical ability requirement.
Description of drawings
Fig. 1 is the deployment system synoptic diagram with dependence assembly;
Fig. 2 is the deployment system overview flow chart with dependence assembly;
Fig. 3 is a complication system hierarchical structure exemplary plot;
Fig. 4 is an overall system deployment file exemplary plot.
Embodiment
Below in conjunction with accompanying drawing deployment system of the present invention and method are done further detailed description, with the webmastering software system in the field of telecommunications is example, and the network management system in the field of telecommunications can be divided into basic supporting layer Support Layer (SL), ccf layer Framework Later (FL) and application layer Application Layer (AL) as shown in Figure 3.All complicated systems all should have clear and definite level to divide, typical in the ICP/IP protocol stack, level notion in the functional mode is corresponding with the module group in deployment, and layer following (being the module group in deployment) is exactly a functional module one by one, for example: alarm, performance, topology etc.
Functional module extracts from functional mode, can be corresponding to function point one by one on the demand, the present invention is based on this situation and proposed a kind of deployment system with dependence functional module, this system mainly comprises: plug-in unit (PAR Plug-inArchive) and plug-in unit are disposed device.
1, plug-in unit is a kind of novel deployment unit that is equivalent to functional module, and can contain other common deployment unit, thereby possesses the ability of encapsulation complicated applications, and the deployment of complicated applications system can be considered as the deployment of plug-in unit one by one.Plug-in unit PAR is that software module corresponding physical on service end/client realizes in the complication system, is embodied as the set of the file that all files that the developer provided of a software module and modular unit generate in the runtime.
Before the notion that does not propose plug-in unit, the needed various files of software module are scrappy, as jar file, configuration file, run-time file etc., often be dispersed under each catalogue of application system, in order to reach the dismountable purpose of each module, need to do a large amount of work by hand, perhaps use the complex installation program to solve this problem.The present invention proposes after the notion of plug-in unit, can be a plug-in unit with all these integrating documents, the degree of modularity when greatly having strengthened the system deployment operation; In addition, plug-in unit (PAR) is also supported dependence, and the function of oneself is finished in the service that plug-in unit may utilize another plug-in unit to provide.With J2EE is example, even if the deployment unit ear of maximum in the J2EE standard also may not embody a function point fully on disposing; And the dependence between these function points (group), can't describe clear especially at present deployment unit.Therefore, the present invention proposes a kind of new deployment unit: i.e. plug-in unit PAR (Plug-in Archive).Realized the modularization that function point is disposed.
Each all has the information of plug-in unit self, for example: plug-in unit ID, plug-in version, and this plug-in unit relied on the same group in the name (so as to a local dependence tabulation is provided) etc. of other plug-in unit, be very important for the deployer.The information of plug-in unit self can be stored with different modes (file or database etc.).What adopt in the present embodiment is file mode, and each plug-in unit is deposited the information of these plug-in units self by a plug-in unit self-described file (being distinguished with specific file suffixes), and the content of each plug-in unit self-described file is finished by add-in developer.
As follows is exactly the example of a plug-in unit self-described file:
The information such as ID (sign), version, module dependence that comprise module (in deployment for plug-in unit) in this document,
<？xml?version＝″1.0″encoding＝″GB2312″？>
<par>
<info?name＝″example1″version＝″1.0″/>
<depend>example2.par</depend>
<depend>example3.par</depend>
</par>
By this file, can know the ID (example1) of plug-in unit, version (1.0), the name of other par (example2.par and example3.par) in the same level of its dependence.
2, plug-in unit is disposed device, and being used to specify needs the scope of disposing in the plug-in unit (PAR), keeps can not increasing the time overhead of system deployment again in the cohesion on realizing the function point structure.
Plug-in unit and plug-in unit are disposed the core that device has constituted deployment system, but in order to dispose large-scale application system, also need some accessories:
A, overall system deployment information, in order to the scope of the plug-in unit PAR that will dispose in the descriptive system, and the sequencing of module group on disposing.These information are that the overall situation is unique in system, can store this information with different modes (file or database etc.), what adopt in the present embodiment is file mode, store with the overall system deployment file, as shown in Figure 4: this document passes through the DeployedPar unit scope of definition part administration plug-in unit usually; Usually define the plug-in unit group by fileset unit, when plug-in unit is disposed the dependence processing, write fileset (plug-in unit group) deployment earlier in front, therefore, the sequencing that the module group is disposed among Fig. 4 is exactly dir1 → dir1/dir2 → dir1/dir3 → dir1/dir4 → dir1/dir5.This document form is simple, and support asterisk wildcard (for example: * or? number etc.), as can be seen from the figure, only need write a few style of writing words, just can define the plug-in unit scope that needs deployment easily.Therefore the user can define the plug-in unit that needs deployment easily in the overall system deployment file.
B, resolver, be responsible for resolution system general plan file (deploy.xml) and one group of plug-in unit self-described file and (adopt file mode in the present embodiment, if adopt slightly difference of database or alternate manner), finish determining of deployment scope, define other plug-in unit tabulations that this plug-in unit relies on, collect all deployment files, a plurality of local dependence tabulations are merged into an overall plug-in unit dependence tabulation, then, according to this tabulation, call plug-in unit deployment device and dispose plug-in unit successively; Plug-in unit is disposed device according to disposing agreement, and which catalogue below the decision plug-in unit will be disposed; Obtain the assembly set that all can be disposed by document scanner then, dispose all assemblies according to type.
The principle that plug-in unit is disposed the dependence processing is:
Dependence between the plug-in unit group (being meant the fileset element in the overall system deployment file) is that the fileset that writes in front disposes earlier.
Dependence within the plug-in unit group is to decide by the dependence that defines in the plug-in unit self-described file (parinfo.xml).
Fig. 2 has described the process flow diagram that the plug-in unit with dependence of the present invention is disposed, and this flow process mainly comprises the steps:
(1) reads general plan file deploy.xml;
(2) by resolving this general plan file, draw the overall plug-in unit tabulation of being disposed;
(3) analyze dependence between the module group (layer);
(4) judge that in fact whether the plug-in unit that will dispose exists, if there is no, unusually withdraw from, if exist, and judge whether there is corresponding self-described file below this plug-in unit, if this plug-in unit does not have corresponding self-described file, then withdraw from unusually, if this plug-in unit has corresponding self-described file, then the self-described file consolidation according to this plug-in unit goes out local dependence chained list;
(5) according to local dependence tabulation, the dependence between the binding modules group (layer) is put out overall dependence chained list in order;
(6) according to overall dependence chained list, call plug-in unit one by one and dispose device, plug-in unit is disposed.
Can learn that by technique scheme the deployment that the present invention is based on plug-in unit is a kind of novel deployment mechanisms, only need revise the overall system deployment information, just can easily realize other deployment of functional module (group) level and go deployment; And other deployment mechanisms all needs from dispose catalogue a large amount of assembly bags of interpolations/deletion could realize the deployment of some assemblies/go deployment;
Overall system deployment information form is simply clear and definite, can allow the deployer be easy to define the functional module scope that needs deployment; Can realize general plan that complication system is disposed by the overall system deployment information;
By introducing Plugin Mechanism, the following deployment of plug-in unit is safeguarded by module developer, and the application deployment person just only needs other deployment of functional module (group) level in the system that is responsible for;
Plug-in unit (PAR) has self descriptiveness, can describe local dependency relationships, the dependence that the deployment personnel only consider higher level (between the functional module group);
Plug-in unit (PAR) is a kind of mode of packing and disposing, but it has surmounted packing again and dispose, and can specify some catalogue (for example: the catalogue at resource file place) not dispose below the PAR; On realizing functional module structure, keep can not increasing the time overhead of system deployment again in the cohesion;
This method effectively reduces the complicacy of system deployment, realizes the modularization deployment; And implement simply, directly perceived, different role (developer, deployer, system operator) only needs to be concerned about configuration file seldom, greatly reduces these roles' technical ability requirement.
Claims (8)
1. the deployment system with dependence assembly is characterized in that, comprising: plug-in unit and plug-in unit are disposed device;
Described plug-in unit is used to encapsulate the file set of complicated applications, the set of the described file set file that to be all files of software module of described complicated applications and modular unit generate in the runtime, and described plug-in unit is also supported dependence, and described dependence represents that service that this plug-in unit utilizes other plug-in units to provide finishes the function of oneself;
Described plug-in unit is disposed device and is used to specify scope that plug-in unit need dispose and plug-in unit is disposed.
2. the deployment system with dependence assembly according to claim 1, it is characterized in that, described plug-in unit has plug-in unit self-described information, and the self-described information of this plug-in unit comprises: plug-in unit sign, plug-in version, this plug-in unit relied on the same group in the name of other plug-in units.
3. the deployment system with dependence assembly according to claim 2 is characterized in that, described plug-in unit self-described information adopts file or database mode to store.
4. the deployment system with dependence assembly according to claim 3, it is characterized in that, also comprise: overall system deployment information, this overall system deployment information are used for the scope and the sequencing of plug-in unit group on disposing of the plug-in unit that descriptive system will dispose.
5. the deployment system with dependence assembly according to claim 4 is characterized in that, described overall system deployment information adopts file or database mode to store.
6. the deployment system with dependence assembly according to claim 5, it is characterized in that, also comprise resolver, described resolver is used for resolution system general plan information and one group of plug-in unit self-described information, finish determining of deployment scope, and put out a plug-in unit dependence chained list on the global sense in order, then according to this chained list, call plug-in unit successively and dispose the deployment that device is finished plug-in unit.
7. the dispositions method with dependence assembly is characterized in that, comprises the steps:
(1) reading system general plan information, wherein, described overall system deployment information is used for the scope and the sequencing of plug-in unit group on disposing of the plug-in unit that descriptive system will dispose, described plug-in unit is used to encapsulate the file set of complicated applications, the set of the described file set file that to be all files of software module of described complicated applications and modular unit generate in the runtime, and described plug-in unit is also supported dependence, and described dependence represents that service that this plug-in unit utilizes other plug-in units to provide finishes the function of oneself;
(2) the overall system deployment information by obtaining in the analytical procedure (1) draws the plug-in unit tabulation of being disposed;
(3) the plug-in unit tabulation by obtaining in the analytical procedure (2) draws the dependence between the plug-in unit group;
(4) if the plug-in unit that will dispose exists and this plug-in unit that will dispose has self-described information, then read the self-described information of this plug-in unit that will dispose, and judge according to this self-described information whether other plug-in units that this plug-in unit relies on exist, if do not exist, unusually withdraw from, if exist, go out local dependence tabulation according to the self-described finish message of this plug-in unit;
(5) according to the local dependence tabulation of putting in order out in the step (4), and the dependence between the plug-in unit group that obtains in the integrating step (3), overall dependence tabulation put out in order;
(6) call plug-in unit one by one according to the overall dependence tabulation that obtains in the step (5) and dispose device, plug-in unit is disposed.
8. the dispositions method with dependence assembly according to claim 7 is characterized in that, described overall system deployment information adopts file or database mode storage; The self-described information of described plug-in unit adopts file or database mode storage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610138332A CN1945530B (en) | 2006-11-07 | 2006-11-07 | Arranging system and method for module having dependence |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610138332A CN1945530B (en) | 2006-11-07 | 2006-11-07 | Arranging system and method for module having dependence |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1945530A CN1945530A (en) | 2007-04-11 |
| CN1945530B true CN1945530B (en) | 2010-05-12 |
Family
ID=38044947
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610138332A Expired - Fee Related CN1945530B (en) | 2006-11-07 | 2006-11-07 | Arranging system and method for module having dependence |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1945530B (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101930379A (en) * | 2010-08-20 | 2010-12-29 | 上海普元信息技术股份有限公司 | Structure and method for incremental deploying of server applications in distributed software system |
| CN103166787A (en) * | 2011-12-15 | 2013-06-19 | 中国移动通信集团浙江有限公司 | Information analysis method and information analysis device |
| CN102521390B (en) * | 2011-12-21 | 2015-07-08 | 北京人大金仓信息技术股份有限公司 | Database management and monitoring system based on pin function |
| CN103309700B (en) * | 2012-03-16 | 2016-05-18 | 腾讯科技（深圳）有限公司 | A kind of plug-in management control method and device |
| CN103678240B (en) * | 2012-09-18 | 2018-08-24 | 阿里巴巴集团控股有限公司 | Method and system for carrying out modularization management to Distributed Calculation |
| CN105099739B (en) * | 2014-05-15 | 2018-08-17 | 中国移动通信集团公司 | One kind being based on plug-in type software deployment method, apparatus and application server |
| CN104063220B (en) * | 2014-06-25 | 2017-04-12 | 清华大学 | Linux basic software dependency relationship analysis method based on files |
| CN105138352B (en) * | 2015-07-31 | 2020-03-20 | 百度在线网络技术（北京）有限公司 | Method and device for installing application plug-in |
| CN107015820A (en) * | 2016-01-27 | 2017-08-04 | 阿里巴巴集团控股有限公司 | Using startup method, device and server |
| CN109597627A (en) * | 2017-09-30 | 2019-04-09 | 北京国双科技有限公司 | A kind of component mounting method, device, storage medium and processor |
| CN109491763B (en) * | 2018-11-14 | 2021-07-20 | 北京奇艺世纪科技有限公司 | System deployment method and device and electronic equipment |
| CN109558139A (en) * | 2018-11-21 | 2019-04-02 | 北京城市网邻信息技术有限公司 | Marker method, device, computer equipment and the storage medium of component dependencies |
| CN110442399B (en) * | 2019-08-09 | 2022-08-16 | 广州小鹏汽车科技有限公司 | Method and device for executing read Native service of application, storage medium and terminal equipment |
| CN116225464B (en) * | 2023-05-09 | 2023-07-11 | 霖济智云科技(苏州)有限公司 | Rapid deployment method of platform |
| CN117289951B (en) * | 2023-11-22 | 2024-04-02 | 华信咨询设计研究院有限公司 | Software system multi-application automatic deployment method based on recursion principle |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1361509A1 (en) * | 2002-05-08 | 2003-11-12 | Sap Ag | Sortware delivery manager |
| CN1553332A (en) * | 2003-06-02 | 2004-12-08 | 联想(北京)有限公司 | Facility centralizing management method based by plugging technology |
| US6892382B1 (en) * | 1999-05-06 | 2005-05-10 | Sun Microsystems, Inc. | Method and apparatus for implementing deployment descriptors in an enterprise environment |
-
2006
- 2006-11-07 CN CN200610138332A patent/CN1945530B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6892382B1 (en) * | 1999-05-06 | 2005-05-10 | Sun Microsystems, Inc. | Method and apparatus for implementing deployment descriptors in an enterprise environment |
| EP1361509A1 (en) * | 2002-05-08 | 2003-11-12 | Sap Ag | Sortware delivery manager |
| CN1553332A (en) * | 2003-06-02 | 2004-12-08 | 联想(北京)有限公司 | Facility centralizing management method based by plugging technology |
Non-Patent Citations (1)
| Title |
|---|
| 全文. |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1945530A (en) | 2007-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1945530B (en) | Arranging system and method for module having dependence | |
| US6892382B1 (en) | Method and apparatus for implementing deployment descriptors in an enterprise environment | |
| US8706697B2 (en) | Data retention component and framework | |
| US8037471B2 (en) | Systems and methods for constructing relationship specifications from component interactions | |
| US7421621B1 (en) | Application integration testing | |
| US20130275958A1 (en) | Automatic identification of services | |
| CN103425468B (en) | Plug-in type software integrating method and device | |
| US9274783B2 (en) | Dynamic delivery and integration of static content into cloud | |
| EP1810131A2 (en) | Services oriented architecture for data integration services | |
| JP2014044743A (en) | Programming interface for computer platform | |
| WO2003034219A1 (en) | System and method for implementing an event adapter | |
| CN102323884A (en) | Web service container and method for issuing multiple Web services | |
| US8972487B2 (en) | Automated framework for testing enterprise services consumer technologies | |
| CN113486095A (en) | Civil aviation air traffic control cross-network safety data exchange management platform | |
| CN111048164A (en) | Medical big data long-term storage system | |
| EP1050813A2 (en) | Method and apparatus for implementing deployment descriptions in an enterprise environment | |
| CN114168421A (en) | Customized code compatibility analysis system and method based on micro-service call chain | |
| US9176974B1 (en) | Low priority, multi-pass, server file discovery and management | |
| US20080147720A1 (en) | Apparatus and method for distributing information between business intelligence systems | |
| Sung et al. | A component-based product data management system | |
| US8423957B2 (en) | Using the z/OS load module system status index to distinguish product tag files | |
| CN108255499B (en) | Component processing method and device | |
| Křenek et al. | gLite Job Provenance—a job‐centric view | |
| Jay | SAP NetWeaver Portal technology: the complete reference | |
| Rosiek et al. | Infrastructural approach to modern digital library and repository management 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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100512 Termination date: 20151107 |
|
| EXPY | Termination of patent right or utility model |