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