Introduction to the MUSE FMC architecture

1. Introduction to the MUSE FMC architecture Dávid Jochadavid.jocha@ericsson.com Gábor Kovácskovacsg@tmit.bme.hu

2. Topics • MUSE Introduction • FMC Introduction • Use-cases • Requirements • Business Roles • Muse FMC Architecture • Next Sessions

3. What is the objective of the research in MUSE ? Multi service access network from fixed operator’s point of view • that provides secure connectivity • between end-user terminals and edge nodes • in an open, multi-provider environment • at a low cost for every European citizen. Network Service Provider Network Access Provider Access Node Customer Premises First Mile MobileService Provider Aggregation network Edge Node Internet Service Provider Residential Gateway Application Service Provider

4. What is MUSE ? • MUSE is a European consortium funded by EC as part of 6th Framework Programme IST • Strategic objective: “Broadband for All” • Co-operative research of operators, vendors and academia • Studies are driven by requirements from European operators • Addresses medium and long term commercialisation • Output • Research reports • Proof of concept in lab prototypes • Standards contributions (DSLF, ETSI, ITU-T, …) http://www.ist-muse.eu

5. Research Inst. & Universities IBBT Inria TU Eindhoven Budapest University (BUTE) ICCS/NTUA HHI Lund Institute of Technology (LTH) ACREO Univ. Carlos III de Madrid University of Essex Who is in MUSE ? Phase I: 2004-2005 Phase II: 2006-2007 36 partners -100 PY/year System vendors Operators (**) Component vendors SME Aarhus BB society (*) (*) (*) (*) Only in phase I (**) Only in phase II

6. Topics • MUSE Introduction • FMC Introduction • Use-cases • Requirements • Business Roles • Muse FMC Architecture • Next Sessions

7. McGuire’s Law (Law of Mobility) • The value of a product increasewith mobility. • The cost of adding mobility has come down due to Moore’s law and Metacalfe’s law. Computer process power will be doubled every 18 month. • Sprint White paper Value of a network is exponential related to the number of users

8. DSL, Cable, Fiber Today's broadband situation Subscriptions tied to household • Desktop for Internet • Laptop with WLAN • Triple play • Data • Voice • Video

9. Coming soon - Portable & PersonalizedAny service, anywhere, anytime

10. Convergence types • Devices • Access technologies in the devices • Multimedia capabilities • Operators • Access provider: fixed + mobile • Content + access provider • Services • Same environment

11. Opportunity with FMC/multi-access • Multiple access networks used as a competitive advantage • Subscriber offerings • Quadruple-play bundling (data, voice, video + mobility) • New differentiating nomadic services “Whenever, where ever” • Synergies • Maximize usage of same infrastructure for all services • Reuse mobile investments for fixed broadband and vice versa

12. Challenges with multi-access • Access to subscribed services at any location • Personalization of network services, individuals rather than household • Common subscriber management • Ensure service delivery over any access type • Differentiate and control subscriber traffic • Introduction of new unique nomadic services • Service aware handling of subscriber traffic (QoS) • Flexible charging based on service and access type • Multi-standard environment • DSLF, 3GPP, IEEE, WiMAX, ETSI TISPAN • Terminal • Mobility • Hand-over between access technologies • Session continuity • Roaming

13. Mobility (taxonomy) • Nomadism • The ability of the user to change his network access point on moving • Session continuity • The ability of a user or terminal to change the network access point while maintaining the ongoing session • Continuous mobility • The ability of a mobile user/terminal/network to change location while media streams are active • Roaming • Handover

14. Topics • MUSE Introduction • FMC Introduction • Use-cases • Requirements • Business Roles • Muse FMC Architecture • Next Sessions

15. Use Case 1: Part #1 Nomadism with video call Access Access network network RGW RGW S ettop box Photo viewer Videophone Computer Computer Television Jose's home Home of Jose's mother • Use Case Description • Jose starts his parents PC and access the Web portal of this SP, authenticates himself and gets nomadic services. • He then initiates a video over IP call from the PC to his home video capable multimedia phone to let his wife know his whereabouts • Next he will access his media-center (can be in his CPN or at another location), to show the pictures from his daughter’s last birthday, and shows it on the TV screen at his parents home

16. Use Case 1: Part #2 Nomadism with IPTV service upgrade • Use Case Description • After he reached his home an important match started. While watching he receives a call from his friend Manolo asking José to come to his house to watch the match together • When José arrives in Manolo's house he upgrades the TV service using his own subscription to HDTV quality and access the match so that are able to enjoy the match together in HDTV quality. • During this time, Manolo’s girlfriend who is not fond of football, could watch another TV program

17. Use Case 2: Session Continuity with conversational services (Voice and Video over IP) • Use Case Description • Bob’s phone gets out of the reach of the wireless home network, the phone is connected to a WIMAX (or UMTS) base station. • Since bandwidth is more expensive on this network, Bob decides to save money and only keeps the audio channel active. • After reaching his office he transfers the running video call from the mobile terminal (WiMAX, UMTS) to his Notebook connected to a fixed access network

18. Other Use Cases • e-Health • Medical consultant (Eva) visits the patients in their homes • Connects to the medical VPN • Using public / shared private wireless access points

19. Topics • MUSE Introduction • FMC Introduction • Use-cases • Requirements • Business Roles • Muse FMC Architecture • Next Sessions

20. End User Requirements on Services • Convenience and ease of use • Users expect similar interfaces for the services accessed irrespectively of the network in use (fixed or mobile). • Always best connected • Users expect to always be connected at any time and to the best possible access technology and that irrespectively of where and when – even when on the move. • Reliability and security • Users expect reliability in all transactions independent of access and connection quality. The users also expect a high level of security from e.g. spam, fraud, viruses, eavesdropping etc.

