hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.2 Procedure for Service Configuration | One of the following options should be supported: • An Application Server may implement the role of an XCAP server as described in [15] with standard authentication mechanisms as discussed below. • Standalone XDMS server may be used, in which case Tr interface is re-used between UE and the server. XCAP usage shall comp... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.3 Procedure for Authentication | HTTP Digest [7] is recommended on the Tr interface. MD5 is recommended digest algorithm as defined in [19], MD5 Message Digest Algorithm. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.4 Procedure for Customer Facing IPTV Applications | Application interface is based on http protocol between UE (converged) and ASF (Customer Facing IPTV applications). UE should implement an http [9] compliant web browser with JavaScript support. Special requirement for CSS is to support to enable rendering capabilities. A particular implementation of the Web Browser is... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.5 Procedure for Notifications | The UE may receive notifications from the CFIA using Tr interface between the UE (converged) and IPTV ASF (Customer Facing IPTV applications) via HTTP protocol [9] and either present notification on GUI (Graphical User Interface) or initiate service action or both. The IPTV ASF (CFIA) shall support XML notifications ov... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.6 Procedure for Messaging | The UE may initiate and present received messages via CFIA using Tr interface between UE (converged) and ASF (Customer Facing IPTV applications) via HTTP protocol [9]. The UE may initiate and present received messages through interactions with the Common NGN ASF as described in TS 182 028 [4], annex A. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.7 Procedure for presence information | The UE may receive presence information via CFIA on Tr interface via HTTP protocol [9]. The CFIA may use the Presence User Agent (PUA) as described in [12] and [13]. Alternatively, presence Network Agent as described in [13] may be used for IPTV in the Common NGN ASF as a gateway to the NGN Presence Server (PS). The Pr... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.8 Procedure for Targeted Advertising | NGN Integrated IPTV advertising procedure shall follow procedure for targeted ad insertion, interactive ad insertion and regionalised ad insertion defined in clause 11.10 [4]. NGN Integrated IPTV uses XML schema carried over HTTP on Adx and Ady interfaces, which are defined in annex H "SCTE based targeted advertising a... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.9 Procedure for User Generated Content | The UGC procedures consist of two main phases: UGC creation and watching UGC. The UGC creation procedure comprises four steps as described in [4]. Http is used between UE and CFIA over Tr reference point: • Step 1: Declaration of User Generated Content. • Step 2: Description of User Generated Content information by the... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.10 Procedure for Content Recommendation | The Content and service RecommendationService (CRS) is used for providing recommendations to IPTV users or user groups. The recommendation service may make recommendations to user/groups based on different criteria including user profile, user indicated preferences, current viewing habits, historic user activities as d... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.11 Procedure for Content Bookmarks | An IPTV Content Bookmark service consists of two main steps: • Creation of IPTV Content Bookmark: allows a user to create and store configurable pointers to content, e.g. entire or parts of content (favourite scene) to be able to quickly access the specified content and location. • Retrieval of IPTV Content Bookmark: a... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.12 Procedure for Interactive TV | CFIA shall provide the UE with the selection of Interactive IPTV applications. After selection of Interactive IPTV application (e.g. as for example one from listed in clause 11.19 Interactive TV procedures [4]), the UE sends HTTP request to CFIA via Tr reference point to initiate selected Interactive TV application. Th... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.13 Procedure for Interaction between users | The UE may initiate and received interaction messages between two or among multiple UEs via CFIA using Tr interface between UEs and ASF (Customer Facing IPTV applications) via HTTP protocol [9]. The interaction between UEs may contain HTTP messages with attached XML as described in clause A.5.1. 5.1.14 Procedure for In... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.15 Procedures for Client PVR (UE) | In order to provide Client PVR (c-PVR) service, the UE initially select required content from EPG/BCG via customer facing IPTV application and requests scheduling selected content for recording in the UE. Before the recording start, CFIA shall send notification to the UE based on clause 5.1.5, Procedure for Notificatio... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.16 Procedure for initiation of inter-destination media synchronization | |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.16.1 Synchronization Client (SC) | Upon a request for inter-destination media synchronization, the SC shall send an HTTP GET request to the MSAS. NOTE 1: There are various ways to convey which services require inter-destination media synchronization. This can be signalled via SD&S information (e.g. the BCG/EPG/ESG), through a shared service control sess... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.16.2 Media Synchronization Application Server (MSAS) | Upon receiving an HTTP GET request, the (session-level) MSAS shall be able to deal with the following parameter. • SyncGroupId. The SyncGroupId is received as an URI parameter, see clause 5.1.16.1. If the MSAS cannot retrieve a SyncGroupId parameter from the HTTP message, no further procedures apply. ETSI ETSI TS 183 0... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.17 Procedures for Personalized Channel (UE) | Personalized Channel (PCh) service allows user to define and watch one or multiple pre-configured/scheduled content items as a single (virtual) channel in timeline as user schedule on UE via Tr interface using HTTP protocol. UE shall construct Personalized Channel playlist follow XML schema specified in annex I (XML sc... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6 Procedures using RTSP for NGN integrated IPTV | The Real Time Streaming Protocol [6], or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1 User Equipment (UE) and Control Functions | |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.1 Procedure for BTV service | Usage of RTSP protocol for normal broadcast services without trick modes is not defined in the present document. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.2 Procedure for CoD service | NGN integrated IPTV uses RTSP protocol [6] for control over the delivery of multimedia with real-time properties. Usage should be compliant with TS 102 034 [5] unless specified otherwise. Table 3 illustrates RTSP methods in [6], [5] and NGN integrated IPTV. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 31 Table 3: RTSP methods... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.3 Procedure for BTV with trick modes service | NGN integrated IPTV media broadcast with trick modes session is a service level aggregation of broadcast and on-demand sessions. Combined session flow is shown in clause 11.3 of [4]. Before starting the service, the UE shall request from the Customer facing IPTV applications RTSP URL from where the interactive media de... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.4 Procedure for time-shift TV | In order to provide time-shift TV service, MDF records TV programs available on the broadcast channels. The programs form a part of EPG (BCG) as discussed in clause 5 and should be requested on Tr interface. After selecting time-shifted content from EPG/BCG, the UE requests from the customer facing IPTV applications RT... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.5 Procedure for nPVR | In order to provide nPVR service, the UE initially selected from EPG/BCG via customer facing IPTV application what content should be recorded in the MDF as discussed in clause 5. When the recording has been initiated, UE can request from the customer facing IPTV applications with the available recordings. The applicati... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.6 Procedures for Push CoD (UE, IPTV-C) | Push COD can be initiated by CFIA based on subscription, user profile or defined IPTV service provider offer. When CFIA identified event and time to push content to the UE, it shall send notification to the UE as described in clause 5.1.5 Procedure for Notifications before uploading or streaming of the content to the U... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.7 Procedures for inter-destination media synchronization (SC) | If the SC did not receive the (complete) synchronization information from the CFIA via the procedure in clause 5.1.16.1, the SC shall request this information by including the SyncGroupId in the RTSP SET UP message. The SyncGroupId may be kept empty (value 0) if the SC does not yet know the SyncGroupId. • a=rtcp-xr: gr... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.1.8 Procedures for inter-destination media synchronization | If the MCF receives an RTSP SET UP message containing a SyncGroupId in the SDP, the MCF shall include the following attributes in the SDP it sends to the SC: • a=ssrc:<ssrc-id> <attribute>:<value> as specified in [44]; • a=rtcp:port [nettype space addrtype space connection-address] as specified in [45]; • a=rtcp-xr: gr... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.2 IPTV Control (IPTV-C) | |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 6.2.1 Procedure for BTV service | Usage of RTSP protocol for normal broadcast services without trick modes is not defined in the present document. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 35 |
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 In... |
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... |
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... |
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: • Mul... |
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 ... |
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 dependin... |
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 sup... |
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 conta... |
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), ot... |
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 f... |
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... |
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 (... |
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... |
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... |
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 ext... |
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]... |
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 s... |
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 out... |
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 c... |
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 h... |
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 prese... |
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. • ... |
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 whic... |
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 Serv... |
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... |
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 th... |
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 t... |
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 si... |
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 capab... |
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 m... |
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 "portab... |
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... |
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 ... |
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... |
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)... |
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 se... |
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). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.