1, Value proposition
2, real-world use case
3,Market Segments
Data Center - Scalability Data Center Networks
Carriar - Service Provider Data Networks
Enterprise
- Streamlined and Dynamic, but Not a technology Nor a market
- Standardized platform for Development of Novel Services
why a new net architecture is needed:
not cost-effective;
not agile enough: time to market; complex/manually intensive provisioning/configuration/network management;
not oriented towards services/end users: static configuration/static traffic patterns and policy
hardware/infrastructure oriented: ports/bandwidth/ids/vlan tags etc
SDN architecture: 25'30"-27'50"
Programmability/contralized Intelligence/Abstraction
OpenFlow: 28'10"-30'20"
southbound protocol
break the layer boundaries(of OSI 7 layer);
value proposition: 33'00"
automation -> OpEx
optimization -> CapEx -> more intelligent processing and a better utilization of the capacity;(more efficient bandwidth - mutli-tenants, multi networks run on the same infrastructure)
Monetization -> New Revenues (Dynamics, intelligence pricing)
applications of Segments: 35'40"
[Data Center]
1, Virtualization: VM mobility/Domain isolation
2, Hybrid Clouds: span public and private DC
3, Multi-Tenancy: multiple customers share services
4, Disaster Recovery: Improved visibility and managememt
[Carrier network] more efficient usage of carrier bandwidth, especially mobile/wireless bandwidth;
1, Mobile Edge: seamless roaming for 3G/4G/Wifi
2, service migration to cloud: span public and private cloud
3, service monitoring: automated provisioning / centralized network view
4, traffic steering: content delivery services
[NFV] carrier lead ETSI
<Network Virtualization>
<Carrier> manage fabric instead fo manage boxes
1, Optimization
- network utilization: Performance-on-Demand (PoD) - e.g. NaaS / Efficient multi-layer traffic engineering/fixed access utilization
- Service performamce: netrwork aware load balancing/Mobile-WiFi offload(or n-casting)/traffic steering for Mobile QoE
- operation: largely centralized upgrades, features,services additions/high-fidelity simulation, straightforward push to production;
2, Monetization
- intellegence : better matching of network supply & user/application demand -- maximized economic utility : PoD- e.g. NaaS; QoS
- Colt: L3 CPE virtualization/ NFV
<Data Center>
<Enterprise>
challenge: multi-VLAN / VM mobility (IP addr mgmt, access control)
requirements: Live migration / Traffic prioritization / Policy enforcement/ Ease of operations and maintenance
SDN solution: (NEC+Hyper-V)
• Live VM migration without network reconfiguration
• Integrated virtual and physical network management
• Greater flexibility/faster deployment of network services
• Open Standard – more infrastructure options
<SP-SDN>
1, NTT: traffic on demand(by user) / VLAN-MPLS(Cloud)
2, Ericsson+Telstra: virtualization of the aggregation netowkr (NFV),
IP edge of the network & service chaining(1st SDN use case for SP)
where treat different data flows different ways & not route traffic in and out of boxes that don't need to.
so that Operator can
A) create service that use less network resources.(lower capex/opex)
B) Create service more quickly because we can route services more dynamically and quick TTM without traditional integrating to every network and every network box.
Using traffic steering as part of SDN allows to individualize products more quickly and more readily.
Telstra expects to move to field trials later in 2013 and to take the first steps toward operationalizing SDN in its production network in 2014.
Ericsson tech talk about Sp-SDn: cross domain (Radio/Core/DC)
blog to read: SP SDN gets real
Difference between SDN & NFV: SDNCentral article
- http://www.nojitter.com/post/240158913/whats-the-role-of-sdn-and-uc
2, real-world use case
3,Market Segments
Data Center - Scalability Data Center Networks
Carriar - Service Provider Data Networks
Enterprise
- Streamlined and Dynamic, but Not a technology Nor a market
- Standardized platform for Development of Novel Services
why a new net architecture is needed:
not cost-effective;
not agile enough: time to market; complex/manually intensive provisioning/configuration/network management;
not oriented towards services/end users: static configuration/static traffic patterns and policy
hardware/infrastructure oriented: ports/bandwidth/ids/vlan tags etc
SDN architecture: 25'30"-27'50"
Programmability/contralized Intelligence/Abstraction
OpenFlow: 28'10"-30'20"
southbound protocol
break the layer boundaries(of OSI 7 layer);
value proposition: 33'00"
automation -> OpEx
optimization -> CapEx -> more intelligent processing and a better utilization of the capacity;(more efficient bandwidth - mutli-tenants, multi networks run on the same infrastructure)
Monetization -> New Revenues (Dynamics, intelligence pricing)
applications of Segments: 35'40"
[Data Center]
1, Virtualization: VM mobility/Domain isolation
2, Hybrid Clouds: span public and private DC
3, Multi-Tenancy: multiple customers share services
4, Disaster Recovery: Improved visibility and managememt
[Carrier network] more efficient usage of carrier bandwidth, especially mobile/wireless bandwidth;
1, Mobile Edge: seamless roaming for 3G/4G/Wifi
2, service migration to cloud: span public and private cloud
3, service monitoring: automated provisioning / centralized network view
4, traffic steering: content delivery services
[NFV] carrier lead ETSI
<Network Virtualization>
<Carrier> manage fabric instead fo manage boxes
1, Optimization
- network utilization: Performance-on-Demand (PoD) - e.g. NaaS / Efficient multi-layer traffic engineering/fixed access utilization
- Service performamce: netrwork aware load balancing/Mobile-WiFi offload(or n-casting)/traffic steering for Mobile QoE
- operation: largely centralized upgrades, features,services additions/high-fidelity simulation, straightforward push to production;
2, Monetization
- intellegence : better matching of network supply & user/application demand -- maximized economic utility : PoD- e.g. NaaS; QoS
- Colt: L3 CPE virtualization/ NFV
<Data Center>
<Enterprise>
challenge: multi-VLAN / VM mobility (IP addr mgmt, access control)
requirements: Live migration / Traffic prioritization / Policy enforcement/ Ease of operations and maintenance
SDN solution: (NEC+Hyper-V)
• Live VM migration without network reconfiguration
• Integrated virtual and physical network management
• Greater flexibility/faster deployment of network services
• Open Standard – more infrastructure options
<SP-SDN>
1, NTT: traffic on demand(by user) / VLAN-MPLS(Cloud)
2, Ericsson+Telstra: virtualization of the aggregation netowkr (NFV),
IP edge of the network & service chaining(1st SDN use case for SP)
where treat different data flows different ways & not route traffic in and out of boxes that don't need to.
so that Operator can
A) create service that use less network resources.(lower capex/opex)
B) Create service more quickly because we can route services more dynamically and quick TTM without traditional integrating to every network and every network box.
Using traffic steering as part of SDN allows to individualize products more quickly and more readily.
Telstra expects to move to field trials later in 2013 and to take the first steps toward operationalizing SDN in its production network in 2014.
Ericsson tech talk about Sp-SDn: cross domain (Radio/Core/DC)
blog to read: SP SDN gets real
Difference between SDN & NFV: SDNCentral article
- http://www.nojitter.com/post/240158913/whats-the-role-of-sdn-and-uc
No comments:
Post a Comment