21. Nomadic requirements • Nomadism implies ubiquitous access to subscribed services. This could include: • Access from the primary residence (home). • Access from a secondary residence (e.g. summer house). • Access from a neighbour’s or friend’s residence. • Access from the office. • Access using public access (e.g. WiFi hot-spot) • Access using the mobile/cellular network. • Roaming relationship between providers

22. Impact of Use Cases, Requirements 1 • The user should be able to access his/her services from any available network connection. NOMADISM • Authentication is based on credentials. AA • A nomadic user may connect to other user’s residential network, local policies must be considered. POLICY • The user should be allowed to continue his/her services in a different access network. ROAMING • Digital Rights Management may impose several constraints for nomadic services.

23. Impact of Use Cases, Requirements 2 • Media adaptationmay be necessary when a nomadic user or device changes his connection point and the service quality or access characteristics at the new location are different or the codec used is not more supported. • Network must keep security and privacy for both nomadic and local users. SECURITY, PRIVACY • Users and terminals must be addressable at layer 3 in residential networks. FIREWALL

24. Impact of Use Cases, Requirements 3 • Location of the user must be known by the network. EMERGENCY CALL, location based services • The network should support SESSION CONTINUITY. • Charging/billing record may be adjusted depending on the type of access and the bandwidth used. • If service environment supports, a user may use the same service from multiple different locations simultaneously. Multiple access to the same service

25. Topics • MUSE Introduction • FMC Introduction • Use-cases • Requirements • Business Roles • Muse FMC Architecture • Next Sessions

26. Actors and roles in the architecture 1 • Customer: • Starts a service session on a device after authenticated • Has a contract to one or more Packagers with a user profile • May have a home network possibly with public access (public WLAN access point) • Packager: • Maintains user’s policy profile and SLA • Contract delivery to Users (including profile, equipment, Helpdesk etc.) • Service Level Agreements with Connectivity Provider, different service providers, other Packagers • Accounting and billing • IMS

27. Actors and roles in the architecture 2 • Network Service Provider: • Provides the function for Internet services • SLA with Packager • Credentials to Connectivity Provider • Network access parameters to Packager • ~ an ISP in the current terminology without address allocation, like T-Online, DataNet, UPC, TVNET etc. in Hungary • Application Service Provider: • Provides application services to users • SLA with Packager • User credentials, service parameters to Packager on service activation, management and usage • For instance a VoD service

28. Actors and roles in the architecture 3 • Connectivity Provider: • Initial signaling for setting up connections (authentication, IP address allocation) • Policy Decision Point, QoS verification with the SLA • Signaling for end-to-end QoS provisioning • Network Access Provider • Access network connections • Management of residential gateways and user devices • Admission control and resource management • Operator who owns access infrastructure, like T-Com or UPC in Hungary • Regional Network Provider • Interconnects NAPs and NSPs

29. Business responsibilities ASP N User data SLA 1 SLA Packager Packager N N 1 1 Network settings User data 1 1 SLA SLA N N N N CP NSP User data N Network settings SLA N NAP Contract N N Customer

30. Topics • MUSE Introduction • FMC Introduction • Use-cases • Requirements • Business Roles • Muse FMC Architecture • Next Sessions

31. Applications [IMS, ....] Common Services Common Network Functions [AAA, PCF, QoS, HA, .....] Common Functionality Fixed Access Fixed Access 3GPP Network Network Network Access Network Specifics * = Eth, DSL, WiMAX, Access Access Access Access Access WLAN Drop* Drop* Drop* Drop* Drop End User End User End User End User End User End User End User End User Specific High level architecture 1

32. High level architecture 2

33. Jose Jose MUSE Use Case on Nomadism HDTV Access Manolo’s Network TV Service Manager CP A Network ASP A Regional Network AAA Network HDTV Access José´s Network

34. MUSE Use Case on Session Continuity

35. Topics • MUSE Introduction • FMC Introduction • Use-cases • Requirements • Business Roles • Muse FMC Architecture • Next Sessions

36. Summary • Mobility increase value for both provider and end user • MUSE aims to solve from a fixed operator’s perspective • Consensus • Successful demos, lab trials, prototypes • Contribution in standardization • Many technical challenges to be solved • Common architecture • Policy control framework • Session continuity • AA, security • …

37. Backup slides

38. Consensus Standards contributions Exchange of info in same area How is MUSE organised ? SP A Technical Steering and Consensus SP B MMBB SP C FMC SP D Distributed nodes SP E Node consolid. TF1 Access architecture & platforms WP B1 WP C1 WP D1 WP E1 TF2 First mile solutions WP B2 WP C2 (DSL) WP D2 WP E2 (Optical) WP A.3 Techno-Economics WP A.4 GSB Standardisation TF3 ResidentialGateways WP B3 WP C3 WP D3 WP E3 TF4 Lab trials WP B4 WP C4 WP D4 WP E4 Proto and trial of E2E deployment scenarios

39. When are the major milestones ? Phase I Phase II Network architecture Model 1 Architecture spec. for lab trials phase II Network architecture Model 2 MUSE Architecture Reference document Standardisation (DSLF, ETSI, ITU-T) SP A - TF 2004 2005 2006 2007 Lab trials phase I evaluated Network elements phase I tested SP B - D Lab trials phase II evaluated Network elements phase II

40. High-level view of different use cases

41. MUSE FMC Architecture

42. 3GPP Multi-Access Architecture