hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
6.2.2 Procedure for CoD service
|
IPTV Control upon receiving SETUP message from the UE on Ct2 interface, responds with the RTSP REDIRECT message containing at minimum sequence and location header. The location of the nominated MCF is passed in the location header. The header should comply with [6]: • "Location: rtsp://host:port"; • "host = <A legal Internet host domain name of IP address (in dotted decimal form), as defined by [6], clause 3.2 >"; • "port = *DIGIT".
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7 Procedures using IGMP for NGN integrated -IPTV
|
During SD&S process the UE shall discover multicast address to access broadcast IPTV services, e.g. BTV, BTV with trick mode. Broadcast IPTV services are based upon using multicast delivery and signalling as defined in the Internet Group Management Protocol [20]. The IGMP is applicable on the Xd interface. Xd interface can be subdivided into Dj, Di and Ds [4]. UE should use IGMP on the Dj interface. If the multicast stream is not available at the access network, the access network will propagate IGMP messages on the Di interface.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.1 User Equipment (UE)
|
If Ipv4 is used for the transport, the UE shall support IGMP v3 as described in [20]. If Ipv6 is used for the transport, the UE shall support MLDv2 as described in [21]. Backward compatibility rules between the UE and the Transport Function have to be done conforming [20], clause 7 and [21], clause 8.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.1.1 Procedure for BTV service
|
The IGMP protocol shall be used conforming to [5], clause 7.3.1 for: • initiating the BTV service on the discovered multicast address; • leaving the BTV service.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.1.1.1 Procedure for starting to receive multicast
|
In order to start receiving multicast media stream, the UE is required to join a multicast group. The UE shall send a Membership Report Message (IGMP) or Multicast Listener Report Message (MLD) for joining in a multicast group. The message shall be populated as follows: • Multicast Address field is set to the multicast address to be joined in. • Source Address field is set to the source address to include if such information is available to the UE and if the protocol version allows it. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 36
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.1.1.2 Procedure for stopping to receive multicast
|
In order to stop receiving multicast media stream, the UE is required to leave the multicast group. The UE shall send a Membership Report Message (IGMP) or Multicast Listener Report Message (MLD) for leaving a multicast group, if the multicast protocol version allows it. The message shall be populated as follows: • Multicast Address field is set to the multicast address to be left. • Source Address field is set to the source address to exclude if source address had been included during the join procedure.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.1.1.3 Procedure for channel switching
|
In order to operate channel switching, the UE is required to leave the old multicast group and join a new multicast group. The UE shall send a Membership Report Message (IGMP) or Multicast Listener Report Message (MLD) for leaving and joining in a multicast group. The message shall be populated as explained in clauses 8.1.1 and 8.1.2.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.1.2 Procedure for BTV with trick modes service
|
The IGMP protocol shall be used conforming to [5], clause 7.3.1 for: • initiating the BTV with trick mode service on the discovered multicast address; • switching from unicast mode back to multicast delivery modes during trick mode operations as defined in [4]; • leaving the BTV with trick mode service.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.1.3 Procedures for Near COD (UE, MDF)
|
Near COD streams shall be delivered using IP multicast from MDF to transport processing function as described in [4] (clause 11.4. Near CoD ) and clause 7. The MDF provides a Near CoD service as a set of multicast channels with the same content where start of the same content on each channel is shifted in time depending on length of content and size of the smallest seek operation (e.g. an interval can be 10 s of minutes). NOTE: For example if content duration is 100 minutes and IPTV service provide chooses to start Near CoD each 15 minutes, it would require at least 7 multicast stream for Near CoD service for a single content item. The UE retrieves via Tr interface service selection information about Near COD content from SD&S, e.g. IP addresses of associated multicast channels. The UE shall initialize BTV service sending a Membership Report Message (IGMP) or Multicast Listener Report Message (MLD) for joining in a multicast group (as described in clause 7.1.1.1). If trick play is supported by Near COD it should follow procedure for BTV with trick modes service (clause 7.1.2). In this case, when fast forward stream reaches the same time position as N+1 multicasted Near COD channel, the UE should instead of using unicast switch back to multicast delivery and join N+1 Near CoD channel as defined in [4]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 37
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
7.2 Transport Functions
|
For Ipv4 multicast IPTV service distribution, the network transport functions shall support minimally IGMPv2 or higher. The use of IGMPv3 is recommended, in which case the backwards compatibility rules of [20], clause 7 shall apply. For Ipv6 multicast IPTV service distribution, the network transport functions shall support minimally MLDv1 or higher. The use of MLDv2 is recommended, in which case the backwards compatibility rules of [21], clause 8 shall apply.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
8 Procedures using SIP for NGN integrated IPTV
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
8.1 User Equipment (UE)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
8.1.1 Procedure for Notifications
|
SIP is optional on Tr interface between UE and CFIA or NGN Applications. SIP usage should comply with [25]. SIP enabled converged IPTV UE may receive notifications through interactions with the Common NGN ASF as defined in TS 182 028 [4], annex A. The SIP message body may be used as a generic unified notification container when Common NGN ASF terminates notifications from multiples incoming sources, i.e. IM (SIP), MMS/SMS (MM7, SMPP), e-mail (SMTP), other for delivery to the UE via single mechanism. The SIP message body may optionally contain actions, which user are allowed to perform. The user can select action(s), which will be passed back to the Common NGN ASF for processing as described in clause A.9. This procedure shall comply with mechanism described in [18] SIP SUBSCRIBE and SIP NOTIFY.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
8.1.2 Procedure for Messaging
|
If the UE supports SIP protocol, then alternatively text messages may be delivered via SIP MESSAGE format as defined in [10]. SIP message body may be used as a generic unified message container. Common NGN ASF terminates messages from multiples incoming sources, i.e. IMS-IM (SIP), MMS/SMS (MM7, SMPP), e-mail (SMTP), other for delivery to the UE via single mechanism. The SIP MESSAGE body may optionally contain actions, which users are allowed to perform. The user can select action(s), which will be passed back to the Common NGN ASF for processing as described in clause A.5.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9 Procedures using DVBSTP for NGN integrated IPTV
|
The DVBSTP may be supported by UE and SD&S functional entity.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.1 User Equipment (UE)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.1.1 Service Discovery and Selection (SD&S)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.1.1.1 Request of DVB Service Discovery and Selection data
|
In the DVB push model of multicast delivery of DVB SD&S data, the UE shall attach to the multicast DVBSTP identified conforming to TS 102 034 [5], clause 5.2.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.1.1.2 Request of DVB Broadband Content Guide
|
In the DVB push model of multicast delivery of a DVB BCG data, the UE shall attach to the multicast DVBSTP streams identified conforming to TS 102 034 [5], clause 5.2. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 38
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.2 Service Discovery and Selection (SD&S)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.2.1 Procedure for Service Selection
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.2.1.1 Delivery of DVB Service Discovery and Selection data
|
In the DVB push model of multicast delivery of DVB SD&S data, the DVBSTP protocol shall be used conforming to TS 102 034 [5], clause 5.4.1. TS 184 009 [26], which specifies the TV URI as globally unique identifier to identify broadcast television channels may be used in the mapping of BC service for DVB Technology as follows. The ServiceName attribute of the TextualIdentifier of TS 102 034 [5], clause C.3.24, should be populated with the TV URI identifying the television channel [26]".
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
9.2.1.2 Delivery of DVB Broadband Content Guide
|
In the DVB push model of multicast delivery of a DVB BCG data, the DVBSTP protocol shall be used conforming to TS 102 539 [8], clause 4.1.2.2.1. 10 Procedures using RTP/RTCP and UDP for NGN integrated IPTV
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.1 User Equipment (UE)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.1.1 Procedures for Real-Time Transport
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.1.1.1 Transport using MPEG2TS
|
The UE shall be able to receive the content encapsulated into MPEG2TS over RTP conforming to TS 102 034 [5], clause 7.1.1. The UE shall be able to receive the content encapsulated into MPEG2TS over UDP conforming to TS 102 034 [5], clause 7.1.2. If VBR is used, the VBR shall be capped and resource reservation performed at the cap rate. In this case fixed length GOP is recommended.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.1.2 Procedure for Real-Time Transport Error Correction
|
The UE may support a transport error correction mechanism.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.1.2.1 Unidirectional Transport Error Correction
|
When unidirectional transport error correction is used, the UE shall be able to receive an Application Layer FEC, conforming to TS 102 034 [5], annex E. If VBR is used, the VBR shall be capped and resource reservation performed at the cap rate. In this case fixed length GOP is recommended. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 39
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.2 Media Delivery Function (MDF)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.2.1 Procedures for Real-Time Transport
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.2.1.1 Transport using MPEG2TS
|
The MDF shall be able to send the content encapsulated into MPEG2-TS as specified in TS 102 034 [5] clause 7.1. The MDF shall support: • the transport of the IPTV content within MPEG2TS layer over RTP shall be done conforming to TS 102 034 [5], clause 7.1.1; • the transport of the IPTV content within MPEG2TS layer over UDP shall be done conforming to TS 102 034 [5], clause 7.1.2.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.2.2 Procedure for Real-Time Transport Error Correction
|
The MDF may support a transport error correction mechanism.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.2.2.1 Unidirectional Transport Error Correction
|
For unidirectional transport error correction the MDF shall use an application Layer FEC mechanism, conforming to annex E in TS 102 034 [5].
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.2.3 Procedures for inter-destination media synchronization
|
The use of inter-destination media synchronization requires the MDF to support transport using MPEG2TS layer over RTP, see clause 10.2.1.1.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.3 Synchronization Client (SC)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.3.1 Procedure for real-time transport
|
The SC shall support at least one of the following transport technologies: • MPEG2TS encapsulation.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.3.1.1 Transport using MPEG2TS
|
The SC may be able to process content that is encapsulated in MPEG2TS packets. When using the MPEG2TS encapsulation technology, the SC shall support MPEG2TS over RTP as described in clause 10.1.1.1. NOTE: The limitation to MPEG2TS over RTP is necessary since RTCP is used. The SC shall support RTCP Extensions for Single-Source Multicast Sessions (i.e. BC services) with Unicast Feedback as specified in [28]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 40
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.3.2 Procedures for inter-destination media synchronization
|
The SC shall send RTCP Receiver Reports (RRs) to media-level MSAS address, which is the specified IP address and port number as exchanged during the synchronization initiation or to a pre-configured media-level MSAS address in case of mapping the UE on a Transport Processing Function, see clause 4.3.9. The SC shall extend the RRs with synchronization status information, using an RTCP eXtended Report (XR), as specified in TS 183 063 [17], clause W.1. The synchronization status information shall include the SSRC of source, the Packet Received NTP timestamp and the Packet Received RTP timestamp. It should include the presentation time stamp. The SC shall populate the Media Stream Correlation Identifier with SyncGroupId parameter as part of the XR as specified in TS 183 063 [17], clause W.1. The SC shall be able to receive RTCP reports from the MSAS, on the regular RTCP receive port. The SC shall be able to receive RTCP eXtended Reports (XR) containing synchronization settings instructions. As specified in TS 183 063 [17], clause W.1. The RTCP XRs with synchronization settings instructions shall include the SSRC of source, and packet arrival time information, specifically the reference Packet Received NTP timestamp and the reference Packet Received RTP timestamp receipt time stamp. It should include the reference Packet Presented NTP timestamp. These RTCP XRs may be both appended to RTCP Sender Reports (SRs), but may also be received separately. NOTE 1: Synchronization settings instructions may be interpreted as the synchronization status information of a virtual SC to which this SC may try to synchronize. The SC shall be NTP synchronized [48]. NOTE 2: The quality of the underlying NTP synchronization of SCs is a determining factor in inter-destination media synchronization. ITU-T Recommendation G.114 [i.6] recommends maximum one-way transmission time for an international telephone connection to achieve transparent interactivity. ITU-T Recommendation G.114 [i.6] contains the following statements: "if delays can be kept below [150 ms], most applications, both speech and non-speech, will experience essentially transparent interactivity" and "delays above 400 ms are unacceptable for general network planning purposes". As the purpose of inter-destination media synchronization is typically achieving transparent interactivity (see also TS 181 016 [47] clause A.9.6), the ITU-T Recommendation G.114 [i.6] is a useful guideline. The SC shall not require to receive any RTCP eXtended Reports (XR) containing synchronization settings instructions. The absence of such instructions shall not be taken as a sign that something is wrong. NOTE 3: The SC may not receive synchronization settings instructions because RTCP is normally transported using the unreliable UDP protocol. The SC may also not receive any instructions if it is the most delayed SC in its synchronization group, if it is the only member of its group or if buffering is carried out in the ECF/EFF, see clause 10.5.1. If the SC is co-located with the MSAS, then the exchange of synchronization status information and synchronization settings instructions is internal to the functional entity in which they reside. NOTE 4: An example of co-located SC+MSAS functionality is when UEs exchange synchronization status information and synchronization settings instructions over an existing direct communication channel, see clause A.13.2.3. NOTE 5: The algorithm that is used by the SC to synchronize the media based on the synchronization settings instructions is a vendor implementation decision. See [i.2] for an overview of techniques. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 41
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.4 Media Synchronization Application Server (MSAS)
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.4.1 Procedures for inter-destination media synchronization
|
In case of synchronization for a broadcast stream, the MSAS shall function as a Feedback Target, specified in [28]. Before forwarding RTCP Receiver Reports to the appropriate MF, the MSAS shall remove RTCP eXtended Reports containing synchronization status information, which are specified in TS 183 063, clause W.1 [17]. The MSAS shall send synchronization settings instructions to the SC using RTCP eXtended Report, which are specified in TS 183 063, clause W.1 [17]. The synchronization settings instructions take the form of RTP timestamps, combined with NTP timestamps. The NTP timestamp indicates the clock shared by the synchronization group, the RTP time stamps indicate the expected receipt and/or presentation time. The MSAS shall send expected receipt times. It should send expected presentation time stamps. NOTE 1: Synchronization settings instructions may be interpreted as the synchronization status information of a virtual SC to which the addressed SCs may try to synchronize. NOTE 2: The algorithm that is used by the MSAS to derive the synchronization settings instructions from the received synchronization status information is a vendor implementation decision. See [i.2] for an overview of techniques. In case of synchronization of Content on Demand or other unicast streams, the MSAS shall forward RTCP Receiver Reports to the appropriate MDF. Before forwarding RTCP Receiver Reports, the MSAS shall remove RTCP eXtended Reports containing synchronization status information. The MSAS shall forward RTCP Sender Reports to the appropriate SC, appending synchronization settings instructions to the SC using RTCP eXtended Report. The MSAS may send synchronization settings instructions to the SC using a separate RTCP XR. The RTCP XR for sending synchronization settings instructions is specified in TS 183 063 [17], clause W.1. In case of synchronization in the presence of functional entities that modify or re-originate media streams (e.g. a transcoder or a mixer in an MDF), the MSAS shall function as a Third Party Monitor [29]. It shall be able to receive and process synchronization correlation information as specified in clause 10.6.2. NOTE 3: Synchronization correlation information enables an MSAS to correlate the timing of two related media streams. By using NTP time as a reference, the MSAS can determine which RTP timestamp of the one media stream corresponds with which RTP timestamp of the other media stream.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.5 ECF/EFF
|
10.5.1 Procedures for inter-destination media synchronization In one mapping of the SC is an adjunct function that may be co-resident with any of the appropriate elements of the Transport Processing Function, see clause 4.3.9. If the SC is an adjunct function of the ECF/EFF, then ECF/EFF shall: • send synchronization status information to the MSAS using an RTCP eXtended Report (XR), as specified in TS 183 063 [17], clause W.1; • be able to receive RTCP eXtended Reports (XR) containing synchronization settings instructions, as specified in TS 183 063 [17], clause W.1. The ECF/EFF may have partial SC functionality, supporting SC functionality in the UE. This requires that the SC in the ECF/EFF is in the path between the UE and the MSAS used. In this case the ECF/EFF shall be able to: • Monitor and possibly adjust synchronization status reports going from UE to MSAS. Reported arrival times need to be adjusted for the current buffer time the ECF/EFF has introduced. • Determine the arrival time for the indicated stream at the SC in the ECF/EFF. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 42 • Intercept and carry out synchronization settings instructions. Synchronization settings instructions may or may not be forwarded to the SC in the UE. NOTE: Combining an SC in an UE with an SC in the ECF/EFF may have advantages for channel changing times and synchronization accuracy. When buffering at an UE, channel changing times during the use of a shared service session may be quite large if one of the participants is severely lagging behind the others. Buffering in the ECF/EFF can reduce channel changing times. This requires the ECF/EFF to pre-buffer the channel to which the UE is changing. Furthermore, if buffering is applied in the ECF/EFF, measurements from an UE can be used to increase synchronization accuracy.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.6 Synchronization Client' (SC')
| |
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.6.1 Procedure for real-time transport
|
Clause 10.3.1 is also applicable to SC'.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
10.6.2 Procedures for inter-destination media synchronization
|
The SC' shall send synchronization correlation information to the MSAS, which acts as a Third Party Monitor [44] with respect to the SC'. Synchronization correlation information has the following components. • RTCP eXtended Report (XR) related to the incoming media stream; • RTCP eXtended Report (XR) related to the outgoing media stream. XR related to the incoming media steam is specified in TS 183 063 [17], clause W.1. The XR contains the SSRC of the incoming media stream, the NTP timestamp and the Packet Received RTP timestamp. The Packet Presented RTP timestamp field shall be set empty. XR related to the outgoing media stream is specified in TS 183 063 [17], clause W.1. The XR contains the SSRC of the outgoing media stream, the NTP timestamp and the RTP time stamp. The Packet Presented RTP timestamp field shall be set empty.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
11 Procedures using FLUTE for NGN integrated IPTV
|
When optional Multicast Download delivery for Push COD is required then FLUTE protocol shall be supported by UE and MDF functional entity.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
11.1 User Equipment (UE)
|
When Multicast Download delivery is used for PushCOD content then UE shall support FLUTE protocol for download and store of PushCOD content as specified in RFC 3926 [30] and TS 102 034 [5] conform to clause 10.
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
11.2 Media Delivery Function (MDF)
|
The File delivery over Unidirectional Transport (FLUTE) protocol [30] shall be used for PushCOD multicast download from MDF to UE. In addition to the basic FLUTE protocol as specified in RFC 3926 [30], the PushCOD multicast download is comprised of parts that further specify how FLUTE is used in TS 102 034 [5] (as in clause 10). The purpose of file delivery is to deliver content items in files. A file may contain any type of data (e.g. Audio/Video file, Binary data, Still images, Text and BCG metadata). ETSI ETSI TS 183 064 V3.4.1 (2011-02) 43 12 Support mobility, interconnection and hybrid scenarios The UE (converged) should support unicast based service continuation between NGN IPTV UEs for the following services ([4], clause 11.12.1): • Trick modes on broadcast TV. • Content on Demand. • Time-shift TV. • Network PVR. • UGC. • Content Bookmarks. The UE (converged) should support unicast based service continuation between NGN IPTV UEs and Mobile UE with 3GPP PSS support for the CoD service (as in [4], clause11.12.1). The UE and NGN based IPTV should support interconnection scenarios refer to [4], annex G. IPTV services supported in interconnection and examples of signalling flows for selected services are described in [i.4]. The NGN integrated IPTV should be interconnected with Content Delivery Networks (CDN) as following TS 182 019 [i.12]: • IPTV Control interconnected with CDN via reference point Cu, Qt (CDNCF) or Ct (CCF) using http or optionally SOAP/XML. • UE interconnected with CDN via reference point Xc' (CCF) and Xd' (CDF) using same protocols as over Xc (RTSP or optionally HTTP) and Xd reference point. NOTE 1: Because this document is published before publication of TS 182 019 [i.12] according mentioned referenced entities (CDNC, CCF, and CDF) and reference point (Cu, Qt, Ct, Xc' and Xd') there may be changes that could not be reflected this time. The UE (converged) may support hybrid scenarios to deliver IPTV services with NGN integrated IPTV as described in [4], annex I. In this case all protocol on NGN integrated IPTV shall follow this specification. In addition hybrid MDF may to support alternative delivery of media over Xd' reference point. Hybrid MDF is Media Delivery Function as specified in clause 4.3.6 which additionally to delivery method specified in clause 10.2 may also support existing alternative media delivery using for example DVB broadcasting technologies. NOTE 2: Alternative delivery of media over Xd' reference point is out of scope for this specification. Example of alternative delivery is mentioned in [4] annex I (e.g. DVB-T, DVB-S, DVB-C and DVB-H).
|
0c678f4294f75d371c5dbfd089522f4b
|
183 064
|
13 IPTV user profile schema
|
NGN Integrated IPTV provides support for several options to access user profile in accordance with the location where the user data is: • Use UPSF as the host for the set of user related information necessary for multi-subsystems service blending. • Use of data federalisation (represented by UDAF). If user profile is hosted in a single place, e.g. using UPSF as the host, the IPTV user profile is described by an XML document. This XML document complies with the XML schema defined in annex H. Although it is not explicit in the XML schema described in annex H, the IPTV user profile must comprise at least profiles of mandatory services one BC profile, CoD profile, PVR profile and UE capabilities profile. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 44 Annex A (informative): Functional entity relations and example signalling flows of NGN integrated IPTV operations A.1 Functional entities relations and overview of the NGN integrated IPTV procedures UE SD&S IUDF CFIA MCF MDF IPTV-C UPSF Xc Sh Sh Ss Ct2 Xd Xp Sa Tr Sh 8. Delivery of media streams to UE 2. Service Discovery 7. User controls of media streams 3. Service selection 6. Selection and control of MCF 1. Service initiation UDP/RTP/RTCP Diameter RTSP HTTP Legenda:NGN integrated IPTV model 7. Control of MDF 5. Service control User & service data Tr 4. Service attachment & Authorization Not defined ECF/EFF IGMP/MLD Ud Di DVBSTP Tr Transport processing functions Ud NOTE: This figure represents high level relationships and protocols between the functional entities. The detailed procedures and signalling flows are presented in the following sections of this clause. Figure A.1: NGN integrated IPTV - protocol model with FE relation 0) Initially, the UE is required to start or boot (i.e. a set-top-box, PC, mobile or any device with an IPTV client) and perform network attachment to obtain network parameters (i.e. an IP address, P-CSCF address, etc.). 1) After network attachment the UE is required to start service initiation steps. 2) UE performs service provider discovery in order to enable SD&S procedure followed by IPTV service selection and attachment as defined in [4]. SD&S can use HTTP over Tr as describe in clause 6 or DVBSTP over Tr as described in clause 9. 3) Then UE performs the service selection procedures with CFIA via Tr (using HTTP over Tr as described in clause 6 to receive service selection information. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 45 4) At this stage the IPTV UE needs to acquire and use collected service selection information to establish appropriate selected service via CFIA 5). NOTE 1: The IPTV-C is able to initiate resource reservation process for network resources needed by the IPTV service according to the capabilities of the UE. The resource reservation and allocation is performed using standardized transport control functions of NGN RACS available to the IPTV-C. 5) Following the successful session initiation, the IPTV-C informs the MCF via Sa interface (or UE in some cases, i.e. BC) about identification of selected content from the Media Delivery Function (or ECF/EFF for BC services) to initiate delivery of the selected multimedia content (CoD, nPVR). 6) The UE may interactively control CoD media stream over the Xc interface (between the UE and the MCF) via RTSP protocol (as defined in clause 6). The UE may control BC media stream over the Di interface (between the UE and the ECF/EFF) with IGMP/MLD protocol (as defined in clause 7). 7) The MDF performs media delivery over the Xd interface is based on UDP/RTP stream delivery and several transport variants (as described in clause A.2). NOTE 2: Fast Channel Change is being discussed by DVB-IPI for the next release. A.2 Example signalling flows of service discovery and selection SD&S mechanisms used for service discovery, selection and the delivery of service discovery information is based upon [5], clause 5.2. Service discovery enables the discovery of IPTV services available over NGN integrated IPTV subsystem. The service discovery results in the presentation of services with sufficient information for the user to make a choice and access the chosen service. Selection takes place after the user has made a service discovery. UE SD&S IPTV Control 1. HTTP GET 2. Service discovery information 5. Service initiation (service selection) 4. Service selection information (HTTP or DVBSTP) 3. HTTP GET Figure A.2: Service discovery and selection procedures 1) The UE request service discovery information based on [5], clause 5.2. The request may contain other header fields conforming to [9]. 2) The SD&S response with appropriate XML based answer to UE request with service delivery information. The response to the HTTP requests above returns the appropriate XML records defined in [5], clause 5.2.6. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 46 3) In the pull model of unicast delivery of DVB SD&S data, the HTTP protocol is used conforming to [5], clause 5.4.2.2. NOTE: In case of push mode this step is not required. 4) There are two mechanisms defined, one for multicast and one for unicast. The protocol DVB SD&S Transport Protocol (DVBSTP), clause 5.4.1 [5] is used. The protocol HTTP [9] is used to transport BCG [8] information over unicast. A.3 Signalling flow and protocol RTP/RTCP for Retransmission Protocol using RTP/RTCP for RETransmission (RET). RETransmission solution is optional. When RET is used then procedure rely on the RTP retransmission solution as specified in TS 102 034 [5] annex F. Procedure may rely on the RTP retransmission solution as specified in [23] and [24], for guaranteeing the delivery of the unicast CoD service and broadcast TV services. NOTE: RTP/RTCP could be applicable for Fast Channel Change. This work is being discussed by DVB-IPI for the next release. This clause describes an example of signalling flow for Retransmission. UE AN MDF Retr Media Management 2. RTCP FB Packet Loss Service Configuration 3. RTP with lost packet 1. RTP/UDP content Retain Content for Retr Figure A.3: Retransmission signalling A.3.1 User Equipment (UE) procedure for BTV service For BTV service delivered over RTP/UDP, retransmission service functionality may be signalled towards the UEs. The way this is signalled as well as which are the retransmission service configuration parameters is for further study. When the UE notices that packet loss may have taken place (based on e.g. RTP sequence number gap detection), it may decide to request retransmission of the missing packet(s). This is done by issuing a unicast RTCP Feedback message to a feedback target. The RTCP Feedback message has the format of the generic NACK as defined in RFC 4585 [23]. The destination port and address of the feedback target is configured at the UE. Upon packet loss detection, the UE may wait some time delta T before issuing a retransmission request. This is to allow the feedback target (see further) to send a RTCP FB message. If such a FB RTCP message is received from the FB target indicating packet loss corresponding with the packet loss detection by the UE, the UE should not issue an RTCP FB message itself. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 47 The RTCP FB messages do not have to be sent in compound RTCP messages by the UE (i.e. they can be sent stand-alone without SDES or RR). The feedback target for the RTCP FB messages can be different from the compound RTCP messages (carrying SDES and RR), and the compound RTCP messaging may be even suppressed upon configuration. The feedback target also hosts the retransmission server from which the UE should expect the retransmissions. The packets that are retransmitted are formatted according to the [24]. The retransmissions can be sent either in unicast or in multicast. When the packets are retransmitted in multicast, they have the same multicast group address of the original MC RTP stream, but a SSRC identifier is used different from the one in the original stream. When the packets are sent in unicast, the SSRC identifier can be identical to the SSRC of the MC stream carrying the original RTP packets. The UE supports reception of RTCP messages sent by the feedback target over MC with the same MC group address as the MC stream carrying the original RTP packets. These RTCP messages can be RR, SDES, FB messages [23]. As described above, a FB message sent out by the Feedback target towards the UE is used for packet loss signalling in order to have the UE abstaining from FB messages itself for the signalled packet loss. The FB target may also send out Receiver Summary Information (RSI) RTCP messages. RSI messages are formatted according RTCPSSM draft (reference) and allow to signal e.g. maximum (upstream) RTCP bandwidth that can be consumed by the UE. The UE can issue multiple retransmission requests to take into account loss of retransmission packets or retransmission requests (RTCP FB message), based on e.g. a time-out mechanism. The maximum number of retransmission requests associated with the same packet loss event that can be issued by the UE is application specific. The way this is signalled as well as which are the retransmission service configuration parameters is for further study. The candidate configuration parameters are: • Common IP address of the Feedback Target and Retransmission Server. • Destination Port number of RTCP upstream messages, Destination Port number of unicast RTP retransmissions. NOTE 1: The above given parameters may be different for each corresponding MC original stream. Optional: separate IP address and port for compound RTCP messaging (RR and SDES). • Payload type number of RTP retransmission packets. • Delta T = Minimum waiting time between packet loss event detection and sending out RTCP FB message by UE (to allow reception of RTCP FB messages from Feedback target, which cancel the outstanding UE RTCP FB message). • Upstream RTCP bandwidth that can be consumed by the UE. • The time a packet is available for retransmission. NOTE 2: If DVB-IPI is extended to include configuration parameters they should be applicable. A.3.2 User Equipment (UE) procedure for CoD service For CoD service delivered over RTP/UDP, retransmission service functionality may be signalled towards the UEs. RFC 4585 [23] and RFC 4588 [24] define how retransmissions is supported. When the UE notices that packet loss may have taken place (based on e.g. RTP sequence number gap detection), it may decide to request retransmission of the missing packet(s). This is done by issuing a unicast RTCP Feedback message to a FB target which may coincide with the CoD server. The RTCP Feedback message has the format of the generic NACK as defined in RFC 4585 [23]. The destination port and address of the feedback target (when different from the CoD server) is configured at the UE. The RTCP FB messages do not have to be sent in compound RTCP messages by the UE (i.e. they can be sent stand-alone without SDES or RR). NOTE 1: Compound RTCP messages (carrying SDES and RR) may be even suppressed upon configuration. If used they are sent to the CoD server. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 48 The feedback target also hosts the retransmission server from which the UE should expect the retransmissions. The packets that are retransmitted are formatted according to the RFC 4588 [24]. The SSRC identifier in the unicast retransmission packets is different from the SSRC of the original RTP packet stream, and the same session address/port is used. The UE can issue multiple retransmission requests to take into account loss of retransmission packets or retransmission requests (RTCP FB message), based on e.g. a time-out mechanism. The maximum number of retransmission requests associated with the same packet loss event that can be issued by the UE is application specific. The way this is signalled as well as which are the retransmission service configuration parameters is for further study. The candidate configuration parameters are: • common IP address of the Feedback Target and Retransmission Server; • destination Port number of RTCP upstream messages; • payload type number of RTP retransmission packets; • upstream RTCP bandwidth that can be consumed by the UE; • the time a packet is available for retransmission. NOTE 2: If DVB-IPI is extended to include configuration parameters they should be applicable. A.4 Example signalling flows of nPVR This clause describes an example of nPVR signalling . nPVR service as typically delivered as CoD service and the CoD flows from annex C apply. UE CoD MF SD&S And CF IPTV Apps 1. http nPVR content capture request IPTV Control nPVR Content Selection 3. Select MF 2. nPVR content capture request 4. nPVR content capture request 5. Record 6. RTSP CoD playout Figure A.4: nPVR signalling flows ETSI ETSI TS 183 064 V3.4.1 (2011-02) 49 User selected Asset from the list of Assets available for nPVR from Customer Facing IPTV application. 1) The UE sends an http request to initiate content capture to the CF IPTV Apps. 2) The CF IPTV Apps asks IPTV control to record the Asset and create recording schedule. 3) The IPTVC selected MDF for the recording. 4) The IPTVC passes the recording schedule to MDF. 5) The MDF records the program. After the recording has started the program is available as normal CoD asset. Flows defined in annex C are applicable. A.5 Example signalling flows of IPTV service for messaging Common NGN ASF should be used for messaging as discussed in clause 5.1.6. In case messages are delivered via CFIA as shown in figure A.5, the role of Common NGN ASF is to terminate and process multiple incoming messages (i.e. SIP, MM7, SMTP, other) into generic XML schemas, which are then passed to CFIA for presentation to the UE. The responses from the UE via CFIA should be passed back to Common NGN ASF, which will route the messages to the appropriate destination. A.5.1 Example signalling flows of IPTV service for messaging using HTTP UE2 IPTV ASF (CFIA) NGN ASF 1. Send Message 2. HTTP POST (Message) UE1 9. Present / Announce incoming message 3. HTTP GET (Message) 5. HTTP 200 OK NGN UDAF 4. Check profile & messaging forwarding 8. HTTP 200 OK 6. Deliver Message to destination HTTP POST 7. Confirm delivery HTTP 200 OK Figure A.5: Messaging between IPTV UEs using HTTP for messaging The detailed description of the protocols and messages flows: 1) User 1 sends message to the IPTV user 2. 2) The UE1 sends HTTP request with attached message and destination identifier to the CFIA. 3) The CFIA forwards message to the NGN ASF messaging server. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 50 4) According to policies the NGN ASF may request IPTV sub-profile of federalized user profile from NGN UDAF if this information is not stored in NGN ASF. The NGN ASF identified destination UE based on policy and destination information. 5) If based on policies the message could be forwarded to the IPTV UE2, the Common NGN ASF informs CFIA about the incoming message. 6) The CFIA delivers message to UE 2. The notification message is delivered to the UE 2 (via HTTP and Tr interface) using internal Notification mechanism as described in clause B.8. 7-8) Successful delivery is confirmed to UE 1 via CFIA. 9) The message is presented to user 2. NOTE: The message can be directly delivered from and to Common NGN ASF. To simplify the message processing, user actions can be packed together with the messages, e.g. to reply to the message or to store the received message in the user message box. The user selection can be passed back to the Common ASF for processing, i.e. to remove message specific processing from the UE. In this case the following XML schema is recommended as defined in annex C. A.5.2 Example signalling flows of IPTV service for messaging using SIP UE2 (IPTV) IPTV ASF (CFIA) NGN ASF 1. UE registred send message 2. SIP MESSAGE UE1 (SIP) 9. Present / Announce incoming message 3. SIP MESSAGE 7. 200 OK NGN UDAF 4. Check profile & messaging forwarding 5. Deliver Message to destination 6. 200 OK SIP Proxy (IMS core) 8. 200 OK Figure A.6: Messaging between from SIP capable UEs to IPTV UE 1) The UE1 is a SIP capable device, compliant with [10] or for interaction with IMS core compliant with [11]. 2) The UE1 generates and sends a SIP MESSAGE to the SIP proxy. 3) The SIP proxy forwards message to NGN ASF. 4) The NGN ASF checks user profile and policy for incoming messages and based on this information it forwards the message to IPTV UE2 network. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 51 5-6) The Message is delivered and presented or stored in message box of the UE2. 7-9) The response is replied back to the UE1 via Common NGN ASF. NOTE: The delivery to the IPTV UE can be both directly from the Common NGN ASF and via the CFIA as described in the above flow. The flows above are applicable to the delivery of messages from other sources such as IMS-IM (SIP), MMS/SMS (MM7, SMPP), e-mail (SMTP), other to IPTV UE via a single notification interfaces utilizing either HTTP or SIP. To simplify the message processing, user actions can be packed together with the messages, e.g. to reply to the message or to store the received message in the user message box. The user selection can be passed back to the Common ASF for processing, i.e. to remove message specific processing from the UE. In this case the following XML schema is recommended as defined in annex C. A.6 Example signalling flows of IPTV presence services A.6.1 Example signalling flows of IPTV presence notification using PA IPTV ASF (CFIA) NGN ASF 9. SIP NOTIFY UE1 (IPTV) 4. SIP SUBSCRIBE UE 2 PS (SIP) 1. HTTP POST 13. Present information is presented to UE or apply in directory UE2 (SIP) 2. HTTP GET 8. Presence status change or actual state 12. 200 OK (XML) NGN UDAF 3. Check profile & presence service access authorization 5. 200 OK 11. 200 OK (XML) 10. 200 OK Subscribe Notification service 6. SIP NOTIFY 7. 200 OK Figure A.7: Presence services to IPTV UE using PA 1) The UE1 may subscribe to presence service information and use HTTP POST to request the information via CFIA. 2) The CFIA forwards the request to NGN ASF to check the user profile. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 52 3) The NGN ASF may check profile and perform authorization for usage of presence service within the IPTV. NOTE 1: Authorization regarding the submission of presence information from the presence service may use [15] with authorization rules content [16] independently. The exact procedure is outside the scope of the present document. For the current flows it is assumed that UE2 authorized access to the presence. 4) The NGN ASF subscribes to the presence information on behalf of the user. 5) The subscription is confirmed to the NGN ASF. 6) After the initial subscription PS sends initial presence status via SIP NOTIFY (actual presence if any available). 7) The notification is confirmed to the PS. 8) The presence state changes or is published for first time. 9) The PS informs the NGN ASF about presence state change using SIP NOTIFY. 10) Notification is confirmed to the PS. 11) The NGN ASF generates http 200 OK with attached presence information in XML document. 12) The presence information is forwarded to the UE1. NOTE 2: For steps 11 and 12 HTTP POST may be alternatively used to deliver presence information to the UE. 13) The UE1 displays information or updates presence status on user interface. The Presence User Agent in the Common NGN ASF may report presence directly to the converged IPTV UE in step 11. The Presence User Agent may perform presence status collection and reporting from NGN IPTV to NGN Presence Server. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 53 A.6.2 Example signalling flows of IPTV presence notification using RLS IPTV ASF (CFIA) NGN ASF w/ PUA 9. SIP NOTIFY UE1 (IPTV) 4. SIP SUBSCRIBE RLS 6. 200 OK 1. HTTP POST 13. Present information is presented to UE or apply in directory UE2 PS (SIP) 2. HTTP GET 7. Presence status change or actual state 5. SIP SUBSCRIBE 12. 200 OK (XML) 8. SIP NOTIFY NGN UDAF 3. Check profile & presence service access authorization 6. 200 OK 11. 200 OK (XML) 10. 200 OK 10. 200 OK Subscribe Notification service Figure A.8: Presence services to IPTV UE using RLS 1) The UE1 may subscribe to presence service information and use HTTP POST to request the information via CFIA. 2) The CFIA forwards the request to NGN ASF to check the user profile. 3) The NGN ASF may check profile and perform authorization for usage of presence service within the IPTV. NOTE 1: Authorization regarding the submission of presence information from the presence service may use [15] with authorization rules content [16] independently. The exact procedure is outside the scope of the present document. For the current flows it is assumed that UE2 authorized access to the presence. 4) The NGN ASF subscribes to the presence information on behalf of the user. The request is sent to a Resource List Server as described in [14]. 5) The RLS subscribes on behalf of the user also to presence information of all users, In this particular case, the user supplying presence is the UE2. 6) The subscription is confirmed to NGN ASF. 7) After the initial subscription the PS sends presence via SIP NOTIFY (if any is available). 8) The UE2 informs the RLS about changes in the presence state via SIP NOTIFY. 9) The RLS sends resource-list notification as described in the [14]. 10) The notification is confirmed via SIP 200 OK. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 54 11) The NGN ASF generates http 200 OK with attached presence information in XML document. 12) The presence information is forwarded to the UE1. NOTE 2: For steps 11 and 12 HTTP POST may be alternatively used to deliver presence information to the UE. 13) The UE1 displays information or updates presence status on user interface. The Presence User Agent in the Common NGN ASF may report presence directly to the converged IPTV UE in step 11. The Presence User Agent may perform presence status collection and reporting from NGN IPTV to NGN Presence Server. A.6.3 Example signalling flows of IPTV presence updates IPTV ASF (CFIA) UE1 (IPTV) 2. HTTP POST (XML) 3. HTTP GET (XML) 1. Presence status change NGN ASF PS 6. 200 OK 5. 200 OK 4. IPTV presence is updated Figure A.9: Presence information about IPTV services used by UE1 The IPTV UE1 may inform IPTV application server about state of services used by the UE1. 1) When new event occurs or IPTV application server makes an update request, the UE1 may send related presence information in XML format. 2) The UE1 generates and sends XML presence state to the CFIA. 3) The information is processed and forwarded to the to the presence agent in the Common NGN ASF. NOTE: Structure of XML document may follow XML schema defined in [17], annex E: "XML schema for IPTV presence document extension". 4) The presence information is updated. 5-6) The presence update is confirmed to the UE1 via HTTP 200 OK. Alternatively, the Presence User Agent or Presence Network Agent may perform presence collection and reporting from NGN IPTV to NGN Presence Server. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 55 A.7 Example signalling flows of IPTV service interaction with NGN/IMS services This clause provides description about interaction procedures between IPTV and other NGN/IMS service level subsystems, e.g. IMS, for composite services. In the data flows it is assumed that both IMS users (IMS UE) are registered in IMS subsystem. The procedure describes several types of the interactive features in converged NGN IPTV applications (e.g. presenting a caller ID of an incoming call on the TV screen). A.7.1 Example signalling flows of IPTV service handling of incoming calls In this scenario User 1 calls towards User 2 and both have their IMS UEs in IMS domain. User 2 is subscribed to a converged IPTV service (e.g. caller ID notification with options to accept, forward or reject incoming call when his IPTV service is active) via the IPTV UE (which have service mapping/relationship with IMS UE 2). There may be supported at least 3 cases for incoming call handling: • confirm acceptance of incoming call; • refuse call; • forward call to voice mail or other terminal. (7) Return of IPTV profile with user’s service information (12) S-CSCF can forward INVITE to User 2 home UE (1) INVITE originating call from User 1 to User (4) Check user profile, user presence (10) User 2 response/reaction (11) Call accepted (3) Call invitation via INVITE is delivered to common NGN ASF (5) Optional request of IPTV user profile data (if not available in NGN UDAF) (8) Deliver service information to IPTV ASF and adapt them for IPTV UE (6) Optional return of IPTV user profile data (9) Call ID is sent to the IPTV UE Core IMS IPTV UE User 2 IPTV IUDF NGN UDAF UPSF User profile IPTV ASF NGN ASF IMS S-CSCF IMS UE2 User 2 (IPTV) IMS User 1 (UE1) Core IMS (2) S-CSCF use User 2 profile to forward service initiation SIP message to NGN ASF Figure A.10: High level interactions procedure between IPTV and other service level subsystems - NGN/IMS inter-working with NGN integrated IPTV NGN ASF should be used for mapping SIP messages to generic XML schemas which should be processed by IPTV ASF that will present information to IPTV UE (and receive/forward user reaction, e.g. confirmation for receiving call back to core IMS) related to user IMS UE. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 56 The detailed description of the used protocols and messages is following: 1) A usual SIP INVITE message with information about destination user, call originating user, type of call, optionally further parameters is forwarded from NGN (core IMS). 2) S-CSCF access user profile data. Dotted line indicates that IMS user profile has been requested from UPSF (at regular IMS registration). 3) Based on IMS user profile the SIP INVITE is forwarded by the S-CSCF to the NGN ASF via ISC interface. NGN ASF acts for the S-CSCF as an IMS AS that can receive SIP messages. A mapping between the SIP identifiers from SIP INVITE message and corresponding IPTV UE device ID (of User 2) can be required. The mapping identifiers may be performed within NGN ASF using information about user stored locally or e.g. in the NGN UDAF (but detail process or place of storage for this information is out of scope for the present document). NOTE 1: In case that user 1 sends messaging/notification information via SIP MESSAGE to user 2 same mapping of SIP identifiers could be applied for delivery information ant their transformation to presentable format to IPTV UE of user 2. 4) According to policies the NGN ASF may request IPTV sub-profile of federalized user profile from NGN UDAF if this information is not stored in NGN ASF. 5-6) Optionally the request can be also forwarded to IUDF. The exact specification of this is out of scope for the present document. 7) When required user data and service information are delivered and available for the NGN ASF. Further steps are performed if user has subscription for such converged service activated and IPTV UE is online. 8) A mapping from SIP messages to the XML message is performed by the NGN ASF. The XML notification message is used for that delivery and presentation service information to IPTV UE (directly or via Client Facing IPTV application - step 9). The mapping of relevant information from SIP message to XML have to be generated by NGN ASF including required SIP identifiers and service information (e.g. call line ID transferred in the XML notification message) in form presentable by IPTV ASF (Client Facing IPTV Application) or finally to the IPTV UE. Mapping is following: - SIP identifiers of destination URI mapped to IPTV UE ID of User 2 (the mapping has been already performed); - SIP identifier of originating URI with information about User 1 (information who is calling or sending message); - SDP parameters - optionally service information and parameters about the call like subject, type of call (emergency, priority), etc. 9) The service information can be then presented to IPTV UE from IPTV ASF (via Tr and using HTTP). 10-12) The IPTV ASF may require future action from User 2 on IPTV UE whether user has for example accepted the call or rejected. This response messages are returned back to NGN ASF which will react appropriate way back towards IMS (e.g. forwarding back SIP INVITE to IMS UE of User 2). NOTE 2: Similar mechanisms may be used also for interaction with other services such as presence or messaging. NOTE 3: Similar procedure should be used for IPTV interaction with SIP based architecture based on RFC 3261 [25] (in this case SIP proxy is used instead of S-CSCF). ETSI ETSI TS 183 064 V3.4.1 (2011-02) 57 A.8 Example signalling flows of Notifications Common NGN ASF may be used for external notification services to the IPTV UE as described below, i.e. for emergency alerting, advertising or maintenance notification (where non-IPTV NGN ASF request notified the IPTV UE). IPTV ASF (CFIA) NGN ASF 5. HTTP POST (Notification) UE1 6. HTTP 200 OK NGN UDAF 4. Check profile & notification message rules 8. 200 OK 7. Deliver Notification message to UE1 3. Notification event 1. Subscribe Notification service 2. 200 OK 9. Message presented to UE or store in message box Figure A.11: Notification services to IPTV UE The description of the protocols and messages illustrated below. 1) The User 1 subscribes to the Notification service. 2) The NGN ASF confirms successful subscription by 200 OK. NOTE 1: Steps 1 and 2 may be performed via CFIA, in this case the steps may be directly between NGN ASF and UE1. 3) The notification event occurs and the NGN ASF performs action to inform the User 1. 4) The NGN ASF may request IPTV sub-profile of federalized user profile from NGN UDAF and policies. The NGN ASF may decide, i.e. based upon received profile or policies, the right UE to send the notification to. In this case the IPTV UE1 is selected, but different UE, i.e. SIP based, may be used. 5) The NGN ASF informs the CFIA about notification event which should be presented to UE. 6) The IPTV ASF confirms receiving information with notification data in XML format (e.g. the UE identifier, notification message, etc.). NOTE 2: Steps 5 and 6 are not required when direct notification to the UE is used, i.e. SIP based. 7) The notification message is delivered to the UE 1 (via HTTP and Tr interface) using internal Notification mechanism as described in B.8. 8) The delivery is confirmed to the NGN ASF. NOTE 3: Steps 7 and 8 may be performed via CFIA or directly between the NGN ASF and UE1. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 58 9) The notification information is present to the user or stored in the UE message box. NOTE 4: Notification methods should use HTTP over Tr interface. Optionally for SIP enabled UE, the SIP notification should comply with [18]. User actions can be delivered together with the notification and user selection passed back to the Common ASF for processing, i.e. to simplify message processing on the UE and remove specific message processing logic from the UE. In this case XML schema defined in clause A.5 is recommended. A.9 Example signalling flows of Targeted Advertising The targeted advertisement content is selected by the ADS (Ad Selection Service). Ad insertion opportunities and key ad insertion steps for unicast and multicast based services defined in clause 11.10 [4] apply. A.9.1 Network side unicast based advertisement This clause defines network side advertisement procedures for pre-roll, post-roll and pause ad placement opportunities discussed in clause 11.10 [4]. Figure A.12 presents network side pre-roll and post roll advertisement procedure for unicast based services. The procedure is applicable for the following services: - Content on Demand. - Network PVR. - Time-shift TV. UE RACS MCF/ MDF User Data CFIA 2. User Profile 4. ADx: Ad Request IPTVC 1. Content Selection 6. Personalised play-list 9. Unicast Session Setup ADS 3. 5. 7. 8. Acknowledgement and personalised playlist ADM POIS SIS Figure A.12: Pre-roll and post-roll advertisement for unicast based services. 1) User selected a content following SD&S procedure discussed in clause 6.3. 2) CFIA optionally requests current profile in order to request an ad. 3) UPSF/IUDF returns current profile. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 59 4) ADM in the CFIA requests personalised ads from ADS on Adx interface as defined in clause 5.1.8. XML schema carried over HTTP applies++ conforming to SCTE130-3 [i.13]. Optionally Adm may request additional ad related information from POIS and SIS. 5) ADS returned content identifiers for personalised ads on Adx. 6) CFIA passes to MCF (s personalised play lists containing main selected content and ads. Optionally trick mode operations can be disabled for ads sat the time of play-list creation. 7) MCF confirms creation of the play-list. 8) CFIA returns name of the personalised play-list in the asset URL. 9) UE initiates unicast session setup. Normal procedure for corresponding service type (e.g. CoD, nPVR) applies. A.10 Example signalling flows of User Generated Content Figure A.13: UGC creation procedure The UGC procedure comprises the following steps: 1) The UE sends a request for User Generated Content declaration. 1a) The UE sends a User Generated Content Declaration http GET Request to the CFIA. 1b) The CFIA may check user rights and user profile prior to granting the UE permission to create UGC and generates a unique UGC ID. UGC ID is location independent, globally unique and should be accessible by other UEs. CFIA 1c. http UGC Declaration Response 1b. Check rights & user profile 1a. http UGC Declaration Request 2a. http UGC Description Request 2b. http UGC Description Response UE 3. UGC Creation 4a. http UGC Publication Request MF 4c. http notification mechanism (clause A.8) User Data SD&S 4b. http UGC Publication Response UGC delivery initiation/modification/termination (clause 6.1) ETSI ETSI TS 183 064 V3.4.1 (2011-02) 60 1c) The CFIA confirms that the UE is authorised to create UGC by sending 200 OK a Declaration Response containing the UCG ID and the designated MCF/MDF where the UCG can be created (uploaded/upstreamed). 2) The UE sends a request for UGC description 2a) The Description Request http POST contains a description of the User Generated Content: name, type, restriction, textual description, selected group users, type of content, coding. 2b) The CFIA records the UGC description, attaches UGC ID and UGC description and sends a UGC Description Response to the UE with 200 OK. 3) UE initiates creation of User Generated Content for uploading or upstreaming the content to the designated MDF and confirms to the CFIA the publication of the content. 4) The CFIA links UGC ID, UGC description and UGC location (address), and publishes this UGC information to the SD&S. CFIA should used existing notification mechanism to announce new UGC content to notify concerned UEs via user interface (http procedures used as in clause 5.1.5). The UGC description publication by the CFIA in step 4 may take place before, during or after the UGC content creation in step 3. The CFIA notifies UEs that have pre-selected the UGC as per clause 5.1.9. A.11 Example signalling flows of Content Recommendation UE UPSF/ IUDF SD&S CFIA 3. http request recommendations for IPTV services CRS NGN ASF PS 4. http response with list of recommendations Recommendation request and delivery 5. Notification with personalised content recommendations 1. Acquisition of metadata and user profiling for CR 2. Recommodation trigger 6. Consumption or bookmarking based on CR Figure A.14: Recommendation request and delivery ETSI ETSI TS 183 064 V3.4.1 (2011-02) 61 Recommendations Request and Delivery 1) Aggregation and user configuration of profile or preferences for CRS using HTTP on Tr interface. CFIA may collect other information for user profiling and identification of user preferences and expectation for CR. The Content Recommendation function with service logic and metadata (recommendation) is exposed by CRS. 2) CFIA or external CRS system triggers recommendation events to request content recommendation to for the UE. 3) CFIA request content recommendation from CRS using HTTP GET request for specified user and recommendation type. Request is identified by unique request ID. 4) CRS replay with http response containing list of recommendations. 5) CFIA notified UE via HTTP notification mechanism or push content delivery. 6) If user accepts recommendation UE shall request delivery of recommended content using existing procedures for particular content type (e.g. CoD, BC, UGC, PushCoD, etc.) or generate content bookmark for later consumption. NOTE: The service delivery itself is not affected by the service recommendations. The case when video based content recommendation (e.g. trailer) is streamed from MDF is not shown in this procedure but it is expected that follows existing procedure (e.g. CoD, BC, UGC, PushCoD, etc.). A.12 Example signalling flows of Content Bookmarks An IPTV Content Bookmark service consists of two main steps: • creation of IPTV Content Bookmark: allows a user to create and store configurable pointers to content, e.g. entire or parts of content (favourite scene) to be able to quickly access the content; • retrieval of IPTV Content Bookmark: allows to exchange and share IPTV favourite data. Figure A.15 provides an overview of IPTV Content Bookmark creation and retrieval. This procedure is applicable at any time during IPTV session (e.g. during BC, CoD, nPVR session) or at the SD&S stage (e.g. EPG browsing). Figure A.15: Creation, storage and retrieval of IPTV Content Bookmark 5. IPTV Content Bookmark retrieving request 7. IPTV Content Bookmark retrieving response UE CFIA MF User profile SD&S 3. Add CM metadata to SD&S 4. IPTV Content Bookmark creation response SD&S service selection or consumption of IPTV content 6. Acquire Content Bookmark 2. Check rights, user profile and store Content Bookmark 1 http Request to create IPTV content bookmarks ETSI ETSI TS 183 064 V3.4.1 (2011-02) 62 1) The UE requests CFIA via Tr using http POST to create Content Bookmark and optionally supplies additional data (e.g. description). The bookmark data may include content information and at minimum requires content and position identifications. NOTE: The translation of the content bookmark into the actual byte position within the content files is highly dependent on the encoding and storage technique and is outside the scope of this specification. 2) The CFIA may check user profile prior to creating content bookmark. CFIA creates bookmark and generates a unique content bookmark ID. Content Bookmark should be stored in user profile. 3) The CFIA may inform SD&S about the Content Bookmark creation and update SD&S over Ss' with metadata. 4) The CFIA confirms creation and storage of Content Bookmark data. 5) The UE sends to CFIA request via http over Tr for retrieval Content Bookmark. 6) The CFIA requests Content Bookmark and generate response including content identification, pointer to the bookmarked position, additional metadata. The information should be sufficient to initiate content delivery from the bookmarked position. 7) The CFIA send content bookmark to UE as part of replay/restart content offer. A.13 Example signalling flows for inter-destination media synchronization A.13.1 Inter-destination media synchronization flows for HTTP signalling A.13.1.0 General The functional entity "MSAS" in this clause refers to the session-level MSAS, see also clause 4.3.9. This clause describes an example HTTP signalling flow to initiate inter-destination media synchronization. SC 1. HTTP GET 2. HTTP 200 OK MSAS Figure A.16: HTTP signalling for initiating inter-destination media synchronization. 1) The SC sends an HTTP GET request to the MSAS, which contains the synchronization group identifier (SyncGroupId). See clause 5.1.15 for details on the use of SyncGroupId. 2) The MSAS responds with a HTTP 200 OK to the SC, which contains the SyncGroupId and adds the MSAS parameters (SSRC-ID, address and port number and RTCP SyncGroupID). ETSI ETSI TS 183 064 V3.4.1 (2011-02) 63 If the SC and MSAS are mapped on the UE and CFIA, respectively, then the sync interface maps on the Tr interface, and the shown flow in Figure 30 may be mapped on the flows for service initialisation, see also TS 182 028 [4], clauses 6.2.1 and 6.2.2. A.13.2 Inter-destination media synchronization flows for RTCP signalling A.13.2.1 General The functional entity "MSAS" in this clause refers to the session-level MSAS, see also clause 4.3.9. A.13.2.2 Inter-destination media synchronization of BTV service This clause describes an example RTCP signalling flow for the exchange of using synchronization status and settings instructions exchange from clauses 10.3 and 10.4. Figure A.17: RTCP signalling for the exchange of synchronization status and settings instructions for a BTV service 1) The SC sends RTCP Receiver Report (RR) to the MSAS. This report includes an eXtended Report (XR) containing the synchronization status information according to TS 183 063 [17], clause W.1. 2) The MSAS sends an RTCP XR containing synchronization settings instructions directly to the SC according to TS 183 063 [17], clause W.1. NOTE: The MSAS may forward RTCP RR to the source of the media. RTCP SR are sent directly from media source to SC. A.13.2.3 Inter-destination media synchronization of CoD service This clause describes an example RTCP signalling flow for the exchange of using synchronization status and settings exchange from clauses 10.3 and 10.4. 1. RTCP RR + XR(status) 2. RTCP XR(settings) SC MSAS ETSI ETSI TS 183 064 V3.4.1 (2011-02) 64 Figure A.18: RTCP signalling for the exchange of synchronization status and settings instructions for a CoD service 1) The SC sends RTCP Receiver Report (RR) to the MSAS. This report includes an eXtended Report (XR) containing the synchronization status information according to TS 183 063 [17], clause W.1. 2) The MSAS removes the XR from the RR and forwards the RR to the source of the media. 3) The MF sends its RTCP Sender Reports (SR) to the MSAS. 4) The MSAS adds the XR containing the settings instructions according to TS 183 063 [17], clause W.1 to the SR, and forwards this to the SC. A.13.2.4 RTCP exchange between UEs directly This clause describes an example RTCP flow for inter-destination media synchronisation between two UEs directly. Both UE1 and UE2 have SC functionality. UE1 acts also as MSAS, see figure A.18a. If the RTP/RTCP flows are handled by a server (e.g. a conference bridge), then the MSAS functionality may also be located there. UE1 UE2 SC2 SC1 MSAS Sync Figure A.18a: UE acting as MSAS for inter-destination media synchronization between UEs SC MSAS MF 1. RTCP RR + XR(status) 2. RTCP RR 3. RTCP SR 4. RTCP SR + XR(settings) ETSI ETSI TS 183 064 V3.4.1 (2011-02) 65 Figure A.18b shows an example RTCP flow for inter-destination media synchronisation between two UEs directly. MF CFIA UE1 (MSAS) UE2 (SC) 1. RTP/RTCP exchange 4. RTCP RR + XR (status) 5. RTCP XR (settings) 2. BTV/CoD session 3. BTV/CoD session MF CFIA UE1 (MSAS) UE2 (SC) 1. RTP/RTCP exchange 4. RTCP RR + XR (status) 5. RTCP XR (settings) 2. BTV/CoD session 3. BTV/CoD session Figure A.18b: RTCP signalling for the exchange of synchronization status and settings instructions between UEs directly 1) UE1 and UE2 have a media session, which includes regular RTP/RTCP exchange for the media transport and transport control. 2)-3 UE1 and UE2 each have a BC or CoD session for the same service and content. 4)-5) UE1 and UE2 reuse their regular RTCP SRs and RRs to append RTCP Extended Reports (XR) [27] for the exchange of synchronisation information. See also clauses 10.3 and 10.4. UE1 and UE2 have to obtain the SyncGroupID, the SSRC value and the MSAS address (=UE1 address) before step 4. These may be obtained using the procedures as described in clauses 5.1.16.1 and 5.1.16.2. A.13.2.5 RTCP exchange for sync' This clause describes an example RTCP flow for sync', see figure A.18c. MSAS SC’ 1. RTCP XR (correlation) Figure A.18c: RTCP flow for sync' 1) SC' sends MSAS synchronization correlation information: RTCP eXtended Reports (XR) related to the incoming media stream and RTCP eXtended Reports (XR) (TS 183 063 [17], clause W.1) related to the outgoing media stream, see TS 183 063 [17], clause W.1. Synchronization correlation information may be sent from SC' to MSAS at regular pre-configured time intervals. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 66 Figure A.18d are example RTCP XR messages for sync', see also TS 183 063 [17], clause W.1. Figure A.18d: Example RTCP messages for sync' A.14 Example signalling flows of Personalized Channel Personalized Channel (PCh) service allows user to define and watch one or multiple pre-configured/scheduled content items as a single (virtual) channel. Personalized Channel information is stored in the user service profile (PCh information). 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |V=2|P|reserved | PT=XR=207 | length=9 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of packet sender SC' | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | BT=9 |SPST=3 |0| block length=7 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PT | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Media Stream Correlation Identifier, same for in and out | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of incoming media stream | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, most significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, least significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received RTP timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Presented NTP timestamp = empty | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ |V=2|P|reserved | PT=XR=207 | length=9 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of packet sender SC' | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | BT=9 |SPST=4 |0| block length=7 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PT | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Media Stream Correlation Identifier, same for in and out | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of outgoing media stream | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, most significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, least significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received RTP timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Presented NTP timestamp = empty | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ ETSI ETSI TS 183 064 V3.4.1 (2011-02) 67 Figure A.19: Overview of PCh service procedures 1) User selects and purchases content for PhC, e.g. from the offers provided by SD&S. UE requests Customer Facing IPTV Applications to setup PCh service with HTTP GET request. 2) CFIA checks service access authorization with UPSF/IUDF. 3) User defines and configures personalized channel via Tr using CFIA with selection of one or more content items discovered via SD&S, and send by HTTP POST as XML with define name/ID for the channel, items on the channel, order, time when each item should be played. Channel definition is confirmed to the UE. XML schema for Personalized Channel playlist is defined in annex I. 4) Optionally, PCh event (e.g. start of the channel or play out of the new scheduled content item) may trigger CFIA notification to the UE, e.g. via notification. 5) CFIA initiates PCh service by HTTP POST via Ss interface towards IPTV-C based on service logic, PCh schedule and user availability to watch personalized channel. 6) IPTV-C reserves required resources via Gq' to RACS. 7) IPTV-C notifies UE and MCF (depending if redirect or proxy mode is used) to start delivery of the personalized content from MDF based on agreed playlist (defined in annex I). 8) MDF delivers the content to UE on Xd interface using existing procedures for content delivery CoD, BC, PushCOD procedures. NOTE: Content could be controlled as for any CoD service via Xc reference point from UE using RTSP or optionally HTTP. 9) PCh can be terminated either by MCF or UE. MCF may terminate PCh when all the content on the channel has been delivered to the UE, or when the channel or user subscription has expired. CFIA 3. PCh Configuration 9. PCh service Termination 4. PCh event based on schedule 2. Request authorization REPEAT 1. PCh Service http GET request (purchase & setup) 3. PCh Configuration RACS MCF/ MDF IPTV-C UPSF IUDF UE 5.PCh notification 3. PCh Configuration confirmation 6.Resource reservation 5.PCh initiation 7.PCh initiation of content delivery 8.PCh content delivery ETSI ETSI TS 183 064 V3.4.1 (2011-02) 68 Annex B (normative): UE capabilities and example Signalling flows of NGN integrated IPTV operations B.1 UE capabilities • UE supports following specifications as described in annex D. B.2 Signalling flows of BTV This clause describes an example of signalling flow of session initiation and termination for BTV. Session Termination Session Initiation UE ECF/EFF SD&S And CF IPTV Apps 1. Multicast Report (Join) 2. Resource Reservation & Admission Control Content Selection: Multicast Address Media Stream 1. Multicast Report (Leave) 2. Resource Release Figure B.1: Signalling flows for BTV operation ECF/EFF is typically a part of the Access Network as shown on TS 182 028 [4], figure 4. User selected BTV channel during SD&S process. UE has received multicast address to join. To start the service: 1) The UE sends a multicast Join request (Membership Report Message (IGMP) or Multicast Listener Report Message (MLD) ) to start receiving multicast media stream. The UE populates the message as follows: - multicast Address field is set to the multicast address to be joined; ETSI ETSI TS 183 064 V3.4.1 (2011-02) 69 - if the protocol is IGMPv3 or MLDv2: if source addresses have been advertised, the Record Type is set to "ALLOW_NEW_SOURCES" ECF/EEFd Source list is set to the source addresses; if no source address has been advertised, the Filter mode is set to "EXCLUDE" and Source list is set to "empty". 2) Local resource reservation and admission controlled is performed by the ECF/EEF as defined in [3]. Media stream is delivered. To leave the service: 1) The UE sends a multicast Leave request (Membership Report Message (IGMP) or Multicast Listener Report Message (MLD) ) to stop receiving multicast media stream. The UE populates the message as follows: - multicast Address field is set to the multicast address to be left; - if the protocol is IGMPv3 or MLDv2: if source addresses have been set in the Join message, the same source address list is excluded from the listening interface; the Record Type is set to "BLOCK_OLD_SOURCES" and Source list is set to the source address; if no source address has been set in the Join message, Filter Change record is set to INCLUDE with an empty source list. 2) Local resource release is performed by the ECF/EEF as defined in [3]. NOTE: Together with the service request, the key exchange and delivery of security metadata to the UE may be initiated in accordance with the media content protection model as described in NGN security architecture TS 187 003 [i.17]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 70 B.3 Signalling flows of CoD This clause describes an example of signalling flow of CoD session initiation and termination. B.3.1 CoD Session initiation UE RACS CoD MF SD&S And CF IPTV Apps 1. RTSP SETUP (Asset URL) IPTV Control 7. 200 OK, Session ID Content Selection: RTSP Asset URL 2. Select CoD MCF 3. Reserve and Commit Resources between MDF/MDF BGF and UE 4. RTSP REDIRECT (MCF address, Resources_Conf_ID) 5. Est TCP Connection for RTSP 6. RTSP SETUP (Asset URL, Resources_Conf_ID) 8. Extract SDP 9. RTSP PLAY 10. Content stream(s) Figure B.2: CoD session initiation User selected CoD asset during SD&S process. UE has received asset URL. 1) The UE sends RTSP SETUP to the IPTV control with the asset URL. 2) The IPTVC control selects MCF. 3) The IPTVC control reserves resources between MDF and UE. 4) The IPTVC control returns selected MCF in the REDIRECT message. 5) TCP connection for RTSP is established between UE and MCF. NOTE 1: Optionally RTSP method DESCRIBE may be used before SETUP to request media delivery initialization information from MCF if the parameters have not been sent by IPTV control within REDIRECT sequence (1 to 5). ETSI ETSI TS 183 064 V3.4.1 (2011-02) 71 6) The UE sends RTSP SETUP to the IPTV control with the asset URL. 7) The CoD-MF sends 200 OK with SDP. The SDP contains the session descriptions of UDP/RTP stream to be used. 8) Optionally, the UE extracts the media descriptions from the SDP of 200 OK. 9) The UE sends RTSP PLAY command. 10) The CoD-MF starts sending UDP/RTP content streams to the UE. NOTE 2: If coupled mode is used for CoD procedure the steps 1 to 4 are not needed (procedure start from step 5). NOTE 3: After successful authorization of the service request, the key exchange and delivery of security metadata to the UE may be initiated in accordance with the media content protection model as described in TS 187 003 [i.17]. B.3.2 CoD Session termination UE RACS CoD MF 4. 200 OK 2. UDP Content Stream is terminated TCP Connection for RTSP 1. RTSP TEARDOWN (optional Resources_Conf_ID) Content stream(s) 3. Resource Release Figure B.3: CoD session initiation 1) TEARDOWN request is sent to CoD-MF. 2) CoD-MF stops sending UDP/RTP content streams. 3) The CoD MF requires for RACS to release resources. 4) The CoD MF responds with 200 OK response. B.4 Signalling flows of BTV with trick modes This clause describes an example of signalling flow of BTV session initiation and termination. BTV with trick modes is a superimposition of BTV and CoD sessions in a single service as discussed in [4]. The switch from BTV to trick modes is shown in figure B.4. ECF/EFF is typically a part of the Access Network as shown on TS 182 028 [4], figure 4. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 72 UE RACS CoD MF SD&S And CF IPTV Apps 2. RTSP SETUP (Asset URL) IPTV Control 8. 200 OK, Session ID 3. Select CoD MCF 4. Reserve and Commit Resources between MDF/MDF BGF and UE 5. RTSP REDIRECT (MCF address, Resources_Conf_ID, ) 6. Est TCP Connection for RTSP 7. RTSP SETUP (Asset URL, Resources_Conf_ID) 9. RTSP PLAY (Range) 10. Content stream(s) ECF/EFF Resource Release 1. Multicast Report (Leave) – Pause bTV channel bTV stream Figure B.4: BTV with trick modes: switch to trick modes User is watching BTV channel and wants to initiate trick mode. 1) The UE sends a multicast leave request (Membership Report Message (IGMP) or Multicast Listener Report Message (MLD)) to stop receiving multicast media stream. NOTE: Local resource reservation and admission controlled is performed by the ECF/EFF as defined in [3]. 2) The UE sends RTSP SETUP to the IPTV control with the asset URL. 3) The IPTV-C control selects MCF. 4) The IPTV-C control reserves resources between MDF and UE. 5) The IPTV-C control returns selected MCF in the REDIRECT message. 6) TCP connection for RTSP is established between UE and MCF. 7) The UE sends RTSP SETUP to the IPTV control with the asset URL. 8) The CoD-MF sends 200 OK. 9) The UE sends RTSP PLAY command. 10) The CoD-MF starts sending UDP/RTP content streams to the UE. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 73 B.5 Signalling flows of Push CoD B.5.1 Push CoD procedures using notification IPTV ASF (CFIA) IPTV-C UE UPSF/ IUDF 2. Check profile & notification Push CoD rules 6. UE accept content 4. Push CoD event 1. Subscribe to Push CoD service 3. Accepted 7. Push CoD content is delivered to UE MF MCF & MDF 5. Deliver Notification about Push CoD content to UE Figure B.5: Push CoD services procedure The detailed description of procedure is following: 1) User subscribes to Push CoD service using Tr reference point. 2) According to policies the CFIA may request IPTV sub-profile of federalized user profile over Ud interface. CFIA decides user authorization to use a service based on received information and service logic. 3) CFIA authorizes request and confirms successful subscription to the UE. NOTE: IPTV Service provider may initiate Push CoD without explicit user subscription in which case 1 to 3 may be optional. 4) New Push CoD event acts as a trigger for CFIA. 5) CFIA delivers notification to the UE (including CoD content identifier) using notification framework. 6) UE may accept delivery of Push COD. 7) IPTV-C initiate towards MCF/MDF PushCOD delivery to UE by one of following option: - CoD content delivery (as described in clause 6.1.2) then stream is stored as file in UE for later PushCOD consumption. - BC content delivery (as described in clause 7.1.1) then stream is stored as file in UE for later PushCOD consumption. - CoD content download from MDF (as described in clause 6.1.6 follows [5], clause 10). The content may be either viewed immediately or stored for later viewings. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 74 B.6 Signalling flows of Near CoD B.7 Signalling flows of Interactive TV UE UPSF/ IUDF CFIA & SD&S External ASFs Common NGN ASF UEs 2. Check user profile & authorization 1. Start Interactive IPTV service 5. Interactive TV application 6. Terminate Interactive TV application and release resources 3. Initiate Interactive TV application 4. Start Interactive IPTV service response Figure B.6: Personalized Interactive TV applications 1) After UE discovers interactive IPTV application via SD&S then send HTTP request GET for service initiation of selected iTV from CFIA using Tr reference point. Request may contain UE id and also required authorization. Depending on iTV application HTTPS may be supported. 2) CFIA optionally checks user profile, requests authorization and information for service personalization. 3) CFIA requests Common NGN ASF to setup interactions with external ASFs, if external ASFs are used. 4) In case of proxy mode all communication goes via CFIA. In cease of redirection, External ASF replies to CFIA with URL and iTV service description. 5) CFIA replies to the UE optionally attaching information for initiating and using interactive TV application. 6) UE initiates by HTTP request personalized interactive IPTV service (e.g. interacting with application or with other users) towards CFIA (direct mode or proxy mode) or external ASF (redirect mode). 7) UE requests termination of Interactive IPTV application. CFIA releases all resources allocated for the interactive TV applications. B.8 Signalling flows of IPTV Notification IPTV ASF (CFIA) shall support notification mechanism to deliver notification Message to the IPTV UE using HTTP delivery over Tr reference point. The procedure is applicable for notification mechanism used in the following services: • Notification Service. • Notification based TAI. • User generated content. • Content Recommendation. • Emergency alerting. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 75 • Incoming call management. • Client PVR. • Content/Service availability notification (e.g. Push CoD, UGC). Figure B.7: IPTV Notification services to IPTV UE The description of the protocols and messages illustrated below: 1) When notification event occurs either through external triggers or by decision of CFIA service logic, IPTV ASF (CFIA) initiates notification and composes Notification message using XML schema defined in annex C. NOTE 1: CFIA may request information from IPTV user profile and check service policies. 2) CFIA sends notification message to the UE (via HTTP and Tr interface) which contains XML notification. NOTE 2: Two options have been identified so far for HTTP notification mechanisms: persistent HTTP session and/or UE browser listener on the known port. 3) The delivery is confirmed by HTTP 200 OK response to the CFIA. 4) The notification information may be presented to the user or trigger UE internal action, for example UE initiated IPTV services. NOTE 3: Notification methods use HTTP over Tr interface. User actions can be delivered together with the notification and user selection passed back to IPTV ASF (CFIA) for processing, i.e. to simplify message processing on the UE and remove specific message processing logic from the UE. In this case XML schema defined in annex C is used. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 76 B.9 UE start up and service attachment Figure B.8 presents functional steps of the UE start-up procedure for NGN Integrated IPTV. The procedure follows [4], clause 6.3.1. UE NASS SD&S 3. IPTV Security Bootstrapping IPTV AS CFIA 1. Network Attachment 2. Service discovery 4. Attach to the IPTV Service 5. IPTV Service Configuration SCP Figure B.8: UE start-up procedure 1) UE shall perform network attachment via e1 reference point. Protocol usage shall comply with e1 reference point. During this step, the UE attaches to network and may acquire network identification, e.g. IP address. The UE may be passed additional data for Service Provider Discovery (SPD) as defined in [4], clause 6.3.2. 2) UE shall discover service providers and services from SD&S. SD&S shall apply conforming to TS 102 034 [5], clause 5.2 as discussed in [4],, clause 6.3.2 and in clause 5.1.1 of the present document. 3) During this step UE, bootstrapping function and IPTV service provider are involved in initial IPTV security bootstrapping processing as defined in [4] and in TS 187 003 [i.17], clause 9 and follows TR 187 013 [i.1]. After successful mutual authentication between the UE and Bootstrapping function the UE tries to access the IPTV service. UE and corresponding IPTV service control entities may derives appropriate keys from key management entities (as initial steps of service protection and content protection mechanisms). 4) UE shall attach to the IPTV Service and request service selection via Tr interface using HTTP. 5) UE obtains IPTV Service offers. During steps 4 and 5, UE navigates and selects a service from available service offers. IPTV AS may update IPTV user profile, presence and other applications of behalf of IPTV. Service navigation and selection can be provided in a generic case via different functional entity as presented on figure 10 in TS 182 028 [4]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 77 Annex C (normative): XML Schema for IPTV notification, messaging and user interaction C.1 XML notification schema This annex defines XML schema for IPTV Notifications. Application of IPTV notifications is defined in TS 182 028 [4]. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uep="urn:org:etsi:ngn:params:xml:ns:iptvnotification" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVNotification" type="tIPTVNotification"/> <xs:complexType name="tIPTVNotification"> <xs:annotation> <xs:documentation>XML Schema for NGN IPTV Notifications</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="Identifier" type="tIPTVNotificationIdentifier" /> <xs:element name="Message Type" type="tIPTVNotificationType" /> <xs:element name="Reference Message Identifier" type="tIPTVNotificationIdentifier" minOccurs="0" maxOccurs="1"/> <xs:element name="Expiry date" type="xs:dateTime " minOccurs="0" maxOccurs="1"/> <xs:element name="Sender Information" type="tIPTVInfo " minOccurs="0" maxOccurs="1"/> <xs:element name="Recipient Information" type="tIPTVInfo " minOccurs="0" maxOccurs="1"/> <xs:element name="Action" type="tIPTVNotificationAction" minOccurs="1" maxOccurs="unbounded"/> <xs:element name="NotificationDescription" type="tIPTVNotificationDescription" /> <xs:element name="Extension" type="tExtension" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tIPTVNotificationIdentifier" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="16"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tIPTVNotificationType" final="list restriction"> <xs:restriction base="xs:string"> <xs:enumeration value="Notification"/> <xs:enumeration value="Update"/> <xs:enumeration value="Cancel"/> <xs:enumeration value="Time Shift"/> <xs:enumeration value="Ack"/> <xs:enumeration value="Error"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tIPTVInfo" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="64"/> </xs:restriction> </xs:simpleType> <xs:element name="tIPTVNotificationAction" type="tIPTVNotificationAction"/> <xs:complexType name="tIPTVNotificationAction"> <xs:sequence> <xs:element name="ActionType" type="tIPTVNotificationActionType" /> <xs:element name="ActionTypeDescription" type="tIPTVNotificationDescription" /> </xs:sequence> </xs:complexType> <xs:simpleType name="tIPTVNotificationActionType" final="list restriction"> ETSI ETSI TS 183 064 V3.4.1 (2011-02) 78 <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="16"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tIPTVNotificationDescription" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="256128"/> </xs:restriction> </xs:simpleType> <xs:complexType name="tExtension"> <xs:annotation> <xs:documentation> This element is reserved for further extensions </xs:documentation> </xs:annotation> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:schema> C.2 Notification delivery mechanisms Notification delivery mechanisms should comply with one of the following methods: • Metadata is encoded in XML (W3C XML). • Application event record can optionally be encoded in XML. • Metadata and application event record encoded in XML can optionally be compressed by using Fast Infoset (ITU-T Recommendation X.891 [i.14]), ZLIB including GZIP format (TS 102 472 [i.15]) or BiM (ISO/IEC 23001 [i.16]). Delivery of IPTV notifications may support one of the methods: • HTTP version 1.1 IETF RFC 2616 [9] for application event or metadata delivery over unicast. • HTTP over TLS IETF RFC 2818 [41] for application event or metadata delivery over unicast with secure manner. • Optionally Session Initiation Protocol (SIP)-Specific Event Notification RFC 3265 [18]. Notification mechanisms should applicable for notification used in the following services with specified "tIPTVNotificationActionType": • Notification Service (tIPTVNotificationActionType=NotifySer). • Notification based TAI (tIPTVNotificationActionType=NotifyTAI). • Content Recommendation (tIPTVNotificationActionType=ContentRecom). • Emergency alerting (tIPTVNotificationActionType=Emergency). • Incoming call management (tIPTVNotificationActionType=CallID). • Client PVR (tIPTVNotificationActionType=cPVR). • Content/Service availability notification (e.g. Push CoD, UGC) (tIPTVNotificationActionType=CoD, PcoD, BC, UGC). • User interaction (tIPTVNotificationActionType=Interaction). • Messaging (tIPTVNotificationActionType=Message). ETSI ETSI TS 183 064 V3.4.1 (2011-02) 79 Where tIPTVNotificationDescription may contain: • Text (e.g. string with text message with possibility include hyperlinks, buttons, etc.). • ContentID (e.g. to IPTV content like CoD, PushCoD, UGC, BC, etc.). • URL to content (e.g. picture, video, audio and multimedia). • Presentation type (e.g. show in pop-up, in PiP, not show, etc.). • Or any combination of listed above. C.3 Mapping to ITU-T IPTV framework for notification ITU-T Notification framework is supported by TISPSAN NGN IPTV Notifications schema. This annex illustrates mapping between TISPSAN NGN IPTV Notifications schema and ITU-T framework for notifications. Table C.1: Mapping between TISPAN IPTV Notifications and ITU-T IPTV framework for notification ITU-T IPTV framework for notification TISPAN IPTV Notifications Note Identifier Identifier REQUIRED Message Type Message Type REQUIRED Reference Message Identifier Reference Message Identifier OPTIONAL Expiry date Expiry date OPTIONAL Sender Information Sender Information REQUIRED - ITU REQUIRED - TISPAN Event Information Action Notification Description REQUIRED Recipient Information Recipient Information REQUIRED - ITU REQUIRED - TISPAN Forward Information Not supported OPTIONAL - ITU Not supported Extensions Optional - TISPAN ETSI ETSI TS 183 064 V3.4.1 (2011-02) 80 Annex D (normative): UE capabilities UE supports following specifications: • HTTP: - HTTP protocol shall be used conforming to [5] and follow standard HTTP [9]; - HTTPS [41]; - HTTP Digest [7] is recommended on the Tr interface; - MD5 is recommended digest algorithm as defined in [19], MD5 Message Digest Algorithm; - UE shall support HTTP notification mechanisms based on persistent HTTP connection (as in [9], clause 8.1) and UE listening on known multicast address for HTTP/XML message; - UE should implement an http compliant web browser with JavaScript for: One or more markup languages, such as HTML, XHTML and SVG (e.g. XHTML 1.0 [31], HTML-5 [i.11]); Standard profiles of style sheets (e.g. CSS 2 [32] or CSS TV profile [33]); Standard scripting language (e.g. ECMAScript [34] or JavaScript); Document Object Model (e.g. DOM2 [35]); XMLHttpRequest ( [36]). NOTE 1: A particular implementation of the web browser is outside the scope of the present document. For example the web browser could be based on technologies described in ITU-T Recommendation H.760 [i.3], annex A, (e.g. CEA-2014 or DVB-HTML). Information about UE capabilities and supported browser profiles shall be included in user profile (UE capabilities). UE should access IPTV profiles (including UE capabilities) via Tr interface using XCAP (as described in clause 5.1.2). To minimize compliance and interoperability issues UE shall minimally provide a CE-HTML [51] web browser with XHTML 1.0 [31], CSS TV profile [33], DOM 2 [35], ISO/IEC-16262 [34] (ECMAScript) support. NOTE 2: The UE can support one or more standard browsers technologies (CE-HTML, DVB-HTML, SVG, Mobile browsers) and browser profiles (examples of browser profiles are described in ITU-T Recommendation H.760, [i.3] annex A). For example the web browser profile could be based on following combinations of web technologies: 1) CE-HTML profile ([51]) (default) - XHTML 1.0, CSS TV profile, DOM 2, ISO/IEC-16262 (ECMAScript). 2) DVB-HTML profile ([i.7]) - XHTML 1.0, CSS 2, DOM 2 , ISO/IEC-16262 (ECMAScript). 3) SVG profile [i.8] - SVG1.1: CSS 2, DOM 1, DOM 2, ISO/IEC-16262 (ECMAScript) or SVG Tiny ([i.9]): CSS 2, uDOM, ECMA ISO/IEC-16262 (ECMAScript). 4) Mobile profile ([i.10]) - XHTML, OMA Mobile Profile. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 81 • RTSP: - Support of RTSP methods in NGN integrated IPTV as described in clause 6 (based on RTSP usage in [5]); - Optionally HTTP Digest Access Authentication can be applied to RTSP control messages as defined in [19]. • IGMP/MLD: - If Ipv4 is used for the transport, the UE shall support IGMPv3 as described in [20]; - If Ipv6 is used for the transport, the UE shall support MLDv2 as described in [21]. • Transport and encapsulation based on [5]: - The UE shall be able to receive the content encapsulated into MPEG2TS over RTP conforming [5], clause 7.1.1 and MPEG2TS over UDP conforming [5], clause 7.1.2. • DVBSTP: - If DVBSTP for multicast (which is optional for UE) is used then it shall conform to [5], clause 5.2. • SIP: - For SIP capable UE interactions with messaging services, SIP MESSAGE should used conforming to [10]; - For SIP capable UE interactions with notification services, SIP SUBSCRIBE and SIP NOTIFY should be used conforming to [18]. • FLUTE: - UE should support FLUTE for multicast content download delivery as described in [30], [5]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 82 Annex E (normative): XML Schema for sync parameters E.1 Mime Type for inter-destination media synchronization The Mime Type "application/vnd.etsi.iptvsync+xml" is used in HTTP to signal the use of the XML schema of annex E.2 for inter-destination media synchronization. The use of this Mime Type and XML schema is specified in clause 5.1.16.1. The XML Schema shown in annexes E to I are contained in archive ts_183064v030401p0.zip which accompanies the present document. E.2 XML Schema for inter-destination media synchronization <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uep="urn:org:etsi:ngn:params:xml:ns:sync" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="SyncGroup" type="tSyncGroup"/> <xs:complexType name="tSyncGroup"> <xs:sequence> <xs:element name="RtcpXrSyncGroupId" type="xs:nonNegativeInteger"/> <xs:annotation> <xs:documentation> RtcpXrSyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. </xs:documentation> </xs:annotation> <xs:element name="Ssrc" type="xs:nonNegativeInteger"/> <xs:annotation> <xs:documentation> Ssrc is a 32-bit unsigned integer in network byte order and represented in decimal. </xs:documentation> </xs:annotation> <xs:element name="RtcpPort" type="xs:string"/> <xs:annotation> <xs:documentation> Encoding of an IP address (Ipv4 or Ipv6) plus port number. Ipv4 example: 139.63.192.106:53020 Ipv6 example: [2002:0:0:0:0:0:8b3f:c06a]:53020 </xs:documentation> </xs:annotation> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 183 064 V3.4.1 (2011-02) 83 Annex F (normative): XML Schema for content bookmark F.1 XML schema for content bookmarks This annex defines XML schema for IPTV Content bookmark. Application of IPTV content bookmark, e.g. for session continuation or "park and pick up" and flows are defined in TS 182 028 [4]. CoD, nPVR, tsTV content bookmark may contain relative timestamp (NPT), absolute time offset (UTC) or absolute byte offset inside ContentOffset. The value should comply with offsets defined in RFC 2326 [6]. <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvcontentbookmark" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvcontentbookmark" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVContentBookmark"> <xs:complexType> <xs:sequence> <xs:element name="BookmarkedContent" type="tBookmarkedContent" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="tBookmarkedContent"> <xs:sequence> <xs:element name="ContentId" type="xs:string"/> <xs:element name="BookmarkType" type="tBookmarkType"/> <xs:element name="ContentOffset" type="xs:string" minOccurs="0"/> <xs:element name="ExpiryTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tBookmarkType" final="list restriction"> <xs:annotation> <xs:documentation> <label xml:lang="en">Bookmark class</label> <definition xml:lang="en">Specifies the type of bookmark </definition> </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="Failed"> </xs:enumeration> <xs:enumeration value="Parked"> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tExtension"> <xs:annotation> <xs:documentation> This element is reserved for further extensions </xs:documentation> </xs:annotation> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 183 064 V3.4.1 (2011-02) 84 Annex G (normative): XML Schema for Content Description <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uep="urn:org:etsi:ngn:params:xml:ns: contentdescription" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="ContentItem" type="tContentItem"/> <xs:complexType name="tContentItem"> <xs:sequence> <xs:element name="ContentId" type="xs:string" /> <xs:element name="Title" type="xs:string" /> <xs:element name="Originator" type="xs:string" /> <xs:element name="CreationTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="Genre" type="xs:string" minOccurs="0"/> <xs:element name="Description" type="xs:string" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 183 064 V3.4.1 (2011-02) 85 Annex H (normative): XML Schema for the IPTV profile This annex referring to XML schema for creating documents representing instances of the IPTV profile described in annex C of TS 183 063 [17] and may be used by NGN integrated IPTV services. This XML schema is used when IPTV profile is manipulated with the XCAP procedure described in clauses 5.1.2 and 13. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 86 Annex I (normative): XML Schema for Content Playlist I.1 XML schema for content play-list IPTV content play-list is a logical collection of physical assets which can be played together a single 'virtual' asset for linear or on-demand NGN Integrated IPTV services. Normal service flows should apply for the respective service type. Content playlist can be used for following services: • Personalized Channel. • Targeted Advertising (ad insertion). This annex defines XML schema for IPTV content play-list. <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvcontentplaylist" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvcontentplaylist" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVContentPlaylis"> <xs:element name="PlaylistName" type="xs:string"/> <xs:element name="ExpiryTime" type="xs:dateTime" minOccurs="0"/> <xs:complexType> <xs:sequence> <xs:element name="PlaylistItem" type="tPlaylistItem" minOccurs="1" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:element name="Extension" type="tExtension" minOccurs="0" maxOccurs="unbounded"/> </xs:element> <xs:complexType name="tPlaylistItem"> <xs:sequence> <xs:element name="ContentId" type="xs:string"/> <xs:element name="StartContentOffset" type="xs:string" minOccurs="0"/> <xs:element name="StopContentOffset" type="xs:string" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tExtension"> <xs:annotation> <xs:documentation> This element is reserved for further extensions </xs:documentation> </xs:annotation> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 183 064 V3.4.1 (2011-02) 87 Annex J (informative): Bibliography • ETSI TS 188 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN);IPTV Management; Context and Requirements". • W3C Recommendation: "SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)". • ETSI TS 102 542 (all parts) (V1.3.1): "Digital Video Broadcasting (DVB); Guidelines for the implementation of DVB-IPTV Phase 1 specifications". ETSI ETSI TS 183 064 V3.4.1 (2011-02) 88 Annex K (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 21-08-09 21bTD028r1 001 B To create the release 3 start of Work 2.1.1 3.0.0 21-08-09 21bTD136r1 002 B Integrated IPTV New Sections 3.0.0 3.0.1 21-08-09 21bTD137r1 003 B Integrated IPTV architecture stage 3 3.0.0 3.0.1 Insertion of change history table 3.0.1 3.0.2 30-09-09 22WTD097 004 B UGC Procedures 3.0.2 3.0.3 30-09-09 22WTD098 005 B CR procedures 3.0.2 3.0.3 30-09-09 22WTD167 006 B Protocols for SCTE based advertising architecture 3.0.2 3.0.3 CRs 001 to 006 TB approved at TISPAN#22 3.0.3 3.1.0 06-11-09 22bTD052r1 007 B Applicability_of_Synchronization 3.1.0 3.1.1 06-11-09 22bTD053r1 008 B Synchronization_Example_Signalling_Flo ws 3.1.0 3.1.1 06-11-09 22bTD054r1 009 B Use_of_HTTP_for_Synchronisation 3.1.0 3.1.1 06-11-09 22bTD055r1 010 B Use_of_RTCP_for_Synchronisation 3.1.0 3.1.1 06-11-09 22bTD062r1 011 B Protocols for SCTE based advertising architecture 3.1.0 3.1.1 06-11-09 22bTD100r1 012 B Content Bookmarks 3.1.0 3.1.1 06-11-09 22bTD102r1 013 B Near CoD 3.1.0 3.1.1 06-11-09 22bTD103r1 014 B Client PVR 3.1.0 3.1.1 06-11-09 22bTD104r1 015 B Push CoD 3.1.0 3.1.1 06-11-09 22bTD106r1 016 B InteractiveTV 3.1.0 3.1.1 06-11-09 22bTD108r2 017 B Notification Mechanisms 3.1.0 3.1.1 06-11-09 22bTD191r1 018 D Editor's Notes on LS to DVB 3.1.0 3.1.1 17-12-09 23WTD059r1 019 B HTTP_Coding_for_Synchronization 3.1.1 3.1.2 17-12-09 23WTD106r1 020 D Editor's Notes 3.1.1 3.1.2 17-12-09 23WTD107r1 021 B Push COD 3.1.1 3.1.2 17-12-09 23WTD108r1 022 B Applicability & Protocols 3.1.1 3.1.2 17-12-09 23WTD109r2 023 B Personalized_channel 3.1.1 3.1.2 17-12-09 23WTD110r1 024 B User Interaction 3.1.1 3.1.2 17-12-09 23WTD111r3 025 B UE Capabilities 3.1.1 3.1.2 05-02-10 TISPAN03(10)0002r1 026 B Rapporteur_input 3.2.0 3.2.1 05-02-10 TISPAN03(10)0020r1 027 B RTCP Coding for Sync 3.2.0 3.2.1 05-02-10 TISPAN03(10)0021r1 028 B Inter-destination media synchronisation 3.2.0 3.2.1 05-02-10 TISPAN03(10)0022r1 029 B Notification of UGC Preselection 3.2.0 3.2.1 05-02-10 TISPAN03(10)0043r2 030 B UE start up 3.2.0 3.2.1 05-02-10 TISPAN03(10)0044r1 031 B Personalisation 3.2.0 3.2.1 05-02-10 TISPAN03(10)0045r1 032 B Support for mobility & interconnection 3.2.0 3.2.1 05-02-10 TISPAN03(10)0046r2 033 B IPTV Security 3.2.0 3.2.1 05-02-10 TISPAN03(10)0053r3 034 B XML Schema for IPTV notification 3.2.0 3.2.1 05-02-10 TISPAN03(10)0054r2 035 B XML Schema for Content Bookmark 3.2.0 3.2.1 05-02-10 TISPAN03(10)0019r2 036 B Clarification_on_Optionality_of_Functionali ties 3.2.0 3.2.1 14-02-10 TISPAN03(10)0107r1 037 B WI-03208 removal of editor's notes 3.2.1 3.2.2 14-02-10 TISPAN03(10)0108r1 038 B WI-03208 removal of SDES references 3.2.1 3.2.2 14-02-10 TISPAN03(10)0109r1 039 C WI-03208 review of TS 183 064 draft 3.2.1 3.2.2 14-02-10 TISPAN03(10)0119r1 040 B WI-02308 User Identification & authentication 3.2.1 3.2.2 14-02-10 TISPAN03(10)0120r3 041 B WI-03208 UE profile interoperability 3.2.1 3.2.2 14-02-10 TISPAN03(10)0121r3 042 B WI-03208 Content upload procedures 3.2.1 3.2.2 14-02-10 TISPAN03(10)0122r2 043 B WI-03208 User Profile 3.2.1 3.2.2 14-02-10 TISPAN03(10)0123r1 044 B WI-03208 Service Continuation 3.2.1 3.2.2 14-02-10 TISPAN03(10)0133r1 045 B WI-03208 XML Schema for Content Playlist 3.2.1 3.2.2 ETSI ETSI TS 183 064 V3.4.1 (2011-02) 89 Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 14-02-10 TISPAN03(10)0141r2 046 B WI-03208 Alignment of RET with DVB 3.2.1 3.2.2 CRs TB approved 3.2.2 3.3.0 04-06-10 TISPAN03(10)0081r2 047 D WI-03208 Editorial Corrections and removal of editor's notes 3.3.0 3.3.1 04-06-10 TISPAN03(10)0176r2 048 F WI-03208 Correction 3.3.0 3.3.1 04-06-10 TISPAN03(10)0204 049 F WI-03208 CDN reference 3.3.0 3.3.1 29-10-10 TISPAN03(10)0255r1 050 F Definition_of_Mime_Type_for_Sync 3.3.1 3.3.2 29-10-10 TISPAN03(10)0272r1 051 F Clarification_for_service_type_and_iptvser vice_mime-type 3.3.1 3.3.2 CRs approved and Publication 3.3.2 3.4.1 ETSI ETSI TS 183 064 V3.4.1 (2011-02) 90 History Document history V2.1.1 October 2008 Publication V3.4.1 Feburary 2010 Publication
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
1 Scope
|
The present document specifies the services requirements and capabilities for Customer Premises Networks (CPNs) and Customer Network Gateways (CNG) connected to a TISPAN NGN as defined in TS 181 005 [1]. Characteristics of Customer Network Devices (CNDs) that can be connected to Customer Networks specified in the present document are addressed.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. [1] ETSI TS 181 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements". [2] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 5)". [3] ETSI TS 181 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service in NGN; Service Description [Endorsement of OMA-ERELD-PoC-V1]". [4] ETSI TS 181 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Videotelephony over NGN; Stage 1 service description". [5] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [6] Home Gateway Initiative: "Home Gateway Technical Requirements: Release 1" http://www.homegateway.org/publis/HGI_V1.0.pdf. [7] ETSI TS 122 340: "Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS) messaging; Stage 1 (3GPP TS 22.340)". [8] ETSI TS 187 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN SECurity (SEC); Requirements". ETSI ETSI TS 185 005 V2.0.0 (2007-07) 6
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
3 Definitions and abbreviations
| |
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: Customer Network Device (CND): physical device enabling service(s) usage NOTE: 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, through the CNG). Customer Network Gateway (CNG): gateway between the Customer Premises Network (CPN) and the Access Network able to perform networking functions from physical connection to bridging and routing capabilities, but also possibly implementing functions related to the service support Customer Premises Network (CPN): the in-house network composed by customer network gateway, customer network devices, network segments (physical wired or wireless connections between customer network elements), network adapters (performing a L1/L2 conversion between different network segments) and nodes (network adapters with L3 routing capabilities) NOTE: Other terms used to identify CPN in TISPAN NGN R1 deliverables or outside TISPAN are Home Area Network (HAN), Home or Residential Network, Customer LAN (C-LAN). "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.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ASP Application Service Provider CND Customer Network Device CNG Customer Network Gateway CoD Content on Demand CPN Customer Premises Network DLNA Digital Living Networking Alliance DNS Domain Network Service DRM Digital Rights Management FXS Foreign Exchange Subscriber HAN Home Area Network HTTP Digest Hyper Text Transfer Protocol Digest authentication IMPI IP Multimedia Private Identity IMPU IP Multimedia PUblic Identity IMS IP Multimedia Subsystem IP Internet Protocol IPTV IP Television ISIM IMS Subscriber Identity Module ISP Internet Service Provider NBA NASS Bundled Authentication NGN Next Generation Network P-CSCF Proxy-Call Session Control Function PPV Pay Per View PSTN Public Switched Telephony Network PVR Personal Video Recording ETSI ETSI TS 185 005 V2.0.0 (2007-07) 7 QoS Quality-of-Service SIP Session Initiation Protocol STB Set Top Box UA User Agent UE User Equipment UICC Universal Integrated Circuit Card VoIP Voice over Internet Protocol WAN Wide Area Network 4 Services requirements and capabilities for customer networks connected to TISPAN NGN
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1 Service scenarios description
|
The use cases can be grouped in the following categories: 1) Broadband connection 2) Communication 3) Home worker 4) Home Management and Security 5) Provisioning and Service configuration 6) Entertainment and information 7) Remote Access
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.1 Broadband connection
|
The user wants to access the Internet from a number of PCs at home, and also can decide to subscribe to new services (e.g. parental control, online audio streaming, etc.) offered by his ISP (Internet Service Provider) or an ASP (Application Service Provider), via email or online. From the service provider point of view, the service must be remotely activated via auto-provisioning, the necessary connectivity including QoS to deliver the service must be guaranteed and there must be the possibility of remotely debugging customer problems. Figure 1 represents an example for this scenario. Network CNG PC PC PC Figure 1: Example of Broadband connection scenario ETSI ETSI TS 185 005 V2.0.0 (2007-07) 8
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.2 Communication Services Support
|
Communication services can be divided at least in three categories: 1) Person-to-Person communication P2P. 2) Person-to-Machine communication P2M. 3) Machine-to-Machine communication M2M.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.2.1 Person-to-Person (P2P) Communication
|
P2P communication is intended as voice or voice/video communication and it could be performed in three different ways: • Voice / VoIP with IP phone. • Voice over IP with legacy analogue phone. • Video Communication. • Text communication with legacy text telephone. • Computer-originated text communication to PSTN. In the first case, the VoIP phone can be used to make or receive a voice call. In the second, using the voice service is rather easy and is not different from making phone calls via standard PSTN. The supplementary voice services can be used on both lines (call transfer, call hold, etc.) according to the definition of Simulation and Emulation Services in TISPAN. In the third a newly installed video phone can be used to make or receive a video call. The typical supplementary voice services will be available. In the fourth, communication is not different from making a text telephone call via standard PSTN—translation services etc are available. In the fifth, a computer is used as text telephony terminal; when suitable technology is mature, text-to-and-from-voice translation may be done on the computer and a VoIP call made. The service provider must guarantee the necessary connectivity to deliver the voice, voice/video, or text service, as well as the necessary quality of service. In the first case, the VoIP phone can be used to make or receive a voice call. In the second, using the voice service is rather easy and is not different from making phone calls via standard PSTN. The supplementary voice services can be used on both lines (call transfer, call hold, etc.) according to the definition of Simulation and Emulation Services in TISPAN. In the third a newly installed video phone can be used to make or receive a video call. The typical supplementary voice services will be available. The service provider must guarantee the necessary connectivity to deliver the voice or voice/video service, as well as the necessary quality of service. Figure 2 represents an example of possible implementation for this scenario. Network CNG POTS IP phone Video phone Figure 2: Example of Communication scenario ETSI ETSI TS 185 005 V2.0.0 (2007-07) 9 With specific reference to the personal communication services, the possibility to use one identity on several terminals as well as to share one terminal with several identities should be supported. In these cases, the Customer Network Gateway could play an active role, according the technical solution chosen. For example it should be possible to use a unique shared public identity (a family identity) to make a call with one of the terminal at home. When the call is direct to the shared public identity all the terminals at home ringing because they are associated at the same shared public identity. Moreover each terminal may have its own public identity (different from family identity) so a call can address directly to it. Figure 3 shows the "shared IMPU" use case as also described in TS 123 228 [2]. Figure 3: Shared public identities use case
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.2.2 Person-to-Machine (P2M) Communication
|
A typical P2M communication use case is, for example remote access of device, where one can access the home media server for uploading or downloading one's photos remotely, that is mentioned in the remote access service section.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.2.3 Machine-to-Machine (M2M) Communication
|
One of the typical use cases for M2M communication from the customer network and NGN standpoints is the automatic electricity meter reading business. The electricity meter is a CND that is attached to the CNG, and the electricity charging server is an IMS enable device that is connected to the NGN service layer. With this approach, network operators can reuse the NGN security functions in CNG and electricity charging server for delivering secure data service between customers' electricity meters and electricity companies' charging servers (that can be hosted by the operator, IT provider or the electricity company itself depending on the business model).
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.3 Home worker
|
In this use case various members of a family simultaneously use the broadband infrastructure. In particular, parents are connected to their respective corporate intranets over a secure link and perform a number of actions, including upload and download of documents, placing VoIP calls for work. They expect to have a simple mechanism by which they can easily switch from private to corporate calls (billing will be different). While the parents are working, children must be able to watch video streaming, or browse the Internet. All these simultaneous applications have to live up to the experiential expectations of the user. Hence the necessary priorities have to be taken into account within the customer network environment.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.4 Home Management and Security
|
Two different sub cases are proposed for this category: the first is related to the access/parental control, the second to the personal monitoring. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 10
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.4.1 Access control
|
The user wants to be sure that she has an overview on the children communication and entertainment activities and be able to control the access to these activities. An access control service can be built up with the following capabilities: Content check, Cost check, Usage check, Time check. The user must have the capability to check the configuration of the access control service via a terminal (e.g. a PC) and changes of the parental control configurations can be only performed by himself as administrator. From the service provider point of view, a number of mechanisms for service activation, billing and web based consumer support in case of problems must be ensured.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.4.2 Personal Monitoring
|
In this use case the user must be able to access images coming from a camera installed at home, via an Internet browser on a remote PC or/and via a mobile Internet connection. Fast internet access with Wi-Fi service is enabled in the house and IP Camera has a build-in web server and can act PC independent. The camera must have an indicator showing when it is active, perceivable even if only a single image is transmitted. No fixed IP address is required to remotely access the camera (Dynamic DNS service included). A security mode can allow the camera to react on motion detection and send an alert via an e-mail to one or more addresses with a few seconds of images attached, or via SMS. The service provider must ensure the actual reachability of the camera installed at home, even if the installation has been performed directly by the user himself.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.5 Provisioning and service configuration
|
A set of parameters shall be configured on UE (device that contains the SIP UA) to access to IMS network. These parameters should be provisioned on UE in order to make seamless for the user the UE registration to IMS network (enabling UE automatic registration on start-up procedure). In addition, they should be "portable", thus meaning that user can assign his/her public identity (and the associated parameters) to a different UE. In case the UE is loaded with UICC both requirements are satisfied: Use Case: First Provisioning (Manual) • The user has a new device. • The user subscribes an IMS service. • Network Operator provides the user with the information needed to access to IMS network through an off-line channel (i.e.: by e-mail, fax, etc.). • The user fills in manually the configuration parameter fields on his/her device with needed information to access to the IMS network (e.g. IMPU, IMPI, Shared keys, Home Network Domain or P-CSCF IP Address, etc.). • This kind of customer experience may be suitable for softphone, but it's quite difficult on a hard phone. Use Case: First Provisioning (automatic) • The user has a new device. • The user subscribes an IMS service. • A Network Configuration Service must be able to send configuration parameters to access to the IMS network (e.g. IMPU, IMPI, Shared keys, Home Network Domain or P-CSCF IP Address, etc.), to the CND when the user starts up the device. • No manual insertion by the user is needed. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 11 Use Case: Manual Re-Configuration • The user is already using a specific device associated to a specific public identity. He wants/needs to: - use a different device with the same public identity, or - assign a different Public Identity to the same device. • As for the previous case relative to the provisioning phase, the user can manually configure the device with the public ID and the associated configuration parameters. • If the user wants/needs to use the same parameters (public identity, username and password) on a different device, the CND to which these parameters have been previously assigned shall be deregistered, in order to de- assign association device-configuration parameters. Use Case: Self Re-Configuration Service The user is already using a specific device associated to a specific public identity. He wants/needs to: use a different device with the same public identity, or assign a different public identity to the same device. • The user accesses a Self Configuration Service through a web interface and/or device-specific menus, to: - Select the device to which assign the public identity and the associated IMS configuration parameter. - Select the public identity, and the associated configuration parameter, to be assigned to a specific device. Based on user' s selection the device is automatically configured by the network.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.6 Entertainment and information
|
A number of different use cases can be proposed for this category. Here three specific scenarios are proposed, the first related to the broadcast IPTV service usage inside the house, the second to the access to contents stored in a media gateway, the third to gaming scenarios.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.6.1 IPTV - Broadcast TV Service
|
The user is able to view access channels and other content from his broadcast IPTV service using his television connected to this set-top-box. A TV is directly connected to the STB. The STB is intended as separate device not integrated in the CNG. It is assumed that in most cases the television is directly connected to the set-top box. Also, he The user may choose to have a range of viewing devices within the home, not just a single television directly connected to the set-top-box so that family members should be able to view the broadcast IPTV channels and other content from any compatible viewing device within the customer network. The user expects that the IPTV streams within the house will provide a quality picture and experience, so appropriate bandwidth must be dynamically available through the customer network. Figure 4 represents an example of this scenario. Network TV Set top box PC CNG PDA TV Set top box Figure 4: Example of IPTV - Broadcast service ETSI ETSI TS 185 005 V2.0.0 (2007-07) 12 Considering the different situations in terms of service features and type of devices used the IPTV customer scenarios can be categorized in the following way: • "Basic" IPTV usage: media streaming with zapping possibilities (same user experience as for the traditional terrestrial TV): single stream on a CND (i.e. STB connected to a TV). • "Advanced" IPTV usage: media streaming with PVR functionalities (time shifting, video recording etc.), single stream on a CND (i.e. STB connected to a TV) • "Nomadic" basic or advanced IPTV service, including the possibility of redirecting the media flow from a device to another in the CPN environment (but always single stream on CND). • "Multi device" scenarios: single stream usage on multiple devices, either with basic or advanced features. Advanced features should be applied to all connected CND. Single/Multi room situations are included in this scenario, with possible different issues in terms of pure connectivity and QoS (especially when a wireless technology is used). • "Multi service" scenarios: usage of broadcast IPTV + additional concurrent services on the same device (typically, communication services as defined in TS 181 016 (see bibliography): direct communication as in TS 181 006 [3], immediate messaging as described in TS 122 340 [7], notification of incoming calls related to Videotelephony and multimedia telephony services as described in TS 181 001 [4] and TS 181 002 [5]. "Multiple" scenarios allowing multiple IPTV streams on multiple CNDs with basic or advanced functionalities and with or without concurrent services.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.6.2 On demand IPTV services
|
In addition to the broadcast TV flows, the usage of contents that are available upon a specific request user side must be considered. Following the contents of TS 181 016 (see bibliography) this can be performed in different ways: • Pay Per View (PPV): the user can ask for being authorized to have access to a specific content, whose schedule is defined by the service provider, without any specific possibility of interacting with the flow itself (it will be seen as the typical live TV streams). • Content on Demand (CoD): the user can ask for having access to a specific content, with the possibility of controlling when and how it is viewed. It includes the possibility of performing pause, rewind, forward actions on the media flow. A "near CoD" and "push CoD" versions of this service are limiting in some way the possibility of direct intervention user side (mainly about timing) or providing a time separation between the content download and the actual usage phases. • Interactive TV, providing additional bidirectional information flows typically associated to the broadcast IPTV service usage. These information flows can allow the user performing specific actions (for example, voting), ask the user for performing actions (e.g. payment overdue notice) or be simply informational. All these services will be based on an interaction between the CPN and some servers placed in the NGN; specific functionalities must be provided in the customer network gateway and customer network devices, but there can be the possibility of implementing specific functionalities on a separate hardware performing storing, possible transcoding and/or protocol adaptation: this kind of device can be identified as "media gateway" or "application gateway".
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.6.3 IPTV services based on presence
|
A particular case mainly related to the usage of broadcast IPTV contents is the interaction between IPTV and presence information. As defined in TS 181 016 (see bibliography) presence information can be used to optimize specific basic or additional services related to IPTV (for example, personalized EPG and advertising, parental control etc). This must be taken into account when depicting the CPN related requirements from what the CNG and STB functionalities will be derived. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 13
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.6.4 Gaming
|
The user can have access to some game application installed in devoted (i.e. game consoles) or general purpose devices. This can require a connection to a game server or a peer game devices and involves some requirements in terms of user experience (corresponding to low delay and latency from a technical point of view). Also, a number of concurrent applications can be used, for example messaging tools can be used or VoIP sessions can be established in parallel, to allow the users sharing opinions and information during the service usage. Customer devices used for gaming can be mobile and so they can join different customer networks depending on the user's needs.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.1.7 Remote Access
|
When a user is away from its customer network, it is in many situations valuable to be able to access services on the customer network. Remote access can be divided into two categories: access of devices and access of services. Example of first category is uploading the latest vacation pictures or films to a storage server on the customer network or when a user sends a message to the home to turn on/off a device. Example of the second category includes accessing a surveillance camera service to check that everything is in order. A use case in the same theme may be when the end-user accesses content stored on its customer network while being away at a friend's house or similar. Another, more futuristic, use case may be when an end-user wants to access its subscribed broadcast media channels when away from its customer network(s). The CNG shall provide secure access control and connectivity to the customer network, assisted by standard NGN functions. The customer network may be reached from the open Internet, but by accessing it through the operator managed IMS/NGN, where for example NGN-assisted QoS can be applied for critical parts of the network path, an enhancement of the end-user experience may be achieved. Figure 5 outlines the remote access use case, exemplified with the DLNA concept. Remote Access Protocol Plane CPN 2. Remote access messages NGN Network NGN 1. NGN 1. NGN Message Control Plane NGN CSCF CNG Figure 5: Schematic view of Remote access architecture
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.2 Overview of terminals/equipment supported
|
The overview of possible equipment to be considered is contained in TS 185 006 (see bibliography).
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3 Requirements derived from service scenarios
|
A number of detailed requirements for the customer networks can be derived from the use case illustrated in the previous clauses. Requirements are split in: • General requirements on Customer Network Gateway. • General requirements on Customer Devices. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 14 • Specific Requirements for communication services support. • Specific Requirements for entertainment and information services. • Specific security requirements. • Specific QoS requirements. • Specific management requirements.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3.1 General Requirements on Customer Network Gateway
|
1) The CNG shall be equipped with a WAN interface towards the NGN, implementing layer 1 and 2 functionalities ("one-box" solution). 2) LAN interfaces. The CNG shall be equipped with at least one Ethernet (minimum 100 Mbit/s) is interface. Optional interfaces could be present, e.g.: wireless LAN Wi-Fi Alliance certified, Powerlines, Plastic Optical Fiber, USB device and/or host, one or more FXS for analog telephony, DECT Cat-iq. 3) The CNG shall support both routed and bridged modes of operation. 4) The CNG shall support direct intra-LAN connectivity between any appropriate pair of devices on the Customer Premises Network. 5) The CNG shall support different IP address schemes and subnets on the same physical LAN port, and on different LAN ports, irrespective of routed or bridged mode of operation, allowing the direct addressability of CNDs from the NGN side in relation to data plane, control plane and management plane flows. 6) The CNG and devices shall support mechanisms to identify and share information about the customer network devices (e.g. type of device and basic capabilities, services supported etc.) within the customer environment. Some of this information can be used locally, while a subset of it can be forwarded to the NGN. 7) The CNG shall support use of one user identity on several terminals as well as to share one terminal with several identities. 8) The CNG and the Customer Network shall support the NGN services usage (e.g. voice communications, video communications, IPTV, entertainment, …) allowing the connection to the right service control platforms. 9) The CNG should support or not prevent redirection of IP Multimedia sessions, as defined by TS 181 005 [1], independently from the type of device used (NGN terminal or other CND). 10) The CNG and the Customer Network shall assure the confidentiality, the integrity of signalling/control/media and management flows. 11) The CNG and the Customer Network shall provide the opportunity for a customer network administrator to perform service and network-related configuration. According to the service/network provider choices, the CNG and Customer Network may prevent - user initiated modification of network and service related parameters. 12) The CNG should negotiate session parameters (bandwidth, screen resolution, codecs…) with the NGN transparently to the user. 13) The CPN shall support secure remote access control, based on NGN network functions. 14) The CNG shall allow the customer remote access to a CND in the Customer Network, for example a surveillance video camera. 15) Standard NGN authentication, routing and connectivity should be used to establish remote access connectivity. 16) The CNG may allow secure dynamic firewall opening for remote access devices based on NGN authentication functions. 17) The CPN may support encrypted communication with remote access devices, and the encrypted communication can be terminated either at the CNG or CND. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 15 18) The CNG may act as a proxy for handling messages (requests and responses) related to the remote access scenarios to and from the home. 19) The CNG may support mechanisms supporting nomadism of the users and their subscribed services from one physical customer environment to another.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3.2 General requirements on Customer Network Devices
|
20) A CND, as defined in clause 3, may use the CNG to access NGN services. 21) Authorized users shall be able to access NGN-based services using any NGN supported home device. 22) Both IMS capable devices with or without UICC and non-IMS capable devices without UICC shall be supported. 23) If the CND contains an ISIM/UICC, it shall support the AKA authentication method (TS 187 001 [8]) 24) If the CND does not contain an ISIM/UICC, it shall support the HTTP Digest authentication or the NBA (TS 187 001 [8]). 25) The CND shall provide its private identity, when it requires the registration to the network. 26) In order to support the NGN services and intra-CPN communications, all the CNDs in the CPN shall be addressable directly or by the mean of the CNG using L2/L3 mechanisms. 27) The CND should support protocols for remote access management. 28) The CND should support protocol for local authentication in CPN/CNG. 29) The CND shall support protocols to process the media. 30) The CND shall support protocol to access the NGN service layer platforms. 31) The CND shall support protocols to access Self Configuration application (as defined in clause 4.1). 32) The CND shall be able to download and install client application services. 33) The CND should be able to communicate its services related capabilities to the CNG. 34) The CND should be able to support one or more codecs for communication services (as defined by TS 181 005 [1]).
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3.3 Specific Requirements for communication services support
|
35) Multiple identities should be supported within the same subscription. Personal service profiles per each identity within the same subscription should be supported. A shared public identity on several terminals, with different private identities, shall be supported (shared IMPU). 36) Multiple public identities on the same terminal shall be supported. 37) The CNG shall support a mechanism allowing the support of call forking towards customer non-IMS capable devices and shall able to store information related to private identities of non-IMS capable CNDs. 38) The CNG shall support a mechanism allowing the support of call forwarding toward non-IMS capable CNDs. 39) The CNG shall support intra-CPN communication between IMS and non-IMS capable CNDs. 40 The customer environment (CNG and/or CNDs) should support a mechanism to allow service roaming (i.e. using the same CND in two different CPNs declaring the same public identity). Supporting this scenario for non IMS capable CNDs is still to be discussed. 41) The NGN network should be provided with a CND location information. 42) Codec requirements and capabilities for the User Equipment (including the CNG) are already defined in TS 181 005 [1] which describes service requirements and capabilities for the TISPAN NGN. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 16
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3.4 Specific Requirements for entertainment and information services
|
43) The CNG shall support mechanisms for managing IPTV flows provided both in unicast and multicast mode. 44) In case of multicast flows the CNG shall keep a record of which devices are subscribed to which multicast group. 45) An IPTV media flow shall be terminated by a STB or by a specific device called "media gateway" (or "application gateway"). The CNG shall not terminate any IPTV flow by itself. 46) The CNG shall support the connection to a STB (or media gateway) both in a bridged or in a routed mode of operation. 47) Depending on the operation mode chosen (bridged or touted) and on the type of flow treated (unicast or multicast) the CNG shall forward packets only to the physical interfaces which are connected to devices interested to the IPTV flow. 48) In case of multicast streams the CNG should support proxy functionalities to optimize the management of information related to signalling. 49) CNG shall perform a link layer multicast to unicast translation if the STB or media gateway are connected using customer network technologies not supporting multicast flows (e.g. powerlines, wireless). 50) STB or media gateways should be equipped with a programmable open API allowing the implementation of specific service logics. 51) Functionalities related to Electronic Programming Guide and DRM management shall be implemented in STB or media gateway and not in CNG. 52) Media flows (data plane) transcoding shall be performed by STB or media gateway and not by the CNG. 53) Protocols adaptation for control plane or management plane may be performed by CNG. 54) Presence related information shall be sent to the NGN by the STB or the CNG (depending on the specific architectural choices, CNG could manage the presence related information on behalf of the specific device used) to enable specific services tailored on the specific user's profile.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3.5 Specific Security requirements
|
55) The CNG shall support mechanisms to authenticate itself to the NGN for connectivity purposes. 56) The CNG shall support mechanisms to authenticate itself to the NGN for service usage purposes. 57) The CNG shall support mechanisms to authenticate CNDs to the NGN for service usage purposes if they are not able to fully support the related procedures in an autonomous way. 58) The CNG shall support mechanisms for authentication of wireless CNDs for local connectivity. Similar mechanisms may be also implemented for non-wireless devices. 59) The CNG and CPN shall support mechanisms that prevent access to the network by unauthorized users. 60) The capacity of the authorized entities should depend on the security policies defined by the service providers, managing the CNG. 61) The CNG and the CPN shall implement mechanisms to limit the visibility of the WAN side network and resources to authorized entities. 62) The diagnostic operations on the CPN by an operator shall be performed in accordance with rules protecting the users' privacy. 63) CPN environment shall be protected with a stateful firewall function, that may be implemented in the CNG. 64) The CNG and the CPN shall be able to support parental control related functionalities limiting the use of the broadband connection on a user or time basis. Limitations on a content basis may be shared with devoted network servers. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 17
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3.6 Specific QoS requirements
|
65) The CNG and the CPN shall support adequate Quality of Service mechanisms (e.g. prioritize the traffic in the event that there is not sufficient bandwidth in the customer network in order to ensure the correct network performances to each traffic flow). To achieve this objective a number of functionalities shall be supported by CNG and/or CNDs, as defined in the following bullets. The following set of requirements is defined adopting as a reference the Home Gateway Initiative (HGI) Release 1 Specification mentioned in clause 2 [6]. 66) The NGN network QoS functions shall be possible to use to enhance the end-user experience. 67) The CNG shall classify packets entering the CPN through its WAN interface (downstream direction) according to a number of predefined priorities. Classification can be done on the basis of different layer 2 and/or layer 3 parameters. 68) The number of possible values defining the packet priority and, by consequence, the number of queues managed in the downstream direction shall be coherent with the number of concurrent services (data, communication, entertainment) to be treated and supported. 69) When forwarding packets from the WAN interface to the customer network, the CNG shall perform one of the following three actions, depending on the classification results: manage a number of queues corresponding to the different priorities detected in the classification phase for each packet processed, send the packets to some internal buffers or simply drop the packet. 70) The CNG shall classify packets coming from the CPN through its LAN interfaces (upstream direction) according to a number of predefined priorities. Classification can be done on the basis of different layer 2 and/or layer 3 parameters. 71) The number of possible values defining the packet priority and, by consequence, the number of queues managed in the upstream direction shall be coherent with the number of concurrent services (data, communication, entertainment) to be treated and supported. 72) When forwarding packets from the customer network to the WAN interface, the CNG shall manage a number of queues corresponding to the different priorities detected in the classification phase for each packet processed. 73) The CNG shall be able to classify intra-LAN traffic that is simply bridged by the CNG itself within the CPN. 74) Traffic marking: depending on what are the parameters used to perform classification, CNDs or CNG itself on behalf of the CNDs shall be able to modify the packets' priority. 75) In case of huge amount of traffic in upstream or downstream directions, a congestion management mechanism shall be implemented in the CNG to minimize the impact from the user experience point of view. 76) In case of managed services, QoS rules applied by CNG shall be configurable by a remote management system. 77) In case of unmanaged services, user shall be able to access a QoS configuration function implemented in the CNG.
|
1d84fce3a470e98ffaf2db0ceda27996
|
185 005
|
4.3.7 Specific Management requirements
|
78) CNG shall be equipped with an application client to be remotely manageable by the service providers for configuration, monitoring, firmware upgrade purposes. In case of multiple service providers multiple clients configuring different sets of parameters (for example referring to different services) may be present. A single parameter can be modified by a single client only. 79) It shall be possible to configure the CNG (e.g. firmware downloading) according to the subscribed services. This operation may be performed when the CNG is connected to the network for the first time, for each new service subscription/modification, or for any technical management (e.g. security, patches, etc.). 80) CNG shall support mechanisms for secure authentication and communication with the remote management system. 81) The CNG shall be associated with a unique Hardware ID to be used for identification NGN side. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 18 82) In case of managed services, the CNG shall support zero-touch provisioning to activate new services, starting from Internet access to voice and video services and shall be remotely manageable. In case of unmanaged services the user shall be able to configure the CNG by himself. 83) The CNG Remote Management requires to manage a specific set of parameters. At least the following list of parameters shall be available: Customer Identification, Physical Line Identification, list of subscribed services, CNG IP address. 84) For the CNG management it is recommended to use a single protocol, so as to minimize the complexity and the cost of the service. 85) CNDs connected to the CPN and devoted to specific managed services shall be remotely manageable (e.g. VoIP phones, Video phones, STBs, etc). 86) CNG shall support mechanisms allowing the CNDs remote management when applicable. 87) Protection mechanisms shall be implemented to avoid that a management client could access and modify parameters that is not allow to configure. 88) The CPN (trough CNDs and/or CNG) shall support manual configuration to insert information to access IMS network (e.g. IMPU, IMPI, Shared keys, Home Network Domain or P-CSCF IP Address, etc.). 89) The CND directly or through the CNG must be able to access to Network Configuration Service Function avoiding any user interaction. (and so the Network Configuration Server should be able to upload different parameter related to service subscription). 90) The CND should be able to support bootstrap capabilities in order to retrieve network configuration data to connect the NGN. 91) The CND/CNG shall support a mechanism allowing the user to manually modify the association between a public identity (e.g. phone number) and a specific private identity corresponding to a single customer device not provided with a UICC. 92) The CPN (CND and/or CNG) shall support a method to access a Self Configuration Server. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 19 Annex A (informative): Bibliography ETSI TS 185 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); TISPAN Customer Devices architecture and interfaces". ETSI TS 181 016: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Requirements to integrate NGN services and IPTV". ETSI ETSI TS 185 005 V2.0.0 (2007-07) 20 History Document history V2.0.0 July 2007 Publication
|
049271446448601336483ab2574d528a
|
185 003
|
1 Scope
|
The present document provides an overview of Customer Network Gateway (CNG) functional architecture and reference points and the way it interacts with an NGN, as described in ETSI TISPAN Release 1 and Release 2 standards (see ES 282 001 [1]). The present document describes architectural building blocks to be included in the CNG to support the interworking with an NGN, both at the transfer, transport and service layers. It also defines the reference points between the CNG internal architectural blocks involved and a CND. The WG5 does not address the layer 1 issues, as such studies refer to the AT&TM Group.
|
049271446448601336483ab2574d528a
|
185 003
|
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.
|
049271446448601336483ab2574d528a
|
185 003
|
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 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [3] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [4] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". [5] 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 003 V2.3.1 (2009-06) 7 [6] ETSI TS 182 012: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [7] ETSI TS 183 019: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment; User-Network Interface Protocol Definitions". [8] IETF RFC 3261: "SIP: Session Initiation Protocol". [9] 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)". [10] IETF RFC 2131: "Dynamic Host Configuration Protocol". [11] 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)". [12] ETSI TS 185 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Devices architecture and Reference Points". [13] 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". [14] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication".
|
049271446448601336483ab2574d528a
|
185 003
|
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 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Analysis of protocols for customer networks connected to TISPAN NGN". [i.2] ETSI TR 185 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); High level customer network architectures". [i.3] Broadband Forum TR-069: "CPE WAN Management Protocol". [i.4] Broadband Forum TR-098: "Data Model for TR-069". [i.5] Broadband Forum TR-104: "Provisioning Parameters for VoIP CPE". [i.6] 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". [i.7] ETSI TR 180 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Release 1; Release definition". ETSI ETSI TS 185 003 V2.3.1 (2009-06) 8
|
049271446448601336483ab2574d528a
|
185 003
|
3 Definitions and abbreviations
| |
049271446448601336483ab2574d528a
|
185 003
|
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: 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). 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 to 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. IMS CND: CND whose external behaviour complies with the IMS specifications NOTE: See [1], [2], [3], [4] and [5]. "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. Non-IMS SIP IETF CND: SIP-based CND whose external behaviour conforms to RFC 3261 [8] but do not fully conform to the IMS specifications Many scenarios are expected to provide one service from a service provider to a customer device (case of multiple service providers, one or several CNG, etc.). They are presented within the TR 185 004 [i.2] and TS 185 005 [i.6].
|
049271446448601336483ab2574d528a
|
185 003
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACS Auto-Configuration Server AKA Authentication and Key Agreement ALG Application Layer Gateway A-MGF Access-Media Gateway Function ARF Access Relay Function B2BUA Back-to-Back User Agent BC Broadcast Content CLF Connectivity session Location and repository Function CND Customer Network Device CNG Customer Network Gateway CNG-ACF CNG-Admission Control Function CNG-AtF CNG-Attachment Function ETSI ETSI TS 185 003 V2.3.1 (2009-06) 9 CNG-AuF CNG-Authentication Function CNGCF CNG Configuration Function CNG-CMF CNG-Configuration and Maintenance Function CNG-CSMF CNG- Communication Services Media 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 CoD Content on Demand CPN Customer Premises Network DHCP Dynamic Host Configuration Protocol NOTE: http://www.ietf.org/rfc/rfc3235.txt?number=2131 DLNA Digital Living Network Alliance EF Elementary Files ETH ETHernet IGMP Internet Group Multicast Protocol IMPU IMS PUblic identity IMS IP Multimedia Subsystem IP Internet Protocol IPTV IP TeleVision ISIM IMS Subscriber Identity Module MGC Media Gateway Controller NACF Network Access Configuration Function NAPT Network Address and Port Translation NOTE: http://www.ietf.org/rfc/rfc3235.txt?number=3235 NASS Network Attachment Subsystem NAT Network Address Translation NDN Next Generation Network P-CSCF Proxy Call Session Control Function PLT Power-Line Telecommunication RADA Remote Access Discovery Agent RATA Remote Access Transport Agent RTSP Real Time Streaming Protocol SDP Session Data Protocol SIP Session Initiation Protocol SSID Service Set IDentifier UE User Equipment UICC Universal Integrated Circuit Card VGCF Voice Gateway Control Function VoIP Voice over IP
|
049271446448601336483ab2574d528a
|
185 003
|
4 The CNG Architecture
| |
049271446448601336483ab2574d528a
|
185 003
|
4.1 Introduction
|
The following clauses present the functional entities for the CNG. Examples of Customer Network Devices may be connected to the CNG: a) Analogue phones connected through the CNG to the NGN network. b) IMS Customer Network Devices connected through a CNG to the NGN network [5]. c) Non IMS SIP IETF Customer Network Devices [7]. d) ISDN Customer Network Devices through the CNG to the NGN network. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 10 Different types of Customer Network Devices may be involved in Intra CPN communication through a CNG. The list of Customer Network Devices which are likely to be connected to the CNG is provided by the TS 185 006 [12]. The general overview of the CPN Architecture is provided by the TR 185 004 [i.2]. The CNG functional entities are described in the following parts of the document, as well as the reference points between each function.
|
049271446448601336483ab2574d528a
|
185 003
|
4.2 CPN and NGN side requirements
|
The list of the CNG requirements is provided by the TS 185 005 [i.6]. specification for Service requirements and capabilities for customer networks connected to TISPAN NGN.
|
049271446448601336483ab2574d528a
|
185 003
|
4.2.1 Analogue phone connected to the NGN through a CNG
|
In this case, the CNG includes all the CPN functionalities necessary to fulfill a service between the analogue phone and the NGN, as shown in figure 1. CNG Access node P-CCSF CNGCF ARF Voice Gateway Control Functions (VGCF) Gm e3 e1 Z Customer Network Gateway Analog CND Dj AS Ut CNG-Attachment Function (CNG-AtF) The CPN Environment the NGN and IMS entities ISIM UICC CNG-IPTV Functions (CNG-IPTVF) CNG-Communication Services Media Function (CNG-CSMF) CNG-Configuration & Management Function (CNG-CMF) CNG-Policy Control Function (CNG-PCF) CNG-Location Function (CNG-LF) Z CNG Access node P-CCSF CNGCF ARF Voice Gateway Control Functions (VGCF) Gm e3 e1 Z Customer Network Gateway Analog CND Dj AS Ut CNG-Attachment Function (CNG-AtF) The CPN Environment the NGN and IMS entities ISIM UICC CNG-IPTV Functions (CNG-IPTVF) CNG-Communication Services Media Function (CNG-CSMF) CNG-Configuration & Management Function (CNG-CMF) CNG-Policy Control Function (CNG-PCF) CNG-Location Function (CNG-LF) Z Exchanges inside the CNG Network attachment functions Transport plane functions Service plane and applicative functions Figure 1: Analogue phone connected to the NGN-IMS network through a CNG ETSI ETSI TS 185 003 V2.3.1 (2009-06) 11 4.2.2 IMS Customer Network Device connected to the NGN through a CNG In this case, the Customer Network Device includes all the CPN functionalities necessary to fulfilll a service between itself and the NGN-IMS network, as shown in figure 2: LAN WAN CNG LAN side : the User Equipment WAN side : the NGN and IMS entities P-CSCF CNGCF ARF Gm e3 e1 Customer Network Gateway CNG-User Interface Function (CNG-UIF) e3' e1' Access node Dj CND-SIP UA CND-NAPT Traversal Function (CND-NTF) CND-Communication Services Media Function (CND-CSMF) u CNG-Location Function (CNG-LF) AS Ut Ut au CNG-Attachment Function (CNG-AtF) CND CNG-Plug and Play Function (CNG-PPF) CND-Plug and Play Function (CND-PPF) C CND-Local Authentication Function (CND-LAF) CND-Configuration & Management Function (CND-CMF) CND-Attachment Function (CND-AtF) CND-Self Provisioning (CND-SP) Customer Application Customer Application Customer Application Gm' CNG-Authentication Function (CNG-AuF) CNG-Policy Control Function (CNG-PCF) CNG-Configuration & Management Function (CNG-CMF) CNG-AdmissionControlFunction (CNG-ACF) Gm CNG-NAPT and Firewall Function (CNG-NFF) e3 B2BUA CNG- SIP proxy B2BUA SIP Proxy Registrar Customer Network Device e1 ISIM UICC UICC ISIM CNG-IPTV Functions (CNG-IPTVF) Gm LAN WAN CNG LAN side : the User Equipment WAN side : the NGN and IMS entities P-CSCF CNGCF ARF Gm e3 e1 Customer Network Gateway CNG-User Interface Function (CNG-UIF) e3' e1' Access node Dj CND-SIP UA CND-NAPT Traversal Function (CND-NTF) CND-Communication Services Media Function (CND-CSMF) u CNG-Location Function (CNG-LF) AS Ut Ut au CNG-Attachment Function (CNG-AtF) CND CNG-Plug and Play Function (CNG-PPF) CND-Plug and Play Function (CND-PPF) C CND-Local Authentication Function (CND-LAF) CND-Configuration & Management Function (CND-CMF) CND-Attachment Function (CND-AtF) CND-Self Provisioning (CND-SP) Customer Application Customer Application Customer Application Gm' CNG-Authentication Function (CNG-AuF) CNG-Policy Control Function (CNG-PCF) CNG-Configuration & Management Function (CNG-CMF) CNG-AdmissionControlFunction (CNG-ACF) Gm CNG-NAPT and Firewall Function (CNG-NFF) e3 B2BUA CNG- SIP proxy B2BUA SIP Proxy Registrar Customer Network Device e1 ISIM UICC UICC ISIM CNG-IPTV Functions (CNG-IPTVF) Gm Exchanges inside the CNG Network attachment functions Transport plane functions Service plane and applicative functions NOTE: The IMS CND functions are described within TS 185 006 [12] dedicated to Customer Network Devices. Figure 2: IMS Customer Network Device connected to the NGN-IMS network through a CNG ETSI ETSI TS 185 003 V2.3.1 (2009-06) 12 4.2.3 SIP-non IMS Customer Network Device connected to the NGN through a CNG In this case, the Customer Network Gateway includes all the CPN functionalities necessary to fulfilll a service between itself and the NGN-IMS network, as shown in figure 3. CNG LAN side : the User Equipment WAN side : the NGN and IMS entities P -CCSF CNGCF ARF G m e3 e1 Customer Network Gateway CNG -User Interface Function (CNG - UIF) e3' e 1 ' Access node Dj CND - SIP UA CND -NAPT Traversal Function (CND -NTF) CND -Communication Services Media Function (CND -CSMF) u CNG -Location Function (CNG -LF) AS U t U t a u CNG -Attachment Function (CNG - AtF) CND CNG -Plug and Play Function (CNG -PPF) CND -Plug and Play Function (CND -PPF) C CND - Local Authentication Function (CND -LAF) CND-Configuration & Management Function (CND -CMF) CND - Attachment Function (CND - AtF) CND -Self Provisioning (CND - SP) Customer Application Customer Application Customer Application G m ' CNG -Authentication Function (CNG -AuF ) CNG - Policy Control Function (CNG -PCF) CNG - Configuration & Management Function (CNG -CMF) CNG -AdmissionControlFunction (CNG -ACF) G m CNG -NAPT and Firewall Function (CNG -NFF) e3 B2BUA CNG - SIP proxy B2BUA SIP Proxy Registrar Customer Network Device e 1 ISIM UICC UICC ISIM CNG -IPTV Functions (CNG -IPTVF) G m Dj' CNG LAN side : the User Equipment WAN side : the NGN and IMS entities P -CCSF CNGCF ARF G m e3 e1 Customer Network Gateway CNG -User Interface Function (CNG - UIF) e3' e 1 ' Access node Dj CND - SIP UA CND -NAPT Traversal Function (CND -NTF) CND -Communication Services Media Function (CND -CSMF) u CNG -Location Function (CNG -LF) AS U t U t a u CNG -Attachment Function (CNG - AtF) CND CNG -Plug and Play Function (CNG -PPF) CND -Plug and Play Function (CND -PPF) C CND - Local Authentication Function (CND -LAF) CND-Configuration & Management Function (CND -CMF) CND - Attachment Function (CND - AtF) CND -Self Provisioning (CND - SP) Customer Application Customer Application Customer Application G m ' CNG -Authentication Function (CNG -AuF ) CNG - Policy Control Function (CNG -PCF) CNG - Configuration & Management Function (CNG -CMF) CNG -AdmissionControlFunction (CNG -ACF) G m CNG -NAPT and Firewall Function (CNG -NFF) e3 B2BUA CNG - SIP proxy B2BUA SIP Proxy Registrar Customer Network Device e 1 ISIM UICC UICC ISIM CNG -IPTV Functions (CNG -IPTVF) G m Dj' Exchanges inside the CNG Network attachment functions Transport plane functions Service plane and applicative functions Figure 3: Non IMS SIP Customer Network Device connected to the NGN-IMS network through a CNG In this case Gm' is used, the SIP proxy B2BUA shall perform an adaptation of the non-IMS SIP profile from a CND which requests for an IMS session. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 13
|
049271446448601336483ab2574d528a
|
185 003
|
4.3 CNG functions
| |
049271446448601336483ab2574d528a
|
185 003
|
4.3.1 The transfer level functions
| |
049271446448601336483ab2574d528a
|
185 003
|
4.3.1.1 CNG-NFF: CNG-NAPT and Firewall Function
|
The CNG-NFF entity shall provide gate control functionality i.e. dynamic NAPT and firewall functions at the boundary between the CPN and the NGN.
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.2 The transport level functions
| |
049271446448601336483ab2574d528a
|
185 003
|
4.3.2.1 CNG-CSMF: CNG-Communication Services Media Function
|
The CNG-CSMF is the termination point for the access node, it shall perform an adaptation so as to deliver media flows from the NGN network to an analogue or IP Customer Network Device. The CNG-CSMF is used for analogue (or digital in the case of ISDN CNDs) to IP media conversion - in which case it corresponds to the R-MGF identified in ES 282 001 [1] or it is used for IP-IP media traffic. In case the CPN is provided with analogue or ISDN CNDs and the media gateway function is not implemented in the NGN (as an A-MGF, c.f. ES 282 001 [1]), the CNG-CSMF shall be used. As a result, this functionality is recommended.
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.2.2 CNG-IPTVF: CNG-IPTV Function
|
When supporting IPTV services, the CNG shall be able to forward inbound multicast packets only to the physical interfaces connected to devices that have joined the specific multicast group. This mechanism should be implemented acting on layer 2 and layer 3 multicast signalling flows (e.g. IGMP based). The CNG shall be able to perform a link layer multicast to unicast translation, if the CPN segment, which the IPTV CND is connected to, is not able to support multicast; specifically, when sending an IP multicast packet to a host received on an NGN reference point, the CNG can send the packet to the unicast MAC address of the host (contained in the multicast signalling message without any change in the IP destination address). This mechanism is also of interest for example when the IPTV CND is connected to the CNG through Powerlines technology (directly or using ETH-to-PLT bridges).
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.3 The CNG Network Attachment Subsystem entities (CNG-NASS)
| |
049271446448601336483ab2574d528a
|
185 003
|
4.3.3.1 CNG-CMF: CNG-Configuration and Management Function
|
The CNG-CMF shall manage a mutual authentication between the CNGCF and the CNG. The CNG-CMF shall enable the CNG configuration and firmware upgrade. The CNG-CMF entity should enable transmission of configuration information to CNDs, obtained from the CNGCF. As a result the CNG-CMF should be able particularly to store configuration information dedicated to several CND, after sending only one request to the CNGCF. As soon as a CND is connected, the CNG-CMF should be able to deliver configuration parameters to it. Furthermore, the CNG-CMF should allow maintenance of any CPN device (CNG/CND) from the NGN network, through the CND-CMF, that is to say the opportunity to do diagnostic and performance tests too. Functionalities should be added to the CNGCF, whether this latter entity could perform the CPN maintenance. For instance, the CNG-CMF could provide the functionality and reference points of a Broadband Forum Auto Configuration Client (see TR-069 [i.3]). ETSI ETSI TS 185 003 V2.3.1 (2009-06) 14 Moreover, the CNG-CMF may be able to perform management activities related to remote access. The remote access allows the user to access a CND from another device via the Internet through the Gm reference point, and work on it remotely. Some authentication parameters may be stored in a UICC (containing the ISIM).
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.3.2 CNG-AtF: CNG-Attachment Function
|
The CNG-AtF entity shall be responsible for allocation of IP addresses to user premises equipment (CND), and to the CNG from the NACF via the ARF.
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.3.3 CNG-PCF: CNG-Policy Control Function
|
The CNG-PCF may integrate a database containing the access profile. This includes bandwidth and QoS parameters for the CNG Customer Network Device side applications and terminals, which could be configured by a user. For instance, congestion issues within the CPN may be solved defining resources for several SSID.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.