Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
164
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ETSI TISPAN#11Ter 11tTD245 Sophia Antipolis, 16-20 October 2006 Title High level architecture overview for IMS-based solution for IPTV standardization Source Fraunhofer FOKUS Contact Oliver Friedrich (oliver.friedrich@fokus.fraunhofer.de) Adel Al-Hezmi (adel.al-hezmi@fokus.fraunhofer.de) Prof. Dr. Thomas Magedanz (magedanz@fokus.fraunhofer.de) Dr. Stefan Arbanowski (Arbanowski@fokus.fraunhofer.de) To WG02 WI Ref. (if any) WI02084 IMS based IPTV Document for: Decision Late submission Discussion X Information Abstract: This contribution presents an overall logical architecture of the IMS-based IPTV solution based on the France Telecom contribution [1] from 10ter meeting. The proposed solution takes into account several actors: user, network service provider and content provider and gives a general overview on the interfaces between theses players. 1 Introduction Due to the fact that there is a lack in a general overview for the IMS-based IPTV solution this contribution shall present a first approach to make use of common NGN components and a possible integrating with new IPTV entities. Based on the France Telecom contribution 10tTD149 [1] from TISPAN 10-ter meeting and the presented approach for an IMS-based solution for IPTV in section 4.1 this proposal describes a high level design concept of an IMS-based IPTV Services Subsystem. The framework applies the concepts of fixed mobile convergence developed by TISPAN NGN and 3GPP IMS [2]. Therefore, the proposed logical framework takes into consideration NGN principles of end-to- end design, aligned with existing standards and architectures that address technical requirements. 2 IMS-based IPTV Services Subsystem The IMS-based IPTV Services Subsystem (ISS) targets cross-access convergence of unicast, multicast and broadcast multimedia streaming services as depicted in the next figure. The framework is based on a layering model and copes with all aspects of user, network, service
  • 2. ETSI TISPAN#11Ter 11tTD245 Sophia Antipolis, 16-20 October 2006 and content provider as described in the following subsections. The last subsection gives a general overview on the interfaces between these players. 2.1 Access and Transport Layer The access and transport layer represents network access links and IP core. The access networks; unicast, multicast and broadcast access network can be any wireless or fixed IP link such as UMTS, DVB-H, WLAN, WiMax, DSL or Cable TV. For resource reservation and admission control the access network layer interacts with the RACS that provides link resource feedback to ISS streaming entities to adapt the content based on the current condition and resource usage. The IP core is in charge of data transmission in IP core with quality of service and mobility support. It is also responsible for provisioning of IP addresses and thus it has to interface with the NASS. 2.2 Media Delivery Layer The media delivery layer initiates and terminates IP-based unicast, multicast and broadcast bearer with quality of services support. It is mainly in charge of media processing such as relay stream between various ports (unicast, multicast and broadcast), recording, caching and trans- coding. It is also responsible for resource scheduling, content adaptation, delivery and distribution around the network ISS streaming entities – content distribution may follow the approach suggested by UTStarcom in the first FG IPTV meeting “Architecture Requirement for Distributed IPTV Content Delivery System” [3]. This layer performs all these functions along with the control of the service enabler layer and the IMS-based control layer. In addition, the delivery layer provides multi access convergence to support access mobility and exposes interfaces to heterogeneous access technologies for signalling and data delivery. Application Layer UPSF IMS-based IPTV Services Sub-System User Plane Service Enabler Layer Other IMS-based Control Layer Networks Content Provider Plane Media Delivery Layer NASS RACS Access and Transport Layer Figure 1: High level architecture of an IMS-based IPTV network architecture
  • 3. ETSI TISPAN#11Ter 11tTD245 Sophia Antipolis, 16-20 October 2006 2.3 IMS-based Control Layer The IMS-based control layer controls the entities on the delivery layers such as media server and streaming servers based on the 3GPP IP Multimedia Subsystem [4]. This layer manages the multimedia session and handles the registration of the endpoints. While guaranteeing QoS and single-sing on across all services. It also routes signalling messages to the appropriate application server or triggers the applications based on user profiles maintained in the UPSF. The IMS-based control layer is also in charge of media delivery control function and online/offline charging system. For resource reservation and admission control this layer interacts with the RACS as specified in TISPAN specifications. 2.4 Service Enabler Layer The service enabler layer includes a set of cooperative service enablers that perform intrinsic functions which can interact with other enablers to offer clear capability features towards the service provider, content provider, network operator or user. Several components carry out all related control functions among these four actors. It performs bearer selections based on the available network resources and context information of the user and content source. The service enabler layer also performs service and content provisioning to the user (e.g. electrical program guide for all TV channel and VoD). At the same time it should enable the user to discover and search for any stored content or streaming content that will occur in the future. It guides also the delivering layer for transmitting linear (e.g. live TV) and on-demand streaming (e.g. VoD) content along with the control layer. This layer should also be in charge of additional functions such as security, digital right management, personalisation, etc. These components should act as a bridge between the content provider and content consumer. Following the Open Mobile Alliance approach [5] to design this layer leads to enable all IPTV entities to make use of already existing or future IMS enablers such as presence, messaging, location, digital right management, etc. With this regards, this layer might also make use of the standardization efforts done by the DVB-IP [6] (see our second contribution: “Avoidance of the development of two European standards for IPTV”). Furthermore, to offer the users with more intelligent and personalized IPTV services composed with other service enablers this layer should be accessible from the application layer based on well-known standardized APIs. 2.5 Application Layer The Application layer includes advanced service logic which makes use of the functionality provided by the under layering service enablers to build enhanced and composed services that focus on specific domains or business models making use of the capabilities of the streaming service enabler composed with other IT or classical IMS service enablers such as presence, call control, messaging, etc. The user might interact with the application directly for configuration purpose.
  • 4. ETSI TISPAN#11Ter 11tTD245 Sophia Antipolis, 16-20 October 2006 2.6 Content Provider Plane The content provider plane manages and provides live or stored content. The role of content provider should be dynamic and flexible. This way, a normal user can take the role of a content provider when he/she offers content; e.g. a user wants to stream a live or captured content to his friends or community. With this regards the content provider plane should interface with all layers. Hence the related interfaces have to be defined and specified. 2.7 User Plane The user plane presents the user’s premises (e.g. at home, office, in the car) connected via fixed or mobile access technologies and interact with the system. For enabling the user to require linear or on-demand streaming services he/she has to be an IMS subscriber. Also the user plane should interface with all ISS layers. 2.8 Interfaces There are two classes of interfaces; in-Layer interfaces - interfaces between the layers and in- Plane interfaces - interfaces between the planes. Both classes of interfaces specify different requirements from their various perspectives. On the other hand the interfaces between the user plane or the content plane and the layers should carry out three type of signalling information. The first type is responsible for configuring user’s preferences and user-related service profiles. The second type is in charge of session-related signalling including session establishment, session teardown, media parameters negotiation and user feedback associated to a particular interactive component. The third type encloses media-related control signals such as distribution function and trick functions (e.g. play, pause, fast forwards, back forwards, recording and caching). These kinds of commands are time sensitive and require short transmission delay between user action and service reaction. 3 Proposoal We suggest adding this architecture overview as a first approach in Section 4 High level overview (for an IMS-based IPTV solution) or the corresponding section after the review of WI02048. 4 References [1] Didier BECAM, Bruno CHATRAS; France Telecom; “IP-TV and TISPAN R2 architecture”; ETSI TISPAN#10ter 10tTD149; Sophia Antipolis, June 2006 [2] DTR 00001, Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Release 1 Definition [3] UTStarcom; FOCUS GROUP ON IPTV; FG IPTV-ID-0074; “Architecture Requirement for Distributed IPTV Content Delivery System”; 1st FG IPTV meeting: Geneva, 10-14 July 2006
  • 5. ETSI TISPAN#11Ter 11tTD245 Sophia Antipolis, 16-20 October 2006 [4] 3GPP, TS 23.228. IP Multimedia Subsystem; (2005). www.3gpp.org [5] “OMA Service Environment”, Approved Version 1.0.2 – 08 Aug; 2005, www.openmobilealliance.org [6] ETSI TS 102 034 V1.2.1 Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks