CN100583783C - Integration tool for telecommunication area inheritance system based on configuration policy - Google Patents
Integration tool for telecommunication area inheritance system based on configuration policy Download PDFInfo
- Publication number
- CN100583783C CN100583783C CN200710176871A CN200710176871A CN100583783C CN 100583783 C CN100583783 C CN 100583783C CN 200710176871 A CN200710176871 A CN 200710176871A CN 200710176871 A CN200710176871 A CN 200710176871A CN 100583783 C CN100583783 C CN 100583783C
- Authority
- CN
- China
- Prior art keywords
- interface
- oss
- component
- module
- assembly
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an integration tool of a configuration strategy-based left-over heterogeneous system in the telecommunication field, wherein, an adaptive manager is responsible for coordinating the whole adapting course, transmitting message flow in two ways with an OSS/L port, a component access module, a data conversion module and a configuration file analysis module respectively. The configuration file analysis module analyzes and maps a configuration file according to standard interface names gained from the adaptive manager and sends the analysis result back to the adaptive manager. The data conversion module performs OSS/J data conversion. The component access module completes the call of components according to the function names and the relevant parameters gained from the adaptive manager and sends the call result back to the adaptive manager. The components are in one-to-one correspondence to the left-over system to shield the difference of the leftover heterogeneous system in a communication protocol, a security mechanism and a platform, and to convert the remote interfaces of the left-over heterogeneous system into local interfaces. The invention simplifies the integrating process and reduces the integrating cost, thereby providing telecom operators with a left-over heterogeneous system integration method which has low-cost, and high efficiency.
Description
Technical field
The present invention relates to a kind of field of telecommunications isomery Legacy System integration tool, belong to Application Middleware platform category towards field of telecommunications based on collocation strategy.
Background technology
Now, openingization is progressively moved towards in global telecommunications market, and the telecommunication user demand constantly changes, and new business, new technology are also constantly weeded out the old and bring forth the new.Telecom operation enterprise just progressively is being converted to the management pattern of " curstomer-oriented " from the management mode of traditional " network-oriented ", constantly stride forward to information-based, market-oriented direction.Main telecom operation system comprises at present: charge system, mobile network administration system, transmission network management system etc.Yet owing to lack unified planning at system's first stage of construction, the information of system and data can not be shared, whole OSS reciprocal process is intricate, thereby make these operation systems when satisfying local business demand, be difficult to carry out information mutual communication and data sharing with other operation systems, formed " information island " between the system, greatly influenced the efficient of telecom operation and the quality of telecommunications service.
In order to solve the problem in the above-mentioned telecom operation management system, Tele Management Forum TMF has proposed expansion telecom operation figure eTOM, standard the business procedure of field of telecommunications, and be that business model has proposed telecom business support system framework NGOSS of future generation with eTOM.NGOSS utilizes technology such as workflow, messaging bus, business function modularization and sharing information model and standard to guarantee that from system, process, information, four aspects of product the OSS system possesses standardization, guarantees the interconnection interoperability, realizes management and supermatic characteristics end to end.The NGOSS framework comprises the technology architecture that has nothing to do, and the telecom operation figure of increase shares three major parts of information model (SID, Shared Information and Data Model).
OSS/J is to be the OSS/BSS solution of new generation of power with the Java technology, this standard is proposed by OSS Through JavaInitiative working group, this working group is by numerous industry new technology advocates such as Motorola, Nokia, Sun, experts such as BEA form, and are specific implementations under NGOSS instructs, and affect the development of NGOSS along with the practice of OSS/J.OSS/J is intended to solve in the present telecommunication administration system interactive interface confusion, architecture complicated situation between each system.Working group utilizes the JAVA technology, and for OSS/BSS defines the standard A PI that has realized a series of opening, the developer who offers OSS/BSS uses.
Sharing information model (Shared Information and Data Modle) is with the be divided into standard of eTOM to the telecommunications service management territory, the data that relate in the telecom operation management are set up relevant information model with information, with standard and the visit of unified telecommunication service to information and data, for telecom business support system provides complete unified data guarantee, satisfy the demand of NGOSS aspect information and uniform data.
OSS/J and SID belong to the standard of Tele Management Forum TMF, also are in research and part trial run stage for both abroad, do not have complete realization case, and for Legacy System integrated still unsolved difficult problem especially to NGOSS.Domestic research work for both is in the level of the research of positive tracking TMF generally, does not see temporarily at present and can aspect interface, data, agreement, safety and the platform five the telecommunications Legacy System carried out comprehensive, lightweight, low-cost integrated realization technology to the OSS/J of standard.
Summary of the invention
Technology of the present invention is dealt with problems: overcome the deficiencies in the prior art, a kind of field of telecommunications isomery Legacy System integration tool based on collocation strategy has been proposed, the present invention utilizes assembly and configuration file just the function of Legacy System can be integrated into OSS/J, simplify integrating process greatly and reduced integrated cost, can be applicable to the fast integration of heterogeneous system, for telecom operators provide low-cost, high efficiency Legacy System Integrated Solution.
Technical solution of the present invention: the field of telecommunications isomery Legacy System integration tool based on collocation strategy, comprise OSS/J interface, adaptive manager, configuration file parsing module, data conversion module, component accesses module and assembly, wherein:
The OSS/J interface, promptly Operation Support System-Java is to be the OSS/BSS solution of new generation of power with the Java technology, is proposed by OSS Through Java Initiative working group, has realized the standard A PI of a series of opening.In method proposed by the invention, do not realize the defined telecommunications functions of OSS/J interface, but the information of interface (is comprised, interface name, return data type, parameter list etc.) generation recalls information bag, give adaptive manager and finish funcall, the function that is about to the OSS/J interface is mapped to the telecommunications Legacy System and finishes.Like this, adaptive manager has shielded the isomerism of Legacy System, and the user on upper strata can call the OSS/J interface of standard, and need not develop new telecommunication assembly.Therefore, the OSS/J interface is integrated result's a door;
Field of telecommunications isomery Legacy System integration tool based on collocation strategy is characterized in that comprising: OSS/J interface, adaptive manager, configuration file parsing module, data conversion module, component accesses module and assembly, wherein:
The OSS/J interface with the information generation recalls information bag of interface, is given adaptive manager and is finished funcall;
Adaptive manager, it is the maincenter of whole adaptive integrating process, arrange other module and finish integrated logic flow, and coordinate whole adaptation procedure, carry out bidirectional data transfers respectively and between OSS/J interface, component accesses module, data conversion module and the configuration file parsing module, its course of work is: at first, resolve the recalls information bag from the OSS/J interface, the interface name in the bag is resolved and obtained the transitional information of interface and parameter by the configuration file parsing module; Then, described transitional information is offered data conversion module carry out data transaction, promptly be transformed into the data model of assembly from the SID data model of OSS/J interface; At last, finish the corresponding assembly function calls by the component accesses module, and the preservation return value, after adaptive manager is finished all function calls by the component accesses module, obtain final result by the data conversion module parsing and return to the OSS/J interface by adaptive manager;
The configuration file parsing module is responsible for the Map Profile of parsing XML format, according to the standard interface name analysis Map Profile that obtains from adaptive manager, and analysis result is returned to adaptive manager;
Data conversion module, carry out the OSS/J interface data, it is the bi-directional conversion between SID and the module data, it is under the allotment of adaptive manager, the OSS/J interface parameters is converted to the data type of assembly according to the mapping ruler of configuration file, and the return value of data type after the component accesses module invokes is converted to the data type of OSS/J interface, be back to adaptive manager;
The component accesses module is responsible for the agreement and the irrelevant function of safety that encapsulate in the invocation component, and its is finished the calling of assembly according to function name that obtains from adaptive manager and relevant parameter, and will call the result and be back to adaptive manager;
Assembly is positioned at the bottom of whole integration tool, and is corresponding one by one with Legacy System, accepts calling of component accesses module, is used to shield the otherness of communication protocol, security mechanism and the platform of heterogeneous system, converts the Legacy System remote interface to local interface.
Also comprise the component register administration module, this module provides remote management capability, can online registration, maintenance and deletion assembly.
The implementation procedure of described adaptive manager is:
(1) parsing is from the recalls information bag of OSS/J interface, the interface name that is wherein comprised, interface return value type and interface parameters vector;
(2) utilize above-mentioned interface name initial configuration document analysis module, if described interface name is registered, then receive the initialization result of true value, initialization result failure is else if then returned error message to invoked OSS/J interface;
(3), and obtain the map information of this OSS/J interface and corresponding assembly interface if the parsing of configuration file parsing module is then passed through in the initialization success;
(4) each component interface to OSS/J interface correspondence calls, at first obtain the parameter transformation rule of this component interface from the configuration file parsing module, give data conversion module and carry out the interface parameters conversion, promptly according to the parameter transformation rule, with the parameter that the result integrates becomes current component interface of calling of the parameter of OSS/J interface and previous component interface; Then, giving the component accesses module with the parameter vector after component interface name and the conversion finishes assembly function and calls; At last, will call the result and hand to the parameter modular converter and preserve, and continue next time that component interface calls;
(5) after adaptive manager is finished all component interfaces and called, obtain the return value transformation rule of described OSS/J interface, and give data conversion module and be converted to final return value, return to invoked OSS/J interface from the configuration file parsing module.
The implementation procedure of described OSS/J interface:
(1) receives and after call on the upper strata interface name, return value type and interface parameters vector lists are packaged into a recalls information bag;
(2) the recalls information bag is given adaptive manager finish the mapping call;
(3), then return correct interface return value if adaptive manager calls success; Otherwise return malloc failure malloc information.
Described configuration file parsing module implementation procedure is:
(1) reads the configuration file of adaptive manager, obtain describing the Profile Path of OSS/J interface and its Map Profile corresponding relation, and read this configuration file, as InterfaceIndex.xml;
(2) according to the OSS/J interface name analysis InterfaceIndex.xml that obtains from adaptive manager, obtain the pairing Map Profile name of this interface, as the Map Profile AlarmManagement.xml of alarm management interface;
(3) read and resolve this Map Profile, and, be each assembly function access and generate a list object, the objectification result who resolves is returned adaptive manager each component accesses function parameters objectification.
The implementation procedure of described data transaction is as follows:
(1) preserves the recalls information bag that obtains from adaptive manager;
(2) according to the data conversion rule that obtains from adaptive manager, OSS/J interface parameter list from the recalls information bag and the tabulation of component call return value obtain source data, generate each assembly function parameters list object;
(3) result of each assembly function call is saved in the tabulation of component call return value, for the component call of back provides source data;
(4) after all component calls and finishes,, generate final return value, return to adaptive manager by the tabulation of component call return value according to the final return value create-rule that obtains from adaptive manager.
Described component accesses module comprises main interface a: invoke, its parameter comprises component class title, class interface title, the tabulation of parameter class and supplemental characteristic list object, its implementation procedure is: at first use reflex mechanism formation component class object, obtain the assembly function by class interface name and the tabulation of parameter class then, be this assembly function of parameter call with the supplemental characteristic list object again, return at last and call the result; During this time, return and do not find error message, if function call is failed then returned the failure error message if component class does not exist.
Described assembly mainly comprises two parts: Map Profile and component class file, wherein the component class file exists with the jar packet form, comprise two types of files: data class file and interface class file, the data class file has comprised used data type in this assembly, these types can be integrated instrument and use, the interface class file has comprised institute's protocols having and the irrelevant interface of safety, has encapsulated the call relation to long-range Legacy System interface; Map Profile has promptly been described the mapping relations between interface that this assembly provided and the OSS/J interface.
Described component register administration module comprises:
(1) registration and charging assembly: at first to the server transmitting assembly bag and the Map Profile thereof of integration tool operation, server dynamic load assembly bag then, and the OSS/J interface described in the Map Profile added in the interface register-file finish component register;
(2) check and revise the configuration file of assembly: the profile list of this module display server end, the client can select to check and revise the content of certain configuration file, change the mapping relations of interface and data with this, wherein the interface register-file has been described the OSS/J interface of registering on the integration tool, can stop and activation interface by revising this file; By revising Map Profile, can redefine mapping relations.
(3) deletion and unloading assembly: at first delete corresponding OSS/J interface from the interface register-file, the component class that unloading has loaded from internal memory is deleted Map Profile and assembly bag at last then.
The present invention's advantage compared with prior art is:
(1) clear in structure, module is independent, and it is loose to be coupled, and each functional module can distributed post, helps maintenance and expansion;
(2) collocation strategy make integrated more flexibly, cost is lower, and has versatility and reusability, thereby greatly improved integrated efficient;
(3) utilize collocation strategy to realize interface and data map, do not rely on hard coded substantially;
(4) utilize integrated various communications protocols of assembly and security mechanism, have more versatility;
(6) assembly can be used as an intermediate layer, has cushioned the difference between OSS/J interface and the Legacy System functional interface to a great extent, has strengthened adaptive applicability;
(7) mode of component registration can be easy to realize cascade;
Description of drawings
Fig. 1 is arranged in towards position and the effect schematic diagram of the Application Middleware platform architecture figure of field of telecommunications for the present invention;
Fig. 2 inserts the system assumption diagram of instrument for Legacy System of the present invention;
Fig. 3 is the data flowchart between the main modular of the present invention;
Fig. 4 is an OSS/J interface function flow chart of the present invention;
Fig. 5 is an adaptive manager flow chart of the present invention;
Fig. 6 is a configuration file parsing module flow chart of the present invention;
Fig. 7 is a data conversion module flow chart of the present invention;
Fig. 8 is a component accesses module flow chart of the present invention;
Fig. 9 is an assembly assumption diagram of the present invention;
Figure 10 is a component register administration module structure chart of the present invention.
Embodiment
The present invention is mainly used in the Application Middleware platform of field of telecommunications, the architecture of this halfpace is that five parts of Legacy System integration tool are formed by Workflow Management System, ESB, sharing information model server, platform basic service assembly and the present invention mainly as shown in Figure 1.Wherein: (1) Workflow Management System is mainly the reorganization of service-oriented telecommunication business process and service end to end provides flow process modeling, operation and monitoring management; (2) ESB is the information exchanging channel of platform each several part, and it ensures inserts interconnecting of component system; (3) platform basic service assembly provides the basic telecommunications service management function that comprises fault management, accounting management, resource management etc. for the telecom operation management; (4) other Legacy System of access platform can obtain the data definition standard that sharing information model provides and the data entity of shared information by the shared object access interface of sharing information server; (5) the Legacy System integration tool provides means for the isomery telecom business support system access platform that will leave over.
Information interaction flow process based on Legacy System access instrument of the present invention on this platform is as follows: the service of registering on the Workflow system visit ESB; ESB resolves into institute's requested service to inserting calling of assembly, comprises platform basic service assembly and OSS/J interface module; The OSS/J interface will call hands to integration tool, and integration tool will call the interface interchange that resolves into corresponding assembly, and finishes the conversion of SID to the Legacy System data model; Assembly is finished calling corresponding Legacy System; Call finish after, assembly returns to integration tool with the result; Integration tool converts the result model data of SID to, and returns to ESB by the OSS/J interface.
According to the application demand of platform as can be known the Legacy System integration tool mainly finish following major function:
(1) realization is to the parsing of OSS/J interface interchange;
(2) realize that the OSS/J interface calls to the mapping and the decomposition of component interface;
(3) mapping and the conversion of realization SID and Legacy System data model;
(4) realize that Legacy System inserts registration, management and the unloading of assembly;
(5) communication and the security mechanism by the shield components Legacy System;
(6) realize integrated cheaply by resolving Map Profile.
According to the above-mentioned functions requirement, structure of the present invention comprises shown in Fig. 2,3:
1.OSS/J interface
The OSS/J interface is under the guidance of target principle, based on NGOSS framework and J2EE platform, and utilization Design Mode, one group of API framework of design.OSS/J interface is not herein really realized their described functions, but give adaptive manager with the recalls information packing, adaptive manager is by decomposing interface function in the corresponding component registration, assembly carries out agreement to its pairing Legacy System once more and finishes interface function with the relevant far call of safety, upwards returns execution result again.OSS/J is equivalent to a standard door in whole process, though do not realize concrete function, see from the upper strata and can finish required funcall.They decompose real task in each Legacy System by integration tool, the isomery telecommunications Legacy System that can realize the information island shape like this is integrated to the transition type of unified OSS/J interface, though i.e. isomery each other between each telecom operators and between the system of operator inside, but can function be united by this integration tool, realize interconnecting.
The recalls information bag comprises three aspect contents:
(1) interface name: the unique identification of OSS/J interface, form by the bag path+interface function name+parameter type name at its place, can distinguish different interfaces, comprise reloading interface;
(2) interface return value type: this type is the class type, is made up of two parts, promptly wraps path+class name;
(3) interface parameters vector: with the interface parameters object of a vector storage, the parameter that this interface is received adds this vector according to its order in parameter list, and it is the key data source that component interface calls.
As shown in Figure 4, OSS/J interface institute implementation procedure is as follows:
(1) OSS/J presents with the EJB interface mode;
(2) in the realization of OSS/J interface, interface name, return value type and interface parameters vector lists are packaged into a recalls information object (being the recalls information bag), as InvokingInfo;
(3) utilize Execute (InvokingInfo) method in the adaptive manager of this recalls information object reference, and obtain the return value of an Object type;
(4) return value is interface return value type and returns downwards transition; If during make a mistake, then return malloc failure malloc information.
2. adaptive manager
Adaptive manager is the maincenter of whole adaptive integrating process, is responsible for coordinating whole adaptation procedure, the information flow between route assembly access modules, data conversion module and the configuration file parsing module.It is equivalent to the logic trunk of integration tool, will combine as other module of branches and leaves, makes it common cooperation, finishes tasks such as interface decomposition and data transaction in an orderly manner.The implementation procedure of adaptive manager is shown in Fig. 3,5:
(1) parsing is from the recalls information bag of OSS/J interface, the interface name that is wherein comprised, interface return value type and interface parameters vector.
(2) with interface name initial configuration document analysis module, if this interface name is registered, then receive the initialization result of true value, initialization result failure is else if then returned the InterfaceNotFound error message to invoked OSS/J interface.
(3), then can resolve and obtain the map information of this OSS/J interface and corresponding assembly interface by the configuration file parsing module if initialization is successful.
(4) to pairing each component interface of this OSS/J interface, at first obtain the parameter transformation rule of this component interface from the configuration file parsing module, give data conversion module and carry out the interface parameters conversion, promptly according to the parameter transformation rule, with the parameter that the result integrates becomes current component interface of calling of the parameter of OSS/J interface and previous component interface.Then, giving the component accesses module with the parameter vector after component interface name and the conversion finishes assembly function and calls.At last, will call the result and hand to data conversion module and preserve, and continue next time that component interface calls.
(5) after adaptive manager is finished all component interfaces and called, obtain the return value transformation rule of this OSS/J, and give data conversion module and be converted to final return value, return to invoked OSS/J interface by mouth from the configuration file parsing module.
In above call flow, if certain step failure, adaptive manager can be received corresponding error information, and is as shown in table 1, and whole like this transfer process will be failed, so return the InvocationFailed error message to invoked OSS/J interface.
Table 1 fatal error information list
| The error message name | Error message is described |
| InterfaceNotFound | The OSS/J interface that is called is not registered |
| MappingFileNotFound | Map Profile does not find |
| InterfaceNotFoundInMappingFile | There is not this OSS/J interface in the Map Profile |
| DataClassNotFound | The data class file does not find |
| DataTranslationFailed | The data transaction failure |
| ComponentClassNotFound | The component class file does not find |
| ComponentInvocationFailed | The assembly function malloc failure malloc |
3. configuration file parsing module
The configuration file parsing module is responsible for the Map Profile of parsing XML format, its is according to the standard interface name analysis Map Profile (comprising information such as query interface description, interface mappings, data transaction) that obtains from adaptive manager, and analysis result is returned to adaptive manager.It has shielded the type and the visit details of configuration file.The XML configuration file that this module is resolved has two types: interface register-file and Map Profile.
(1) the interface register-file writes down all registered OSS/J interface and pairing Map Profiles thereof.Parsing module can judge at first whether OSS/J interface to be processed is available according to this file, promptly whether has registered its assembly and configuration mapped file.If register, then can in this file, find the clauses and subclauses of this OSS/J interface, and obtain the Map Profile path and the filename at place, search, read and resolve this Map Profile again; If search failure, then return the MappingFileNotFound error message.If this interface is registration not, then return the InterfaceNotFound error message.The form of this interface register-file is as follows:
<xsd:schema xmlns:xsd＝″http://www.w3.org/2001/XMLSchema″>
<xsd:element name＝″InterfaceIndex″>
<xsd:sequence>
<xsd:element name＝″Item″>
<xsd:complexType>
<xsd:complexContent>
<xsd:restriction base＝″xsd:anyType″>
<xsd:attribute name＝″interface″type＝″xsd:string″/>
<xsd:attribute name＝″mappingfile″type＝″xsd:string″/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:element>
</xsd:schema>
(2) Map Profile writes down the mapping transitional information of a collection of registered OSS/J interface, and is general corresponding with certain component registration, promptly describes the mapping relations between OSS/J interface and the component interface.Can in this file, find concrete mapping transitional information by the interface name, if search failure then return the InterfaceNotFoundInMappingFile error message.The mapping transitional information of each interface is made up of three parts: the basic description of interface, its pairing component interface tabulation and return value transformation rule.A segment of this Map Profile is as follows:
<InterfaceMapping>
<Interface>Interface information</Interface>
<Methods>
<Method>
<Information>Method 1 information</Information>
<Translations>Data translation information</Translations>
</Method>
<Method>
<Information>Method 2 information</Information>
<Translations>Data translation information</Translations>
</Method>
</Methods>
<ReturnDataTranslation>
<Translations>Data translation information</Translations>
</ReturnDataTranslation>
</InterfaceMapping>
Wherein,
＜InterfaceMapping〉interface mappings process of description;
＜Interface〉the description standard interface message, comprise the type of interface name, parameter and return value;
＜Methods〉the pairing assembly function information of description standard interface;
＜Method〉concrete assembly function information is described, comprise function parameters, return value type and data conversion rule;
＜Translation〉transformation rule of characterising parameter, comprise the best property of attribute mapping relation between assembly function parameter and the standard interface parameter;
＜ReturnDataTranslation〉transformation rule between description standard interface return value and the assembly function return value.
This module functions interface is as shown in table 2:
The main interface of table 2 configuration file parsing module
| The interface name | Interface function |
| Initiate | Initial configuration document analysis module.Whether registered, read the Map Profile at this interface place then if at first searching the OSS/J interface that will resolve in the interface register-file, resolve the mapping transitional information of this interface in this file. |
| GetSubFunsNum | Obtain the pairing assembly neutron of this OSS/J interface number of functions, promptly this interface can resolve into calling what component interfaces. |
| GetNextFun | Obtain the recalls information of next assembly subfunction, comprise place class name, title, interface description, parameter type, return value type, parameter transformation rule of subfunction etc. |
| GetRetValueTranInfo | Obtain the data transaction information of final return value, be included as and obtain the transformation rule that return value should adopt. |
As shown in Figure 6, the implementation procedure of configuration file parsing module is as follows:
(1) with OSS/J interface name initialization parsing module.Its process is, reads the configuration file of adaptive manager, obtains describing the Profile Path of OSS/J interface and its Map Profile corresponding relation, and reads this configuration file, as InterfaceIndex.xml;
(2) according to the OSS/J interface name analysis InterfaceIndex.xml that obtains from adaptive manager, obtain the pairing Map Profile name of this interface, as the Map Profile AlarmManagement.xml of alarm management interface;
(3) if this Map Profile is then read and resolves in the initialization success, and with each component accesses function parameters objectification, be each assembly function access and generate a list object, the objectification result who resolves is returned adaptive manager; Otherwise return error message.
Above-mentioned objectification result mainly comprises following content: OSS/J interface name, bag path, return value type place, the tabulation of assembly function access, final return value transformation rule; Each element (corresponding to a subprogram map information) of assembly function access tabulation mainly comprises following content: the create-rule of function place class name, function name, function representation, function parameter list of types, function return value type, each parameter of function in path, assembly place, the assembly; The create-rule of function parameter comprises: source data type, source data mapping point (being certain attribute in the type), target data type, target data mapping point.
4. data conversion module
Data conversion module carries out the bi-directional conversion between OSS/J interface data (being SID) and the module data.It is converted to the data type of assembly according to the mapping ruler of configuration file with the OSS/J interface parameters, and return value is converted to the data type of OSS/J interface under the allotment of adaptive manager.It has preserved the return results that each component interface calls, and the generation of parameter of calling for subsequent components and final return value lays the foundation, i.e. the generation of follow-up data depends on the result that calls of front.
This module is as shown in table 3 for the interface that adaptive manager provides:
The main interface of table 3 data conversion module
| The interface name | Interface function |
| Initiate | Initialization.Preserve the parameter object tabulation of OSS/J interface, and generate return value preservation tabulation according to the number of component interface. |
| TransformData | Translation data.According to the transformation rule sequence of receiving, adopt reflex mechanism, each parameter object of formation component interface, and assignment is returned. |
| SetRetValue | Preserve the result that calls of component interface.The order of calling according to component interface is preserved each result that calls successively, for the generation of subsequent components interface interchange parameter and final return value provides data. |
| ComputeFinalValue | Calculate final return value.According to the transformation rule of receiving from adaptive manager, the data map of preserving the tabulation from OSS/J interface parameters vector sum return value generates final return value. |
The description of transformation rule can be divided into four parts, and is as shown in table 4:
Table 4 transformation rule is described
| Rule is formed | Form and describe |
| DestinationType | Target data type belongs to basic data type, as int, String etc. |
| DestinationValue | Target data values, be the property value of a certain parameter in the component interface, representation such as p1.person.name, wherein p1 refers to first parameter object, person is object properties of this object, and name is a String type attribute of these object properties. |
| SourceType | Source data type belongs to basic data type, as int, String etc. |
| SourceValue | Source data value has two kinds of sources: the return value that the parameter of OSS/J interface and front module are called.Such as, p1.member.name, wherein p1 refers to first parameter object in the parameter vector of OSS/J interface, and member is object properties of this object, and name is a String type attribute of this attribute; R1.company.employee.name, wherein r1 represents the return value of first component call of front, and company and employee are object properties, and name is a String type attribute. |
Data transaction is mainly used the principle of reflection of Java and is carried out.At first, judge between the data type of target and source data and whether can change,, then return the DataTranslationFailed error message if can't change; Then, use reflex mechanism, obtain source data value from SourceValue, and convert it to target data type; At last, the value of using once more after reflex mechanism will be changed is given DestinationValue.
After all parameters that belong to certain component call convert, just generated the parameter list of component interface.Equally, the return value conversion is also carried out according to this principle.The interaction flow of this module and adaptive manager as shown in Figure 7, the implementation procedure of data transaction is as follows:
(1) the recalls information bag is promptly resolved and is preserved in the initialization of the adaptive manager of acceptance, and formation component calls the return value saving sequence;
(2) the component call data transaction information of the adaptive manager of reception, carry out data transaction according to wherein mapping ruler, source data is taken from interface parameter list and the component call return value saving sequence in the recalls information bag, if convert then return the parameter list of generation; Otherwise return error message;
(3) after all data transaction are finished, generate final return value as source data by component call return value saving sequence.
5. component accesses module
The irrelevant function of agreement that the component accesses module is responsible for encapsulating in the invocation component and safety.Its is finished the calling of assembly according to function name that obtains from adaptive manager and relevant parameter, and will call the result and return.
The component accesses module comprises main interface a: invoke (calling), its parameter comprises component class title, class interface title, the tabulation of parameter class and supplemental characteristic list object, its implementation procedure is as shown in Figure 8: at first use reflex mechanism formation component class object, obtain the assembly function by class interface name and the tabulation of parameter class then, be this assembly function of parameter call with the supplemental characteristic list object again, return at last and call the result.During this time, return ComponentClassNotFound if component class does not exist and do not find error message, return ComponentInvocationFailed failure error message if function call is failed.
Because the component register administration module is loaded into the class of assembly of registration in the internal memory, thus the example of these classes can be generated, and utilize reflex mechanism to call the interface of these examples.
6. assembly
Assembly is corresponding one by one with Legacy System, and the otherness of the communication protocol of maskable heterogeneous system, security mechanism and platform converts remote interface to local interface.Assembly is positioned at the bottom of whole integration tool, acts on also comparison basis, comprises two aspects: the preliminary integration of agreement and security mechanism access, Legacy System interface and data.
Agreement inserts by agreement and the security strategy realization identical with pairing Legacy System remote interface is provided with security mechanism, such as, if Legacy System is the Corba interface, then its assembly should adopt the Corba related protocol to insert these remote interfaces, and they are become agreement and the irrelevant local interface of safety.
The preliminary integration of interface and data is on the basis of shielding Legacy System interface protocol and security mechanism, tentatively adjusts the corresponding relation between Legacy System interface and OSS/J interface, Legacy System data and the SID data.The result who integrates is, is the relation of one-to-many between OSS/J interface and the Legacy System interface, and promptly the OSS/J interface can resolve into calling a plurality of Legacy System interfaces; There is the attribute corresponding relation between the data type, promptly can realizes mutual conversion between the data, we can say a kind of intermediate data type of definition by best property of attribute mapping.This integration process is not essential, and purpose is the most basic mapping requirement that reaches between interface and the data.
As shown in Figure 9, the structure of an assembly mainly comprises two parts: Map Profile and component class file.Wherein, the component class file exists with the jar packet form, comprises two types of files: data class file and interface class file.The data class file has comprised used data type in this assembly, and these types can be integrated instrument and use.The interface class file has comprised institute's protocols having and the irrelevant interface of safety, has encapsulated the call relation to long-range Legacy System interface.Map Profile has promptly been described the mapping relations between interface that this assembly provided and the OSS/J interface.
7. component register administration module
The component register administration module provides remote management capability for integration tool, can online registration, maintenance and deletion assembly, and the concrete function that provides is as follows:
(1) registration and charging assembly: at first to the server transmitting assembly bag and the Map Profile thereof of integration tool operation, server dynamic load assembly bag then, and the OSS/J interface described in the Map Profile added in the interface register-file finish component register.
(2) check and revise the configuration file of assembly: the profile list that this module can the display server end, the client can select to check and revise the content of certain configuration file, changes the mapping relations of interface and data with this.Wherein, the interface register-file has been described the OSS/J interface of registering on the integration tool, can stop and activation interface by revising this file; By revising Map Profile, can redefine mapping relations.
(3) deletion and unloading assembly: at first delete corresponding OSS/J interface from the interface register-file, the component class that unloading has loaded from internal memory is deleted Map Profile and assembly bag at last then.The structure of this module as shown in figure 10, top layer is a user interface, realizes in the mode of B/S, can add, check, revise by form web page and delete information such as component profile, assembly bag; The centre is a Business Logic, realizes that additions and deletions change the service logic of looking into; The data access layer of bottom can manage configuration file, and assembly dynamic load assembly can dynamic load assembly bag and class file thereof.
In addition, the present invention does not describe in detail and partly belongs to those skilled in the art's known technology.
The present invention has realized mapping between Legacy System interface and the OSS/J interface and the mapping between Legacy System data and the SID, the standardization of finishing lightweight is integrated, satisfy the uniformity demand of telecom business support system of new generation, be further application layer and integrated interface and the data that standard is provided of process level physical layer interface and data.
What may be obvious that for the person of ordinary skill of the art draws other advantages and modification.Therefore, the present invention with wider aspect is not limited to shown and described specifying and exemplary embodiment here.Therefore, under situation about not breaking away from, can make various modifications to it by the spirit and scope of claim and the defined general inventive concept of equivalents thereof subsequently.
Claims (9)
1, based on the field of telecommunications isomery Legacy System integration tool of collocation strategy, it is characterized in that comprising: OSS/J interface, adaptive manager, configuration file parsing module, data conversion module, component accesses module and assembly, wherein:
The OSS/J interface with the information generation recalls information bag of interface, is given adaptive manager and is finished funcall;
Adaptive manager, it is the maincenter of whole adaptive integrating process, arrange other module and finish integrated logic flow, and coordinate whole adaptation procedure, carry out bidirectional data transfers respectively and between OSS/J interface, component accesses module, data conversion module and the configuration file parsing module, its course of work is: at first, resolve the recalls information bag from the OSS/J interface, the interface name in the bag is resolved and obtained the transitional information of interface and parameter by the configuration file parsing module; Then, described transitional information is offered data conversion module carry out data transaction, promptly be transformed into the data model of assembly from the SID data model of OSS/J interface; At last, finish the corresponding assembly function calls by the component accesses module, and the preservation return value, after adaptive manager is finished all function calls by the component accesses module, obtain final result by the data conversion module parsing and return to the OSS/J interface by adaptive manager;
The configuration file parsing module is responsible for the Map Profile of parsing XML format, according to the standard interface name analysis Map Profile that obtains from adaptive manager, and analysis result is returned to adaptive manager;
Data conversion module, carry out the OSS/J interface data, it is the bi-directional conversion between SID and the module data, it is under the allotment of adaptive manager, the OSS/J interface parameters is converted to the data type of assembly according to the mapping ruler of configuration file, and the return value of data type after the component accesses module invokes is converted to the data type of OSS/J interface, be back to adaptive manager;
The component accesses module is responsible for the agreement and the irrelevant function of safety that encapsulate in the invocation component, and its is finished the calling of assembly according to function name that obtains from adaptive manager and relevant parameter, and will call the result and be back to adaptive manager;
Assembly is positioned at the bottom of whole integration tool, and is corresponding one by one with Legacy System, accepts calling of component accesses module, is used to shield the otherness of communication protocol, security mechanism and the platform of heterogeneous system, converts the Legacy System remote interface to local interface.
2, the field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 1, it is characterized in that: also comprise the component register administration module, this module provides remote management capability, can online registration, maintenance and deletion assembly.
3, the field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 1 and 2, it is characterized in that: the implementation procedure of described adaptive manager is:
(1) parsing is from the recalls information bag of OSS/J interface, the interface name that is wherein comprised, interface return value type and interface parameters vector;
(2) utilize above-mentioned interface name initial configuration document analysis module, if described interface name is registered, then receive the initialization result of true value, initialization result failure is else if then returned error message to invoked OSS/J interface;
(3), and obtain the map information of this OSS/J interface and corresponding assembly interface if the parsing of configuration file parsing module is then passed through in the initialization success;
(4) each component interface to OSS/J interface correspondence calls, at first obtain the parameter transformation rule of this component interface from the configuration file parsing module, give data conversion module and carry out the interface parameters conversion, promptly according to the parameter transformation rule, with the parameter that the result integrates becomes current component interface of calling of the parameter of OSS/J interface and previous component interface; Then, giving the component accesses module with the parameter vector after component interface name and the conversion finishes assembly function and calls; At last, will call the result and hand to data conversion module and preserve, and continue next time that component interface calls;
(5) after adaptive manager is finished all component interfaces and called, obtain the return value transformation rule of described OSS/J interface, and give data conversion module and be converted to final return value, return to invoked OSS/J interface from the configuration file parsing module.
4, the field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 1 and 2 is characterized in that: the implementation procedure of described OSS/J interface:
(1) receives and after call on the upper strata interface name, return value type and interface parameters vector lists are packaged into a recalls information bag;
(2) the recalls information bag is given adaptive manager finish the mapping call;
(3), then return correct interface return value if adaptive manager calls success; Otherwise return malloc failure malloc information.
5, the field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 1 and 2, it is characterized in that: described configuration file parsing module implementation procedure is:
(1) reads the configuration file of adaptive manager, obtain describing the Profile Path of OSS/J interface and its Map Profile corresponding relation, and read this configuration file;
(2) according to the OSS/J interface name analysis configuration file that obtains from adaptive manager, obtain the pairing Map Profile name of this interface;
(3) read and resolve this Map Profile, and, be each assembly function access and generate a list object, the objectification result who resolves is returned adaptive manager each component accesses function parameters objectification.
6, the field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 1 and 2, it is characterized in that: the implementation procedure of described data conversion module is as follows:
(1) preserves the recalls information bag that obtains from adaptive manager;
(2) according to the data conversion rule that obtains from adaptive manager, OSS/J interface parameter list from the recalls information bag and the tabulation of component call return value obtain source data, generate each assembly function parameters list object;
(3) result of each assembly function call is saved in the tabulation of component call return value, for the component call of back provides source data;
(4) after all component calls and finishes,, generate final return value, return to adaptive manager by the tabulation of component call return value according to the final return value create-rule that obtains from adaptive manager.
7, the field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 1 and 2, it is characterized in that: described component accesses module comprises main interface a: invoke, its parameter comprises component class title, class interface title, the tabulation of parameter class and supplemental characteristic list object, its implementation procedure is: at first use reflex mechanism formation component class object, obtain the assembly function by class interface name and the tabulation of parameter class then, be this assembly function of parameter call with the supplemental characteristic list object again, return at last and call the result; During this time, return and do not find error message, if function call is failed then returned the failure error message if component class does not exist.
8, field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 1 and 2, it is characterized in that: described assembly mainly comprises two parts: Map Profile and component class file, wherein the component class file exists with the jar packet form, comprise two types of files: data class file and interface class file, the data class file has comprised used data type in this assembly, these types can be integrated instrument and use, the interface class file has comprised institute's protocols having and the irrelevant interface of safety, has encapsulated the call relation to long-range Legacy System interface; Map Profile has promptly been described the mapping relations between interface that this assembly provided and the OSS/J interface.
9, the field of telecommunications isomery Legacy System integration tool based on collocation strategy according to claim 2, it is characterized in that: described component register administration module concrete function is:
(1) registration and charging assembly: at first to the server transmitting assembly bag and the Map Profile thereof of integration tool operation, server dynamic load assembly bag then, and the OSS/J interface described in the Map Profile added in the interface register-file finish component register;
(2) check and revise the configuration file of assembly: the profile list of this module display server end, the client can select to check and revise the content of certain configuration file, change the mapping relations of interface and data with this, wherein the interface register-file has been described the OSS/J interface of registering on the integration tool, can stop and activation interface by revising this file; By revising Map Profile, can redefine mapping relations;
(3) deletion and unloading assembly: at first delete corresponding OSS/J interface from the interface register-file, the component class that unloading has loaded from internal memory is deleted Map Profile and assembly bag at last then.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710176871A CN100583783C (en) | 2007-11-06 | 2007-11-06 | Integration tool for telecommunication area inheritance system based on configuration policy |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710176871A CN100583783C (en) | 2007-11-06 | 2007-11-06 | Integration tool for telecommunication area inheritance system based on configuration policy |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101188520A CN101188520A (en) | 2008-05-28 |
| CN100583783C true CN100583783C (en) | 2010-01-20 |
Family
ID=39480719
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710176871A Expired - Fee Related CN100583783C (en) | 2007-11-06 | 2007-11-06 | Integration tool for telecommunication area inheritance system based on configuration policy |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100583783C (en) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103188085B (en) * | 2011-12-27 | 2016-06-29 | 中国电信股份有限公司 | Intelligent maintenance method and system based on Enterprise information integration technology |
| CN103581238B (en) * | 2012-07-27 | 2019-04-26 | 中兴通讯股份有限公司 | The unified service platform and service implementation method of ubiquitous network |
| CN102902577B (en) * | 2012-09-28 | 2015-05-27 | 方正国际软件有限公司 | Cross-system service layering processing system in heterogeneous environment |
| CN103023609A (en) * | 2012-11-22 | 2013-04-03 | 用友软件股份有限公司 | Data transmission device and method for heterogeneous systems |
| CN104063209B (en) * | 2013-03-22 | 2018-05-04 | 上海联影医疗科技有限公司 | A kind of heterogeneous system integration method and apparatus of facing area medical treatment |
| KR102578553B1 (en) | 2015-12-10 | 2023-09-13 | 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 | Data-Driven Automated Provisioning for Telecommunications Applications |
| US10129769B2 (en) | 2015-12-31 | 2018-11-13 | Affirmed Networks, Inc. | Adaptive peer overload control in mobile networks |
| WO2017123845A1 (en) | 2016-01-15 | 2017-07-20 | Affirmed Networks, Inc. | Database based redundancy in a telecommunications network |
| CN105760196B (en) * | 2016-02-18 | 2019-04-30 | 福建天晴数码有限公司 | The detection method and system of plug-in unit plug-in program |
| CN106407797B (en) * | 2016-09-08 | 2020-01-07 | 努比亚技术有限公司 | Application authority control device and method |
| CN107798617B (en) * | 2017-04-07 | 2021-04-13 | 平安科技（深圳）有限公司 | Insurance business processing method and device |
| CN109240683A (en) * | 2018-07-13 | 2019-01-18 | 中建三局第二建设工程有限责任公司 | The bus architecture computer programming designing system and method for modular applications service |
| CN109408123B (en) * | 2018-10-10 | 2021-08-24 | 聚好看科技股份有限公司 | Method and device for reloading configuration file |
| CN109598505B (en) * | 2018-10-31 | 2020-05-19 | 阿里巴巴集团控股有限公司 | Quality data processing method and device based on block chain |
| CN113396393A (en) | 2019-01-15 | 2021-09-14 | 微软技术许可有限责任公司 | Dynamic auto-configuration of multi-tenant PAAS components |
| CN111917755B (en) * | 2020-07-24 | 2022-11-15 | 群硕软件开发(上海)有限公司 | Dynamic data integration method based on configuration |
| CN113411203B (en) * | 2021-05-14 | 2022-12-20 | 深圳市广和通无线股份有限公司 | Terminal configuration method and device, computer equipment and storage medium |
-
2007
- 2007-11-06 CN CN200710176871A patent/CN100583783C/en not_active Expired - Fee Related
Non-Patent Citations (4)
| Title |
|---|
| Service-Oriented Business Integration and Management inTelecom. Xinyu Wang,Jianchu Kang.IEEE,Vol.2 . 2005 |
| Service-Oriented Business Integration and Management inTelecom. Xinyu Wang,Jianchu Kang.IEEE,Vol.2 . 2005 * |
| 面向电信运营管理的中间件平台的研究与实现. 余继光，康建初.计算机工程与应用，第15期. 2005 |
| 面向电信运营管理的中间件平台的研究与实现. 余继光，康建初.计算机工程与应用，第15期. 2005 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101188520A (en) | 2008-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100583783C (en) | Integration tool for telecommunication area inheritance system based on configuration policy | |
| CN100401288C (en) | Distributed data source data integration system and method | |
| CN101741850B (en) | Multitask concurrent executive system and method for hybrid network service | |
| CN101826987B (en) | System and method for supporting mixed service based on integrated open network | |
| CN102053860B (en) | CORBA-based OSGi distributed extensible system and method | |
| CN101655943B (en) | Enterprise application integrated working flow management method and system | |
| US20080120600A1 (en) | Exchange Infrastructure System and Method | |
| CN107203376A (en) | A kind of enterprise-level information system | |
| CN100479551C (en) | Universal service system and its implementation method | |
| CN102968307B (en) | A kind of web based on java develops middleware | |
| CN103902286A (en) | Hierarchy type multi-source data fusion method based on SOA | |
| CN101605141A (en) | Web service relational network system based on semanteme | |
| WO2002086679A2 (en) | Service provision system and method | |
| CN101232626A (en) | Business supporting system and method based on business events developing platform | |
| CN102523200A (en) | Internet of things information processing method | |
| CN104636329A (en) | Unified management method for large-scale cross-platform heterogeneous data | |
| CN102402507A (en) | Heterogeneous data integration system for service-oriented architecture (SOA) multi-message mechanism | |
| CN105721562A (en) | Proxy-based heterogeneous service calling method and collaborative calling system | |
| CN103268230A (en) | Method used for constructing cloud computing information management platform capable of expanding service | |
| CN107656951A (en) | A kind of method of real time data in synchronous and heterogeneous Database Systems | |
| CN1972276B (en) | A management method and system for protocol access | |
| CN102984272B (en) | A kind of system of remote control mobile terminal communication capacity and method thereof | |
| Dai | Design and implementation of ESB based on SOA in power system | |
| CA2481099C (en) | Exchange infrastructure system and method | |
| CN100466554C (en) | Communication adaptation layer system and method for obtaining the network element information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100120 Termination date: 20121106 |