Interface for transcoding system

FIELD OF THE INVENTION

The present invention relates to a transcoding system comprising an application platform and a transcoding platform for executing transcoding transactions that comprise the following steps:

transmission of a request from said application platform to said transcoding platform,
execution of said request by said transcoding platform,
transmission of a response from said transcoding platform to said application platform.

In the present description, the word “platform” refers to a combination of hardware and software that provides the functionality of the concerned applications.

BACKGROUND OF THE INVENTION

The deployment of multimedia applications like MMS Multimedia Messaging Service), WAP 2 (Wireless Application Protocol), e-mail, web browsing . . . etc.) may require some Content adaptations, due to the diversity of the phone specifications (memory, screen size, resolution, colour depth, etc, and supported media formats) and of the media formats as distributed by the Content industry (JPEG, GIF, all AMR modes, 13K vocoder, EVRC, SMV, MPEG-1, MPEG-4, H.263 . . . etc.). The word “Content” used here means any subject matter or information that is processed, stored or transmitted electronically. Content Adaptation is largely independent on the type of service that delivers the data to the end users. In this context, STI 1.0 is the first specification of a standard interface between the Multimedia Application Platforms and the Transcoding Platform and is meant to resolve some of the integration and testing problems when deploying multimedia services towards mobile devices.

SUMMARY OF THE INVENTION

The object of the invention is to propose a new solution for the standard interface, to be used by OMA STI 1.0. (OMA=Open Mobile Alliance).

To this end, the invention relates to a transcoding system such as defined in the introductory paragraph of the description and in which said request is based on a request body which is structured as indicated in Table 1, and said response, when successful, is based on a response body which is structured as indicated in Table 3.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be described, by way of example, with reference to the accompanying drawings in which:

FIG. 1 illustrates a transcoding transaction;

FIG. 2 shows an overview of the request components for such a transaction;

FIG. 3 presents the transcoding job structure, including the source parameters and the target parameters,

FIG. 4 presents the response transaction structure, and

FIG. 5 presents the job result structure;

FIG. 6 is an example of combined media format;

FIG. 7 shows the structure of a request transaction, and

FIG. 8 the structure of a response transaction.

DETAILED DESCRIPTION OF THE INVENTION

A high level overview of the interaction between an Application Platform 10 and a Transcoding Platform 20 is illustrated in FIG. 1. The communication between the Platforms is transactional, that is a transcoding session is always a request 30 followed by a response 40. A session is closed only when a response has been received. The Application Platform requests transcoding from the Transcoding Platform. The Transcoding Platform receives the request, parses it, handles it and generates a response to the originating Application Platform.

