hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
6.4 Transport protocol
|
Diameter messages over the a4 interface shall make use of SCTP RFC 2960 [6] and shall utilize the new SCTP checksum method specified in RFC 3309 [7]. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 16
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
6.5 Routing considerations
|
This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. Requests initiated by the UAAF towards the CLF shall include both Destination-Host and Destination-Realm AVPs. The UAAF obtains the Destination-Host AVP to use in requests towards a CLF, from configuration data in UAAF or the NASS User profile from the PDBF. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the UAAF. Requests initiated by the CLF towards the UAAF shall include both Destination-Host and Destination-Realm AVPs. The CLF obtains the Destination-Host AVP to use in requests towards a UAAF, from the Origin-Host and Origin- Realm AVPs received in previous commands from the UAAF related to the same IP realm. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the CLF. Destination-Realm AVP is declared as mandatory in the ABNF for all requests.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
6.6 Advertising Application Support
|
The CLF and UAAF shall advertise support of the a4 specific application by including the value 16777257 of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The vendor identifier value of ETSI (13019) shall be included in the Supported-Vendor-Id AVP of the Capabilities- Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor- Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. Additionally, support of 3GPP AVPs shall be advertised by adding the vendor identifier value of 3GPP (10415) to the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. NOTE: The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above indicates the manufacturer of the Diameter node as per RFC 3588 [9].
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7 DIAMETER application
|
This clause specifies a Diameter application that allows a Diameter server and Diameter client exchange information related to NASS User network profile information. The Diameter application identifier assigned to this application is 16777257 (allocated by IANA). The Diameter Base Protocol as specified in RFC 3588 [9] is used to support information transfer on both interfaces. RFC 3588 [9] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 5. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) are unmodified.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.1 Commands
|
The present document re-uses and modifies commands defined in the TS 129 329 [3] for the Sh interface. Only the following commands defined in TS 129 329 [3] are used. Any other command defined in TS 129 329 [3] shall be ignored. Table 7.1: Command-code values Command-Name Abbreviation Code User-Data-Request UDR 306 User-Data-Answer UDA 306 Push-Notification-Request PNR 309 Push-Notification-Answer PNA 309 ETSI ETSI TS 183 066 V2.1.1 (2009-01) 17 AVPs defined in TS 129 329 [3] and not used in the present document are not shown in the below clauses. If received, these AVPs shall be ignored by the CLF and the A-RACF. New AVPs are represented in bold.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.1.1 User-Data-Request command
|
The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the "R" bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request user data. This command is defined in TS 129 329 [3] and used with additional AVPs defined in the present document. NOTE: In the context of the document the user whose data are requested using the UDR command is the NASS user. Message Format: < User-Data -Request > ::= < Diameter Header: 306, REQ, PXY, 16777257 > < Session-Id > { Vendor-Specific-Application-Id } { Auth-Session-State } { Origin-Host } { Origin-Realm } [ Destination-Host ] { Destination-Realm } [Globally-Unique-Address] [Logical-Access-Id] [User-Name] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ]
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.1.2 User-Data-Answer command
|
The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the "R" bit cleared in the Command Flags field, is sent by a server in response to the User-Data-Request command. This command is defined in TS 129 329 [3] and used with additional AVPs defined in the present document. The Experimental-Result AVP may contain one of the values defined in clause 7.2 or in TS 129 229 [2]. Message Format: < User-Data-Answer > ::= < Diameter Header: 306, PXY, 16777257 > < Session-Id > { Vendor-Specific-Application-Id } [ Result-Code ] [ Experimental-Result ] { Auth-Session-State } { Origin-Host } { Origin-Realm } [Globally-Unique-Address] [User-Name] [Logical-Access-Id] [Physical-Access-Id] [CNGCF-Address] [SIP-Outbound-Proxy] [Initial-Gate-Setting-Description] *[QoS-Profile-Description] [QoS-Profile-ID] [Initial-Gate-Setting-ID] *[Privacy-Indicator] *[ AVP ] *[ Failed-AVP ] *[ Proxy-Info ] *[ Route-Record ]
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.1.3 Push-Notification-Request command
|
The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the "R" bit set in the Command Flags field, is sent by a Diameter server to a Diameter client in order to notify changes in the user data in the server. This command is defined in TS 129 329 [3] and used with additional AVPs defined in the present document. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 18 Message Format: < Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777257 > < Session-Id > { Vendor-Specific-Application-Id } { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Host } { Destination-Realm } [Globally-Unique-Address] [User-Name] [Logical-Access-Id] [Physical-Access-Id] [CNGCF-Address] [SIP-Outbound-Proxy] [Initial-Gate-Setting-Description] *[QoS-Profile-Description] [QoS-Profile-ID] [Initial-Gate-Setting-ID] *[Privacy-Indicator] [Data-Operation-Indicator] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ]
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.1.4 Push-Notification-Answer command
|
The Push-Notifications-Answer (PNA) command, indicated by the Command-Code field set to 309 and the "R" bit cleared in the Command Flags field, is sent by a client in response to the Push-Notification-Request command. This command is defined in TS 129 329 [3]. The Experimental-Result AVP may contain one of the values defined in clause 7.2 or in TS 129 229 [2]. Message Format: < Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777257 > < Session-Id > { Vendor-Specific-Application-Id } [ Result-Code ] [ Experimental-Result ] { Auth-Session-State } { Origin-Host } { Origin-Realm } *[ AVP ] *[ Failed-AVP ] *[ Proxy-Info ] *[ Route-Record ]
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.2 Result-Code AVP values
|
This clause defines new result code values that must be supported by all Diameter implementations that conform to the present document. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.2.1 Success
|
Result codes that fall within the Success category are used to inform a peer that a request has been successfully completed. No result codes within this category have been defined so far.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.2.2 Permanent failures
|
Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 19 No errors within this category have been defined so far. However the following error defined in TS 129 229 [2] is used in the present document: • DIAMETER_ERROR_USER_UNKNOWN (5001). When this result code is used, the 3GPP Vendor ID shall be included in the Vendor-Id AVP of the Experimental-Result AVP.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.2.3 Transient failures
|
Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. No errors within this category have been defined so far. However the following error defined in TS 129 329 [3] is used in the present document: • DIAMETER_USER_DATA_NOT_AVAILABLE (4100).
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.3 AVPs
|
The following tables summarize the AVP used in the present document, beyond those defined in the Diameter Base Protocol. Table 7.2 describes the Diameter AVPs defined in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. The Vendor-Id header of all AVPs defined in the present document shall be set to ETSI (13019). Table 7.2: Diameter AVPs defined in the present document AVP Flag rules Attribute Name AVP Code Clause d efined Value Type Must May Should not Must not May Encrypt Data-Operation-Indicator 420 7.3.1 Enumerated V M Yes NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. Table 7.3 describes the Diameter AVPs defined for the e4 application (ES 283 034 [4]) and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in ES 283 034 [4] but not listed in the following table should not be sent by Diameter conforming to the present document and shall be ignored by receiving entities. The Vendor-Id header for these AVPs shall be set to ETSI (13019). Table 7.3: Diameter AVPs imported from the ES 283 034 [4] (e4 specification) AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt Globally-Unique-Address 300 See ES 283 034 [4] Grouped M,V Yes Logical-Access-Id 302 See ES 283 034 [4] OctetString V M Yes Initial-Gate-Setting-Description 303 See ES 283 034 [4] Grouped V M Yes QoS-Profile-Description 304 See ES 283 034 [4] Grouped V M Yes Physical-Access-ID 313 See ES 283 034 [4] UTF8String V M Yes Initial-Gate-Setting-ID 314 See ES 283 034 [4] Unsigned32 V M Yes QoS-Profile-ID 315 See ES 283 034 [4] Unsigned32 V M Yes NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 20 Table 7.4 describes the Diameter AVPs defined in TS 183 020 [5] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in TS 183 020 [5] but not listed in the following table should not be sent by Diameter conforming to the present document and shall be ignored by receiving entities. The Vendor-Id header for these AVPs shall be set to ETSI (13019). Table 7.4: Diameter AVPs imported from the TS 183 020 [5] AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt Privacy-Indicator 440 See TS 183 020 [5] Grouped V M Yes NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. Table 7.5 describes the Diameter AVPs defined in TS 183 059-1 [10] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in TS 183 059-1 [10] but not listed in the following table should not be sent by Diameter conforming to the present document and shall be ignored by receiving entities. The Vendor-Id header for these AVPs shall be set to ETSI (13019). Table 7.5: Diameter AVPs imported from the TS 183 059-1 [10] AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt SIP-Outbound-Proxy 601 See TS 183 059-1 [10] OctetString V M Yes CNGCF-Address 600 See TS 183 059-1 [10] Grouped V M Yes NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.3.1 Data-Operation-Indicator
|
The Data-Operation-Indicator AVP (AVP code 420 13019) is of type Enumerated and represents the type of data operation the receiver shall perform after receiving this AVP. When the Data-Operation-Indicator AVP is omitted, the receiver shall perform the update operation by default. The following values are defined: • UPDATE (0). • REMOVE (1).
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.4 Use of namespaces
|
This clause contains the namespaces that have either been created in the present document, or the values assigned to existing namespaces managed by IANA.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.4.1 AVP codes
|
The present document assigns the AVP values in the 420 to 439 range from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. See clause 7.3 for the assigned values.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.4.2 Experimental-Result-Code AVP values
|
The present document does not assign any Experimental-Result-Code AVP value. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 21
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.4.3 Command Code values
|
The present document does not assign command code values but uses existing command codes assigned to 3GPP.
|
8417e56860be9e8305a0eeb862fa5f87
|
183 066
|
7.4.4 Application-ID value
|
The present document uses value 16777257, allocated by IANA, as application identifier. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 22 Annex A (informative): Mapping of a4 operations and terminology to Diameter Table A.1 defines the mapping between the information flows defined in ES 282 004 [1] and Diameter commands. Table A.1: a4 message to Diameter command mapping a4 message Source Destination Command-Name Abbreviation Access Profile Pull CLF UAAF User-Data-Request UDR Access Profile Pull Response UAAF CLF User-Data-Answer UDA Access Profile Push UAAF CLF Push-Notification-Request PNR Access Profile Push Response CLF UAAF Push-Notification-Answer PNA Remove Access Profile Indication UAAF CLF Push-Notification-Request PNR Remove Access Profile Response CLF UAAF Push-Notification-Answer PNA ETSI ETSI TS 183 066 V2.1.1 (2009-01) 23 History Document history V2.1.1 January 2009 Publication
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
1 Scope
|
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 007-2 [2]. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 610: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 version 8.3.0 Release 8)". [2] ETSI TS 186 007-2 (V3.1.1): "Technical Committee for IMS Network Testing (INT); Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Testing; Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [3] ETSI TS 102 790-3: "Technical Committee for IMS Network Testing (INT); Network Integration Testing; IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification". [4] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 6 [5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [6] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [7] ETSI ES 201 873-1 (V4.3.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [8] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [9] ETSI TS 102 587-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to- Peer Digital Private Mobile Radio; Part 2: Conformance testing; Test Suite Structure and Test Purposes (TSS&TP) specification". [10] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication".
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
3 Definitions and abbreviations
| |
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [6], TS 102 587-2 [9] and TS 102 790-3 [3] apply.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-7 [6], TS 102 790-3 [3] and TS 124 610 [1] apply.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
4 Abstract Test Method (ATM)
|
For the purposes of the present document, the ATM described in clause 4 of TS 102 790-3 [3] applies with following additions.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
4.1 Configurations for testing UE
|
The Gm interface is located between SUT (UE) and the IMS. SUT TS UE IMS Gm Figure 1: Test configuration CF_1GmUE ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 7 The ISC interface provides an access to the AP. SUT IMS AS ISC TS Figure 2: Test configuration CF_1ISC
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5 The ATS development process
| |
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 5 of TS 186 007-2 [2]. The requirements applicable to this TP are given by a reference to TS 124 610 [1]. There are no explicit formulations of requirements.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5.2 ATS structure
| |
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5.2.1 Test case grouping
|
The ATS structure defined in Table 1 is based on the structuring of Test Purposes in clause 4 of TS 186 007-2 [2]. The group names in column 2 of Table 1 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 007-2 [2], but use the naming conventions defined for the ATS (see clause 5.2.2). Table 1: HOLD ATS structure ServedUser WithUPDATE CH_U01_xxx WithoutUPDATE CH_U02_xxx
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in Table 1 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit decimal number, starting in each subgroup path with "001". EXAMPLE: TC_CH_U01_001: i) the identifier has Group index "CH_U01", i.e. it is in the subgroup having complete path: SupplementaryServices_CH/ServedUser/WithUPDATE; ii) the identifier is the first test case of this group/subgroup. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 8 NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 007-2 [2] and test case names. The TP identifier of TC_CH_U01_001 is TP CH_U01_001.
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5.3 ATS specification framework
| |
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5.3.1 ATS Library
|
For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules. 2) LibIms modules. 3) LibSip modules (RFC 3261 [4]). 4) LibCommon modules (taken from an improved version of TS 102 351 [8]). NOTE: Due to the common LibSip and LibIms library approach with some other parallel running projects there is necessary to create tag version of all library modules. Table 2 shows the organization of the ATS as library of modules. Table 2: Library of modules Module Class Module Id Description CH CH_TC_Functions CH test case functions CH_TestCases CH test case definitions AtsCommon SS_Ims_PICS Module Parameter declarations associated with PICS SS_Ims_PIXITS SIP common Module Parameter declarations associated with PIXIT SS_Ims_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations SS_Ims_TestSystem TSI components, test system internal ports SS_Ims_TestCases Test case definitions SS_Ims_Functions Test case functions LibIms LibIms_PIXITS IMS specific common Module Parameter (e.g. addresses related to SUT components and TS) declarations associated with PIXIT LibIms_Interface IMS component LibIms_SIPTypesAndValues IMS specific user and interface specific profile data (see note) LibIms_Templates Modified templates with IMS specific header fields LibIms_Steps functions using IMS specific types LibSip LibSip_PIXITS SIP general common Module Parameter (e.g. SDP/SIP procedure options) declarations associated with PIXIT LibSip_Interface SIP component LibSip_SIPTypesAndValues SIP message types and constants, simple user profiles (see note) LibSip_SDPTypes SDP types and constants LibSip_Templates Basic and modified templates with SIP specific header fields LibSip_Steps SIP specific behaviour function library LibSip_XMLTypes XML types for SIP tests XSDAUX Basic types used in XML LibCommon LibCommon_AbstractData Generic data types for a stack and its operations LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean) LibCommon_DataStrings Bit and Octet string types LibCommon_Sync Co-ordination/synchronization of test components LibCommon_TextStrings Basic character and string types with fixed length LibCommon_Time Time handling functions and module parameter LibCommon_VerdictControl Basic functions for setting of test component verdicts NOTE: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 9
|
cde0dbe1a14aa46ac50042d67991544b
|
186 007-3
|
5.3.2 Use of TTCN-3
|
For the purposes of the present document, the description of the use of TTCN-3 described in clause 5.3.2 of TS 102 790-3 [3] applies. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 10 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the type of ATS defined in the present document, the PIXIT are divided in PIXIT items for UE testing and for general PIXIT items that apply for all types of IUT. Each PIXIT item corresponds to a Module Parameter of the ATS. NOTE: The PIXIT definitions are part of a SIP TTCN-3 library that contains additional PIXIT definitions that are not used in this ATS and are therefore not presented in the following tables. A.2.1 PIXIT for UE Testing Table A.1: PIXIT items for UE testing Id Identifier Type / Description 1 PX_IMS_TS_PCSCF_IPADDR charstring, for TS/P-CSCF IP address to exchange SIP messages. 2 PX_IMS_TS_PCSCF_PORT integer, for IUT/P-CSCF port number to exchange SIP messages. 3 PX_IMS_TS_UE1_IPADDR charstring, for IP address used by the UE1 to exchange SIP messages. 4 PX_IMS_TS_UE1_PORT integer, for port number used by the UE1 to exchange SIP messages. 5 PX_IMS_SUT_UE1_BEARER_IPADDR charstring, for IP address used by the TS to exchange media streams for UE1. 6 PX_IMS_SUT_UE1_HOME_DOMAIN charstring, for identity of the tester UE1 local domain. 7 PX_IMS_SUT_UE1_PUBLIC_USER charstring, for identity of the tester UE1 local user. 8 PX_IMS_SUT_UE1_PRIVAT_USERNAME charstring, for RFC 2617 [10], clause 3.2.2 username of UE1: The name of user in the specified realm. 9 PX_IMS_SUT_UE1_PRIVAT_PASSWD charstring, for RFC 2617 [10], clause 3.2.2.2 passwd of UE1: A known shared secret, the password of user of the specified username. 10 PX_IMS_SUT_UE1_QOP charstring, for RFC 2617 [10], clause 3.2.1 qop options of UE1: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection. 11 PX_IMS_SUT_UE1_REGISTRAR charstring, for home (SUT) REGISTRAR domain of UE1. 12 PX_UE_REGISTRATION boolean, En-/disable UE registration. 13 PX_UE_REG_EVENT_SUBSCRIPTION boolean, En-/disable UE reg event subscription. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 11 A.2.2 General PIXIT The following PIXIT items apply for all types of IUT. Table A.2: General PIXIT items (SDP and Synchronization) Id Identifier Type / Description 1 PX_SIP_SDP_dyn charstring, for SDP dynamic port. 2 PX_SIP_SDP_b_modifier charstring, for SDP bandwidth modifier. 3 PX_SIP_SDP_b_bandwidth integer, for SDP bandwidth value. 4 PX_SIP_SDP_encoding charstring, for SDP media attribute encoding supported by the IUT. 5 PX_TSYNC_TIME_LIMIT float, Default time limit for a sync client to reach a synchronization point. 6 PX_TSHUT_DOWN_TIME_LIMIT float, Default time limit for a sync client to finish its execution of the shutdown default. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 12 Annex B (informative): TTCN-3 library modules B.1 Electronic annex, zip file with TTCN-3 code The TTCN-3 library modules are contained in archive ts_18600703v030101p0.zip which accompanies the present document. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 13 Annex C (informative): Validation Report C.1 Test Suite Validation Level Level 3 validation (strong) was achieved. C.2 TTCN-3 Edition Release 4.3.1 of the TTCN-3 documents [7] were used. C.3 TTCN-3 Tool(s) The following TTCN-3 tools were used: • Elvior TestCast® • Ericsson® Titan • Testing Technologies TTWorkbench® C.3.1 TTCN-3 Tool Elvior TestCast® C.3.1.1 Identification of the TTCN-3 Tool Elvior TestCast® Elvior TestCast® T3 Version 6.4.3, no plugins necessary. C.3.1.2 Compilation status Full compilation, without any errors. C.3.2 TTCN-3 Tool Ericsson® Titan C.3.2.1 Identification of the TTCN-3 Tool Ericsson® Titan Ericsson® Titan as in file ttcn3-1.8.pl4-mingw, no plugins necessary. C.3.2.2 Compilation status Partial compilation, as xml data structure were not supported by this version. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 14 C.3.3 TTCN-3 Tool Testing Technologies TTWorkbench® C.3.3.1 Identification of the TTCN-3 Tool Testing Technologies TTWorkbench® Testing Technologies TTworkbench® Basic, Version: 13, Build id: 2011.10.17.13.21.07.953 with plugin TTplugin-XSD Version 1.1.4. C.3.3.2 Compilation status Full compilation, without any errors. C.3.4 Test Platform(s) The test cases were run on the execution environment of the Testing Technology TTworkbench® tool mentioned in clause C.3.3. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 15 History Document history V1.1.1 September 2008 Publication V3.1.1 January 2012 Publication
|
83397221380043918c10ad89da3c4c25
|
183 065
|
1 Scope
|
The present document provides the ETSI TISPAN endorsement of DSL Forum TR-069 "CPE WAN Management Protocol" (CWMP) in line with the requirements of TISPAN NGN for the specification of the e3 interface.
|
83397221380043918c10ad89da3c4c25
|
183 065
|
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.
|
83397221380043918c10ad89da3c4c25
|
183 065
|
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] DSL Forum Technical Report TR-069: "CPE WAN management Protocol". [2] DSL Forum Technical Report TR-098 Amendment 1: "Internet Gateway Device Data Model for TR-069", November 2006. [3] DSL Forum Technical Report TR-104: "Provisioning Parameters for VoIP CPE", September 2005. [4] DSL Forum Technical Report TR-106 Amendment 1: "Data Model Template for TR-069-Enabled Devices", November 2006. [5] DSL Forum Technical Report TR-135: "Data model for a TR-069 enabled STB", December 2007. ETSI ETSI TS 183 065 V2.0.0 (2008-02) 6
|
83397221380043918c10ad89da3c4c25
|
183 065
|
3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACS Auto-Configuration Server CND Customer Network Device CNG Customer Network Gateway CNGCF Customer Network Gateway Configuration Function CPN Customer Premises Network CPNCF Customer Premises Network Configuration Function CPE Customer Premises Equipment CWMP CPE WAN Management Protocol DHCP Dynamic Host Configuration Protocol IMS IP Multimedia Subsystem IPTV IP TeleVision LAN Local Area Network NAPT Network Address and Port Translation OAM Operation Administration Maintenance RMS Remote Management System STB Set Top Box STUN Simple Traversal of UDP through NAT VoIP Voice over IP WAN Wide Area Network Endorsement notice All elements of TR-069 [1] apply. ETSI ETSI TS 183 065 V2.0.0 (2008-02) 7 History Document history V1.1.1 February 2008 Publication
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
1 Scope
|
The present document provides the stage 3 description of the NGN integrated IPTV subsystem based on the architecture and stage 2 information flows described in TS 182 028 [4]. The protocol enhancements will form the scope of new or enhanced protocol specifications. The interaction with other NGN subsystems such as PES, IMS and RACS will be considered. The current release is applicable to: • the interface between the User Equipment (UE) and the SD&S; • the interface between the User Equipment (UE) and Customer facing IPTV Applications (CF-IPTV-Apps); • the interface between the User Equipment (UE) and IPTV Control (IPTV-C); • the interface between the User Equipment (UE) and Media Control Functions (MCF); • the interface between the User Equipment (UE) and Media Delivery Functions (MDF); • the interface between the Customer facing IPTV Applications (CF-IPTV-Apps) and IPTV Control (IPTV-C); • the interface for access to IPTV User Data Function (IPTV UDF); • the interface between the IPTV Control (IPTV-C) and Media Control Functions (MCF); • the interface for access to NGN User Data Access Function (NGN UDAF).
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI ES 282 001 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI ES 282 004 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [3] ETSI ES 282 003 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [4] ETSI TS 182 028 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN integrated IPTV subsystem Architecture". ETSI ETSI TS 183 064 V3.4.1 (2011-02) 9 [5] ETSI TS 102 034 (V1.4.1): "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". [6] IETF RFC 2326 (April 1998): "Real Time Streaming Protocol (RTSP)". [7] IETF RFC 2617 (June 1996): " HTTP Authentication: Basic and Digest Access Authentication". [8] ETSI TS 102 539: "Digital Video Broadcasting (DVB); Carriage of Broadband Content Guide (BCG) information over Internet Protocol (IP)". [9] IETF RFC 2616 (June 1999): "Hypertext Transfer Protocol - HTTP/1.1". [10] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging". [11] ETSI TS 183 041 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3: Protocol specifications [Endorsement of 3GPP TS 24.247 Release 6]". [12] IETF RFC 3856 (2004): "Presence Event Package for the Session Initiation Protocol (SIP)". [13] ETSI TS 182 008 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service; Architecture and functional description [Endorsement of 3GPP TS 23.508 Release 7 and OMA-AD-Presence-SIMPLE-V1-0]". [14] IETF RFC 4662 (August 2006): "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists". [15] IETF RFC 4825 (May 2007): "The Extensible Markup Language (XML). Configuration Access Protocol (XCAP)". [16] IETF RFC 5025 (December 2007): "Presence Authorization Rules". [17] ETSI TS 183 063 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification". [18] IETF RFC 3265 (June 2002): "Session Initiation Protocol (SIP)-Specific Event Notification". [19] IETF RFC 1321 (April, 1992): "The MD5 Message-Digest Algorithm". [20] IETF RFC 3376 (October 2002): "Internet Group Management Protocol, Version 3". [21] IETF RFC 3810 (June 2004): "Multicast Listener Discovery Version 2 (MLDv2) for Ipv6". [22] ETSI TS 183 017 (Release 3): "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". [23] IETF RFC 4585 (July 2006): "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)". [24] IETF RFC 4588 (July 2006): "RTP Retransmission Payload Format". [25] IETF RFC 3261: "SIP: Session Initiation Protocol". [26] ETSI TS 184 009 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) Rules covering the use of TV URIs for the Identification of Television Channels". [27] IETF RFC 3611: "RTP Control Protocol Extended Reports (RTCP XR)". [28] IETF RFC 5760: "RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback". ETSI ETSI TS 183 064 V3.4.1 (2011-02) 10 [29] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". [30] IETF RFC 3926: "FLUTE - File Delivery over Unidirectional Transport". [31] W3C Recommendation (2002): "XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)". [32] W3C Candidate Recommendation (2007): "Cascading Style Sheets, level 2 Revision 1 (CSS 2.1) Specification". [33] W3C Candidate Recommendation: "CSS TV Profile 1.0". [34] ISO/IEC International Standard 16262 (2002): "Information technology - ECMA Script language specification". [35] W3C Recommendation: "Document Object Model (DOM) Level 2 Core Specification". NOTE Available at http://www.w3.org/DOM/DOMTR#dom2 [36] W3C Candidate Recommendation: "XMLHttpRequest". [37] Void. [38] Void. [39] Void. [40] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [41] IETF RFC 2818: "HTTP Over TLS". [42] Void. [43] Void. [44] IETF RFC 5576: "Source-Specific Media Attributes in the Session Description Protocol (SDP)". [45] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". [46] Void. [47] ETSI TS 181 016 (V3.3.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN Services and IPTV". [48] IETF RFC 1305: "Network Time Protocol (Version 3), Specification, Implementation and Analysis". [49] ETSI TS 184 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Identifiers (IDs) for NGN". [50] IETF RFC 4282: "The Network Access Identifier". [51] CEA CEA-2014-A ERTA (2008): "Web-based Protocol Framework for Remote User Interface on UpnP™ Networks and the Internet (Web4CE)". ETSI ETSI TS 183 064 V3.4.1 (2011-02) 11
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 187 013 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study on IPTV Security Architecture". [i.2] F. Boronat, J. Lloret, M. García: "Multimedia group and inter-stream synchronization techniques: A comparative study", Elsevier Information Systems 34 (2009), pp. 108-131. [i.3] ITU-T Recommendation H.760:"Overview of multimedia application frameworks for IPTV services". [i.4] ETSI TR 182 030 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV architecture, NGN based IPTV mapping or interconnect between IPTV systems". [i.5] Void. [i.6] ITU-T Recommendation G.114: "General Recommendations on the transmission quality for an entire international telephone connection, One-way transmission time", May 2003. [i.7] ETSI TS 102 727 (V1.1.1): "Digital Video Broadcasting (DVB); Multimedia Home Platform (MHP) Specification 1.2.2". [i.8] W3C Recommendation Scalable Vector Graphics (SVG) 1.1 Specification. [i.9] W3C Recommendation Scalable Vector Graphics (SVG) Tiny 1.2 Specification. [i.10] OMA, XHTML Mobile Profile v. 1.2. [i.11] W3C HTML5, W3C Working Draft. [i.12] ETSI TS 182 019 (Release 3):"Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Content Delivery Network (CDN) architecture - Interconnection with TISPAN IPTV architectures". [i.13] SCTE-130 part 3: "Digital Program Insertion - Advertising Systems Interfaces; Part 3: Ad Management Service (ADM) Interface". NOTE: Available at: http://www.scte.org/documents/pdf/standards/top%20ten/ANSI_SCTE%20130- 3%202009.pdf). [i.14] ITU-T Recommendation X.891: "Information technology - Generic applications of ASN.1: Fast infoset". [i.15] ETSI TS 102 472: "Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Content Delivery Protocols". [i.16] ISO/IEC 23001: "Information technology - MPEG systems technologies". [i.17] ETSI TS 187 003 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture". ETSI ETSI TS 183 064 V3.4.1 (2011-02) 12
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
3 Definitions and abbreviations
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: NGN Integrated IPTV subsystem: IPTV subsystem integrated within TISPAN NGN architecture which provides advanced personalized interactive IPTV services UE (converged): end user device, e.g. set top box or enhanced TV, capable of supporting IPTV services and services provided by other NGN subsystems
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
3.2 Abbreviations
|
For the purposes of the present document the abbreviations given in TS 182 028 [4] and the following apply: ADM Ad Management Service ADS Ad Decision Service ASF Application Server Function BC BroadCast BCG Broadband Content Guide BiM Binary MPEG format for XML BTV Broadcast TV CCF Cluster Controller Function CDF Content Delivery Function CDN Content Delivery Networks CDNCF Content Delivery Network Control Function CF Customer Facing CFIA Customer Facing IPTV Applications CoD Content on Demand CoD-MF Content on Demand Media Functions c-PVR Client PVR CR Content Recommendation CRS Content and service Recommendation Service CSS Cascading Style Sheets DHCP Dynamic Host Configuration Protocol DNS Domain Name System DVB Digital Video Broadcast DVBSTP Digital Video Broadcasting Service discovery and Selection Transport Protocol ECF Elementary Control Function EFF Elementary Forwarding Function EPG Electric Program Guide ESG Electronic Service Guide FB FeedBack FE Functional Entity FLUTE File Delivery over Unidirectional Transport GOP Group of pictures GUI Graphical User Interface HTTP HyperText Transfer Protocol ID IDentifier IGMP Internet Group Management Protocol IGMPv2 Internet Group Management Protocol version 2 IGMPv3 Internet Group Management Protocol version 3 IM Instant messaging IMS IP Multimedia Subsystem IPTV UDF IPTV User Data Function IPTV Internet Protocol TeleVision IPTV-C IPTV Control Ipv4 Internet Protocol version 4 ETSI ETSI TS 183 064 V3.4.1 (2011-02) 13 IUDF IPTV User Data Function LMB Linear Media Broadcast MBwTM Media Broadcast with Trick Modes MC MulitCast MCF Media Control Function MDF Media Delivery Function MF Media Function MLD Multicast Listener Discovery (protocol) MLDv1 Multicast Listener Discovery version 1 MLDv2 Multicast Listener Discovery version 2 MM7 MMS protocol MMS Multimedia Messaging Service MSAS Synchronization Application Server NAI Network Access Identifier NGN Next Generation Network NPT Normal Play Time nPVR network-side Personal Video Recorder NTP Network Time Protocol OSA Open Service Access PCh Personalized Channel POIS Placement Opportunity Information Service PS Presence Server PUA Presence User Agent PVR Personal Video Recorder RACS Resources Admission Control Sub-system RET RETransmission RFC Request For Comments RLS Resource List Server RR Receiver Report RSI Receiver Summary Information RTCP Real Time Control Protocol RTCPSSM RTCP extension for Source Specific Multicast RTP Real Time transport Protocol RTSP Real Time Streaming Protocol SC Synchronization Client SCP Service Content Protection S-CSCF Serving Call Session Control Function SCTE Society of Cable Telecommunications Engineers SD&S Service Discovery and Selection SDES Source Description RTCP Packet SDP Session Description Protocol SIP Session Initiation Protocol SIS Subscriber Information Service SMPP Short Message Peer-to-Peer SMS Short Message Service SMTP Simple Mail Transfer Protocol SOAP Simple Object Access Protocol SR Sender Report SSRC Synchronization SouRCe TCP Transmission Control Protocol TPF Transport Functions TsTV Time-shift TV UDAF User Data Access Function UDP User Datagram Protocol UE User Equipment UGC User Generated Content UPSF User Profile Server Function URI Uniform Resource Identifier URL Uniform Resource Locator UTC Coordinated Universal Time VBR Variable bitrate WEB4CE Web-based Protocol and Framework for Consumer Electronics ETSI ETSI TS 183 064 V3.4.1 (2011-02) 14 XCAP XML Configuration Access Protocol XDMS XML Data Management Server XML Extensible Markup Language XR eXtended Report
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4 Applicability
|
The following clauses explain the concept and approach used to define the protocols for the NGN integrated IPTV subsystem.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.1 Concept and Approach
|
This clause outlines concept and approach adopted in the present document. The approach is then applied to protocol selections, mapping to interfaces and protocol extensions. The present document focuses on defining protocols for flexible functional architecture described in [4], which can: • allow development of new IPTV subsystem in NGN; • integrate existing IPTV subsystem in NGN; • extend both to support other NGN services. In order to achieve high level of flexibility and support integration of existing subsystems, the work is focused on evaluating and endorsing protocols already defined for similar functions in [5] and other standard bodies. Protocol extensions are defined where applicable as well as overall applicability to the end-to-end architecture [4]. For example, recommendations are made how to integrate DVB compliant UE without modifications and DVB compliant system with minimal modification to the service layer.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.2 Overview
|
The clause describes applicability of the protocols discussed further in the present document to reference points defined in TS 182 028 [4]. The overall functional architecture for the NGN integrated IPTV service conforms to [4]. Figure 1 presents mapping of protocols to interfaces in NGN integrated NGN-IPTV and to interworking with other NGN subsystems and common components. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 15 UE SD&S CFIA Transporting processing functions MCF IPTV-C UPSF Xc Sh Ss Ct2 Xd Xp Sa Tr Sh UDP/RTP/RTCP Diameter RTSP HTTP Legend: NGN integrated IPTV model DVBSTP ECF/EFF IGMP/MLD Other Dj Ud NASS RACS MDF Gq’ IUDF Tr e2 e4 NGN Apps NGN App UDF IUDF Ug Not defined Intr NGN and CFIA UE & NGN Apps Intr Ss’ NOTE: Xc and Xd are logical interfaces that can be decomposed into Dj and optionally Di, Ds or Iz interfaces depending on the location of the MCF or MDF as described in [4] clause 5.2.5 for Xc and clause 5.1.6 for Xd. Figure 1: Protocols mapped to NGN integrated IPTV functional architecture ETSI ETSI TS 183 064 V3.4.1 (2011-02) 16 Table 1: NGN integrated IPTV functional entities and protocols used on interfaces FE/ Reference .point (protocol) UE IPTV-C CFIA SD&S UPSF IUDF MCF MDF ECF/ EFF UE --- Ct2 (RTSP), (HTTP, Optional) Tr (HTTP) Tr (HTTP, DVBSTP) --- --- Xc (RTSP, HTTP optional) Xd (UDP/ RTP /RTCP, HTTP, FLUTE optional) Dj, Di IGMP/ MLD IPTV-C Ct2 (RTSP), (HTTP, Optional) --- Ss (HTTP) --- Sh (Diameter) Ud (not defined) Sa (RTSP) --- --- CFIA Tr (HTTP) Ss (HTTP) Sh (Diameter) Ss' (HTTP) --- --- --- --- --- SD&S Tr (HTTP, DVBSTP) --- Ss' (HTTP) --- --- --- --- --- --- UPSF --- Sh (Diameter) Sh (Diameter) --- --- --- --- --- --- IUDF --- Ud (not defined) --- --- --- --- Ud (not defined) --- --- MCF Xc (RTSP, HTTP optional) Sa (RTSP) --- --- --- Ud (not defined) --- Xp (not defined) --- MDF Xd (UDP/ RTP/RTC P, HTTP, FLUTE optional) --- --- --- --- --- Xp (not defined) --- ECF/ EFF --- --- --- --- --- --- --- --- --- NOTE 1: NGN integrated IPTV protocol model is required to comply with standards applicable for NGN integrated IPTV as defined below. NOTE 2: See clause 4.3.9 for more details on the Sync interface. Usage of the HTTP protocol across the following interfaces is described in clause 5: • interface Tr; • interface Xc; • interface Xd; • interface Ss, Ss'; • interface Ct2 (Optional); • interface Sync (Optional). Usage of the HTTP protocol for interactions between NGN Applications and UE is described in annex E. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 17 Usage of the RTSP protocol across the following interfaces is described in clause 6: • interface Ct2; • interface Sa; • interface Xc. Usage of the IGMP/MLD protocol across the following interfaces is described in clause 7: • interface Dj, Di. Usage of the SIP protocol for interactions between NGN Applications and UE is described in the clause 8. Usage of the DVBSTP across the following interfaces is described in clause 9: • interface Tr. Usage of the RTP/RTCP protocol across the following interface is described in clause 10: • interface Xd; • interface Sync. Usage of the MPEG2 TS across the following interfaces is described in clause 10: • interface Xd; • interface Tr. NOTE 3: Applications can be transferred as private data streams inside MPEG2 TS. Applicability of MPEG2 TS to Tr interface is outside the current release. Usage of the AL-FEC protocol across the following interface is described in clause 10: • interface Xd. Usage of the FLUTE protocol across the following interface is described in clause 11: • interface Xd (optional). Use of Diameter shall comply to the following specifications: • [22] and [3] for interface; • [3] for e2 interface; • [1] for Sh interfaces.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3 Functional Entities
|
The functional entities that constitute the NGN integrated IPTV subsystem are defined in TS 182 028 [4]. The following clauses summarize the functionality of each functional entity.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.1 User Equipment(UE)
|
The UE is a functional entity that provides the user with access to IPTV services.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.2 Service Discovery and Selection (SD&S)
|
The Service Discovery and Selection (SD&S) is a functional entity that provides description information for discovery of the service as well as information required for description and selection of IPTV services. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 18
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.3 Customer Facing IPTV Applications (CF-IPTV-Apps)
|
The Customer Facing IPTV Application (CFIA) is a functional entity that provides IPTV service provisioning, selection and authorization.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.4 IPTV Control (IPTV-C)
|
The IPTV Control (IPTV-C) is a functional entity that checks if UE has been authorized by the Customer Facing IPTV Application to use IPTV Service Control and Delivery Functions (provides selection of the Media Control Function).
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.5 Media Control Function (MCF)
|
The Media Control Function (MCF) is a functional entity that provides the UE with functions required to control media flows and manages the MDFs under its control.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.6 Media Delivery Function (MDF)
|
The Media Delivery Function (MDF) is a functional entity that delivers content data to the UE.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.7 IPTV User Data Function (IPTV UDF)
|
IPTV user data (IUDF) functional entity is responsible for handling NGN integrated IPTV user data.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.8 NGN User Data Access Function (NGN UDAF)
|
NGN Application User Data FE (NGN UDF) is a functional entity responsible for handling NGN application and user data.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.9 Inter-destination media synchronization entities
|
Figure 1a shows the two functional entities involved in inter-destination media synchronization, i.e. the synchronization client (SC) and the media synchronization application server (MSAS). Optionally, there is also a Synchronisation Client' (SC'). These functional entities are described in clauses 4.3.9.1, 4.3.9.2 and 4.3.9.3. Figure 1a: Functional entities and reference points for inter-destination media synchronization. Media Synchronization Application Server (MSAS) Synchronisation Client' (SC') Sync’ Synchronisation Client (SC) Sync Session-level capabilities Media-level capabilities ETSI ETSI TS 183 064 V3.4.1 (2011-02) 19 As described in TS 182 028 [4], there exist different mappings of the SC and MSAS onto the functional entities depicted in figure 1. The mapping of the SC as an elementary function of the UE is aimed at small-scale deployments of services that require media synchronization and only if a limited number of UEs uses media synchronization. It reuses existing service initialization. The mapping of the SC as an adjunct function that may be co-resident with any of the appropriate elements of the Transport Processing Function is aimed at large-scale deployment of media synchronization. The process of inter-destination media synchronization involves two basic steps: 1) Synchronization initiation 2) Synchronization status information and settings instruction exchange NOTE: As the synchronization initiation is stateless, synchronization termination is not needed. Given these steps, the Sync reference point is decomposed as follows: • Synchronization initiation information is exchanged over the Tr reference point, using HTTP. Synchronization initiation information can also be exchanged over the Xc reference point, using RTSP/SDP. • Synchronization status information and delay information in the form of settings instruction is exchanged over the Xd reference points, using RTCP. RTCP reports with synchronization status information or synchronization settings instructions can be sent directly between UEs, if a direct communication channel between UEs already exists. In that case, one UE acts as co-located SC+MSAS as described in clauses 10.3.2 and A.13.2.3. The Sync' reference point is used to report synchronization correlation information on the synchronicity relationship between the incoming media stream (which could be received by some SCs) and the outgoing media stream(s) (which could be received by other SCs) from the SC' to the MSAS. The Sync' reference point uses RTCP.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.9.1 MSAS
|
The MSAS is a functional entity that coordinates session synchronization with SCs and SC's for inter-destination synchronization purposes. The MSAS session-level capabilities are reflected as elementary functions of the CFIA, its media-level capabilities are reflected as independent functional entities or as adjunct functions other functional entities. For synchronisation using a direct communication channel between multiple UEs, the MSAS is co-located with the SC in a UE. Tasks of the MSAS are: • setting up and accepting synchronization sessions with/from SCs; • collecting synchronization status information from SCs; • collecting synchronization correlation information from SC's; • calculating delay information and derive synchronization settings instructions for the SCs and distributing synchronization settings instructions to SCs.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.9.2 SC
|
The SC is a functional entity that coordinates session synchronization with the MSAS for inter-destination synchronization purposes. It is an elementary function of the UE or an adjunct function of the Transport Processing Functions. Tasks of the SC are: • setting up and accepting synchronization sessions with/from the MSAS; • sending synchronization status information to the MSAS; • receiving delay information in the form of synchronization settings instructions from the MSAS; • delaying (buffering) a media stream according to the received synchronization settings instruction. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 20
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.9.3 SC'
|
The SC' is a functional entity that assists session synchronization by the MSAS for inter-destination media synchronization purposes. It is an elementary or adjunct function of functional entities that modify and/or re-originate media streams, e.g. a transcoder or a mixer in an MDF.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.3.10 Service Protection and Content Protection function (SCP)
|
The functional entities and elementary functions that in the NGN integrated IPTV subsystem responsible for Service protection and content protection are defined in TS 182 028 [4] clause 7 and TISPAN NGN security architecture TS 187 003 [i.17] in clause 9 and IPTV security TR 187 013 [i.1].
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
4.4 Compliance
|
Compliance for the Integrated IPTV service conforms to table 1a. Table 1a: IPTV services and features supported by NGN integrated IPTV subsystem: NGN IPTV Release Service and Feature Short name (ServiceType) TISPAN R3 Stage 2 NGN integrated IPTV subsystem TISPAN R3 Stage 3 NGN integrated IPTV subsystem Specification TS 182 028 [4] Present document Linear/Broadcast TV BTV M M Linear/Broadcast TV with Trick Play BTVwTP M M Time Shifted TV TsTV O O Content on Demand CoD M M Push CoD pCoD M M Near COD nCoD M M Network PVR nPVR M M Client PVR cPVR O O Audio Audio M M Pay-Per-View PPV M M Interactive TV iTV M M Service discovery Sdisc M M Service Information (EPG) EPG M M Parental Control ParCont M M User Profiling & personalization UserProf O O Communications and Messaging msg O O Notifications notif O O IPTV Presence presence O O Interaction between users iuser O O Interaction with NGN services INGN O O Advertising AD M M Targeted Advertising TAI O O User Generated Content UGC O O Internationalization Intern O O Content recommendation CR O O Games Games O O Picture Pict O O Bookmarks (Content Marking) CB O O Personalized channel PCh O O Personalized Service Composition PSC O O Service Portability SerPort O O Service Continuation between IPTV UEs ServCont O O ETSI ETSI TS 183 064 V3.4.1 (2011-02) 21 NGN IPTV Release Service and Feature Short name (ServiceType) TISPAN R3 Stage 2 NGN integrated IPTV subsystem TISPAN R3 Stage 3 NGN integrated IPTV subsystem Service Continuation fixed-mobile ServCont O O Remote Control of IPTV services RemContr O O Emergency Information Emergency O O Interaction with 3rd Party application (e.g. Parlay) 3pty O O Interaction with Internet Services IntServ O O Service synchronization Synch O O Incoming call management CallMng O O NOTE: M - Mandatory, O- Optional, NA - not available or not specified (out of scope in release) in architecture. Features that are only used by optional services are optional as well.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5 Procedures using HTTP for NGN integrated IPTV
|
NGN integrated IPTV reference points (Tr, Ct2, Ss, Ss') using http shall follow HTTP/1.1 [9]. NOTE: Other protocols such as RTSP may be used on Ct2, Ss and Ss'. If URI is supplied as "http:" [40], the receiver and the sender shall conform to HTTP/1.1 [9] and use port specified in the URI. When the URI is specified as "https:", the receiver and the sender shall establish a connection using https [41] with TLS1.0 and SSL3.0, and apply encrypted communication using HTTP/1.1 at the port specified in the URI. If the port is not specified in the URI, default port 80 is used for "http:" and 443 for "https". URI and URL convention defined in [40] shall be used for access to TISPAN Integrated IPTV services.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1 User Equipment (UE) and Control Functions
|
Mechanism used for user interaction between UE and Control Function shall support service personalization and multiple user behind UE. Access to personalized IPTV services may required additional user authentication and authorization, e.g. PIN for content purchase, access to restricted content. The personalization of IPTV services should enable fulfil user personal expectation (provide user preferred content and services) during all steps of service selection and service delivery. The IPTV personalization requires unique identification of the IPTV user, or of the IPTV Service, with assignments made by the IPTV Service. The user identification used user identifiers for NGN subscribers as specified in TS 184 002 [49]. Private user identifier shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of RFC 4282 [50]. The user authentication shall follows details specified in clause 5.1.3, Procedure for Authentication using HTTP Digest [7].
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.1 Procedures for SD&S
|
Mechanisms used to identify service providers and services in the context of service discovery shall apply conforming to TS 102 034 [5], clause 5.2. SD&S segments may be encoded with BiM conforming to TS 102 034 [5], clause 5.5.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.1.1 Push mode
|
Push model delivery of BCGs using multicast shall use the DVBSTP protocol for this purpose in alignment with clause 4.1.2 of TS 102 034 [5]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 22
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.1.2 Pull Mode
|
In the pull model of unicast delivery of a DVB SD&S data, the HTTP protocol shall be used conforming to TS 102 034 [5], clause 5.4.2. In the pull model of unicast container-based delivery of DVB BCG data, the HTTP protocol shall be used conforming to TS 102 539 [8], clause 4.1.2.2.2. In the pull model of unicast query mechanism of DVB BCG data, the HTTP protocol is used to transport SOAP messages. This shall be conforming to TS 102 539 [8], clause 4.2. NOTE: Some services such as network PVR, notification may fall outside current [5] SD&S scope. In this case and for additional services the following mechanism may be used: The http request may contain other header fields conforming to the [9] and XML records specifying additional service name in the XML format. The response to the HTTP requests above shall contain matching XML service definition records or http URL of other SD&S server where this information can be discovered via alternative means. The additional XML definitions may be discarded by the UE.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.2 Procedure for Service Configuration
|
One of the following options should be supported: • An Application Server may implement the role of an XCAP server as described in [15] with standard authentication mechanisms as discussed below. • Standalone XDMS server may be used, in which case Tr interface is re-used between UE and the server. XCAP usage shall comply with [15]. • Service can be configured over standard http [9]. In this case UE normally implements WEB browser with JavaScript or higher support for running WEB applications.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.3 Procedure for Authentication
|
HTTP Digest [7] is recommended on the Tr interface. MD5 is recommended digest algorithm as defined in [19], MD5 Message Digest Algorithm.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.4 Procedure for Customer Facing IPTV Applications
|
Application interface is based on http protocol between UE (converged) and ASF (Customer Facing IPTV applications). UE should implement an http [9] compliant web browser with JavaScript support. Special requirement for CSS is to support to enable rendering capabilities. A particular implementation of the Web Browser is outside the scope of the present document, however, most of widely used browsers can be supported. Application Gateway may be used on the Tr interface; however, the gateway specification is outside the scope of the present document. Interface between UE and CFIA may use https if additional protection is required. If HTTP is used, the UE shall requested IPTV service using HTTP GET or POST methods towards CFIA and supply ServiceType for selected IPTV services. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 23 The ServiceType HTTP parameter is conveyed as an URI parameter and shall use the following format: • "http:" "//" host [ ":" port ] "/etsi/iptv/service?ServiceType=" ServiceType • http://iptv.domain.com:80/etsi/iptv/service?ServiceType=CB The HTTP Accept header shall include the content-type identifier that corresponds to the MIME type of XML documents representing service parameters: "application/vnd.etsi.iptvservice+xml". Table 1b: Customer facing IPTV services, their service types and XML schemas IPTV Service ServiceType Clause where procedure described XML schema Notification notif 5.1.5 Annex C.1 Messaging msg 5.1.6 Annex C.1 Presence information presence 5.1.7 Annex C.1 Targeted Advertising tai 5.1.8 Annex H User Generated Content ugc 5.1.9 Annex G (content description) Annex C (notification) Content Recommendation cr 5.1.10 Annex C.1 Content Bookmarks cb 5.1.11 Annex F.1(XML schema for content bookmarks) Interactive TV itv 5.1.12 N/A Interaction between users iuser 5.1.13 C.1 Interaction with 3rd Party application (e.g. Parlay) and Internet services 3pty 5.1.14 N/A Client PVR cpvr 5.1.15 N/A Personalized Channel pch 5.1.17 Annex I (XML schema for Content Playlist) Service continuation sc 5.1.18 Annex F.1(XML schema for content bookmarks)
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.5 Procedure for Notifications
|
The UE may receive notifications from the CFIA using Tr interface between the UE (converged) and IPTV ASF (Customer Facing IPTV applications) via HTTP protocol [9] and either present notification on GUI (Graphical User Interface) or initiate service action or both. The IPTV ASF (CFIA) shall support XML notifications over HTTP [9] via Tr reference point. Procedure for IPTV Notification shall follow signalling flows described in clause B.8.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.6 Procedure for Messaging
|
The UE may initiate and present received messages via CFIA using Tr interface between UE (converged) and ASF (Customer Facing IPTV applications) via HTTP protocol [9]. The UE may initiate and present received messages through interactions with the Common NGN ASF as described in TS 182 028 [4], annex A.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.7 Procedure for presence information
|
The UE may receive presence information via CFIA on Tr interface via HTTP protocol [9]. The CFIA may use the Presence User Agent (PUA) as described in [12] and [13]. Alternatively, presence Network Agent as described in [13] may be used for IPTV in the Common NGN ASF as a gateway to the NGN Presence Server (PS). The Presence Server or agent can be located in the network. The PUA can request resource lists from a Resource List Server (RLS) as described in [14] to retrieve presence information from multiple users. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 24 The PUA (or presence network agent if used alternatively) should provide the mapping of IPTV user account to IMS user identities. UE may inform CFIA about presence status information. Alternatively presence information may be collected by the PUA or network agent (in Common NGN ASF) and reported to the NGN presence server.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.8 Procedure for Targeted Advertising
|
NGN Integrated IPTV advertising procedure shall follow procedure for targeted ad insertion, interactive ad insertion and regionalised ad insertion defined in clause 11.10 [4]. NGN Integrated IPTV uses XML schema carried over HTTP on Adx and Ady interfaces, which are defined in annex H "SCTE based targeted advertising architecture" of [4]: • Adx used to exchange advertising related messages between an ADM in the TISPAN CFIA and an SCTE-130 functional entities: ADS, POIS and SIS. XML schema carried over HTTP shall apply conforming to SCTE130-3 [i.13]. • Ady used to exchange advertising related messages between TISPAN IPTV MF and an SCTE-130 ADS for unicast and broadcast services. The MF entity is interconnected with the Ad Decision service via Ady to made ad-selection and ad-placement requests for both broadcast and unicast (e.g. for interstitial, pause opportunities) services. XML schema carried over HTTP shall apply conforming to SCTE130-3 [i.13].
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.9 Procedure for User Generated Content
|
The UGC procedures consist of two main phases: UGC creation and watching UGC. The UGC creation procedure comprises four steps as described in [4]. Http is used between UE and CFIA over Tr reference point: • Step 1: Declaration of User Generated Content. • Step 2: Description of User Generated Content information by the UE. • Step 3: Creation of User Generated Content. • Step 4: Publication of User Generated Content information by the CFIA. In step 1 UE sends a User Generated Content creation request to the CFIA and receives a content ID from the CFIA using XML schema over HTTP. The content ID is location independent and globally unique. In step 2 UE sends a request to the CFIA containing XML description of the User Generated Content: name, type, restriction, textual description, special group and others. The XML schema for content description is provided in annex G. In step 3 the UE requests CFIA via Tr to post User Generated Content either directly via HTTP or upload/upstream in unicast to the MF. In case the UGC is upstreamed to the MF the HTTP request contains a SDP or XML session description of the media, see [5]. If the content is distributed to the MF, the MF confirms to the CFIA the location at which the UGC becomes available. The CFIA keeps the link between UGC content ID, UGC description and optionally the MF. When user generated content is uploaded using HTTP method PUT shall be used. When user generated content is upstreamed, HTTP PUT or HTTP streaming shall be used. NOTE 1: The speed at which content is transmitted with HTTP is limited by the available bandwidth. In the case of HTTP PUT, the difference between uploading and upstreaming lies in setting the bitrate for upstreaming such that the available bandwidth is equal or higher than the encoding bitrate. This allows for delivery of the file in real-time. In the case of HTTP streaming, content that is transported without storing or very limited buffering, similar to CoD streaming. NOTE 2: XMLHttpRequest can be used for asynchronous signalling of the content. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 25 In step 4 CFIA publishes this UGC description to the SD&S to make it available to subscribed UEs. CFIA may use existing notification mechanism to announce new UGC content to interested UEs (following http procedures defined in clause 5.1.5). The UGC description publication by the CFIA in step 4 may take place before, during or after the UGC content creation in step 3. After UGC publication a UE can select UGC by browsing SD&S and initiate watching of User Generated Content, or pre-select UGC by subscribing to UGC that has already been declared and published, but not yet created. These procedures allow a user to select and watch User Generated Content where initiation and delivery of UGC content shall used existing procedures (clause 6.1) for CoD, BC or PushCoD services. When a UE pre-selects UGC that has already been declared and published, but not yet created, the UE is notified by the CFIA when the UGC becomes available, using the existing notification procedure from clause 5.1.5. The notification follows the XML schema of annex C, where tIPTVNotificationActionType has the value "UGC_preselection" and tIPTVNotificationDescription contains the UGC ContentId that the UE subscribed to. The notification triggers the UE to initiate UGC retrieval using existing procedures (clauses 6.1.2 and 6.1.6), at which the MF associates the upstream multimedia stream (this clause, step 3) with the downstream multimedia stream (clauses 6.1.2 and 6.1.6).
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.10 Procedure for Content Recommendation
|
The Content and service RecommendationService (CRS) is used for providing recommendations to IPTV users or user groups. The recommendation service may make recommendations to user/groups based on different criteria including user profile, user indicated preferences, current viewing habits, historic user activities as defined in [4]. The recommendation may be in form of text message (notification), multimedia message, content bookmark (pointer to recommended content) or video recommendation streamed from MDF. The CRS service procedures include aggregation and correlation of metadata/information for recommendations as described in clause 11.9 in [4]. User profiling mechanism may be used for collecting and evaluation of user preferences (self settings of user interest), user data (service history, presence information, content bookmarks) and actual service state to provide support for correctly targeted Content Recommendation. CFIA may request content recommendation either based on UE actions or on trigger from external CRS. CFIA should deliver content recommendations via existing http notification mechanisms. If user accepts recommendation, the UE shall request delivery of recommended content using existing procedures for particular content type (e.g. CoD, BC, UGC, PushCoD, etc.) or generate content bookmark for later delivery request.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.11 Procedure for Content Bookmarks
|
An IPTV Content Bookmark service consists of two main steps: • Creation of IPTV Content Bookmark: allows a user to create and store configurable pointers to content, e.g. entire or parts of content (favourite scene) to be able to quickly access the specified content and location. • Retrieval of IPTV Content Bookmark: allows to access directly content or exchange and share data about user's favourite IPTV content. Creation and retrieval shall use HTTP over Tr interface between UE and CFIA. Content Bookmarks should be stored in User Profile. User may enable sharing of bookmarks, in which case CFIA may update SD&S with bookmarks metadata. Content Bookmark shall used XML schema from annex F. Procedure for Content Bookmarks may be adopted by other services and procedures to identify point and share pointer to exact content (from defined time as entire or part of the content) as for example: • Service continuation. • Content recommendation. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 26 • User interaction. • Interactive TV. • Notification (about content or specific part of content). Content Bookmark primary purpose is to set a personal user bookmark (which will be used by user or send to other users for sharing the bookmark), but same content bookmark mechanisms should be used as well by IPTV system itself pointing out the content or to refer to timestamp in content (following structure of XML schema in annex F). CFIA should control the use and authorization for any of the mentioned content bookmark. For some services may be Content Bookmark linked with content metadata (e.g. service selection information) and/or content description (as in annex G).
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.12 Procedure for Interactive TV
|
CFIA shall provide the UE with the selection of Interactive IPTV applications. After selection of Interactive IPTV application (e.g. as for example one from listed in clause 11.19 Interactive TV procedures [4]), the UE sends HTTP request to CFIA via Tr reference point to initiate selected Interactive TV application. The selected application can either be located with CFIA, or externally, in which case the UE shall be provided with URL of External Interactive IPTV application (clause 5.1.14). The UE should implement an HTTP [9] compliant web browser with JavaScript support. Special requirement for CSS is to support to enable rendering capabilities and adopted for presentation on TV. NOTE: A particular implementation of the Web Browser is outside the scope of the present document; however, most of widely used browsers can be supported. CFIA should act as HTTP proxy or redirect UE to external ASFs.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.13 Procedure for Interaction between users
|
The UE may initiate and received interaction messages between two or among multiple UEs via CFIA using Tr interface between UEs and ASF (Customer Facing IPTV applications) via HTTP protocol [9]. The interaction between UEs may contain HTTP messages with attached XML as described in clause A.5.1. 5.1.14 Procedure for Interaction with 3rd Party application (e.g. Parlay) and Internet services Same procedure as described in clause 5.1.12 shall apply for Interaction with 3rd Party application or external Internet services. If Parlay/Parlay X is used, OSA Parlay/Parlay X gateway for interaction with OSA S (as described in [4], clause A.1) shall be provided.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.15 Procedures for Client PVR (UE)
|
In order to provide Client PVR (c-PVR) service, the UE initially select required content from EPG/BCG via customer facing IPTV application and requests scheduling selected content for recording in the UE. Before the recording start, CFIA shall send notification to the UE based on clause 5.1.5, Procedure for Notifications, to initiate scheduled recordings (when UE is online). The application of IGMP protocol between UE and TPF for content delivery shall comply with BC procedure (clause 7.1.1 Procedure for BTV service). After the UE joins multicast channel, it shall start recording the content as Client PVR stored on the UE storage. Watching of recordings is performed locally in the UE and no further interaction with CFIA or SD&S is required. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 27
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.16 Procedure for initiation of inter-destination media synchronization
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.16.1 Synchronization Client (SC)
|
Upon a request for inter-destination media synchronization, the SC shall send an HTTP GET request to the MSAS. NOTE 1: There are various ways to convey which services require inter-destination media synchronization. This can be signalled via SD&S information (e.g. the BCG/EPG/ESG), through a shared service control session, with notifications, recommendations and others. The SC shall include the SyncGroupId as part of HTTP GET request. If the SyncGroupId is known, it shall be set accordingly. If no SyncGroupId is known, e.g. because the SC is first to setup the inter-destination media synchronization, the SC shall include the parameter but leave it empty. The SyncGroupId HTTP parameter is conveyed as an URI parameter and shall use the following format: • "http:" "//" host [ ":" port ] "/etsi/sync/syncgroup?SyncGroupId=" SyncGroupId SyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. The value SyncGroupId=0 represents an empty SyncGroupId. The value 4294967295 (2^32-1) is reserved for future use. The following URI shows an example of a reference to a sync group: • http://iptv.example.com:80/etsi/sync/syncgroup?SyncGroupId=1073774600 The HTTP Accept header shall include the content-type identifier that corresponds to the MIME type of XML documents representing synchronization parameters: "application/vnd.etsi.iptvsync+xml". If the SC is mapped on the UE, then the SyncGroupId parameter may be contained in the HTTP GET request for service initialisation, see also TS 182 028 [4], clauses 6.2.1 and 6.2.2. NOTE 2: The ways that an SC can obtain a SyncGroupId are similar to obtaining a phone conference id. For example, one user can request a new SyncGroupId through an off-line process, and share it with other users through an offline process. If the group of users does already have a group identifier, e.g. a phone conference id, they may reuse this identifier. When the SC receives an HTTP 200 OK response, the SC shall be able to deal with the following parameters, as described in clause 5.1.16.2: • ssrc-id; • rtcp-port: IP address plus port number; • SyncGroupId. The parameters are part of the XML payload in the HTTP response; see annex E for XML schema. The SC shall keep these values for use in synchronization status information and settings instructions procedures, described in clause 10.3. Since the SSRC value may change if an SSRC conflict is discovered at the transport level, the SC shall be prepared for this. When leaving a synchronization group, the SC shall send an HTTP DELETE request to the MSAS. The SC shall include the SyncGroupId as part of HTTP DELETE request.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.16.2 Media Synchronization Application Server (MSAS)
|
Upon receiving an HTTP GET request, the (session-level) MSAS shall be able to deal with the following parameter. • SyncGroupId. The SyncGroupId is received as an URI parameter, see clause 5.1.16.1. If the MSAS cannot retrieve a SyncGroupId parameter from the HTTP message, no further procedures apply. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 28 The MSAS shall assign a media-level MSAS using the SyncGroupId. If the SyncGroupId is present and empty (SyncGroupId=0), the MSAS shall assign a new SyncGroupId to the synchronization session and it shall assign a media-level MSAS address and port to be used for this SyncGroupId. If the SyncGroupId is present and is assigned a value, the MSAS shall check if this value is known. If this value is known, the MSAS shall lookup the media-level MSAS address and port to be used for this synchronization group. If this value is not known, the MSAS shall assign an MSAS address and port to be used. If the SyncGroupId is empty, the MSAS shall store this SyncGroupId and assign a media-level MSAS address and port to be used for this SyncGroupId. NOTE 1: The MSAS can assign address and port values from a different media-level MSAesS if necessary. The MSAS shall include in its HTTP 200 OK response to the SC the following parameters: • ssrc-id; • rtcp-port: IP address plus port number; • SyncGroupId. The parameters are encoded in XML using the XML schema defined in annex E. The ssrc-id is a 32-bit unsigned integer in network byte order and represented in decimal. The SyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. The Content-Type header shall be set to the MIME type "application/vnd.etsi.iptvsync+xml". If the MSAS is mapped on the CFIA, then the sync interface maps on the Tr interface, and these parameters may be contained in the HTTP 200 OK response for service initialisation, see also TS 182 028 [4], clauses 6.2.1 and 6.2.2. NOTE 2: In case of a BTV service, in order to distinguish RTCP reports coming from the media-level MSAS and from the multicast media source, they can have different addresses. Upon receiving an HTTP DELETE request, the MSAS shall respond with a 200 OK message.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
5.1.17 Procedures for Personalized Channel (UE)
|
Personalized Channel (PCh) service allows user to define and watch one or multiple pre-configured/scheduled content items as a single (virtual) channel in timeline as user schedule on UE via Tr interface using HTTP protocol. UE shall construct Personalized Channel playlist follow XML schema specified in annex I (XML schema for Content Playlist). 5.1.18 Service continuation This clause discusses procedures for service continuation. 5.1.18.1 Procedure for service continuation using Content Bookmarks As described in [4] in clause 11.12 service continuation should be provided between two NGN IPTV UEs. The procedure is applicable for the following services: - Trick modes on broadcast TV. - Content on Demand. - Time-shift TV. - Network PVR. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 29 Service continuation contains two phases - pause and restart (sometime refer also as park and pick-up) where Content Bookmark procedures (from clause 5.1.11) should be reused in following way: • Pause for service continuation shall pausing actually watched content and creation of IPTV Content Bookmark with pointers to content (CoD, recorded as nPVR/Time-shift/BCwTM) and timepoint. • Restart of paused service then shall in second phase continue on bookmarked content and timestamp. Creation and retrieval shall use HTTP over Tr interface between UE and CFIA (Content Bookmark itself is based on the schema from annex F). Content Bookmarks should be stored in User Profile.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6 Procedures using RTSP for NGN integrated IPTV
|
The Real Time Streaming Protocol [6], or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips. This clause defines usage of RTSP in dedicated IPTV for interactive control between UE and IPTV service control functions: IPTV-C and MCF. RTSP application for interactive service control over IP multimedia delivery is defined in DVB-IPI [5] and unless stated explicitly otherwise, the application defined in DVB-IPI [5] is used. Service selection The service discovery and selection process as defined in clause 5 provides UE with the RTSP URL for initializing interactive multimedia delivery session. The URL discovery methods are discussed in clause 6.1.1 of [5]. The format of RTSP URL shall comply with [7]. Session transport A transient TCP connection is a temporary connection that exists only long enough to transmit one or more requests. The UE should use transient connection for exchanging control messages on Ct2 interface for selecting most suitable MCF function. After MCF is selected there is no need to keep the connection. A persistent TCP connection is a lasting connection between a client and RTSP server, all requests and replies are sent over the same connection, and the connection remains intact until the session is completed. The UE should use persistent connection for RTSP control over interactive media delivery on Xc interface. The usage of persistent connection is discussed in clause 6.1.2 of [5]. Optionally, transient connection can be used on Xc interface. A method to keep a persistent connection active is discussed in clause 6.1. Security considerations Security considerations discussed in clause 6.1.4 of [5] apply. Optionally HTTP Digest Access Authentication can be applied to RTSP control messages as defined in [7]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 30 Mapping between DVB and TISPAN profiles The services defined in the service level requirements and NGN integrated IPTV architecture is identical when mapped to DVB service profiles as defined in table 2. Table 2: Mapping between TISPAN IPTV services and DVB service profiles TISPAN Service DVB Service profile BTV LMB BTV with trick modes MBwTM CoD CoD Time-shift TV CoD Network PVR CoD RTSP Methods RTSP methods supported for each profiles and their definitions are identical to clause 6.3 [5]. The requirement to support XML structures in clause 6.3 of [5] is optional. SDP parameters can be used instead. RTSP Headers The pause trick mode operation may be signalled by the standard RTSP PAUSE message as defined in [6]. RTSP scale header with 0 value is optional.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1 User Equipment (UE) and Control Functions
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.1 Procedure for BTV service
|
Usage of RTSP protocol for normal broadcast services without trick modes is not defined in the present document.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.2 Procedure for CoD service
|
NGN integrated IPTV uses RTSP protocol [6] for control over the delivery of multimedia with real-time properties. Usage should be compliant with TS 102 034 [5] unless specified otherwise. Table 3 illustrates RTSP methods in [6], [5] and NGN integrated IPTV. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 31 Table 3: RTSP methods in [6], [5] and NGN integrated IPTV RTSP Method Direction: C = client - UE; S = Server - MCF RFC 2326 [6] DVB Requirement TS 102 034 [5] TISPAN NGN integrated IPTV LMB MBwTM and CoD Coupled mode Decoupled mode ANNOUNCE C→S MAY MAY MAY MAY MAY ANNOUNCE S→C MAY SHOULD SHOULD SHOULD SHOULD DESCRIBE C→S SHOULD SHOULD SHOULD SHOULD SHOULD GET_PARAMETER C→S MAY SHOULD SHOULD SHOULD SHOULD GET_PARAMETER S→C MAY MAY MAY MAY MAY OPTIONS C→S SHALL SHALL SHALL SHOULD SHOULD OPTIONS S→C MAY MAY MAY MAY MAY PAUSE C→S SHOULD N.A. SHALL SHALL SHALL PLAY C→S SHALL SHALL SHALL SHALL SHALL REDIRECT S→C MAY SHALL SHALL N.A. SHALL SETUP C→S SHALL SHALL SHALL SHALL SHALL TEARDOWN C→S SHALL SHALL SHALL SHALL SHALL SET_PARAMETER C→S MAY N.A. N.A. N.A. N.A. SET_PARAMETER S→C MAY N.A. N.A. N.A. N.A. RECORD C→S MAY N.A. N.A. N.A. N.A. NOTE 1: N.A. - Not Applicable. The text in bold shows optional difference in the required support of RTSP methods in NGN integrated IPTV and TS 102 034 [5]. NOTE 2: ANNOUNCE, DESCRIBE, OPTIONS are optional methods which are not shown explicitly on the NGN integrated IPTV flows, but may be supported by UE and MCF. Coupled mode: In the coupled mode Customer facing IPTV applications reserves the delivery resources via IPTV Control on Ss interface and returns the UE RTSP URL with the exact location of the MCF to request interactive media delivery. The format of RTSP URL shall comply with [6]. The UE in the coupled mode shall send RTSP SETUP message containing at minimum RTSP URL, Sequence, and Transport headers to establish video delivery. Sample message flow in the coupled mode is shown in table 4. Table 4: Sample RTSP message flow in coupled mode RTSP Method from UE RTSP Method to UE Reference point Notes SETUP Xc UE requested on-demand session from MCF RTSP 200 OK Xc PLAY Xc UE requested the play-out to start RTSP 200 OK Xc GET_PARAMETER Xc UE sends heartbeat to keep the session active RTSP 200 OK Xc PAUSE Xc UE initiated trick mode RTSP 200 OK Xc ANNOUNCE Xc MCF made asynchronously announcement to the UE, e.g. "End of stream reached" RTSP 200 OK Xc TEARDOWN Xc UE closed on-demand session RTSP 200 OK Xc Decoupled mode: In the decoupled mode Customer facing IPTV applications return the UE RTSP URL with the exact location of the IPTV control. Resource reservation, selection of the exact MCF and session recovery is done via IPTV control at the time when the delivery is requested. The UE in the decoupled mode shall send RTSP SETUP message containing at minimum RTSP URL, Sequence, and Transport headers to establish video delivery. Sample message flow in the decoupled mode is shown in table 5. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 32 Table 5: Sample RTSP message flow in decoupled mode RTSP method from UE RTSP method to UE Reference point Notes SETUP Ct2 UE requested on-demand session from IPTV control REDIRECT Ct2 IPTV Control nominates MCF and reserves delivery resources SETUP Xc UE requested on-demand session from MCF RTSP 200 OK Xc PLAY Xc UE requested the play-out to start RTSP 200 OK Xc GET_PARAMETER Xc UE sends heartbeat to keep the session active RTSP 200 OK Xc PAUSE Xc UE initiated trick mode RTSP 200 OK Xc ANNOUNCE Xc MCF made asynchronously announcement to the UE, e.g. "End of stream reached" RTSP 200 OK Xc TEARDOWN Xc UE closed on-demand session RTSP 200 OK Xc Decoupled mode can be used for on-demand session recovery in the real-time, e.g. due to MCF failure. The UE upon detection loss of stream repeats session initiation sequence from table 3, supplying the last position of the received video in the "Range" header of the first PLAY method. The newly allocated MDF continues media delivery from the interrupted position instead of the beginning. If the UE contains sufficient buffering, multimedia session is recovered without visible artefacts. Using both transient and persistent connection the UE should keep the session active by sending heartbeats in the form of RTSP GET_PARAMETER method at the negotiated time inter RTSP. This method is applicable to any control session during CoD, BTV with trick modes, time-shift TV and nPVR.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.3 Procedure for BTV with trick modes service
|
NGN integrated IPTV media broadcast with trick modes session is a service level aggregation of broadcast and on-demand sessions. Combined session flow is shown in clause 11.3 of [4]. Before starting the service, the UE shall request from the Customer facing IPTV applications RTSP URL from where the interactive media delivery can be requested using RTSP protocol. The service is started by joining broadcast channel as specified in clause 7. The UE can pause the stream by leaving the broadcast stream as discussed and clause 7 and optionally setup interactive media delivery using identical procedure to the COD service, clause 6.1.2. Both coupled and decoupled modes can be supported. In the coupled mode Customer Facing IPTV application nominates a particular MCF for on-demand media delivery. In the decoupled mode the selection is performed in the real-time during switch to the trick mode. Sample message flow for BTV with trick modes in the decoupled mode is shown in table 6. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 33 Table 6: Sample message flow for BTV with trick modes in the decoupled mode from UE to UE Reference point Notes IGMP JOIN Xd (Dj, Dl or Ds) UE requested to join broadcast channel. The Access and Core network performs local admission control. Multicast channel is delivered IGMP LEAVE Xd (Dj, Dl or Ds) UE requested trick mode. UE leaves multicast channel RTSP SETUP Ct2 UE requested on-demand session from IPTV control RTSP REDIRECT Ct2 IPTV Control nominates MCF and optionally reserves delivery resources (previously reserved resources can be re-used) RTSP PLAY Xc UE requested the play-out to start TRICK MODE control on Xc TEARDOWN Xc UE switches from trick mode RTSP 200 OK Xc ANNOUNCE Xc MCF made asynchronously announcement to the UE, e.g. "End of stream reached" RTSP 200 OK Xc IGMP JOIN Xd (Dj, Dl or Ds) UE switches back to life stream. The Access and Core network optionally performs local admission control. (previously reserved resources can be re-used)
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.4 Procedure for time-shift TV
|
In order to provide time-shift TV service, MDF records TV programs available on the broadcast channels. The programs form a part of EPG (BCG) as discussed in clause 5 and should be requested on Tr interface. After selecting time-shifted content from EPG/BCG, the UE requests from the customer facing IPTV applications RTSP URL for initializing multimedia delivery time-shifted content. The procedure from this point is identical to CoD service defined in clause 6.1.2.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.5 Procedure for nPVR
|
In order to provide nPVR service, the UE initially selected from EPG/BCG via customer facing IPTV application what content should be recorded in the MDF as discussed in clause 5. When the recording has been initiated, UE can request from the customer facing IPTV applications with the available recordings. The application of RTSP protocol for content delivery is identical to CoD procedure. NOTE: Both coupled and decoupled modes are supported for nPVR. In the coupled mode, client is allocated precise disk quote on a selected MDF. The MCF associated with the MDF is always selected for interactive control over nPVR services. In decoupled mode, statistical optimizations are possible, e.g. only one or small number of content copies is created and users are redetected to the nearest copies via Ct2 interface using RTSP REDIRECT. Content delivery's procedure is identical to time-shift TV service, MDF records TV programs available on the broadcast channels. The programs form a part of EPG (BCG) as discussed in clause 5 and should be requested on Tr interface.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.6 Procedures for Push CoD (UE, IPTV-C)
|
Push COD can be initiated by CFIA based on subscription, user profile or defined IPTV service provider offer. When CFIA identified event and time to push content to the UE, it shall send notification to the UE as described in clause 5.1.5 Procedure for Notifications before uploading or streaming of the content to the UE (procedure described as Push content from MDF). ETSI ETSI TS 183 064 V3.4.1 (2011-02) 34 Push CoD in case of unicast content delivery shall use unicast RTSP/HTTP based streaming or HTTP based download of CoD content. Where Push CoD content is streamed/downloaded from MDF to the UE. The UE stores push CoD content for later consumption. Push CoD multicast content delivery shall used BC multicast stream or optionally multicast download based on FLUTE from MDF via transport processing functions. The UE joins push CoD as BC service without immediate presenting content to the user. The UE instead stores push multicast CoD content for later consumption. The IPTV system shall support following download session types as described in [5], clause 10: • Scheduled Multicast Download (SMD) Session. • Carousel Multicast Download (CMD) Session. • Unicast Download (UD) Session. The UE and MF functions shall support all mandatory features of all three types of download sessions [5]. URI of PushCOD content and PushCOD download session descriptions can be provided in XML or in SDP syntax shall follow [5], clause 10.3.2).
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.7 Procedures for inter-destination media synchronization (SC)
|
If the SC did not receive the (complete) synchronization information from the CFIA via the procedure in clause 5.1.16.1, the SC shall request this information by including the SyncGroupId in the RTSP SET UP message. The SyncGroupId may be kept empty (value 0) if the SC does not yet know the SyncGroupId. • a=rtcp-xr: grp-sync,sync-group=<SyncGroupId>, as specified in TS 183 063, clause W.2 [17]. When receiving the reply to the RTSP SET UP message, the SC shall check its SDP and extract the SSRC, the rtcp-parameter containing the MSAS address and the SyncGroupId. When an SSRC conflict occurs at the transport level, the SC shall be prepared to receive an RTSP ANNOUNCE containing a new SSRC value.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.1.8 Procedures for inter-destination media synchronization
|
If the MCF receives an RTSP SET UP message containing a SyncGroupId in the SDP, the MCF shall include the following attributes in the SDP it sends to the SC: • a=ssrc:<ssrc-id> <attribute>:<value> as specified in [44]; • a=rtcp:port [nettype space addrtype space connection-address] as specified in [45]; • a=rtcp-xr: grp-sync,sync-group=<value>, as specified in TS 183 063, clause W.2 [17]. SyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. The value SyncGroupId=0 represents an empty SyncGroupId. The value 4294967295 (2^32-1) is reserved for future use. If an SSRC conflict occurs at the transport level, and the MF has to assign a new SSRC value, the MCF shall send an RTSP announce to the SC containing the new SSRC value as part of the modified SDP.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.2 IPTV Control (IPTV-C)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.2.1 Procedure for BTV service
|
Usage of RTSP protocol for normal broadcast services without trick modes is not defined in the present document. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 35
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.