Supporting mobility in the RAN cloud

Transcription

1 Supporting mobility in the RAN cloud Michael Fitch BT 23 rd October 2012

2 Cloud basics On-Demand Self-Service A consumer can provision computing capabilities, such as server time and network storage, automatically as needed Broad Network Access Network capabilities and accessed through mobile phones, tablets, laptops, and workstations Resource Pooling Physical and virtual resources dynamically assigned and reassigned according to consumer demand. Rapid Elasticity Capabilities can be elastically provisioned and released to scale rapidly with demand Pay-As-You-Go Leveraging a metering capability at some level of abstraction appropriate to the type of service Taken mostly from NIST definition of Cloud Computing, special publication , September 2011

3 Service delivery models Infrastructure as a Service (IaaS). Processing, storage, networks etc. The consumer can deploy, manage and run arbitrary software, including operating systems and applications. Platform as a Service (PaaS). Consumer applications created using programming languages, libraries, services, and tools supported by the provider. Software as a Service (SaaS). Consumer uses the provider s applications running on a cloud infrastructure. Accessible from client devices such as a web browser or a programmable interface.

4 Business Relevance / Advantages Network Virtualization Enable Cloud paradigm ( IaaS/NaaS) New business models Easy service deployment High flexibility Easy scalability Optimal resource utilization Energy saving Decentralization of processing and storage resources Cost-reduction due to backhaul capacity savings High QoE (low delay) Access to local or location-based services

5 Mobile architecture reminder IP Services (IMS, Internet etc) Gb SGSN lu S3 S4 MME S5 SGi SAE gateway S6 S7 HLR / HSS PCRF BSC RNC S1 S2 BTS NodeB enodeb Non- 3GPP 2G 3G 4G? WiFi etc System Architecture Evolution Policy Control and Routing Function Serving GPRS Support Node Mobility Management Entity IP Multimedia Subsystem

6 Mobile operators are suffering. 1/3 Difficult deployment/roll-out of new services: IMS is still not rolled out and can only offer traditional operator services Roll-out of new Internet-like operator services (e.g. online storage, VoD) only possible through deployment of dedicated HW at central locations 3 rd party services (e.g. Google caches/docs) can only be hosted in central data centers and based on special arrangements and/or custom solutions Value-added services (e.g. based on location or proximity) is very difficult due to lack of network/service integration Operators lack truly flexible(!) service deployment/delivery platforms Note: Flexibility in terms of no restrictions on protocols (e.g. SIP) or platform specific APIs, but rather on the level of Virtual Machines. 6

7 Mobile operators are suffering. 2/3 High CAPEX/OPEX with disproportionate RoI Due to the explosive growth of mobile data traffic, operator network infrastructure needs to be constantly upgraded Operators are considered mere bit-pipe providers Difficult to dimension network entities deployments Current network entities typically serve a single-purpose Unused resources can not be made available to other services Flexible scale-up of resources/performance (e.g. processing power, memory, etc.) is lacking Operators must carefully plan and dimension current singlepurpose network entities to avoid bottlenecks and high investment for under-utilized equipment 7

8 Mobile operators are suffering. 3/3 Excluded from the revenue value chain of the Internet ecosystem Operators are considered mere bit-pipe providers 3 rd party Service Provider 3 rd party Service Provider Mobile Network Operator API Mobile Network Operator service revenue 8 Subscribers Subscribers

9 9 Ingredients of a successful solution Decentralization of Service Processors / Information Storage Enables operators to offer (network) services close to user Advantages Low delay fast service experience Significant cost saving in backhaul Optimum resource utilization in the backhaul Cloud/Virtualization Technology: Extension of existing infrastructure for multi-purpose use Enables operators to flexibly and dynamically deploy new (network) services E.g. Network as a Service (NaaS), Internet-like operator services, 3 rd party services and Telco services Enable new business models and revenue streams go beyond bit-pipe provider Facilitates more optimal resource utilization Facilitates flexible and dynamic scale-up of resources Lower investment risks

10 1 st Step: Decentralized Mobile Carrier Cloud Decentralize Mobile Cloud Local P+S-GW Local P+S-GW Local P+S-GW LTE LTE LTE LTE P + S GW = PDN Network +Serving Gateway LTE

11 1 st Step: Decentralized Mobile Carrier Cloud Carrier s Cloud Cloud Decentralize services server are provided are provided Mobile close Cloud to close the to the user user acceleration! Move Cloud Nodes close to the Radio Node (i.e. into the Backhaul NW) Local P+S-GW Fast service Local experience Optimal P+S-GW routing Reduction of traffic in backbone/core network Local P+S-GW LTE LTE LTE LTE LTE

12 2 nd Step: Mobile Carrier Network Cloud Virtual Mobile Core Nodes/Gateways Virtualize Mobile Core Nodes and Gateways (e.g. P/S-GWs, MMEs, PCRFs) LTE LTE LTE LTE LTE

13 Mobile Carrier Network Cloud The carrier network cloud allows for IaaS/NaaS Example services Mobile operators can run their Mobile Core Network functions as a network cloud service (e.g. SGSN, GGSN, MMEs, S-GWs) Advantages Single, integrated platform for both end-user and network services Reduced time for network functionality/service development and deployment Reduced infrastructure cost Enables new business models

14 Moving the cloud edge towards the air interface

