ISO/IEC 23006-4:2013
Information technology — Multimedia service platform technologies — Part 4: Elementary services
ISO/IEC 23006-4:2013 specifies a set of Elementary Services and protocols enabling distributed applications to exchange information related to content items and parts thereof, including all the necessary Operations on MPEG-related Entities: Content, Contract, Device, Event, License, Service and User. These operations are defined to be the following: Authenticate, Authorize, Check With, Create, Deliver, Describe, Identify, Install, Interact With, Negotiate, Package, Post, Present, Process, Request, Revoke, Search, Store, Transact, Uninstall and Verify. Elementary Services can be combined in well defined sequences to build Aggregated Services, both of them being called in general Multimedia Services. ISO/IEC 23006 (all parts) will be referred to as MPEG-M for short in the text. The Multimedia Services are provided by and consumed by Multimedia Devices in a MSPT ecosystem, an example of which is the Advanced IPTV Terminal.
| Get this standard | Prices exclude GST | |
|---|---|---|
| PDF ( Single user document) |
$403.48 NZD
|
|
| HardCopy |
$459.13 NZD
|
|
| Networkable PDF |
Price varies
|
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
3.2 Abbreviated terms
4 Namespaces and conventions
4.1 Namespaces
4.1.1 Introduction
4.1.2 Schema namespaces
4.1.3 BPMN namespaces
4.1.4 Service Type namespaces
4.1.5 Classification Scheme namespaces
4.2 Namespace convention
4.3 Conventions
5 Elementary Services
5.1 Introduction
5.1.1 Overview of Elementary Services
5.1.2 Overview of Operations and Entities
5.1.3 General Service Definition
5.1.4 Service Type
5.1.5 Service Instance Declaration
5.1.6 Message transport
5.1.7 Validation
5.1.8 BPMN 2.0 XML representation of Service workflows
5.1.8.1 Introduction
5.1.8.2 BPMN 2.0 XML representation of abstract base Elementary Service workflows
5.1.8.3 Examples
5.2 Base data types, elements, and common messages
5.2.1 Introduction
5.2.2 MPEG-M base Schema wrapper
5.2.3 Common elements and types
5.2.3.1 Introduction
5.2.3.2 ServiceTypeType
5.2.3.2.1 Introduction
5.2.3.2.2 Syntax
5.2.3.2.3 Semantics
5.2.3.2.4 Additional validation rules
5.2.3.2.4.1 Introduction
5.2.3.2.4.2 The value of the RequestParametersType element must be an existing complex type that extends RequestParametersBaseType.
5.2.3.2.4.3 The value of the CompletionParametersType element must be an existing complex type that extends CompletionParametersBaseType.
5.2.3.3 ContractIdentifier
5.2.3.3.1 Introduction
5.2.3.3.2 Syntax
5.2.3.3.3 Semantics
5.2.3.4 LicenseIdentifier
5.2.3.4.1 Introduction
5.2.3.4.2 Syntax
5.2.3.4.3 Semantics
5.2.3.5 ServiceTypeIdentifier
5.2.3.5.1 Introduction
5.2.3.5.2 Syntax
5.2.3.5.3 Semantics
5.2.3.6 SIDIdentifier
5.2.3.6.1 Introduction
5.2.3.6.2 Syntax
5.2.3.6.3 Semantics
5.2.3.7 UserIdentifier
5.2.3.7.1 Introduction
5.2.3.7.2 Syntax
5.2.3.7.3 Semantics
5.2.3.8 EntityBaseType
5.2.3.8.1 Introduction
5.2.3.8.2 Syntax
5.2.3.8.3 Semantics
5.2.3.9 ContentEntityType
5.2.3.9.1 Introduction
5.2.3.9.2 Syntax
5.2.3.9.3 Semantics
5.2.3.9.4 Additional validation rules
5.2.3.9.4.1 Introduction
5.2.3.9.4.2 If multiple ContentRef elements are specified, they must all point to copies of the same Content.
5.2.3.9.4.3 If multiple dii:Identifier elements are specified, they must all identify the same Content.
5.2.3.10 ContractEntityType
5.2.3.10.1 Introduction
5.2.3.10.2 Syntax
5.2.3.10.3 Semantics
5.2.3.10.4 Additional validation rules
5.2.3.10.4.1 Introduction
5.2.3.10.4.2 If multiple ContractRef elements are specified, they must all point to copies of the same Contract.
5.2.3.10.4.3 If multiple ContractIdentifier elements are specified, they must all identify the same Contract.
5.2.3.11 DeviceEntityType
5.2.3.11.1 Introduction
5.2.3.11.2 Syntax
5.2.3.11.3 Semantics
5.2.3.11.4 Additional validation rules
5.2.3.11.4.1 Introduction
5.2.3.11.4.2 If multiple DeviceRef elements are specified, they must all point to the same Device.
5.2.3.11.4.3 If multiple ipmpinfo-msx:ToolBodyID elements are specified, they must all identify the same Device.
5.2.3.12 LicenseEntityType
5.2.3.12.1 Introduction
5.2.3.12.2 Syntax
5.2.3.12.3 Semantics
5.2.3.12.4 Additional validation rules
5.2.3.12.4.1 Introduction
5.2.3.12.4.2 If multiple LicenseRef elements are specified, they must all point to copies of the same License.
5.2.3.12.4.3 If multiple LicenseIdentifier elements are specified, they must all identify the same License.
5.2.3.13 ServiceTypeEntityType
5.2.3.13.1 Introduction
5.2.3.13.2 Syntax
5.2.3.13.3 Semantics
5.2.3.13.4 Additional validation rules
5.2.3.13.4.1 Introduction
5.2.3.13.4.2 If multiple ServiceTypeRef elements are specified, they must all point to the same Service Type.
5.2.3.13.4.3 If multiple ServiceTypeIdentifier elements are specified, they must all identify the same Service Type.
5.2.3.14 UserEntityType
5.2.3.14.1 Introduction
5.2.3.14.2 Syntax
5.2.3.14.3 Semantics
5.2.3.14.4 Additional validation rules
5.2.3.14.4.1 Introduction
5.2.3.14.4.2 If multiple UserRef elements are specified, they must all point to the same User.
5.2.3.14.4.3 If multiple UserIdentifier elements are specified, they must all identify the same User.
5.2.3.15 RequestParametersBaseType
5.2.3.15.1 Introduction
5.2.3.15.2 Syntax
5.2.3.15.3 Semantics
5.2.3.16 CompletionParametersBaseType
5.2.3.16.1 Introduction
5.2.3.16.2 Syntax
5.2.3.16.3 Semantics
5.2.3.17 SupportedMetadataSchemaType
5.2.3.17.1 Introduction
5.2.3.17.2 Syntax
5.2.3.17.3 Semantics
5.2.3.18 SupportedTransferProtocolType
5.2.3.18.1 Introduction
5.2.3.18.2 Syntax
5.2.3.18.3 Semantics
5.2.3.19 RevocationReasonType
5.2.3.19.1 Introduction
5.2.3.19.2 Syntax
5.2.3.19.3 Semantics
5.2.3.20 EntityOrderInformationType
5.2.3.20.1 Introduction
5.2.3.20.2 Syntax
5.2.3.20.3 Semantics
5.2.3.21 ContentOrderInformationType
5.2.3.21.1 Introduction
5.2.3.21.2 Syntax
5.2.3.21.3 Semantics
5.2.3.22 LicenseOrderInformationType
5.2.3.22.1 Introduction
5.2.3.22.2 Syntax
5.2.3.22.3 Semantics
5.2.4 Base Protocol
5.2.4.1 Introduction
5.2.4.2 Syntax
5.2.4.3 Semantics
5.2.4.4 Examples
5.2.5 Common messages
5.2.5.1 Introduction
5.2.5.2 Syntax
5.2.5.3 Semantics
5.2.5.4 Additional validation rules
5.2.5.4.1 Introduction
5.2.5.4.2 Each complex type extending the ProtocolResponseType must contain a choice between an element of complex type ProtocolSuccessType and an element of complex type ProtocolFailureType or subtypes of them. These elements are named
5.3 MPEG-M service Schema wrapper
5.4 Session control and status polling
5.4.1 Session control messages
5.4.1.1 Introduction
5.4.1.2 Interfaces and protocol specification
5.4.1.3 Syntax of protocol data format
5.4.1.4 Semantics of protocol data format
5.4.1.5 Example
5.4.2 Session status polling messages
5.4.2.1 Introduction
5.4.2.2 Interfaces and protocol specification
5.4.2.3 Syntax of protocol data format
5.4.2.4 Semantics of protocol data format
5.4.2.5 Additional validation rules
5.4.2.5.1 Introduction
5.4.2.5.2 The completion attribute may only be present if the ProgressStatus is set to "CURRENTLY_IN_PROGRESS" or "PROGRESS_PAUSED".
5.4.2.6 Example
5.5 The Authenticate Services
5.5.1 Authenticate Entity
5.5.1.1 Introduction
5.5.1.2 Interfaces and protocol specification
5.5.1.3 Syntax of protocol data format
5.5.1.4 Semantics of protocol data format
5.5.1.5 Additional validation rules
5.5.1.5.1 Introduction
5.5.1.5.2 Each complex type extending the AuthenticateEntityRequestType must contain an authentication entity of the appropriate type (e.g., mpegmb:ContentEntityType for Authenticate Content).
5.5.1.6 Extension to SID
5.5.2 Authenticate Content
5.5.2.1 Introduction
5.5.2.2 Interfaces and protocol specification
5.5.2.3 Syntax of protocol data format
5.5.2.4 Semantics of protocol data format
5.5.2.5 Extension to SID
5.5.3 Authenticate Contract
5.5.3.1 Introduction
5.5.3.2 Interfaces and protocol specification
5.5.3.3 Syntax of protocol data format
5.5.3.4 Semantics of protocol data format
5.5.3.5 Extension to SID
5.5.4 Authenticate License
5.5.4.1 Introduction
5.5.4.2 Interfaces and protocol specification
5.5.4.3 Syntax of protocol data format
5.5.4.4 Semantics of protocol data format
5.5.4.5 Extension to SID
5.5.5 Authenticate User
5.5.5.1 Introduction
5.5.5.2 Interfaces and protocol specification
5.5.5.3 Syntax of protocol data format
5.5.5.4 Semantics of protocol data format
5.5.5.5 Extension to SID
5.6 The Authorize Services
5.6.1 Authorize User
5.6.1.1 Introduction
5.6.1.2 Interfaces and protocol specification
5.6.1.3 Syntax of protocol data format
5.6.1.4 Semantics of protocol data format
5.6.1.5 Extension to SID
5.7 The Check With Services
5.7.1 Check With Contract
5.7.1.1 Introduction
5.7.1.2 Interfaces and protocol specification
5.7.1.3 Syntax of protocol data format
5.7.1.4 Semantics of protocol data format
5.7.1.5 Extension to SID
5.7.2 Check With License
5.7.2.1 Introduction
5.7.2.2 Interfaces and protocol specification
5.7.2.3 Syntax of protocol data format
5.7.2.4 Semantics of protocol data format
5.7.2.5 Extension to SID
5.8 The Create Services
5.8.1 Create Content
5.8.1.1 Introduction
5.8.1.2 Interfaces and protocol specification
5.8.1.3 Syntax of protocol data format
5.8.1.4 Semantics of protocol data format
5.8.1.5 Extension to SID
5.8.2 Create Contract
5.8.2.1 Introduction
5.8.2.2 Interfaces and protocol specification
5.8.2.3 Syntax of protocol data format
5.8.2.4 Semantics of protocol data format
5.8.2.5 Extension to SID
5.8.3 Create License
5.8.3.1 Introduction
5.8.3.2 Interfaces and protocol specification
5.8.3.3 Syntax of protocol data format
5.8.3.4 Semantics of protocol data format
5.8.3.5 Extension to SID
5.9 The Deliver Services
5.9.1 Deliver Content
5.9.1.1 Introduction
5.9.1.2 Interfaces and protocol specification
5.9.1.3 Syntax of protocol data format
5.9.1.4 Semantics of protocol data format
5.9.1.5 Extension to SID
5.9.1.6 Example
5.9.2 Deliver Contract
5.9.2.1 Introduction
5.9.2.2 Interfaces and protocol specification
5.9.2.3 Syntax of protocol data format
5.9.2.4 Semantics of protocol data format
5.9.2.5 Extension to SID
5.10 The Describe Services
5.10.1 Describe Entity
5.10.1.1 Introduction
5.10.1.2 Set Describe Entity Protocol
5.10.1.2.1 Interfaces and protocol specification
5.10.1.2.2 Syntax of protocol data format
5.10.1.2.3 Semantics of protocol data format
5.10.1.2.4 Additional validation rules
5.10.1.2.4.1 Introduction
5.10.1.2.4.2 The metadata schema of the description conveyed in the AccessUnit element of the request must conform to one of the metadata schemas specified by the sid:SupportedMetadataSchema elements of the SID.
5.10.1.3 Get Describe Entity Protocol
5.10.1.3.1 Interfaces and protocol specification
5.10.1.3.1.1 General
5.10.1.3.1.2 Processing of FRU
5.10.1.3.1.3 Conformance to ISO/IEC 23001-2
5.10.1.3.1.4 Processing of FUU
5.10.1.3.2 Syntax of protocol data format
5.10.1.3.3 Semantics of protocol data format
5.10.1.3.4 Additional validation rules
5.10.1.3.4.1 Introduction
5.10.1.3.4.2 If present, the SupportedMetadataSchema elements must be a subset of the sid:SupportedMetadataSchema elements in the SID of the Service Instance. However, the client sets its own preferences through the pref attribute.
5.10.1.3.4.3 The metadata schema of the description conveyed in the AccessUnit element of the response must conform to one of the metadata schemas specified by the SupportedMetadataSchema elements of the request message.
5.10.1.4 Extension to SID
5.10.2 Describe Content
5.10.2.1 Introduction
5.10.2.2 Set Describe Content Protocol
5.10.2.2.1 Interfaces and protocol specification
5.10.2.2.2 Syntax of protocol data format
5.10.2.2.3 Semantics of protocol data format
5.10.2.2.4 Additional validation rules
5.10.2.2.4.1 Introduction
5.10.2.2.4.2 The EntityIdentifier must be a Content Identifier represented as dii:Identifier.
5.10.2.2.5 Example
5.10.2.3 Get Describe Content Protocol
5.10.2.3.1 Interfaces and protocol specification
5.10.2.3.2 Syntax of protocol data format
5.10.2.3.3 Semantics of protocol data format
5.10.2.3.4 Additional validation rules
5.10.2.3.4.1 Introduction
5.10.2.3.4.2 The EntityIdentifier must be a Content Identifier represented as dii:Identifier.
5.10.2.3.5 Examples
5.10.2.4 Extension to SID
5.10.3 Describe Device
5.10.3.1 Introduction
5.10.3.2 Set Describe Device Protocol
5.10.3.2.1 Interfaces and protocol specification
5.10.3.2.2 Syntax of protocol data format
5.10.3.2.3 Semantics of protocol data format
5.10.3.2.4 Additional validation rules
5.10.3.2.4.1 Introduction
5.10.3.2.4.2 The EntityIdentifier must be a Device Identifier represented as ipmpinfo-msx:ToolBodyID.
5.10.3.2.5 Example
5.10.3.3 Get Describe Device Protocol
5.10.3.3.1 Interfaces and protocol specification
5.10.3.3.2 Syntax of protocol data format
5.10.3.3.3 Semantics of protocol data format
5.10.3.3.4 Additional validation rules
5.10.3.3.4.1 Introduction
5.10.3.3.4.2 The EntityIdentifier must be a Device Identifier represented as ipmpinfo-msx:ToolBodyID.
5.10.3.3.5 Example
5.10.3.4 Extension to SID
5.10.4 Describe Service
5.10.4.1 Introduction
5.10.4.2 Set Describe Service Protocol
5.10.4.2.1 Interfaces and protocol specification
5.10.4.2.2 Syntax of protocol data format
5.10.4.2.3 Semantics of protocol data format
5.10.4.2.4 Additional validation rules
5.10.4.2.4.1 Introduction
5.10.4.2.4.2 The EntityIdentifier must be a Service Instance Identifier represented as mpegmb:SIDIdentifier.
5.10.4.2.5 Example
5.10.4.3 Get Describe Service Protocol
5.10.4.3.1 Interfaces and protocol specification
5.10.4.3.2 Syntax of protocol data format
5.10.4.3.3 Semantics of protocol data format
5.10.4.3.4 Additional validation rules
5.10.4.3.4.1 Introduction
5.10.4.3.4.2 The EntityIdentifier must be an SID Identifier represented as mpegmb:SIDIdentifier.
5.10.4.3.5 Example
5.10.4.4 Extension to SID
5.10.5 Describe User
5.10.5.1 Introduction
5.10.5.2 Set Describe User Protocol
5.10.5.2.1 Interfaces and protocol specification
5.10.5.2.2 Syntax of protocol data format
5.10.5.2.3 Semantics of protocol data format
5.10.5.2.4 Additional validation rules
5.10.5.2.4.1 Introduction
5.10.5.2.4.2 The EntityIdentifier must be a User Identifier represented as mpegmb:UserIdentifier.
5.10.5.2.5 Example
5.10.5.3 Get Describe User Protocol
5.10.5.3.1 Interfaces and protocol specification
5.10.5.3.2 Syntax of protocol data format
5.10.5.3.3 Semantics of protocol data format
5.10.5.3.4 Additional validation rules
5.10.5.3.4.1 Introduction
5.10.5.3.4.2 The EntityIdentifier must be a User Identifier represented as mpegmb:UserIdentifier.
5.10.5.3.5 Examples
5.10.5.4 Extension to SID
5.11 The Identify Services
5.11.1 Identify Entity
5.11.1.1 Introduction
5.11.1.2 Interfaces and protocol specification
5.11.1.3 Syntax of protocol data format
5.11.1.4 Semantics of protocol data format
5.11.1.5 Extension to SID
5.11.2 Identify Content
5.11.2.1 Introduction
5.11.2.2 Interfaces and protocol specification
5.11.2.3 Syntax of protocol data format
5.11.2.4 Semantics of protocol data format
5.11.2.5 Extension to SID
5.11.3 Identify Contract
5.11.3.1 Introduction
5.11.3.2 Interfaces and protocol specification
5.11.3.3 Syntax of protocol data format
5.11.3.4 Semantics of protocol data format
5.11.3.5 Extension to SID
5.11.4 Identify Device
5.11.4.1 Introduction
5.11.4.2 Interfaces and protocol specification
5.11.4.3 Syntax of protocol data format
5.11.4.4 Semantics of protocol data format
5.11.4.5 Extension to SID
5.11.5 Identify License
5.11.5.1 Introduction
5.11.5.2 Interfaces and protocol specification
5.11.5.3 Syntax of protocol data format
5.11.5.4 Semantics of protocol data format
5.11.5.5 Extension to SID
5.11.6 Identify User
5.11.6.1 Introduction
5.11.6.2 Interfaces and protocol specification
5.11.6.3 Syntax of protocol data format
5.11.6.4 Semantics of protocol data format
5.11.6.5 Additional validation rules
5.11.6.5.1 Introduction
5.11.6.5.2 The UserIdentificationAssertion shall only be used if the User to be identified is not the same as the requesting client. If the client requests a user identifier for himself/herself, then the saml:Assertion element of the mpegmb:ProtocolRequestType shall be used.
5.11.6.6 Extension to SID
5.12 The Negotiate Services
5.12.1 Negotiate Entity
5.12.1.1 Introduction
5.12.1.2 General Considerations
5.12.1.3 Interfaces and protocol specification
5.12.1.4 SetupNegotiationEntity
5.12.1.4.1 Syntax of protocol data format
5.12.1.4.2 Semantics of protocol data format
5.12.1.4.3 Additional validation rules
5.12.1.4.3.1 Introduction
5.12.1.4.3.2 If at least one Participant is specified, the publish attribute of the SetupNegotiationEntityRequestType is typically set to false.
5.12.1.4.3.3 The accepted attribute of all IssueOffer elements must be set to false in the SetupNegotiationEntityRequestType.
5.12.1.4.3.4 If the publish attribute of the SetupNegotiationEntityRequestType is set to false, at least one Participant must be specified.
5.12.1.4.3.5 The accepted attribute of the IssueType may only be set to true if exactly one ProposedValue element is provided (i.e., the accepted value).
5.12.1.5 AdmissionEntity
5.12.1.5.1 Syntax of protocol data format
5.12.1.5.2 Semantics of protocol data format
5.12.1.6 OfferEntity
5.12.1.6.1 Syntax of protocol data format
5.12.1.6.2 Semantics of protocol data format
5.12.1.7 AgreementEntity
5.12.1.7.1 Syntax of protocol data format
5.12.1.7.2 Semantics of protocol data format
5.12.1.8 Extension to SID
5.12.2 Negotiate Contract
5.12.2.1 Introduction
5.12.2.2 Interfaces and protocol specification
5.12.2.3 Syntax of protocol data format
5.12.2.4 Semantics of protocol data format
5.12.2.5 Additional validation rules
5.12.2.5.1 Introduction
5.12.2.5.2 The NegotiationItemTemplate of the SetupNegotiationContractRequest must be of type mpegmb:ContractEntityType.
5.12.2.5.3 The TemplateEntity of the AgreementContractRequest must be of type mpegmb:ContractEntityType.
5.12.2.5.4 The FinalEntity of the AgreementContractRequest must be of type mpegmb:ContractEntityType.
5.12.2.5.5 The TemplateEntity of the AgreementContractResponse must be of type mpegmb:ContractEntityType.
5.12.2.5.6 The FinalEntity of the AgreementContractResponse must be of type mpegmb:ContractEntityType.
5.12.2.6 Extension to SID
5.12.2.7 Example
5.12.3 Negotiate License
5.12.3.1 Introduction
5.12.3.2 Interfaces and protocol specification
5.12.3.3 Syntax of protocol data format
5.12.3.4 Semantics of protocol data format
5.12.3.4.1 Additional validation rules
5.12.3.4.1.1 Introduction
5.12.3.4.1.2 The NegotiationItemTemplate of the SetupNegotiationLicenseRequest must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.3 The TemplateEntity of the AgreementLicenseRequest must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.4 The FinalEntity of the AgreementLicenseRequest must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.5 The TemplateEntity of the AgreementLicenseResponse must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.6 The FinalEntity of the AgreementLicenseResponse must be of type mpegmb:LicenseEntityType.
5.12.3.5 Extension to SID
5.13 The Package Services
5.13.1 Package Content
5.13.1.1 Introduction
5.13.1.2 Interfaces and protocol specification
5.13.1.3 Syntax of protocol data format
5.13.1.4 Semantics of protocol data format
5.13.1.5 Extension to SID
5.13.1.6 Example
5.14 The Post Services
5.14.1 Post Content
5.14.1.1 Introduction
5.14.1.2 Interfaces and protocol specification
5.14.1.3 Syntax of protocol data format
5.14.1.4 Semantics of protocol data format
5.14.1.5 Extension to SID
5.14.1.6 Example
5.15 The Present Services
5.15.1 Present Entity
5.15.1.1 Introduction
5.15.1.2 Interfaces and protocol specification
5.15.1.3 Syntax of protocol data format
5.15.1.4 Semantics of protocol data format
5.15.1.5 Extension to SID
5.15.2 Present Contract
5.15.2.1 Introduction
5.15.2.2 Interfaces and protocol specification
5.15.2.3 Syntax of protocol data format
5.15.2.4 Semantics of protocol data format
5.15.2.5 Extension to SID
5.15.3 Present License
5.15.3.1 Introduction
5.15.3.2 Interfaces and protocol specification
5.15.3.3 Syntax of protocol data format
5.15.3.4 Semantics of protocol data format
5.15.3.5 Extension to SID
5.16 The Process Services
5.16.1 Process Content
5.16.1.1 Introduction
5.16.1.2 Interfaces and protocol specification
5.16.1.3 Syntax of protocol data format
5.16.1.4 Semantics of protocol data format
5.16.1.5 Additional validation rules
5.16.1.5.1 Introduction
5.16.1.5.2 The Service Type specified by the ServiceTypeEntity must have the same Service Type Identifier as the one specified in the underlying Service Instance Declaration.
5.16.1.5.3 The type of RequestParameters must conform to the type specified by the RequestParametersType element of the Service Type for that particular Process Content Service Instance.
5.16.1.5.4 The type of CompletionParameters must conform to the type specified by the CompletionParametersType element of the Service Type for that particular Process Content Service Instance.
5.16.1.6 Extension to SID
5.16.2 Process License
5.16.2.1 Introduction
5.16.2.2 Interfaces and protocol specification
5.16.2.3 Syntax of protocol data format
5.16.2.4 Semantics of protocol data format
5.16.2.5 Extension to SID
5.17 The Request Services
5.17.1 Request Content
5.17.1.1 Introduction
5.17.1.2 Interfaces and protocol specification
5.17.1.3 Syntax of protocol data format
5.17.1.4 Semantics of protocol data format
5.17.1.5 Extension to SID
5.17.1.6 Examples
5.17.2 Request Contract
5.17.2.1 Introduction
5.17.2.2 Interfaces and protocol specification
5.17.2.3 Syntax of protocol data format
5.17.2.4 Semantics of protocol data format
5.17.2.5 Extension to SID
5.17.3 Request Device
5.17.3.1 Introduction
5.17.3.2 Interfaces and protocol specification
5.17.3.3 Syntax of protocol data format
5.17.3.4 Semantics of protocol data format
5.17.3.5 Extension to SID
5.17.4 Request Event
5.17.4.1 Introduction
5.17.4.2 Interfaces and protocol specification
5.17.4.3 Syntax of protocol data format
5.17.4.4 Semantics of protocol data format
5.17.4.5 Additional validation rules
5.17.4.5.1 Introduction
5.17.4.5.2 If the RequestEventRequest message contains a ContentEntity and the RequestEventResponse message contains a RequestEventSuccess, then the RequestEventSuccess shall contain a erl:ERR.
5.17.4.5.3 If the RequestEventRequest message contains a erl:ERR and the RequestEventResponse message contains a RequestEventSuccess, then the RequestEventSuccess shall contain one or more erl:ER elements.
5.17.4.6 Extension to SID
5.17.5 Request License
5.17.5.1 Introduction
5.17.5.2 Interfaces and protocol specification
5.17.5.3 Syntax of protocol data format
5.17.5.4 Semantics of protocol data format
5.17.5.5 Extension to SID
5.18 The Revoke Services
5.18.1 Revoke Entity
5.18.1.1 Introduction
5.18.1.2 Interfaces and protocol specification
5.18.1.3 Syntax of protocol data format
5.18.1.4 Semantics of protocol data format
5.18.1.5 Extension to SID
5.18.2 Revoke Content
5.18.2.1 Introduction
5.18.2.2 Interfaces and protocol specification
5.18.2.3 Syntax of protocol data format
5.18.2.4 Semantics of protocol data format
5.18.2.5 Additional validation rules
5.18.2.5.1 Introduction
5.18.2.5.2 The RevokedEntity element of the RevokeContentRequest message must be of type mpegmb:ContentEntityType.
5.18.2.6 Extension to SID
5.18.3 Revoke Contract
5.18.3.1 Introduction
5.18.3.2 Interfaces and protocol specification
5.18.3.3 Syntax of protocol data format
5.18.3.4 Semantics of protocol data format
5.18.3.5 Additional validation rules
5.18.3.5.1 Introduction
5.18.3.5.2 The RevokedEntity element of the RevokeContractRequest message must be of type mpegmb:ContractEntityType.
5.18.3.6 Extension to SID
5.18.4 Revoke License
5.18.4.1 Introduction
5.18.4.2 Interfaces and protocol specification
5.18.4.3 Syntax of protocol data format
5.18.4.4 Semantics of protocol data format
5.18.4.5 Additional validation rules
5.18.4.5.1 Introduction
5.18.4.5.2 The RevokedEntity element of the RevokeLicenseRequest message must be of type mpegmb:LicenseEntityType.
5.18.4.6 Extension to SID
5.19 The Search Services
5.19.1 Search Entity
5.19.1.1 Introduction
5.19.1.2 Interfaces and protocol specification
5.19.1.3 Syntax of protocol data format
5.19.1.4 Semantics of protocol data format
5.19.1.5 Extension to SID
5.19.1.6 Examples
5.19.2 Search Content
5.19.2.1 Introduction
5.19.2.2 Interfaces and protocol specification
5.19.2.3 Syntax of protocol data format
5.19.2.4 Semantics of protocol data format
5.19.2.5 Extension to SID
5.19.2.6 Examples
5.19.3 Search Contract
5.19.3.1 Introduction
5.19.3.2 Interfaces and protocol specification
5.19.3.3 Syntax of protocol data format
5.19.3.4 Semantics of protocol data format
5.19.3.5 Extension to SID
5.19.3.6 Example
5.19.4 Search Device
5.19.4.1 Introduction
5.19.4.2 Interfaces and protocol specification
5.19.4.3 Syntax of protocol data format
5.19.4.4 Semantics of protocol data format
5.19.4.5 Extension to SID
5.19.5 Search License
5.19.5.1 Introduction
5.19.5.2 Interfaces and protocol specification
5.19.5.3 Syntax of protocol data format
5.19.5.4 Semantics of protocol data format
5.19.5.5 Extension to SID
5.19.5.6 Example
5.19.6 Search Service
5.19.6.1 Introduction
5.19.6.2 Interfaces and protocol specification
5.19.6.3 Syntax of protocol data format
5.19.6.4 Semantics of protocol data format
5.19.6.5 Extension to SID
5.19.7 Search User
5.19.7.1 Introduction
5.19.7.2 Interfaces and protocol specification
5.19.7.3 Syntax of protocol data format
5.19.7.4 Semantics of protocol data format
5.19.7.5 Extension to SID
5.19.7.6 Example
5.20 The Store Services
5.20.1 Store Content
5.20.1.1 Introduction
5.20.1.2 Interfaces and protocol specification
5.20.1.3 Syntax of protocol data format
5.20.1.4 Semantics of protocol data format
5.20.1.5 Extension to SID
5.20.2 Store Contract
5.20.2.1 Introduction
5.20.2.2 Interfaces and protocol specification
5.20.2.3 Syntax of protocol data format
5.20.2.4 Semantics of protocol data format
5.20.2.5 Extension to SID
5.20.3 Store Event
5.20.3.1 Introduction
5.20.3.2 Interfaces and protocol specification
5.20.3.3 Syntax of protocol data format
5.20.3.4 Semantics of protocol data format
5.20.3.5 Extension to SID
5.20.4 Store License
5.20.4.1 Introduction
5.20.4.2 Interfaces and protocol specification
5.20.4.3 Syntax of protocol data format
5.20.4.4 Semantics of protocol data format
5.20.4.5 Extension to SID
5.21 The Transact Services
5.21.1 Transact Entity
5.21.1.1 Introduction
5.21.1.2 Reference model
5.21.1.3 Interfaces and protocol specification
5.21.1.4 Seller Payment Order Entity
5.21.1.4.1 Introduction
5.21.1.4.2 Syntax of protocol data format
5.21.1.4.3 Semantics of protocol data format
5.21.1.5 Buyer Payment Order Entity
5.21.1.5.1 Introduction
5.21.1.5.2 Syntax of protocol data format
5.21.1.5.3 Semantics of protocol data format
5.21.1.6 Mandate Offer Entity
5.21.1.6.1 Introduction
5.21.1.6.2 Syntax of protocol data format
5.21.1.6.3 Semantics of protocol data format
5.21.1.7 Mandate Revoke Entity
5.21.1.7.1 Introduction
5.21.1.7.2 Syntax of protocol data format
5.21.1.7.3 Semantics of protocol data format
5.21.1.8 Extension to SID
5.21.2 Transact Content
5.21.2.1 Introduction
5.21.2.2 Interfaces and protocol specification
5.21.2.3 Syntax of protocol data format
5.21.2.4 Semantics of protocol data format
5.21.2.5 Extension to SID
5.21.3 Transact License
5.21.3.1 Introduction
5.21.3.2 Interfaces and protocol specification
5.21.3.3 Syntax of protocol data format
5.21.3.4 Semantics of protocol data format
5.21.3.5 Extension to SID
5.22 The Verify Services
5.22.1 Verify Contract
5.22.1.1 Introduction
5.22.1.2 Interfaces and protocol specification
5.22.1.3 Syntax of protocol data format
5.22.1.4 Semantics of protocol data format
5.22.1.5 Extension to SID
5.22.2 Verify Device
5.22.2.1 Introduction
5.22.2.2 Interfaces and protocol specification
5.22.2.3 Syntax of protocol data format
5.22.2.4 Semantics of protocol data format
5.22.2.5 Extension to SID
5.22.3 Verify License
5.22.3.1 Introduction
5.22.3.2 Interfaces and protocol specification
5.22.3.3 Syntax of protocol data format
5.22.3.4 Semantics of protocol data format
5.22.3.5 Extension to SID
Previous versions
Keep me up-to-date
Register to receive notifications when updates are made to this standard.
Related Information
Similar Standards
-
BS EN 61937-10:2011
Digital audio. Interface for non-linear PCM encoded audio bitstreams applying IEC 60958, Non-linear PCM bitstreams according to the MPEG-4 Audio Lossless Coding (ALS) format
-
BS EN 61937-5:2006
Digital audio. Interface for non-linear PCM encoded audio bitstreams applying IEC 60958, Non-linear PCM bitstreams according to the DTS (digital theatre systems) format(s)
-
BS EN 61937-6:2006+A1:2014
Digital audio. Interface for non-linear PCM encoded audio bitstreams applying IEC 60958, Non-linear PCM bitstreams according to the MPEG-2 AAC and MPEG-4 AAC formats
-
BS EN 61937-8:2007
Digital audio. Interface for non-linear PCM encoded audio bitstreams applying IEC 60958, Non-linear PCM bitstreams according to the Windows Media Audio (WMA) Professional format
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
3.2 Abbreviated terms
4 Namespaces and conventions
4.1 Namespaces
4.1.1 Introduction
4.1.2 Schema namespaces
4.1.3 BPMN namespaces
4.1.4 Service Type namespaces
4.1.5 Classification Scheme namespaces
4.2 Namespace convention
4.3 Conventions
5 Elementary Services
5.1 Introduction
5.1.1 Overview of Elementary Services
5.1.2 Overview of Operations and Entities
5.1.3 General Service Definition
5.1.4 Service Type
5.1.5 Service Instance Declaration
5.1.6 Message transport
5.1.7 Validation
5.1.8 BPMN 2.0 XML representation of Service workflows
5.1.8.1 Introduction
5.1.8.2 BPMN 2.0 XML representation of abstract base Elementary Service workflows
5.1.8.3 Examples
5.2 Base data types, elements, and common messages
5.2.1 Introduction
5.2.2 MPEG-M base Schema wrapper
5.2.3 Common elements and types
5.2.3.1 Introduction
5.2.3.2 ServiceTypeType
5.2.3.2.1 Introduction
5.2.3.2.2 Syntax
5.2.3.2.3 Semantics
5.2.3.2.4 Additional validation rules
5.2.3.2.4.1 Introduction
5.2.3.2.4.2 The value of the RequestParametersType element must be an existing complex type that extends RequestParametersBaseType.
5.2.3.2.4.3 The value of the CompletionParametersType element must be an existing complex type that extends CompletionParametersBaseType.
5.2.3.3 ContractIdentifier
5.2.3.3.1 Introduction
5.2.3.3.2 Syntax
5.2.3.3.3 Semantics
5.2.3.4 LicenseIdentifier
5.2.3.4.1 Introduction
5.2.3.4.2 Syntax
5.2.3.4.3 Semantics
5.2.3.5 ServiceTypeIdentifier
5.2.3.5.1 Introduction
5.2.3.5.2 Syntax
5.2.3.5.3 Semantics
5.2.3.6 SIDIdentifier
5.2.3.6.1 Introduction
5.2.3.6.2 Syntax
5.2.3.6.3 Semantics
5.2.3.7 UserIdentifier
5.2.3.7.1 Introduction
5.2.3.7.2 Syntax
5.2.3.7.3 Semantics
5.2.3.8 EntityBaseType
5.2.3.8.1 Introduction
5.2.3.8.2 Syntax
5.2.3.8.3 Semantics
5.2.3.9 ContentEntityType
5.2.3.9.1 Introduction
5.2.3.9.2 Syntax
5.2.3.9.3 Semantics
5.2.3.9.4 Additional validation rules
5.2.3.9.4.1 Introduction
5.2.3.9.4.2 If multiple ContentRef elements are specified, they must all point to copies of the same Content.
5.2.3.9.4.3 If multiple dii:Identifier elements are specified, they must all identify the same Content.
5.2.3.10 ContractEntityType
5.2.3.10.1 Introduction
5.2.3.10.2 Syntax
5.2.3.10.3 Semantics
5.2.3.10.4 Additional validation rules
5.2.3.10.4.1 Introduction
5.2.3.10.4.2 If multiple ContractRef elements are specified, they must all point to copies of the same Contract.
5.2.3.10.4.3 If multiple ContractIdentifier elements are specified, they must all identify the same Contract.
5.2.3.11 DeviceEntityType
5.2.3.11.1 Introduction
5.2.3.11.2 Syntax
5.2.3.11.3 Semantics
5.2.3.11.4 Additional validation rules
5.2.3.11.4.1 Introduction
5.2.3.11.4.2 If multiple DeviceRef elements are specified, they must all point to the same Device.
5.2.3.11.4.3 If multiple ipmpinfo-msx:ToolBodyID elements are specified, they must all identify the same Device.
5.2.3.12 LicenseEntityType
5.2.3.12.1 Introduction
5.2.3.12.2 Syntax
5.2.3.12.3 Semantics
5.2.3.12.4 Additional validation rules
5.2.3.12.4.1 Introduction
5.2.3.12.4.2 If multiple LicenseRef elements are specified, they must all point to copies of the same License.
5.2.3.12.4.3 If multiple LicenseIdentifier elements are specified, they must all identify the same License.
5.2.3.13 ServiceTypeEntityType
5.2.3.13.1 Introduction
5.2.3.13.2 Syntax
5.2.3.13.3 Semantics
5.2.3.13.4 Additional validation rules
5.2.3.13.4.1 Introduction
5.2.3.13.4.2 If multiple ServiceTypeRef elements are specified, they must all point to the same Service Type.
5.2.3.13.4.3 If multiple ServiceTypeIdentifier elements are specified, they must all identify the same Service Type.
5.2.3.14 UserEntityType
5.2.3.14.1 Introduction
5.2.3.14.2 Syntax
5.2.3.14.3 Semantics
5.2.3.14.4 Additional validation rules
5.2.3.14.4.1 Introduction
5.2.3.14.4.2 If multiple UserRef elements are specified, they must all point to the same User.
5.2.3.14.4.3 If multiple UserIdentifier elements are specified, they must all identify the same User.
5.2.3.15 RequestParametersBaseType
5.2.3.15.1 Introduction
5.2.3.15.2 Syntax
5.2.3.15.3 Semantics
5.2.3.16 CompletionParametersBaseType
5.2.3.16.1 Introduction
5.2.3.16.2 Syntax
5.2.3.16.3 Semantics
5.2.3.17 SupportedMetadataSchemaType
5.2.3.17.1 Introduction
5.2.3.17.2 Syntax
5.2.3.17.3 Semantics
5.2.3.18 SupportedTransferProtocolType
5.2.3.18.1 Introduction
5.2.3.18.2 Syntax
5.2.3.18.3 Semantics
5.2.3.19 RevocationReasonType
5.2.3.19.1 Introduction
5.2.3.19.2 Syntax
5.2.3.19.3 Semantics
5.2.3.20 EntityOrderInformationType
5.2.3.20.1 Introduction
5.2.3.20.2 Syntax
5.2.3.20.3 Semantics
5.2.3.21 ContentOrderInformationType
5.2.3.21.1 Introduction
5.2.3.21.2 Syntax
5.2.3.21.3 Semantics
5.2.3.22 LicenseOrderInformationType
5.2.3.22.1 Introduction
5.2.3.22.2 Syntax
5.2.3.22.3 Semantics
5.2.4 Base Protocol
5.2.4.1 Introduction
5.2.4.2 Syntax
5.2.4.3 Semantics
5.2.4.4 Examples
5.2.5 Common messages
5.2.5.1 Introduction
5.2.5.2 Syntax
5.2.5.3 Semantics
5.2.5.4 Additional validation rules
5.2.5.4.1 Introduction
5.2.5.4.2 Each complex type extending the ProtocolResponseType must contain a choice between an element of complex type ProtocolSuccessType and an element of complex type ProtocolFailureType or subtypes of them. These elements are named
5.3 MPEG-M service Schema wrapper
5.4 Session control and status polling
5.4.1 Session control messages
5.4.1.1 Introduction
5.4.1.2 Interfaces and protocol specification
5.4.1.3 Syntax of protocol data format
5.4.1.4 Semantics of protocol data format
5.4.1.5 Example
5.4.2 Session status polling messages
5.4.2.1 Introduction
5.4.2.2 Interfaces and protocol specification
5.4.2.3 Syntax of protocol data format
5.4.2.4 Semantics of protocol data format
5.4.2.5 Additional validation rules
5.4.2.5.1 Introduction
5.4.2.5.2 The completion attribute may only be present if the ProgressStatus is set to "CURRENTLY_IN_PROGRESS" or "PROGRESS_PAUSED".
5.4.2.6 Example
5.5 The Authenticate Services
5.5.1 Authenticate Entity
5.5.1.1 Introduction
5.5.1.2 Interfaces and protocol specification
5.5.1.3 Syntax of protocol data format
5.5.1.4 Semantics of protocol data format
5.5.1.5 Additional validation rules
5.5.1.5.1 Introduction
5.5.1.5.2 Each complex type extending the AuthenticateEntityRequestType must contain an authentication entity of the appropriate type (e.g., mpegmb:ContentEntityType for Authenticate Content).
5.5.1.6 Extension to SID
5.5.2 Authenticate Content
5.5.2.1 Introduction
5.5.2.2 Interfaces and protocol specification
5.5.2.3 Syntax of protocol data format
5.5.2.4 Semantics of protocol data format
5.5.2.5 Extension to SID
5.5.3 Authenticate Contract
5.5.3.1 Introduction
5.5.3.2 Interfaces and protocol specification
5.5.3.3 Syntax of protocol data format
5.5.3.4 Semantics of protocol data format
5.5.3.5 Extension to SID
5.5.4 Authenticate License
5.5.4.1 Introduction
5.5.4.2 Interfaces and protocol specification
5.5.4.3 Syntax of protocol data format
5.5.4.4 Semantics of protocol data format
5.5.4.5 Extension to SID
5.5.5 Authenticate User
5.5.5.1 Introduction
5.5.5.2 Interfaces and protocol specification
5.5.5.3 Syntax of protocol data format
5.5.5.4 Semantics of protocol data format
5.5.5.5 Extension to SID
5.6 The Authorize Services
5.6.1 Authorize User
5.6.1.1 Introduction
5.6.1.2 Interfaces and protocol specification
5.6.1.3 Syntax of protocol data format
5.6.1.4 Semantics of protocol data format
5.6.1.5 Extension to SID
5.7 The Check With Services
5.7.1 Check With Contract
5.7.1.1 Introduction
5.7.1.2 Interfaces and protocol specification
5.7.1.3 Syntax of protocol data format
5.7.1.4 Semantics of protocol data format
5.7.1.5 Extension to SID
5.7.2 Check With License
5.7.2.1 Introduction
5.7.2.2 Interfaces and protocol specification
5.7.2.3 Syntax of protocol data format
5.7.2.4 Semantics of protocol data format
5.7.2.5 Extension to SID
5.8 The Create Services
5.8.1 Create Content
5.8.1.1 Introduction
5.8.1.2 Interfaces and protocol specification
5.8.1.3 Syntax of protocol data format
5.8.1.4 Semantics of protocol data format
5.8.1.5 Extension to SID
5.8.2 Create Contract
5.8.2.1 Introduction
5.8.2.2 Interfaces and protocol specification
5.8.2.3 Syntax of protocol data format
5.8.2.4 Semantics of protocol data format
5.8.2.5 Extension to SID
5.8.3 Create License
5.8.3.1 Introduction
5.8.3.2 Interfaces and protocol specification
5.8.3.3 Syntax of protocol data format
5.8.3.4 Semantics of protocol data format
5.8.3.5 Extension to SID
5.9 The Deliver Services
5.9.1 Deliver Content
5.9.1.1 Introduction
5.9.1.2 Interfaces and protocol specification
5.9.1.3 Syntax of protocol data format
5.9.1.4 Semantics of protocol data format
5.9.1.5 Extension to SID
5.9.1.6 Example
5.9.2 Deliver Contract
5.9.2.1 Introduction
5.9.2.2 Interfaces and protocol specification
5.9.2.3 Syntax of protocol data format
5.9.2.4 Semantics of protocol data format
5.9.2.5 Extension to SID
5.10 The Describe Services
5.10.1 Describe Entity
5.10.1.1 Introduction
5.10.1.2 Set Describe Entity Protocol
5.10.1.2.1 Interfaces and protocol specification
5.10.1.2.2 Syntax of protocol data format
5.10.1.2.3 Semantics of protocol data format
5.10.1.2.4 Additional validation rules
5.10.1.2.4.1 Introduction
5.10.1.2.4.2 The metadata schema of the description conveyed in the AccessUnit element of the request must conform to one of the metadata schemas specified by the sid:SupportedMetadataSchema elements of the SID.
5.10.1.3 Get Describe Entity Protocol
5.10.1.3.1 Interfaces and protocol specification
5.10.1.3.1.1 General
5.10.1.3.1.2 Processing of FRU
5.10.1.3.1.3 Conformance to ISO/IEC 23001-2
5.10.1.3.1.4 Processing of FUU
5.10.1.3.2 Syntax of protocol data format
5.10.1.3.3 Semantics of protocol data format
5.10.1.3.4 Additional validation rules
5.10.1.3.4.1 Introduction
5.10.1.3.4.2 If present, the SupportedMetadataSchema elements must be a subset of the sid:SupportedMetadataSchema elements in the SID of the Service Instance. However, the client sets its own preferences through the pref attribute.
5.10.1.3.4.3 The metadata schema of the description conveyed in the AccessUnit element of the response must conform to one of the metadata schemas specified by the SupportedMetadataSchema elements of the request message.
5.10.1.4 Extension to SID
5.10.2 Describe Content
5.10.2.1 Introduction
5.10.2.2 Set Describe Content Protocol
5.10.2.2.1 Interfaces and protocol specification
5.10.2.2.2 Syntax of protocol data format
5.10.2.2.3 Semantics of protocol data format
5.10.2.2.4 Additional validation rules
5.10.2.2.4.1 Introduction
5.10.2.2.4.2 The EntityIdentifier must be a Content Identifier represented as dii:Identifier.
5.10.2.2.5 Example
5.10.2.3 Get Describe Content Protocol
5.10.2.3.1 Interfaces and protocol specification
5.10.2.3.2 Syntax of protocol data format
5.10.2.3.3 Semantics of protocol data format
5.10.2.3.4 Additional validation rules
5.10.2.3.4.1 Introduction
5.10.2.3.4.2 The EntityIdentifier must be a Content Identifier represented as dii:Identifier.
5.10.2.3.5 Examples
5.10.2.4 Extension to SID
5.10.3 Describe Device
5.10.3.1 Introduction
5.10.3.2 Set Describe Device Protocol
5.10.3.2.1 Interfaces and protocol specification
5.10.3.2.2 Syntax of protocol data format
5.10.3.2.3 Semantics of protocol data format
5.10.3.2.4 Additional validation rules
5.10.3.2.4.1 Introduction
5.10.3.2.4.2 The EntityIdentifier must be a Device Identifier represented as ipmpinfo-msx:ToolBodyID.
5.10.3.2.5 Example
5.10.3.3 Get Describe Device Protocol
5.10.3.3.1 Interfaces and protocol specification
5.10.3.3.2 Syntax of protocol data format
5.10.3.3.3 Semantics of protocol data format
5.10.3.3.4 Additional validation rules
5.10.3.3.4.1 Introduction
5.10.3.3.4.2 The EntityIdentifier must be a Device Identifier represented as ipmpinfo-msx:ToolBodyID.
5.10.3.3.5 Example
5.10.3.4 Extension to SID
5.10.4 Describe Service
5.10.4.1 Introduction
5.10.4.2 Set Describe Service Protocol
5.10.4.2.1 Interfaces and protocol specification
5.10.4.2.2 Syntax of protocol data format
5.10.4.2.3 Semantics of protocol data format
5.10.4.2.4 Additional validation rules
5.10.4.2.4.1 Introduction
5.10.4.2.4.2 The EntityIdentifier must be a Service Instance Identifier represented as mpegmb:SIDIdentifier.
5.10.4.2.5 Example
5.10.4.3 Get Describe Service Protocol
5.10.4.3.1 Interfaces and protocol specification
5.10.4.3.2 Syntax of protocol data format
5.10.4.3.3 Semantics of protocol data format
5.10.4.3.4 Additional validation rules
5.10.4.3.4.1 Introduction
5.10.4.3.4.2 The EntityIdentifier must be an SID Identifier represented as mpegmb:SIDIdentifier.
5.10.4.3.5 Example
5.10.4.4 Extension to SID
5.10.5 Describe User
5.10.5.1 Introduction
5.10.5.2 Set Describe User Protocol
5.10.5.2.1 Interfaces and protocol specification
5.10.5.2.2 Syntax of protocol data format
5.10.5.2.3 Semantics of protocol data format
5.10.5.2.4 Additional validation rules
5.10.5.2.4.1 Introduction
5.10.5.2.4.2 The EntityIdentifier must be a User Identifier represented as mpegmb:UserIdentifier.
5.10.5.2.5 Example
5.10.5.3 Get Describe User Protocol
5.10.5.3.1 Interfaces and protocol specification
5.10.5.3.2 Syntax of protocol data format
5.10.5.3.3 Semantics of protocol data format
5.10.5.3.4 Additional validation rules
5.10.5.3.4.1 Introduction
5.10.5.3.4.2 The EntityIdentifier must be a User Identifier represented as mpegmb:UserIdentifier.
5.10.5.3.5 Examples
5.10.5.4 Extension to SID
5.11 The Identify Services
5.11.1 Identify Entity
5.11.1.1 Introduction
5.11.1.2 Interfaces and protocol specification
5.11.1.3 Syntax of protocol data format
5.11.1.4 Semantics of protocol data format
5.11.1.5 Extension to SID
5.11.2 Identify Content
5.11.2.1 Introduction
5.11.2.2 Interfaces and protocol specification
5.11.2.3 Syntax of protocol data format
5.11.2.4 Semantics of protocol data format
5.11.2.5 Extension to SID
5.11.3 Identify Contract
5.11.3.1 Introduction
5.11.3.2 Interfaces and protocol specification
5.11.3.3 Syntax of protocol data format
5.11.3.4 Semantics of protocol data format
5.11.3.5 Extension to SID
5.11.4 Identify Device
5.11.4.1 Introduction
5.11.4.2 Interfaces and protocol specification
5.11.4.3 Syntax of protocol data format
5.11.4.4 Semantics of protocol data format
5.11.4.5 Extension to SID
5.11.5 Identify License
5.11.5.1 Introduction
5.11.5.2 Interfaces and protocol specification
5.11.5.3 Syntax of protocol data format
5.11.5.4 Semantics of protocol data format
5.11.5.5 Extension to SID
5.11.6 Identify User
5.11.6.1 Introduction
5.11.6.2 Interfaces and protocol specification
5.11.6.3 Syntax of protocol data format
5.11.6.4 Semantics of protocol data format
5.11.6.5 Additional validation rules
5.11.6.5.1 Introduction
5.11.6.5.2 The UserIdentificationAssertion shall only be used if the User to be identified is not the same as the requesting client. If the client requests a user identifier for himself/herself, then the saml:Assertion element of the mpegmb:ProtocolRequestType shall be used.
5.11.6.6 Extension to SID
5.12 The Negotiate Services
5.12.1 Negotiate Entity
5.12.1.1 Introduction
5.12.1.2 General Considerations
5.12.1.3 Interfaces and protocol specification
5.12.1.4 SetupNegotiationEntity
5.12.1.4.1 Syntax of protocol data format
5.12.1.4.2 Semantics of protocol data format
5.12.1.4.3 Additional validation rules
5.12.1.4.3.1 Introduction
5.12.1.4.3.2 If at least one Participant is specified, the publish attribute of the SetupNegotiationEntityRequestType is typically set to false.
5.12.1.4.3.3 The accepted attribute of all IssueOffer elements must be set to false in the SetupNegotiationEntityRequestType.
5.12.1.4.3.4 If the publish attribute of the SetupNegotiationEntityRequestType is set to false, at least one Participant must be specified.
5.12.1.4.3.5 The accepted attribute of the IssueType may only be set to true if exactly one ProposedValue element is provided (i.e., the accepted value).
5.12.1.5 AdmissionEntity
5.12.1.5.1 Syntax of protocol data format
5.12.1.5.2 Semantics of protocol data format
5.12.1.6 OfferEntity
5.12.1.6.1 Syntax of protocol data format
5.12.1.6.2 Semantics of protocol data format
5.12.1.7 AgreementEntity
5.12.1.7.1 Syntax of protocol data format
5.12.1.7.2 Semantics of protocol data format
5.12.1.8 Extension to SID
5.12.2 Negotiate Contract
5.12.2.1 Introduction
5.12.2.2 Interfaces and protocol specification
5.12.2.3 Syntax of protocol data format
5.12.2.4 Semantics of protocol data format
5.12.2.5 Additional validation rules
5.12.2.5.1 Introduction
5.12.2.5.2 The NegotiationItemTemplate of the SetupNegotiationContractRequest must be of type mpegmb:ContractEntityType.
5.12.2.5.3 The TemplateEntity of the AgreementContractRequest must be of type mpegmb:ContractEntityType.
5.12.2.5.4 The FinalEntity of the AgreementContractRequest must be of type mpegmb:ContractEntityType.
5.12.2.5.5 The TemplateEntity of the AgreementContractResponse must be of type mpegmb:ContractEntityType.
5.12.2.5.6 The FinalEntity of the AgreementContractResponse must be of type mpegmb:ContractEntityType.
5.12.2.6 Extension to SID
5.12.2.7 Example
5.12.3 Negotiate License
5.12.3.1 Introduction
5.12.3.2 Interfaces and protocol specification
5.12.3.3 Syntax of protocol data format
5.12.3.4 Semantics of protocol data format
5.12.3.4.1 Additional validation rules
5.12.3.4.1.1 Introduction
5.12.3.4.1.2 The NegotiationItemTemplate of the SetupNegotiationLicenseRequest must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.3 The TemplateEntity of the AgreementLicenseRequest must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.4 The FinalEntity of the AgreementLicenseRequest must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.5 The TemplateEntity of the AgreementLicenseResponse must be of type mpegmb:LicenseEntityType.
5.12.3.4.1.6 The FinalEntity of the AgreementLicenseResponse must be of type mpegmb:LicenseEntityType.
5.12.3.5 Extension to SID
5.13 The Package Services
5.13.1 Package Content
5.13.1.1 Introduction
5.13.1.2 Interfaces and protocol specification
5.13.1.3 Syntax of protocol data format
5.13.1.4 Semantics of protocol data format
5.13.1.5 Extension to SID
5.13.1.6 Example
5.14 The Post Services
5.14.1 Post Content
5.14.1.1 Introduction
5.14.1.2 Interfaces and protocol specification
5.14.1.3 Syntax of protocol data format
5.14.1.4 Semantics of protocol data format
5.14.1.5 Extension to SID
5.14.1.6 Example
5.15 The Present Services
5.15.1 Present Entity
5.15.1.1 Introduction
5.15.1.2 Interfaces and protocol specification
5.15.1.3 Syntax of protocol data format
5.15.1.4 Semantics of protocol data format
5.15.1.5 Extension to SID
5.15.2 Present Contract
5.15.2.1 Introduction
5.15.2.2 Interfaces and protocol specification
5.15.2.3 Syntax of protocol data format
5.15.2.4 Semantics of protocol data format
5.15.2.5 Extension to SID
5.15.3 Present License
5.15.3.1 Introduction
5.15.3.2 Interfaces and protocol specification
5.15.3.3 Syntax of protocol data format
5.15.3.4 Semantics of protocol data format
5.15.3.5 Extension to SID
5.16 The Process Services
5.16.1 Process Content
5.16.1.1 Introduction
5.16.1.2 Interfaces and protocol specification
5.16.1.3 Syntax of protocol data format
5.16.1.4 Semantics of protocol data format
5.16.1.5 Additional validation rules
5.16.1.5.1 Introduction
5.16.1.5.2 The Service Type specified by the ServiceTypeEntity must have the same Service Type Identifier as the one specified in the underlying Service Instance Declaration.
5.16.1.5.3 The type of RequestParameters must conform to the type specified by the RequestParametersType element of the Service Type for that particular Process Content Service Instance.
5.16.1.5.4 The type of CompletionParameters must conform to the type specified by the CompletionParametersType element of the Service Type for that particular Process Content Service Instance.
5.16.1.6 Extension to SID
5.16.2 Process License
5.16.2.1 Introduction
5.16.2.2 Interfaces and protocol specification
5.16.2.3 Syntax of protocol data format
5.16.2.4 Semantics of protocol data format
5.16.2.5 Extension to SID
5.17 The Request Services
5.17.1 Request Content
5.17.1.1 Introduction
5.17.1.2 Interfaces and protocol specification
5.17.1.3 Syntax of protocol data format
5.17.1.4 Semantics of protocol data format
5.17.1.5 Extension to SID
5.17.1.6 Examples
5.17.2 Request Contract
5.17.2.1 Introduction
5.17.2.2 Interfaces and protocol specification
5.17.2.3 Syntax of protocol data format
5.17.2.4 Semantics of protocol data format
5.17.2.5 Extension to SID
5.17.3 Request Device
5.17.3.1 Introduction
5.17.3.2 Interfaces and protocol specification
5.17.3.3 Syntax of protocol data format
5.17.3.4 Semantics of protocol data format
5.17.3.5 Extension to SID
5.17.4 Request Event
5.17.4.1 Introduction
5.17.4.2 Interfaces and protocol specification
5.17.4.3 Syntax of protocol data format
5.17.4.4 Semantics of protocol data format
5.17.4.5 Additional validation rules
5.17.4.5.1 Introduction
5.17.4.5.2 If the RequestEventRequest message contains a ContentEntity and the RequestEventResponse message contains a RequestEventSuccess, then the RequestEventSuccess shall contain a erl:ERR.
5.17.4.5.3 If the RequestEventRequest message contains a erl:ERR and the RequestEventResponse message contains a RequestEventSuccess, then the RequestEventSuccess shall contain one or more erl:ER elements.
5.17.4.6 Extension to SID
5.17.5 Request License
5.17.5.1 Introduction
5.17.5.2 Interfaces and protocol specification
5.17.5.3 Syntax of protocol data format
5.17.5.4 Semantics of protocol data format
5.17.5.5 Extension to SID
5.18 The Revoke Services
5.18.1 Revoke Entity
5.18.1.1 Introduction
5.18.1.2 Interfaces and protocol specification
5.18.1.3 Syntax of protocol data format
5.18.1.4 Semantics of protocol data format
5.18.1.5 Extension to SID
5.18.2 Revoke Content
5.18.2.1 Introduction
5.18.2.2 Interfaces and protocol specification
5.18.2.3 Syntax of protocol data format
5.18.2.4 Semantics of protocol data format
5.18.2.5 Additional validation rules
5.18.2.5.1 Introduction
5.18.2.5.2 The RevokedEntity element of the RevokeContentRequest message must be of type mpegmb:ContentEntityType.
5.18.2.6 Extension to SID
5.18.3 Revoke Contract
5.18.3.1 Introduction
5.18.3.2 Interfaces and protocol specification
5.18.3.3 Syntax of protocol data format
5.18.3.4 Semantics of protocol data format
5.18.3.5 Additional validation rules
5.18.3.5.1 Introduction
5.18.3.5.2 The RevokedEntity element of the RevokeContractRequest message must be of type mpegmb:ContractEntityType.
5.18.3.6 Extension to SID
5.18.4 Revoke License
5.18.4.1 Introduction
5.18.4.2 Interfaces and protocol specification
5.18.4.3 Syntax of protocol data format
5.18.4.4 Semantics of protocol data format
5.18.4.5 Additional validation rules
5.18.4.5.1 Introduction
5.18.4.5.2 The RevokedEntity element of the RevokeLicenseRequest message must be of type mpegmb:LicenseEntityType.
5.18.4.6 Extension to SID
5.19 The Search Services
5.19.1 Search Entity
5.19.1.1 Introduction
5.19.1.2 Interfaces and protocol specification
5.19.1.3 Syntax of protocol data format
5.19.1.4 Semantics of protocol data format
5.19.1.5 Extension to SID
5.19.1.6 Examples
5.19.2 Search Content
5.19.2.1 Introduction
5.19.2.2 Interfaces and protocol specification
5.19.2.3 Syntax of protocol data format
5.19.2.4 Semantics of protocol data format
5.19.2.5 Extension to SID
5.19.2.6 Examples
5.19.3 Search Contract
5.19.3.1 Introduction
5.19.3.2 Interfaces and protocol specification
5.19.3.3 Syntax of protocol data format
5.19.3.4 Semantics of protocol data format
5.19.3.5 Extension to SID
5.19.3.6 Example
5.19.4 Search Device
5.19.4.1 Introduction
5.19.4.2 Interfaces and protocol specification
5.19.4.3 Syntax of protocol data format
5.19.4.4 Semantics of protocol data format
5.19.4.5 Extension to SID
5.19.5 Search License
5.19.5.1 Introduction
5.19.5.2 Interfaces and protocol specification
5.19.5.3 Syntax of protocol data format
5.19.5.4 Semantics of protocol data format
5.19.5.5 Extension to SID
5.19.5.6 Example
5.19.6 Search Service
5.19.6.1 Introduction
5.19.6.2 Interfaces and protocol specification
5.19.6.3 Syntax of protocol data format
5.19.6.4 Semantics of protocol data format
5.19.6.5 Extension to SID
5.19.7 Search User
5.19.7.1 Introduction
5.19.7.2 Interfaces and protocol specification
5.19.7.3 Syntax of protocol data format
5.19.7.4 Semantics of protocol data format
5.19.7.5 Extension to SID
5.19.7.6 Example
5.20 The Store Services
5.20.1 Store Content
5.20.1.1 Introduction
5.20.1.2 Interfaces and protocol specification
5.20.1.3 Syntax of protocol data format
5.20.1.4 Semantics of protocol data format
5.20.1.5 Extension to SID
5.20.2 Store Contract
5.20.2.1 Introduction
5.20.2.2 Interfaces and protocol specification
5.20.2.3 Syntax of protocol data format
5.20.2.4 Semantics of protocol data format
5.20.2.5 Extension to SID
5.20.3 Store Event
5.20.3.1 Introduction
5.20.3.2 Interfaces and protocol specification
5.20.3.3 Syntax of protocol data format
5.20.3.4 Semantics of protocol data format
5.20.3.5 Extension to SID
5.20.4 Store License
5.20.4.1 Introduction
5.20.4.2 Interfaces and protocol specification
5.20.4.3 Syntax of protocol data format
5.20.4.4 Semantics of protocol data format
5.20.4.5 Extension to SID
5.21 The Transact Services
5.21.1 Transact Entity
5.21.1.1 Introduction
5.21.1.2 Reference model
5.21.1.3 Interfaces and protocol specification
5.21.1.4 Seller Payment Order Entity
5.21.1.4.1 Introduction
5.21.1.4.2 Syntax of protocol data format
5.21.1.4.3 Semantics of protocol data format
5.21.1.5 Buyer Payment Order Entity
5.21.1.5.1 Introduction
5.21.1.5.2 Syntax of protocol data format
5.21.1.5.3 Semantics of protocol data format
5.21.1.6 Mandate Offer Entity
5.21.1.6.1 Introduction
5.21.1.6.2 Syntax of protocol data format
5.21.1.6.3 Semantics of protocol data format
5.21.1.7 Mandate Revoke Entity
5.21.1.7.1 Introduction
5.21.1.7.2 Syntax of protocol data format
5.21.1.7.3 Semantics of protocol data format
5.21.1.8 Extension to SID
5.21.2 Transact Content
5.21.2.1 Introduction
5.21.2.2 Interfaces and protocol specification
5.21.2.3 Syntax of protocol data format
5.21.2.4 Semantics of protocol data format
5.21.2.5 Extension to SID
5.21.3 Transact License
5.21.3.1 Introduction
5.21.3.2 Interfaces and protocol specification
5.21.3.3 Syntax of protocol data format
5.21.3.4 Semantics of protocol data format
5.21.3.5 Extension to SID
5.22 The Verify Services
5.22.1 Verify Contract
5.22.1.1 Introduction
5.22.1.2 Interfaces and protocol specification
5.22.1.3 Syntax of protocol data format
5.22.1.4 Semantics of protocol data format
5.22.1.5 Extension to SID
5.22.2 Verify Device
5.22.2.1 Introduction
5.22.2.2 Interfaces and protocol specification
5.22.2.3 Syntax of protocol data format
5.22.2.4 Semantics of protocol data format
5.22.2.5 Extension to SID
5.22.3 Verify License
5.22.3.1 Introduction
5.22.3.2 Interfaces and protocol specification
5.22.3.3 Syntax of protocol data format
5.22.3.4 Semantics of protocol data format
5.22.3.5 Extension to SID