CN103117983B - The method for designing of data service request answer method and data, services protocol stack - Google Patents
The method for designing of data service request answer method and data, services protocol stack Download PDFInfo
- Publication number
- CN103117983B CN103117983B CN201110362878.6A CN201110362878A CN103117983B CN 103117983 B CN103117983 B CN 103117983B CN 201110362878 A CN201110362878 A CN 201110362878A CN 103117983 B CN103117983 B CN 103117983B
- Authority
- CN
- China
- Prior art keywords
- service
- data
- 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.)
- Active
Links
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of data service request answer method and data, services protocol stack, wherein, the method comprises: service indication parameter is encapsulated into SOAP packet by service requester; SOAP Packet Generation after encapsulation to service provider, is obtained service-seeking instruction after SOAP packet or HTTP packet being carried out dissection process to make service provider, in database, obtains service data by service requester.The present invention not only can realize applying and the decoupling zero of data, can also realize the decoupling zero of data, services inside, makes the inside of data, services realize simpler, efficient, clear, the flexible and easily extensible of details.
Description
Technical field
The present invention relates to service operation support technology in the communications field, particularly, relate to method and the data, services protocol stack of data service request response.
Background technology
A lot of large enterprise at present, the enterprise as industries such as communication, finance has all come into effect SOA (Service-Oriented Architecture, Service-Oriented Architecture Based).SOA provides a kind of standard and the method that build IT tissue, IT business redundancy is reduced by setting up capable of being combined, reusable service system, and accelerate the process of project development, SOA system can make that IT department efficiency is higher, the construction cycle is shorter, project distribution is faster, in assistance IT technology and business integration, have higher value.
One of key content in SOA implementation process is the realization of data, services, and data, services, as the technology of application with data decoupler, can realize the high cohesion of software, loose coupling, can improve the reusing degree of software.
Existing industry mainly contains the technology such as EJB, CORBA, DCOM and Web Service in the realizing of data, services, and wherein that popular is Web Service.Web Service use standard, the XML of specification describes interface, describe and serve and carry out mutual required full details, comprise message format, host-host protocol and service position; And the details that the service that conceals in external interface realizes, only provide a series of executable operation, this operation serves programming language used independent of hardware and software platform with writing.The architecture of Web Service mainly based on service register center, mutual between service requester (i.e. service requester) and ISP's (i.e. service provider) Three role, as shown in Figure 1.
The relating generally to issue alternately, search and bindings of Three role, ISP defines the service describing of Web service and it is published to service register center, service requester uses search operation to describe from local or service register center retrieval service, then uses service describing and ISP to carry out binding and called Web service.
Application number be 201010616910.4 Chinese patent application describe a kind of Web Service serve management method and system, comprising: the webserver obtain client send authenticating user identification request; Described authenticating user identification request comprises: customer digital certificate and user's ID authentication information; The authenticating user identification request forward that the described webserver is got is to authentication center, so that described authentication center carries out certification to the described webserver and user identity; After described authentication center completes certification, the described webserver receives 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, effectively can also solve the problem whether the checking user of digital certificate and the owner be same entity.
The Chinese patent application that application number is 200910167170.8 discloses a kind for the treatment of system and the method that provide data, services, comprise: receive user the service request of data, services is provided after, when needs call external interface, based on the position of calling external interface, business is split as initial logic business and subsequent logic business; Initial logic business is processed, and returns segmentation response result to Reverse Proxy; Reverse Proxy is according to the request call external interface of segmentation response results; After the external interface called returns response results, by segmentation response results with call the response results that external interface returns and be integrated into the data, services result being supplied to 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 new request continuously and need not lose time in the response 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 service interface aspect, the inside that can not be deep into data, services realizes details and carries out normalized illustration, the inside of data, services is made to realize obtaining 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 object of the invention is, for the lower defect of the implementation efficiency of data, services in prior art, to propose a kind of data service request answer method and data, services protocol stack.
For achieving the above object, according to an aspect of the present invention, a kind of data service request method is provided.
According to the data service request method of the embodiment of the present invention, comprising:
Service indication parameter is encapsulated into SOAP packet or HTTP packet by the presentation layer of data, services protocol stack, session layer, service layer and interface layer by service requester;
Service requester by encapsulation after SOAP packet or HTTP Packet Generation to service provider, obtain service-seeking instruction after SOAP packet or HTTP packet being carried out dissection process to make service provider, in database, obtain service data.
In technique scheme, SOAP packet or HTTP packet carry out resolving rear acquisition service-seeking instruction by service provider, and the step obtaining service data in database comprises: service provider resolves rear acquisition service indication parameter by the interface layer of data, services protocol stack, service layer, session layer and presentation layer to SOAP packet or HTTP packet;
Service provider to be submitted in database according to service indication parameter composition service-seeking instruction by the Model Mapping layer of data, services protocol stack and articulamentum and to perform, in database, obtain service data.
In technique scheme, the step that service indication parameter is encapsulated into SOAP packet or HTTP packet is comprised:
Service indication parameter is become extensible markup by the UI Layer Wrapper of data, services protocol stack, and the type of interaction according to service is initiated a session request by the session layer of data, services protocol stack;
By the service layer of data, services protocol stack, extensible markup is encapsulated in the inclusion of SOAP packet or HTTP packet;
The encapsulation operation of service release, route, request source and authentication is carried out by the interface layer of the data, services protocol stack packet header to SOAP packet or HTTP packet.
In technique scheme, service indication parameter is encapsulated into SOAP packet or HTTP packet step and by the SOAP packet after encapsulating or HTTP Packet Generation to the step of service provider between also comprise: the operation by the interface layer of data, services protocol stack, SOAP packet or HTTP packet being carried out to digital signature.
In technique scheme, the step of SOAP packet or HTTP packet being resolved to rear acquisition service indication parameter comprises: carry out digital signature identification and data deciphering by the interface layer of data, services protocol stack to SOAP packet or HTTP packet; Resolved by the packet header of interface layer to SOAP packet or HTTP packet of data, services protocol stack, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet; Resolved by the inclusion of service layer to SOAP packet or HTTP packet of data, services protocol stack, obtain extensible markup; By the session layer of data, services protocol stack, know the type of interaction of service, according to the type of interaction of serving, extensible markup is forwarded to the presentation layer of data, services protocol stack; By the presentation layer of data, services protocol stack, extensible markup is resolved, obtain service indication parameter.
In technique scheme, be submitted in database according to service indication parameter composition service-seeking instruction and perform, the step obtaining service data in database specifically comprises: by the Model Mapping layer of data, services protocol stack, service indication parameter group is dressed up service-seeking instruction; By the articulamentum of data, services protocol stack service-seeking instruction is submitted in database and performs, in database, obtain service data.
For achieving the above object, according to an aspect of the present invention, a kind of data, services answer method is provided.
According to the data, services answer method of the embodiment of the present invention, comprising:
Service provider obtains service data by the articulamentum of data, services protocol stack in database, by the Model Mapping layer of data, services protocol stack, presentation layer, session layer, service layer and interface layer, service data is packaged into SOAP packet or HTTP packet;
Service provider by encapsulation after SOAP packet or HTTP Packet Generation to service requester, after SOAP packet or HTTP packet being resolved by the interface layer of data, services protocol stack, service layer, session layer and presentation layer to make service requester, obtain service data.
In technique scheme, step service data being packaged into SOAP packet or HTTP packet comprises: service data is converted to relational data by the Model Mapping layer of data, services protocol stack, and this relational data is become extensible markup by the UI Layer Wrapper of data, services protocol stack; By the session layer of data, services protocol stack, know the type of interaction of service, according to the type of interaction of serving, extensible markup is forwarded to the service layer of data, services protocol stack; By extensible markup by the services layer encapsulates of data, services protocol stack in the inclusion of SOAP packet or HTTP packet; The encapsulation operation of the control information that response result, response time, encoding the response and response describe is carried out by the interface layer of the data, services protocol stack packet header to SOAP packet or HTTP packet.
For achieving the above object, according to another aspect of the present invention, a kind of data service request data, services protocol stack is provided.
According to the data, services protocol stack of the embodiment of the present invention, comprising:
Presentation layer, for service indication parameter is packaged into extensible markup, resolves extensible markup, obtains service indication parameter;
Session layer, for initiating a session request according to the type of interaction of service, knows the type of interaction of service, and extensible markup is forwarded to presentation layer by the type of interaction according to service;
Service layer, for extensible markup being encapsulated in the inclusion of SOAP packet or HTTP packet, resolves the inclusion of SOAP packet or HTTP packet, obtains extensible markup;
Interface layer, for carrying out the encapsulation operation of service release, route, request source and authentication to the packet header of SOAP packet or HTTP packet, the packet header of SOAP packet or HTTP packet is resolved, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
Model Mapping layer, for dressing up service-seeking instruction by service indication parameter group;
Articulamentum, performing for service-seeking instruction being submitted in database, in database, obtaining service data.
In technique scheme, protocol stack also comprises: interface layer, also for carrying out the operation of digital signature to SOAP packet or HTTP packet, carries out digital signature identification and data deciphering to SOAP packet or HTTP packet.
In technique scheme, protocol stack also comprises: interface layer, also for data, services externally being issued, being supplied to service requester and calling, and by the access that ESB control data is served, realizes the integrated and unified control of data, services.
In technique scheme, protocol stack also comprises: Model Mapping layer, also for the mapping of the data model and data base data model that realize data, services.
For achieving the above object, according to another aspect of the present invention, a kind of data, services protocol stack is provided.
According to the data, services protocol stack of the embodiment of the present invention, comprising:
Articulamentum, for obtaining service data in database;
Model Mapping layer, for being converted to relational data by service data;
Presentation layer, for being packaged into extensible markup by relational data;
Session layer, for knowing the type of interaction of service, extensible markup is forwarded to service layer by the type of interaction according to service;
Service layer, for being encapsulated in the inclusion of SOAP packet or HTTP packet by extensible markup;
Interface layer, for carrying out the encapsulation operation of the control information that response result, response time, encoding the response and response describe to the packet header of SOAP packet or HTTP packet.
The data service request answer method of various embodiments of the present invention and data, services protocol stack, not only can realize applying the decoupling zero with data, the decoupling zero of data, services inside can also be realized, make the inside of data, services realize simpler, efficient, clear, the flexible and easily extensible of details.
Other features and advantages of the present invention will be set forth in the following description, and, partly become apparent from specification, or understand by implementing the present invention.Object of the present invention and other advantages realize by structure specifically noted in write specification, claims and accompanying drawing and obtain.
Below by drawings and Examples, technical scheme of the present invention is described in further detail.
Accompanying drawing explanation
Accompanying drawing is used to provide a further understanding of the present invention, and forms a part for specification, together with embodiments of the present invention for 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 according to relational data form schematic diagram in Model Mapping layer of the present invention;
Fig. 7 is the XML data representation schematic diagram according to presentation layer of the present invention;
Fig. 8 is the CSV data coding method schematic diagram according to presentation layer of the present invention;
Fig. 9 is the schematic diagram data of the Excel file type according to presentation layer of the present invention;
Figure 10 is the schematic diagram of the online request-sync response mode according to session layer of the present invention;
Figure 11 is the schematic diagram of the online request-asynchronous response mode according to session layer of the present invention;
Figure 12 is the schematic diagram of the issue-subscribing manner according to session layer of the present invention;
Figure 13 is the SOAP request message data format schematic diagram encapsulating request message body according to service layer of the present invention;
Figure 14 is the SOAP response message data format schematic diagram encapsulating response message body according to service layer of the present invention;
Figure 15 is the SOAP request message data format schematic diagram added after service release according to interface layer of the present invention;
Figure 16 is the SOAP request message data format schematic diagram added after service routing according to interface layer of the present invention;
Figure 17 be according to the time that joins request of interface layer of the present invention after SOAP request message data format schematic diagram;
Figure 18 is the SOAP request message data format schematic diagram added after short connection authentication information according to interface layer of the present invention;
Figure 19 is the SOAP request message data format schematic diagram added after long connection authentication information according to interface layer of the present invention;
Figure 20 is the SOAP request message data format schematic diagram added after reliable request source information according to interface layer of the present invention;
Figure 21 be according to the access control information of interface layer of the present invention after SOAP response message data format schematic diagram;
Figure 22 is the schematic flow sheet of initiating service request according to service request direction of the present invention service provider;
Figure 23 is the data format schematic diagram according to KPI index parameter in step 102 of the present invention;
Figure 24 is the data format schematic diagram according to XML format data in step 104 of the present invention;
Figure 25 is according to SOAP data format schematic diagram in step 108 of the present invention;
Figure 26 is the data format schematic diagram that the present invention initiates in service request method embodiment after step 110 encapsulation;
Figure 27 is the schematic flow sheet according to service provider of the present invention, the service request that service requester is initiated being carried out to service response;
Figure 28 is according to data source data form schematic diagram in step 202 of the present invention;
Figure 29 is according to relational data form schematic diagram in step 204 of the present invention;
Figure 30 is according to XML data form schematic diagram after encapsulation in step 206 of the present invention;
Figure 31 is the data format schematic diagram that the present invention carries out in service response embodiment of the method after step 210 encapsulation;
Figure 32 is the SOAP packet schematic diagram that the present invention carries out in service response embodiment of the method after step 212 encapsulation.
Embodiment
Below in conjunction with accompanying drawing, the preferred embodiments of the present invention are described, should be appreciated that preferred embodiment described herein is only for instruction and explanation of the present invention, is not intended to limit the present invention.
The technical scheme that existing Web Service data, services realizes, mainly for the realization of service interface aspect, the inside that can not be deep into data, services realizes details and carries out normalized illustration, the inside of data, services is made to realize obtaining 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 solve the problem preferably, except realizing applying the decoupling zero with data, can also realize the decoupling zero that data, services inside realizes, the inside of data, services is realized, and details is simpler, efficient, clear, flexible, easily extensible.
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 two parts: service requester part and service provider part, service requester part is made up of presentation layer, session layer, service layer and interface layer from top to bottom, and service provider part is made up of articulamentum, Model Mapping layer, presentation layer, session layer, service layer and interface layer from top to bottom; Wherein, service requester part and the presentation layer in service provider part, session layer, service layer are all identical with the 26S Proteasome Structure and Function of interface layer.Data, services is by data source data, and in data, services protocol stack, articulamentum forms to the successively encapsulation of interface layer.
1, articulamentum
Articulamentum is used for realizing the connection of data, services to various data source, and the operation of data source data, thus obtains the data source data required for data, services.
Articulamentum is by data source interconnection technique, and such as JDBC, ODBC, FTP and SOAP etc. realize the connection to various data source, and obtain data source data from data source (i.e. database).Articulamentum, after handles data, exists with the data format of bit stream form, as shown in Figure 3.
2, Model Mapping layer
Model Mapping layer is used for realizing the data model of data, services and the mapping of data source data model, 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 Model Mapping layer provides for presentation layer, mainly can adopt SQL or LSQL of standard (LSQL is Business Analysis Support Systemin China Mobile Communication Corporation data warehouse Boolean query language CMCC-LSQL) to realize.Wherein, SQL cannot difference between shadow data storehouse and data model, is therefore mainly applicable to rate request higher, the application scenarios that data model difference is little; And LSQL to be mainly applicable to rate request 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, then directly submit to articulamentum and perform, if LSQL, then need after Model Mapping, be converted to executable physics SQL, then submit to articulamentum execution.SQL submits to database to perform by interconnection technique by articulamentum, and the data source data that will obtain, return to Model Mapping layer, the data representation of Model Mapping layer conveniently presentation layer, data source data is converted to relational data, and 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 Model Mapping layer to be expressed as data format required in data, services reciprocal process.
Data coding method mainly comprises: XML, CSV and binary mode, in different data, services reciprocal process, the representation of data may be different, as: in the data, services interactive mode of " online request-sync response ", adopt XML as the representation of data; Data, services control information in " online request-asynchronous response " and " issue-subscribe to " interactive mode adopts XML, and the data content of response adopts CSV data coding method; There being the demand occasion of particular/special requirement to data format, the data coding method of binary stream can be adopted.
As shown in Figure 7, the data coding method of CSV as shown in Figure 8 for the data coding method of XML.
Binary stream data coding method, mainly according to the needs of embody rule or the requirement of user, 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 " issue-subscribing manner ".The selection of these three kinds of interactive modes (i.e. session negotiation mode) determines primarily of the service provider of data, and service provider, according to features such as its data amount, requirement of real-times, determines to adopt which kind of data interactive mode when data, services is developed.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 returns.Service provider, after receiving request of data, carries out a series of Business Processing and obtains response data, and response data is replied to service requester.Service requester, after receiving response data, stops blocked state and continues to run.The data interaction flow process of concrete online request-sync response mode as shown in Figure 10.
Which is applicable to response speed than very fast, and the occasion that data volume is smaller.Run because the service requester sending request of data needs to block, if therefore the speed of response is slow, service requester can be caused to block for a long time can not be run, and has influence on the normal operation of service requester application possibly; Equally, if the data volume of transmission is larger, in the process so transmitted, the service of request msg also needs to wait for, 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, after receiving request of data, returns request Success Flag, the estimating the processing time, advise the message such as the regular time interval of data query preparation and the obtain manner of data of data encasement.Service requester can continue to run after the above-mentioned message of acquisition, does not need to be in blocked state for a long time.Service provider carries out a series of Business Processing to prepare data after returning above-mentioned message.Service requester is estimated after the processing time arrives at data encasement, and according to the time interval of the regular data query preparation of suggestion, service request direction service provider sends the request of data query preparation.If data are not ready, the not ready message of service provider return data, service requester then continues inquiry after the time interval of suggestion; If data encasement is complete, service provider returns the message comprising and when and where how to obtain data.Namely service requester can be decided in its sole discretion to given place (FTP or http address) according to the given time and when use given mode (FTP or http protocol) to obtain data in the given term of validity.The data interaction flow process of concrete online request-asynchronous response mode as shown in figure 11.
It is long which is applicable to requested data volume generation time, or the occasion that data volume is larger.Because employing asynchronous system, do not need to wait for for a long time and block, service requester can normally run other function, only needs the data of reprocessing request after receiving the complete signal of data encasement.
(3) issue-subscribing manner
Issue-subscribing manner refers to requirement and the notification service of " register method " registration request data of service request direction service provider.Service provider, after receiving the registration message of service requester, returns request successfully mark.Service requester is after the above-mentioned registration message of acquisition, and can continue run and do not need to be in blocked state for a long time, service provider, after returning above-mentioned registration message, carries out a series of Business Processing to prepare data.When data encasement is complete, service provider calls the notification service of service requester registration, advertise service requesting party data encasement situation and relevant obtaining information.Service requester is replied successfully or failed mark, namely service requester can be decided in its sole discretion to given place (FTP or http address) according to the given time and when use given mode (FTP or http protocol) to obtain data in the given term of validity, thus the trigger-type realizing data is mutual.The interaction flow of concrete issue-subscribing manner as shown in figure 12.
Which is applicable to the data encapsulation service of the various data volume of triggering transmission, and because issue-subscribing manner is asynchronous response mode in essence, therefore service requester does not need to wait for for a long time and block, and can normally run other function.
5, service layer
Further encapsulation is done mainly through the data of service actualizing technology to presentation layer by service layer, the message body of data content is encapsulated in the message body of data, services, and realizes concrete data, services.
The realization of service layer's data, services mainly adopts Web Service technology, 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 of 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.The main implementation introduced based on SOAP below:
5.1 request message body encapsulation
The message body of presentation layer request msg content is packaged into the data format of SOAP request message as shown in figure 13.
5.2 response message body encapsulation
The message body of presentation layer reply data content is packaged into the data format of SOAP response message as shown in figure 14.
6, interface layer
Interface layer is on the basis of service layer, realize the further encapsulation of the safety to data services messages head, version, route and control information etc., and data, services is externally issued, be supplied to service requester to call, simultaneously by ESB (Enterprise Service Bus, i.e. ESB) technology come control data service access, realize the integrated and unified control of data, services.
Based on the data, services that SOAP realizes, mainly message header is encapsulated 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.The main implementation introduced based on SOAP below:
6.1 request message head encapsulation
6.1.1 service release
Service release is for controlling the access of service requester to the data, services of different editions.On the basis of service layer SOAP request message, encapsulate 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 of service requester is sent to corresponding service provider according to certain routing rule, is mainly used in the situation that service provider carries out the clustered deploy(ment) such as region-by-region, point storehouse.Such as: according to the routing iinformation in area, service request can be sent to the data access servers at place, this area.
On the basis of service layer SOAP request message, encapsulate 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 service layer SOAP request message, encapsulate the request message data format of request time message header as shown in figure 17.
6.1.4 authentication
Authentication is used for differentiating whether service requester is legal and confirms.By authentication, the identity of service provider confirmed service requesting party can be made, determine whether the access rights of this service.Authentication mainly contains following two kinds of modes:
(1) short connection certification
Short connection authentication mode is mainly applicable to the access of external system to data, services, external system generally can not be too high to the access efficiency of data, services, but fail safe is relatively high, the check information such as user name, password when therefore service requester is asked at every turn, all to be provided to carry out authentication.
On the basis of service layer SOAP request message, encapsulate the request message data format of short connection authentication information as shown in figure 18.
(2) long connection certification
The long authentication mode that connects mainly is applicable to the access of internal system application to data, services, internal applications generally can be higher to the access efficiency of data, services, fail safe is also reliable, therefore service requester only need when the user authentication service of access services provider first, user name, cipher authentication information are provided, after certification is passed through, service provider is that service requester generates unique token information, service requester, in the term of validity of token, all provides the check information such as user name, password without the need to asking at every turn.
On the basis of service layer SOAP request message, encapsulate the request message data format of long connection authentication information as shown in figure 19.
6.1.5 reliable request source
Reliable request source is used for controlling certain request source the need of safety check function, and for the system of being trusted, allow user without safety check, just energy access data services, can reduce the development by belief system.
On the basis of service layer SOAP request message, encapsulate the request message data format of reliable request source information as shown in figure 20.
6.1.6 digital signature
Digital signature is the security mechanism based on asymmetric encryption techniques, can be ensured the confidentiality of data or service traffics information by digital signature technology, and the denial behavior of prevention client.
6.2 response message head encapsulation
The control information content such as the predominant package response time of data, services, response result, response error coded, response error message in response message head, as service requester to replying successfully or failed basis for estimation, and the analysis of failure cause.
On the basis of service layer SOAP response message, encapsulate the response message data format of control information as shown in figure 21.
embodiment of the method
Below asking online-" key index monitoring " application scenarios of sync response interactive mode, illustrate that data, services protocol stack is in service request and service answering, carries out the flow process of protocol package encapsulation and parsing.
Se ce request procedure
When " key index monitoring " application initiates service request by service request direction service provider, data, services protocol stack carries out the flow process of protocol package encapsulation and parsing, as shown in figure 22.
Idiographic flow step is as follows:
Step 102: " key index monitoring " application is by the interface input KPI index parameter of service requester, and initiate application request to service provider, KPI index parameter as shown in figure 23;
Step 104: service requester is by the presentation layer of KPI index parameter by data, services protocol stack, and be encapsulated in XML (Extensible Markup Language, extend markup language), the XML format data after encapsulation as shown in figure 24.
Step 106: service requester, according to the interactive mode of service, initiates the session of online request-sync response mode by the session layer of data, services protocol stack;
Step 108: service requester is by the service layer of data, services protocol stack, and XML data be encapsulated in the inclusion of SOAP packet, the SOAP data format after encapsulation as shown in figure 25.Step 110: service requester is by the interface layer of data, services protocol stack, and to the packet header of SOAP packet, carry out the encapsulation operation such as service release, route, request source and authentication, the data format after encapsulation as shown in figure 26;
Step 112: service requester, by the interface layer of data, services protocol stack, carries out digital signing operations to SOAP packet;
Step 114: service requester, by the SOAP packet after having encapsulated, to ask-sync response mode online, sends to service provider by HTTP passage;
Step 116: after service provider receives service request, digital signature identification and the data deciphering of SOAP packet is carried out 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 then obtaining SOAP packet sends to the service layer of data, services protocol stack;
Step 118: service provider, by the service layer of data, services protocol stack, is resolved the inclusion of SOAP packet, obtains the XML data of service data request content;
Step 120: service provider, by the session layer of data, services protocol stack, knows that current interactive mode is for after online request-sync response mode, is transmitted to the presentation layer of data, services protocol stack by the XML data of request by the method for synchronization;
Step 122: service provider, by presentation layer, is resolved XML data, obtains the KPI parameter of service request;
Step 124: KPI index parameter, by the Model Mapping layer of data, services protocol stack, is assembled into the SQL statement of KPI information inquiry by service provider;
Step 126: service provider, by the articulamentum of data, services protocol stack, by SQL statement by JDBC interconnection technique, is submitted in database and performs, obtain service data (i.e. data source data) in database.
Service response flow process
When service provider carries out service response to the service request that " key index monitoring " application is initiated, data, services agreement carries out the encapsulation of packet and the flow process of parsing, as shown in figure 27.
Idiographic flow step is as follows:
Step 202: service provider is by the articulamentum of data, services protocol stack, and get service data (i.e. data source data) in database, data source data form as shown in figure 28.
Step 204: service provider is by the Model Mapping layer of data, services protocol stack, and data source data is converted to relational data, facilitates the encapsulation of the presentation layer of data, services protocol stack, the relational data after conversion as shown in figure 29.
Step 206: service provider is by the presentation layer of data, services protocol stack, and be encapsulated in XML by the relational data in Model Mapping layer, the XML data form after encapsulation as shown in figure 30.
Step 208: service provider, by the session layer of data, services protocol stack, judges this alternately as the mode of online request-sync response, XML data is transmitted to the service layer of data, services protocol stack;
Step 210: service provider is by the service layer of data, services protocol stack, and XML data be encapsulated in the inclusion of SOAP packet, the data format after encapsulation as shown in figure 31;
Step 212: service provider is by the interface layer of data, services protocol stack, to the packet header of SOAP packet, carry out the encapsulation of the control informations such as response result, response time, encoding the response and response description, and by SOAP Packet Generation to service requester, the SOAP packet after encapsulation as shown in figure 32;
Step 214: service requester is resolved SOAP packet by interface layer, service layer, session layer, presentation layer successively, finally gets data source data, and shown by " key index monitoring " application.
Request of data answer method of the present invention, not only can realize applying and the decoupling zero of data, can also realize the decoupling zero of data, services inside, makes the inside of data, services realize simpler, efficient, clear, the flexible and easily extensible of details.
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, for service indication parameter is packaged into extensible markup, resolves extensible markup, obtains service indication parameter;
Session layer, for initiating a session request according to the type of interaction of service, knows the type of interaction of service, and extensible markup is forwarded to presentation layer by the type of interaction according to service;
Service layer, for extensible markup being encapsulated in the inclusion of SOAP packet or HTTP packet, resolves the inclusion of SOAP packet or HTTP packet, obtains extensible markup;
Interface layer, for carrying out the encapsulation operation of service release, route, request source and authentication to the packet header of SOAP packet or HTTP packet, the packet header of SOAP packet or HTTP packet is resolved, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
Model Mapping layer, for dressing up service-seeking instruction by service indication parameter group;
Articulamentum, performing for service-seeking instruction being submitted in database, in database, obtaining service data.
Wherein:
Interface layer, also for carrying out the operation of digital signature to SOAP packet or HTTP packet, carries out digital signature identification and data deciphering to SOAP packet or HTTP packet.
Wherein:
Interface layer, also for data, services externally being issued, being supplied to service requester and calling, and by the access that ESB control data is served, realizes the integrated and unified control of data, services.
Wherein:
Model Mapping layer, also for the mapping of the data model and data base data model that realize data, services.
According to the embodiment of the present invention, provide a kind of data, services protocol stack.The present embodiment comprises:
Articulamentum, for obtaining service data in database;
Model Mapping layer, for being converted to relational data by service data;
Presentation layer, for being packaged into extensible markup by relational data;
Session layer, for knowing the type of interaction of service, extensible markup is forwarded to service layer by the type of interaction according to service;
Service layer, for being encapsulated in the inclusion of SOAP packet or HTTP packet by extensible markup;
Interface layer, for carrying out the encapsulation operation of the control information that response result, response time, encoding the response and response describe to the packet header of SOAP packet or HTTP packet.
Data, services protocol stack of the present invention, not only can realize applying and the decoupling zero of data, can also realize the decoupling zero of data, services inside, makes the inside of data, services realize simpler, efficient, clear, the flexible and easily extensible of details.
One of ordinary skill in the art will appreciate that: all or part of step realizing said method embodiment can have been come by the hardware that program command is relevant, aforesaid program can be stored in a computer read/write memory medium, this program, when performing, performs the step comprising said method embodiment; And aforesaid storage medium comprises: ROM, RAM, magnetic disc or CD etc. various can be program code stored medium.
Last it is noted that the foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, although with reference to previous embodiment to invention has been detailed description, for a person skilled in the art, it still can be modified to the technical scheme described in foregoing embodiments, or carries out equivalent replacement to wherein portion of techniques feature.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (13)
1. a data service request method, is characterized in that, comprising:
Service indication parameter is encapsulated into SOAP packet or HTTP packet by the presentation layer of data, services protocol stack, session layer, service layer and interface layer by service requester;
Service requester by encapsulation after SOAP packet or HTTP Packet Generation to service provider, obtain service-seeking instruction after described SOAP packet or HTTP packet being carried out dissection process to make service provider, in database, obtain service data;
Described data, services protocol stack comprises:
Presentation layer, for service indication parameter is packaged into extensible markup, resolves extensible markup, obtains service indication parameter;
Session layer, for initiating a session request according to the type of interaction of service, knows the type of interaction of service, and extensible markup is forwarded to presentation layer by the type of interaction according to service;
Service layer, for extensible markup being encapsulated in the inclusion of SOAP packet or HTTP packet, resolves the inclusion of SOAP packet or HTTP packet, obtains extensible markup;
Interface layer, for carrying out the encapsulation operation of service release, route, request source and authentication to the packet header of SOAP packet or HTTP packet, the packet header of SOAP packet or HTTP packet is resolved, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
Model Mapping layer, for dressing up service-seeking instruction by service indication parameter group;
Articulamentum, performing for described service-seeking instruction being submitted in database, in database, obtaining service data.
2. method according to claim 1, is characterized in that, described SOAP packet or HTTP packet carry out resolving rear acquisition service-seeking instruction by service provider, and the step obtaining service data in database comprises:
Service provider resolves the described service indication parameter of rear acquisition by the interface layer of data, services protocol stack, service layer, session layer and presentation layer to described SOAP packet or HTTP packet;
Service provider to be submitted in database according to described service indication parameter composition service-seeking instruction by the Model Mapping layer of data, services protocol stack and articulamentum and to perform, in database, obtain service data.
3. method according to claim 1, is characterized in that, the step that service indication parameter is encapsulated into SOAP packet or HTTP packet is comprised:
Service indication parameter is become extensible markup by the UI Layer Wrapper of data, services protocol stack, and the type of interaction according to service is initiated a session request by the session layer of data, services protocol stack;
By the service layer of data, services protocol stack, extensible markup is encapsulated in the inclusion of SOAP packet or HTTP packet;
The encapsulation operation of service release, route, request source and authentication is carried out by the interface layer of the data, services protocol stack packet header to SOAP packet or HTTP packet.
4. method according to claim 1, is characterized in that, service indication parameter is encapsulated into SOAP packet or HTTP packet step and by the SOAP packet after encapsulating or HTTP Packet Generation to the step of service provider between also comprise:
By the interface layer of data, services protocol stack, described SOAP packet or HTTP packet are carried out to the operation of digital signature.
5. method according to claim 4, is characterized in that, the step of described SOAP packet or HTTP packet being resolved to the described service indication parameter of rear acquisition comprises:
By the interface layer of data, services protocol stack, digital signature identification and data deciphering are carried out to SOAP packet or HTTP packet;
Resolved by the packet header of interface layer to SOAP packet or HTTP packet of data, services protocol stack, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
Resolved by the inclusion of service layer to SOAP packet or HTTP packet of data, services protocol stack, obtain described extensible markup;
By the session layer of data, services protocol stack, know the type of interaction of service, according to the type of interaction of serving, described extensible markup is forwarded to the presentation layer of data, services protocol stack;
By the presentation layer of data, services protocol stack, described extensible markup is resolved, obtain service indication parameter.
6. method according to claim 2, is characterized in that, be submitted in database according to described service indication parameter composition service-seeking instruction and perform, the step obtaining service data in database specifically comprises:
By the Model Mapping layer of data, services protocol stack, service indication parameter group is dressed up service-seeking instruction;
By the articulamentum of data, services protocol stack described service-seeking instruction is submitted in database and performs, in database, obtain service data.
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, by the Model Mapping layer of data, services protocol stack, presentation layer, session layer, service layer and interface layer, described service data is packaged into SOAP packet or HTTP packet;
Service provider by encapsulation after SOAP packet or HTTP Packet Generation to service requester, after described SOAP packet or HTTP packet being resolved by the interface layer of data, services protocol stack, service layer, session layer and presentation layer to make service requester, obtain described service data;
Described data, services protocol stack comprises:
Presentation layer, for service indication parameter is packaged into extensible markup, resolves extensible markup, obtains service indication parameter;
Session layer, for initiating a session request according to the type of interaction of service, knows the type of interaction of service, and extensible markup is forwarded to presentation layer by the type of interaction according to service;
Service layer, for extensible markup being encapsulated in the inclusion of SOAP packet or HTTP packet, resolves the inclusion of SOAP packet or HTTP packet, obtains extensible markup;
Interface layer, for carrying out the encapsulation operation of service release, route, request source and authentication to the packet header of SOAP packet or HTTP packet, the packet header of SOAP packet or HTTP packet is resolved, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
Model Mapping layer, for dressing up service-seeking instruction by service indication parameter group;
Articulamentum, performing for described service-seeking instruction being submitted in database, in database, obtaining service data.
8. method according to claim 7, is characterized in that, step service data being packaged into SOAP packet or HTTP packet comprises:
Described service data is converted to relational data by the Model Mapping layer of data, services protocol stack, and this relational data is become extensible markup by the UI Layer Wrapper of data, services protocol stack;
By the session layer of data, services protocol stack, know the type of interaction of service, according to the type of interaction of serving, described extensible markup is forwarded to the service layer of data, services protocol stack;
By described extensible markup by the services layer encapsulates of data, services protocol stack in the inclusion of SOAP packet or HTTP packet;
The encapsulation operation of the control information that response result, response time, encoding the response and response describe is carried out by the interface layer of the data, services protocol stack packet header to described SOAP packet or HTTP packet.
9. a method for designing for data, services protocol stack, is characterized in that, this data, services protocol stack comprises:
Presentation layer, for service indication parameter is packaged into extensible markup, resolves extensible markup, obtains service indication parameter;
Session layer, for initiating a session request according to the type of interaction of service, knows the type of interaction of service, and extensible markup is forwarded to presentation layer by the type of interaction according to service;
Service layer, for extensible markup being encapsulated in the inclusion of SOAP packet or HTTP packet, resolving the inclusion of SOAP packet or HTTP packet, obtaining described extensible markup;
Interface layer, for carrying out the encapsulation operation of service release, route, request source and authentication to the packet header of SOAP packet or HTTP packet, the packet header of SOAP packet or HTTP packet is resolved, carry out the control operation of authentication, request source, route and service release, obtain the inclusion of SOAP packet or HTTP packet;
Model Mapping layer, for dressing up service-seeking instruction by service indication parameter group;
Articulamentum, performing for described service-seeking instruction being submitted in database, in database, obtaining service data.
10. the method for designing of protocol stack according to claim 9, is characterized in that, this data, services protocol stack also comprises:
Interface layer, also for carrying out the operation of digital signature to described SOAP packet or HTTP packet, carries out digital signature identification and data deciphering to SOAP packet or HTTP packet.
The method for designing of 11. protocol stacks according to claim 9, is characterized in that, this data, services protocol stack also comprises:
Interface layer, also for data, services externally being issued, being supplied to service requester and calling, and by the access that ESB control data is served, realizes the integrated and unified control of data, services.
The method for designing of 12. protocol stacks according to claim 9, is characterized in that, this data, services protocol stack also comprises:
Model Mapping layer, also for the mapping of the data model and data base data model that realize data, services.
The method for designing of 13. 1 kinds of data, services protocol stacks, is characterized in that, this data, services protocol stack comprises:
Articulamentum, for obtaining service data in database;
Model Mapping layer, for being converted to relational data by described service data;
Presentation layer, for being packaged into extensible markup by described relational data;
Session layer, for knowing the type of interaction of service, extensible markup is forwarded to service layer by the type of interaction according to service;
Service layer, for being encapsulated in the inclusion of SOAP packet or HTTP packet by described extensible markup;
Interface layer, for carrying out the encapsulation operation of the control information that response result, response time, encoding the response and response describe to the packet header of described SOAP packet or HTTP packet.
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 CN103117983A (en) | 2013-05-22 |
| CN103117983B true 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) |
Families Citing this family (20)
| 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 |
| CN110324837B (en) * | 2018-03-29 | 2022-03-08 | 中兴通讯股份有限公司 | Network management method and device |
| CN115426391A (en) * | 2018-05-31 | 2022-12-02 | 华为技术有限公司 | Remote procedure call protocol self-adaption method, related device and server |
| CN109117152B (en) * | 2018-07-26 | 2022-02-25 | 新华三大数据技术有限公司 | Service generation system and method |
| 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 |
| CN111683148B (en) * | 2020-06-09 | 2023-01-31 | 吉林亿联银行股份有限公司 | Service processing system and method, service publishing method |
| CN115017128B (en) * | 2022-05-26 | 2023-02-10 | 上海介方信息技术有限公司 | Lightweight log service design method and system based on CORBA middleware |
| CN117494163B (en) * | 2023-11-06 | 2024-05-31 | 深圳市马博士网络科技有限公司 | Data service method and device based on security rules |
| CN117436053B (en) * | 2023-12-20 | 2024-02-23 | 永鼎行远(南京)信息科技有限公司 | Data service bus system and data authentication transmission method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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) |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EA015549B1 (en) * | 2003-06-05 | 2011-08-30 | Интертраст Текнолоджис Корпорейшн | Interoperable systems and methods for peer-to-peer service orchestration |
-
2011
- 2011-11-16 CN CN201110362878.6A patent/CN103117983B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
|---|
| Implementation of Web Services Composition System Based on SOA;shujun Pei 等;《2011 International Conference on Uncertainty Reasoning and Knowledge Engineering (URKE)》;20110807;第2卷;第82-85页 * |
| 基于SOA架构的Web服务组合系统;高岩 等;《小型微型计算机系统》;20070430;第28卷(第4期);第729-733页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103117983A (en) | 2013-05-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103117983B (en) | The method for designing of data service request answer method and data, services protocol stack | |
| CN108650262B (en) | Cloud platform expansion method and system based on micro-service architecture | |
| US10957326B2 (en) | Device identifier dependent operation processing of packet based data communication | |
| CN112862612B (en) | Method and device for transmitting resources across chains | |
| CN108306877B (en) | NODE JS-based user identity information verification method and device and storage medium | |
| CN108521858B (en) | Device identifier dependent handling of operations for packet-based data communication | |
| CN112003703B (en) | Method and device for transmitting authenticatable message across chains | |
| US20200177572A1 (en) | Sending cross-chain authenticatable messages | |
| CN111083220B (en) | Method for providing financial service application | |
| WO2021203853A1 (en) | Key generation method, device, apparatus, and medium | |
| CN103139234B (en) | A kind of device and method of data, services encapsulation | |
| CN101334887B (en) | Financial data-handling process and bank enterprise platform device | |
| CN114978638B (en) | Block chain cross-chain supervision method based on shared node | |
| CN113409047B (en) | Data processing method, device and equipment based on block chain and readable storage medium | |
| CN106656919B (en) | A kind of session analytic method and system based on Telnet agreement | |
| CN111885133A (en) | Data processing method and device based on block chain and computer storage medium | |
| EP2262166A1 (en) | Method, system and apparatus for realizing combined charging service | |
| CN109800557A (en) | Integrated processing method, device, server, equipment and medium based on block chain | |
| CN114598531B (en) | Identity authentication method and equipment | |
| KR102051839B1 (en) | Methods for processing a message in M2M system and Apparatuses thereof | |
| CN112615838B (en) | Extensible block chain cross-chain communication method | |
| CN111901384B (en) | System, method, electronic device and readable storage medium for processing message | |
| CN117294763A (en) | Cloud desktop terminal management method for forwarding terminal request information based on proxy service | |
| CN109413053B (en) | Method for user state verification in service grid | |
| CN102480475A (en) | Web service safety access control method, apparatus and system 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 |