2. What is Telco Cloud?
MBB Liquid Core
Przemyslaw Szufarski

3. Agenda 1 2 3 4
Expectations
Solutions
Features
Future

4. Programmable world - Explosion of possibilities
Big Data
Nokia is preparing networks for programmable world: all devices which can benefit from connectivity shall be connected, and internet of things is starting to happen already.
The bulbs controlled over network are just a beginning, in US it is proven that such idea is feasible and it’s a real business actually. We’ll see what is next we can say that networks are not ready for this kind of loads.
Then Big Data – another infrastructure challenge is a computing power for applications used to analyze Big Data. We have successful applications of this technology for Customer Experience Management, where carriers make sure that problems reported by their subscribers do not happen or for Preventive Maintenance, where failures are successfully predicted based on various number of sources.

5. Programmable world - Explosion of possibilities
Smart phones already have a huge impact on how networks are evolving now. New devices are emerging, here are examples of some designed to make public safety services easier.
New devices:
[walkie talki communications with mobile network quality]
[augmented reality]
[virtual reality]
, with various traffic profiles, from easier voice communication through augmented reality to virtual reality, with various demands for Quality of Service will influence future mobile networks

6. Programmable world - Explosion of possibilities
Dynamic adaptation of active resources & network wide multi-layer, multi-technology with centralized management
Offices
Rural
Urban outdoor
Shopping mall t
Currently netowrks are designed for static traffic profiles, e.g. 40% of mobile calls, 40% of SMS 20% internent and can move on. And after that we are informed that internet traffic in Smartphones is in average 70% and almose everyone in the network wants to have it. This may be a problem…
Additionally traffic distribution over time is not static.
Networks should respond to capacity demand dynamically
Also Energy optimization is a challange: If netowrk is not used, it‘s resources should be released and in stand-by mode rather than fully consume power.
public
RF1
RF3
RF2
RF1

7. Key to the programmable world
Elasticity
Massive machine communication
Extreme Mobile Broadband
Critical machine communication
C-U Plane Split
Dynamic resource usage
Telco Cloud towards 2020 and beyond
Geographical Distribution
Configurability
we expect demands for network‘s capacity will grow significantly. Solutions based on „classic“ approach would be too slow and unflexible.
This slide presetns idea of delivering networks specialization to excel in one of the areas: broadband, low latency or massive connectivity. But 3 netowkrs instead of one is not feasible either. We need to merge them back and this is the goal for telco clouds.
To conclude: we expect telco cloud to deliver capability for exterme data rates for broadband subscribers, ability to send data by millions of devices, and to optimize network latency for timing critical services. And network should optimize itself to fit best the demands in those areas.
We wants to achieve this by „Dynamic resource usage“: as small as possible with solid safty margin.
And automated „Configurability“: with a internal logic which allows to reconfigure netowrk for brodband usage during evenings and device communication over nights.
The center of those technol
public

8. 1 2 3 4 Agenda Expectations Solutions Features Future 1.
Telco Clouds are quite fresh concept and I’m going to start my presentation with list of wishes towards telco clouds. And expectations for this technology are quite high. 2.
Then I’m going to describe solution which is of course cloud but it is something more 3.
Then briefly describe quite detailed scenarios which Telco Cloud application needs to handle 4.
And then some concepts for the future 5
And after that we may have a Summary and Q&A
But lets start with the expectations

9. Document ID / v. 0.1 / Life cycle status / Dept. / Author
9/22/2018

