SIST ES 202 504-19 V1.1.1:2008
Open Service Access (OSA) - Parlay X Web Services - Part 19: Multimedia Streaming Control (Parlay X 3)
Open Service Access (OSA) - Parlay X Web Services - Part 19: Multimedia Streaming Control (Parlay X 3)
New ParlayX specification to cover Multimedia Streaming Control, corresponding to 3GPP TS 29.199-19 Rel-7. The present document is part 19 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Multimedia Streaming Control Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
Odprti dostop do storitve (OSA) - Spletne storitve Parlay X - 19. del: Krmiljenje večpredstavnostnega strujanja (Parlay X 3)
General Information
Buy Standard
Standards Content (Sample)
ETSI ES 202 504-19 V1.1.1 (2008-05)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 19: Multimedia Streaming Control
(Parlay X 3)
�
---------------------- Page: 1 ----------------------
2 ETSI ES 202 504-19 V1.1.1 (2008-05)
Reference
DES/TISPAN-01034-19-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI ES 202 504-19 V1.1.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
4.1 Overview.8
5 Namespaces.9
6 Sequence diagrams.9
6.1 Getting requests.10
6.2 Charging refund.11
6.3 Trans-coding update.12
6.4 Controlling multiple streams .12
6.5 Redirecting a stream.13
6.6 Multimedia Stream Control with Dynamic QoS .14
7 XML Schema data type definition .15
7.1 MediaStreamRequest structure.15
7.2 MediaStreamInformation structure.15
7.3 StreamControlAction enumeration.16
7.4 MediaStreamStatus enumeration.16
8 Web Service interface definition.16
8.1 Interface: Streaming.16
8.1.1 Operation: startMediaStream.16
8.1.1.1 Input message: startMediaStreamRequest.16
8.1.1.2 Output message: startMediaStreamResponse.17
8.1.1.3 Referenced faults.17
8.1.2 Operation: getStreamingRequests.17
8.1.2.1 Input message: getStreamingRequestsRequest .17
8.1.2.2 Output message: getStreamingRequestsResponse.17
8.1.2.3 Referenced faults.17
8.1.3 Operation: controlMediaStream.18
8.1.3.1 Input message: controlMediaStreamRequest.18
8.1.3.2 Output message: controlMediaStreamResponse .18
8.1.3.3 Referenced faults.18
8.1.4 Operation: getMediaStreamStatus.18
8.1.4.1 Input message: getMediaStreamStatusRequest.18
8.1.4.2 Output message: getMediaStreamStatusResponse.18
8.1.4.3 Referenced faults.18
8.1.5 Operation: refundEndUserCharges.19
8.1.5.1 Input message: refundEndUserChargesRequest.19
8.1.5.2 Output message: refundEndUserChargesResponse.19
8.1.5.3 Referenced faults.19
8.2 Interface: StreamingNotificationManager.19
8.2.1 Operation: startNotification.19
8.2.1.1 Input message: startNotificationRequest.20
8.2.1.2 Output message: startNotificationResponse.20
8.2.1.3 Referenced faults.20
8.2.2 Operation: endNotification.20
ETSI
---------------------- Page: 3 ----------------------
4 ETSI ES 202 504-19 V1.1.1 (2008-05)
8.2.2.1 Input message: endNotificationRequest.20
8.2.2.2 Output message: endNotificationResponse.20
8.2.2.3 Referenced faults.21
8.3 Interface: StreamingNotification.21
8.3.1 Operation: notifyMediaStreamRequest.21
8.3.1.1 Input message: notifyMediaStreamRequestRequest .21
8.3.1.2 Output message: notifyMediaStreamRequestResponse.21
8.3.1.3 Referenced faults.21
8.3.2 Operation: notifyMediaStreamStatus.21
8.3.2.1 Input message: notifyMediaStreamStatusRequest .21
8.3.2.2 Output message: notifyMediaStreamStatusResponse.21
8.3.2.3 Referenced faults.22
8.3.3 Operation: notifyError.22
8.3.3.1 Input message: notifyErrorRequest.22
8.3.3.2 Output message: notifyErrorResponse.22
8.3.3.3 Referenced faults.22
8.3.4 Operation: notifyEnd.22
8.3.4.1 Input message: notifyEndRequest.22
8.3.4.2 Output message: notifyEndResponse.22
8.3.4.3 Referenced faults.22
9 Fault definitions.23
9.1 ServiceException.23
9.1.1 SVC0270: Charge failed.23
10 Service policies .23
Annex A (normative): WSDL for Multimedia Streaming Control.24
Annex B (informative): Bibliography.25
History .26
ETSI
---------------------- Page: 4 ----------------------
5 ETSI ES 202 504-19 V1.1.1 (2008-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 19 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web
Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence";
Part 15: "Message Broadcast";
Part 16: "Geocoding";
Part 17: "Application-driven Quality of Service (QoS)";
Part 18: "Device Capabilities and Configuration";
Part 19: "Multimedia Streaming Control";
Part 20: "Multimedia Multicast Session Management".
ETSI
---------------------- Page: 5 ----------------------
6 ETSI ES 202 504-19 V1.1.1 (2008-05)
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 3.0 set of specifications.
The present document is equivalent to 3GPP TS 29.199-19 V7.0.2 (Release 7).
ETSI
---------------------- Page: 6 ----------------------
7 ETSI ES 202 504-19 V1.1.1 (2008-05)
1 Scope
The present document is part 19 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Multimedia Streaming Control Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
---------------------- Page: 7 ----------------------
8 ETSI ES 202 504-19 V1.1.1 (2008-05)
[2] ETSI ES 202 504-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 3)".
[3] ETSI ES 202 504-6: "Open Service Access (OSA); Parlay X Web Services; Part 6: Payment
(Parlay X 3)".
[4] ETSI ES 204 915-7: "Open Service Access (OSA); Application Programming Interface (API);
Part 7: Terminal Capabilities SCF (Parlay 6)".
[5] ISO 4217: "Codes for the representation of currencies and funds".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 504-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ES 202 504-1 [2] apply.
4 Detailed service description
The service provided to an end-user is consumption of streaming multimedia. The end-user has a terminal that is able to
request a media stream, either from a built-in player, or an installed application. The terminal can be any terminal with
streaming media playing capabilities, and the service should allow a user to transfer between his terminals.
• The basic scenario is where an individual is browsing the Internet and finds some interesting content that
he/she wants to watch. The end-user is then either doing this through the operator’s portal or accesses the
content provider’s site. In the first case, the request is then processed through the portal, and charged as the
stream is set-up. In the second case, the content provider redirects the request to the operator, so that the
terminal capabilities can be collected and charging is done, before the stream is started.
• One scenario is an individual watching his favourite sports stream on his TV or PC at home, but he/she must
leave the house of some reason, and still wants to continue the session on his mobile terminal. In that case
he/she would transfer the ongoing session to the other terminal with other capabilities, since he already paid
for the entire episode.
• The other way is a similar case where an individual arrives at a destination with better viewing capabilities.
4.1 Overview
The figure below shows streaming content delivered to mobile terminals, but is not restricted to any particular terminal
type. The content is either on a location accessible over the Internet or stored locally on an operator's domain or the
content provider's domain. The access to the content is done through a smart router controlling the stream towards the
terminal. Transcoding of a stream is an optional feature that could allow users to switch between different terminal and
networks, while consuming content from a streaming source.
ETSI
---------------------- Page: 8 ----------------------
9 ETSI ES 202 504-19 V1.1.1 (2008-05)
Figure 4.1.1
5 Namespaces
The Streaming interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/streaming/ v3_0
The StreamingNotificationManager interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/ streaming /notification_manager/v3_0
The StreamingNotification interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/ streaming /notification/v3_0
The data types are defined in the namespace:
http://www.csapi.org/schema/parlayx/ streaming /v3_0
The 'xsd' namespace is used in the present document to refer to the XML Schema data types defined in
XML Schema [1]. The use of the name 'xsd' is not semantically significant.
6 Sequence diagrams
The following use case diagram defines the core functionality which should be supported by the Multimedia Streaming
Control web service. These high level logical use cases will be supported by the defined API, but not necessarily on a
one to one mapping basis.
ETSI
---------------------- Page: 9 ----------------------
10 ETSI ES 202 504-19 V1.1.1 (2008-05)
Figure 6.1
6.1 Getting requests
The following diagram illustrates the scenario where incoming stream requests are buffered at the operator. The content
provider periodically retrieves streaming requests and handles them.
ETSI
---------------------- Page: 10 ----------------------
11 ETSI ES 202 504-19 V1.1.1 (2008-05)
: End-User
: Content : Router
: Multimedia
Provider
StreamingControl
Request content (SETUP)
getStreamingRequests
Start the stream
including charging
info and
startMediaStream
transcoding
Content description
PLAY
Stream started
notifyMediaStreamStatus
Stream completed
End stream
notifyMediaStreamStatus
6.2 Charging refund
The following diagram illustrates the scenario where incoming stream requests are sent to the content provider when
received by the operator. In this scenario the stream is cancelled before playing is completed and the content provider
refunds an amount previously requested.
: End-User
: Content : Router
: Multimedia
Provider
StreamingControl
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and
startMediaStream
transcoding
Content description
Stream started PLAY
notifyMediaStreamStatus
Stream cancelled TEARDOWN
or interrupted
notifyMediaStreamStatus
Stream interrupted
so refund charging
refundEndUserCharges
ETSI
---------------------- Page: 11 ----------------------
12 ETSI ES 202 504-19 V1.1.1 (2008-05)
6.3 Trans-coding update
The following diagram illustrates the scenario where the capabilities for a terminal or a network changes, for example
due to handover between GPRS and 3G. The contents provider is notified about this change and can change for
example transcoding of the stream.
: Multimedia
: Content : Router : End-User
StreamingControl
Provider
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and trans-
startMediaStream
coding
Content description
Stream started PLAY
notifyMediaStreamStatus
Capabilities
changed
notifyMediaStreamStatus
Stream
capabilities
changed, send
Send new
startMediaStream
new trans-coding
trans-coding
6.4 Controlling multiple streams
The following diagram illustrates the scenario where the content provider pauses an ongoing stream and temporarily
plays another stream, for example an advertisement. When the second stream ends the first original stream is continued.
From the end-user’s point of view this should be perceived as one uninterrupted stream.
ETSI
---------------------- Page: 12 ----------------------
13 ETSI ES 202 504-19 V1.1.1 (2008-05)
: Multimedia
: Content : Router : End-User
Provider StreamingControl
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and
startMediaStream
transcoding
Content description
Stream 1 started PLAY
Content provider
notifyMediaStreamStatus
pauses stream
and plays an other
controlMediaStream
stream
Pause stream 1
Stream 2 started
Stream 2 finished
notifyMediaStreamStatus
Second stream
finished, resume
controlMediaStream
Resume stream 1
the first stream
Stream 1 resumed
Stream 1 finished
notifyMediaStreamStatus
End stream
6.5 Redirecting a stream
The following diagram illustrates the scenario where a stream is being redirected to another device due to a user
request. The contents provider receives the request from the end-user and continues the stream to the new device.
ETSI
---------------------- Page: 13 ----------------------
14 ETSI ES 202 504-19 V1.1.1 (2008-05)
: Multimedia : End-User
: Content : Router
StreamingControl
Provider
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and trans-
startMediaStream
coding
Content description
Stream started PLAY
notifyMediaStreamStatus
PAUSE
Stream paused
notifyMediaStreamStatus
Stream
capabilities
Request content (New device)
notifyMediaStreamRequest
changed, send
new trans-coding
startMediaStream
Content description
Stream started PLAY
notifyMediaStreamStatus
6.6 Multimedia Stream Control with Dynamic QoS
The following sequence diagram provides an example of how an application could combine functionality from the
Multimedia Streaming Control web service (this specification) with the Application Driven QoS (ADQ) web service to
provide guaranteed media stream delivery.
Flow summary:
1. Content Provider receives a NotifyMediaStreamRequest which includes the content identifier, terminal
capabilities and an estimated available bandwidth of the current network session.
2. Based upon content requirements and current network bandwidth, the content provider may decide to provide
a guaranteed QoS for content delivery by applying a temporary QoS session (addTemporaryQoSFeature on
ADQ Web Service).
3. The content provider will then continue to setup the media stream through the StartMediaStream operation, as
for previous scenarios.
4. At some point during the ongoing stream, the network / terminal capabilities change and the content provider
is notified by the operator with the NotifySessionStatus operation.
5. Based on the new session parameters (e.g. available bandwidth), the content provider may modify the
guaranteed QoS parameters previously requested (modifyTemporaryQoSFeature).
6. Upon stream completion, content provider will remove the previously requested QoS session
(removeTemporaryQosFeature).
ETSI
---------------------- Page: 14 ----------------------
15 ETSI ES 202 504-19 V1.1.1 (2008-05)
: ADQ Web
: Content : Router : End-User
: Multimedia
Service
Provider
StreamingControl
startStreamingNotification
Request content (SETUP)
on
notifyMediaStreamRequest
addTemporaryQoSFeature
startMediaStream
Content description
Stream started PLAY
notifyMediaStreamStatus
Stream
capabilities
changed
notifyMediaStreamStatus
modifyTemporaryQoSFeature
Stream
TEARDOWN
cancelled
notifyMediaStreamStatus
removeTemporaryQoSFeature
7 XML Schema data type definition
7.1 MediaStreamRequest structure
Data type used to capture attributes of a single media stream request.
Element Name Element Type Optional Description
subscriberIdentifier xsd:anyURI No Identity of subscriber / end-user making the
request for content streaming
contentIdentifier xsd:anyURI No Identifier / Address of requested content item
sessionIdentifier xsd:string No Operator provided session identifier
streamTransfer xsd:boolean Yes States whether this request is a result of a
stream transfer (e.g. transfer of existing
stream from mobile device to a PC) or is a
new media stream request.
terminalCapabilities xsd:string [0.unbounded] Yes Terminal capability description derived from
TpTerminalCapabilities (ref ES 204 915-7 [4])
availableBandwidth xsd:int Yes Estimation of current available network
bandwidth in bits per second
7.2 MediaStreamInformation structure
Composite data type required by the getMediaStreamStatus operation in order to return all requested information in a
single message part.
Element Name Element Type Optional Description
status MediaStreamStatus No Communi
...
Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 19: Multimedia Streaming Control
(Parlay X 3)
�
---------------------- Page: 1 ----------------------
2 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
Reference
DES/TISPAN-01034-19-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
---------------------- Page: 2 ----------------------
3 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
4.1 Overview.8
5 Namespaces.9
6 Sequence diagrams.9
6.1 Getting requests.10
6.2 Charging refund.11
6.3 Trans-coding update.12
6.4 Controlling multiple streams .12
6.5 Redirecting a stream.13
6.6 Multimedia Stream Control with Dynamic QoS .14
7 XML Schema data type definition .15
7.1 MediaStreamRequest structure.15
7.2 MediaStreamInformation structure.15
7.3 StreamControlAction enumeration.16
7.4 MediaStreamStatus enumeration.16
8 Web Service interface definition.16
8.1 Interface: Streaming.16
8.1.1 Operation: startMediaStream.16
8.1.1.1 Input message: startMediaStreamRequest.16
8.1.1.2 Output message: startMediaStreamResponse.17
8.1.1.3 Referenced faults.17
8.1.2 Operation: getStreamingRequests.17
8.1.2.1 Input message: getStreamingRequestsRequest .17
8.1.2.2 Output message: getStreamingRequestsResponse.17
8.1.2.3 Referenced faults.17
8.1.3 Operation: controlMediaStream.18
8.1.3.1 Input message: controlMediaStreamRequest.18
8.1.3.2 Output message: controlMediaStreamResponse .18
8.1.3.3 Referenced faults.18
8.1.4 Operation: getMediaStreamStatus.18
8.1.4.1 Input message: getMediaStreamStatusRequest.18
8.1.4.2 Output message: getMediaStreamStatusResponse.18
8.1.4.3 Referenced faults.18
8.1.5 Operation: refundEndUserCharges.19
8.1.5.1 Input message: refundEndUserChargesRequest.19
8.1.5.2 Output message: refundEndUserChargesResponse.19
8.1.5.3 Referenced faults.19
8.2 Interface: StreamingNotificationManager.19
8.2.1 Operation: startNotification.19
8.2.1.1 Input message: startNotificationRequest.20
8.2.1.2 Output message: startNotificationResponse.20
8.2.1.3 Referenced faults.20
8.2.2 Operation: endNotification.20
ETSI
---------------------- Page: 3 ----------------------
4 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
8.2.2.1 Input message: endNotificationRequest.20
8.2.2.2 Output message: endNotificationResponse.20
8.2.2.3 Referenced faults.21
8.3 Interface: StreamingNotification.21
8.3.1 Operation: notifyMediaStreamRequest.21
8.3.1.1 Input message: notifyMediaStreamRequestRequest .21
8.3.1.2 Output message: notifyMediaStreamRequestResponse.21
8.3.1.3 Referenced faults.21
8.3.2 Operation: notifyMediaStreamStatus.21
8.3.2.1 Input message: notifyMediaStreamStatusRequest .21
8.3.2.2 Output message: notifyMediaStreamStatusResponse.21
8.3.2.3 Referenced faults.22
8.3.3 Operation: notifyError.22
8.3.3.1 Input message: notifyErrorRequest.22
8.3.3.2 Output message: notifyErrorResponse.22
8.3.3.3 Referenced faults.22
8.3.4 Operation: notifyEnd.22
8.3.4.1 Input message: notifyEndRequest.22
8.3.4.2 Output message: notifyEndResponse.22
8.3.4.3 Referenced faults.22
9 Fault definitions.23
9.1 ServiceException.23
9.1.1 SVC0270: Charge failed.23
10 Service policies .23
Annex A (normative): WSDL for Multimedia Streaming Control.24
Annex B (informative): Bibliography.25
History .26
ETSI
---------------------- Page: 4 ----------------------
5 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN), and is now submitted for the ETSI standards
Membership Approval Procedure.
The present document is part 19 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web
Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence";
Part 15: "Message Broadcast";
Part 16: "Geocoding";
Part 17: "Application-driven Quality of Service (QoS)";
Part 18: "Device Capabilities and Configuration";
Part 19: "Multimedia Streaming Control";
Part 20: "Multimedia Multicast Session Management".
ETSI
---------------------- Page: 5 ----------------------
6 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 3.0 set of specifications.
The present document is equivalent to 3GPP TS 29.199-19 V7.0.2 (Release 7).
ETSI
---------------------- Page: 6 ----------------------
7 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
1 Scope
The present document is part 19 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Multimedia Streaming Control Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
---------------------- Page: 7 ----------------------
8 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
[2] ETSI ES 202 504-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 3)".
[3] ETSI ES 202 504-6: "Open Service Access (OSA); Parlay X Web Services; Part 6: Payment
(Parlay X 3)".
[4] ETSI ES 204 915-7: "Open Service Access (OSA); Application Programming Interface (API);
Part 7: Terminal Capabilities SCF (Parlay 6)".
[5] ISO 4217: "Codes for the representation of currencies and funds".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 504-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ES 202 504-1 [2] apply.
4 Detailed service description
The service provided to an end-user is consumption of streaming multimedia. The end-user has a terminal that is able to
request a media stream, either from a built-in player, or an installed application. The terminal can be any terminal with
streaming media playing capabilities, and the service should allow a user to transfer between his terminals.
• The basic scenario is where an individual is browsing the Internet and finds some interesting content that
he/she wants to watch. The end-user is then either doing this through the operator’s portal or accesses the
content provider’s site. In the first case, the request is then processed through the portal, and charged as the
stream is set-up. In the second case, the content provider redirects the request to the operator, so that the
terminal capabilities can be collected and charging is done, before the stream is started.
• One scenario is an individual watching his favourite sports stream on his TV or PC at home, but he/she must
leave the house of some reason, and still wants to continue the session on his mobile terminal. In that case
he/she would transfer the ongoing session to the other terminal with other capabilities, since he already paid
for the entire episode.
• The other way is a similar case where an individual arrives at a destination with better viewing capabilities.
4.1 Overview
The figure below shows streaming content delivered to mobile terminals, but is not restricted to any particular terminal
type. The content is either on a location accessible over the Internet or stored locally on an operator's domain or the
content provider's domain. The access to the content is done through a smart router controlling the stream towards the
terminal. Transcoding of a stream is an optional feature that could allow users to switch between different terminal and
networks, while consuming content from a streaming source.
ETSI
---------------------- Page: 8 ----------------------
9 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
Figure 4.1.1
5 Namespaces
The Streaming interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/streaming/ v3_0
The StreamingNotificationManager interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/ streaming /notification_manager/v3_0
The StreamingNotification interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/ streaming /notification/v3_0
The data types are defined in the namespace:
http://www.csapi.org/schema/parlayx/ streaming /v3_0
The 'xsd' namespace is used in the present document to refer to the XML Schema data types defined in
XML Schema [1]. The use of the name 'xsd' is not semantically significant.
6 Sequence diagrams
The following use case diagram defines the core functionality which should be supported by the Multimedia Streaming
Control web service. These high level logical use cases will be supported by the defined API, but not necessarily on a
one to one mapping basis.
ETSI
---------------------- Page: 9 ----------------------
10 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
Figure 6.1
6.1 Getting requests
The following diagram illustrates the scenario where incoming stream requests are buffered at the operator. The content
provider periodically retrieves streaming requests and handles them.
ETSI
---------------------- Page: 10 ----------------------
11 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
: End-User
: Content : Router
: Multimedia
Provider
StreamingControl
Request content (SETUP)
getStreamingRequests
Start the stream
including charging
info and
startMediaStream
transcoding
Content description
PLAY
Stream started
notifyMediaStreamStatus
Stream completed
End stream
notifyMediaStreamStatus
6.2 Charging refund
The following diagram illustrates the scenario where incoming stream requests are sent to the content provider when
received by the operator. In this scenario the stream is cancelled before playing is completed and the content provider
refunds an amount previously requested.
: End-User
: Content : Router
: Multimedia
Provider
StreamingControl
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and
startMediaStream
transcoding
Content description
Stream started PLAY
notifyMediaStreamStatus
Stream cancelled TEARDOWN
or interrupted
notifyMediaStreamStatus
Stream interrupted
so refund charging
refundEndUserCharges
ETSI
---------------------- Page: 11 ----------------------
12 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
6.3 Trans-coding update
The following diagram illustrates the scenario where the capabilities for a terminal or a network changes, for example
due to handover between GPRS and 3G. The contents provider is notified about this change and can change for
example transcoding of the stream.
: Multimedia
: Content : Router : End-User
StreamingControl
Provider
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and trans-
startMediaStream
coding
Content description
Stream started PLAY
notifyMediaStreamStatus
Capabilities
changed
notifyMediaStreamStatus
Stream
capabilities
changed, send
Send new
startMediaStream
new trans-coding
trans-coding
6.4 Controlling multiple streams
The following diagram illustrates the scenario where the content provider pauses an ongoing stream and temporarily
plays another stream, for example an advertisement. When the second stream ends the first original stream is continued.
From the end-user’s point of view this should be perceived as one uninterrupted stream.
ETSI
---------------------- Page: 12 ----------------------
13 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
: Multimedia
: Content : Router : End-User
Provider StreamingControl
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and
startMediaStream
transcoding
Content description
Stream 1 started PLAY
Content provider
notifyMediaStreamStatus
pauses stream
and plays an other
controlMediaStream
stream
Pause stream 1
Stream 2 started
Stream 2 finished
notifyMediaStreamStatus
Second stream
finished, resume
controlMediaStream
Resume stream 1
the first stream
Stream 1 resumed
Stream 1 finished
notifyMediaStreamStatus
End stream
6.5 Redirecting a stream
The following diagram illustrates the scenario where a stream is being redirected to another device due to a user
request. The contents provider receives the request from the end-user and continues the stream to the new device.
ETSI
---------------------- Page: 13 ----------------------
14 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
: Multimedia : End-User
: Content : Router
StreamingControl
Provider
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and trans-
startMediaStream
coding
Content description
Stream started PLAY
notifyMediaStreamStatus
PAUSE
Stream paused
notifyMediaStreamStatus
Stream
capabilities
Request content (New device)
notifyMediaStreamRequest
changed, send
new trans-coding
startMediaStream
Content description
Stream started PLAY
notifyMediaStreamStatus
6.6 Multimedia Stream Control with Dynamic QoS
The following sequence diagram provides an example of how an application could combine functionality from the
Multimedia Streaming Control web service (this specification) with the Application Driven QoS (ADQ) web service to
provide guaranteed media stream delivery.
Flow summary:
1. Content Provider receives a NotifyMediaStreamRequest which includes the content identifier, terminal
capabilities and an estimated available bandwidth of the current network session.
2. Based upon content requirements and current network bandwidth, the content provider may decide to provide
a guaranteed QoS for content delivery by applying a temporary QoS session (addTemporaryQoSFeature on
ADQ Web Service).
3. The content provider will then continue to setup the media stream through the StartMediaStream operation, as
for previous scenarios.
4. At some point during the ongoing stream, the network / terminal capabilities change and the content provider
is notified by the operator with the NotifySessionStatus operation.
5. Based on the new session parameters (e.g. available bandwidth), the content provider may modify the
guaranteed QoS parameters previously requested (modifyTemporaryQoSFeature).
6. Upon stream completion, content provider will remove the previously requested QoS session
(removeTemporaryQosFeature).
ETSI
---------------------- Page: 14 ----------------------
15 Final draft ETSI ES 202 504-19 V1.1.1 (2008-02)
: ADQ Web
: Content : Router : End-User
: Multimedia
Service
Provider
StreamingControl
startStreamingNotification
Request content (SETUP)
on
notifyMediaStreamRequest
addTemporaryQoSFeature
startMediaStream
Content description
Stream started PLAY
notifyMediaStreamStatus
Stream
capabilities
changed
notifyMediaStreamStatus
modifyTemporaryQoSFeature
Stream
TEARDOWN
cancelled
notifyMediaStreamStatus
removeTemporaryQoSFeature
7 XML Schema data type definition
7.1 MediaStreamRequest structure
Data type used to capture attributes of a single media stream request.
Element Name Element Type Optional Description
subscriberIdentifier xsd:anyURI No Identity of subscriber / end-user making the
request for content streaming
contentIdentifier xsd:anyURI No Identifier / Address of requested content item
sessionIdentifier xsd:string No Operator provided session identifier
streamTransfer xsd:boolean Yes States whether this request is a result of a
stream transfer (e.g. transfer of existing
stream from mobile device to a PC) or is a
new media stream request.
terminalCapabilities xsd:string [0.unbounded] Yes Terminal capability description derived from
TpTerminalCapabilities (ref ES 204 915-7 [4])
availableBandwidth xsd:int Yes Estimation of current available network
bandwidth in bits per second
7.2 Med
...
SLOVENSKI STANDARD
SIST ES 202 504-19 V1.1.1:2008
01-september-2008
2GSUWLGRVWRSGRVWRULWYH 26$ 6SOHWQHVWRULWYH3DUOD\; GHO .UPLOMHQMH
YHþSUHGVWDYQRVWQHJDVWUXMDQMD 3DUOD\;
Open Service Access (OSA) - Parlay X Web Services - Part 19: Multimedia Streaming
Control (Parlay X 3)
Ta slovenski standard je istoveten z: ES 202 504-19 Version 1.1.1
ICS:
35.100.01 Medsebojno povezovanje Open systems
odprtih sistemov na splošno interconnection in general
SIST ES 202 504-19 V1.1.1:2008 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ES 202 504-19 V1.1.1:2008
---------------------- Page: 2 ----------------------
SIST ES 202 504-19 V1.1.1:2008
ETSI ES 202 504-19 V1.1.1 (2008-05)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 19: Multimedia Streaming Control
(Parlay X 3)
�
---------------------- Page: 3 ----------------------
SIST ES 202 504-19 V1.1.1:2008
2 ETSI ES 202 504-19 V1.1.1 (2008-05)
Reference
DES/TISPAN-01034-19-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
---------------------- Page: 4 ----------------------
SIST ES 202 504-19 V1.1.1:2008
3 ETSI ES 202 504-19 V1.1.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
4.1 Overview.8
5 Namespaces.9
6 Sequence diagrams.9
6.1 Getting requests.10
6.2 Charging refund.11
6.3 Trans-coding update.12
6.4 Controlling multiple streams .12
6.5 Redirecting a stream.13
6.6 Multimedia Stream Control with Dynamic QoS .14
7 XML Schema data type definition .15
7.1 MediaStreamRequest structure.15
7.2 MediaStreamInformation structure.15
7.3 StreamControlAction enumeration.16
7.4 MediaStreamStatus enumeration.16
8 Web Service interface definition.16
8.1 Interface: Streaming.16
8.1.1 Operation: startMediaStream.16
8.1.1.1 Input message: startMediaStreamRequest.16
8.1.1.2 Output message: startMediaStreamResponse.17
8.1.1.3 Referenced faults.17
8.1.2 Operation: getStreamingRequests.17
8.1.2.1 Input message: getStreamingRequestsRequest .17
8.1.2.2 Output message: getStreamingRequestsResponse.17
8.1.2.3 Referenced faults.17
8.1.3 Operation: controlMediaStream.18
8.1.3.1 Input message: controlMediaStreamRequest.18
8.1.3.2 Output message: controlMediaStreamResponse .18
8.1.3.3 Referenced faults.18
8.1.4 Operation: getMediaStreamStatus.18
8.1.4.1 Input message: getMediaStreamStatusRequest.18
8.1.4.2 Output message: getMediaStreamStatusResponse.18
8.1.4.3 Referenced faults.18
8.1.5 Operation: refundEndUserCharges.19
8.1.5.1 Input message: refundEndUserChargesRequest.19
8.1.5.2 Output message: refundEndUserChargesResponse.19
8.1.5.3 Referenced faults.19
8.2 Interface: StreamingNotificationManager.19
8.2.1 Operation: startNotification.19
8.2.1.1 Input message: startNotificationRequest.20
8.2.1.2 Output message: startNotificationResponse.20
8.2.1.3 Referenced faults.20
8.2.2 Operation: endNotification.20
ETSI
---------------------- Page: 5 ----------------------
SIST ES 202 504-19 V1.1.1:2008
4 ETSI ES 202 504-19 V1.1.1 (2008-05)
8.2.2.1 Input message: endNotificationRequest.20
8.2.2.2 Output message: endNotificationResponse.20
8.2.2.3 Referenced faults.21
8.3 Interface: StreamingNotification.21
8.3.1 Operation: notifyMediaStreamRequest.21
8.3.1.1 Input message: notifyMediaStreamRequestRequest .21
8.3.1.2 Output message: notifyMediaStreamRequestResponse.21
8.3.1.3 Referenced faults.21
8.3.2 Operation: notifyMediaStreamStatus.21
8.3.2.1 Input message: notifyMediaStreamStatusRequest .21
8.3.2.2 Output message: notifyMediaStreamStatusResponse.21
8.3.2.3 Referenced faults.22
8.3.3 Operation: notifyError.22
8.3.3.1 Input message: notifyErrorRequest.22
8.3.3.2 Output message: notifyErrorResponse.22
8.3.3.3 Referenced faults.22
8.3.4 Operation: notifyEnd.22
8.3.4.1 Input message: notifyEndRequest.22
8.3.4.2 Output message: notifyEndResponse.22
8.3.4.3 Referenced faults.22
9 Fault definitions.23
9.1 ServiceException.23
9.1.1 SVC0270: Charge failed.23
10 Service policies .23
Annex A (normative): WSDL for Multimedia Streaming Control.24
Annex B (informative): Bibliography.25
History .26
ETSI
---------------------- Page: 6 ----------------------
SIST ES 202 504-19 V1.1.1:2008
5 ETSI ES 202 504-19 V1.1.1 (2008-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 19 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web
Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence";
Part 15: "Message Broadcast";
Part 16: "Geocoding";
Part 17: "Application-driven Quality of Service (QoS)";
Part 18: "Device Capabilities and Configuration";
Part 19: "Multimedia Streaming Control";
Part 20: "Multimedia Multicast Session Management".
ETSI
---------------------- Page: 7 ----------------------
SIST ES 202 504-19 V1.1.1:2008
6 ETSI ES 202 504-19 V1.1.1 (2008-05)
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 3.0 set of specifications.
The present document is equivalent to 3GPP TS 29.199-19 V7.0.2 (Release 7).
ETSI
---------------------- Page: 8 ----------------------
SIST ES 202 504-19 V1.1.1:2008
7 ETSI ES 202 504-19 V1.1.1 (2008-05)
1 Scope
The present document is part 19 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Multimedia Streaming Control Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
---------------------- Page: 9 ----------------------
SIST ES 202 504-19 V1.1.1:2008
8 ETSI ES 202 504-19 V1.1.1 (2008-05)
[2] ETSI ES 202 504-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 3)".
[3] ETSI ES 202 504-6: "Open Service Access (OSA); Parlay X Web Services; Part 6: Payment
(Parlay X 3)".
[4] ETSI ES 204 915-7: "Open Service Access (OSA); Application Programming Interface (API);
Part 7: Terminal Capabilities SCF (Parlay 6)".
[5] ISO 4217: "Codes for the representation of currencies and funds".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 504-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ES 202 504-1 [2] apply.
4 Detailed service description
The service provided to an end-user is consumption of streaming multimedia. The end-user has a terminal that is able to
request a media stream, either from a built-in player, or an installed application. The terminal can be any terminal with
streaming media playing capabilities, and the service should allow a user to transfer between his terminals.
• The basic scenario is where an individual is browsing the Internet and finds some interesting content that
he/she wants to watch. The end-user is then either doing this through the operator’s portal or accesses the
content provider’s site. In the first case, the request is then processed through the portal, and charged as the
stream is set-up. In the second case, the content provider redirects the request to the operator, so that the
terminal capabilities can be collected and charging is done, before the stream is started.
• One scenario is an individual watching his favourite sports stream on his TV or PC at home, but he/she must
leave the house of some reason, and still wants to continue the session on his mobile terminal. In that case
he/she would transfer the ongoing session to the other terminal with other capabilities, since he already paid
for the entire episode.
• The other way is a similar case where an individual arrives at a destination with better viewing capabilities.
4.1 Overview
The figure below shows streaming content delivered to mobile terminals, but is not restricted to any particular terminal
type. The content is either on a location accessible over the Internet or stored locally on an operator's domain or the
content provider's domain. The access to the content is done through a smart router controlling the stream towards the
terminal. Transcoding of a stream is an optional feature that could allow users to switch between different terminal and
networks, while consuming content from a streaming source.
ETSI
---------------------- Page: 10 ----------------------
SIST ES 202 504-19 V1.1.1:2008
9 ETSI ES 202 504-19 V1.1.1 (2008-05)
Figure 4.1.1
5 Namespaces
The Streaming interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/streaming/ v3_0
The StreamingNotificationManager interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/ streaming /notification_manager/v3_0
The StreamingNotification interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/ streaming /notification/v3_0
The data types are defined in the namespace:
http://www.csapi.org/schema/parlayx/ streaming /v3_0
The 'xsd' namespace is used in the present document to refer to the XML Schema data types defined in
XML Schema [1]. The use of the name 'xsd' is not semantically significant.
6 Sequence diagrams
The following use case diagram defines the core functionality which should be supported by the Multimedia Streaming
Control web service. These high level logical use cases will be supported by the defined API, but not necessarily on a
one to one mapping basis.
ETSI
---------------------- Page: 11 ----------------------
SIST ES 202 504-19 V1.1.1:2008
10 ETSI ES 202 504-19 V1.1.1 (2008-05)
Figure 6.1
6.1 Getting requests
The following diagram illustrates the scenario where incoming stream requests are buffered at the operator. The content
provider periodically retrieves streaming requests and handles them.
ETSI
---------------------- Page: 12 ----------------------
SIST ES 202 504-19 V1.1.1:2008
11 ETSI ES 202 504-19 V1.1.1 (2008-05)
: End-User
: Content : Router
: Multimedia
Provider
StreamingControl
Request content (SETUP)
getStreamingRequests
Start the stream
including charging
info and
startMediaStream
transcoding
Content description
PLAY
Stream started
notifyMediaStreamStatus
Stream completed
End stream
notifyMediaStreamStatus
6.2 Charging refund
The following diagram illustrates the scenario where incoming stream requests are sent to the content provider when
received by the operator. In this scenario the stream is cancelled before playing is completed and the content provider
refunds an amount previously requested.
: End-User
: Content : Router
: Multimedia
Provider
StreamingControl
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and
startMediaStream
transcoding
Content description
Stream started PLAY
notifyMediaStreamStatus
Stream cancelled TEARDOWN
or interrupted
notifyMediaStreamStatus
Stream interrupted
so refund charging
refundEndUserCharges
ETSI
---------------------- Page: 13 ----------------------
SIST ES 202 504-19 V1.1.1:2008
12 ETSI ES 202 504-19 V1.1.1 (2008-05)
6.3 Trans-coding update
The following diagram illustrates the scenario where the capabilities for a terminal or a network changes, for example
due to handover between GPRS and 3G. The contents provider is notified about this change and can change for
example transcoding of the stream.
: Multimedia
: Content : Router : End-User
StreamingControl
Provider
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and trans-
startMediaStream
coding
Content description
Stream started PLAY
notifyMediaStreamStatus
Capabilities
changed
notifyMediaStreamStatus
Stream
capabilities
changed, send
Send new
startMediaStream
new trans-coding
trans-coding
6.4 Controlling multiple streams
The following diagram illustrates the scenario where the content provider pauses an ongoing stream and temporarily
plays another stream, for example an advertisement. When the second stream ends the first original stream is continued.
From the end-user’s point of view this should be perceived as one uninterrupted stream.
ETSI
---------------------- Page: 14 ----------------------
SIST ES 202 504-19 V1.1.1:2008
13 ETSI ES 202 504-19 V1.1.1 (2008-05)
: Multimedia
: Content : Router : End-User
Provider StreamingControl
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and
startMediaStream
transcoding
Content description
Stream 1 started PLAY
Content provider
notifyMediaStreamStatus
pauses stream
and plays an other
controlMediaStream
stream
Pause stream 1
Stream 2 started
Stream 2 finished
notifyMediaStreamStatus
Second stream
finished, resume
controlMediaStream
Resume stream 1
the first stream
Stream 1 resumed
Stream 1 finished
notifyMediaStreamStatus
End stream
6.5 Redirecting a stream
The following diagram illustrates the scenario where a stream is being redirected to another device due to a user
request. The contents provider receives the request from the end-user and continues the stream to the new device.
ETSI
---------------------- Page: 15 ----------------------
SIST ES 202 504-19 V1.1.1:2008
14 ETSI ES 202 504-19 V1.1.1 (2008-05)
: Multimedia : End-User
: Content : Router
StreamingControl
Provider
startStreamingNotification
Request content (SETUP)
on
Start the stream
notifyMediaStreamRequest
including charging
info and trans-
startMediaStream
coding
Content description
Stream started PLAY
notifyMediaStreamStatus
PAUSE
Stream paused
notifyMediaStreamStatus
Stream
capabilities
Request content (New device)
notifyMediaStreamRequest
changed, send
new trans-coding
startMediaStream
Content description
Stream started PLAY
notifyMediaStreamStatus
6.6 Multimedia Stream Control with Dynamic QoS
The following sequence diagram provides an example of how an application could combine functionality from the
Multimedia Streaming Control web service (this specification) with the Application Driven QoS (ADQ) web service to
provide guaranteed media stream delivery.
Flow summary:
1. Content Provider receives a NotifyMediaStreamRequest which includes the content identifier, terminal
capabilities and an estimated available bandwidth of the current network session.
2. Based upon content requirements and current network bandwidth, the content provider may decide to provide
a guaranteed QoS for content delivery by applying a temporary QoS session (addTemporaryQoSFeature on
ADQ Web Service).
3. The content provider will then continue to setup the media stream through the StartMediaStream operation, as
for previous scenarios.
4. At some point during the ongoing stream, the network / terminal capabilities change and the content provider
is notified by the operator with the NotifySessionStatus operation.
5. Based on the new session parameters (e.g. available bandwidth), the content provider may modify the
guaranteed QoS parameters previously requested (modifyTemporaryQoSFeature).
6. Upon stream completion, content provider will remove the previously requested QoS session
(removeTemporaryQosFeature).
ETSI
---------------------- Page: 16 ----------------------
SIST ES 202 504-19 V1.1.1:2008
15 ETSI ES 202 504-19 V1.1.1 (2008-05)
: ADQ Web
: Content : Router : End-User
: Multimedia
Service
Provider
StreamingControl
startStreamingNotification
Request content (SETUP)
on
notifyMediaStreamRequest
addTemporaryQoSFeature
startMediaStream
Content description
Stream started PLAY
notifyMediaStreamStatus
Stream
capabilities
changed
not
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.