hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
6.2 PULL mode: case 2
|
When the RCEF sends a CCR for PULL mode case 2, it shall use the mapping defined in table 6.3 for IGMPv3/MLDv2 request. Table 6.3: Rules for derivation of CCR AVPs from IGMPv3/MLDv2 requests for PULL mode case 2 CCR AVPs Derivation from IGMPv3/MLDv2 Parameters CC-Request-Type It shall be set to UPDATE_REQUEST. Framed-IP address It shall set to termination point IP address. Physical-Access-Id It shall not be present. Logical-Access-Id It shall not be present. User-Name It shall not be present. Called-station-ID It shall not be present. Event-Trigger It shall be set to RESOURCES_MODIFICATION. Policy-rule-Report If the flow is already received, for each multicast/source address: • Policy-rule-Name shall be set to the corresponding policy rule name for that pair. • If Record Type indicates BLOCK_OLD_SOURCE or CHANGE_TO_INCLUDE_MODE with an empty source list, Policy-Rule-status shall be se to INACTIVE. Flow-Description If the flow is not already received, for each multicast/source address: • Direction shall be set to "in". • Destination address shall be set to the "multicast address". • Source address shall be set to the Source address if present. • Source and Destination port shall be not be supplied. When the RCEF sends a CCR for PULL mode case 2, it shall use the mapping defined in table 6.4 for IGMPv2 request. Table 6.4: Rules for derivation of CCR AVPs from IGMPv2 requests for PULL mode case 2 CCR AVPs Derivation from IGMPv2 Parameters CC-Request-Type It shall be set to UPDATE_REQUEST. Event-Trigger It shall be set to RESOURCES_MODIFICATION. Policy-rule-Report If the flow is already received: • Policy-rule-Name shall be set to the corresponding policy rule name for the Group Address indicated in the request. • If the type is set to 0x17 "Leave Group" Policy-Rule-status shall be se to INACTIVE. Flow-Description If the flow is not already received: • Direction shall be set to "in". • Destination address shall be set to the Group Address parameter. • Source address shall not be supplied. • Source and Destination port shall be not be supplied. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 12
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7 Behaviours of the transport functions for unicast
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1 Push mode (RACS initiated Procedures)
|
This clause specifies the behavior of the RSVP transport functions for unicast in the case of Push mode with on-path QoS reservation.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.1 Handling Policy-Install-Request from RACS
|
On receipt of a Policy-Install-Request from RACS, the RCEF shall process the message as specified in TS 183 060 [2]. In addition, when operating in the Push mode with on-path QoS reservation, the RCEF shall extend this behavior as defined in clause 7.1.1.1 (respectively clauses 7.1.1.2 and 7.1.1.3) in case of policy activation (respectively policy modification and policy deactivation).
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.1.1 Activation of a Policy Rule
|
On receipt of a Policy-Install-Request with PI-Request-Type AVP containing the value INITIAL_REQUEST that activates a new Policy Rule with Flow-Status ENABLED-DOWNLINK, the RCEF shall consider that a new on-path QoS reservation is to be initiated for each IP Flow defined in a Flow-Description AVP. The RCEF shall communicate with the BTF to ensure that an RSVP Path message is transmitted. The parameters in the RSVP Path message shall be mapped from those of the PIR command in accordance with table 8.1. The BTF is responsible for refreshing the RSVP path state in accordance with RSVP procedures during all the time that the corresponding Policy Rule is maintained active by the RACS.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.1.2 Policy Modification
|
On receipt of a Policy-Install-Request with the PI-Request-Type AVP set to UPDATE_REQUEST, and a Policy-Rule-Install AVP specified (with Flow-Status ENABLED-DOWNLINK), the RCEF shall consider that the existing on-path QoS reservation for each IP Flow is to be modified. The RCEF shall communicate with the BTF to ensure that an RSVP Path message is re-signalled for each such existing on-path QoS reservation. The parameters in the RSVP Path message shall be mapped using the same mapping rules as used for establishment of an initial on-path QoS reservation (i.e. in accordance with table 8.1). On receipt of a Policy-Install-Request with the PI-Request-Type AVP set to UPDATE_REQUEST, and a Policy-Rule-Install AVP (with Flow-Status REMOVED) or a Policy-Rule-Remove AVP specified, the RCEF shall consider that the existing on-path QoS reservation for each IP Flow is to be torn down. The RCEF shall communicate with the BTF to ensure that an RSVP PathTear message is transmitted for each such existing on-path QoS reservation. The parameters in the RSVP PathTear message shall be the same as those used in the Path messages that were sent previously for the corresponding on-path QoS reservation. The BTF shall then communicate with the RCEF to confirm that the on-path QoS reservation has been torn down. Then, assuming all the other processing of the Policy-Install-Request as defined in [2] is successful, the RCEF shall return a Policy-Install-Answer to the RACS with the Result-Code AVP set to DIAMETER_SUCCESS.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.1.3 Deactivation of a Policy Rule
|
On receipt of a Policy-Install-Request with PI-Request-Type AVP set to TERMINATION_REQUEST, if the terminated Policy Rule(s) had a Flow-Status ENABLED-DOWNLINK the RCEF shall consider that the corresponding on-path QoS reservation for each IP Flow is to be torn down. The RCEF shall communicate with the BTF to ensure that an RSVP PathTear message is transmitted for each such existing on-path QoS reservation. The parameters in the RSVP PathTear message shall be the same as those used in the Path messages that were sent previously for the corresponding on-path QoS reservation. The BTF shall then communicate with the RCEF to confirm that the on-path QoS reservation has been torn down. Then, assuming all the other processing as defined in [2] is successful, the RCEF shall return a Policy-Install-Answer to the RACS with the Result-Code AVP set to DIAMETER_SUCCESS. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 13
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.2 Handling unicast transport control protocol events
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.2.1 RSVP Reservation establishment
|
On receipt of an RSVP Resv message for a new, or a modified on-path QoS reservation, the BTF shall process the RSVP message as per procedures specified in [1]. On successful establishment of the Resv state, the BTF shall notify the RCEF. Then, assuming all the other processing of the corresponding Policy-Install-Request as defined in [2] is successful, the RCEF shall return a Policy-Install-Answer to the RACS with the Result-Code AVP set to DIAMETER_SUCCESS. The BTF is responsible for managing the soft state of the RSVP Resv state. This includes handling received RSVP Resv refresh messages and processing of those in accordance with RSVP procedures. This also includes detecting time-out of the Resv state and handling of this situation as defined in clause 7.1.1.4.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.2.2 RSVP Reservation Reject/Establishment Failure/Modification Failure
|
On receipt of an RSVP message indicating that a new on-path QoS reservation establishment has been rejected (e.g. receipt of a PathErr message containing an ERROR_SPEC object with an error code of "Code 1 - Admission Control Failure" or "Code 2 - Policy Control Failure" as specified in [5]) or has failed possibly after appropriate re-attempts (e.g. a corresponding Resv message is not received in a timely manner) for an on-path QoS reservation that the BTF is attempting to establish, the BTF shall communicate this to the RCEF. In turn, the RCEF shall return a Policy-Install-Answer to the RACS with the Experimental-Result-Code AVP set to POLICY_ACTIVATION_FAILURE. The RCEF shall set the Rule-Failure-Code AVP within the Policy-Rule-Report AVP to RESOURCES_LIMITATION. The RCEF may include in the Error-Message AVP the following string: • "On-Path reservation Admission Control Failure" in case of a PathErr message with an ERROR_SPEC containing an error code "Code 1- Admission Control Failure". • "On-Path reservation Policy Control Failure" in case of a PathErr message with an ERROR_SPEC containing an error code "Code 2- Policy Control Failure". • "On-Path reservation failure because of Transport Network reasons" in the other cases of QoS reservation failure. The BTF should remove the corresponding Path state in the transport nodes by issuing an RSVP PathTear message (with the same parameters as the corresponding Path messages) unless the BTF knows that the path state has already been removed or never got established. On receipt of an RSVP message indicating that an on-path QoS reservation modification (e.g. reservation bandwidth increase) has been rejected but that the original reservation has been maintained (.i.e. on receipt of a PathErr with the InPlace flag set in the ERROR_SPEC as specified in [5]), the BTF shall communicate this to the RCEF. In turn, the RCEF shall return a Policy-Install-Answer to the RACS with the Experimental-Result-Code AVP set to POLICY_MODIFICATION FAILURE. The RCEF shall set the Rule-Failure-Code AVP within the Policy-Rule-Report AVP to RESOURCES_LIMITATION. The RCEF may include in the Error-Message AVP the following string: • "On-Path QoS reservation modification Admission Control Failure" in case of a PathErr message with an ERROR_SPEC containing an error code "Code 1- Admission Control Failure". • "On-Path QoS reservation modification Policy Control Failure" in case of a PathErr message with an ERROR_SPEC containing an error code "Code 2- Policy Control Failure". • "On-Path reservation failure because of Transport Network reasons" in the other cases of QoS reservation modification failure. The BTF shall maintain the Path state corresponding to the original QoS reservation.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.1.2.3 RSVP Reservation Loss/Tear-Down
|
The BTF shall detect the loss or teardown on an existing on-path QoS reservation that the RCEF established. The detection is based on existing RSVP procedures as specified in [2] and [5]. For example, this includes time-out of received Resv refreshes or receipt of an RSVP PathErr containing an ERROR_SPEC object with an error code of "Code 1 - Admission Control Failure" or "Code 2 - Policy Control Failure". ETSI ETSI TS 183 067 V3.1.1 (2009-11) 14 In case the BTF deems that attempting to re-establish the reservation is likely to succeed, the BTF may optionally re-attempt such reestablishment by resending an RSVP Path message with corresponding parameters. If that attempt fails, or if the BTF deems that re-attempting reservation establishment is unlikely to succeed, the BTF shall notify the RCEF that the on-path QoS reservation has been torn down. In turn, the RCEF shall generate an event towards the RACS (assuming explicit or implicit subscription of RACS for this event type). The event is of type LOSS_OF_BEARER. The RCEF shall set the Rule-Failure-Code AVP within the Policy-Rule-Report AVP to RESOURCES_LIMITATION. The RCEF may include in the Error-Message AVP the following string: • "On-Path Reservation Admission Control Failure" when the BTF detects the loss of reservation by receipt of a PathErr containing an ERROR_SPEC with an error code of "Admission Control Failure". • "On-Path Reservation Policy Control Failure" when the BTF detects the loss of reservation by receipt of a PathErr containing an ERROR_SPEC with an error code of "Policy Control Failure". • "On-Path QoS reservation failure because of Transport Network reasons" when the BTF detects the loss of reservation by any other means (e.g. Resv Refresh time-out). The BTF should remove the Path state for the reservation that was lost or torn downs by issuing an RSVP PathTear message (with the same parameters as the corresponding Path messages) unless it knows the Path state has already been torn down. If there are on-path QoS reservations for flows corresponding to the same Policy-Install-Request, the RCEF shall tear down these reservations by issuing an RSVP PathTear message for each other reservation.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.2 Pull mode (RCEF initiated Procedures)
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.2.1 Reservation pre-authorization
|
NOTE: The current release does not specify reservation pre-authorization for unicast pull-mode.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.2.2 Reservation establishment in pull mode
|
On receipt of an RSVP Resv message for a new on-path QoS reservation, the BTF shall process the RSVP message as per procedures specified in [1]. In case of RSVP message processing failure, the BTF shall behave in accordance with [1] (e.g. generate a ResvErr). In case of successful message processing, the BTF shall notify the RCEF. The RCEF shall then send a CCR request to the RACS to request actual reservation of the corresponding resources. The parameters in the CCR request shall be mapped from those of the RSVP Resv message in accordance with table 8.2, the CC-Request-Type AVP shall be set to INITIAL_REQUEST and the Flow-Status shall be set to ENABLED-DOWNLINK. The RACS shall respond to the RCEF with a CCA indicating whether the resource reservation was successfully performed by RACS. If the resource reservation is authorized by RACS, the RACS shall send a CCA with a Result-Code AVP set to DIAMETER_SUCCESS. The RCEF shall then confirm the positive decision to the BTF. In turn, the BTF shall forward the RSVP Resv message towards the reservation destination. If the resource reservation is not authorized by RACS, the RACS shall send a CCA with a Result-Code AVP set to DIAMETER_AUTHORIZATION_REJECTED. The RCEF shall then communicate the negative decision to the BTF. In turn, the BTF shall generate a ResvErr message with an ERROR_SPEC object whose Error Code is set to Policy Control Failure and shall not forward the Resv message.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.2.3 Reservation Loss/Tear-Down
|
The BTF shall detect the loss or tear-down on an existing on-path QoS reservation. The detection is based on existing RSVP procedures as specified in [2] and [5]. For example, this includes: • time-out of received Resv refreshes; • receipt of a ResvTear; • receipt of an RSVP PathErr containing an ERROR_SPEC object with an error code of "Code 1 - Admission Control Failure" or "Code 2 - Policy Control Failure"; • receipt of a PathTear. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 15 The BTF shall notify the RCEF of such reservation loss or tear-down. In turn, the RCEF shall send a CCR request to the RACS to notify RACS of the resource reservation termination. The CC-Request-Type AVP in this CCR shall be set to TERMINATION_REQUEST. The RACS shall release the corresponding resources and respond to RCEF with a CCA with Result-Code AVP set to DIAMETER_SUCCESS.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
7.2.4 Reservation Modification
|
The BTF shall detect the modification of an existing on-path QoS reservation (i.e. the change of one or more reservation parameters specified in the received Resv message). The BTF shall first process the RSVP message as per procedures specified in [1]. In case of RSVP message processing failure, the BTF shall behave in accordance with [1] (e.g. generate a ResvErr). In case of successful message processing, the BTF shall notify the RCEF of the reservation modification. The RCEF shall then send a CCR request to the RACS to request reservation adjustment of the corresponding resources. The parameters in the CCR request shall be mapped from those of the RSVP Resv message in accordance with table 8.2 and the CC-Request-Type AVP shall be set to UPDATE_REQUEST. The RACS shall respond to the RCEF with a CCA indicating whether the resource reservation was successfully modified by RACS. If the resource reservation modification is authorized by RACS, the RACS shall send a CCA with a Result-Code AVP set to DIAMETER_SUCCESS. The RCEF shall then confirm the positive decision to the BTF. In turn, the BTF shall forward the RSVP Resv message towards the reservation destination. If the resource reservation is not authorized by RACS, the RACS shall send a CCA with a Result-Code AVP set to DIAMETER_AUTHORIZATION_REJECTED. The RCEF shall then communicate the negative decision to the BTF. In turn, the BTF shall generate a ResvErr message with an ERROR_SPEC object whose Error Code is set to Policy Control Failure and shall not forward the Resv message. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 16
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
8 RSVP to Re parameters mapping
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
8.1 Push Mode
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
8.1.1 Re PIR to RSVP Path Parameter Mapping
|
When, in accordance with clause 7.1.1.1, the RCEF/BTF sends an RSVP Path message to initiate an on-path QoS reservation as a result of a received Policy-Install-Request from RACS, the mapping defined in the following table shall be used: Table 8.1: Re PIR to RSVP Path Parameter mapping RSVP Objects Derivation from PIR AVPs SESSION It shall be mapped from the Policy-Rule-Install AVP ->Policy-Rule-Definition AVP -> Flow- Description AVP: • Destination IP Address shall be set to Flow-Description AVP ->Destination IP Address. • Protocol shall be set to Flow-Description AVP ->Protocol. • Destination Port shall be set to Flow-Description AVP ->Destination Port. SENDER_TEMPLATE It shall be mapped from the Policy-Rule-Install AVP ->Policy-Rule-Definition AVP -> Flow- Description AVP: • Sender IP Address shall be Flow-Description AVP ->Source IP Address. • Sender Port shall be set to Flow-Description AVP ->Source Port. SENDER_TSPEC The RSVP Peak Data Rate [p] shall be mapped from Policy-Rule-Install AVP ->Policy-Rule-Definition AVP ->QoS-Information AVP: • Peak Data Rate shall be computed from the Flow-Description AVP -> Max-Requested-Bandwidth-DL. The Peak Data Rate shall be expressed in bytes/sec. It shall include IP headers but shall not include Layer-2 headers or any other Layer-2 overheads. The RSVP Token Bucket Rate [r] shall be mapped from Traffic-Descriptor-DL AVP: • Token Bucket Rate shall be computed from the Traffic-Descriptor-DL-> Committed-Data-Rate. The Token Bucket Rate shall be expressed in bytes/sec. It shall include IP headers but shall not include Layer-2 headers or any other Layer- 2 overheads. The other SENDER_TSPEC parameters may be mapped from the Traffic-Descriptor-DL AVP or from the traffic class identified by the TOS-Traffic-class AVP. POLICY_DATA (Preemption [3], AUTH_USER [4], AUTH_APP [4]) NOTE: The current release does not specify mapping from the Re PIR into the RSVP Path POLICY_DATA object. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 17
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
8.2 Pull Mode
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
8.2.1 RSVP Resv to Re CCR Parameter Mapping
|
When, in accordance with clause 7.2.2, the RCEF/BTF sends a CCR request to RACS to request resource reservation as a result of a received RSVP Resv message, the mapping defined in the following table shall be used: Table 8.2: RSVP Resv to Re CCR Parameter mapping CCR AVP Derivation from RSVP Resv Flow-Description AVP It shall be mapped from the SESSION and FILTER_SPEC objects: • Source Address shall be set to FILTER_SPEC IP Source Address. • Source Port shall be set to FILTER_SPEC Source Port. • Destination Address shall be set SESSION IP Destination Address. • Destination Port shall be set to SESSION Destination Port. • Protocol shall be set to SESSION Protocol Id. QoS-Information AVP It shall be mapped from the FLOWSPEC object: • QoS-Information AVP -> Max-Requested-Bandwidth-DL shall be computed from FLOWSPEC Peak Data Rate. • QoS-Information AVP ->Traffic-Descriptor-DL-> Committed-Data-Rate shall be computed from FLOWSPEC Token Bucket Rate. • QoS-Information AVP ->Traffic-Descriptor-DL-> Committed-Burst-Size shall be mapped from the FLOWSPEC Token Bucket Size. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 18 Annex A (informative): Change history Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 25-02-09 20WTD146r1 001 F WI3191 Unicast Pull Mode – RSVP Reservation Loss/Teardown 0.0.8 0.0.9 25-02-09 20WTD147r1 002 F WI3191 Unicast Pull Mode – RSVP Reservation Modification 0.0.8 0.0.9 25-02-09 20WTD213r1 003 F WI-03191 Editorial corrections 0.0.8 0.0.9 25-02-09 20WTD215r1 004 F WI3191 – Clarification of reservation pre-authorization for pull mode 0.0.8 0.0.9 11-03-09 CRs 001 to 004 TB approved at plenary#20 and move to v3.x.x since R2 deliverable has been TB approved 0.0.9 3.0.0 17-03-09 20bTD259r1 005 D CR 005 WG approved at 20Bis 3.0.0 3.0.1 28-09-09 22WTD146r1 006 D Editorial Cleanup 3.0.1 3.0.2 Publication 3.1.1 ETSI ETSI TS 183 067 V3.1.1 (2009-11) 19 History Document history V2.1.1 April 2009 Publication V3.1.1 November 2009 Publication
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
1 Scope
|
The present document describes the protocols used on the reference points defined for the Customer Network Device (CND) enabling the IMS-based IPTV service usage. This description is based on the architecture and stage 2 information flows contained in TS 185 009 [4], the architectural specifications of the Customer Network Gateway (CNG) described in TS 185 003 [3] as well as the protocol suites defined for the reference points between the CPN itself and the NGN in TR 185 007 [i.3]. The present document is to be regarded in close conjunction with TS 185 010 [5] as it covers only the IP TV related specifics.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
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. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
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] ETSI TS 182 027 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem". NOTE: The latest version in the V2.y.z series applies. [2] ETSI TS 183 063 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification". NOTE: The latest version in the V2.y.z series applies. [3] ETSI TS 185 003 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Network Gateway Architecture and Reference Points". NOTE: The latest version in the V2.y.z series applies. [4] ETSI TS 185 009 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Architecture and reference points of a customer network device for IMS based IPTV services". NOTE: The latest version in the V2.y.z series applies. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 7 [5] ETSI TS 185 010 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Premises Networks: Protocol Specification (Stage 3)". NOTE: The latest version in the V2.y.z series applies. [6] UPnP™ AV 1.0 Specifications, UPnP Forum. NOTE: Available at http://www.upnp.org/standardizeddcps/mediaserver.asp. [7] DLNA Networked Device Interoperability Guidelines v 1.5 expanded Oct 2006. NOTE: Available at http://www.dlna.org/members/guidelines/. [8] ETSI TS 182 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Organization of user data". [9] ETSI ES 283 003 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3". NOTE: The latest version in the V2.y.z series applies. [10] ETSI TS 129 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents". [11] ETSI TS 183 065 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Customer Network Gateway Configuration Function; e3 Interface based upon CWMP". NOTE: The latest version in the V2.y.z series applies. [12] ETSI TS 183 019 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment; User-Network Interface Protocol Definitions". NOTE: The latest version in the V2.y.z series applies. [13] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2". [14] ETSI ES 282 003 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". NOTE: The latest version in the V2.y.z series applies. [15] IETF RFC 2131: "Dynamic Host Configuration Protocol".
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 185 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); High level customer network architectures". [i.2] ETSI TR 185 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services requirements and capabilities for customer networks connected to TISPAN NGN". ETSI ETSI TS 185 011 V2.1.1 (2009-07) 8 [i.3] ETSI TR 185 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Analysis of protocols for customer networks connected to TISPAN NGN". [i.4] TR-135 specifications: "Broadband Forum TR-135 "Data model for TR-069 enabled Set-Top Box". [i.5] TR-069 specification Annex G: "Broadband Forum TR-069 amendment 2 "CPE WAN Management Protocol v1.1".
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
3 Definitions and abbreviations
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: Customer Premises Network (CPN): in-house network composed by customer network gateway, customer network devices, network segments, network adapters and nodes NOTE 1: See TR 185 004 [i.1]. NOTE 2: Network segments are physical wired or wireless connections between customer premises network elements; network adapters are elements performing a L1/L2 conversion between different network segments; nodes are network adapters with L3 routing capabilities. CPN Device: device that is physically installed in the CPN allowing user access to network services; this can be a Customer Network Gateway with gateway functionalities towards the NGN, or a Customer Network Device being the end user terminal NOTE: See TR 185 005 [i.2]. Customer Network Gateway (CNG): CPN device acting as a gateway between the CPN and the NGN NOTE 1: See TR 185 004 [i.1]. NOTE 2: CNG is able to perform networking functions from physical connection to bridging and routing capabilities (L1-L3), but also possibly implementing functions related to the service support (up to L7). Customer Network Device (CND): CPN device enabling the final user to have direct access to services through a specific user interface NOTE 1: See TR 185 004 [i.1]. NOTE 2: CNDs can be dedicated to the internet, conversational and audio-video services. But they could be also Consumer Electronics equipment and other devices which may have nothing to do with these premium services (e.g. services performing a content sharing within a CPN, typically between a PC and a music system).
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ALG Application Layer Gateway B2BUA Back-to-Back User Agent BC BroadCast CDS Content Directory Service CND PPF CND Plug and Play Function CND Customer Network Device CND-AtF CND Attachment Function CNG Customer Network Gateway CNG-ACF CNG-Admission Control Function ETSI ETSI TS 185 011 V2.1.1 (2009-07) 9 CNGCF Customer Network Gateway Configuration Function CNG-NFF CNG NAPT and Firewall Function CNG-PCF CNG Policy Control Function CoD Content on Demand CPN Customer Premises Network CWMP CPE (Customer Premises Equipment) WAN Management Protocol DHCP Dynamic Host Configuration Protocol DNS SRV Domain Name Server Service FW Firewall IETF Internet Engineering Task Force IGMP Internet Group Management Protocol IMS IP Multimedia Subsystem IP Internet Protocol IPTV IP Television NAPT Network Address and Port Translation NAT Network Address Translation NGN Next Generation Network NPVR Networked Personal Video Recorder P-CSCF Proxy-Call Session Control Function PSI Public Service Identifier QoS Quality of Service RTP Real-time Transport Protocol SDF Service Discovery Function SIP Session Initiation Protocol STB Set Top Box UPnP Universal Plug and Play URI Uniform Resource Identifier WAN Wide Area Network
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
4 Overview
|
The clause briefly describes applicability of the protocols discussed further in the present document to the Reference Points and Functional Entities defined in TS 185 003 [3] and TS 185 009 [4]. NOTE: The IPTV CND functions are described within the specification document reference TS 185 009 [4]. 4.1 Overview of IPTV CND Operating Modes and Reference Points There are 3 operating modes defined in TS 185 009 [4] and to be considered here. • Bridged mode: In this mode, the IPTV CND is working in compliance with TS 183 063 [2] and is connected to the NGN network or connects to the NGN via a CNG operating in bridged mode. In bridged mode of operation, the CNG provides only L1-L2 functionality. The CND connects over Gm to the NGN. • Routed mode: In this mode, the IPTV CND connects to the NGN via a CNG operating in routed mode and is capable to interact with other devices in the CPN with other protocols above L3. In routed mode of operation, the CNG includes routing and service layer functionality as well (L3 and above). The routed mode shall be related to an authentication session. A session operating in one of the following routed modes can only operate in one of them at the same time: - NGN mode: IPTV CND connects directly to the NGN through the CNG over Gm. The CNG-PCF and CNG-NFF as defined in TS 185 003 [3] may perform functionality such as NAPT and CNG internal QoS. - CPN mode: IPTV CND connects to the NGN through CNG over Gm'. The CNG-SIP Proxy B2BUA, CNG-ACF, CNG-PCF as defined in TS 185 003 [3] may perform functionality such as NAT/FW traversal, CNG internal QoS or IETF SIP to IMS SIP conversion. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 10 In the routed mode, e1' and e3' are sharing a similar procedure for routed NGN and routed CPN modes; e1' and e3' are therefore described in a common section for these two modes. On the other hand, interface C will have different procedures for these two modes and are therefore described in separate clauses.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
4.1.1 Bridged mode
|
Reference points Gm, Xc, Xd, Ut, Xa all conforms to TS 183 063 [2]. Reference point e1 conforms to TS 183 019 [12]. Reference point e3 conforms to TS 183 065 [11].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
4.1.2 Routed mode
|
Reference points Xc, Xd, Ut, Xa conforms to TS 183 063 [2]. The e1 reference point is described in clause 5. The e3 reference point is described in clause 6.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
4.1.2.1 Routed NGN mode
|
The C reference point is described in clause 14.1. The Gm reference point is described in clause 7.2.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
4.1.2.2 Routed CPN mode
|
The C reference point is described in clause 14.2. The Gm' reference point is described in clause 15.1.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
4.2 Data model information
|
Table 1 summarizes parameters to be provisioned in the CND, thanks to the CNGCF (reference point e3), through DHCP options (reference point e1') or by pre-configuration. Some kinds of data are grouped together, according to the SIP message types in which they are used: The table describes the data to be provisioned and some related information: • Entity responsible for the provisioning: the entity which is responsible for the provisioning in the TISPAN IMS network. In specific cases an entity can be responsible for the provisioning as a relay. This means that such an entity has been provisioned by another equipment during a previous phase (e.g. provisioning of the SDF Address through DHCP option 125 by the CNG in a routed NGN mode to the IPTV CND, while the CNG has been provisioned with this parameter by the CNGCF). • Requirement level: gives the level of the required parameter as it is mentioned in TISPAN specifications. This means that the table informs whether the parameter must or may be provisioned in the CND. Table 1 Data Description (ref) Entity responsible for the provisioning Parameters manageable by TR- 069/TR-104 Requirement level IMPI Authentication Username for IMS authentication CNGCF Yes Mandatory IMPU SIP URI CNGCF Yes Mandatory P-CSCF Address Host name or IP address of the SIP Proxy CNGCF or DHCP server Yes Mandatory ETSI ETSI TS 185 011 V2.1.1 (2009-07) 11 Data Description (ref) Entity responsible for the provisioning Parameters manageable by TR- 069/TR-104 Requirement level Registrar Server Host name or IP address of the SIP registrar server CNGCF Yes Mandatory Registration period Timer to send Register messages periodically CNGCF Yes Mandatory Vendor Class Id Device identifier Pre-configured Not applicable Optional IPTV service provider name (see note 1) service provider name CNGCF or DHCP server No Mandatory IPTV service provider domain name (see note 1) service provider domain name CNGCF or DHCP server No IPTV service provider URI (see note 1) service provider URI CNGCF, DNS SRV or DHCP server of the CNG (option 43 or 125), pre-configured not provisioned (S-CSCF routes the subscribe to the SDF) No Mandatory Service Discovery Server (see note 1) SDF Address CNGCF or DHCP server No Mandatory Content type identifier (see note 1) includes the content-type identifier that corresponds to the registered MIME type of XML documents representing application/vnd.etsi.iptvdiscovery+xml" Pre-configured Not applicable Mandatory Event header (see note 1) shall be set to the "ua-profile" event package Pre-configured Not applicable Mandatory UE Capabilities (see note 1) This defines the set of UE capabilities Pre-configured (sent via Subscribe/Notify) Not applicable Mandatory BC PSI (see note 2) well known PSI (Public Service Identifier) of the BC service (used by S-CSCF to route to the AS) Not defined (Not retrieved from SSF), it should be pre-configured Not applicable Mandatory Delay timer (see note 3) When the delay timer expires, the network shall be informed of the currently viewed channel with a SIP INFO message Not defined, it should be pre- configured Not applicable Optional BC PSI (see note 4) PSI (Public Service Identifier) of the BC service Not defined, it should be pre- configured Not applicable Mandatory NOTE 1: Parameters dedicated to the IPTV Service attachment, via Subscribe/Notify to the SDF. NOTE 2: Parameters dedicated to the IPTV Session initiation/modification, via Invite/Update for BC service. NOTE 3: Parameters dedicated to the Procedure for retrieving missing parameters before session initiation, via Option. NOTE 4: Parameters dedicated to the IPTV Session initiation/modification, via Invite/Update for CoD service. NOTE: The mention "Not applicable" in table 1 refers to the provisioning by pre-configuration, in case CWMP protocols are not used. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 12
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
5 Procedures at the e1 reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
5.1 IPTV-CND Operating in Bridged Mode
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
5.1.1 Procedures for Network Attachment
|
The IPTV-CND follows network attachment procedures over the e1 reference point as defined in TS 183 019 [12].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
5.1.2 Procedures for SDF Discovery
|
The IPTV-CND should use vendor class ("ETSI_TISPAN_IPTV_SDS") DHCP options 43/60 or DHCP options 124/125 to fetch addresses of SDF and associated service provider information during network attachment as per procedures defined in TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
5.1.3 Data model information
|
Table 2 summarizes the parameters which may be provisioned by the NGN network DHCP server or DNS SRV procedure to the IPTV-CND, through the e1 reference point. Table 2 Data Description (ref) P-CSCF Address Host name or IP address of the SIP Proxy IMS_IPTV_SP service provider name IMS-IPTV-SPDOMAIN service provider domain name IMS-IPTV-SDF SDF Address NOTE: Every parameters listed in table 2 can be provisioned in another way than by the DHCP procedures (see clause 4.2).
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
6 Procedures at the e3 reference point
|
6.1 IPTV-CND Operating in Bridged Mode and Routed NGN mode
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
6.1.1 Procedures for remote management
|
The IPTV-CND is remotely managed over the e3 reference point using the CPE WAN Management Protocol (CWMP) as described in TS 183 065 [11]. The IPTV-CND should support the device data model for remote management as defined by the Broadband Forum, the TR-135 [i.4] model for STB published in December 2007. Additionally, any relevant TR135 object extensions specified in TS 183 063 [2], ES 283 003 [9], TS 182 005 [8], TS 182 027 [1], TS 129 228 [10] and required to support IPTV Services should be supported, when they have to be provisioned by the CNGCF. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 13
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
6.1.2 Procedures for SDF Discovery
|
The IPTV-CND may be optionally provisioned with the addresses of the SDF server and associated service provider information by the CNGCF using the CWMP protocol over the e3 reference point. The procedures are as described in TS 183 063 [2]. NOTE: The exact format of the IPTV objects will be as specified by appropriate amendment to existing TR-135 specifications [i.4].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
6.1.3 Procedures for NAT traversal (applicable only in routed mode)
|
The NAT-traversal procedures described in the TR-069 specification Annex G [i.5] should be used to manage a CND through the CNG NAT.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
6.1.4 Data model information
|
Table 3 summarizes the parameters provisioned by the CNGCF to the IPTV-CND through the e3 reference point. Table 3 Data Description (ref) IMPI Authentication Username for IMS authentication IMPU SIP URI P-CSCF Address Host name or IP address of the SIP Proxy Registrar Server Host name or IP address of the SIP registrar server Registration period Timer to send Register messages periodically IPTV service provider name (see note) service provider name IPTV service provider domain name (see note) service provider domain name IPTV service provider (see note) service provider URI Service Discovery Server (see note) SDF Address NOTE: See clause I.4 "TR-069 Based Discovery" of TS 183 063 [2]. NOTE: Both P-CSCF Address and IPTV service provider URI can be provisioned in another way than by the CNGCF (see clause 4.2).
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7 Procedures at the Gm reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.1 IPTV-CND Operating in Bridged Mode
|
The procedures for IMS registration, Service Attachment, BC Service, CoD Service, IPTV Presence, BC with trick plays, NPVR Service and Service Configuration follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2 IPTV-CND Operating in Routed NGN Mode
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.1 Procedures for IMS Registration
|
Conforms to TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.2 Procedures for Service attachment
|
Conforms to TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.3 Procedures for BC service
|
Conforms to TS 183 063 [2]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 14
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.4 Procedures for CoD service
|
Conforms to TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.5 Procedures for Services Configuration
|
Conforms to TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.6 Procedures for IPTV Presence
|
Conforms to TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.7 Procedures for NPVR service
|
Conforms to TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.2.8 Procedures for NAT traversal
|
The CNG NAT-traversal may be performed using the P-CSCF functionalities described in TS 123 228 [13], annex G and RACS specified in ES 282 003 [14]. NOTE: The SIP ALG in the CNG-SIP Proxy B2BUA may be an alternative to the network-based NAT-traversal mechanism, in this case the CND should use the Gm' reference point.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
7.3 Data model information
|
To retrieve parameters provisioned through Gm reference point, see TS 183 063 [2], clause 5.2.2.3.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
8 Procedures at the Ut reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
8.1 IPTV-CND Operating in Bridged Mode
|
The procedures for managing service action data follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
8.2 IPTV-CND Operating in Routed NGN Mode
|
The procedures for managing service action data follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
8.3 Data model information
|
To retrieve parameters provisioned through Ut reference point, see TS 183 063 [2], annex C.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
9 Procedures at the Xa reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
9.1 IPTV-CND Operating in Bridged Mode
|
The procedures for service selection follow TS 183 063 [2]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 15
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
9.2 IPTV-CND Operating in Routed (NGN/CPN) Mode
|
The procedures for service selection follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
9.3 Data model information
|
To retrieve parameters provisioned through Xa reference point, see TS 183 063 [2], annex J.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
10 Procedures at the Xc reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
10.1 IPTV-CND Operating in Bridged Mode
|
The procedures for media control for CoD service and BC with trick plays follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
10.2 IPTV-CND Operating in Routed NGN Mode
|
The procedures for media control for CoD service and BC with trick plays follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
10.2.1 Procedures for NAT traversal
|
NOTE: NAT traversal support on Xc is out of the scope of the present document.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
10.3 IPTV-CND Operating in Routed CPN Mode
|
The procedures for media control for CoD service and BC with trick plays follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
11 Procedures at the Xd reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
11.1 IPTV-CND Operating in Bridged Mode
|
All procedures at this reference point follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
11.2 IPTV-CND Operating in Routed NGN Mode
|
The procedures for media delivery for CoD service, BC service, NPVR service and BC with trick play follow TS 183 063 [2].
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
11.2.1 Procedures for NAT traversal
|
To keep NAT bindings and firewall pinholes open with unidirectional RTP traffic early media (empty RTP packets) shall be sent by the IPTV CND so as to open CNG NAT pinholes before receiving media flows from the NGN. This is described in ES 283 003 [9], annex F.4a.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
11.3 IPTV-CND Operating in Routed CPN Mode
|
The procedures for media delivery for CoD service, BC service, NPVR service and BC with trick play follow TS 183 063 [2]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 16
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
11.3.1 Procedures for NAT traversal
|
NAT traversal for media delivery in CNG may be performed by the CNG - SIP Proxy B2BUA TS 185 010 [5] based on Gm' signalling. This mechanism performs a NAT binding between the IPTV CND receiver IP address (and port) and the NGN side CNG receiving port, for incoming media delivery. NOTE: The solution above works for CoD where Gm' signalling is used for each change of service. For broadcast services where IGMP is used there are situations without Gm' signalling. Therefore the use of an IGMP proxy is needed.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
12 Procedures at the e1' reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
12.1 IPTV-CND Operating in Routed (NGN/CPN) Mode
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
12.2 Procedures for network attachment
|
The e1' reference point serves the CND-AtF with appropriate configuration data to connect to a local IP network and attach to some selected services such as the P-CSCF. The protocol of choice is DHCP (RFC 2131 [15]). The DHCP options needed to implement this procedure are described in TS 185 010 [5]. In addition to these options, e1' serves to provide the IPTV CND with SDF discovery information. The procedure conforms to TS 183 063 [2], annex I to implement the related DHCP options. NOTE: Other methods to configure P-CSCF and SDF addresses exist, see clause 4.2.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
12.3 Data model information
|
In the case the IPTV-CND does not go through the CNG-SIP B2BUA (Routed NGN Mode), the IPTV-CND shall be provisioned with the following parameter. Table 4 Data Description (ref) Entity responsible for the provisioning P-CSCF Address Host name or IP address of the SIP Proxy CNG DHCP server (option 120)
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
12.4 CNG
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
12.4.1 Procedures for network attachment
|
When the IPTV CND is sending the DHCP request to the CNG including options to get SDF discovery information, the CNG should provide the requested information to the IPTV CND as described TS 183 063 [2], annex I. NOTE: Other methods to configure P-CSCF and SDF addresses exist, see clause 4.2.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
12.4.2 Data model information
|
In the case the IPTV-CND goes through the CNG-SIP B2BUA (Routed CPN Mode), the CNG has to be provisioned with the following parameters, so as to connect non-IMS CND to the IMS Network (e.g. replacing the CNG-SIP proxy Address by the P-CSCF Address). ETSI ETSI TS 185 011 V2.1.1 (2009-07) 17 Table 5 Data Description (ref) Entity responsible for the provisioning P-CSCF Address Host name or IP address of the SIP Proxy CNG DHCP server (option 120)
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
13 Procedures at the e3' reference point
|
NOTE: This clause is not elaborated in Release 2.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
14 Procedures at the C reference point
|
Utilization of reference point C in Release 2 for IPTV services is limited to three service offers: Broadcast, CoD and NPVR offers. In such a limited scope of offers, reference point C is only partially described within the present document. Routed NGN and Routed CPN modes can be used in parallel.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
14.1 IPTV-CND Operating in Routed NGN Mode
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
14.1.1 Procedures for Content description Functions
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
14.1.1.1 Procedures for Synchronization of Device List
|
The IPTV-CND PPF can collect available UPnP™ devices either at a regular interval (polling mode) or by listening to proper events (notification mode) in accordance with UPnP™ Device Architecture 1.0 (UPnP™ AV 1.0 Specifications, UPnP Forum [6]). This is done using M-SEARCH and NOTIFY messages.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
14.1.1.2 Procedures for Collecting Media List
|
The IPTV-CND PPF can collect available UPnP™ media items either at a regular interval (polling mode) or by listening to proper events (notification mode) in accordance with UPnP™ AV 1.0. This is done using UPnP AV messages. The IPTV-CND PPF should use UPnP™ AV CDS::Browse and CDS::Search actions to retrieve the list of media items proposed by an UPnP™ AV Media Server device. Those actions can be called at regular interval (polling mode) in order for the IPTV-CND PPF to refresh its media item lists. The IPTV-CND PPF can use the SystemUpdateID event to be notified when a change occurs in the whole list of items (change of the content or change of the metadata) of the UPnP™ AV Media Server. The IPTV-CND PPF may use (if implemented by the UPnP™ AV Media Server device) the ContainerUpdateID event to be notified of changes that occur on a container basis granularity. If an UPnP™ Media Server exposes itself as a DLNAVIRT Media Server, it means that it aggregates media items from other UPnP™ Media Server devices, as defined in DLNA 1.5 [7], clause 7.5.2 (DDC UPnP™ Device Description of Virtualized Device). The IPTV-CND PPF can then retrieve media items lists of several Media Servers at once by browsing/searching this DLNAVIRT device. The IPTV-CND PPF shall be compliant with DLNA 1.5 [7], clause 7.3.80 (MM CDS DLNA PlaySingle URI values) for access to the media item.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
14.1.1.3 Procedure for Exposing Media List
|
The IPTV-CND PPF can expose available UPnP media items. Three cases are possible: • Those media items can be locally stored within the device where the IPTV-CND PPF resides. The UPnP™ AV architecture is used. The Content Directory Service exposes the list of media items. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 18 • Those media items come from other devices in the home network. The IPTV-CND PPF then acts as an "aggregator" for those media items It can list those media items using DLNA Guidelines 1.5: - The IPTV-CND PPF exposes its DLNAVIRT device capability in its UPnP device description document, as defined in DLNA 1.5 [7], clause 7.5.2. (DDC UPnP Device Description of Virtualized Device). - The media item can have a <res> element: That points to the original media item in the original device where it is stored. In this case, the PlaySingle URI shall be used, as defined in DLNA 1.5 [7], clause 7.3.80 (MM CDS DLNA PlaySingle URI values). That points to a local media item. This is used to perform transformation on the media item to extend the rendering capabilities on other devices. • Those media items come from NGN (e.g. IPTV service coming from the NGN). The IPTV-CND PPF should be able to adapt the DVB formatted service selection data coming from the NGN into a format compliant with the UPnP™ AV.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
15 Procedures at the Gm' reference point
| |
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
15.1 IPTV CND Operating in Routed CPN Mode
|
In routed CPN mode the IPTV CND utilizes Gm' for SIP signalling with CNG-SIP Proxy B2BUA TS 185 010 [5]. The CNG-SIP Proxy B2BUA may perform NAT/FW-traversal and QoS management based on this signalling. Signalling conforms to TS 183 063 [2] with two limitations: • SIP messages shall be sent to the CNG-SIP Proxy B2BUA (discovery procedures as usual, e.g. DHCP, but not of the P-CSCF but instead discovery of the CNG-SIP Proxy B2BUA's IP address and port). Parameters such as SIP request URI, To headers etc. are as in TS 183 063 [2], e.g. the Public Service Identifier of the BC Service. • Signalling shall be unencrypted, otherwise CNG-SIP Proxy B2BUA cannot read it. Authentication is performed by the P-CSCF, i.e. CNG-SIP Proxy B2BUA keeps state of sessions, performs NAT-t and only acts when requests has been authorized by the IPTV Service Functions. A typical action would be to perform FW-opening, NAT-bindings and QoS management (CNG internal) after a successful SIP INVITE for IPTV media and control streams.
|
ecb85a7739eb1fdb3cacaea64cc5c9a3
|
185 011
|
16 Procedures at the au reference point
|
Procedures at the au reference point are as specified by TS 185 010 [5]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 19 17 Data to be provisioned in the IPTV-CND by pre-configuration This clause is dedicated to the pre-configured data, which are presented in table 6. Table 6 Data Description (ref) Vendor Class Id Device identifier IPTV service provider URI service provider URI Content type identifier includes the content-type identifier that corresponds to the registered MIME type of XML documents representing "application/vnd.etsi.iptvdiscovery+xml" Event header shall be set to the "ua-profile" event package UE Capabilities this defines the set of UE capabilities BC PSI well known PSI (Public Service Identifier) of the BC service (used by S-CSCF to route to the AS) Delay timer when the delay timer expires, the network shall be informed of the currently viewed channel with a SIP INFO message NOTE: The IPTV service provider URI can be provisioned in the IPTV-CND in another way than by pre-configuration (see clause 4.2), whereas the BC PSI and Delay Timer are assumed to be pre-configured, as no more information are given in the Network TISPAN specifications. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 20 Annex A (informative): Bibliography ETSI TS 185 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Devices architecture and interfaces and Reference Points". ETSI ETSI TS 185 011 V2.1.1 (2009-07) 21 History Document history V2.1.1 July 2009 Publication
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
1 Scope
|
The present document defines the stage 2 Customer Network Devices (CND) specifications, including architectural building blocks to be included in the Customer Network Devices to support the interworking with control plane NGN architecture, both for the transport layers (NASS, RACS) and for the service layer. The present document will also define the reference points between the NGN architectural blocks involved and the corresponding CNDs functions here defined (for the cases in what the CNG will be transparent for the service and control planes point of view), as well as between the Customer Network Devices and the CNG when appropriate. The present document will perform, as first step, a categorization of the different user equipment with reference to the type of service supported and the different levels of implementation of the related functionalities. Please note that in relation to the Customer Network Devices for IPTV usage the present document will cover only the classification step and will not provide any detail about the architecture and reference points. The IPTV CND are specified in TS 185 009 [i.1].
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
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. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
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] ETSI ES 282 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [2] ETSI TS 183 043: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification". [3] ETSI TS 182 012: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Subsystem; Functional architecture". [4] ETSI ES 283 003 "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified]". ETSI ETSI TS 185 006 V2.3.1 (2009-05) 7 [5] ETSI TS 185 005 "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services requirements and capabilities for customer networks connected to TISPAN NGN". [6] ETSI TS 185 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Network Gateway Architecture and Reference Points". NOTE: Available at http://www.homegateway.org. [7] DSL-Forum TR-069 Amendment 1: "CPE WAN Management Protocol". [8] DSL-Forum TR-104: "DSLHome Provisioning Parameters for VoIP CPE". [9] DSL Forum TR-106: " Data Model Template for TR-069-Enabled Devices". NOTE: Available at http://www.dslforum.org. [10] IETF RFC 3261: "SIP: Session Initiation Protocol". [11] ETSI ES 282 007 "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". [12] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [13] ETSI TS 183 019: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment; User-Network Interface Protocol Definitions". [14] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [15] ETSI TS 131 103: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Characteristics of the IP Multimedia Services Identity Module (ISIM) application (3GPP TS 31.103 version 7.3.0 Release 7)". [16] IETF RFC 2131: "Dynamic Host Configuration Protocol". [17] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 8.2.0 Release 8)".
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 185 009: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Architecture and reference points of a customer network device for IMS based IPTV services". [i.2] ETSI TS 187 001 (V2.1.5): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN SECurity (SEC); Requirements". [i.3] ETSI TR 187 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NAT traversal feasibility study report". [i.4] ETSI TR 185 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Analysis of protocols for customer networks connected to TISPAN NGN". ETSI ETSI TS 185 006 V2.3.1 (2009-05) 8 [i.5] ETSI TR 182 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Organization of user data".
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
3 Definitions and abbreviations
| |
d20cee83487b776a4bad5c032873a036
|
185 006
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: CPN Device: device that is physically installed in the CPN allowing user access to network services; this can be a Customer Network Gateway with gateway functionalities towards the NGN, or a Customer Network Device being the end user terminal Customer Network Device (CND): CPN device enabling the final user to have direct access to services through a specific user interface NOTE 1: CNDs can be dedicated to the internet, conversational and audio-video services. But they could be also Consumer Electronics equipment and other devices which may have nothing to do with these premium services (e.g. services performing a content sharing within a CPN, typically between a PC and a music system). CND classification is reported in clause 4. NOTE 2: For CND classifications see clause 4. Customer Network Gateway (CNG): CPN device acting as a gateway between the CPN and the NGN NOTE: CNG is able to perform networking functions from physical connection to bridging and routing capabilities (L1-L3), but also possibly implementing functions related to the service support (up to L7). Customer Premises Network (CPN): in-house network composed by customer network gateway, customer network devices, network segments, network adapters and nodes NOTE: Network segments are physical wired or wireless connections between customer premises network elements); network adapters are elements performing a L1/L2 conversion between different network segments; nodes are network adapters with L3 routing capabilities. "Multiple" Play Services (can be: double, triple, quadruple, etc.): delivery by a single service provider of different types of concurrent services to one or multiple users within the same CPN NOTE: Services can be categorized in the following way: data (e.g. Web browsing, best effort traffic, etc.), person(s) to person(s) communication, entertainment.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AKA Authentication and Key Agreement B2BUA Back to Back User Agent C-BGF Core Border Gateway Function CND Customer Network Device CND-A CND-client Application CND-AtF CND-Attachment Function CND-CMF CND-Configuration and Management Function CND-CSMF CND-Communication Services Media Function CND-LAF CND-Local Authentication Function CND-NASS Customer Network Devices- Network Attachment SubSystem CND-NTF CND-NAPT Traversal Function CND-PPF CND-Plug and Play Function CND-SC CND-Self Configuration CND-SF Customer Network Devices - Service related Functional entities CND-SIP UA CND-SIP User Agent ETSI ETSI TS 185 006 V2.3.1 (2009-05) 9 CNG Customer Network Gateway CNG-ACF CNG-Admission Control Function CNG-AtF CNG Attachment Function CNG-AuF CNG Authentication Function CNGCF Customer Network Gateway Configuration Function CNG-CMF CNG Configuration and Management Function CNG-LF CNG Location Function CNG-NFF CNG NAPT and Firewall Function CNG-PCF CNG Policy Control Function CNG-PPF CNG Plug and Play Function CNG-UIF CNG User reference point Function CPN Customer Premises Network DB DataBase DHCP Dynamic Host Configuration Protocol FXS Foreign eXchange Subscriber IM CN IP Multimedia Core Network IMPU IMS Public User identifier IMS IP Multimedia Subsystem IP-PBX Internet Protocol - Private Branch eXchange IPTV Internet Protocol TeleVision ISDN Integrated Services Digital Network ISIM IP Multimedia Services Identity Module LAN Local Area Network MG Media Gateway NAPT Network Address and Port Translation NAS Network Attached Storage NASS Network Attachment SubSystem NAT Network Address Translation NBA NASS Bundled Authentication NGN Next Generation Network NTF NAPT Traversal Function NW NetWork P-CSCF Proxy Call Session Control Function PDA Personal Digital Assistant PES PSTN/ISDN Emulation Sub-system PLC Power Line Communication POTS Plain Old Telephone Service PSTN Public Switched Telephone Network RA Remote Access RACS Resource and Admission Control Sub-system SDP Session Description Protocol SIP Session Initiation Protocol SSID Service Set Identifier STB Set Top Box UA User Agent UE User Equipment UICC Universal Integrated Circuit Card UPNP Universal Plag aNd Play UPSF User Profile Server Function URI Uniform Resource Identifier URL Uniform Resource Locator USIM Universal Subscriber Identity Module WAN Wide Area Network
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4 Customer Network Device (CND) classification
|
The Customer Network Devices connected to the Customer Premises Network can be of different types. The services supported from each CND depend of the CND's type. In this clause a macro-classification is given. More in general, in a customer premises network End Devices used by end user, Network Devices to support the CPN infrastructure and Gateway Devices to connect the Customer Premises Network to the NGN are present. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 10 End Devices: The end devices can be divided into two main categories: non-IMS capable and IMS capable. 1) Non-IMS capable devices: - non-IP device: It can be a POTS (Plain Old Telephone Service) phone that support traditional voice services and STS (Supplementary Telephone Services) services. It can be connected to the NGN through the CNG (e.g. in case of PSTN simulation services) or without the CNG (e.g. PSTN emulation services); it supports the Z interface. It can be a common ISDN phone supporting the S/T interfaces or also a DECT phone. - IP device: It is a generic IP based device without any SIP stack. For example: PC, Personal Digital Assistant (PDA), network printer, Network Attached Storage (NAS), IP-PBX. In some cases IP devices, such as a PC or PDA, can evolve in an easy way to IMS capable devices. - SIP Device: It is an IP device with a SIP stack not compliant with ES 283 003 [4] e.g. ietf based RFC 3261 [10]. For example Videophone, PDA, STB. - Consumer Electronics: There are a number of consumer electronics equipment that can be connected to the CPN and they can be IP based or not. Some examples are the Set Top Box (STB), gaming console, Network Attached Storage (NAS). These devices in some cases do not need a connection with WAN side and are used for Intra-Customer Environment services. - Mobile Device: It can be a 2G/3G mobile device that takes part into CPN through a wireless local access (mobility enable) offered by CNG. 2) IMS capable device: An IMS capable device is able to register with the IM CN via exchange of SIP messages with the P-CSCF, and then create/accept/end multimedia IP sessions, in compliance with ES 283 003 [4]. The establishment of a trust relationship to the IM CN shall be by one of the 3 methods defined in ES 283 003 [4] (by ISIM, or if that is not present then by USIM, or if that is not present then by device-internal transmission of a private user identity, a public user identity and a home network domain name). For authentication issues, see also clause 6. - Fixed device: It can be a fixed corded phone, dual mode phone (equipped with 2G/3G and Wi-Fi/Bluetooth), PC, PDA (with IMS client soft phone), IP-PBX. The dual mode phone (mobile + wireless) is considered as a fixed device when it is attached by Wi-Fi/Bluetooth. - Mobile device: It can be a mobile phone or a PC/PDA with 2G/3G interface. - Consumer Electronics: They can be a STB, Media Servers or media players, etc. Network Device: It is a device that can be connected to the CPN infrastructure (e.g. network adapter and nodes as defined in clause 3). Gateway: CNG: It is the Customer Network Gateway to access the NGN side, as specified in TS 185 003 [6]. Table 4.1 classifies the customer devices in order to support the use case define in TS 185 005 [5]. Moreover the CNDs are related to a number of possible local physical interfaces: FXS, Ethernet, Wireless (with or without mobility), where mobility is defined as service and session continuity independently from the location. In case of wired local access, both analogue and digital access are considered. Wired digital includes Ethernet and other technologies. In table 4.1 the "X" means that the CND may be able to support a service or that local physical interface. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 11 Table 4.1: Customer Network Devices classification Device Services CPN interfaces Customer Network Device Type Communi- cation service Data service Video Streaming Presence Messaging Intra- Customer Environment Wired analogue Wired digital Wireless not enabling mobility Wireless enabling mobility Non IMS capable Non IP (e.g., POTS, ISDN phone) X X X X IP (e.g. PC, PDA, IP-PBX, NAS, Printer) X X X X SIP (e.g. VideoPhone, PDA, STB) X X X X X X Consumer Electronics (e.g. STB, gaming console, NAS) X X X X Mobile 2G/ 3G Phone X X X IMS capable Fixed (e.g. Fixed phone, multi mode phone, PC, PDA (with IMS client soft phone), IP-PBX) X X X X X X X X X Mobile (mobile phone, PC/PDA with 2G/3G itf X X X X X X X Consumer Electronics (e.g. STB, etc.) X X X X The CNDs related to IP-TV are specified in TS 185 009 [i.1].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.