10. Nokia prepares the telco cloud environment
Four dimensions
telco cloud
Cloud computing
NFV
SDN
NFV
SDN
C-RAN
Together
C-RAN
Management Applications
Virtualized network functions
Decoupling Control from Forwarding …
forwarding
control
RACS
Orchestration
Cloud App. Manager
NetAct
IMS
MME
Registers
TAS
Cloud enhanced Radio
Cloud Core 1 2 3 4
Programmable Transport
Telco Clouds should convert Networks perception from large number of independent components into one centrally managed component which could be perceived as single a cluster or even a geographically distributed supercomputer (with antenas devices attached here and there.
Components of that solution are:
1. Networks Functions Virtualization: replace HW based infrastructure components by Virtual Network Functions. Network components are SW images running in the shared environment
2. Software Define Networks: define routs in the network via SW algorithms rather than static configuration.
3. Cloud RAN: offload & simplify HW used for Radio Access components. Shift advanced computing into cloud.
And finally smooth consolidation of all components

11. Nokia cloud-based radio architecture
Multi-layered approach – multiple cloud locations – distributed and centralized
Multiple fronthaul types, including Ethernet
Highly scalable, flexible and efficient  
Evolutionary approach
A new architecture for Cloud RAN
Distributed clouds
Centralized clouds
OBSAI, CPRI
OBSAI, CPRI, Ethernet
RRHs
Data center
Ethernet
VNFs:
RAN
EPC
L1+RRHs (intelligent RRHs)
Flexi Zone Micro Pico eNB
Flexi Zone Controller
In this slide we will look further at the Nokia Radio Cloud. Nokia Radio Cloud is our approach to what operators need to do to successfully deploy Cloud RAN concepts and to prepare and roll-out a Telco Cloud platform which is capable of future RAN needs.
The first trait is "multi-layered". This has different meanings.
It means for one to extend the Telco Cloud architecture to reach into the access domain to provide low-latency services as well as be able to meet the stringent requirements which are unique to the RAN functions as cloud applications. Nokia Radio Cloud features both distributed and centralized cloud solutions which are adapted to local deployment conditions and are capable of virtualizing functions of Single RAN, LTE, Wi-F, and future 5G networks. RAN functions can be migrated between clouds as needed, to be effectively bundled as part of an e2e service offering, to offer elasticity and resilience, or as a result of optimizing the network and service performance in the network. The RAN is simply software defined and all clouds are integrated by a common orchestration function and linked to the network management and optimization framework. The clouds are connected to dedicated RAN functions, such as RF heads, by means of existing or new Nokia interface.
"Multi-layered" also links to a flexible deployment of RAN functionalities in both distributed and centralized locations (or split onto both as a hybrid solution) to optimize network performance, enable new radio technologies, and to optimize TCO at the same time.
As part of Nokia Radio Cloud we are also announcing multiple new fronthaul types as supplemtary options to the existing available options. In 2011, Nokia announced Flexi Zone, a hybrid architecture for dense small cell network deployments for better performance and TCO, and in Mobile World Congress this year we demonstrated live a second variant capable of advanced LTE features such as intra-site and inter-site carrier aggregation as well as CoMP, both running on standard Gigabit Ethernet. The cell site solution displayed was an intelligent and Ethernet pluggable and compact RF head that connected to a centrally located IT server. These solution enable centralization benefits with relaxed transport requirements and this is a key for many operators to achieve real Cloud RAN savings. Simultaneously, Nokia's support for Ethernet transport allow operators to fully pursue fixed-mobile convergence opportunities.
Please note that Nokia Radio Cloud still works with existing Telco interface standards and technologies widely deployed in the field.
Nokia Radio Cloud builds on our Single RAN and Centralized RAN solutions being stepping stones to our Radio Cloud solution. Single RAN brings New advanced radio platform development with the Radio Antenna System, with Multi-Radio Access Technologies support with RF Sharing and integrated multi-band radios. Centralized RAN brings centralization with high hardware utilization and improved RRM with coordinated multipoint.
Nokia Radio Cloud offers an evolutionary deployment for operators. The cloud operating model is build for co-existence of both dedicated and virtualized network functions and is able to bring benefits also with Nokia equipment deployed in the field today. Migration to new processing platforms can take place flexibly as network functions are modernized, new network layers are built, or as new service offerings are deployed.
This architecture provides a highly scalable, flexible and efficient cloud-based radio access networks. With Nokia Radio Cloud, processing capacity is allocated from almost anywhere in the network, such as an adjacent cell or a centralized data center, to where it is needed most for coordination and capacity. The multi-layer approach supports distributed and centralized deployments, or a combination of both, using multiple fronthaul types, including Ethernet.

12. Multiservice Backbone
SDN in mobile networks
WAN: On Demand Capacity Allocation, Traffic Optimization, Liquid Apps
Data Center: Automation Service Chaining
Transport SON
Network Orchestrator
Access & Aggregation
WAN SDN Controller
Cloud Application
Manager
Multiservice Backbone
IMS
MME
Registers
TAS
P-GW
Cloud Stack + SDN
Data Center
SDN in the Telco Cloud data center: needed for Nokia VNFs
SDN in WAN: still maturing, mobile specific use cases emerging
Software Defined Networks are broader project, with impact on IP transport in general. Those are part of telco cloud idea as it allows to centralized management of polices for routing, loadbalancing and geo-redundacy. SDN term refers to internal capabilities of data center as well as backbone transport over Wide Area Network.

13. ETSI NFV framework NFV Management and Orchestration Computing Hardware
Storage
Network
Hardware resources
Virtualisation Layer
VNF
Manager(s)
VNF 2
NFV Orchestrator
OSS/BSS
NFVI
VNF 3
VNF 1
Virtual Computing
Virtual Storage
Virtual Network
EMS 2
EMS 3
EMS 1
Service, VNF and Infrastructure Description
Or-Vi
Or-Vnfm
Vi-Vnfm
Os-Ma
Se-Ma
Ve-Vnfm
Nf-Vi
Vn-Nf
Vl-Ha
Virtualized Infrastructure Manager(s)
Main NFV reference points
Execution reference points
Other reference points
From NFV 002, v1.1.1

14. The whole Core in a single box unleashing Cloud
What is “Core in a Box “?
The whole Core in a single box unleashing Cloud
Dedicated HW for each Core functionality
MME
S/P-GW
TAS
Innovation
Squeezing
Fine-tuning
CSCF
HSS
CMD
AAA
PCRF
ePDG
Nokia AirFrame
How telco cloud is beneficial from telco clouds perspective?
Here is example: Infrastructure which requires 9x Racks, huge footprint and HW cost can be placed together in one rack as entry or dedicated network for niche players, such as public safety . This is “Core In a Box”. Nokia is planning to release that solution with a servers based on Intel’s Xeon CPUs in an IT rack. Of course bandwidth for telco clouds is a bit specific and essential for network devices.

15. Growing flexibly with the Cloud
What is service chaining ?
Service chaining controller
Virtual appliances
Chaining
classifier
Content filter
TCP optimizer
CDN
cache
vCPE
Analytics
Media optimizer
Optimized
video
Networking overlay (SDN enabled)
Parental
control
vEnterprise
Customer
care
We believe main change to telco networks will be done via service chaining, where services will be designed and netowrk structure
How programmers community may benefit from that?
A number of network services or applications are visualized here, in terms of an actual service chain that is followed, consisting of a range of service functions, instances and nodes. In a cloud environment, traffic flows are routed to only those service chains and functions that are actually necessary for the treatment of packets related to a particular network service, whereas previously all resources were traversed whether they were needed or not.
For example, if a parental control treatment is needed, the data flow for this particular session is routed via the classifier, content filter, TCP optimizer and CDN cache virtual appliances. For other network services, a different service chain is followed utilizing different functions.
Service chaining within a virtualized environment offers a number of benefits both for the operator and the end-user:
Finer granular traffic classification coupled with per-user policy routing and control results in only the necessary service functions being traversed, to deliver an improved and more responsive experience as well as avoiding over provisioning
Service chain functions scale on demand with no need to size them for peak usage
Increased agility through novel, innovative and personalized network services that are readily available and which offer a differentiated service
Best of breed applications with no constraints by monolithic gateways that can be added in a modular fashion
Network misconfiguration is eliminated resulting in higher availability of network services

16. 1 2 3 4 Agenda Expectations Solutions Features Future 1.
Telco Clouds are quite fresh concept and I’m going to start my presentation with list of wishes towards telco clouds. And expectations for this technology are quite high. 2.
Then I’m going to describe solution which is of course cloud but it is something more 3.
Then briefly describe quite detailed scenarios which Telco Cloud application needs to handle 4.
And then some concepts for the future 5
And after that we may have a Summary and Q&A
But lets start with the expectations

17. Open Eco System and Big Data Analytics
Liquid Applications
CEM
Differentiated experience with speed and interactivity
OSS
SDM
Mobile broadband subscribers
Enhanced multimedia, unique spectator experience
Enterprise and Corporates
Fast and secure local connectivity, real-time shopper engagement
Internet-of-Things and Verticals
Edge analytics for smart cities, connected cars
Core
Security
Regarding use cases for subscribers as well as essential network functions and ubiquitous services, Liquid Applications takes the mobile broadband experience to exciting new levels, both from a network-wide perspective and also in specific locations, for example, stadiums and shopping malls.
Towards Enterprises and corporates, typical ‘zonal’ scenarios are created whereby an enterprise campus has local deployment with minimum footprint (e.g. with small cells) and can run very specific and localized services and applications.
Internet-of-Things and vertical-based use cases are also a key area for Liquid Applications. Nokia Networks has already demonstrated how drivers can be alerted, in real-time, to road hazards utilizing an LTE network and Liquid Applications. The key enabler for car-to-car and car-to-roadside communications is the delivery of time-critical information, both from the vehicle and the surrounding environment. For the consumer, they benefit from increased road safety through traffic related hazard warnings and an improved driving experience (e.g. route optimization, traveling time reduction).
Specific applications (e.g. smart cities, IoT, public safety) would also fit to this category. Mobile edge video analytics that has been previously showcased is an example of the type of application that an operator could deploy within a smart city, and Nokia’s Network-in-a-Box (NiB) offers authorized IP connectivity and can provide a complete LTE network service for users, for example on industrial campuses, oil rigs, mines and ships.

18. Telco Cloud: VNF-specific Features
BSS
NFV
Orches-
trator
Service Orchestrator
Network Orchestrator
vApp Differentiators:
Open API
Elasticity
Orchestration
Subscriber and Service
aware routing
Continuous SW (Upgrade) Delivery
NetAct
FCAPS Management
Cloud Application Manager
Automated Deployment via Application Templates
Elasticity Manager
Virtualized network functions
IaaS API
CMD
CMD
Multivendor
IaaS API
Hypervisor
Virtual Infrastructure Manager
VMware (ESXi)
KVM
Cloud stacks
Virtualization Layer Independence
Openstack
VMware (vCenter, vCloud)
Data center Hardware (x86 server)
Features which will be provided by VNFs will make netowrks ready for C

19. Compliance to the standards is a feature itself.
Document ID / v. 0.1 / Life cycle status / Dept. / Author
9/22/2018

20. 1 2 3 4 Agenda Expectations Solutions Features Future
In this presentation I’ve share with you…

21. Nokia AirFrame Containerized Data Center
Containerized data center supports local telco and IT services anywhere in a network
Build data centers as efficiently as possible
Modular design for green data centers
Pre-built and pre-integrated for fast and efficient integration in 1-2 days
Up to 6 fully equipped racks
Autonomous data center with power, cooling, door locking and integrated management system
Drop-in data center to cater for peak demand and/or to provide localized telco and IT services
Finding the right architecture for the TelcoCloud
Telco Cloud initial steps were focused on taking core applications to a virtualized environment
Initial gains are clear with added scalability, flexibility and business agility
However, the architecture so far has been basically emulating the traditional IT cloud structure with centralized data centers. Is this really enough?
We believe that in a Telco environment, to better address the specific requirements of this domain, the cloud architecture has to evolve and mix centralized and distributed capabilities
The Telco Cloud architecture enables more flexibility for operators to react quickly to traffic spikes, quickly providing additional capacity when needed.
Nevertheless, other issues like latency and even the ability to allocate different server categories to specific functions also become important. After all some requirements are really telco specific and haven't been addressed in the traditional IT cloud world.
Also, the network architecture plays an important role here. For some specific applications it is very important to have processing capacity closer to the traffic hotspots, either due to latency issues or simply to reduce the costs to move a huge data payload all the way to a centralized data center
The adherence to open standards is important to guarantee the success of the Telco Cloud deployments, therefore ETSI NFV and OPNFV support is important.
Our point of view
At Nokia, we are focused on bridging those gaps and putting together a Telco Cloud solution that goes beyond a pure translation of the IT world to the telco domain. We focus on building the best of both worlds, combining all the flexibility of the cloud technologies while addressing the requirements of telco applications on the core and radio domains
As part of bridging this gap, we believe that the cloud management solution need to combine the best of both worlds, not getting limited to a purely IT driven approach
We are putting together a set of solutions to expand our reach in the Telco Cloud domain, focusing on making the Telco Cloud architecture more flexible and building data centers that address the requirements of the telco world
---
Background Story
While the Telco industry prepares its transformation towards a cloud architecture and takes the first steps to define 5G it is important to keep in mind the characteristics and performance requirements that brought us to where we are. So, while we are focusing our efforts to bring to the Telco market the advancements that the IT world achieved with cloud computing, we cannot lose sight of the fact that the requirements are different and much more stringent for Telcos. Thus it is important that we bridge this existing gap between what the IT cloud can offer and the requirements of the Telco world via more efficient HW and SW solutions and a network architecture that supports these requirements. For example, most traditional Telco applications are extremely latency-sensitive and very data intensive. If we implement a centralized Telco Cloud architecture, following the IT cloud concept, we will end up with higher latencies than acceptable and a huge load on the operator backhaul. This means a lot of costs due to all this traffic flowing on the network and even potential technical problems due to latency levels higher than required. To avoid these problems, and others, the Telco Cloud architecture will have to be much more distributed than a traditional IT cloud. So, instead of a few huge data centers, operators will require more data centers of potentially smaller sizes.
 Also, looking specifically into HW and SW solutions, those will have to be built in such a way that we can at the same time leverage the savings and flexibility brought by the IT domain and also take in consideration the specific requirements of the Telco world. So, for example, this target HW solution can (and will) be based on a traditional IT architecture and will support IT applications, but it cannot limit itself to this. The industry needs a solution tailored to support the current requirements of the Telco and to pave the way towards 5G. This is what us at Nokia are doing with this launch.
* For illustration purpose only

22. LTE public safety network - Overview
OSS, BSS
Register
Core in a Box
Core for PS services
(optinally dedicated)
HSS, SPR
MCPTT , Group Comm
Live video
Management
Charging
One-NDS
PCRF
MME
S/P-GW
IMS
AS (e.g. VoLTE)
Cell site
Interworking
Tetra/P25 core
BM-SC
MBMS-GW
Agency 1
eNodeB
Cell site
Control room / Dispatcher
Agency 2
IP backhaul
IP backbone
eNodeB
Internet
LTE public safety networks, Mika Aalto
Control room / Dispatcher
Tetra/P25 BTS

23. Mobility on demand | Highly efficient resource utilization
TCO optimized use of network resources
Core cloud
Less traffic backhauling to centralized cloud
Centralized
Mobility anchor
TCO optimization
Best per service flexibility
Radio cloud
Local
30% of users are actually mobile
70% are nomadic / static devices
Reduce core network resources
High-speed mobility
10,000 x
>10 Gbps
100 Mbps
<1 ms x
ultra low
Let’s talk some more about the architecture and why creating a more distributed topology makes sense within the telco domain. As part of bridging the gap between IT and telco, we believe that a cloud solution needs to combine the best of both worlds, breaking free of a pure IT play and really addressing the specific requirements of telco applications. You can see towards the bottom of this slide some of the application categories, including OSS, Core and Radio.
By nature, telco applications are latency-sensitive and data intensive, meaning that if we implement a centralized telco cloud architecture and follow the traditional IT approach, we end up with higher latencies and excessive load on the ingress to the core network. This in turn translates into higher costs in order to shift all of this traffic around the network and also a number of technical issues. An effective way to deal with this is to create a more distributed architecture or sub-clouds, as you can see from the right-hand-side of the slide. So, instead of a few huge data centers, operators should create smaller ones, located in the places that are close to where the resources are actually needed, in order to deliver optimized latencies and throughput, and just as important, include the most advanced security capabilities that we can deliver from our own Security expertise. This combination will result in a more distributed architecture and the need for a data center solution that is able to deliver a lot of processing power to deal with the data storm that is so typical on telco networks
It has been observed that only 30% of the users who are actually camping in cellular operator networks are actually mobile. So, the overhead introduced in the network to support seamless mobility should be minimized by introducing support for flexible mobility, also referred to as “mobility on demand”. Flexible active mobility is made possible by supporting flexible IP anchoring and enabling mobility support only on demand (i.e. start with mobility OFF and enable it ON demand)
public

24. We have learnt that future mobile networks need to be more flexible
Key Takeaways
We have learnt that future mobile networks need to be more flexible
Virtualized IT HW is foundation of future mobile networks
Telco Cloud means SDN, NFV and C-RAN together
Service Chaining makes future mobile networks programmable
Open Ecosystem allows to build programmers communities around Telco Clouds

25. Q&A