BS EN 62766-4-1:2017:2018 Edition
$243.87
Consumer terminal function for access to IPTV and open internet multimedia services – Protocols
| Published By | Publication Date | Number of Pages |
| BSI | 2018 | 354 |
IEC 62766-4-1:2017(E) specifies the protocols, which apply to the following reference point interfaces identified in the architecture described in Annex B of IEC 62766-1:2017. – The UNI interfaces, between the consumer domain and the network or service provider domains. – The HNI interfaces, between the functional entities in the consumer network domain. – Interfaces to external systems, which include DLNA networks in the consumer domain.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 4 | CONTENTS |
| 16 | FOREWORD |
| 18 | INTRODUCTION |
| 19 | 1 Scope 2 Normative references |
| 24 | 3 Terms, definitions and abbreviations 3.1 Terms and definitions |
| 25 | 3.2 Abbreviated terms 4 Interface definitions 4.1 Consumer network to provider network interfaces (UNI) |
| 26 | Tables Table 1 – UNI reference points and protocols |
| 27 | 4.2 Provider network reference points description Table 2 – Other interfaces |
| 28 | Table 3 – NPI reference points and protocols |
| 30 | 4.3 Interfaces to external systems, consumer network 5 Structure of this document Table 4 – External interfaces from the consumer network |
| 31 | 6 HTTP 6.1 HTTP reference points |
| 32 | 6.2 IG as a protocol converter supporting the HNI-IGI interface – HTTP option 6.3 Protocols for IPTV service functions 6.3.1 Multicast content streaming with SIP session management protocol over HNI-IGI – HTTP option |
| 35 | Table 5 – Supported HTTP extension headers in the HNI-IGI INVITE request message for multicast content service session setup (OITF–>IG) |
| 36 | Table 6 – Supported HTTP extension headers in the response message to an HNI-IGI INVITE request message for multicast content service session setup (IG–>OITF) Table 7 – Supported HTTP extension headers in the HNI-IGI ACK message for a successful multicast content service session setup (OITF–>IG) |
| 38 | Table 8 – Supported HTTP extension headers in HNI-IGI BYE request for teardown of a multicast content streaming session (OITF–>IG) Table 9 – Supported HTTP extension headers in the response to an HNI-IGI BYE request for teardown of a multicast content streaming session (IG–>OITF) |
| 40 | Table 10 – Supported HTTP extension headers in the HNI-IGI SIP INFO request message for content reporting (OITF–>IG) Table 11 – Supported HTTP extension headers in the response message to an HNI-IGI INFO request message for content reporting (IG–>OITF) |
| 41 | Table 12 – List of HTTP extension headers for an incoming SIP UPDATE (IG–>OITF) Table 13 – Supported HTTP extension headers in the response message to an incoming HNI-IGI SIP UPDATE request message (OITF–>IG) |
| 44 | 6.3.2 Unicast content streaming with SIP session management |
| 45 | Table 14 – Supported HTTP extension headers in HNI-IGI OPTION request for unicast content streaming session setup parameters (OITF–>IG) Table 15 – Supported HTTP extension headers in the response to an HNI-IGI OPTION request for unicast content streaming session setup parameters |
| 49 | Table 16 – Supported HTTP extension headers in HNI-IGI INVITE request for unicast content streaming session setup (OITF–>IG) |
| 50 | Table 17 – Supported HTTP extension headers in the response to an HNI-IGI INVITE request for unicast content streaming session setup (IG–>OITF) Table 18 – Supported HTTP extension headers in HNI-IGI ACK request for successful unicast content streaming session teardown (OITF–>IG) |
| 51 | Table 19 – Supported HTTP extension headers in HNI-IGI BYE request for unicast content streaming session teardown (OITF–>IG) Table 20 – Supported HTTP extension headers in the response to an HNI-IGI BYE request for unicast content streaming session teardown (IG–>OITF) |
| 52 | 6.3.3 Forced play-out control with SIP session management – Protocol for forced play-out control over HNI-IGI 6.3.4 Content download 6.3.5 Purchase of digital media service using SIP |
| 53 | Figures Figure 1 – Elements of OIPF extended RelatedMaterialType Figure 2 – Construction of advertising window using (x, y, w, h) in Position_Size element |
| 54 | Figure 3 – Overlaying the content with advertisement for related media |
| 55 | Table 21 – Supported HTTP extension headers in the HNI-IGI SIP INFO request message for Digital-Media-Purchase (OITF–>IG) Table 22 – Supported HTTP extension headers in the response message to an HNI-IGI INFO request message for Digital-Media-Purchase (IG–>OITF) |
| 56 | Table 23 – List of HTTP extension headers for an incoming SIP UPDATE (IG–>OITF) Table 24 – Supported HTTP extension headers in the response message to an incoming HNI-IGI SIP UPDATE request message (OITF–>IG) |
| 57 | Table 25 – Mandatory HTTP headers in the request message for advertisement of digital media (OITF(IPTV Metadata control FE) Table 26 – Mandatory HTTP headers in the response message for advertisement of digital media (IPTV Metadata control FE–>OITF) |
| 59 | 6.3.6 Pay per view multicast content service with SIP session managementprotocol over HNI-IGI – HTTP option |
| 60 | 6.3.7 Parental control for content using SIP |
| 61 | Table 27 – Supported HTTP extension headers in HNI-IGI SUBSCRIBE request for the parental control watched content event package |
| 62 | Table 28 – Supported HTTP extension headers in the response to an HNI-IGI SUBSCRIBE request for the parental control watched content event package Table 29 – Supported HTTP extension headers in the NOTIFY request containing changes in the watched programme (IG–>OITF) Table 30 – Supported HTTP extension headers in the response to a NOTIFY request (OITF–>IG) |
| 65 | Table 31 – Supported HTTP extension headers in the MESSAGE request for parental control (OITF–>IG) Table 32 – Supported HTTP extension headers in the response message to a MESSAGE request message for parental control (IG–>OITF) |
| 66 | Table 33 – Supported HTTP extension headers in the MESSAGE request for parental control (IG–>OITF) |
| 68 | 6.3.8 Network-based user notification services |
| 69 | Table 34 – List of HTTP extension headers for an outgoing SIP MESSAGE for setting up a user notification request (OITF–>IG) Table 35 – List of HTTP extension headers for the response to an outgoing SIP MESSAGE for setting up a user notification request (IG–>OITF) |
| 71 | 6.3.9 Content bookmarking |
| 73 | Table 36 – Supported HTTP extension headers for an incoming SIP INFO (IG–>OITF) |
| 74 | Table 37 – Supported HTTP extension headers in the response message to an incoming HNI-IGI SIP INFO (OITF–>IG) |
| 76 | Table 38 – Supported HTTP extension headers in the HNI-IGI SIP INFO request message for content bookmark (OITF–>IG) Table 39 – Supported HTTP extension headers in the response message to an HNI-IGI INFO request message for content bookmark (IG–>OITF) |
| 77 | Table 40 – List of HTTP extension headers for an incoming SIP UPDATE (IG–>OITF) Table 41 – Supported HTTP extension headers in the response message to an incoming HNI-IGI SIP UPDATE request message (OITF–>IG) |
| 79 | 6.3.10 Local PVR service usig SIP |
| 81 | Table 42 – List of HTTP extension headers for PVR service capture request message (OITF–>IG) Table 43 – List of HTTP extension headers for the response to PVR service capture request and PVR record request message (IG(OITF and OITF–>IG) |
| 82 | Table 44 – List of HTTP extension headers for the PVR record request (IG–>OITF) |
| 84 | 6.3.11 Network PVR (nPVR) using SIP |
| 85 | Table 45 – List of HTTP extension headers for the PVR record request (IG–>OITF) |
| 86 | 6.3.12 Personalised channel |
| 87 | 6.3.13 Session transfer with SIP session management |
| 91 | Table 46 –HTTP extension headers for SIP REFER |
| 92 | Table 47 –HTTP extension headers SIP REFER response |
| 93 | Table 48 –HTTP extension headers in the NOTIFY request Table 49 –HTTP extension headers in the NOTIFY response |
| 94 | 6.4 Protocol for service access and control functions 6.4.1 Service provider discovery |
| 97 | Table 50 – Supported HTTP extension headers in HNI-IGI SUBSCRIBE request for SP discovery |
| 98 | Table 51 – Supported HTTP extension headers in the response to an HNI-IGI SUBSCRIBE request for SP discovery Table 52 – Supported HTTP extension headers in the NOTIFY request to the SUBSCRIBE to SP discovery Table 53 – Supported HTTP extension headers in the response to a NOTIFY request to the SUBSCRIBE to SP discovery |
| 99 | 6.4.2 Service discovery 6.4.3 Service access |
| 100 | 6.4.4 Subscription profile management and usage |
| 103 | Table 54 – Supported HTTP extension headers in HNI-IGI SUBSCRIBE request for receiving notification of changes in the IPTV service profile Table 55 – Supported HTTP extension headers in the response to an HNI-IGI SUBSCRIBE request |
| 104 | Table 56 – Supported HTTP extension headers in the NOTIFY request containing changes in the IPTV service profile Table 57 – Supported HTTP extension headers in the response to a NOTIFY request |
| 105 | 6.4.5 Remote management Table 58 – RPC methods |
| 106 | Table 59 – RPC method parameters |
| 107 | Figure 4 – Sequence for the configuration of an IG |
| 110 | 6.4.6 User registration and network authentication |
| 113 | Table 60 –Mandatory HTTP extension headers for user registration/de-registration (OITF–>IG) |
| 114 | Table 61 –HTTP extension headers for user registration/de-registration response (IG–>OITF) |
| 115 | Table 62 – Supported HTTP extension headers in the HNI-IGI SUBSCRIBE request for the registration event package |
| 116 | Table 63 – Supported HTTP extension headers in the response to an HNI-IGI SUBSCRIBE request for the registration event package Table 64 –HTTP extension headers for a HNI-IGI NOTIFY request sent IG–>OITF Table 65 –HTTP extension headers in the response to a NOTIFY request |
| 121 | 6.5 Protocols for communications functions using SIP 6.5.1 CallerID Table 66 –HTTP extension headers for an instant message based caller ID (IG–>OITF) |
| 122 | Table 67 –HTTP extension headers for the response to an Instant message based caller ID (OITF–>IG) |
| 123 | 6.5.2 Instant messagingProcedure for instant messaging on HGI-INI – HTTP option Table 68 –HTTP extension headers on the HNI-IGI interface (IG–>OITF) for a received SIP INVITE Table 69 –HTTP extension headers on the HNI-IGI interface (OITF–>IG) for a response to the SIP INVITE Table 70 –HTTP headers in the HNI-IGI ACK message (IG–>OITF) |
| 124 | Table 71 –HTTP extension headers for an outgoing instant message (OITF–>IG) Table 72 –HTTP extension headers for the response to an outgoing and incoming Instant message (IG(OITF and OITF–>IG) |
| 125 | 6.5.3 IM session (chat using MSRP) Table 73 – List of HTTP extension headers for an incoming instant message (IG–>OITF) |
| 127 | Table 74 –HTTP extension headers for IM INVITE request (OITF–>IG) Table 75 –HTTP extension headers for a 200 OK response received for the INVITE IG–>OITF |
| 128 | Table 76 – List of HTTP extension headers in HNI-IGI ACK request |
| 129 | Table 77 –HNI-IGI HTTP extension headers for an MSRP SEND request (OITF–>IG) Table 78 –HNI-IGI HTTP extension headers included in the HTTP 200 OK response (IG–>OITF) |
| 130 | Table 79 –HNI-IGI HTTP extension headers for an MSRP SEND ACTIVITY request (OITF–>IG) Table 80 –HNI-IGI HTTP extension headers for an incoming MSRP message (IG–>OITF) Table 81 –HNI-IGI HTTP extension headers for an MSRP 200 OK response to an incoming MSRP message (OITF–>IG) |
| 131 | Table 82 –HNI-IGI HTTP extension headers for an incoming MSRP receive activity (IG–>OITF) |
| 132 | Table 83 –HTTP extension headers for an MSRP BYE request (OITF–>IG) Table 84 –HTTP extension headers for a 200 OK response to a BYE (IG–>OITF) |
| 133 | Table 85 –HTTP extension headers for an incoming SIP BYE (IG–>OITF) Table 86 –HTTP extension headers for the response to an SIP BYE (OITF–>IG) |
| 135 | Table 87 –HTTP extension headers for an incoming IM INVITE request (IG–>OITF) Table 88 – List of HTTP extension headers for the response to an incoming IM INVITE request (OITF–>IG) |
| 136 | 6.5.4 Presence Table 89 – Supported HTTP extension headers in HNI-IGI ACK request for successful IM session (MSRP chat) (IG–>OITF) |
| 138 | Table 90 –HTTP extension headers for a SUBSCRIBE request (OITF–>IG) Table 91 –HTTP extension headers for the response to a SUBSCRIBE to presence (IG–>OITF) |
| 139 | Table 92 –HTTP extension headers for a SIP NOTIFY (IG–>OITF) Table 93 – List of HTTP extension headers for a response to a received SIP NOTIFY (OITF–>IG) |
| 140 | Table 94 –HTTP extension headers for the PUBLISH request (OITF–>IG) |
| 141 | 6.5.5 Content sharing Table 95 –HTTP extension headers for a response to SIP PUBLISH (IG–>OITF) |
| 143 | Table 96 –HTTP extension headers on the HNI-IGI interface (OITF–>IG) for a SIP OPTIONS request and response (IG–>OITF) |
| 144 | Table 97 –HTTP extension headers on the HNI-IGI interface (OITF–>IG) for a SIP INVITE request |
| 145 | Table 98 –HTTP extension headers for a 200 OK response received for the INVITE IG–>OITF Table 99 –HTTP extension headers in HNI-IGI ACK request |
| 147 | Table 100 –HTTP extension headers for SIP REFER |
| 148 | Table 101 – Supported HTTP extension headers in the NOTIFY request sent from the transferee OITF (OITF->IG) to the transferor (IG->OITF) |
| 150 | Table 102 –HTTP extension headers for a SIP BYE request (OITF–>IG) |
| 151 | 6.6 Protocols system infrastructure functionsOITFIG interface (HNIIGI) 6.6.1 HNI-IGI message types Table 103 –HTTP extension headers for a 200 OK response to a BYE (IG–>OITF) |
| 152 | 6.6.2 HNI-IGI messages in the OITF to IG direction – HTTP option Table 104 – HNI-IGI message types |
| 153 | Table 105 – X-OITF HTTP extension headers and IG actions for OITF–>IG messages |
| 154 | 6.6.3 HNI-IGI messages in the IG to OITF direction – HTTP option Table 106 – Mapping of SIP header to X-OITF HTTP extension headers in IG–>OITF |
| 155 | 6.6.4 HNI-IGI PENDING_IG message – HTTP option |
| 156 | 6.6.5 HNI-IGI SIP message – HTTP option 6.6.6 HNI-IGI auxiliary message |
| 157 | 6.6.7 HNI-IGI message body – HTTP option 6.6.8 Guidelines for applications using the HNI-IGI interface – HTTP option 6.6.9 Error recovery in the IG – HTTP option |
| 158 | 6.7 Protocols for content preparation 6.7.1 Reference points NPI-45, NPI-46, NPI-CSPT3 and NPI-CSPG3 |
| 159 | Table 107 – Reference points calling entity and called entity Table 108 – Operations according to functional entity roles |
| 160 | Figure 5 – GetKeyScheduleSignalingrequest schema Table 109 – getKeyScheduleSignaling method parameters |
| 161 | Table 110 – GetKeyScheduleSignalingrequestType |
| 162 | Figure 6 – GetKeyScheduleSignalingresponse schema |
| 163 | Table 111 – GetKeyScheduleSignalingresponseType |
| 164 | Table 112 – setScheduleAndGetKeySignaling method parameters |
| 165 | Figure 7 – SetScheduleAndGetKeySignalingrequest schema Table 113 – SetScheduleAndGetKeySignalingrequestType |
| 166 | Figure 8 – SetScheduleAndGetKeySignalingresponse schema |
| 167 | Table 114 – SetScheduleAndGetKeySignalingresponseType |
| 168 | Table 115 – setKeyScheduleAndGetSignaling method parameters |
| 169 | Figure 9 – SetKeyScheduleAndGetSignalingrequest schema Table 116 – SetKeyScheduleAndGetSignalingrequestType |
| 170 | Figure 10 – SetKeyScheduleAndGetSignalingresponse schema |
| 171 | Table 117 – SetKeyScheduleAndGetSignalingresponseType |
| 172 | Table 118 – UUIDType Table 119 – StatusType Table 120 – ContentKeyType structure |
| 173 | Table 121 – DrmInfoType structure Table 122 – DrmMetadataType structure Table 123 – DrmSignalingType structure |
| 174 | Table 124 – DashSignalingType structure Table 125 – EncryptionprofileType structure |
| 175 | Table 126 – KeyIdScheduleType structure Table 127 – PregenerationWindowType structure Table 128 – PrivateSignalingType structure |
| 176 | Table 129 – ScheduledKeyType structure |
| 177 | Table 130 – ScheduleType structure Table 131 – TimeReferenceType structure |
| 178 | 6.7.2 XML schema for content preparation |
| 183 | 7 SIP and SIP/SDP 7.1 General |
| 184 | 7.2 SIP/SDP reference points within the provider network 7.2.1 General 7.2.2 Generic handling for SIP requests/responses 7.2.3 Protocols for IPTV service functions |
| 200 | Table 132 –SIP headers for PVR service recording status (CC(IPTV Control) |
| 202 | Table 133 –SIP headers for PVR service recording status (CC(IPTV Control) |
| 206 | 7.2.4 Protocols for service access and control functions |
| 208 | 7.2.5 Protocols for communication services using SIP CallerIDProcedures for caller ID on UNIS-8 |
| 210 | 7.3 SIP/SDP reference points within the residential network 7.3.1 General 7.3.2 IG as a B2BUA |
| 211 | 7.3.3 Protocols for IPTV service functions |
| 222 | 7.3.4 Protocols for service access and control functions |
| 226 | 7.3.5 Protocols for communication services using SIP |
| 233 | Table 134 – Supported SIP headers in the HNI-IGI INVITE request message for an outgoing MM telephony session setup (OITF–>IG) Table 135 – Supported SIP headers in the response message to an HNI-IGI INVITE request message for an outgoing MM telephony session setup (IG–>OITF) |
| 234 | Table 136 – Supported SIP headers in the HNI-IGI ACK message for a successful MM telephony session setup (OITF–>IG) Table 137 – Supported SIP headers in the HNI-IGI INVITE request message for an incoming MM telephony session setup (IG–>OITF) |
| 235 | Table 138 – Supported SIP headers in the response message to an HNI-IGI INVITE request message for an incoming MM telephony session setup (OITF–>IG) Table 139 – Supported SIP headers in the HNI-IGI ACK message for a successful incoming MM telephony session setup (IG–>OITF) |
| 236 | Table 140 – List of SIP headers for an outgoing SIP BYE (OITF–>IG) Table 141 – List of SIP headers for the response to an outgoing SIP BYE (IG–>OITF) Table 142 – List of SIP headers for an incoming SIP BYE (IG–>OITF) |
| 237 | 8 RTSP 8.1 General Table 143 – List of SIP headers for the response to an incoming SIP BYE (OITF–>IG) |
| 238 | 8.2 Protocols for IPTV service functions 8.2.1 Use of RTSP for unicast content streaming services |
| 245 | 8.2.2 Use of RTSP for forced play-out controlRTSP for managed model over UNIS-11 and NPI-10 |
| 246 | 8.2.3 Use of RTSP for network PVR (nPVR) 8.2.4 Use of RTSP for personalized channel |
| 247 | 8.2.5 Content streaming post-session transfer 8.3 Protocols for service access and controlPerformance monitoring over UNIT-18 |
| 250 | 9 IGMP and multicast protocol 9.1 General |
| 251 | 9.2 Protocols for IPTV service functions 9.2.1 Multicast content streaming service on UNIS-13 9.2.2 Pay-per-view multicast content service with SIP session management 9.2.3 nPVRProtocol over NPI-40 9.2.4 Network-generated notification service |
| 252 | 9.2.5 Emergency notification service 9.3 Protocols for service access and control functions 9.3.1 Service discovery and Content Selection 9.3.2 Remote management – protocol over UNI-RMS 9.4 Protocols for system infrastructure functions – interactive application delivery – protocol over UNIS-6 and UNIS-12 |
| 253 | 10 RTP/RTCP 10.1 General 10.2 Protocols for IPTV service functions 10.2.1 Multicast content streaming service 10.2.2 Unicast content streaming service 10.2.3 nPVRProtocol over NPI-41 10.3 Service access and control – Performance monitoring over UNIT-18 |
| 254 | 10.4 Application-layer forward error correction 10.5 Application-layer retransmission (RET) 10.5.1 General 10.5.2 Protocol over UNIT-17 |
| 255 | 10.5.3 Protocol over UNIT-18 10.6 Fast channel change (FCC) 10.6.1 General 10.6.2 Protocol over UNIT-17 10.6.3 Protocol over UNIT-18 10.7 Protocols for multimedia telephony services – protocol over UNIT-17 10.7.1 General 10.7.2 RTP payload formats for video streams 10.7.3 RTP payload formats for audio streams |
| 256 | 11 UPnP protocols for system infrastructure functions – UPnP discovery 11.1 General 11.2 Procedure for IG discovery 11.2.1 Discovery sequence 11.2.2 urn:oipf-org:device:ig:1 device definitions 11.2.3 IG description Table 144 – urn:oipf-org:device:ig:1 deviceType |
| 257 | Figure 11 – IG description XML schema |
| 258 | Table 145 – igDescription elements and attributes |
| 259 | 11.3 Procedure for AG discovery 11.3.1 Discovery sequence 11.3.2 urn:oipf-org:device:ag:1 device definitions 11.3.3 AG description Table 146 – urn:oipf-org:device:ag:1 deviceType |
| 260 | 11.4 Procedure for CSPG-DTCP discovery 11.4.1 Discovery sequence 11.4.2 urn:oipf-org:device:cspg-dtcp:1 device definitions Table 147 – agDescription elements and attributes Table 148 – urn:oipf-org:device:cspg-dtcp:1 deviceType |
| 261 | 11.4.3 CSPG-DTCP description Table 149 – cspgdtcpDescription elements and attributes |
| 262 | 11.5 Procedure for OITF discovery 11.5.1 Discovery sequence 11.5.2 OITF description 12 DLNA function 13 DHCP 13.1 General Table 150 – urn:oipf-org:device:oitf:1 deviceType |
| 263 | 13.2 Protocols for system infrastructure functions – network attachment 13.2.1 General 13.2.2 DHCP option usage |
| 265 | 14 UDP for IPTV service functions 14.1 Multicast content streaming service – protocol over UNIT-17 14.2 Unicast content streaming service – Protocol over UNIT-17 14.3 nPVR – protocol over NPI-41 15 FLUTE 15.1 General |
| 266 | 15.2 Protocols for IPTV service Functions 15.2.1 Emergency notification 15.2.2 Network-generated notification 16 Diameter 16.1 General 16.2 Protocols for IPTV service functions – Purchase of digital media – Protocol over NPI-11 |
| 267 | Annexes Annex A (informative)Example messages A.1 IPTV service functions message examples – Unicast content streaming session setup with SIP session management Figure A.1 – COD session setup sequence |
| 271 | A.2 Communication services message examples – HNI-IGI message mapping to SIP A.2.1 General |
| 272 | A.2.2 Presence |
| 277 | A.2.3 Chat |
| 281 | A.2.4 Presence document |
| 282 | Annex B (informative)User profile description B.1 IPTV subscription profile B.1.1 General B.1.2 XML Schema for the IPTV subscription profile |
| 287 | B.2 XML schema for the OIPF profile |
| 292 | B.3 IPTV subscription profile elements classification B.3.1 General B.3.2 User visible and manageable data B.3.3 User visible, but not manageable data |
| 293 | B.3.4 Data neither visible nor manageable by the user |
| 294 | Annex C (normative)Mapping attributes for scheduled content C.1 Mapping SDP attributes from DVB SD&S information Table C.1 – Definition of names |
| 296 | C.2 Service package SDP attributes |
| 297 | Annex D (normative) names Table D.1 – Definition of names |
| 298 | Annex E (normative)System infrastructure E.1 OITF start-up high-level procedures E.1.1 OITF with native HNI-IGI support |
| 299 | E.1.2 OITF with non-native HNI-IGI support Figure E.1 – High-level start-up procedural flow for an OITF with native HNI-IGI support |
| 300 | E.1.3 Integrated OITF/IG with no HNI-IGI support Figure E.2 – High-level start-up procedural flow for an OITF without native HNI-IGI support |
| 301 | E.2 High-level procedure for an OITF graceful shut-down in network relying on IMS Figure E.3 – High-level start-up procedural flow for an integrated OITF/IG |
| 302 | E.3 OITF restart high-level procedures for an IG integrating WAN GW Figure E.4 – High-level shut-down procedural flow for an OITF |
| 303 | Figure E.5 – Overview of OITF start-up |
| 304 | E.4 IG start-up and shutdown procedures E.4.1 IG start-up procedures E.4.2 IG shutdown procedures Figure E.6 – Overview of OITF restart |
| 305 | E.5 WAN Gateway functions E.5.1 General E.5.2 NAT traversal E.5.3 NAT traversal for SIP-based services |
| 306 | Figure E.7 – NAT traversal with UDP keep alive messages |
| 307 | E.5.4 NAT traversal and keep-alive messages for unicast content streaming services Figure E.8 – NAT traversal with SIP keep alive messages |
| 309 | Annex F (informative)System infrastructure mechanisms – NAT-T informational flows for IPTV services with SIP session management F.1 General F.2 IG and WAN GW in one physical device Figure F.1 – Protocol flows for IG and WAN GW in one device |
| 310 | Figure F.2 – Simplified unicast content streaming service information flows |
| 311 | F.3 IG and WAN GW in different physical devices Figure F.3 – NAT traversal based on IMS access NAT-T model |
| 312 | Figure F.4 – Workflow for IMS NAT-T model |
| 314 | Annex G (informative)NAT-T informational flows for IPTV services Figure G.1 – NAT traversal based on the Symmetric-RTP mechanism |
| 315 | Annex H (normative)Port mapping and NAT traversal for FCC/RET for multicast content services H.1 General H.2 Cookie signalling |
| 316 | Figure H.1 – Port mapping process and keep-alive packets for RET Figure H.2 – NAPT traversal for FCC/RET with cookie signalling |
| 317 | H.3 NAT traversal without cookie signalling Figure H.3 – NAPT traversal for FCC/RET without cookie signalling |
| 318 | H.4 Correlation of RTCP messages sent to the RS and FT entity |
| 319 | Annex I (normative)Presence XML schema |
| 320 | Annex J (informative)Protocol procedure subclause structure Figure J.1 – Subclause structure in the present annex |
| 321 | Figure J.2 – TISPAN IMS IPTV Stage 3 specification structure |
| 322 | Annex K (normative)OITF-specific TR-135 and TR-106 remote management objects K.1 General K.2 OITF-specific TR-135 remote management object Table K.1 – Parameter list for an OITF using TR-135 |
| 328 | K.3 OITF-specific TR-106 remote management object |
| 329 | Table K.2 – Parameter list for an OITF using TR-106 |
| 331 | Annex L (informative)New event package for SIP SUBSCRIBE/NOTIFY |
| 332 | Annex M (informative)Overview of notification services in OIPF R2 Figure M.1 – Overview of notification services |
| 333 | Table M.1 – Summary of notification mechanisms |
| 334 | Annex N (normative)Fast Channel Change and Retransmission (FCC/RET) N.1 Application-layer retransmission (RET) N.1.1 General N.1.2 Unicast RET for multicast content service |
| 335 | N.1.3 Unicast RET for unicast content service Figure N.1 – Call flow for multicast content service with unicast retransmission service |
| 336 | N.1.4 Multicast RET for multicast content service N.1.5 Packet loss event upstream of the RET server Figure N.2 – Example showing location of packet loss deep in the network relative to the RET server |
| 337 | N.1.6 Packet loss event downstream of the RET server Figure N.3 – Multicast RET protocol interaction for packet loss upstream of RET server |
| 338 | N.2 Fast channel change (FCC) Figure N.4 – Multicast RET protocol interaction for packet loss downstream of RET server, with the OITF acting as immediate reporter |
| 340 | Figure N.5 – Multicast content delivery with FCC |
| 341 | Annex O (informative)IG handling of IMPUs in association with GRUU |
| 342 | Annex P (normative)FDT schema extensions |
| 343 | Annex Q (normative)IG Service awareness Q.1 General Q.2 IG Algorithm for service awareness |
| 344 | Annex R (normative)Definition of content reporting info package R.1 General R.2 Applicability R.3 Info Package Name R.4 Info Package Parameters |
| 345 | R.5 SIP option Tags R.6 INFO message body parts R.6.1 General R.6.2 SIP Content-Type header field value R.6.3 SIP Content-Disposition header field value R.6.4 Message body syntax R.7 Info package usage restrictions R.8 Rate of INFO requests R.9 Info Package Security Considerations |
| 346 | Annex S (normative)Definition of Digital-Media-Purchase info package S.1 General S.2 Applicability S.3 Info package name S.4 Info Package parameters S.5 SIP option Tags |
| 347 | S.6 INFO message body parts S.6.1 General S.6.2 SIP Content-Type header field value S.6.3 SIP Content-Disposition header field value S.6.4 Message body syntax S.6.5 Info Package usage restrictions S.7 Rate of INFO requests S.8 Info package security considerations |
| 348 | Annex T (normative)Definition of parental control watched content info package T.1 General T.2 Applicability T.3 Info package name T.4 Info package parameters T.5 SIP option tags T.6 INFO message body parts T.6.1 General |
| 349 | T.6.2 SIP Content-Type header field value T.6.3 SIP Content-Disposition header field value T.6.4 Message body syntax T.7 Info package usage restrictions T.8 Rate of INFO requests T.9 Info package security considerations |
| 350 | Annex U (normative)Common types U.1 Schema U.2 Definitions U.2.1 ProgramIdType U.2.2 UserIdType |
| 351 | Annex V (normative)Schema extension for FLUTE FDT V.1 Namespace V.2 Import Namespace and schema V.3 Extension of FDT attributes |
| 352 | Bibliography |
