CN100589652C - Conflict evading method of multi-user configuring network element data - Google Patents
Conflict evading method of multi-user configuring network element data Download PDFInfo
- Publication number
- CN100589652C CN100589652C CN200710124423A CN200710124423A CN100589652C CN 100589652 C CN100589652 C CN 100589652C CN 200710124423 A CN200710124423 A CN 200710124423A CN 200710124423 A CN200710124423 A CN 200710124423A CN 100589652 C CN100589652 C CN 100589652C
- Authority
- CN
- China
- Prior art keywords
- data
- data class
- network element
- class
- configuration order
- 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 conflict dodging method of multi-user configuration network element data. After a user initiates data configuration order, a system determines all data classes correspondingwith the configuration order; then, the system judges whether all data classes are not locked and if so, the system executes the configuration order after locking all data classes; or else, the systemrefuses to execute the configuration order. The technical proposal of the invention can effectively dodge the conflict of multi-user network element data configuration.
Description
Technical field
The present invention relates to a kind of conflict evading method, especially a kind of conflict evading method of multi-user configuring network element data.
Background technology
When a plurality of users were configured the network element data of mobile communication system, system's inspection that do not conflict so just may exist a plurality of users to revise the situation of homogeneous data simultaneously, causes conflict easily; And when a user does transfer operation, may be sent to the foreground to the still uncompleted configuration data of other users, the generation of both of these case all can cause data safety problem, causes the unusual of business.
At present,, take following two kinds of methods usually for addressing the above problem: first method, by the function piecemeal, the user can make amendment to certain functional block data, and certain functional block data is transmitted with data; Second method is carried out disaggregated classification with data, and according to being decided to be single data, other data are decided to be non-single data with the pure quantity to be quoted of no adduction relationship, find out whole single data after, put out the relation of non-single data and single data in order after, by single data to subscriber authorisation; The user only possesses the authority of single data, could revise non-single data, if not the single data that single data refers to is not authorized the user, then the user can not operate this non-single data.Yet, in the first method, data are handled respectively by the difference in functionality piece, relate to the quoted problem between data block, if deal with improperly, can cause the inconsistent hidden danger of bringing of data.And in the second method, come to subscriber authorisation by single data, run counter to the switching principle on the one hand, influenced the stability of code, as long as system has the table that increases newly will have influence on the relevant function of authentication after making; The user also needs the variation of concern table on the other hand, makes subscriber authorisation become pretty troublesome thing, and the user need go to understand too many basis should their notion and table name of understanding; At last, table that exists in the system and the inner inside secret that realizes relevant, such way meeting exposing product.
Summary of the invention
The technical problem to be solved in the present invention provides a kind of when multi-user configuring network element data, effectively realizes the conflict evading method of the multi-user configuring network element data of conflict evading.
The technical solution adopted for the present invention to solve the technical problems is:
A kind of conflict evading method of multi-user configuring network element data may further comprise the steps:
A, user initiate the data configuration order, and system determines each data class of described configuration order correspondence;
B, described system judge whether described each data class is all not locked, if described each data class is all not locked, carry out described configuration order behind described each data class of then described system lock; Otherwise described system refusal is carried out described configuration order.
In the such scheme, after described each data class was locked, if described configuration order is carried out failure, then described system removed the locking of described each data class; If described configuration order runs succeeded, the transfer of data after then will disposing is behind the foreground, and described system automatically terminates the locking of described each data class.
In the such scheme, among the described step b, the locking list of described system detection of stored judges whether described each data class is all not locked.
In the such scheme, if described each data class of described system lock, then described system also adds the locking information of described each data class in the described locking list to; If described system removes the locking of described each data class, the locking information of described each data class also will be deleted by then described system from described locking list.
In the such scheme,, then before described each data class of locking, back up the data that are configured if described system judges that described each data class is all not locked.
In the such scheme, among the described step a, described system at first determines its corresponding net element according to described configuration order, then, determines each data class that described configuration order is corresponding according to the data class and the corresponding relation of configuration order of described network element.
In the such scheme, the data class of described network element is to divide according to the configuration feature of described network element.
In the such scheme, further comprising the steps of between described step a and the described step b: described system judges whether described user has the configuration authority to described each data class, if described user has authority, then enters described step b, otherwise described configuration order is directly refused by described system.
Beneficial effect of the present invention mainly shows: technical scheme provided by the invention is classified to network element data according to the disclosed configuration feature set of industry, the user is by each data class of the mode lock arrangement order correspondence of contention, to obtain the configuration authority to the data in each data class; Have only after the locking of each data class is disengaged, other user could operate the data in described each data class; By such mode, the conflict when carrying out the network element data configuration with regard to having evaded the multi-user effectively.
Description of drawings
Fig. 1 is the conflict evading method flow chart of multi-user configuring network element data of the present invention;
Fig. 2 is the flow chart of one embodiment of the invention.
Embodiment
With reference to Fig. 1, a kind of conflict evading method of multi-user configuring network element data may further comprise the steps:
Step 101: the user initiates the data configuration order, and system determines each data class of configuration order correspondence;
Step 102: system judges whether described each data class is all not locked, if described each data class is all not locked, then carries out configuration order behind described each data class of system lock; Otherwise system's refusal is carried out configuration order.
Be example with MSCS (Mobile Switch Center Server, Mobile Switching Center Server) network element below, the invention will be further described.
Configuration feature according to the MSCS network element, its data can be divided into following data class: call number analysis classes (containing special service number), GT (Global Title, global title) number class, the mobile number analysis classes, black and white lists inserts configuration (sub-district etc.), the relaying configuration, the fraud detection class, common configuration (containing every other configuration items such as physics, signaling), non-transmission configuration (this part is not sent to the foreground, does not do locking control).
Physics, resources-type data are included into " common configuration " and belong to basic configuration; Access configuration, relaying configuration also belong to basic configuration.
Above-mentioned each data class is side by side independently, locking application separately, discharge irrelevant mutually.Because office data is quoted " common configuration " part configuration item, when therefore requiring " common configuration " to do the deletion action, if configuration item has adduction relationship with office data, such as office direction, route chain, must check whether quoted, if quote then can not delete by office data.Other each classification configurations were also locked when " common configuration " was locked, unlocked up to " common configuration ".
After having determined data class, just determined the lock class of locking data class.Table 1 is MSCS network element data class when locked, the lock class of each data class correspondence.
| Netype | Locknumber | Lockname | Lockname (English script) |
| 32 | 1 | Call number is analyzed | Call Number Analysis |
| 32 | 2 | The GT number | GT Number |
| 32 | 3 | Mobile number is analyzed | Mobile Number Analysis |
| 32 | 4 | Black and white lists | Blacklist/Whitelist Analysis |
| 32 | 5 | Insert configuration | Access Configuration |
| 32 | 6 | The relaying configuration | Trunk Management |
| 32 | 1000 | Common configuration | Common Configuration |
Table 1
In the table 1, the Netype field is represented NE type, and the NE type of supporting is as follows at present: 16 is MGW (Media Gateway, media gateway); 32 is MSCS; 1024 is CG (ChargingGateway, charging gateway);
The Locknumber field is represented the lock numbering, and the lock numbering is the overall unique number of lock, and whole system is pressed the unified numbering in network element classification back, and at present, 1-1000 is the numbering of MSCS, and 1001-2000 is the numbering of MGW; 2001-3000 is the numbering of CG;
The Lockname field represents to lock title, corresponding each different data class.
Determined that the lock class just can determine to lock the corresponding relation between class, configuration order and the tables of data.A configuration order can be operated a plurality of tables of data, and these tables of data can be in same data qualification, so once-through operation might need to lock a plurality of data class.For example: the tables of data of ADD MSCCFG (newly-increased local exchange mobile data) command operation is respectively CN_R_MSCCFG and CN_R_TEMPLETDAS, two tables are corresponding common configuration and call number analysis classes respectively, must lock common configuration and call number analysis classes when therefore carrying out ADD MSCCFG.
Configuration order adopts MML (Man Machine Language, man-machine language) command code planning, preceding 3 types that are used to distinguish network element, inferior 2 are used for the definition of data class, therefore, and when the user submits the MML order to, system at first determines its corresponding net element according to configuration order, then, can determine each data class that this configuration order is corresponding according to the data class of network element with the corresponding relation of configuration order, thereby determine corresponding operation.
Table 2 has shown that the MSCS network element partly locks the corresponding relation between class, configuration order and the tables of data.
| Locknumber | MmlCode | Tablename_b | Tablename_f |
| 1 | 1302000 | CN_R_ENTR | NULL |
| 1 | 1302001 | CN_R_ENTR | NULL |
| 1 | 1302002 | CN_R_ENTR | NULL |
| 1 | 1302020 | CN_R_DNALINFO | R_DNALINFO |
| 1 | 1302020 | CN_R_DNAL | NULL |
| 1 | 1302020 | CN_R_DNALTREE | R_DNALTREE |
| 1 | 1302021 | CN_R_DNALINFO | R_DNALINFO |
| 1 | 1302021 | CN_R_DNAL | NULL |
Table 2
In the table 2, the Locknumber field is the lock numbering;
The MmlCode field is a command code, is used to represent configuration order;
The Tablename_b field is the backstage table name;
The Tablename_f field is the foreground table name, and NULL represents it is that the backstage table is not sent to the foreground.
When system lock behind certain data class, system will add the lock category information of this data class correspondence in the locking list to; Removed the locking of certain data class when system after, system will delete the lock category information of this data class correspondence from locking list.Simultaneously, system also is by the inquiry of locking list being determined whether certain data class is locked.Wherein, locking list generally comprises following field information:
The Locknumber field is the lock numbering;
The Tablename_b field is the backstage table name;
The Tablename_f field is the foreground table name;
The MmlCode field is a command code;
The BUREAUNO field is a network element number;
The USERNAME field is a user name;
The Firstdatetime field is modification time first.
Below just the process of user's configuration data is described.
Step 201: the user initiates the data configuration order, system determines each data class of configuration order correspondence according to the configuration order and the corresponding relation of lock class, tables of data, be that system at first determines its corresponding net element according to configuration order, then, data class according to this network element is determined each data class that configuration order is corresponding with the corresponding relation of configuration order, also is each lock class of clear and definite configuration order correspondence;
Step 202: system numbers the locking list of cycle detection storage to judge whether described each data class is all not locked according to the lock of each lock class; If the result who detects is that described each data class is all not locked, then enter step 203, otherwise, enter step 206; In each testing process of cycle detection, then the data class of this lock class correspondence is not locked if there is not detected lock numbering in the locking list; If exist the data class of detected lock numbering or unusual then this lock class correspondence of testing result locked in the locking list;
Step 203: lock described each data class after the corresponding tables of data of system backup, and the lock category information of described each data class correspondence is added in the locking list;
Step 204: system carries out this configuration order; If configuration order is carried out failure, then system removes the locking of described each data class and enters step 205; If configuration order runs succeeded, the transfer of data after then will disposing is behind the foreground, and system automatically terminates the locking of described each data class and enters step 205;
Step 205: the lock category information and the process ends of described each data class correspondence deleted by system from locking list;
Step 206: system's refusal is carried out this configuration order and process ends.
As can be seen, by above step, system can effectively evade the multi-user and carry out the network element data conflict in when configuration.
The foregoing description only be for provide to of the present invention comprehensively and thorough, rather than the present invention carried out any restriction.
Claims (7)
1, a kind of conflict evading method of multi-user configuring network element data is characterized in that, may further comprise the steps:
A, user initiate the data configuration order, system at first determines its corresponding net element according to described configuration order, then, determine each data class that described configuration order is corresponding according to the data class and the corresponding relation of configuration order of described network element, arranged side by side between described each data class, independent;
B, described system judge whether described each data class is all not locked, if described each data class is all not locked, carry out described configuration order behind described each data class of then described system lock; Otherwise described system refusal is carried out described configuration order.
2, the conflict evading method of multi-user configuring network element data as claimed in claim 1 is characterized in that: after described each data class was locked, if described configuration order is carried out failure, then described system removed the locking of described each data class; If described configuration order runs succeeded, then with transfer of data behind the foreground, described system automatically terminates the locking of described each data class.
3, the conflict evading method of multi-user configuring network element data as claimed in claim 2 is characterized in that: among the described step b, the locking list of described system detection of stored judges whether described each data class is all not locked.
4, the conflict evading method of multi-user configuring network element data as claimed in claim 3 is characterized in that: if described each data class of described system lock, then described system also adds the locking information of described each data class in the described locking list to; If described system removes the locking of described each data class, the locking information of described each data class also will be deleted by then described system from described locking list.
5, the conflict evading method of multi-user configuring network element data as claimed in claim 4 is characterized in that: if described system judges that described each data class is all not locked, then back up the data that are configured before described each data class of locking.
6, as the conflict evading method of each described multi-user configuring network element data in the claim 1 to 5, it is characterized in that: the data class of described network element is to divide according to the configuration feature of described network element.
7, the conflict evading method of multi-user configuring network element data as claimed in claim 6, it is characterized in that: further comprising the steps of between described step a and the described step b: described system judges whether described user has the configuration authority to described each data class, if described user has authority, then enter described step b, otherwise described configuration order is directly refused by described system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710124423A CN100589652C (en) | 2007-11-09 | 2007-11-09 | Conflict evading method of multi-user configuring network element data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710124423A CN100589652C (en) | 2007-11-09 | 2007-11-09 | Conflict evading method of multi-user configuring network element data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101159973A CN101159973A (en) | 2008-04-09 |
| CN100589652C true CN100589652C (en) | 2010-02-10 |
Family
ID=39307860
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710124423A Expired - Fee Related CN100589652C (en) | 2007-11-09 | 2007-11-09 | Conflict evading method of multi-user configuring network element data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100589652C (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102036274B (en) * | 2009-09-29 | 2014-12-10 | 中国移动通信集团公司 | Independent conflict processing method, system, independent network elements and independent management center |
| CN105990185B (en) * | 2015-02-27 | 2020-02-11 | 中芯国际集成电路制造(上海)有限公司 | Processing method, system and device for executing operation on semiconductor object |
| CN107295540B (en) * | 2016-03-31 | 2021-02-26 | 华为技术有限公司 | Network element configuration method and device |
| CN105959148A (en) * | 2016-06-15 | 2016-09-21 | 上海斐讯数据通信技术有限公司 | Method for network management system to control network equipment |
| CN111984893B (en) * | 2020-09-29 | 2023-09-12 | 杭州迪普科技股份有限公司 | System log configuration conflict reminding method, device and system |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6115715A (en) * | 1998-06-29 | 2000-09-05 | Sun Microsystems, Inc. | Transaction management in a configuration database |
-
2007
- 2007-11-09 CN CN200710124423A patent/CN100589652C/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6115715A (en) * | 1998-06-29 | 2000-09-05 | Sun Microsystems, Inc. | Transaction management in a configuration database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101159973A (en) | 2008-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106326219B (en) | Method, device and system for checking business system data | |
| CN100589652C (en) | Conflict evading method of multi-user configuring network element data | |
| CN108134764B (en) | Distributed data sharing and exchanging method and system | |
| CN101959183B (en) | Mobile user identification code IMSI protection method based on pseudonym | |
| CN101976314B (en) | Access control method and system | |
| CN102752741B (en) | To the method, system and device of protecting terminal data | |
| EP2528276B1 (en) | Method for controlling resources on shared network element, shared network element and relevant device | |
| JPH02228749A (en) | Unorthorized service prevention method and system for lan | |
| CN100481032C (en) | USB interface lock based on double-USB key apparatus | |
| CN101242658A (en) | Mobile information multi-layer network secure auditing system | |
| CN101552989B (en) | A user data configuration method, system and mobile line configuration gateway | |
| CN113269565B (en) | Anti-counterfeiting identification method and device for preventing identification code from being reused and electronic equipment | |
| CN102243653A (en) | Method and device for managing database connections | |
| CN102984739A (en) | Breakdown information processing method and processing device | |
| CN106326786A (en) | Automatic batch processing method based on NFC chip anti-counterfeiting authentication | |
| CN110008006B (en) | Container-based big data tool deployment method and system | |
| CN101616366A (en) | The system and method that concurrent service is handled in a kind of Short Message Service Gateway | |
| CN100386990C (en) | Method for implementing intelligent network flexible authority management | |
| CN112153023B (en) | Multi-intelligent contract system platform based on intelligent contract library | |
| CN100473009C (en) | Line card management method and system | |
| CN114297841A (en) | Simulation model resource system construction system and construction method thereof | |
| CN108256812A (en) | Problem information processing method and server | |
| CN113806808A (en) | Non-invasive data desensitization method and system in distributed environment | |
| CN106878378A (en) | Scatterplot processing method in network service management | |
| CN102013979A (en) | Anti-counterfeiting authentication 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: 20100210 Termination date: 20171109 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |