CN103117983A - Data service request response method and data service protocol stack - Google Patents
Data service request response method and data service protocol stack Download PDFInfo
- Publication number
- CN103117983A CN103117983A CN2011103628786A CN201110362878A CN103117983A CN 103117983 A CN103117983 A CN 103117983A CN 2011103628786 A CN2011103628786 A CN 2011103628786A CN 201110362878 A CN201110362878 A CN 201110362878A CN 103117983 A CN103117983 A CN 103117983A
- Authority
- CN
- China
- Prior art keywords
- data
- service
- packet
- layer
- protocol stack
- 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.)
- Granted
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention discloses a data service request response method and a data service protocol stack, wherein the method comprises the steps that a service requester encapsulates a service index parameter into a simple object access protocol (SOAP) data packet, and the service requester sends the encapsulated SOAP data packet to a service provider to enable the service provider to obtain an service query order and service data from the database after conducting analysis processing to the SOAP data packet or a hyper text transport protocol (HTTP) data packet. The data service request response method and the data service protocol stack can not only achieve the decoupling of application and data, but also achieve the decoupling inside the data service to enable the details inside the data service to be simpler, more effective, clearer, more flexible and extensible.
Description
Technical field
The present invention relates to service operation support technology in the communications field, particularly, relate to method and data, services protocol stack that data service request is replied.
Background technology
Present a lot of large enterprises have all come into effect SOA (Service-Oriented Architecture, Service-Oriented Architecture Based) as the enterprise of the industries such as communication, finance.SOA provides a kind of standard and method of the IT of structure tissue, capable of being combined by setting up, reusable service system reduces the IT business redundancy, and the process of quickening project development, the SOA system can make that IT department efficient is higher, the construction cycle is shorter, the project distribution is faster, is assisting aspect IT technology and business integration, higher value is being arranged.
One of key content in the SOA implementation process is the realization of data, services, and data, services can realize high cohesion, the loose coupling of software as the technology of application with data decoupler, can improve the reusing degree of software.
Existing industry mainly contains the technology such as EJB, CORBA, DCOM and Web Service aspect the realizing of data, services, wherein that popular is Web Service.Web Service is Application standard, XML standard describes interface, describes with service and carries out mutual needed full details, comprises message format, host-host protocol and service position; And hidden the details that service realizes in external interface, only provide a series of executable operations, the programming language that this operation is independent of hardware and software platform and the service of writing is used.The architecture of Web Service is mutual based between service register center, service requester (being service requester) and ISP's (being service provider) Three role mainly, as shown in Figure 1.
The relating generally to alternately issue, search and bindings of Three role, the ISP defines the service describing of Web service and it is published to service register center, service requester uses search operation from this locality or the service register center retrieval service is described, and then uses service describing and ISP to bind and called Web service.
Application number is management method and the system that 201010616910.4 Chinese patent application has been introduced a kind of Web Service service, comprising: the webserver obtains the authenticating user identification request that client sends; Described authenticating user identification request comprises: customer digital certificate and user's ID authentication information; The described webserver is transmitted to authentication center with the authenticating user identification request that it gets, so that described authentication center authenticates the described webserver and user identity; After described authentication center completed authentication, the described webserver received the authentication result that described authentication center returns; According to described authentication result, the described webserver is that described client is provided services on the Internet.Present patent application can improve the fail safe of Web Service, and whether user and the owner that can also effectively solve the checking digital certificate are the problems of same entity.
Application number discloses a kind for the treatment of system and method that data, services is provided for 200910167170.8 Chinese patent application, comprise: after receiving user's the service request that data, services is provided, when needs call external interface, based on the position of calling external interface, business is split as initial logic business and subsequent logic business; The initial logic business is processed, and returned to segmentation response result to Reverse Proxy; Reverse Proxy is according to the request call external interface of segmentation response results; After the external interface that calls returns to response results, with the segmentation response results with call the response results that external interface returns and be integrated into the data, services result that offers the user; To user's return data service result.Present patent application can avoid front end logic to get clogged, and makes front end services can process continuously new request and need not lose time in the response of waiting for external service request.
On the whole, although above-mentioned existing scheme can solve the problem of implementation of Web Service data, services to a certain extent, but realize mainly for the service interface aspect, the inside that can not be deep into data, services realizes that details carries out normalized illustration, make the inside of data, services realize to obtain sufficient decoupling zero and multiplexing, cause the inside of data, services to realize more complicated, affect the implementation efficiency of data, services.
Summary of the invention
The objective of the invention is to propose a kind of data service request answer method and data, services protocol stack for the lower defective of the implementation efficiency of data, services in prior art.
For achieving the above object, according to an aspect of the present invention, provide a kind of data service request method.
Data service request method according to the embodiment of the present invention comprises:
Service requester is encapsulated into SOAP packet or HTTP packet by presentation layer, session layer, service layer and the interface layer of data, services protocol stack with the service indication parameter;
SOAP packet after service requester will encapsulate or HTTP Packet Generation are to service provider, so that service provider carries out SOAP packet or HTTP packet to obtain the service-seeking instruction after dissection process, obtain service data in database.
In technique scheme, service provider is resolved rear acquisition service-seeking instruction with SOAP packet or HTTP packet, and the step of obtaining service data in database comprises: service provider is resolved rear acquisition service indication parameter by interface layer, service layer, session layer and the presentation layer of data, services protocol stack to SOAP packet or HTTP packet;
Model Mapping layer and the articulamentum of service provider by the data, services protocol stack forms the service-seeking instruction according to the service indication parameter and is submitted in database and carries out, and obtains service data in database.
In technique scheme, the step that the service indication parameter is encapsulated into SOAP packet or HTTP packet comprises:
UI Layer Wrapper with the service indication parameter by the data, services protocol stack becomes extensible markup, initiates a session request according to the type of interaction of the service session layer by the data, services protocol stack;
Service layer by the data, services protocol stack is encapsulated into extensible markup in the inclusion of SOAP packet or HTTP packet;
Interface layer by the data, services protocol stack carries out the encapsulation operation of service release, route, request source and authentication to the packet header of SOAP packet or HTTP packet.
In technique scheme, the service indication parameter is encapsulated into the step of SOAP packet or HTTP packet and will encapsulate after the SOAP packet or the step of HTTP Packet Generation to service provider between also comprise: the interface layer by the data, services protocol stack carries out the operation of digital signature to SOAP packet or HTTP packet.
In technique scheme, the step of SOAP packet or HTTP packet being resolved rear acquisition service indication parameter comprises: the interface layer by the data, services protocol stack carries out digital signature identification and data deciphering to SOAP packet or HTTP packet; Interface layer by the data, services protocol stack is resolved the packet header of SOAP packet or HTTP packet, carries out the control operation of authentication, request source, route and service release, obtains the inclusion of SOAP packet or HTTP packet; Service layer by the data, services protocol stack resolves the inclusion of SOAP packet or HTTP packet, obtains extensible markup; By the session layer of data, services protocol stack, know the type of interaction of service, extensible markup is forwarded to the presentation layer of data, services protocol stack according to the type of interaction of serving; Presentation layer by the data, services protocol stack is resolved extensible markup, obtains the service indication parameter.
In technique scheme, be submitted in database according to service indication parameter composition service-seeking instruction and carry out, the step of obtaining service data in database specifically comprises: the Model Mapping layer by the data, services protocol stack is dressed up the service-seeking instruction with the service indication parameter group; Articulamentum by the data, services protocol stack is submitted to the service-seeking instruction in database to be carried out, and obtains service data in database.
For achieving the above object, according to an aspect of the present invention, provide a kind of data, services answer method.
Data, services answer method according to the embodiment of the present invention comprises:
Service provider obtains service data by the articulamentum of data, services protocol stack in database, Model Mapping layer, presentation layer, session layer, service layer and interface layer by the data, services protocol stack are packaged into SOAP packet or HTTP packet with service data;
SOAP packet after service provider will encapsulate or HTTP Packet Generation are to service requester, so that after interface layer, service layer, session layer and the presentation layer of service requester by the data, services protocol stack resolve SOAP packet or HTTP packet, obtain service data.
In technique scheme, the step that service data is packaged into SOAP packet or HTTP packet comprises: the Model Mapping layer with service data by the data, services protocol stack is converted to relational data, and the UI Layer Wrapper by the data, services protocol stack becomes extensible markup with this relational data; By the session layer of data, services protocol stack, know the type of interaction of service, extensible markup is forwarded to the service layer of data, services protocol stack according to the type of interaction of serving; The service layer of extensible markup by the data, services protocol stack is encapsulated in the inclusion of SOAP packet or HTTP packet; Interface layer by the data, services protocol stack carries out response result, response time, encoding the response to the packet header of SOAP packet or HTTP packet and replys the encapsulation operation of the control information of description.
For achieving the above object, according to another aspect of the present invention, provide a kind of data service request data, services protocol stack.
Data, services protocol stack according to the embodiment of the present invention comprises:
Presentation layer is used for the service indication parameter is packaged into extensible markup, and extensible markup is resolved, and obtains the service indication parameter;
Session layer is used for initiating a session request according to the type of interaction of service, knows the type of interaction of service, according to the type of interaction of serving, extensible markup is forwarded to presentation layer;
Service layer for extensible markup being encapsulated into the inclusion of SOAP packet or HTTP packet, resolves the inclusion of SOAP packet or HTTP packet, obtains extensible markup;
Interface layer, be used for the packet header of SOAP packet or HTTP packet is carried out the encapsulation operation of service release, route, request source and authentication, resolve in packet header to SOAP packet or HTTP packet, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
The Model Mapping layer is used for the service indication parameter group is dressed up the service-seeking instruction;
Articulamentum is used for that the service-seeking instruction is submitted to database and carries out, and obtains service data in database.
In technique scheme, protocol stack also comprises: interface layer, also be used for SOAP packet or HTTP packet are carried out the operation of digital signature, and SOAP packet or HTTP packet are carried out digital signature identification and data deciphering.
In technique scheme, protocol stack also comprises: interface layer, also be used for data, services is externally issued, and offer service requester and call, and control the access of data, services by ESB, realize the integrated and unified control of data, services.
In technique scheme, protocol stack also comprises: the Model Mapping layer also is used for realizing the mapping of data model and the data base data model of data, services.
For achieving the above object, according to another aspect of the present invention, provide a kind of data, services protocol stack.
Data, services protocol stack according to the embodiment of the present invention comprises:
Articulamentum is used for obtaining service data from database;
The Model Mapping layer is used for service data is converted to relational data;
Presentation layer is used for relational data is packaged into extensible markup;
Session layer for the type of interaction of knowing service, is forwarded to service layer according to the type of interaction of serving with extensible markup;
Service layer is for extensible markup being encapsulated into the inclusion of SOAP packet or HTTP packet;
Interface layer is used for the packet header of SOAP packet or HTTP packet is carried out response result, response time, encoding the response and replied the encapsulation operation of the control information of description.
The data service request answer method of various embodiments of the present invention and data, services protocol stack, not only can realize using the decoupling zero with data, can also realize the decoupling zero of data, services inside, make the inside of data, services realize that details is simpler, efficient, clear, flexible and can expand.
Other features and advantages of the present invention will be set forth in the following description, and, partly become apparent from specification, perhaps understand by implementing the present invention.Purpose of the present invention and other advantages can realize and obtain by specifically noted structure in the specification of writing, claims and accompanying drawing.
Below by drawings and Examples, technical scheme of the present invention is described in further detail.
Description of drawings
Accompanying drawing is used to provide a further understanding of the present invention, and consists of the part of specification, is used for together with embodiments of the present invention explaining the present invention, is not construed as limiting the invention.In the accompanying drawings:
Fig. 1 is according to service register center of the prior art, service requester and service provider interactive relation schematic diagram;
Fig. 2 is the structural representation of data, services protocol stack of the present invention;
Fig. 3 is data source data form schematic diagram in articulamentum of the present invention;
Fig. 4 is the data format schematic diagram of LSQL of the present invention;
Fig. 5 is the data format schematic diagram of SQL of the present invention;
Fig. 6 is relational data form schematic diagram in the Model Mapping layer according to the present invention;
Fig. 7 is the XML data coding method schematic diagram of the presentation layer according to the present invention;
Fig. 8 is the CSV data coding method schematic diagram of the presentation layer according to the present invention;
Fig. 9 is the schematic diagram data of the Excel file type of the presentation layer according to the present invention;
Figure 10 is the schematic diagram of the online request-sync response mode of the session layer according to the present invention;
Figure 11 is the schematic diagram of the online request-asynchronous response mode of session layer according to the present invention;
Figure 12 is the schematic diagram of the Publish-subscribe mode of the session layer according to the present invention;
Figure 13 be the service layer according to the present invention encapsulation the SOAP request message data format schematic diagram of request message body;
Figure 14 be the service layer according to the present invention encapsulation the SOAP response message data format schematic diagram of response message body;
Figure 15 is the SOAP request message data format schematic diagram after service release of adding of the interface layer according to the present invention;
Figure 16 is the SOAP request message data format schematic diagram after service routing of adding of the interface layer according to the present invention;
The SOAP request message data format schematic diagram of Figure 17 after for time that joins request of interface layer according to the present invention;
Figure 18 is the SOAP request message data format schematic diagram after short connection authentication information of adding of the interface layer according to the present invention;
Figure 19 connects the SOAP request message data format schematic diagram after authentication information for adding of the interface layer according to the present invention is long;
Figure 20 is the SOAP request message data format schematic diagram after reliable request source information of adding of the interface layer according to the present invention;
Figure 21 is the SOAP request message data format schematic diagram after digital signature of carrying out of the interface layer according to the present invention;
Figure 22 is the SOAP response message data format schematic diagram after the access control information of the interface layer according to the present invention;
Figure 23 is the schematic flow sheet that service request direction service provider is initiated service request according to the present invention;
Figure 24 is the data format schematic diagram of KPI index parameter in step 102 according to the present invention;
Figure 25 is the data format schematic diagram of XML formatted data in step 104 according to the present invention;
Figure 26 is SOAP data format schematic diagram in step 108 according to the present invention;
Figure 27 is that the present invention initiates the data format schematic diagram after step 110 encapsulation in service request method embodiment;
Figure 28 is that the present invention initiates the data format schematic diagram after step 112 digital signature in service request method embodiment;
The service request that Figure 29 initiates service requester for the service provider according to the present invention is carried out the schematic flow sheet of service response;
Figure 30 is data source data form schematic diagram in step 202 according to the present invention;
Figure 31 is relational data form schematic diagram in step 204 according to the present invention;
Figure 32 is XML data format schematic diagram after encapsulating in step 206 according to the present invention;
Figure 33 is that the present invention carries out the data format schematic diagram after step 210 encapsulation in the service response embodiment of the method;
Figure 34 is that the present invention carries out the SOAP packet schematic diagram after step 212 encapsulation in the service response embodiment of the method.
Embodiment
Below in conjunction with accompanying drawing, the preferred embodiments of the present invention are described, should be appreciated that preferred embodiment described herein only is used for description and interpretation the present invention, is not intended to limit the present invention.
The technical scheme that existing Web Service data, services realizes, realization mainly for the service interface aspect, the inside that can not be deep into data, services realizes that details carries out normalized illustration, make the inside of data, services realize to obtain sufficient decoupling zero and multiplexing, cause the inside of data, services to realize more complicated, affect the implementation efficiency of data, services.Public data service request answer method of the present invention and data, services protocol stack, can address the above problem preferably, except realizing using the decoupling zero with data, can also realize the inner decoupling zero that realizes of data, services, make the inside of data, services realize that details is simpler, efficient, clear, flexible, can expand.
As shown in Figure 2, data, services protocol stack of the present invention is divided into six layers altogether, is articulamentum, Model Mapping layer, presentation layer, session layer, service layer and interface layer from top to bottom successively; Data, services protocol stack of the present invention is divided into and is two parts: service requester part and service provider part, the service requester part is comprised of presentation layer, session layer, service layer and interface layer from top to bottom, and the service provider part is comprised of articulamentum, Model Mapping layer, presentation layer, session layer, service layer and interface layer from top to bottom; Wherein, the 26S Proteasome Structure and Function of presentation layer, session layer, service layer and the interface layer in service requester part and service provider part is all identical.Data, services is by data source data, and the successively encapsulation to interface layer forms through articulamentum in the data, services protocol stack.
1, articulamentum
Articulamentum is used for realizing data, services to the connection of various data sources, and the operation of data source data, thereby obtains the needed data source data of data, services.
Articulamentum is by the data source interconnection technique, is connected to realize connection to various data sources such as JDBC, ODBC, FTP and SOAP, and obtains data source data from data source (being database).After articulamentum is obtained data from data source, exist with the data format of bit stream form, as shown in Figure 3.
2, Model Mapping layer
The Model Mapping layer is used for realizing the mapping of data model and the data source data model of data, services, the query statement of the data model of data, services is converted to the query statement of the data model of executable data source, and the data source data of articulamentum is converted to relational data.
The query statement interface of the data model of the data, services that the Model Mapping layer provides for presentation layer mainly can adopt the SQL of standard or LSQL (LSQL is Business Analysis Support Systemin China Mobile Communication Corporation data warehouse Boolean query language CMCC-LSQL) to realize.Wherein, SQL can't the shadow data storehouse and data model between difference, therefore mainly be applicable to rate request higher, the application scenarios that data model difference is little; And that LSQL mainly is applicable to rate request is not high, the application scenarios that data model differs greatly.
The data format of LSQL as shown in Figure 4.
The data format of SQL as shown in Figure 5.
If SQL, directly submit to articulamentum and carry out, if LSQL, need through being converted to executable physics SQL after Model Mapping, then submit to articulamentum and carry out.Articulamentum submits to database to carry out SQL by interconnection technique, and with the data source data of obtaining, returning to the Model Mapping layer, the Model Mapping layer is in order to facilitate the data representation of presentation layer, data source data is converted to relational data, and the relational data form as shown in Figure 6.
3, presentation layer
Presentation layer is used for representing the data in data, services reciprocal process, realizes the relational data in the Model Mapping layer is expressed as needed data format in data, services reciprocal process.
Data coding method mainly comprises: XML, CSV and binary mode, in different data, services reciprocal process, the expression mode of data may be different, as: adopt XML as the expression mode of data in the data, services interactive mode of " online request-sync response "; XML is adopted in data, services control information in " online request-asynchronous response " and " Publish-subscribe " interactive mode, and the data content of replying adopts the CSV data coding method; The data form there is being the demand occasion of specific (special) requirements, can adopting the data coding method of binary stream.
The data coding method of XML as shown in Figure 7, the data coding method of CSV is as shown in Figure 8.
The binary stream data coding method is mainly according to the concrete needs of using or user's requirement, generates the data of corresponding document type, as the data of Excel file type, as shown in Figure 9.
4, session layer
Session layer is the place that service requester and service provider carry out interactive sessions, and session layer represents the reciprocal process of data, services by different interactive modes.
The data interactive mode of session layer has " online request-sync response mode ", " online request-asynchronous response mode " and " Publish-subscribe mode ".Mainly by the service provider decision of data, which kind of data interactive mode service provider determines to adopt according to characteristics such as its data amount, requirement of real-times when data, services is developed in the selection of these three kinds of interactive modes (being the session negotiation mode).Be described as follows:
(1) online request-sync response mode
Online request-sync response mode refers to that service request direction service provider sends request of data, and enters blocked state, waits for that the response data of service provider is returned.Service provider carries out a series of Business Processing and obtains response data, and response data is replied to service requester after receiving request of data.Service requester is ended blocked state and is continued operation after receiving response data.The data interaction flow process of concrete online request-sync response mode as shown in figure 10.
This mode is applicable to response speed than very fast, and the smaller occasion of data volume.Because the service requester that sends request of data need to block operation, if therefore the speed of response is slow, can cause the long-time obstruction of service requester not move, have influence on possibly the normal operation that service requester is used; Equally, if the data volume of transmission is larger, in the process of transmission, the service of request msg also needs to wait for so, causes waits for too long.
(2) online request-asynchronous response mode
Online request-asynchronous response mode refers to that service requester calls " the preparation data method " of service provider, sends request of data to service provider.Service provider is after receiving request of data, and the request of returning successfully indicates, data are prepared estimates processing time, the time interval of the regular data query preparation of suggestion and the message such as obtain manner of data.Service requester can continue operation after obtaining above-mentioned message, do not need to be in for a long time blocked state.Service provider carries out a series of Business Processing to prepare data after returning to above-mentioned message.After processing time arrived, according to the time interval of the regular data query preparation of suggestion, service request direction service provider sent the request of data query preparation to service requester estimating of preparing of data.If data are not ready, the not ready message of service provider return data, service requester continues inquiry after the time interval of suggestion; If data are ready, service provider returns and comprises message when and where how to obtain data.Service requester namely can according to the given time to given place (FTP or http address) decide in its sole discretion in the given term of validity and when use given mode (FTP or http protocol) to obtain data.The data interaction flow process of concrete online request-asynchronous response mode as shown in figure 11.
It is long that this mode is applicable to requested data volume generation time, perhaps the larger occasion of data volume.Because the employing asynchronous system does not need to wait for for a long time and block that service requester can normally move other function, only need to process the data of request after receiving the ready signal of data again.
(3) Publish-subscribe mode
The Publish-subscribe mode refers to requirement and the notification service of " register method " registration request data of service request direction service provider.Service provider returns to the successful sign of request after receiving the registration message of service requester.Service requester can continue operation and not need to be in for a long time blocked state after obtaining above-mentioned registration message, and service provider carries out a series of Business Processing to prepare data after returning to above-mentioned registration message.Ready when data, service provider calls the notification service of service requester registration, informs service requester data preparation and relevant obtaining information.Service requester is replied successfully or failed sign, service requester namely can according to the given time to given place (FTP or http address) decide in its sole discretion in the given term of validity and when use given mode (FTP or http protocol) to obtain data, thereby the trigger-type of realizing data is mutual.The interaction flow of concrete Publish-subscribe mode as shown in figure 12.
This mode is applicable to the data encapsulation service of the various data volumes of triggering property transmission, and because the Publish-subscribe mode is asynchronous response mode in essence, so service requester do not need to wait for for a long time and block, and can normally move other function.
5, service layer
Service layer mainly realizes that by service technology does further encapsulation to the data of presentation layer, the message body of data content is encapsulated in the message body of data, services, and realizes concrete data, services.
Web Service technology is mainly adopted in the realization of service layer's data, services, and wherein the service provider of Web Service can be realized by SOAP or REST framework.Based on the data, services that SOAP realizes, mainly the data content message body with presentation layer is encapsulated in the Body of soap protocol, and based on the data, services that REST realizes, mainly message body is encapsulated in the message body of http protocol.Following article is based on the implementation of SOAP:
5.1 request message body encapsulation
The data format that the message body of presentation layer request msg content is packaged into the SOAP request message as shown in figure 13.
5.2 response message body encapsulation
The data format that the message body of presentation layer reply data content is packaged into the SOAP response message as shown in figure 14.
6, interface layer
Interface layer is on the basis of service layer, the further encapsulation of realization to safety, version, route and the control information etc. of data service message head, and data, services is externally issued, offering service requester calls, simultaneously by ESB (Enterprise Service Bus, being ESB) technology controls the access of data, services, realizes the integrated and unified control of data, services.
Data, services based on SOAP realizes mainly is encapsulated into message header in the Header of soap protocol; And based on the data, services that REST realizes, mainly message header is encapsulated in the custom variable HeaderReq of http protocol heading.Following article is based on the implementation of SOAP:
6.1 request message head encapsulation
6.1.1 service release
Service release is used for controlling service requester to the access of the data, services of different editions.On the basis of the SOAP of service layer request message, encapsulated the request message data format of service release message header as shown in figure 15.
6.1.2 service routing
Service routing is that the request with service requester sends to corresponding service provider according to certain routing rule, is mainly used in the situation that service provider carries out the clustered deploy(ment)s such as region-by-region, minute storehouse.For example: can according to the routing iinformation in area, service request be sent to the data, services server at place, this area.
On the basis of the SOAP of service layer request message, encapsulated the request message data format of service routing message header as shown in figure 16.
6.1.3 request time
Request time is used for identifying the time of this data, services access, and as the main contents of access log, investigation is followed the trail of in convenient daily record in the future.
On the basis of the SOAP of service layer request message, encapsulated the request message data format of request time message header as shown in figure 17.
6.1.4 authentication
Authentication is used for differentiating and confirming whether service requester is legal.By authentication, can make service provider confirm the identity of service requester, determine whether the access rights of this service.Authentication mainly contains following dual mode:
(1) short connection authentication
Short connection authentication mode mainly is applicable to external system to the access of data service, external system generally can be too not high to the access efficiency of data service, but fail safe is relatively high, so service requester all will provide the check informations such as user name, password to carry out authentication when asking at every turn.
On the basis of the SOAP of service layer request message, encapsulated the request message data format of short connection authentication information as shown in figure 18.
(2) the long connection authenticates
The long authentication mode that connects mainly is applicable to the internal system application to the access of data service, internal applications generally can be higher to the access efficiency of data service, fail safe is also reliable, therefore service requester only needs when user's authentication service of access services provider first, user name, cipher authentication information are provided, after passing through through authentication, service provider is that service requester generates unique token information, service requester need not each request the check informations such as user name, password all is provided in the term of validity of token.
On the basis of the SOAP of service layer request message, encapsulated the request message data format of long connection authentication information as shown in figure 19.
6.1.5 reliable request source
Reliably request source is used for controlling certain request and originates whether need the safety check function, for the system that is trusted, allows the user without safety check, and just the energy access data services, can reduce the development that is subjected to belief system.
On the basis of the SOAP of service layer request message, encapsulated the request message data format of reliable request source information as shown in figure 20.
6.1.6 digital signature
Digital signature is based on the security mechanism of asymmetric encryption techniques, can ensure the confidentiality of data or service traffics information by digital signature technology, and the denial behavior of prevention client.
To the SOAP request message carry out after digital signature data format as shown in figure 21.
6.2 response message head encapsulation
Mainly encapsulated in the response message head data, services response time, response result, reply error coded, reply the control information contents such as error message, as service requester to replying successfully or failed basis for estimation, and the analysis of failure cause.
On the basis of the SOAP of service layer response message, encapsulated the response message data format of control information as shown in figure 22.
Embodiment of the method
The below illustrates the data, services protocol stack in service request and service answering, the flow process of carrying out the protocol package encapsulation and resolving take " key index monitoring " application scenarios of online request-sync response interactive mode as example.
The service request flow process
" key index monitoring " uses when initiating service request by service request direction service provider, the flow process that the data, services protocol stack carries out the protocol package encapsulation and resolves, as shown in figure 23.
The idiographic flow step is as follows:
Step 102: " key index monitoring " uses the interface input KPI index parameter by service requester, initiates application request to service provider, and the KPI index parameter as shown in figure 24;
Step 104: service requester is encapsulated into the presentation layer of KPI index parameter by the data, services protocol stack in XML (Extensible Markup Language, extend markup language), and the XML formatted data after encapsulation as shown in figure 25.
Step 106: service requester is initiated the session of online request-sync response mode according to the interactive mode of service by the session layer of data, services protocol stack;
Step 108: service requester is by the service layer of data, services protocol stack, and in the inclusion of SOAP packet, the SOAP data format after encapsulation as shown in figure 26 with the XML data encapsulation.Step 110: service requester to the packet header of SOAP packet, carries out the encapsulation operation such as service release, route, request source and authentication by the interface layer of data, services protocol stack, and the data format after encapsulation as shown in figure 27;
Step 112: service requester carries out the digital signature operation by the interface layer of data, services protocol stack to the SOAP packet, and the data format after signature as shown in figure 28;
Step 114: the SOAP packet after service requester is completed encapsulation in online request-sync response mode, sends to service provider by the HTTP passage;
Step 116: after service provider receives service request, carry out digital signature identification and the data deciphering of SOAP packet by the interface layer of data, services protocol stack, and the packet header of SOAP packet is resolved, carry out the controls such as authentication, request source, route and version, the inclusion that then obtains the SOAP packet sends to the service layer of data, services protocol stack;
Step 118: service provider is resolved the inclusion of SOAP packet by the service layer of data, services protocol stack, obtains the XML data of service data request content;
Step 120: the session layer of service provider by the data, services protocol stack, after knowing that present interactive mode is for online request-sync response mode, by the method for synchronization with the XML data retransmission of the asking presentation layer to the data, services protocol stack;
Step 122: service provider is resolved the XML data by presentation layer, obtains the KPI parameter of service request;
Step 124: service provider is assembled into the KPI index parameter SQL statement of KPI information inquiry by the Model Mapping layer of data, services protocol stack;
Step 126: service provider by the JDBC interconnection technique, is submitted to SQL statement in database and carries out by the articulamentum of data, services protocol stack, obtains service data (being data source data) in database.
The service response flow process
When the service request that service provider is initiated " key index monitoring " application was carried out service response, the data, services agreement was carried out the flow process of encapsulation and the parsing of packet, as shown in figure 29.
The idiographic flow step is as follows:
Step 202: service provider gets service data (being data source data) by the articulamentum of data, services protocol stack in database, the data source data form as shown in figure 30.
Step 204: service provider is converted to relational data by the Model Mapping layer of data, services protocol stack with data source data, facilitates the encapsulation of the presentation layer of data, services protocol stack, and the relational data after conversion as shown in figure 31.
Step 206: service provider is encapsulated into the relational data in the Model Mapping layer in XML by the presentation layer of data, services protocol stack, and the XML data format after encapsulation shown in figure 32.
Step 208: service provider judges that this is the mode of online request-sync response alternately, with the service layer of XML data retransmission to the data, services protocol stack by the session layer of data, services protocol stack;
Step 210: service provider is by the service layer of data, services protocol stack, and in the inclusion of SOAP packet, the data format after encapsulation as shown in figure 33 with the XML data encapsulation;
Step 212: service provider is by the interface layer of data, services protocol stack, packet header to the SOAP packet, carry out response result, response time, encoding the response and reply the encapsulation of the control informations such as description, and with the SOAP Packet Generation to service requester, the SOAP packet after encapsulation is as shown in figure 34;
Step 214: service requester is resolved the SOAP packet by interface layer, service layer, session layer, presentation layer successively, finally gets data source data, and shows by " key index monitoring " application.
Request of data answer method of the present invention not only can realize using the decoupling zero with data, can also realize the decoupling zero of data, services inside, makes the inside of data, services realize that details is simpler, efficient, clear, flexible and can expand.
Protocol stack embodiment
According to the embodiment of the present invention, provide a kind of data, services protocol stack.The present embodiment comprises:
Presentation layer is used for the service indication parameter is packaged into extensible markup, and extensible markup is resolved, and obtains the service indication parameter;
Session layer is used for initiating a session request according to the type of interaction of service, knows the type of interaction of service, according to the type of interaction of serving, extensible markup is forwarded to presentation layer;
Service layer for extensible markup being encapsulated into the inclusion of SOAP packet or HTTP packet, resolves the inclusion of SOAP packet or HTTP packet, obtains extensible markup;
Interface layer, be used for the packet header of SOAP packet or HTTP packet is carried out the encapsulation operation of service release, route, request source and authentication, resolve in packet header to SOAP packet or HTTP packet, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
The Model Mapping layer is used for the service indication parameter group is dressed up the service-seeking instruction;
Articulamentum is used for that the service-seeking instruction is submitted to database and carries out, and obtains service data in database.
Wherein:
Interface layer also is used for SOAP packet or HTTP packet are carried out the operation of digital signature, and SOAP packet or HTTP packet are carried out digital signature identification and data deciphering.
Wherein:
Interface layer also is used for data, services is externally issued, and offers service requester and calls, and control the access of data, services by ESB, realizes the integrated and unified control of data, services.
Wherein:
The Model Mapping layer also is used for realizing the mapping of data model and the data base data model of data, services.
According to the embodiment of the present invention, provide a kind of data, services protocol stack.The present embodiment comprises:
Articulamentum is used for obtaining service data from database;
The Model Mapping layer is used for service data is converted to relational data;
Presentation layer is used for relational data is packaged into extensible markup;
Session layer for the type of interaction of knowing service, is forwarded to service layer according to the type of interaction of serving with extensible markup;
Service layer is for extensible markup being encapsulated into the inclusion of SOAP packet or HTTP packet;
Interface layer is used for the packet header of SOAP packet or HTTP packet is carried out response result, response time, encoding the response and replied the encapsulation operation of the control information of description.
Data, services protocol stack of the present invention not only can realize using the decoupling zero with data, can also realize the decoupling zero of data, services inside, makes the inside of data, services realize that details is simpler, efficient, clear, flexible and can expand.
One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment can be completed by the hardware that program command is correlated with, aforesaid program can be stored in a computer read/write memory medium, this program is carried out the step that comprises said method embodiment when carrying out; And aforesaid storage medium comprises: the various media that can be program code stored such as ROM, RAM, magnetic disc or CD.
It should be noted that at last: the above only is the preferred embodiments of the present invention, be not limited to the present invention, although with reference to previous embodiment, the present invention is had been described in detail, for a person skilled in the art, it still can be modified to the technical scheme that aforementioned each embodiment puts down in writing, and perhaps part technical characterictic wherein is equal to replacement.Within the spirit and principles in the present invention all, any modification of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (13)
1. a data service request method, is characterized in that, comprising:
Service requester is encapsulated into SOAP packet or HTTP packet by presentation layer, session layer, service layer and the interface layer of data, services protocol stack with the service indication parameter;
SOAP packet after service requester will encapsulate or HTTP Packet Generation are to service provider, so that service provider carries out described SOAP packet or HTTP packet to obtain the service-seeking instruction after dissection process, obtain service data in database.
2. method according to claim 1, is characterized in that, service provider is resolved rear acquisition service-seeking instruction with described SOAP packet or HTTP packet, and the step of obtaining service data in database comprises:
Service provider is resolved the described service indication parameter of rear acquisition by interface layer, service layer, session layer and the presentation layer of data, services protocol stack to described SOAP packet or HTTP packet;
Model Mapping layer and the articulamentum of service provider by the data, services protocol stack forms the service-seeking instruction according to described service indication parameter and is submitted in database and carries out, and obtains service data in database.
3. method according to claim 1, is characterized in that, the step that the service indication parameter is encapsulated into SOAP packet or HTTP packet comprises:
UI Layer Wrapper with the service indication parameter by the data, services protocol stack becomes extensible markup, initiates a session request according to the type of interaction of the service session layer by the data, services protocol stack;
Service layer by the data, services protocol stack is encapsulated into extensible markup in the inclusion of SOAP packet or HTTP packet;
Interface layer by the data, services protocol stack carries out the encapsulation operation of service release, route, request source and authentication to the packet header of SOAP packet or HTTP packet.
4. method according to claim 1, is characterized in that, the service indication parameter is encapsulated into the step of SOAP packet or HTTP packet and will encapsulate after the SOAP packet or the step of HTTP Packet Generation to service provider between also comprise:
Interface layer by the data, services protocol stack carries out the operation of digital signature to described SOAP packet or HTTP packet.
5. method according to claim 4, is characterized in that, the step of described SOAP packet or HTTP packet being resolved the described service indication parameter of rear acquisition comprises:
Interface layer by the data, services protocol stack carries out digital signature identification and data deciphering to SOAP packet or HTTP packet;
Interface layer by the data, services protocol stack is resolved the packet header of SOAP packet or HTTP packet, carries out the control operation of authentication, request source, route and service release, obtains the inclusion of SOAP packet or HTTP packet;
Service layer by the data, services protocol stack resolves the inclusion of SOAP packet or HTTP packet, obtains described extensible markup;
By the session layer of data, services protocol stack, know the type of interaction of service, described extensible markup is forwarded to the presentation layer of data, services protocol stack according to the type of interaction of serving;
Presentation layer by the data, services protocol stack is resolved described extensible markup, obtains the service indication parameter.
6. method according to claim 2, is characterized in that, is submitted in database according to described service indication parameter composition service-seeking instruction and carries out, and the step of obtaining service data in database specifically comprises:
Model Mapping layer by the data, services protocol stack is dressed up the service-seeking instruction with the service indication parameter group;
Articulamentum by the data, services protocol stack is submitted to described service-seeking instruction in database to be carried out, and obtains service data in database.
7. a data, services answer method, is characterized in that, comprising:
Service provider obtains service data by the articulamentum of data, services protocol stack in database, Model Mapping layer, presentation layer, session layer, service layer and interface layer by the data, services protocol stack are packaged into SOAP packet or HTTP packet with described service data;
SOAP packet after service provider will encapsulate or HTTP Packet Generation are to service requester, so that after interface layer, service layer, session layer and the presentation layer of service requester by the data, services protocol stack resolve described SOAP packet or HTTP packet, obtain described service data.
8. method according to claim 7, is characterized in that, the step that service data is packaged into SOAP packet or HTTP packet comprises:
Model Mapping layer with described service data by the data, services protocol stack is converted to relational data, and the UI Layer Wrapper by the data, services protocol stack becomes extensible markup with this relational data;
By the session layer of data, services protocol stack, know the type of interaction of service, described extensible markup is forwarded to the service layer of data, services protocol stack according to the type of interaction of serving;
The service layer of described extensible markup by the data, services protocol stack is encapsulated in the inclusion of SOAP packet or HTTP packet;
Interface layer by the data, services protocol stack carries out response result, response time, encoding the response to the packet header of described SOAP packet or HTTP packet and replys the encapsulation operation of the control information of description.
9. a data, services protocol stack, is characterized in that, comprising:
Presentation layer is used for the service indication parameter is packaged into extensible markup, and extensible markup is resolved, and obtains the service indication parameter;
Session layer is used for initiating a session request according to the type of interaction of service, knows the type of interaction of service, according to the type of interaction of serving, described extensible markup is forwarded to presentation layer;
Service layer for extensible markup being encapsulated into the inclusion of SOAP packet or HTTP packet, resolves the inclusion of SOAP packet or HTTP packet, obtains described extensible markup;
Interface layer, be used for the packet header of SOAP packet or HTTP packet is carried out the encapsulation operation of service release, route, request source and authentication, resolve in packet header to SOAP packet or HTTP packet, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
The Model Mapping layer is used for the service indication parameter group is dressed up the service-seeking instruction;
Articulamentum is used for that described service-seeking instruction is submitted to database and carries out, and obtains service data in database.
10. protocol stack according to claim 9, is characterized in that, also comprises:
Interface layer also is used for described SOAP packet or HTTP packet are carried out the operation of digital signature, and SOAP packet or HTTP packet are carried out digital signature identification and data deciphering.
11. protocol stack according to claim 9 is characterized in that, also comprises:
Interface layer also is used for data, services is externally issued, and offers service requester and calls, and control the access of data, services by ESB, realizes the integrated and unified control of data, services.
12. protocol stack according to claim 9 is characterized in that, also comprises:
The Model Mapping layer also is used for realizing the mapping of data model and the data base data model of data, services.
13. a data, services protocol stack is characterized in that, comprising:
Articulamentum is used for obtaining service data from database;
The Model Mapping layer is used for described service data is converted to relational data;
Presentation layer is used for described relational data is packaged into extensible markup;
Session layer for the type of interaction of knowing service, is forwarded to service layer according to the type of interaction of serving with described extensible markup;
Service layer is for described extensible markup being encapsulated into the inclusion of SOAP packet or HTTP packet;
Interface layer is used for the packet header of described SOAP packet or HTTP packet is carried out response result, response time, encoding the response and replied the encapsulation operation of the control information of description.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110362878.6A CN103117983B (en) | 2011-11-16 | 2011-11-16 | The method for designing of data service request answer method and data, services protocol stack |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110362878.6A CN103117983B (en) | 2011-11-16 | 2011-11-16 | The method for designing of data service request answer method and data, services protocol stack |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103117983A true CN103117983A (en) | 2013-05-22 |
| CN103117983B CN103117983B (en) | 2015-11-04 |
Family
ID=48416258
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110362878.6A Active CN103117983B (en) | 2011-11-16 | 2011-11-16 | The method for designing of data service request answer method and data, services protocol stack |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103117983B (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103577590A (en) * | 2013-11-12 | 2014-02-12 | 北京润乾信息系统技术有限公司 | Data query method and system |
| CN103139234B (en) * | 2011-11-23 | 2016-01-20 | 中国移动通信集团公司 | A kind of device and method of data, services encapsulation |
| CN105631568A (en) * | 2014-10-30 | 2016-06-01 | 博世包装技术（杭州）有限公司 | Communication method and device |
| CN105871979A (en) * | 2015-11-30 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Upgrade version detection method, device and system |
| CN106331080A (en) * | 2016-08-19 | 2017-01-11 | 明算科技（北京）股份有限公司 | SOA (Service-oriented architecture)-based resource cooperation system and method |
| CN106850502A (en) * | 2015-12-04 | 2017-06-13 | 阿里巴巴集团控股有限公司 | Service request retransmission method, storage method, apparatus and system based on connection long |
| CN107071058A (en) * | 2017-05-24 | 2017-08-18 | 深圳市可可卓科科技有限公司 | Asynchronous data upload process method and system |
| CN107104932A (en) * | 2016-02-23 | 2017-08-29 | 中兴通讯股份有限公司 | Key updating method, apparatus and system |
| CN107295007A (en) * | 2017-07-31 | 2017-10-24 | 浪潮天元通信信息系统有限公司 | A kind of method of servicing for supporting various protocols, apparatus and system |
| CN107609424A (en) * | 2017-10-30 | 2018-01-19 | 国网江苏省电力公司电力科学研究院 | A kind of intelligent substation data organization system for being adapted to more producer's configuration tool accesses |
| CN109117152A (en) * | 2018-07-26 | 2019-01-01 | 新华三大数据技术有限公司 | Service creation system and method |
| CN109542816A (en) * | 2018-10-29 | 2019-03-29 | 中国电子科技集团公司第二十九研究所 | A kind of service bus building method based on distributed system |
| CN109710675A (en) * | 2018-12-26 | 2019-05-03 | 深圳乐信软件技术有限公司 | A kind of storing data library switching method, device, server and storage medium |
| CN109857379A (en) * | 2019-01-18 | 2019-06-07 | 广州九尾信息科技有限公司 | A kind of method and device of data service encapsulation |
| WO2019184801A1 (en) * | 2018-03-29 | 2019-10-03 | 中兴通讯股份有限公司 | Network management method and apparatus |
| WO2019228515A1 (en) * | 2018-05-31 | 2019-12-05 | 华为技术有限公司 | Remote procedure call protocol self-adaptation method, related device, and server |
| CN111683148A (en) * | 2020-06-09 | 2020-09-18 | 吉林亿联银行股份有限公司 | Service processing system and method, service publishing method |
| CN115017128A (en) * | 2022-05-26 | 2022-09-06 | 上海介方信息技术有限公司 | Lightweight log service design method and system based on CORBA middleware |
| CN117436053A (en) * | 2023-12-20 | 2024-01-23 | 永鼎行远(南京)信息科技有限公司 | Data service bus system and data authentication transmission method |
| CN117494163A (en) * | 2023-11-06 | 2024-02-02 | 深圳市马博士网络科技有限公司 | Data service method and device based on security rules |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050027871A1 (en) * | 2003-06-05 | 2005-02-03 | William Bradley | Interoperable systems and methods for peer-to-peer service orchestration |
| CN101964739A (en) * | 2009-07-22 | 2011-02-02 | 中国移动通信集团公司 | Data transmission method, device and system |
| CN102081605A (en) * | 2009-11-30 | 2011-06-01 | 中国移动通信集团上海有限公司 | Data warehouse-based data encapsulation device and service data acquisition method |
| CN102110110A (en) * | 2009-12-28 | 2011-06-29 | 中国移动通信集团公司 | Method and device for data access based on SOA (Service-Oriented Architecture) |
-
2011
- 2011-11-16 CN CN201110362878.6A patent/CN103117983B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050027871A1 (en) * | 2003-06-05 | 2005-02-03 | William Bradley | Interoperable systems and methods for peer-to-peer service orchestration |
| CN101964739A (en) * | 2009-07-22 | 2011-02-02 | 中国移动通信集团公司 | Data transmission method, device and system |
| CN102081605A (en) * | 2009-11-30 | 2011-06-01 | 中国移动通信集团上海有限公司 | Data warehouse-based data encapsulation device and service data acquisition method |
| CN102110110A (en) * | 2009-12-28 | 2011-06-29 | 中国移动通信集团公司 | Method and device for data access based on SOA (Service-Oriented Architecture) |
Non-Patent Citations (2)
| Title |
|---|
| SHUJUN PEI 等: "Implementation of Web Services Composition System Based on SOA", 《2011 INTERNATIONAL CONFERENCE ON UNCERTAINTY REASONING AND KNOWLEDGE ENGINEERING (URKE)》 * |
| 高岩 等: "基于SOA架构的Web服务组合系统", 《小型微型计算机系统》 * |
Cited By (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139234B (en) * | 2011-11-23 | 2016-01-20 | 中国移动通信集团公司 | A kind of device and method of data, services encapsulation |
| CN103577590A (en) * | 2013-11-12 | 2014-02-12 | 北京润乾信息系统技术有限公司 | Data query method and system |
| CN105631568A (en) * | 2014-10-30 | 2016-06-01 | 博世包装技术（杭州）有限公司 | Communication method and device |
| CN105871979A (en) * | 2015-11-30 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Upgrade version detection method, device and system |
| CN106850502A (en) * | 2015-12-04 | 2017-06-13 | 阿里巴巴集团控股有限公司 | Service request retransmission method, storage method, apparatus and system based on connection long |
| CN107104932A (en) * | 2016-02-23 | 2017-08-29 | 中兴通讯股份有限公司 | Key updating method, apparatus and system |
| CN106331080A (en) * | 2016-08-19 | 2017-01-11 | 明算科技（北京）股份有限公司 | SOA (Service-oriented architecture)-based resource cooperation system and method |
| CN107071058A (en) * | 2017-05-24 | 2017-08-18 | 深圳市可可卓科科技有限公司 | Asynchronous data upload process method and system |
| CN107295007A (en) * | 2017-07-31 | 2017-10-24 | 浪潮天元通信信息系统有限公司 | A kind of method of servicing for supporting various protocols, apparatus and system |
| CN107609424A (en) * | 2017-10-30 | 2018-01-19 | 国网江苏省电力公司电力科学研究院 | A kind of intelligent substation data organization system for being adapted to more producer's configuration tool accesses |
| WO2019184801A1 (en) * | 2018-03-29 | 2019-10-03 | 中兴通讯股份有限公司 | Network management method and apparatus |
| CN110324837A (en) * | 2018-03-29 | 2019-10-11 | 中兴通讯股份有限公司 | A kind of network management and device |
| CN110324837B (en) * | 2018-03-29 | 2022-03-08 | 中兴通讯股份有限公司 | Network management method and device |
| WO2019228515A1 (en) * | 2018-05-31 | 2019-12-05 | 华为技术有限公司 | Remote procedure call protocol self-adaptation method, related device, and server |
| CN109117152B (en) * | 2018-07-26 | 2022-02-25 | 新华三大数据技术有限公司 | Service generation system and method |
| CN109117152A (en) * | 2018-07-26 | 2019-01-01 | 新华三大数据技术有限公司 | Service creation system and method |
| CN109542816A (en) * | 2018-10-29 | 2019-03-29 | 中国电子科技集团公司第二十九研究所 | A kind of service bus building method based on distributed system |
| CN109542816B (en) * | 2018-10-29 | 2021-05-18 | 中国电子科技集团公司第二十九研究所 | Service bus construction method based on distributed system |
| CN109710675A (en) * | 2018-12-26 | 2019-05-03 | 深圳乐信软件技术有限公司 | A kind of storing data library switching method, device, server and storage medium |
| CN109857379B (en) * | 2019-01-18 | 2023-09-05 | 广州九尾信息科技有限公司 | Method and device for packaging data service |
| CN109857379A (en) * | 2019-01-18 | 2019-06-07 | 广州九尾信息科技有限公司 | A kind of method and device of data service encapsulation |
| CN111683148A (en) * | 2020-06-09 | 2020-09-18 | 吉林亿联银行股份有限公司 | Service processing system and method, service publishing method |
| CN111683148B (en) * | 2020-06-09 | 2023-01-31 | 吉林亿联银行股份有限公司 | Service processing system and method, service publishing method |
| CN115017128A (en) * | 2022-05-26 | 2022-09-06 | 上海介方信息技术有限公司 | Lightweight log service design method and system based on CORBA middleware |
| CN115017128B (en) * | 2022-05-26 | 2023-02-10 | 上海介方信息技术有限公司 | Lightweight log service design method and system based on CORBA middleware |
| CN117494163A (en) * | 2023-11-06 | 2024-02-02 | 深圳市马博士网络科技有限公司 | Data service method and device based on security rules |
| CN117494163B (en) * | 2023-11-06 | 2024-05-31 | 深圳市马博士网络科技有限公司 | Data service method and device based on security rules |
| CN117436053A (en) * | 2023-12-20 | 2024-01-23 | 永鼎行远(南京)信息科技有限公司 | Data service bus system and data authentication transmission method |
| CN117436053B (en) * | 2023-12-20 | 2024-02-23 | 永鼎行远(南京)信息科技有限公司 | Data service bus system and data authentication transmission method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103117983B (en) | 2015-11-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103117983B (en) | The method for designing of data service request answer method and data, services protocol stack | |
| CN108306877B (en) | NODE JS-based user identity information verification method and device and storage medium | |
| CN108650262B (en) | Cloud platform expansion method and system based on micro-service architecture | |
| US20220329422A1 (en) | Data processing method, apparatus, computer program, and storage medium | |
| CN112883412B (en) | Device identifier dependent operation handling for packet based data communications | |
| US11356282B2 (en) | Sending cross-chain authenticatable messages | |
| CN103139234A (en) | Device and method for encapsulating data service | |
| US9219678B2 (en) | Method, system, and computer program product for sending and receiving messages | |
| CN101334887B (en) | Financial data-handling process and bank enterprise platform device | |
| US8255566B2 (en) | System and method for routing messages between applications | |
| CN104717647B (en) | Professional ability method for authenticating, equipment and system | |
| US20110307948A1 (en) | Extending a customer relationship management eventing framework to a cloud computing environment in a secure manner | |
| CN113409047B (en) | Data processing method, device and equipment based on block chain and readable storage medium | |
| WO2008016415A1 (en) | Portable personal identity information | |
| JP2013538380A (en) | Method, system, and computer program for a security model for a workflow that aggregates third party secure services | |
| CN101635707A (en) | Method for providing identity management for user in Web environment and device thereof | |
| CN106656919B (en) | A kind of session analytic method and system based on Telnet agreement | |
| US11184389B2 (en) | Security mechanisms for preventing retry or replay attacks | |
| CN111885133A (en) | Data processing method and device based on block chain and computer storage medium | |
| CN111327613A (en) | Distributed service authority control method and device and computer readable storage medium | |
| CN109800557A (en) | Integrated processing method, device, server, equipment and medium based on block chain | |
| CN105959385A (en) | Information communication method, device and system | |
| CN109146523A (en) | A kind of commodity counterfeit prevention verification system and method based on block chain | |
| CN114598531B (en) | Identity authentication method and equipment | |
| KR102051839B1 (en) | Methods for processing a message in M2M system and Apparatuses thereof |
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 |