CN101193452B - Method for control module registration in automatic switching optical network and its application method - Google Patents
Method for control module registration in automatic switching optical network and its application method Download PDFInfo
- Publication number
- CN101193452B CN101193452B CN2007100867628A CN200710086762A CN101193452B CN 101193452 B CN101193452 B CN 101193452B CN 2007100867628 A CN2007100867628 A CN 2007100867628A CN 200710086762 A CN200710086762 A CN 200710086762A CN 101193452 B CN101193452 B CN 101193452B
- Authority
- CN
- China
- Prior art keywords
- module
- control plane
- registration table
- chosen
- depending
- 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 a method for automatically control module registration in a switching optical network. The method comprises the processes: an identification of the control plane module is distributed; a parameter of a module registration list is confirmed according to needs of a user; the module registration list is filled by the parameter of the module registration list and the module registration list is used in the start or restart process of the control plane, or in the process of stopping module or restarting module in running process of the control plane. The invention also discloses a method for managing an ASON control plane module by using the module registration list. The invention can be used for starting and restarting the control plane, as well as stopping the module and restarting part of the module in the running process of the control plane. The invention has the advantages of flexible selection of function set and flexible customization of demanded module number. Different versions and function sets can be acquired by maintaining a complete version and filling different module registration lists.
Description
Technical field
The present invention relates to a kind of ASON field, specifically, relate to the method and the application process thereof of control module in a kind of ASON or component register.
Background technology
In ASON (ASON is commonly called as ASON (Automatically Switched Optical Network)) field, connection management and control that the ASON Control Node is responsible for whole network are moving more processing protocol on it.Clear for convenience on the maintenance and management and function is divided into a plurality of different modules (or assembly) with the The whole control plane function usually, realizes specific function by certain combination.In the control plane operational process, needs may occur increases before and the demand of off-duty module; Perhaps because the restriction of hardware condition can not load whole ASON modules; Perhaps because in the commercial affairs, wishing only provides part A SON the situation of function.How to be implemented in the demand that satisfies different user (or different hardware platforms) under the cover ASON Control Software, even satisfy in operational process the dynamic load that realizes function, this becomes a unusual complicated and significant problem, does not still have perfect solution at present.
In known solution, the function with needs combines usually, forms a particular version and issues.Because the complicacy of the technology of control plane own and the diversity of demand, under the prior art condition, often by safeguarding that a plurality of different editions realize the demand of different user (or different hardware platforms).This disposal route has tangible deficiency: when the function collection of needs has than big-difference, often need to safeguard simultaneously a plurality of versions, even need a plurality of different versions of exploitation synchronously, increased the cost and the cost of exploitation; In a single day version is determined, often be difficult to change, and this change generally need spend big cost.
Summary of the invention
Technical matters solved by the invention provides control module process registration in a kind of ASON, carrying out function by module register method flexibly reduces, thereby realize only needing the same set of version of maintenance (function complete or collected works) just can realize different function collection, thereby satisfy the demand of different user (or different hardware platforms).
Technical scheme is as follows:
Control module process registration in the ASON, step comprises:
A, be the module assignment sign of control plane;
B, according to user's needs, the parameter of determination module registration table;
C, fill in the module registration table according to the parameter of module registration table;
D, when control plane start or restarting process in use the module registration table; Perhaps, when start-stop module in the control plane operational process or restart and use the module registration table in the process of module.
Further, in the steps A, the described module I D that is designated, described module I D is the unique identification of control plane inner module.
Further, among the step B, the parameter of described module registration table comprises that dependence, registration boot sequence, module weight or the module between the module starts time-out time.
Another technical matters solved by the invention provides a kind of method that adopts the module registration table that ASON control plane module is managed, and realizes dynamic load or reduces part A SON control plane module, realizes the demand of smooth upgrade.
Technical scheme is as follows:
The method that adopts the module registration table that ASON control plane module is managed, step comprises:
(1) when control plane starts or restarts, the read module registration table;
(2) if, then start overtime timer when front module startup as yet;
(3) all start success if work as the Depending module of front module, then start and work as front module;
(4) deletion overtime timer.
Further, in the step (1), when control plane starts or restarts, calling module register method, read module registration table.
Further, in the step (2),, judge successively whether corresponding module starts by the described module registration table that reads; If, handle the next module in the described module registration table when front module starts.
Further, in the step (3),, judge successively whether Depending module has started success according to Depending module number and Depending module ID; If Depending module does not start as yet, then start Depending module.
Further, in the step (4),, then handle accordingly according to weight if Depending module starts failure, when front module starts the startup timer expiry of failure or module.
Another technical matters solved by the invention provides a kind of module registration table that adopts to the method that ASON control plane module manages, and has realized dynamically stopping in the control plane operational process or reduced part A SON control plane module.
Technical scheme is as follows:
The method that adopts the module registration table that ASON control plane module is managed, step comprises:
I, in the control plane normal course of operation, the read module registration table;
Ii, in described module registration table, there is chosen module, sends notification message that described chosen module is about to stop to Depending module;
Iii, stop described chosen module, and return and stop described chosen module result.
Further, step I is specially, when control plane normally in service, when receiving the order that stops chosen module, calling module register method, read module registration table.
Further, comprise among the step I i, obtain the Depending module table, stop to depend in the described Depending module table module of chosen module.
Another technical matters solved by the invention provides a kind of method that adopts the module registration table that ASON control plane module is managed, realized in the control plane operational process, dynamic load, start or restart part A SON control plane module, satisfied the demand of smooth upgrade.
Technical scheme is as follows:
The method that adopts the module registration table that ASON control plane module is managed, step comprises:
I, when control plane normally in service, the read module registration table;
If the II chosen module exists, start described chosen module in the module registration table;
The notification message that III, the described chosen module of transmission start is to the Depending module of chosen module;
IV, return the result that starts described chosen module.
Further, step I is specially, and is normally in service when control plane, when receiving startup or restarting the order of chosen module, and calling module register method, read module registration table.
Further, in the Step II, whether have described chosen module in the judge module registration table, if there is no described chosen module is returned described chosen module to main control module and is not had message; If chosen module exists in the module registration table, start described chosen module, and obtain the Depending module table.
Further, among the Step II I, all modules send described chosen module and start or restart in the described Depending module table that obtains, and join the notification message of control plane operation.
Technique effect of the present invention is as follows:
1) the function collection can be selected flexibly, and the number of modules that needs can flexible customization.
2) only need to safeguard complete or collected works' version, fill in different module registration tablies and can obtain different versions, realize different function collection.
3) can be applicable to that control plane starts, control plane is restarted, control plane start-stop module in service, control plane are in service restarts multiple occasion such as part of module.
4) weight can be selected and expand as required flexibly, satisfies the demand of different scenes.
5) setting of time-out time is convenient in time handle unusual.
6) can divide the module registration table flexibly according to the requirement of real system, actual operation is strong, adaptability is strong.
7) can realize that the control plane system is in service, dynamic load or Unload module.
8) can realize that the control plane system is in service, dynamically restart part of module.
Description of drawings
Fig. 1 is that control plane starts or the main flow chart when restarting;
Fig. 2 is the detailed process process flow diagram of embodiment one;
Fig. 3 is in the control plane operational process, the main flow chart of Unload module;
Fig. 4 is the detailed process process flow diagram of embodiment two;
Fig. 5 is in the control plane operational process, the main flow chart of load-on module;
Fig. 6 is the detailed process process flow diagram of embodiment three.
Embodiment
When only needing partial function, ASON control plane module process registration proposed by the invention is utilized module registration flexibly to carry out function and is reduced, thereby realized only needing to safeguard same set of version (function complete or collected works), just can realize different function collection, satisfy the demand of different user (or different hardware platforms).
The present invention adopts the module registration table that the module boot sequence of ASON control plane is controlled, and may further comprise the steps:
1, distributes a unique sign (module I D) for the module of each control plane (satisfying the module independence requirement);
2, according to function collection (being user's request) requirement, clearly need to make up which module;
3, according to the requirement of function collection, the dependence of determination module;
4, according to the requirement of function collection, clear and definite module registration and boot sequence;
5, according to the requirement of function collection, the weight of clear and definite module;
6, according to the requirement of function collection, the time-out time that clear and definite module starts;
7, according to above definite parameter, fill in the module registration table, the order of filling in has illustrated the boot sequence of module.
Detailed description to each parameter sees table description:
| Parameter | Explanation |
| Module I D | The module that sign will start, position have determined the order that starts |
| Weight | How this handled when sign started the module failure, and its codomain scope can be determined as required flexibly.As: represent to load the success of this module with 0, otherwise stop the operation on The whole control plane; Representing to load the failure of this module with 1 may influence the control plane operation, but can not cause the paralysis of control plane function, can continue operation; Represent to load the operation that the success or not of this module does not influence the The whole control plane with 2; Represent not pay close attention to this module with 3 and whether load success. |
| Time-out time | Also do not have definite result after starting execution how long, then think failure |
| The Depending module number | Sign starts the quantity that this module needs Depending module |
| Depending module ID | Need the module I D of dependence, quantity is caught up with the Depending module of face and is counted unanimity, uses CSV between the module I D.Module I D1 (first module that sign relies on, optional), module I D2 (second module that sign relies on, optional) ..., module I Dn (n the module that sign relies on, optional) |
For basic module (just can not reduce module), this method is not adopted in suggestion, directly loads during startup.In the present embodiment, only optional module is adopted this module login mechanism.
8, when control plane starts or restarts, use the module registration table, perhaps start-stop module in the operational process, use the module registration table when restarting module.
Of the present inventionly focus on adopting the module registration table that the module of ASON control plane is managed effectively and controlled, start, restart applicable to control plane, perhaps in the control plane operational process dynamic load, unload or restart multiple occasion such as module.
With reference to the accompanying drawings, the above-mentioned ASON control plane of several application module process registration is illustrated respectively.
Embodiment one
Shown in seeing figures.1.and.2, when control plane starts or restarts, each module of control plane is registered, realized the startup of control plane or restart.
Step S101: read module registration table.
When control plane starts or restarts, after basic module (as: operating system package module, database module, main control module, communication module, link control module, Link Resource Manager module etc.) startup finishes, the calling module register method, the read module registration table.
In this example, suppose to start basic module and finish, the calling module register method, the module relationship table that reads following (with reference to Fig. 2):
| ## module I D | Weight | Time-out time | The Depending module number | Depending |
| 26 | 0 | 60 | 2 | 18，20 |
| 29 | 1 | 30 | 0 | 0 |
| 34 | 1 | 45 | 2 | 26，29 |
Step S102: whether the module of judging current selected starts.
By the module registration table that reads, order judges whether corresponding module starts.If be not activated, execution in step S103; Otherwise, execution in step S104.
In this example, owing to be the control plane start-up course, three modules (TAP (26), LMP (29), DA (34)) all do not start (with reference to Fig. 2).At first judge module ID is whether 26 TAP module starts, and starts as yet if judged result is the TAP module, carries out the startup of TAP module, execution in step S103.If the TAP module starts, judge further then whether the LMP module starts, if the LMP module is not activated, carry out the start-up course of LMP module, the start-up course of the start-up course of LMP module and TAP module is similar; If the LMP module starts, then carry out the start-up course of DA module, the start-up course of the start-up course of DA module and TAP module is similar.
Step S103: when judged result when not starting, start overtime timer.
If chosen module does not start as yet, then start overtime timer according to time-out time.
In this example (with reference to Fig. 2), the time-out time that reads TAP module (module I D is 26) is 60 seconds, starts corresponding 60s overtime timer (Ason_Timer (26,60000)).Similarly, the time-out time of LMP module (module I D is 29) is 30 seconds, starts corresponding 30s overtime timer (Ason_Timer (29,30000)).The time-out time of DA module (module I D is 34) is 45 seconds, starts corresponding 45s overtime timer (Ason_Timer (34,45000)).
Step S104:, then further judge whether to also have next module to need to start if current chosen module starts.
In this example (with reference to Fig. 2), if there is next module to need to start, then with this module as chosen module, execution in step S102 continues to start chosen module then.As: start TAP module (module I D is 26) and continue to start LMP module (module I D is 29) and DA module (module I D is 34) afterwards.If there is not next module to need to start, process ends then, return results.This place hypothesis LMP module and DA module all start success, return the optional module initialization information that finishes to main control module, and the module register method disposes.
Step S105: judge whether current Depending module starts.
If be not activated, execution in step S106; Otherwise execution in step S108.
Step S106: start current Depending module.
In this example (with reference to Fig. 2), be 2, judge whether link control module (CC module, ID is 18) and Link Resource Manager module (LRM module, ID is 20) start according to the Depending module number of TAP module.Because link control module, Link Resource Manager module be all as basic module, and started success, judged result is that Depending module has all started success.
The Depending module number of LMP module is 0, skips the step that starts Depending module; The Depending module of DA module is TAP module and LMP module, if TAP module and LMP module all start, then the DA module is finished the startup of Depending module.
Step S107: judge whether Depending module all starts successfully.
According to Depending module number and Depending module ID, order judges whether all Depending modules all successfully start; If have certain Depending module not start as yet, then start the Depending module that this does not start.
Step S108: start chosen module.
If Depending module has all started success, then start chosen module.
In this example (with reference to Fig. 2), the initialization of calling the TAP module starts function and starts the TAP module; The initialization of perhaps calling the LMP module starts function and starts the LMP module; The initialization of perhaps calling the DA module starts function and starts the DA module.
Step S109: judge whether chosen module starts success.
If start successfully execution in step S110; Otherwise execution in step S111.
Step S110: deletion overtime timer.
If chosen module starts successfully before the time of overtime timer arrives, then delete corresponding overtime timer.
In this example (with reference to Fig. 2), if before the time-out time of TAP module overtime timer (Ason_Timer (26,60000)) arrives, the TAP module starts successfully, then return and start successful operating result, the overtime timer (Ason_Timer (26,60000)) of deletion TAP module.In like manner, the LMP module is before the time-out time of overtime timer (Ason_Timer (29,30000)) arrives, and the LMP module starts successfully, returns to start successful operating result the overtime timer (Ason_Timer (29,30000)) of deletion LMP module; The DA module is before the time-out time of overtime timer (Ason_Timer (34,45000)) arrives, and the DA module starts successfully, then returns to start successful operating result the overtime timer (Ason_Timer (34,45000)) of deletion DA module.
Step S111: if Depending module starts failure, or chosen module startup failure, or module startup timer expiry, handle accordingly according to weight.
At last, return the optional module initialization information that finishes to main control module, the module register method disposes.
Embodiment two
In the control plane normal course of operation, optional module in the control plane is stopped, realizing the dynamic offloading of control plane module.
With reference to Fig. 3 and shown in Figure 4, in the control plane normal course of operation, the following description of the processing procedure of stopping modular.
Step S301: read module registration table.
When control plane normally in service, when receiving the order that stops certain module, calling module register method then, read module registration table.
In this example (with reference to Fig. 4), suppose that control plane receives the order that stops DA module (module I D is 34), by main control module calls module register method, the module relationship table that reads is as follows:
| ## module I D | Weight | Time-out time | The Depending module number | Depending |
| 26 | 0 | 60 | 2 | 18，20 |
| 29 | 1 | 30 | 0 | 0 |
| 34 | 1 | 45 | 2 | 26，29 |
Step S302: the module that whether exists these selected needs to stop in the judge module registration table.
In the module registration table, the content of existence comprises module I D and Depending module ID to the module that judgement need stop.
If have the module that need stop, execution in step S303 in the module registration table; Otherwise execution in step S304.
Step S303: obtain the Depending module table.
In this example (with reference to Fig. 4), judge that DA module (module I D is 34) exists, and does not have to depend on the module (not occurring 34 among the Depending module ID) of DA module in the module registration table.
Step S304: return module I D to main control module and do not have message.
Step S305: the module that stops to depend on this chosen module.
Comprise the module (comprising the module I D tabulation of this module among the Depending module ID) that need stop if having in the Depending module table, then need preferentially to stop to comprise the module of this Depending module table.
As (with reference to Fig. 4) in this example, the module that stops if desired is TAP module (module I D is 26), and the TAP module then needs preferentially to stop the DA module in the Depending module ID of DA module.In this example, do not have to depend on the module of DA module, skip this step.
Step S306: judge whether Depending module all stops success.
If all stop success, execution in step S307; Otherwise execution in step S308.
Step S307: the notification message that the transmission chosen module is about to stop is to Depending module.
All modules that need depend on this chosen module all stop, send message that this chosen module is about to stop to Depending module.
In this example (with reference to Fig. 4), the Depending module ID of DA module is TAP module (module I D is 26) and LMP module (module I D is 29), sends the notification message that the DA module is about to stop to TAP module and LMP module respectively.
Step S308: return the stopping modular failed message to main control module.
Step S309: stop chosen module.
In this example (with reference to Fig. 4), send the notification message that the DA module is about to stop to TAP module and LMP module and finish, call the DA module and finish the operation that function stops the DA module.
Step S310: judge whether chosen module stops success.
If stop success, execution in step S311; Otherwise, execution in step S312.
Step S311: return to main control module and to stop success message.
In this example (with reference to Fig. 4), stop the success of DA module, return the DA module to main control module and stop success message, the module register method disposes.
Step S312: if chosen module stops failure, return to main control module and to stop failed message, carry out respective handling according to weight.
In this example (with reference to Fig. 4), stop the failure of DA module, return the DA module to main control module and stop failed message, the module register method disposes.
Embodiment three
In the control plane normal course of operation, can adopt the method for the invention, optional module in the control plane is started, realize the dynamic load of control plane module.
With reference to Fig. 5 and shown in Figure 6, in the control plane normal course of operation, start being described in detail as follows of processing procedure of certain chosen module.
Step S501: read module registration table.
Normally in service when control plane, when receiving the order that starts certain chosen module, calling module register method, read module registration table.
In this example (with reference to Fig. 6), suppose that control plane receives the order (supposing that the LMP module does not start) that starts LMP module (module I D is 29), by main control module calls module register method, the module relationship table that reads is as follows:
| ## module I D | Weight | Time-out time | The Depending module number | Depending |
| 26 | 0 | 60 | 2 | 18，20 |
| 29 | 1 | 30 | 0 | 0 |
| 34 | 1 | 45 | 2 | 26，29 |
Step S502: whether have this chosen module in the judge module registration table.
Judge whether the chosen module that needs to start exists, and the content of existence comprises module I D, Depending module ID in the module registration table.
If there is execution in step S503; Otherwise, execution in step S504.
In this example (with reference to Fig. 6), LMP module (module I D is 29) exists in the module registration table, and DA module (module I D is 34) depends on the LMP module.
Step S503: obtain the Depending module table.
Step S504: return chosen module ID to main control module and do not have message.
Step S505: start this chosen module.
If this chosen module exists in the module registration table, method starts this chosen module among the employing embodiment one.
In this example (with reference to Fig. 6), adopt method startup LMP module among the embodiment one.
Step S506: judge whether chosen module starts success.
If success, execution in step S507; Otherwise, execution in step S508.
Step S507: send this chosen module and start successful notification message depends on this chosen module to needs module.
The module records that depends on this chosen module is in the Depending module table.All modules send this chosen module and have started successful message in the Depending module table that obtains in the step S503 module I D of this chosen module (need depend on tabulation), and join the notification message of control plane operation.
In this example (with reference to Fig. 6), what depend on the LMP module has only the DA module, sends the LMP module to the DA module and has started successful message, and join the notification message of control plane operation.
Step S508:, return chosen module to main control module and start failure, so that handle accordingly according to the module weight if chosen module starts failure.
Step S509: return the message that starts this chosen module success to main control module.
In this example (with reference to Fig. 6), start the success of LMP module, return the LMP module to main control module and start successful message, the module register method disposes.
Embodiment four
Present embodiment explanation control plane is normally in service, restarts the processing procedure of module.
Restarting process can be regarded the stack of stopped process and start-up course as, embodiment two and embodiment three is stacked up, and work in coordination with, and just can finish the processing that module is restarted.At this, it should be noted that the notification message difference.
Claims (14)
1. control module process registration in the ASON, step comprises:
A, be the module assignment sign of control plane;
B, according to user's needs, the parameter of determination module registration table; The parameter of described module registration table comprises that dependence, registration boot sequence, module weight or the module between the module starts time-out time;
C, fill in the module registration table according to the parameter of module registration table;
D, when control plane start or restarting process in use the module registration table; Perhaps, when start-stop module in the control plane operational process or restart and use the module registration table in the process of module.
2. control module process registration in the ASON according to claim 1 is characterized in that, in the steps A, and the described module I D that is designated, described module I D is the unique identification of control plane inner module.
3. method that adopts the module registration table that ASON control plane module is managed, step comprises:
(1) when control plane starts or restarts, the read module registration table; Described module registration table generates by following rule: be unique sign of module assignment of each control plane; According to the requirement of function collection, clearly need the module that makes up; According to the requirement of function collection, the dependence of determination module; According to the requirement of function collection, clear and definite module registration and boot sequence; According to the requirement of function collection, the weight of clear and definite module; According to the requirement of function collection, the time-out time that clear and definite module starts; According to above definite parameter, fill in the module registration table, the order of filling in has illustrated the boot sequence of module;
(2) if, then start overtime timer when front module startup as yet;
(3) all start success if work as the Depending module of front module, then start and work as front module;
(4) deletion overtime timer.
4. employing module registration table according to claim 3 is characterized in that the method that ASON control plane module manages, in the step (1), when control plane starts or restarts calling module register method, read module registration table.
5. employing module registration table according to claim 3 is characterized in that the method that ASON control plane module manages, and in the step (2), by the described module registration table that reads, judges successively whether corresponding module starts; If, handle the next module in the described module registration table when front module starts.
6. employing module registration table according to claim 3 is characterized in that the method that ASON control plane module manages, and in the step (3), according to Depending module number and Depending module ID, judges successively whether Depending module has started success; If Depending module does not start as yet, then start Depending module.
7. the method that employing module registration table according to claim 3 manages ASON control plane module, it is characterized in that, in the step (4),, then handle accordingly according to weight if Depending module starts failure, when front module starts the startup timer expiry of failure or module.
8. method that adopts the module registration table that ASON control plane module is managed, step comprises:
I, in the control plane normal course of operation, the read module registration table; Described module registration table generates by following rule: be unique sign of module assignment of each control plane; According to the requirement of function collection, clearly need the module that makes up; According to the requirement of function collection, the dependence of determination module; According to the requirement of function collection, clear and definite module registration and boot sequence; According to the requirement of function collection, the weight of clear and definite module; According to the requirement of function collection, the time-out time that clear and definite module starts; According to above definite parameter, fill in the module registration table, the order of filling in has illustrated the boot sequence of module;
Ii, in described module registration table, there is chosen module, sends notification message that described chosen module is about to stop to Depending module;
Iii, stop described chosen module, and return the result that stops described chosen module.
9. employing module registration table according to claim 8 is characterized in that to the method that ASON control plane module manages step I is specially, when control plane normally in service, when receiving the order that stops chosen module, calling module register method, read module registration table.
10. employing module registration table according to claim 8 is characterized in that the method that ASON control plane module manages, and comprises among the step I i, obtains the Depending module table, stops to depend in the described Depending module table module of chosen module.
11. a method that adopts the module registration table that ASON control plane module is managed, step comprises:
I, when control plane normally in service, the read module registration table; Described module registration table generates by following rule: be unique sign of module assignment of each control plane; According to the requirement of function collection, clearly need the module that makes up; According to the requirement of function collection, the dependence of determination module; According to the requirement of function collection, clear and definite module registration and boot sequence; According to the requirement of function collection, the weight of clear and definite module; According to the requirement of function collection, the time-out time that clear and definite module starts; According to above definite parameter, fill in the module registration table, the order of filling in has illustrated the boot sequence of module;
If the II chosen module exists, start described chosen module in the module registration table;
The notification message that III, the described chosen module of transmission start is to the Depending module of chosen module;
IV, return the result that starts described chosen module.
12. the method that employing module registration table according to claim 11 manages ASON control plane module, it is characterized in that, step I is specially, when control plane normally in service, when receiving startup or restarting the order of chosen module, the calling module register method, the read module registration table.
13. the method that employing module registration table according to claim 11 manages ASON control plane module, it is characterized in that, in the Step II, whether there is described chosen module in the judge module registration table, if there is no described chosen module is returned described chosen module to main control module and is not had message; If chosen module exists in the module registration table, start described chosen module, and obtain the Depending module table.
14. the method that employing module registration table according to claim 11 manages ASON control plane module, it is characterized in that, among the Step II I, all modules send described chosen module and start or restart in the Depending module table that obtains, and join the notification message of control plane operation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100867628A CN101193452B (en) | 2007-03-15 | 2007-03-15 | Method for control module registration in automatic switching optical network and its application method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100867628A CN101193452B (en) | 2007-03-15 | 2007-03-15 | Method for control module registration in automatic switching optical network and its application method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101193452A CN101193452A (en) | 2008-06-04 |
| CN101193452B true CN101193452B (en) | 2011-03-16 |
Family
ID=39488125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007100867628A Expired - Fee Related CN101193452B (en) | 2007-03-15 | 2007-03-15 | Method for control module registration in automatic switching optical network and its application method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101193452B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0940747A2 (en) * | 1998-03-05 | 1999-09-08 | NOKIA TECHNOLOGY GmbH | Computer system |
| JP2002320158A (en) * | 2001-04-23 | 2002-10-31 | Nippon Hoso Kyokai <Nhk> | Function addition/deletion-type receiver, function- loading method, and function-providing method |
| CN1399194A (en) * | 2001-07-24 | 2003-02-26 | 微软公司 | Method and system for creating and using operation system with optional functions |
| CN1593054A (en) * | 2001-05-18 | 2005-03-09 | 高通股份有限公司 | Dynamic loading and creation of functional objects in a wireless device |
| CN1601467A (en) * | 2003-09-22 | 2005-03-30 | 联想(北京)有限公司 | Custom method of embedded appliance applied software |
| CN1642105A (en) * | 2004-01-05 | 2005-07-20 | 华为技术有限公司 | Method for realizing task management for network system |
| CN1914597A (en) * | 2004-10-01 | 2007-02-14 | 索尼计算机娱乐公司 | Dynamic loading and unloading for processing unit |
-
2007
- 2007-03-15 CN CN2007100867628A patent/CN101193452B/en not_active Expired - Fee Related
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0940747A2 (en) * | 1998-03-05 | 1999-09-08 | NOKIA TECHNOLOGY GmbH | Computer system |
| JP2002320158A (en) * | 2001-04-23 | 2002-10-31 | Nippon Hoso Kyokai <Nhk> | Function addition/deletion-type receiver, function- loading method, and function-providing method |
| CN1593054A (en) * | 2001-05-18 | 2005-03-09 | 高通股份有限公司 | Dynamic loading and creation of functional objects in a wireless device |
| CN1399194A (en) * | 2001-07-24 | 2003-02-26 | 微软公司 | Method and system for creating and using operation system with optional functions |
| CN1601467A (en) * | 2003-09-22 | 2005-03-30 | 联想(北京)有限公司 | Custom method of embedded appliance applied software |
| CN1642105A (en) * | 2004-01-05 | 2005-07-20 | 华为技术有限公司 | Method for realizing task management for network system |
| CN1914597A (en) * | 2004-10-01 | 2007-02-14 | 索尼计算机娱乐公司 | Dynamic loading and unloading for processing unit |
Non-Patent Citations (1)
| Title |
|---|
| 全文. |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101193452A (en) | 2008-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100488123C (en) | Software and hardware version management method and system of communication equipment | |
| CN102244669B (en) | Software upgrading method in stacking equipment and stacking equipment | |
| CN106789250A (en) | A kind of service multi version based on container coexists implementation method | |
| CN107395729A (en) | A kind of consumption system of message queue, method and device | |
| CN102081540B (en) | Distributed dual-master control network equipment software updating method and device | |
| CN102811136A (en) | Software upgrading system and method | |
| CN102035893A (en) | Method and system for pushing data actively by server | |
| CN101155073A (en) | Computer system, changeover-to-backup-system method, changeover-to-backup-system program, monitoring device, terminal device and backup system | |
| CN111045745A (en) | Method and system for managing configuration information | |
| CN101547122B (en) | Method, device and system for recovering terminal configuration | |
| CN101645800A (en) | Upgrading method and system of computer telecommunication integrated device | |
| CN101206575B (en) | Software patch on-line upgrade method, veneer and system | |
| CN101405990B (en) | System, apparatus and method for maintaining present information of public group members | |
| AU731020B2 (en) | Method of preventing data inconsistency between master exchange data and backup exchange data | |
| CN101159896B (en) | Individual mobile terminal data packet downloading method | |
| CN101193452B (en) | Method for control module registration in automatic switching optical network and its application method | |
| CN101369914B (en) | Method and system for switching service link | |
| CN100388745C (en) | A method and system for distributed management of relay resources | |
| CN102307113B (en) | System upgrading method, system and device | |
| KR101490349B1 (en) | Method and apparatus for minimizing call failure in call processing module | |
| US6956934B2 (en) | Management system and method, and data processing apparatus | |
| CN101835067A (en) | ASON (Automatic Switch Optical Network) automatic backup method, reduction method and device | |
| CN101483728A (en) | Digital television receiving terminal, connecting apparatus, system and method | |
| WO2016206399A1 (en) | Communication equipment, device and software version upgrade method utilized in communication equipment | |
| CN100548002C (en) | The permanent virtual circuit state inquiry system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| 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: 20110316 Termination date: 20150315 |
|
| EXPY | Termination of patent right or utility model |