15 Centralised virtualisation needs fibre to all BSs RRH RRH Fibres Datacentre RRH

16 There is not fibre on all links. RRH RRH Fibres RRH Cloud edge Maybe fibre Maybe not Datacentre - There may be bandwidth restrictions on backhaul links, so what should run at the cloud edge and what in the DC? - How big should clusters be?

17 Virtualising the mobile network - how far? IP Services (IMS, Internet etc) Gb SGSN lu S3 S4 MME S5 SGi SAE gateway S6 S7 HLR / HSS PCRF BSC RNC S1 S2 BTS NodeB enodeb Non- 3GPP

18 Virtualising the mobile network - how far? IP Services (IMS, Internet etc) Gb SGSN lu S3 S4 MME S5 SGi SAE gateway S6 S7 HLR / HSS PCRF BSC RNC S1 S2 BTS NodeB enodeb Non- 3GPP

19 Virtualising the mobile network - how far? IP Services (IMS, Internet etc) Gb SGSN lu S3 S4 MME S5 SGi SAE gateway S6 S7 HLR / HSS PCRF BSC RNC S1 S2 BTS NodeB enodeb Non- 3GPP BBU, antenna processing, radio resource allocation can be moved to a cloud processor

20 SAP 2007 / Envisioned Mobile Cloud Architecture Mobile data services provided by geographically distributed data centers, administrated by the same and/or different cloud providers Distributed Cloud Data Center 1 Data Center 2 Data Center 3 Decentralized Mobile Carrier Network, provided as a cloud service (NaaS) Flat Mobile Network Decentralized Evolved Packet Core P-GW 1 P-GW 2 S-GW 1 S-GW 2 S-GW 3 P-GW 3 Consumer devices Heterogenou UEs, UEs implementing specific application logic that minimizes user s intervention to receive the service

21 Follow Me Cloud Concept Service Mobility Seamless Service Migration Distributed Cloud Data Center 1 Data Center 2 Data Center 3 Flat Mobile Network Consumer devices SAP 2007 / Access to Mobile Cloud Service P-GW 1 S-GW 1 Distributed EPC User Mobility S-GW 2 P-GW 2 Service continuity Material thanks to NEC S-GW 3 P-GW 3

22 Infrastructure Provider Domain IaaS Service Level Request/Negotiation (e.g. to launch of new service/virtual network/platform, increase capacity, change QoS) Customer (e.g. Mobile Service Provider, Virtual MN Operator) IaaS API Cloud Resource Manager (sorts out the right NaaS/PaaS configuration based on customer request) NaaS Configuration Ex. 1 (LTEaaS) NaaS Configuration Ex. 2 (EPCaaS) PGW BBU BBU MME SGW PaaS Configuration Ex. 3 (FMCaaS) FMC FMC Statistical Profiling Of Cloud and NW CN CE-APIs CN NW Probes Configuration Enforcement APIs (e.g., GMPLS, OpenFlow, etc.) CN CN Cloud Probes

23 Research Challenges towards a Decentralized Mobile Carrier Cloud Infrastructure / Network Virtualization Generic node/platform design for network/service cloud What network functionality is needed? How are network functionality (native?) and virtual platform integrated? Service deployment/control API for 3 rd parties (incl. SLAs) Resource management of physical infrastructure/resources Slicing Load balancing / concentration Real-time migration mechanisms Energy saving Decentralization of physical cloud nodes Self-management for decentralized cloud infrastructure Self-organization/optimization for Service Placement & Migration (mobilityaware) Virtualization of mobile network functions (e.g. MME, S-GW, P-GW) Distributed Mobility Management New roaming paradigm

24 Presenting Project

25 Objectives to define / evaluate / design A cloud-based mobile network architecture to bring mobile communication and mobile cloud services to the mobile enduser. Business models that indicate commercial potential A novel virtualisation layer, general monitoring system, and general provisioning across the various domains namely Radio Access Network, Mobile Core Network, and Data Centre. A worked example mobile network (Radio Access + Mobile Core) based on 3GPP LTE/EPC. In particular, BBU-pooling, EPCaaS, and Distributed Mobility Management, will be proven. A platform for services and applications. In particular, Follow- Me Cloud, Cross-Domain QoE, Rating and Charging Test beds among partners to prove above concepts Dissemination etc

26 Overall architecture

27 Macro datacentres will evolve towards micro datacentres

28 vital statistics EC Framework 7 call 8 Integrating Project 16.2m Euro budget with 10.8m funding from EC 36 months from 1 st November partners

29 Mobile cloud workpackages and their interactions WP1: Project Management Application Scenarios & Requirements WP3: Mobile Cloud Infrastructural Foundation Infrastructure Abstraction Management and Control WP2: Reference Scenarios, System Requirements and Business Models Scenarios, Requirements, Business Models, and Overall Architecture WP4: Mobile Network Cloud Mobile Network Cloud Software Components WP6: Integration and Evaluation W5: Mobile Platform Mobile Cloud Computing Platform Archtectural integration of evaluation results WP7: Dissemination, Exploitation, Standardization

30 Co-ordinator Technical co-ordinator

31 Advertisement There is an upcoming " " workshop co-located with IEEE ICC st international Workshop on Mobile Cloud (MCN 2013) June 9-13 in Budapest

32 Thankyou for listening Follow the project at