The choice of the protocol is done as follows. The interface between Application Platform and the Transcoding Platform relies on a SOAP protocol (SOAP v 1.1, http://www.w3.org/TR/SOAP/), sent over HTTP (HyperText Transfer Protocol) and used over TCP/IP (Transmission Control Protocol/Internet Protocol).

FIG. 2 shows an overview of the request components. Multiple bulk transcoding within a single Request Transaction (=transcoding request, as issued by the Application Platform; it can contain one or more Transcoding Jobs 1 to N and one or more Content Attachments 1 to M, a Transcoding Job being the part of the Request Transaction that corresponds to one individual transcoding, i.e. one input content reference and the parameters corresponding to the particular transcoding as given by the Application Platform) is allowed by the proposed interface: therefore one will distinguish between Transcoding Job (individual media transcoding) and Request Body (list of Job results) which can contain one or several Jobs as part of one single request to the Transcoding Platform. For each single Transcoding Job within a Request body, the transcoding parameters are specified within the SOAP context. In case a Transcoding Job contains the Content files themselves, they are attached inside the concerned message, but outside the SOAP envelope. Each Transcoding Job in a Request Body has to contain the source parameters (format, type, location, etc) and the target parameters (profile ID, transcoding parameters, location, policy ID, policy parameters, etc), as presented in FIG. 3. The proposed Request Transaction structure supports all the Content types within the scope of STI 1.0: images, audio, speech, video, text, presentation formats and combined media . . . etc.

The Response transaction (response of the Transcoding Platform to the Request Transaction) contains the Job Results (the Transcoding Jobs' results 1, 2, . . . , N), as presented in FIG. 4. In this Response Body, parameters (duration, return code, etc) either concern the whole Transaction or the individual Transcoding Jobs' results. For example, the duration corresponds to the complete Transaction duration. Still, in the job Results, there might also be some parameters describing the particular transcoding that was performed (i.e. image 1 was transcoded from GIF—Graphic Interchange Format—to JPEG—Joint Photographic Experts Group). The proposed interface supports reporting of statistical data gathered during the transcoding at the Job and Transaction levels. The Job Results contained in the Transaction are detailed in FIG. 5. The Source block of each Transcoding Job may specify the source type, format and parameters. The Target block of each Transaction Job has to specify the desired transcoding parameters and can specify Policy parameters.

The proposed interface also supports transcoding of combined media Content, i.e a set of media elements can be transcoded as a whole. In this case, it is expected that the Transcoding Platform receives a combined media file, performs combined transcoding of the difference media elements (including any logical decisions between the different media elements) and recombines these elements into one transcoded combined media file as a response. The combined-media is transferred as a MIME-Multipart content item (MIME Part 1 (2, 3, . . . ): see http://www.ietf.org/rfc/rfc2045(to2049).txt). The MIME type is either multipart/related (in case a presentation exists) or multipart/mixed (in case a presentation does not exist). In the first case, the start parameter refers to the presentation part. FIG. 6 illustrates the structure of a combined media (with a presentation part). The encoding of the MIME-Multipart (both input and output) is either textual, as defined in [MIME], or WAP binary encoding, as defined in [WAPWSP] (“Wireless Application Protocol, Wireless Session Protocol Specification”, WAP-203-WSP-20000504-a, WAP Forum™. URL [Uniform Resource Locator]=http://www.openmobilealliance.org). The requested encoding for the target MIME-Multipart is specified in the transcoding parameters of the Transcoding Job. The Content data (either combined media or individual media parts) is referenced from within the SOAP Request Body (and Response Body), and resides either on a storage that can be accessed by the Transcoding Platform or attached as part of the Transaction itself. The proposed interface provides two methods of supporting media attachments:

self contained requests, in which the content data reside within the Transaction itself;

references to external Content elements, in which case the Transaction only contains a pointer to a remote location from where the Content elements can be pulled by the Transcoding Platform.

Each of the methods will be described below (note that the two options can be combined within one Transaction containing references (URLs) to external Content elements and attached Content elements). In the case references to external Content elements are used, the SOAP Request/Response Body contains the URLs, pointing to the relevant files, and the Application Platform and the Transcoding Platform have access to a shared persistent storage device, either “local” or accessible via HTTP or FTP (File Transfer Protocol). In case of self-contained requests, the SOAP Request/Response Body contains references to the attachments sent along with the Transaction, as MIME parts. Each content attachment is identified by its MIME Content ID. The SOAP Request/Response Body refers to the content, using the Content IDs.

The transcoding parameters are the parameters that determine the target the Transcoding platform has to create. To specify the transcoding parameters, the Application Platform uses predefined Profiles and/or explicit transcoding parameters (note that in all cases, the Transcoding Platform can complement the list of parameters, but one of the Transcoding Platform parameters overrides the parameters that the Application Platform indicated in the Request Transaction). The transcoding parameters can be indicated using a reference to a pre-defined Profile (a profile is a set of parameters and constraints that define the transcoding target). One common use of a Profile is to describe the user Equipment (=a device allowing a user access to network services) characteristics. The profile reference can then be a reference to the database that both the Transcoding and Application Platforms share. In order to use a predefined profile, the Request Transaction specifies the Profile ID of the profile to be used (the definition of a profile and its content are out of the scope of the present description). The transcoding parameters can also be indicated using an explicit list of parameters, which will reflect the characteristics of the target device and/or the specific requirements from the Application. When a Profile ID is indicated and explicit parameters are added, the explicit parameters override the corresponding parameters in the referenced Profile.

Policy parameters are a mean for the Application Platform to specify general rules (general limitations and preferences) for the Request Transaction (i.e. priority order between the different media elements, . . . ). To specify the Policy parameters, the Application Platform uses predefined Policy and/or explicit Policy parameters. When a PolicyID is indicated and explicit policy parameters are added, the explicit parameters override the corresponding parameters in the referenced Policy.

The request transaction will now be explained in detail. As mentioned above, the Request Transactions contain a SOAP header, made of Transcoding Jobs, and can contain one or several Content attachments (if some Content elements are contained in the Transaction itself). All Content elements to be transcoded are referenced in the Transcoding Jobs (pointing to an attachment or an external source). The Request Transaction contains at least one Transcoding Job, and it can contain several Transcoding Jobs. FIG. 7 shows the structure of a Request Transaction. Request Transactions that do no contain attachments (all the files are referenced using a URLs pointing to external sources) have a SOAP header and a SOAP-based Request Body. The SOAP header specifies the originating host, the length, the request encoding and the SOAP action. Request Transactions with Content attachments contain the SOAP header and a string that will indicate the boundary between each content attachment, as defined in MIME (see [MIME]). Each Content attachment contains its own header (using MIME). Each Content Attachment header contains its unique ID, its type, its encoding and its length.

According to the invention, the SOAP-based Request Body is structured as indicated in the following Table 1 (in which the structures are written in bold):

TABLE 1Mandatory/parentNameTypePossible ValuesOptionalCommentsTransactionMandatorySeveral Transcoding Jobscan be sent within onerequest.TransactionTransactionIDIntegerMandatoryA unique ID that is given bythe Application Platform.TransactionNumTranscodingJobsIntegerOptionalHow many TranscodingJobs reside in thisTransaction.TransactionPriorityInteger0-2OptionalThe priority of theTransaction (0 is thehighest, default is 1)compared to others.TransactionProfileIDStringOptionalThe pre-defined Profile to beused for all the TranscodingJobs within this Transaction.TransactionTranscodingParamsOptionalThe transcoding parametersto be used for all theTranscoding Jobs withinthis Transaction. When apredefined Profile isspecified and this tagappears, the values specifiedwithin this tag override theones in the Profile.TransactionPolicyIDStringOptionalThe pre-defined policy to beused for the Transaction.TransactionPolicyParamsOptionalThe policy rules to be usedfor this Transaction. When apredefined Policy isspecified and this tagappears, the values specifiedwithin this tag override theones in the Policy.TransactionTranscodingJobMandatoryEach individual transcoding(1 or more)request.TranscodingJobSourceMandatoryThe source for theTranscoding Job.TranscodingJobTargetMandatoryThe Target of thisTranscoding Job.SourceTypeString“Combined”,OptionalThe type of the Source.“Audio”,“Image”,“Video”,“Text”,“SyntheticAudio”SourceFormatStringAccording to theOptionalThe format of the Source.supported formatsSourceCodecStringAccording to theOptionalThe codec of the Source.supported codecsSourceLocationStringURLMandatoryThe full-path on a sharedstorage or the Content ID ofthe attachmentSourceURLSettingsIDStringOptionalIf any specific settings(headers, passwords, etc.)should be used, in order toaccess the Source URL, thenthe Application PlatformSHALL specify a referenceto such a set of predefinedsettings through thisparameter.The definition of the set ofavailable settings is out ofthe scope of this specificationTargetProfileIDStringOptionalA predefined Profile to usefor the Transcoding Job.When a ProfileID is definedat the Transaction level andthis tag is present at theTranscoding Job level, theProfileID at the TranscodingJob level overrides the oneat the Transaction level.TargetTranscodingParamsOptionalThe transcoding parametersto be used for all theTranscoding Jobs withinthis Transaction. When apredefined Profile isspecified and this tagappears, the values specifiedwithin this tag override theones in the Profile. WhenTranscodingParams aredefined at the Transactionlevel and this tag is presentat the Transcoding Job level,the TranscodingParams atthe Transcoding Job leveloverride the ones at theTransaction level.TargetLocationStringURLMandatoryThe full-path on a sharedstorage or the Content ID ofthe attachment.TargetURLSettingsIDStringOptionalIf any specific settings(headers, passwords, etc.)should be used, in order toaccess the Target URL, thenthe Application PlatformSHALL specify a referenceto such a set of predefinedsettings through thisparameter.The definition of the set ofavailable settings is out ofthe scope of thisspecification.PolicyParamsDeleteOrderOptionalOrdered list of media typesto be deleted if necessary.PolicyParamsCompressOrderOptionalOrdered list of media types tocompressed if necessaryDeleteOrderMediaTypeString“Audio”,Optional (1Media types in order of“Image”,or more)deletion.“Video”,“Text”,“SyntheticAudio”,“Combined”CompressOrderMediaTypeString“Audio”,Optional (1Media types in order for“Image”,or more)compression.“Video”,“Text”,“SyntheticAudio”,“Combined”TranscodingParamsSizeLimitIntegerOptionalThe limit of the file sizes forthe Transaction or theTranscodingJob. Default isunlimited (−1)TranscodingParamsAudioOptionalThe audio transcodingparameters.TranscodingParamsImageOptionalThe image transcodingparameters (also graphics).TranscodingParamsVideooptionalThe video transcodingparameters.TranscodingParamsTextOptionalThe text transcodingparameters.TranscodingParamsCombinedMediaOptionalThe combined-mediatranscoding parameters.TranscodingParamsTransformationOptional (0transformation that theor morecontent should go throughappearances)TransformationTypeStringAccording to theOptionalType of transformationsupportedTransformationsTransformationparameterStringAccording to theOptionalValue of parameter for thisSupportedTransformationparameter valuesfor the specifictransformationAudioFormatStringAccording to theOptionalThe file-format of the target.supported audioAny supported audioformatsAudioCodecStringAccording to theOptionalThe desired codec.supported audioRestricted by the file formatcodecsAudioBitRateIntegerOptionalThe desired bit-rate.Restricted by the codecAudioSamplingRateIntegerOptionalThe desired sampling rate.Restricted by the codecAudioSamplingResolutionIntegerOptionalThe desired samplingresolution. Restricted by thecodecAudioSyntheticOptionalSynthetic audio relatedparameters.SyntheticChannelToUseIntegerOptionalNumber of input channel tobe used in case the outputcontains only one channel.SyntheticChannelsPriorityStringOptionalA comma separatedpermutation of 0-15. Thepriority of the channels, fromthe most important to theleast important.Default is 0-15.SyntheticInstrumentIntegerOptionalThe instrument to use, whentranscoding to midi.Irrelevant for other formats,default is pianoAudioSizeLimitIntegerOptionalThe limit of the file size foran audio. Default isunimited (−1)ImageFormatStringAccording to theOptionalThe format of the target.supported imageAny supported imageformatsImageColorSchemeString“True24Bit”,OptionalThe desired color scheme“True12Bit”,“Palette256Co”,“Palette256Gr”,“Palette32Co”,“Palette32Gr”,“Palette16Co”,“Palette16Gr”,“Palette4Co”,“Palette4Gr”,“1Bit”ImageWidthIntegerOptionalThe target width.The default is the originalwidth.ImageHeightIntegerOptionalThe target height.The default is the original heigImageResizeString“AspectRatio”,OptionalMaintain the aspect ratioPolicy“Crop”, “None”when resizing (the newdimensions are set to fit intothe desired width whileaspect ratio is maintained),crop when shrinking (do notscale the image - take itscentral rectangle), or juststretch.ImageSizeLimitIntegerOptionalSize limit for the image.Default is unlimited (−1)VideoFormatStringAccording to theOptionalThe format of the target.supported videoAny supported videoformatsVideoCodecStringAccording to theOptionalThe video codec of thesupported videotarget.codecsVideoWidthIntegerOptionalTarget widthVideoHeightIntegerOptionalTarget heightVideoFrameRateIntegerOptionalThe wanted target frame rateVideoBitRateIntegerOptionalThe desired target bit rateVideoAudioOptionalAudio parameters.VideoSizeLimitIntegerOptionalSize limit for the Audio.Default is unlimited (−1)CombinedMediaSizeLimitIntegerOptionalSize limit for the wholecombined media.Default is unlimited (−1)CombinedMediaPresentationParamsOptionalParameters for the targetpresentation.PresentationParamsFormatString“SMIL”,OptionalTarget presentation format“HTML”, “None”PresentationParamsTemplateStringOptionalTemplate for presentation tobe used in case ofpresentation format change.This is either a URL, or acontent ID of the attachmentPresentationParamsLayoutString“Portrait”,OptionalTarget layout.“Landscape”Default is the source layout.CombinedMediaEncodingString“Textual”,OptionalThe encoding of the output“WAP”MIME-Multipart.Default is textual.CombinedMediaTranscodingParamsOptionalTranscoding Parameters formedia-elements inside thecombined-media (more thanone media type may bespecifled here). TheParameters are specified forall the content-elements ofthe same type.For example, in order totranscode a video to acombined-media (e.g.image/s + audio + presentation),the target Parameters forthe audio, image, andpresentation are specifiedhere.CombinedMediaOverallParamsOptionalLimitations on mediaparameters in the combined-media.OverallParamsWidthIntegerOptionalTarget widthOverallParamsHeightIntegerOptionalTarget heightOverallParamsBitsPerPixelIntegerOptionalSupported Number of bitsper pixelOverallParamsAllowColorBooleanOptionalIndication whether colorimages are allowed as anoutput.OverallParamsMaxImageWidthIntegerOptionalMaximum widthallowed forimage.OverallParamsMaxImageHeightIntegerOptionalMaximum heightallowed foran image.OverallParamsAllowImageBooleanOptionalIndication whetheroutputcan contain image.OverallParamsAllowAudioBooleanOptionalIndication whetheroutputcan contain audio.OverallParamsAllowVideoBooleanOptionalIndication whetheroutput can contain videoOverallParamsSupportedContentTypesOptionalA list of the supportedcontent types.SupportedContentTypesTypeStringOptionalA single content type1 or more)

In order to perform transformations on the media, the Application Platform specifies, for each requested transformation, the type of the transformation and the parameter for the transformation. The following Table 2 lists the minimal set of supported transformations, the allowed parameter values for these transformations, and the type (or types) of media elements on which these transformations may be used. STI supports other proprietary Transformations that will then have to be defined between the Application Platform and the Transcoding Platform. If the Transcoding Platform does not recognize the Transformation type, it returns an error.

TABLE 2TransformationTypePossible parameter valuesMedia TypesDescriptionLevelCorrectionNo parameterImagePerform level correction.Mirror“UD”, “LR,Image“UD” - vertical mirror, “LR” -“Diagonal”,horizontal mirror. Default is“None”“None”.NoiseReductionNo parameterImagePerform noise reduction.RotationAngle of clockwiseImagePerform Image rotationrotation (0-359)SharpenNo parameterImagePerform image sharpening.DurationLimitLimit on duration (inVideo, Audio,Truncate the media if its durationmilliseconds)CombinedMedia (e.g.exceeds this limit.for slideshow)AGCNo parameterAudioPerform Automatic Gain ControlOffsetOffset in source mediaAudio, Videothe source image to start the(inTranscoding from.milliseconds)AudioChannels“Mono”, “Stereo”,AudioChange the number of channels“DualMono”,in the output.“IntensityStereo”FrameRateSampleNew frame rateImage (e.g. forChange the frame sampling rateslideshow)(without changing the speed andthe duration of the media)FrameRateOutputNew frame rateImage (e.g. forChange the frame rate in theslideshow)output (and thus change alsothe speed and the duration ofthe media).NumberOfFramesNew number of framesImage (e.g. forChange the number of frames inslideshow)the output.

A request Transaction is considered as successful unless there was an error during the handling of the transaction that prevented the completion of the whole Transaction. Errors in specific Transcoding Jobs do not affect the success value of the entire Request Transaction. That is, a Request Transaction may be successful even though some (or all) of the Transcoding Jobs failed. The structure of a successful Response Transaction, containing the results of one or more Transcoding Jobs, is quite similar to the Request Transaction, i.e. a SOAP header, including a success code, and one or more Job Results and optionally the Content attachments. The Response Body contains references to either external content element or self-contained content elements. The same differences between a Transaction with contained content elements and without contained content elements, as discussed in the Request Transaction, apply for Response Transactions. FIG. 8 shows the structure of the Response Transaction. As for the Request Body, a table indicates (Table 3) how the Response Body is structured:

TABLE 3ParentNameTypePossible valuesCommentsTransactionThe responseTransactionReturnCodeIntegerThe return code of theTransaction (either asuccessful or a warning)TransactionNumJobResultsIntegerHow many Job Resultsresidue in this response.TransactionProfileIDStringThe Profile ID that wasused for this transaction(in case it was specifiedin the Transaction blockof the request)TransactionPolicyIDStringThe Policy ID that wasused for this transaction(in case it was specifiedin the Transaction blockof the request)TransactionTransactionIDIntegerThe unique ID that wasreceived from theApplication Platform inthe requestTransactionContextIDIntegerA unique ID of thetranscoding sessionthat is given by theTranscoding Platform.TransactionTotalDurationIntegerThe time it took theTranscoding Platform toperform the entiretranscoding Transactionin milliseconds. Thisnumber is the durationof the whole transactionfrom the time it reachedthe TranscodingPlatform to the time theresponse was sent (itcan be higher or lowerthe sum of durations forall the Job Results).TransactionJobResultThe Job Results. Maybe more than one (oneper each Transcoding Job)JobResultReturnCodeIntegerThe return code of theTranscoding Job (eithera successful or awarning)JobResultMessageStringA message with anexplanation in case of awarningJobResultDurationIntegerThe duration it took thisTranscoding Job (inmilliseconds)JobResultTargetDetails about the target.TargetFileSizeIntegerThe actual size of the fileTargetLocationStringThe full-path on ashared storage or theContent ID of theattachment.TargetProfileIDStringThe Profile ID that wasused for thisTranscoding Job (incase it was specified).TargetTranscodingParamsThe TranscodingParameters of the target.TranscodingParamsSizeLimitIntegerThe limit that was givento the entire transactionTranscodingParamsAudioAudio detailsTranscodingParamsImageImage detailsTranscodingParamsVideoVideo detailsTranscodingParamsTextText detailsTranscodingParamsCombinedMediaCombined-media detailsTranscodingParamsTransformationA Transformation thatwas applied (0 or moreappearances).TransformationTypeStringAccording to theType of transformationsupportedTransformationsTransformationParameterStringAccording to theValue of parameter forSupportedthis transformationparameter valuesfor the specifictransformationAudioFormatStringThe supportedThe file formataudio formatsAudioCodecStringThe supportedThe codecaudio codecsAudioBitRateIntegerThe bit-rateAudioSamplingRateIntegerThe sampling rateAudioSamplingResolutionIntegerThe sampling resolutionAudioSizeLimitIntegerThe limit that was givenfor an audioAudioSyntheticOptionalSynthetic audio relatedparameters.SyntheticChannelToUseIntegerOptionalNumber of input channelused in case the outputcontains only one channel.SyntheticChannelsPriorityStringOptionalA comma separatedpermutation of 0-15. Thepriority of the channels,from the most importantto the least important.SyntheticInstrumentIntegerOptionalThe instrument used,when transcoding tomidi. Irrelevant for otherformats.ImageFormatStringThe supportedThe formatimage formatsImageColorSchemeString“True24Bit”,The color scheme of the“True12Bit”,image“Palette256Co”,“Palette256Gr”,“Palette32Co”,“Palette32Gr”,“Palette16Co”,“Pallete16Gr”,“Palette4Co”,“Palette4Gr”,“1Bit”ImageNunberOfColorsIntegerThe actual number ofcolorsImageWidthIntegerThe widthImageHeightIntegerThe heightImageSizeLimitIntegerThe limit that was givenfor an imageVideoFormatStringThe supportedThe formatvideo formatsVideoCodecStringThe supportedThe codecvideo codecsVideoWidthIntegerThe widthVideoHeightIntegerThe heightVideoFrameRateIntegerThe frame rateVideoBitRateIntegerThe bit rateVideoSizeLimitIntegerThe limit that was givenfor a videoCombinedMediaSizeLimitIntegerThe limit that was givenfor a combined-mediaCombinedMediaPresentationParamsParameters for the targetpresentationtranscoding.PresentationParamsFormatString“SMIL”,Target presentation“HTML”,format“None”PresentationParamsTemplateStringTemplate forpresentation that wasused.PresentationParamsLayoutString“Portrait”,Target layout.“Landscape”CombinedMediaEncodingString“Textual”,The encoding of the“WAP”output MIME-Multipart.

A Transaction Failure response is returned in a situation where the whole Transaction could not be handled. This may happen if there was a problem with the Transaction parameters, or any other problem, which relates to the whole Transaction (and not only to one or more of the Transcoding Jobs). The header of a Transcoding error contains a line that indicates that there was an error (HTTP/1.1 500 Error), and the regular fields. The body of the SOAP, of a different structure from a successful one, is given in Table 4 below:

TABLE 4ParentNameTypePossible valuesDescriptionFaultResponseThe faultFaultResponseTransactionIDIntegerThe unique ID that wasreceived fromthe Application Platform in therequestFaultResponseContextIDIntegerA unique ID of thetranscoding sessionthat is given by theTranscoding platformFaultResponseTotalDurationIntegerThe total milliseconds it tookthe wholeTransaction to be handled(until the error occurred)FaultResponseReturnCodeIntegerOut of the possibleerror codesFaultResponseMessageStringAn explanatory error message

It may be added that the Transcoding Platform supports the Transaction error codes indicated in the following Table 5:

TABLE 5Error codeError string1001Parsing error1004Erroneous target structure1005Error in target data1006General server error1008No media detected in request message1009Response composition error (<err-code>)1010Number of concurrent requests exceeded the maximum1011Erroneous transcoding request1012Transaction result exceed maximal size1013Policy could not be accomplished and transaction failed.1014Policy could not be accomplished but transaction succeeded.

and that Transcoding Platform supports the Transcoding Job error codes indicated in the following Table 6:

TABLE 6Error codeError string2001Error in input media2002Unsupported Content Type2003Unsupported Content Format2004Unsupported Content Codec2005Unsupported Content2006Unsupported transcoding request2006Unsupported Transformation2007No media detected in request message2008Output content size exceeds the limit2009Failed to read source content.2010Failed to write target content.2101DRM protected content: no transcoding done

Interface for transcoding system

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims

Priority Claims (1)

PCT Information