CN101645785A - Data-intensive multimedia service calling method based on extended SOAP - Google Patents
Data-intensive multimedia service calling method based on extended SOAP Download PDFInfo
- Publication number
- CN101645785A CN101645785A CN200910083304A CN200910083304A CN101645785A CN 101645785 A CN101645785 A CN 101645785A CN 200910083304 A CN200910083304 A CN 200910083304A CN 200910083304 A CN200910083304 A CN 200910083304A CN 101645785 A CN101645785 A CN 101645785A
- Authority
- CN
- China
- Prior art keywords
- soap
- service
- data
- annex
- expansion
- 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
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a data-intensive multimedia service calling method based on an extended SOAP, wherein, the involved entity comprises an extended SOAP client side and an extended SOAP server side. The calling method comprises the following steps: 1) the client side sends an extended SOAP request message to the server side, the message comprises a message main body part and an attachment part, and the message main body comprises a request service name, a request service parameter name, a request service instance value, and association relationship between the parameter name and the attachment; and the attachment part comprises an attachment entity correlated to the request service parameter name, and the attachment entity comprises attachment metadata information and binary data contained in an attachment file; 2) the server side receives the extended SOAP request message and calls a performance function corresponding to the request service in the message to obtain a computing result, and the computing result comprises a function return value which needs to be returned and some possibly processed attachment data; and 3) the server side returns a SOAP feedback message to theclient side, and the message carries the computing result obtained in step 2).
Description
Technical field
The present invention relates to the Internet Web service technical field, more specifically, the present invention relates to a kind of data-intensive multimedia service call method based on expansion SOAP.
Background technology
Owing to need handle to the multimedia audio-video data, often comprise continuous in the multimedia service and aspect time and space two the very strong data flow of correlation, be a kind of typical data-intensive business.Based on this reason, multimedia application is at present realized with single, tightly coupled holonomic system mode at large.This make multimedia service foundation, maintenance, upgrading and and and the integrated of other business be the difficult problem more thorny, expensive, that time consumption is huge always.Except that multimedia service, data-intensive business also comprises Data Hosting, large-scale data analysis such as data excavation application etc., and also there is the problem with other business integration difficulties in these data-intensive business.
On the other hand, Service-Oriented Architecture Based (Service Oriented Architecture, be called for short SOA) provide the service of a kind of dynamic combined as required to form the method for integrated service, it is based on according to the predefined interface of standard, allow to carry out between distributed and the isomery assembly loosely connected, be a kind of more robust and the large scale system method for designing that is easy to expand, successfully provide more flexible solution for numerous large-scale application system.Under the INTERNET environment, Web Service technology obtains the support of admitting and obtain numerous software giants such as IBM, Microsoft etc. of academia as a kind of implementation of SOA.Web Service is made up of a series of standards based on XML, as SOAP, UDDI and WSDL etc., in fact it defined a kind of remote object interaction models of platform independence, and the core that realizes this model is simple object request protocol (Simple Object AccessProtocol is called for short SOAP).Therefore, if Web Service can be applied to the multimedia service field, make up a kind of distributed multimedia application system of supporting Service-Oriented Architecture Based, then can solve effectively multi-media service system exploitation, safeguard the difficult problem with aspects such as reaching and other operation systems are integrated.
But, Web Service technology is to be suggested as the solution that the INTERNET transactions classes is used (as ecommerce) at first, what be primarily aimed at is the less text data business of data scale of input parameter, very weak for the multimedia service support that relates to jumbo binary data.One of them key reason is exactly that data generally will be as the process object of program in the multimedia application, and for example transcoding service Central Plains video file must offer service as parameter.And existing SOAP and expansion thereof can't be supported large-scale data is encapsulated in its message body input as remote procedure call as parameter effectively.
World Wide Web Consortium (W3C) has defined two standards of carrying annex in SOAP: band annex soap message (SOAP Message with Attachment) and XML binary data optimization packing (XML-binaryOptimized Packages, XOP) standard.These two standards are all based on multipurpose internet mail expansion (Multipurpose Internet Mail Extensions, MIME) agreement, the binary data that annex comprised the time will at first use base64 to be encoded to text in transmission to transmit as the part in the MIME envelope then, and soap message itself is as another part.Because binary data is carried out the base64 coding can increase by 1/3 data volume, this practice will cause serious data to expand when annex is very big, cause unnecessary network resource consumption; And owing to whole annex will be read in internal memory and pack, internal memory will be found in experiment when annex is big by totally when annex is very big, based on the system of these two standards extremely instability that begins to become.On the other hand, based on these two kinds of method call services, the role of perception annex (being the effect of being played of annex) handles thereby can't carry out automation automatically, particularly exists under the situation of a plurality of annexes, and this deficiency highlights more.At last, based on this feature of MIME, destroyed the independence of SOAP standard itself.Therefore above-mentioned two standards both can't compatible existing Web Service model, can not fully support the data-intensive application of this class of multimedia service.
Moreover, often relating to the copyright safety of digital content in the multimedia service, present Web Service system can't provide an efficient content protection scheme.The safety of soap message mainly depends on the WS-Security standard at present, mainly obtains safety guarantee by the mode that message body is encrypted fully, and this is feasible when data volume is little.But for multimedia application; because multi-medium data is hundreds of more than million through being everlasting; adopt complete cipher mode cost too big; the correlation that the while multi-medium data is compared with text data between its data is very strong, adopts suitable cipher mode generally can reach the effect that an encryption section data can reach the whole data file of protection.
Summary of the invention
The objective of the invention is, SOAP is expanded, in soap message, introduce the relation mechanism of parameter and annex, make that SOAP can support large-scale data is encapsulated into the input of calling as remote service in the soap message body as parameter, thereby a kind of data-intensive multimedia service call method based on expansion SOAP is provided.For achieving the above object, the data-intensive multimedia service call method based on expansion SOAP provided by the invention, the entity that relates to comprise expansion SOAP client and expansion SOAP server end, and described multimedia service call method comprises the steps:
1) expansion SOAP client sends expansion SOAP request message to expansion SOAP server end, described expansion SOAP request message comprises source body part and accessories section, described source body partly comprises the title of the service of asking, the parameter name and the example value of the service of asking, and the incidence relation of described parameter name and annex; Described accessories section comprises the annex entity of asking the parameter name of service to be associated with described source body part, and described annex entity comprises the binary data that annex metadata information and attachment files are comprised;
2) expansion SOAP server end receives described expansion SOAP request message, call the power function of institute's requested service correspondence in this request message and obtain result of calculation, described result of calculation comprises the function return value that need return and reaches some possible treated attachment data;
3) expansion SOAP server end returns expansion SOAP feedback message to expansion SOAP client, and described expansion SOAP feedback message carries step 2) in the result of calculation that obtains.
In the technique scheme, during describing, the WSDL of described service indicates the parameter in this service and the incidence relation of annex.
In the technique scheme, the WSDL of described service comprises element: Relation, Parameter and Note in describing; Described Relation, Parameter and Note are used for indicating at WSDL the incidence relation of parameter and annex; Want the parameter of associated attachment for each, in the WSDL document of service, generate the Relation element of a correspondence; First daughter element of Relation element is the Parameter element, and the value of Parameter element is service some in the defined input parameter; Second daughter element of Relation element is the Note element, and this element is this related descriptive information, indicates this related implication.
In the technique scheme, the entity that relates to also comprises application program, before the described step 1), also comprises the steps:
The application program launching service invocation procedure, indicate service invocation information to expansion SOAP client, described recalls information comprises that the WSDL of the service of being called describes or its address, the title of the service of calling, the example value of each input parameter of the service of calling, and the incidence relation of the parameter of form and annex.
In the technique scheme, in the described step 1), described expansion SOAP client is according to the described expansion of the specified information structuring of described application program SOAP request message.
In the technique scheme, described expansion SOAP request message is transmitted to expansion SOAP server end by Web server.
In the technique scheme, in the described step 1), described expansion SOAP client at first sends the source body part, and then sends accessories section.
In the technique scheme, in the described step 3), when described result of calculation comprises annex, described expansion SOAP feedback message comprises source body part and accessories section, when described result of calculation did not comprise annex, described expansion SOAP feedback message comprised the source body part, does not comprise accessories section; In the described step 3), expansion SOAP server end at first sends the source body part, inquires about whether comprise annex in the result of calculation then, when comprising annex, described expansion SOAP server sends accessories section, otherwise, disconnect with described and expanding being connected of SOAP client.
In the technique scheme, described accessories section carries out encrypted transmission, encryption method is to use a global secret that the data in the data block are selectively encrypted, and uses a streaming key corresponding with each data block to the encryption (described staggered be meant upset putting in order of original binary data bit string) that interlocks of each data block.
Compared with prior art, the present invention has following technique effect:
1, the present invention is based on the SOAP model and realize data-intensive business (especially multimedia service), can compatible Web Service existing standard, help the maintenance and the upgrading of operation system.
2, optimizing packaging technique with band annex soap message with the XML binary data compares, the present invention does not need binary data is transcoded into text and packing, what can not cause happening suddenly a large amount of internal memories in ground takies the stand-by period that the present invention has simultaneously greatly reduced service call.
3, the present invention brings the protection of digital content into whole multimedia service call framework, has significantly improved encryption efficiency.
Description of drawings
Fig. 1 is expansion SOAP client and the mutual sequential example of server end in service invocation procedure;
Fig. 2 is for expanding the SOAP server to calling the processing of request flow chart.
Embodiment
The present invention expands SOAP by introduce new semantic feature in SOAP on the basis of compatible Web Service existing standard, makes it can support to carry the large scale multimedia data and carries out the remote object visit; Defined with existing standard fully compatible new end node soap message interactive mode---current interactive mode is its subclass, and providing a kind of method that realizes this interaction models based on http protocol, the present invention has provided the Service-Oriented Architecture Based implementation strategy of a multimedia service on this basis.Below in conjunction with the drawings and specific embodiments the present invention is done description further.
Embodiment
Model definition
SOAP can be divided into request and feed back two parts as a kind of remote object invocation method, the title and the parameter that mainly comprise the service of to call in the request message, feedback message then comprises the service compute result of client expectation, more popular understanding can think that service is a function, and it then is the result of function call that the instruction SOAP feedback of calling this function is promptly sent in the SOAP request.Obviously, under this computation model, passing into as parameter large-scale binary system multi-medium data, function is unrealistic.In general programming model, allowing function handle large-scale data if desired is the FLV form with the film transcoding of an AVI coding for example, generally be that get up then name with file of storage is referred to as parameter and passes to function, thereby make function can index this document and handle.The defined SOAP expansion of present embodiment comes from this thought.The formalized description of the remote object Access Model that present embodiment is expanded is as follows:
Defining 1: one expansion SOAP request is one 4 tuple: (N, M, P, R), wherein N is the NameSpace of service; M is the title of service; P is the parameter sets of service, and its element is two tuples: (wherein pj is a parameter name for pj, vj) (j 〉=0), and vj is the example value of pj; The set of the incidence relation of R annex and parameter, its element is two tuples: (am, fm) (m 〉=0), wherein ak ∈ p1, p2 ..., (k≤m), fk is the annex relevant with parameter ak to pj}; With | ak| and | fk| represents the occurrence number in R among ak and the fk respectively, requires ak to satisfy | ak| 〉=0, fk must satisfy | fk| ∈ 0,1}.
According to this definition, when R is sky, the defined expansion of present embodiment SOAP request will deteriorate to the SOAP request of standard, so standard SOAP request is actually a special case expanding the SOAP request.
Defining 2: one expansion SOAP feedbacks is one 4 tuples: (N ', M ', V, R '), wherein N ' is the NameSpace of service; M ' is the title of the service of this feedback of generation, must be corresponding with the M in the definition 1; V is the return value of service; R ' is the incidence relation set of annex and parameter, and it defines same R.
Because feedback is based on request, therefore defining 2 is what to rely on definition 1.Obviously, above-mentioned expansion is complete compatible current SOAP standard.Based on these two definition, provide concrete expansion soap message form below.
Message format
Soap message generally transmits by http protocol at present, and soon soap message is encapsulated in the http data bag and transmits.Can make soap message pass through most fire compartment wall by the HTTP transmission, thereby increase the availability of Web Service; On the other hand, can make it support Web Service to use, avoid special server being set for Web Service by in general Web server, increasing the SOAP processing module.In view of the above-mentioned advantage of SOAP HTTP binding, expansion soap message defined herein still uses http protocol to transmit.An expansion SOAP request message example of using HTTP POST mode to submit to according to definition 1, as follows:
POST/UpLoadService.ews?HTTP/1.1
Host:?www.tempuri.org
Content-Type:?text/xml；charset＝utf-8
Content-Length:?length
SOAPAction:″http://tempuri.org/UploadMovie″
<？xml?version＝″1.0″encoding＝″utf-8″？>
<esoap:Envelope
xmlns:xsi＝″http://www.w3.org/2001/XMLSchema-
instance″?xmlns:xsd＝″http://www.w3.org/2001/
XMLSchema″?xmlns:esoap＝″http://dsp.ac.cn/enhanced-
soap/envelope/″>
<esoap:Body>
<UploadMovie?xmlns＝″http://tempuri.org″>
<Provider>China?Movie?Group</Provider>
<Name>Warm?Spring</Name>
<Prevue>Girl，don’t?cry！</Prevue>
<Tag>China?story?</Tag>
</UploadMovie>
<esoap:Attachments>
<Name>
<esoap:File>video-cd1.avi</esoap:File>
<esoap:?File>video-cd2.avi</esoap:?File>
</Name>
<Prevue>
<esoap:File>summary.flv</esoap:File>
</Prevue>
</esoap:Attachments>
</esoap:Body>
</esoap:Envelope>
--?attachment?part--
Message shown in the top code is one and uploads the movie services request message.This message comprises two parts: http protocol header and expansion SOAP request message.Wherein the HTTP head has indicated the address of service: " www.tempurl.org/UpLoadService.ews ", it in fact indicated the SOAP server the serviced component that should load, Dui Ying assembly is " UpLoadService.ews " in this example, and the service that call must define in this assembly.Expansion SOAP request message comprises two parts: source body and accessories section.Above only listed the main part of message, accessories section will provide hereinafter.Source body indicates the method that will call and is " UploadMovie ", and it has four parameter: Provider, Name, Preview and Type, represents supplier, title, trailer title and the affiliated classified information of film respectively; Wherein parameter N ame and Preview associated attachment, the i.e. video file of the video file of film and trailer.The Attachments element is used to define the annex set relevant with call method, and its daughter element must be the title of parameter, and each parameter can related one or more annexes, and each annex uses File element to state.In the above example, related two annexes of parameter N ame are respectively video-cd2.avi and video-cd2.avi, and they are two video files will uploading the film correspondence; The related annex summary.flv of parameter Preview, it is the video file of film trailer correspondence.
For each annex that in expansion soap message main body, indicates, the entity of a correspondence must be arranged at the accessories section of message.The entity part of annex video-cd1.avi is as follows in the expansion of example above SOAP request message:
--boundary--
Content-Type:video/avi
Content-Length:987786786
filename:video-cd1.avi
EBS:4096
Encryption-Algorithm:AES
Encryption-Key:ewefj＊78y78JKJHHhjhff...
Key-Size:128
Encryption-Intensify:10％
--boundary-
binary?data(of?video-cd?1.avi)
…
The situation of two annexes is similar in addition.Each annex entity comprises two parts information: the binary data that annex metadata information and attachment files are comprised.There is the border between this two parts information, also has the border between the different annex entities.With band annex SOAP and XML binary system optimization packing data method binary data being transcoded into text is bundled in the soap message body different, present embodiment sends for the content partition packetization that different boundary separates, and adopts direct send mode for binary data.In the metadata part, territory Content-Type is used to represent the file type of annex, and document type definition is according to the MIME medium type; Territory Content-Length is used to represent the size of annex, and unit is a byte; Territory filename is the name of attachment files, and this name must occur in the File of source body element.Set up for the protection content of multimedia in last 5 territories.Because content of multimedia relates to copyright problem, safe class is higher, so present embodiment considered safety problem in the lump when the interaction models of definition service and client, specifically will introduce hereinafter.Data block size when territory EBS is the annex encryption is that server is necessary to the annex deciphering; Territory Encryption-Algorithm is the cryptographic algorithm that annex is adopted when carrying out encryption; Territory Encryption-Key is the key that cryptographic attachment adopted, and adopt the symmetric cryptography mode for attachment content, but key transmits with the ciphertext form; Territory Key-Size is a key length; Territory Encryption-Intensity has defined Cipher Strength, and it has defined which bit in the encrypted data chunk with encrypted.
Service end after calling respective service and obtaining result of calculation, will send feedback message according to the expansion SOAP request message of client to client, and this message also may comprise annex.One is as follows based on the expansion SOAP feedback message example of HTTP binding according to definition 2:
…
<Name>String</Name>
<Prevue>String</Prevue>
…
</UploadMovie>
<Attachments>
<Relation>
<Parameter>Name</Parameter>
<Note>using?for?specifying?the?video
files?of?the?movie
</Note>
</Relation>
<Relation>
<Parameter>Prevue</Parameter>
<Note>using?for?specifying?the?video
file?of?the?movie?abstract
</Note>
</Relation>
</Attachments>
…
Message shown in the top code is the feedback message of a video code conversion service, and the title of service is VideoTranscode, and the return value of service is the success of true respresentation transcoding, and this is consistent with standard SOAP; Also having comprised two annexes in the return results, is exactly the video file that transcoding obtains afterwards, uses the parameters C ontentId of service definition to carry out association.Attachment format in feedback message accessories section form and the request message is on all four, repeats no more.
Indicate which parameter during developer of services must be described at the WSDL of its service and will be associated with annex, and must carry out note to the implication of this association, for example effect of the annex of explanation and certain parameter association.So, the service call person can understand the method that the input data are provided to service by the WSDL description of checking service before the service of calling.In this way, when the WSDL that meets service at expansion SOAP request message described, service can automation determined each role who submits annex to (promptly determining the effect that each submits annex to) and handles.For example, in example above, service may be encrypted the annex of Name parameter association, does not then do this processing for the annex of Preview parameter association.For making WSDL can support the accessory association statement of service parameter, present embodiment is expanded the WSDL standard.If service needs caller to provide with attachment version in the return results of data or service and comprises parameter, then must in describing, its WSDL indicate the incidence relation of parameter and annex.For this reason, present embodiment is expanded WSDL, has introduced 3 new elements, is respectively Relation, Parameter and Note.It is as follows with the method for the incidence relation of annex to indicate parameter based on these three elements in WSDL: (1) wants the parameter of associated attachment to generate a corresponding Relation element in the WSDL document of service for each; (2) first daughter element of Relation element must be the Parameter element, and the value of Parameter element is service some in the defined input parameter; (3) second of the Relation element daughter element must be the Note element, and this element is this related descriptive information, indicates the implication of this kind association.The service describing fragment corresponding with expansion SOAP request corresponding with service " UploadMovie " in the example above is as follows:
HTTP/1.1?200?OK
Content-Type:text/xml；charset＝utf-8
Content-Length:length
<？xml?version＝″1.0″encoding＝″utf-8″？>
<esoap:Envelope
xmlns:xsi＝″http://www.w3.org/2001/XMLSchema-instance″
xmlns:xsd＝″http://www.w3.org/2001/XMLSchema″
xmlns:esoap＝″http://dsp.ac.cn/enhanced-soap/envelope/″>
<esoap:Body>
<VideoTranscodeResponse?xmlns＝″http://tempuri.org″>
<VideoTranscodeResult>True</VideoTranscodeResult>
</VideoTranscodeResponse>
<esoap:Attachments>
<ContentId>
<esoap:File>video_cd1_trans.flv</esoap:File>
<esoap:File>video_cd2_trans.flv</esoap:File>
</ContentId>
</esoap:Attachments>
</esoap:Body>
</esoap:Envelope>
--attachment?part--
In the foregoing description fragment Attachments element content for expansion SOAP request corresponding parameter-accessory association contextual definition.For each parameter accessory association set of relationship, usually define by a Relation unit, this element comprises two daughter elements, wherein Parameter indicates parameter name (must be the parameter of service), Note describes this related implication, having indicated the parameter of wanting associated attachment by the Parameter element in first Relation element above is Name, and to indicate the annex that is associated with this parameter by the Note element be the video file of film.The service call person describes to judge whether service request needs to carry accessory information by the WSDL that checks service before the service of calling, and obtains whether to comprise annex among the service feedback result.
Service invocation procedure
Above provide the form of expansion soap message, provided when carrying out multimedia service and calling the reciprocal process of client and service end now.At first be defined as follows system entity: (1) application program: the consumer of multimedia service; (2) expansion SOAP client: be used to application program that transparent service call is provided; (3) http server: the access point that service is provided for application program; (4) expansion SOAP server end: a module that is embedded in the http server, be specifically designed to expand the SOAP client mutual, finish service invocation procedure; (5) service: finish some functional programs modules.In these entities, in fact expansion SOAP client is not an independent entity, and it is embedded in the application program.Provide the reciprocal process of each entity in the service invocation procedure below based on accompanying drawing 1:
The function C allService that the consumer of step 1, service (may be application program, business process engine or other services etc.) provides by invoke extensions SOAP client (being designated hereinafter simply as EC) starts the invoked procedure of a service, application program must be in this function indicates content aspect four as its input parameter for EC: 1. the WSDL of the service that will call describes or its address, 2. will call the title of service; 3. to call the example value of each input parameter of service; 4. the form with [parameter name, annex] indicates the related annex of wanting;
Step 2, EC are at this call request, at first whether the analysis application input parameter is accurate, whether the main service name that will call of checking exists in specified service describing, with and parameter whether have omission, specified parameter accessory association relation whether to follow service describing etc., if check not by return the input parameter error message to application program; Otherwise EC calls the GenESQMainpart function and begins structure expansion SOAP request message main body, sends this service invocation request according to the address of service of binding in the service WSDL description after structure is finished; After sending this request, do not need annex if indicate in this invoked service, then EC enters to receive and calls the feedback message state, otherwise forwards step 5 to;
After the Web server at step 3, service place receives this request, at first check the type of this request,, handle otherwise this request is transmitted to expansion SOAP server module (being designated hereinafter simply as ES) if not replying voluntarily;
Step 4, ES call MPAnalyze Functional Analysis request message main body, if this message does not contain annex, then change step 10; Otherwise it is right that ES generates a public-key cryptography, and PKI is sent to EC, and ES waits for and receives the annex that EC sends;
Step 5, EC wait for that ES sends the needed PKI of this session, and receive this PKI, and i=1 is set;
Step 6, EC at first are that i specified annex of application program generates encryption key, call the value that the GenFileMetadata function generates each territory of annex metadata information afterwards, wherein encryption key uses the PKI of ES transmission to encrypt, and after generation is finished this message is sent to ES;
After step 7, ES receive the annex metadata information, call the information that the GetAttachmentInfo function parses each corresponding domain, and use the right private key of its 4th step institute PKI that generates that the encryption key of annex is decrypted, begin to wait for the reception binary data that annex comprised thereafter;
Step 8, EC order from attachment files reads the data block of EBS territory indication size, send to ES after using the annex encryption key to encrypt the back, ES uses its annex encryption key that parses to be decrypted and to store after receiving this data block, and this process continues to carry out to finish until whole attachment data transmission---and ES determines according to the size of annex whether this annex receives; The algorithm that the attachment data piece is encrypted in this step is as follows:
The secret key of encryption of supposing annex is K (K is at least 128), is shown as A by sequence list from left to right
1A
2... A
N, A wherein
iComprise (i-1) * 64 among the K to i * 64-1 bit, establish M=A
NOr A
N-1, C
-2=A
1, C
-1=A
2, m (0≤m) individual encryption key C then with the attachment data piece that is sent out
mCalculate acquisition by following formula:
C
m(C
m-1+C
m-2)Mod?M，m≥0 (1)
Acquiescence is converted to corresponding signless integer with Bit String when carrying out add operation in the above-mentioned formula.Calculate C
mAfter, the algorithm (e as follows that m data block encrypted
mFor with encrypted data block):
Algorithm?StreamEP?UEncrypt(SharedKey:K，
PrivateKey:c
m，EPU:e
m)
begin
EcryptionEPU(K，e
m).
D＝uint(c
m).
N＝e.Length().
while(D＞0)
R＝D?Mod?N.
D＝D/N.
end?while
end
Function EcryptionEPU (K, e have been called in the above-mentioned algorithm
m), this function is used for enciphered data is carried out preliminary treatment, is actually the process of a scrambling, specific algorithm following (EI is the specified Cipher Strength value of annex metadata information territory Encryption-Intensity):
Algorithm?EcryptionEPU(EncryptionKey:K，
EPU:e)
begin
uint?loop＝(K.Length())×(uint)(100/EI).
b＝0.
while(b＜e.Length())
t＝e.Length()-b.
r＝t＞K.Length()？K.Length()，t.
for(i＝0；i＜r；i++)
e
b+i＝e
b+i?Xor?K
i.
end?for
b＝b+loop.
end?while
end
Whether step 9, inspection also have other annex to send, if i=i+1 is set and forwards step 6 to, otherwise represent that whole expansion SOAP request receives, and changes next step;
Step 10, in expansion SOAP request, extract service place module title, be called this module of parameter call ServiceModelarLoad function dynamic load in ES with this name;
Step 11, extracting the title of the service of calling and the value of each parameter in expansion in the soap message, be that parameter is called corresponding function in the rapid institute of previous step load-on module with it, and the return value of acquisition function;
In the multimedia application field, annex is very general as the input data of function, this causes the SOAP of the present standard of mutual ratio between SOAP server and the service place assembly of expanding to call far away from complicated: at first accessory information must effectively pass to service, if secondly comprise annex then serve also and accessory information must be offered server in the service return results.For this reason, present embodiment requires the class at service (function) place to develop according to following masterplate:
public?class?ClassName
{
public?ClassName(string?ESQMB)
{ ...... }
public?string?GetAttachmentInfo()
{ ...... }
......//service?functions
}
Promptly at first necessary constructing definitions function, to pass to service as parameter by this function expansion SOAP server through the SOAP request message head of renewal (mainly being that the routing information of annex in server added in the Attachment element) by this function, and make the service can the access annex with this; Secondly, must define the GetAttachmentInfo function, expansion SOAP server is by calling in this functional query service feedback whether comprise annex;
Step 12, ES call function GenESSMainPart produce service call feedback message head and send to EC, ES call function GetAttachmentInfo checks whether service has the annex person that need return to the service call then, if there is not annex to return, ES directly closes and being connected of EC, and closes this connection (if having annex to return then the process of transmitting of annex and top EC to send annex consistent to the process of ES) behind the annex otherwise send;
Step 13, EC extract and call the result and return to application program after receiving the expansion SOAP request feedback message of ES transmission, finish service invocation procedure;
Accompanying drawing 1 has provided a service call example sequential chart based on said process, has all comprised an annex in service request and the feedback in this example.The main activities of server end is listed in accompanying drawing 2 in the above-mentioned service invocation procedure.Server end is a general http protocol server that comprises expansion SOAP service processing unit.Behind the startup of server, begin to intercept request, if this request is service invocation request then will be handled by expansion SOAP service processing unit from client.Expansion SOAP processing unit is at first analyzed request message, if comprise annex in this request then start the annex receiving course.At first expanding the SOAP processing unit, to generate the public-key cryptography be used for this session right, and PKI is sent to client, and client will be used the symmetric cryptographic key of this each annex of public key encryption.The receiving course of each annex comprises two steps: (1) receives the annex metadata information that client sends, and extracts information such as receiving required key of attachment data and file size; (2) according to the block size that indicates in the annex metadata information, block-by-block receives and deciphers the binary data of annex, until the file size of appointment.Specified service loads corresponding software module according to service request after receiving all annexes, finishes calling of service respective function, and the result that calls that will serve encapsulates generation service feedback information and sending to client.If comprise annex in the feedback message, after then expanding the SOAP processing unit and sending the feedback message head, begin to wait for that client sends its PKI (behind the client reception feedback message head, comprise annex if find in the feedback message by analysis, it is right that then it will generate the used public-key cryptography of this session, and PKI is sent to expansion SOAP processing unit); After receiving this PKI, use following steps to send to each annex that need send: (1) generates an annex and encrypts used symmetric key, and uses and receive public-key cryptography and encrypt, and constructs the annex metadata information afterwards, and sends to client; (2) according to enciphered data block size specified in the annex metadata information, block-by-block reads and sends to client after attachment data is encrypted, until sending all attachment datas.
The present invention has provided a kind of expansion SOAP model of the data-intensive multimedia service far call of support of compatible Web Service existing standard, the method that provides based on this model can in the carrying out of multimedia service, adopt the Service-Oriented Architecture Based technology by the mode of service combination develop rapidly new business with and carry out integrated with the information service of other types; While, owing to each functional unit (service) relatively independent (loose coupling), this helped reducing the maintenance and the upgrade cost of system under Service-Oriented Architecture Based.Optimizing packaging technique with band annex soap message with the XML binary data compares, adopt method that the present invention provides to call carrying out data-intensive multimedia service, owing to do not need binary data is transcoded into text and packing, the stand-by period of greatly having reduced service call simultaneously that takies of a large amount of internal memories in ground that therefore can not cause happening suddenly.In realization of the present invention system, shorten more than 50% for its stand-by period of same service.On the other hand; the present invention brings the protection of digital content into whole multimedia service call framework; avoided using WS-Security to carry out overall message and encrypted the poor efficiency of being brought, can make application designer break away from complicated content safety subject under discussion simultaneously, monograph designs in business.Based on strong this feature of multi-medium data temporal correlation, the present invention uses data bit staggered in conjunction with XOR, reaches the encipher only partial data and obtains near the effect of encrypting (from the angle of content decoding) fully; And the user can be provided with different Cipher Strengths according to different content ratings, and general Cipher Strength can reach the effect of encrypting fully about 30%, carries out complete encryption method with employing AES this moment and compares, and can save for about 80% data encryption time.
Claims (9)
1, a kind of data-intensive multimedia service call method based on expansion SOAP, the entity that relates to comprise expansion SOAP client and expansion SOAP server end, and described multimedia service call method comprises the steps:
1) expansion SOAP client sends expansion SOAP request message to expansion SOAP server end, described expansion SOAP request message comprises source body part and accessories section, described source body partly comprises the title of the service of asking, the parameter name and the example value of the service of asking, and the incidence relation of described parameter name and annex; Described accessories section comprises the annex entity of asking the parameter name of service to be associated with described source body part, and described annex entity comprises the binary data that annex metadata information and attachment files are comprised;
2) expansion SOAP server end receives described expansion SOAP request message, call the power function of institute's requested service correspondence in this request message and obtain result of calculation, described result of calculation comprises the function return value that need return and reaches some possible treated attachment data;
3) expansion SOAP server end returns expansion SOAP feedback message to expansion SOAP client, and described expansion SOAP feedback message carries step 2) in the result of calculation that obtains.
2, the data-intensive multimedia service call method based on expansion SOAP according to claim 1 is characterized in that, indicates the parameter in this service and the incidence relation of annex during the WSDL of described service describes.
3, the data-intensive multimedia service call method based on expansion SOAP according to claim 2 is characterized in that, the WSDL of described service comprises element: Relation, Parameter and Note in describing; Described Relation, Parameter and Note are used for indicating at WSDL the incidence relation of parameter and annex; Want the parameter of associated attachment for each, in the WSDL document of service, generate the Relation element of a correspondence; First daughter element of Relation element is the Parameter element, and the value of Parameter element is service some in the defined input parameter; Second daughter element of Relation element is the Note element, and this element is this related descriptive information, indicates this related implication.
4, the data-intensive multimedia service call method based on expansion SOAP according to claim 3 is characterized in that the entity that relates to also comprises application program, before the described step 1), also comprises the steps:
The application program launching service invocation procedure, indicate service invocation information to expansion SOAP client, described recalls information comprises that the WSDL of the service of being called describes or its address, the title of the service of calling, the example value of each input parameter of the service of calling, and the incidence relation of parameter and annex.
5, the data-intensive multimedia service call method based on expansion SOAP according to claim 4, it is characterized in that, in the described step 1), described expansion SOAP client is according to the described expansion of the specified information structuring of described application program SOAP request message.
6, the data-intensive multimedia service call method based on expansion SOAP according to claim 1 is characterized in that, described expansion SOAP request message is transmitted to expansion SOAP server end by Web server.
7, the data-intensive multimedia service call method based on expansion SOAP according to claim 1 is characterized in that in the described step 1), described expansion SOAP client at first sends the source body part, and then sends accessories section.
8, the data-intensive multimedia service call method based on expansion SOAP according to claim 1, it is characterized in that, in the described step 3), when described result of calculation comprises annex, described expansion SOAP feedback message comprises source body part and accessories section, when described result of calculation did not comprise annex, described expansion SOAP feedback message comprised the source body part, does not comprise accessories section; In the described step 3), expansion SOAP server end at first sends the source body part, inquires about whether comprise annex in the result of calculation then, when comprising annex, described expansion SOAP server sends accessories section, otherwise, disconnect with described and expanding being connected of SOAP client.
9, according to claim 7 or 8 described data-intensive multimedia service call methods based on expansion SOAP, it is characterized in that, described accessories section carries out encrypted transmission, encryption method is to use a global secret that the data in the data block are selectively encrypted, and uses a streaming key corresponding with each data block to the encryption that interlocks of each data block.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100833048A CN101645785B (en) | 2009-04-30 | 2009-04-30 | Data-intensive multimedia service calling method based on extended SOAP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100833048A CN101645785B (en) | 2009-04-30 | 2009-04-30 | Data-intensive multimedia service calling method based on extended SOAP |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101645785A true CN101645785A (en) | 2010-02-10 |
| CN101645785B CN101645785B (en) | 2011-12-07 |
Family
ID=41657511
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009100833048A Expired - Fee Related CN101645785B (en) | 2009-04-30 | 2009-04-30 | Data-intensive multimedia service calling method based on extended SOAP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101645785B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102970378A (en) * | 2012-12-13 | 2013-03-13 | 中国电子科技集团公司第十五研究所 | Binary data optimized transmission system |
| CN104270470A (en) * | 2014-10-24 | 2015-01-07 | 杭州高达软件系统股份有限公司 | Remote service invocation method, device and system |
| CN104270472A (en) * | 2014-10-24 | 2015-01-07 | 杭州高达软件系统股份有限公司 | Remote service invocation method, device and system |
| CN108600023A (en) * | 2018-05-02 | 2018-09-28 | 山东浪潮通软信息科技有限公司 | A kind of SOAP transmitters, SOAP receivers, data transmission method and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100737801B1 (en) * | 2004-12-30 | 2007-07-10 | 전자부품연구원 | Method for delivering non-anonymous user metadata using an soap operation |
| CN101388905B (en) * | 2008-10-09 | 2011-09-07 | 浙江大学 | Simple object access protocol engine implementing method based on mobile device |
-
2009
- 2009-04-30 CN CN2009100833048A patent/CN101645785B/en not_active Expired - Fee Related
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102970378A (en) * | 2012-12-13 | 2013-03-13 | 中国电子科技集团公司第十五研究所 | Binary data optimized transmission system |
| CN104270470A (en) * | 2014-10-24 | 2015-01-07 | 杭州高达软件系统股份有限公司 | Remote service invocation method, device and system |
| CN104270472A (en) * | 2014-10-24 | 2015-01-07 | 杭州高达软件系统股份有限公司 | Remote service invocation method, device and system |
| CN104270472B (en) * | 2014-10-24 | 2017-11-07 | 杭州高达软件系统股份有限公司 | A kind of remote service calling method, apparatus and system |
| CN108600023A (en) * | 2018-05-02 | 2018-09-28 | 山东浪潮通软信息科技有限公司 | A kind of SOAP transmitters, SOAP receivers, data transmission method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101645785B (en) | 2011-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102161681B1 (en) | Device identifier dependent operation processing of packet based data communication | |
| US7529793B2 (en) | Web service simple object access protocol request response processing | |
| JP3969654B2 (en) | SOAP message creation method and processing method, information processing method, information processing apparatus, and program | |
| JP4563450B2 (en) | Content distribution system | |
| US6460137B1 (en) | Encryption processing system | |
| CA2797306C (en) | Security processing system and method for http live streaming | |
| CN110213652B (en) | Audio and video data transmission method and device and storage medium | |
| CA2623089C (en) | Method and apparatus for providing a digital rights management engine | |
| US11025432B2 (en) | Access control technology for peer-to-peer sharing | |
| Walker et al. | ROUTE/DASH IP streaming-based system for delivery of broadcast, broadband, and hybrid services | |
| JP2015517685A (en) | Method, apparatus and system for implementing media data processing | |
| CN104255010A (en) | Support for short cryptoperiods in template mode | |
| US8725788B2 (en) | System and method for decryption of content including partial-block discard | |
| CN103136459B (en) | A kind of copyright method and system of encrypted digital content | |
| CN101645785B (en) | Data-intensive multimedia service calling method based on extended SOAP | |
| CN102075790A (en) | Method for distributing and encrypting streaming media | |
| EP1480410B1 (en) | System and method for dynamically enabling components to implement data transfer security mechanisms | |
| US20140337620A1 (en) | System and Method for Local Generation of Streaming Content with a Hint Track | |
| CN106209896A (en) | Streaming media encryption method based on audio frequency and video form and module | |
| JP2009296554A (en) | Server device, license distributing method and content receiving device | |
| CN112804058A (en) | Conference data encryption and decryption method and device, storage medium and electronic equipment | |
| KR101323230B1 (en) | Methods and apparatus for conditional access of non real-time content in a distribution system | |
| CN104301102A (en) | Widget communication method, device and system | |
| US11929933B2 (en) | Ephemeral data stream routing service | |
| Jeon et al. | User centric content management system for open IPTV over SNS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20111207 Termination date: 20140430 |