CN100527735C - Adapter - Google Patents
Adapter Download PDFInfo
- Publication number
- CN100527735C CN100527735C CNB2004100884013A CN200410088401A CN100527735C CN 100527735 C CN100527735 C CN 100527735C CN B2004100884013 A CNB2004100884013 A CN B2004100884013A CN 200410088401 A CN200410088401 A CN 200410088401A CN 100527735 C CN100527735 C CN 100527735C
- Authority
- CN
- China
- Prior art keywords
- service
- adapter
- message
- title
- module
- 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
This invention relates to an adapter including: a service issuing module analyzing the service description file of XML form generated by a service component of a left system, which describes the service provided by the left system, the related position information to said service and interface parameter, a register module for fetching and analyzing the description file of the adapter and service description file of the left system and registering them to the information bus of a newly developed platform, a message process module processing messages according to the transmission protocol, a service call module used in analyzing and calling SOAP massage block to locate the being called service based on the service call file generated by the service issuing module and feed back the result to the message module in the way of SOAP message block to realize the interaction between the left system and the operation platform.
Description
Technical field
The invention belongs to Application Middleware platform category, particularly a kind of adapter.
Background technology
Adapter mainly is to utilize middleware Technology, between the functional unit of Legacy System and support platform, increase an adapter intermediate layer, by adapter layer data, function and the agreement of Legacy System are unified to describe, provide unified access interface to management platform, thereby the difference of visiting mutually between the shielding Legacy System reaches the purpose of carrying out interoperability between the different system.
Flourish along with communication network and technology, China's telecommunications industry have changed over to gradually from networking stage of high speed development and have pursued the good operation management stage that network quality guaranteed and can provide multiple business.Telecom operators adopt multiple telecom operation management application software to provide various service for the user.Therefore, the telecom operation of the telecommunication administration software system function that foundation can integrated a plurality of isomeries management support platform is very necessary.
Summary of the invention
The objective of the invention is to, in order to have solved telecom operation management support platform isomerism problem of visit and data sharing mutually in the integrated existing telecommunications application software system of leaving over, thereby provide a kind of adapter, to integrate and integrated existing telecommunications Legacy System.
The adapter that technical scheme of the present invention provided is used to realize mutual between Legacy System and the platform newly developed, and described adapter comprises service release module, Registering modules, message processing module and service calling module;
Described service release module, be used to resolve the service description file that the Legacy System Service Component generates corresponding XML (Extensible Marked Language) form, this description document describe service that Legacy System can provide and with this service relevant location information and interface parameters;
Described Registering modules is used to read and the description document of resolution adapter and the service description file of Legacy System, and the log-on message of the adapter that parsing is obtained and the information on services of Legacy System are registered on the messaging bus of platform newly developed;
Described message processing module, be used for according to the host-host protocol processing messages, resolve on the messaging bus message with JMS (Java Messaging Service) agreement or HTTP (HyperText TransferProtocol) protocol transmission and obtain calling the soap message body that calls the result that SOAP (Simple Object Access Protocol) message body and packing service calling module return;
Described service calling module is used for resolving and calls the soap message body, and according to the service description file that the service release module generates, the service that the location will be called also will be called the result and return to message processing module with the form of soap message body.
Described service release module generates service description file by resolving the program code of Legacy System Service Component.
The type and the title of the title of the title of the service that described service description file is provided with XML format description functional unit, service call type, the pairing class of service and the type that parameter is imported in relative position, service into and title, return parameters.
Described service registry module comprises the service registry module of the Registering modules and the Legacy System of adapter.
The log-on message of described adapter comprises adapter title (adapterName), adapter IP address (addr), type of adapter (type), adapter-num (adapterId), service profiles (Server_Config_file).
The service registry information of described Legacy System comprises the supplemental instruction of the title of service, the WSDL of service (Web Service Description Language) file position, service, the title of the adapter under the service.
Described message processing module is used to intercept the message of transmitting from JMS agreement or http protocol on the bus and return and call the result, and it comprises message parse unit and message encapsulation unit;
According to the transmission format protocol of messaging bus, selects corresponding processing mode that message is resolved and obtain to call the soap message body, and recording messages is originated simultaneously in described message parse unit;
Described message encapsulation unit, transmission format protocol according to messaging bus, the soap message body encapsulation of calling the result that service calling module is returned generates message, according to the above-mentioned informed source that writes down, by messaging bus this message is sent to and to initiate the corresponding service assembly call or the associated components corresponding location of platform.
Described interface parameters comprises: the title and the type of input parameter in the title of the method in the class title of the service that call, the service, the method.
As depicted in figs. 1 and 2, Legacy System or assembly newly developed (at this, being referred to as Service Component) are connected to the messaging bus of platform by adapter, and mutual by other functional part of messaging bus and platform.Here, the work of adapter comprises two aspects, and work is that the function register of each Service Component is inquired about for other assemblies to messaging bus on the one hand; Be the recalls information of processing messages bus on the other hand, and return to Legacy System and to call the result the Legacy System Service Component.
Wherein, the service release module is resolved the function of Legacy System Service Component, generates to have the service description file of XML form accordingly.Registering modules reads adapter arrangement file and analysis service description document, with Adapter Information with and the information on services of the Service Component that connects be registered on the messaging bus, wait for then receiving the recalls information that transmits on the bus.Like this, other Service Component on the platform can be found the service that the Service Component of adapter connection provides by log-on message.In case when having SOAP information to pass to adapter on the bus, message processing module is resolved the content of message, obtain and call the necessary interface parameters of service, and send these information to service calling module.Service calling module is according to the interface parameters analysis service description document that transmits, and the position of service in the Legacy System Service Component positioned and call it.At last, the result that message processing module returns service calling module is packaged into bus and can transmits and discernible soap message, returns to messaging bus.
Because the messaging bus of platform adopts multiple transport protocols to carry out transmission of messages usually, as JMS or http protocol etc., so adapter need possess the function that these host-host protocols are disposed voluntarily, so that make bus can adapt to the needs of differing transmission protocols.In addition, because each Legacy System may use the different language exploitation, in order to shield each Legacy System at the stylistic isomerism of message transfer, the message of transmitting on the messaging bus adopts the soap message form more, so, adapter needs by Legacy System being issued and operation such as parsing, so that realize the different disposal method and the unified of processing protocol of the isomeric data of Legacy System are described, finally realizes integrated to Legacy System.
The invention has the advantages that, the present invention adopts adapter technique to shield the difference of heterogeneous system on data, method and agreement, carry out integrated and integration to Legacy System, mutual visit and cooperation between the heterogeneous system have been realized, the plug and play and dynamic discovery of sharing and supporting Service Component newly developed of isomery information are realized the intercommunication between Legacy System and the operation platform.The present invention need also to can be applicable in the other industry that the system integration and heterogeneous system visit mutually.
Description of drawings
Fig. 1 is applied to the architecture of telecom operation management platform for the present invention
Fig. 2 is the structural representation of adapter of the present invention
Fig. 3 is the workflow diagram of the service release module of adapter of the present invention
Fig. 4 is the workflow diagram of the Registering modules of adapter of the present invention
Fig. 5 is the workflow diagram of the message resolution module of adapter of the present invention
Fig. 6 is the workflow diagram of the forwards of adapter of the present invention
Fig. 7 is the workflow diagram that soap message is resolved that calls of adapter of the present invention
Fig. 8 is the workflow diagram that the SOAP of the return messages of adapter of the present invention encapsulates
Embodiment
Be that example is described adapter of the present invention with telecom operation management support platform below.
This adapter mainly is to utilize middleware Technology, between Legacy System or functional unit and support platform, increase an adapter intermediate layer, by adapter layer data, function and the agreement of Legacy System are unified to describe, provide unified access interface to management platform, thereby the difference of visiting mutually between the shielding Legacy System reaches the purpose of carrying out interoperability between the different system.
As shown in Figure 2, adapter mainly is made up of service release module, service calling module, message processing module, four parts of Registering modules, and the function of each several part and working mechanism can be described below:
1, service release module
The service release module generates its service profiles by resolving the program code of Legacy System Service Component.Service profiles is described as the file of XML form.But the type of the title of the title of the service that file representation function assembly is provided, service call type, the pairing class of service and the type that parameter is imported in relative position, service into and title, return parameters and title etc.
It is as follows that service profiles is described segment:
<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>
<deployment?xmlns＝http://xml.apache.org/axis/wsdd/
xmlns:java＝＂http://xml.apache.org/axis/wsdd/providers/java＂>
<servicename＝＂FaultdispatchSessionFacadeTestClient4＂
provider＝＂java:RPC＂>
<parameter?name＝＂allowedMethods＂value＝＂faultsDispatch＂/>
<parameter?name＝＂scope＂value＝＂Request＂/>
<parameter?name＝＂className＂
value＝＂pjt_dispatch_fault.FaultdispatchSessionFacadeTestClient4＂/
>
<typeMapping
deserializer＝＂org.apache.axis.encoding.ser.BeanDeserializerFactory＂
encodingStyle＝http://schemas.xmlsoap.org/soap/encoding/
qname＝＂nsl:Status＂
serializer＝＂org.apache.axis.encoding.ser.BeanSerializerFactory＂
type＝＂java:pjt_dispatch_fault.Status＂
xmlns:nsl＝＂http://pjt_dispatch_fault＂/>
</service>
</deployment>
Wherein, servicename represents the title of serving, the concrete grammar during allowedMethods represents to serve, and scope represents call type, className represents to serve the position at pairing specific procedure place, and typeMapping represents to import in the method for servicing type of parameter and return value.
As shown in Figure 3, adapter is at first determined the position at Legacy System place by the Legacy System location parameter of input, resolves the Legacy System of assigned address then.In the resolving,, parsing generates service description file according to the content of resolving if passing through; If owing to positional information is made mistakes or the reason of Legacy System itself causes and resolves failure, then adapter can be quoted corresponding error and prompting is resolved again.
2, Registering modules
Registering modules is mainly used in the service that adapter and Legacy System Service Component are provided and registers.Registering modules with Adapter Information with and the information on services of the functional unit hung down be registered on the messaging bus, so that other Service Component can be by these information on the inquiry bus, obtain the positional information and the interface message of required service, thereby related service is called.
2.1 adapter registration
The adapter Registering modules registers Adapter Information to messaging bus.Log-on message mainly comprises adapter title (adapterName), adapter IP address (addr), type of adapter (type), adapter-num (adapterId), service profiles (Server_Config_file).The title of adapter can freely be named according to relevant regulations; Adapter IP address is meant the IP address of the machine that adapter moves; It is the adapter of which kind of type that the type of adapter is used for describing, and for example, is CORBA/SOAP adapter or EJB/SOAP adapter etc.; Type of adapter depends primarily on the implementation language and the implementation of Legacy System; Adapter-num is mainly used to adapter of unique identification, so that for platform or the inquiry of other functional units; The service profiles position attribution is used to describe the position of service profiles.Above-mentioned Adapter Information all reads from the adapter arrangement file, and the adapter arrangement file is as follows:
adapterName＝yujiguang
addr＝192.168.6.188
type＝EJB/soap
adapterId＝00001
Server_Config_file＝server-config-locate.wsdd
The adapter registration mainly realizes that by registration adapter (registerAdapter) method of calling in the Registering modules this method comprises three parameters, is respectively adapter title, adapter IP address, type of adapter, and these three parameters are character type.The return value of this method is Adapter Information (AdapterInfo) type, adapter title (adapterName) parameter of importing into when the type mainly comprises by the connection factory (connectionFactory), name and the directory service factory (jndiFactory) that obtain of registration adapter, JMS address (jmsUr1), request queue (requestQueue), adapter-num (adapterId) and registration.By obtaining these parameters, the messaging bus of platform can be set up message channel with adapter, can pass through the concrete message content of this channel transfer.The successful foundation of passage shows that adapter is articulated on the platform.
2.2 service registry
The service registry module is registered the information on services of the Legacy System Service Component that adapter inserts to messaging bus, so that make platform or other Service Component can find and call these services, platform can carry out unified management to these services simultaneously.The service registry information spinner will be by the service profiles record of analysis service.Service profiles generates in the service release module.Service registry information comprises the supplemental instruction of the title of service, the WSDL of service (Web Service DescriptionLanguage) file position, service, the title of the adapter under the service.Bus manages and controls by the service of these information to adapter access function assembly.
Realize that the service registry module is mainly by calling service registry (registerService (the SvcIf)) method in the Registering modules.This method is imported the parameter of an information on services (ServiceInfo) type into to messaging bus, this structure mainly comprises service name (serviceName), remarks (comment), wsd1 document location (wsd1), these several projects of affiliated adapter title (adapterName), wherein serviceName is the title of service, comment refers to the related description to this service, wsdl is meant the residing position of the wsdl document of service, and adapterName is meant the title of the adapter under this service.Whether the return value of this interface is a Boolean type, successful to judge service registry.
As shown in Figure 4, at first carry out the adapter registration, earlier read Adapter Information from the adapter arrangement file, then call adapter registration interface adapter registration (registerAdapter) method, the Adapter Information that will read from configuration file is as call parameters.If malloc failure malloc is then quoted corresponding mistake and gone back to and reads the configuration file step and restart,, then carry out service registry if call success.When carrying out service registry, at first to read service description file, therefrom read service description information, then call service registry interface service registration (registerService (SvcIf)) method, with service description information as call parameters.If malloc failure malloc is then quoted corresponding mistake and is gone back to and reads the service description file step and restart.If call success, then service registry flow process finishes.After above register flow path was finished, adapter was just intercepted bus the zero hour, once there is the SOAP message call to transmit calling of just can serving.
3, message processing module
The message processing module of adapter mainly provides and carries out mutual interface between adapter and the messaging bus, intercepts the message from bus simultaneously, and returns and call the result.Message processing module mainly contains message parse and message encapsulation two big functions; Can accept and identification bus on the message of JMS agreement or http protocol transmission.
3.1 message parse
Message resolution module selects corresponding processing mode that message is resolved according to the difference of the host-host protocol of message, to obtain the soap message body, goes back the source of recording messages simultaneously, so that can finish the back and return to message source and call the result calling.
As shown in Figure 5, message processing module at first obtains the service invocation message that bus transfer is come, and then message is analyzed, and judges the type of the host-host protocol of message, simultaneously the source of recording messages.If analytic target is with JMS agreement message transmitted, then call JMS message parse program, obtain the soap message body in the JMS message.If the message of http protocol transmission is then called the soap message body in the HTTP analysis program acquisition HTTP message.Message processing module sends the soap message body that is obtained to service calling module in order to calling.
3.2 forwards
After service call finishes, the result that service calling module is returned is sent to message processing module, message processing module encapsulates return results according to the transmission format protocol of bus, and according to the record of front informed source, sends a message to the corresponding location by messaging bus.So, the initiator of service call can obtain return results easily.
As shown in Figure 6, message processing module at first obtains the soap message that calls the result that has that service calling module returns, and the informed source that writes down before reading, the soap message that will have a return results according to the transmission format protocol of bus is encapsulated in the corresponding host-host protocol then, at last packaged message is sent on the messaging bus.Messaging bus sends to return results according to informed source and initiates the corresponding service assembly call or the associated components of platform.
4, service calling module
Service calling module is mainly resolved the service call soap message that message processing module obtains, and analysis result is reached service calling module, finishes final service call by service calling module; After obtaining return results simultaneously, end value is packaged into soap message returns to message processing module.Service calling module is mainly finished to the parsing of the soap message of the service of calling and to two functions of the SOAP of return results encapsulation.
4.1 call the parsing of soap message
Service calling module is resolved the service call soap message that message processing module obtains, and obtains following service call parameter: 1. the class title of the service that will call; 2. the title of the method in serving; 3. the title of input parameter and type in the method.In resolving, if call parameters is a compound type, then must carry out unserializing, if simple types then can directly be resolved to compound type.Module will be resolved the above-mentioned information that obtains and be passed to service calling module, and service calling module just can be according to these information, and the concrete grammar of the service that call is positioned, and finish final service call.It is as follows to call the soap message example:
<soapenv:Envelope
xmlns:soapenv＝＂http://schemas.xmlsoap.org/soap/envelope/＂
xmlns:xsd＝＂http://www.w3.org/2001/XMLSchema＂
xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>
<soapenv:Body>
<nsl:startRequest
soapenv:encodingStyle＝＂http://schemas.xmlsoap.org/soap/encoding/＂
xmlns:nsl＝＂DPRequestEJB＂/>
</soapenv:Body>
</soapenv:Envelope>
As shown in Figure 7, service calling module at first obtains the SOAP message call that message processing module transmits, next message is resolved and obtain to import into parameter, if contain multiple type in the parameter then compound type carried out unserializing, passing to calling module, pass to calling module if simple types then directly saves, call service by calling module, and return and call the result.
4.2 the SOAP of return messages encapsulation
After calling end, service calling module will be called return results and return to messaging bus with the form of soap message, for this reason, need will carry out the SOAP encapsulation to the result who returns, and encapsulation is finished by service calling module.
May there be two kinds of situations in return results, and a kind of is that return results is the data of simple types, and as character type or integer, at this moment, the type of SOAP encapsulation is fairly simple, only needs to indicate in soap message return value title, return value type and concrete value.If return results is a compound type, as structure or array, in the case, service calling module need indicate the title of structure in the return value, the title of each simple types, type, value in the structure, and these types and value are carried out serializing.Concrete coding rule is followed the SOAP coding rule of standard, and the coding example of compound type soap message is as follows:
<？xml?version＝”1.0”encoding＝”UTF-8＂？>
<soapenv:Envelopexmlns:soapenv＝＂http://schemas.xmlsoap.org/soap/
envelope/＂ xmlns:xsd＝＂http://www.w3.org/2001/XMLSchema＂
xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>
<soapenv:Body>
<nsl:queryFaultsResponsesoapenv:encodingStyle＝＂http://schemas.xm
lsoap.org/soap/encoding/＂
xmlns:nsl＝＂FaultquerySessionFacadeTestClient2＂>
<nsl:queryFaultsReturnhref＝＂#id0＂/>
</nsl:queryFaultsResponse>
<multiRefid＝＂id0＂soapenc:root＝＂0＂
soapenv:encodingStyle＝＂http://schemas.xmlsoap.org/soap/encoding/＂
xsi:type＝＂ns2:FaultsList＂xmlns:soapenc＝＂http://schemas.xmlsoap.org/soap
/encoding/＂xmlns:ns2＝＂http://pjt_query_fault＂>
＜DeviceFaultListxsi:type=＂ xsd:string ＂〉2004-3-270:00:00:: big fortune
The village:: TRH:: universiade village base station equipment:: shenzw::＜/DeviceFaultList 〉
＜TransportationFaultListxsi:type=＂ xsd:string ＂〉the big fortune of 2004-3-230:0
The village::＜/TransportationFaultList 〉
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
Service calling module sends to message processing module with packaged soap message body as the semantic description agreement, and message processing module just can send on the bus after according to the set host-host protocol of bus the soap message body being encapsulated.
As shown in Figure 8, after service calling module obtains return results, judge that at first return value gets type, if the result is a compound type, then call compound type is carried out serializing, then, calling module is packaged into the soap message body to return value, pass to message processing module at last and carry out the encapsulation of host-host protocol, if the result is a simple types, then call service calling module and directly resolve encapsulation and generate SOPA message body, and finally pass to the encapsulation that message processing module carries out host-host protocol.
Heterogeneous system integrated adapter technology of the present invention, it is a kind of general adaptation technique, its realization and operation and concrete application there is no direct relation, a above-mentioned application example that only is it at field of telecommunications, in fact it not only can be used for field of telecommunications and also can be used for other and need in the middle of the sector application that the system integration and heterogeneous system visit mutually.
Claims (7)
1, a kind of adapter, this adapter are used to realize mutual between Legacy System and the platform newly developed it is characterized in that described adapter comprises service release module, Registering modules, message processing module and service calling module;
Described service release module is used to resolve the Legacy System Service Component generating the service description file of corresponding XML form, and this service description file is described service that Legacy System can provide and positional information and the interface parameters relevant with this service;
Described Registering modules is used to read and the description document of resolution adapter and the service description file of Legacy System, and the log-on message of the adapter that parsing is obtained and the information on services of Legacy System are registered on the messaging bus of platform newly developed;
Described message processing module, be used for according to the host-host protocol processing messages, resolve the message of transmitting with JMS agreement or http protocol on the messaging bus, obtain calling the soap message body, to call the soap message body and send service calling module to, and the soap message bodily form formula returned of packing service calling module call the result, generate information and sending to messaging bus;
Described service calling module is used for resolving and calls the soap message body, and according to the service description file that the service release module generates, the service that the location will be called also will be called the result and return to message processing module with the form of soap message body.
According to the described adapter of claim 1, it is characterized in that 2, described service release module generates service description file by resolving the program code of Legacy System Service Component.
3, according to the described adapter of claim 1, it is characterized in that the type and the title of the title of the title of the service that described service description file is provided with XML format description Legacy System, service call type, the pairing class of service and the type that parameter is imported in relative position, service into and title, return parameters.
According to the described adapter of claim 1, it is characterized in that 4, the log-on message of described adapter comprises adapter title, adapter IP address, type of adapter, adapter-num, service profiles.
According to the described adapter of claim 1, it is characterized in that 5, the information on services of described Legacy System comprises the supplemental instruction of the wsdl document position of the title of service, service, service, the title of the adapter under the service.
6, according to the described adapter of claim 1, it is characterized in that, described message processing module be used to intercept from the message of JMS agreement or http protocol transmission on the bus and return encapsulation soap message bodily form formula call the result, described message processing module comprises message parse unit and message encapsulation unit;
According to the transmission format protocol of messaging bus, selects corresponding processing mode that message is resolved and obtain to call the soap message body, and recording messages is originated simultaneously in described message parse unit;
Described message encapsulation unit, transmission format protocol according to messaging bus, the result that calls of the soap message bodily form formula that service calling module is returned encapsulates generation message, and according to the informed source that is write down, the message that described encapsulation is generated sends to the corresponding service assembly that initiation is called by messaging bus.
According to the described adapter of claim 1, it is characterized in that 7, described interface parameters comprises: the title and the type of input parameter in the title of the method in the class title of the service that call, the service, the method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100884013A CN100527735C (en) | 2004-10-29 | 2004-10-29 | Adapter |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100884013A CN100527735C (en) | 2004-10-29 | 2004-10-29 | Adapter |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1767530A CN1767530A (en) | 2006-05-03 |
| CN100527735C true CN100527735C (en) | 2009-08-12 |
Family
ID=36743136
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100884013A Expired - Fee Related CN100527735C (en) | 2004-10-29 | 2004-10-29 | Adapter |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100527735C (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103944902B (en) * | 2010-08-13 | 2017-11-24 | 华为技术有限公司 | Realize the method, apparatus and equipment of business polymerization Mashup business |
| CN102571550B (en) * | 2010-12-30 | 2016-05-25 | 北京亿阳信通科技有限公司 | A kind of general information exchange platform and method |
| CN102811199B (en) * | 2011-05-30 | 2015-10-28 | 深圳市金蝶友商电子商务服务有限公司 | A kind of method for interface adaptation, Apparatus and system |
| CN103428019A (en) * | 2012-05-24 | 2013-12-04 | 中兴通讯股份有限公司 | Network service message management method and system |
| CN104753860B (en) * | 2013-12-27 | 2019-06-28 | 上海宝信软件股份有限公司 | Network service system based on middleware |
| CN104808973A (en) * | 2014-01-24 | 2015-07-29 | 阿里巴巴集团控股有限公司 | Screen shooting system and method |
| CN109388591B (en) * | 2017-08-07 | 2021-07-16 | 北京北斗星通导航技术股份有限公司 | MATLAB application system and STK application system interface adapter and adaptation method |
| CN113051202A (en) * | 2019-12-27 | 2021-06-29 | 中国移动通信集团湖南有限公司 | Interface adaptation method, device, electronic equipment and computer readable storage medium |
| CN111478945B (en) * | 2020-03-13 | 2022-10-14 | 国家电网有限公司 | Pumped storage operation and inspection data processing system and method |
| CN112181516A (en) * | 2020-09-24 | 2021-01-05 | 武汉深之度科技有限公司 | Application software execution method and computing device |
-
2004
- 2004-10-29 CN CNB2004100884013A patent/CN100527735C/en not_active Expired - Fee Related
Non-Patent Citations (2)
| Title |
|---|
| 新一代电信业务支撑系统软件体系结构的研究. 杨娟，张雷，王柏，艾波.北京邮电大学学报，第26 增刊卷. 2003 * |
| 新一代运营支撑系统体系结构. 孔令萍.中兴通讯技术，第3期. 2003 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1767530A (en) | 2006-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6757899B2 (en) | Dynamic CORBA gateway for CORBA and non-CORBA clients and services | |
| CN102571550B (en) | A kind of general information exchange platform and method | |
| US7774477B2 (en) | Peer networking host framework and hosting API | |
| EP2765756A1 (en) | Service configuration method and device | |
| JP2006504297A (en) | Service access gateway | |
| CN100527735C (en) | Adapter | |
| US8230448B2 (en) | Methods, systems and computer program products for web service interaction with a resource management system | |
| CN101167327A (en) | System and method for accessing multiple data sources by mobile applications | |
| CN101557426A (en) | Web service-based and uniformly managed interface message processor, web service component and method thereof | |
| US20020069262A1 (en) | Extendable provisioning mechanism for a service gateway | |
| CN100405760C (en) | Method and system for providing web services from a service environment with a gateway | |
| KR100601023B1 (en) | Integrated communication server and method | |
| JP2005196772A (en) | Apparatus and method for sharing service on network | |
| AU766949B2 (en) | A smart molecule system for processing network information in any physical object | |
| US20020069257A1 (en) | Provisioning mechanism for a service gateway | |
| CN103391294A (en) | Remote method invocation based on service description | |
| KR100758791B1 (en) | Proxy Apparatus and the Method for Homenetwork device control | |
| JP5081888B2 (en) | Method port apparatus and configuration method for robot software components | |
| CN115509647A (en) | API (application program interface) access method, conversion method, device, equipment and storage medium | |
| CN114615321A (en) | Traffic processing method and device | |
| CN112929454A (en) | Heterogeneous service interoperation method and device | |
| CN111552737A (en) | Zookeeper-based multi-source data wide-area access system and method | |
| CN111865746B (en) | System development method and device based on loop bus | |
| JP2001265747A (en) | Distributed object linking device | |
| Lee et al. | General middleware bridge to support device interoperability on different middlewares |
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: 20090812 Termination date: 20111029 |