S2OB - LTE Bearer Solution (PTN) - 20130510 PDF

LTE Bearer Solution------MPLS-TP
(High Quality & Low Costs & Simple Implementation)
Agenda
Demand Analysis
LTE Bearer Solution
Implementation of The Bearer Solutions
PTN Development Trend
>
LTE is Coming
Country/Area
USA
Aggregate global mobile traffic forecast

2G impact
3G impact
4G impact
35.0
30.0
Verizon Wireless
AT&T Mobility
Norway
TeliaSonera
Sweden
3
Vodafone
25.0
Tbps
Operator
Germany
20.0
Deutsche Telekom
O2
15.0
Hongkong
10.0
5.0
Japan
0.0
2006
Source: Ovum
2007
2008
2009
2010
2011
2012
2013
CSL Limited
NTT DoCoMo
Softbank
Singapore
M1
India
Bharti Airtel
As per the data of OVUM, LTE traffic keeps growing fast since 2010.
Famous operators around the world gradually take LTE as the future of their wireless networks. Since 2010, they
started related trials or official applications. To June 2012, 80 LTE networks were under official application.
ZTE Corporation. All rights reserved.
>
Changes Brought by LTE

Flat network architecture
Broadband mobile application

Bandwidth
HD video
S-GW
S-GW
S-GW
S-GW
Online video
P2P download
S1
Online game
Web surfing
S1
S1
X2
Voice
eNB
Self-organization network
eNB
eNB
High-quality network bearer
eNB
S-GW
eNB
>
Broadband Mobile application Estimated Bearer Bandwidth
LTE throughput (Theoretical value)
Downlink/uplink
subframe distribution
The number of
downlink subframes
of the wireless frame
The number of uplink

subframes of the
wireless frame
The number of
special subframes of
the wireless frame
The downlink peak speed of single

community (Mbps)
The uplink peak speed of single

community (Mbps)
2DL:2UL
81.938
17.526
3DL:1UL
111.893
8.763
Under representative configuration conditions: LTE carrier bandwidth 20M, MIMO 2*2, downlink 64QAM and uplink 16QAM.
Estimated transport bandwidth of 2DL:2UL subframe
Estimated transport bandwidth of 3DL:1UL subframe
Throughput of single community (theoretically)
Throughput of single community (theoretically)
81.938 + 17.526 = 99.464Mbps
111.893 + 8.763 = 121.656Mbps
Transport bandwidth of single community (theoretically)
Transport bandwidth of single community (theoretically)
99.464 (1+10%+5%) = 114.384Mbps
121.656 (1+10%+5%) = 139.904Mbps
(Taking the consumption as 10% and the X2 service as 5%)
(Taking the consumption as 10% and the X2 service as 5%)
Transport bandwidth of single base station (theoretically, S1/1/1)
Transport bandwidth of single base station (theoretically, S1/1/1)
114.384 3 = 343.152Mbps
139.904 3 = 419.712Mbps
Transport bandwidth of single base station (estimated,
Transport bandwidth of single base station (estimated,
considering the coverage)
considering the coverage)
Indoor situation: 343.152 42% = 144.124Mbps
Indoor situation: 419.712 42% = 176.279Mbps
Outdoor situation: 343.152 32% = 109.809Mbps
Outdoor situation: 419.712 32% = 134.308Mbps

Flat Network Architecture

S-GW
BSC/RNC
Abis/Iub
S-GW
S1
Mobile Backhaul
S-GW
S1
Mobile Backhaul
X2
X2
BTS/NodeB
BTS/NodeB
BTS/NodeB
eNB
X2
One BTS/NodeB only belongs to one BSC/RNC. The flows are

aggregated.
Wireless networks are between BTS/NodeBs.
eNB
eNB
One eNB belongs to multiple S-GW/MMEs at the same time. X2

Ports are used to connect eNBs. The flows are in MESH manner.
More than 95% RAN services belong to S1 services. there are

only less than 5% X2 services in the entire RAN service.
Flat LTE enables more flexible service connection, which realizes complete network resource sharing. In this way, the bearer
network should give support to L3 forwarding service and have less impact to the existing networks and services.
Self-Organization Wireless Network

As the LTE network architecture is going to be more
complicated, the network administrator will have to process
more parameters and data. Thus, SON (Self Organization
Network) for wireless network comes out to realize some selforganization services of the LTE network to reduce the
workload and costs.
S-GW Pool
MME Pool
S1-U flex
S1-C flex
Mobile Backhaul
X2
X2
X2
SON has the following four services:
eNB
Self
configuration
Self
planning
Automatic software installation,

automatic configuration of
Implement automatic calculation
Self
healing
Find out failures through
wireless and transport parameters,
of network parameters and
automatic alarm association.
automatic detection, automatic
performance dynamically. Make
Implement isolation and
management of neighbor relations
related planning.
recovery in time.
eNB
eNB
Self
optimization
Implement self-adaptive
parameter adjustment to
optimize the network
performance according to the
device running status.
On the basis of flexible configuration of the bearer network, the LTE SON on one hand ensures the network security and reliability,
on the other hand implements easy-maintained and easy-managed networks.
Changes to Network Service Requirements
Differentiated services and QoS requirements

Precedence
QCI
Packet latency
Packet loss rate
Representative services
5(non-GBR)
100ms
10-6
IMS signaling and OAM information (including protection and synchronization

information)
1(GBR)
100ms
10-2
Session voice
3(GBR)
50ms
10-3
Real-time games
2(GBR)
150ms
10-3
Session video (real-time services)
4(GBR)
300ms
10-6
Non-session video (buffer services)
6(non-GBR)
300ms
10-6
Video (buffer services)
7(non-GBR)
100ms
10-3
Voice, video (real-time services) and interactive games
8(non-GBR)
300ms
10-6
TCP-based applications (e.g. online surfing, E-mail, Internet chat and P2P)
9(non-GBR)
300ms
10-6
File sharing
Latency requirements
S1 Port
End-to-end service experience latency<25ms, 3GPP <10ms, ideal value<5ms
X2 Port
Service mobile latency 50ms-100ms, 3GPP<20ms and ideal value<10ms
Comprehensive Considerations of Building LTE Network

BSC/RNC
BTS
NodeB
BSC
RNC
BTS
NodeB
BTS/NodeB
BTS
NodeB
S-GW
MGW, MSC
SGSN, GGSN
BSC/RNC
E2E
PW/LSP
BSC/RNC
IMS, EPC
eNB
S-GW
S-GW1
S-GW2
S-GW3
eNB
BTS/NodeB/eNB
eNB
E2E
PW/LSP
Flatness of the LTE network VS. How to decrease the impact to the existing network?
eNB
eNB
eNB
eNB
eNB
BSC/RNC
S-GW
VRF
S-GW
S-GW
S-GW
Good quality
Flexibility of the network architecture VS. How does the bearer network deploy L3 services?
Small costs
The coexistence of LTE and 2G/3G VS. How does the bearer network take care of both old and new services?
More complicated service configurations VS. How does the bearer network simplify the operation and management?
Simple implementation
Agenda
Demand Analysis
LTE Bearer Solution
LTE S1, X2 Services Bearing Mode
L2 VPN can adopt middle-small

scale LTE networking.
L2 VPN(Agg layer and below)+L3

VPN(Core layer ) is the LTE S1
bearing solution.
X2 and S1 will share transmission

path, fulfill switching in wireless
backhaul layer.
S1
X2
General Architecture of Mobile LTE Service

Access
AGG
Aggregation
AGG
eNB
S1
NodeB
X2
Core
AGG
Core
BSC/RNC
S-GW
S-GW
eNB
3G IP Service
LTE
Backbone
L2
L2
L2 VPN
L2 VPN
MME
IP/MPLS
MME
L2
L3 VPN
L2/L3
Features of LTE bearer solution:
Implementing unified scheduling in the core layer, the LTE service bearer insists on the Backhaul bearer architecture in 2G/3G era.. As the LTE has S1-Flex and X2 Ports which
require service forwarding according to destination IP addresses, so the bearer layer should support L3 services to meet the requirements of the service Ports and wireless SON
theory.
Both the China Mobile and other mainstream providers agreed access aggregation layer L2+ core layer L3 VPN solution.
LTE Service Bearer Solution 1: Core Layer PTN+CE Bearer

E-Line
termination
VRF
VRF
PTN
PTN
aggregation
layer
S-GW
Core node
S-GW
LSP
CE
S-GW
MME
Domain
C
MME
IP private network
GE/10GE
VRF
S-GW
LSP
Aggregation hub node

S-GW
S-GW
MME
Access
L2 VPN
L2
Aggregation
L2 VPN
L2
S-GW
S-GW
MME
Domain
A
S-GW
L3 VPN
L3
L2
Local-domain Core
service scheduling
L2
MME
Domain
B
MME
Cross-domain
service scheduling
Potential considerations of the solution:

The implementation of core layer router bearer solution:
The impact from either the CE capacity extension solution or new CE solution onto the existing IP
Terminated on the core node, the access aggregation layer E-line (S1/X2)
services
interconnects the core node router in the manner of L2. The router
As PTN and routers belong to different domains, the cross-domain service configuration,
initiates L3 VPN to implement S1/X2 route forwarding on the basis of the
scheduling and protection require the cooperation of different operation and maintenance
destination address.
systems, so therere lots of potential risks.
Face two options: 1. Extend the capacity of the existing CE. 2. Build a new
The hybrid bearer mixing LTE and other services together brings in dangers in security and
CE.
reliability.
LTE Service Bearer Solution 2: PTN End-to-End Bearer Solution

Access node
Aggregation node
eNB
S1
NodeB
X2
Aggregation hub node
Core node
S-GW
S-GW
eNB
IP 3G
LTE
BSC/RNC
L2
L2
L2 VPN
L2 VPN
The implementation of PTN end-to-end bearer solution:
Use PTN end-to-end networking to realize L2 VPN + L3 VPN solution. The access
aggregation layer uses L2 VPN, and the core scheduling adopts L3 VPN.
Both the access aggregation layer and core layer use PTN scheduling to be
responsible for the S1/X2.
The core node of the PTN scheduling layer is configured with the L3 VPN to
realize flexible configurations. Both dynamic route and static route are
supported.
Compared with the router, the PTN device not only simplifies the L3 service,
but also inherits the reliability and easy-management feature of the PTN.
MME
IP/MPLS
MME
L2
L3 VPN
L2
Advantages of the PTN bearer solution:
Unified management can realize end-to-end service

management and configuration.
Only build PTN on the core layer to realize the L3 VPN. In this
way, the network changes little.
The network planning stage is very simple and cost-effective.
The operation and management are much more efficient.
Give complete support to multiple services.
PTN Solution Core Layer L3 VPN

LTE load
IP header
Internal virtualized
VLAN sub-Port is
used to terminate ELine services.
VLAN
LTE load
Eth header
IP header
PW label
VRF label
LSP label
NNI Eth
header
LSP label
NNI Eth
header
L2
PW
VRF
Aggregation layer
PTN
S-GW
S-GW
MME
BGP routing
information
interaction
S-GW
DomainA
MME
VRF
OSPF/ISIS
BGP routing
information
interaction
S-GW
MME
S-GW
S-GW
LSP
PTN network in
core layer
LSP
Aggregation
hub node
Simplify core theories of L3VPN:

Follow technical features of PTN devices. IP services are run on the TP static tunnel.
Theres no essential difference between the IP service and L2 service.
Domain C
MME
VRF
S-GW
OSPF/ISIS
S-GW
S-GW
MME
Domain
B
MME
The EVPL service is used for access aggregation. The base station uses L2 private lines to access the core PTN node. The bridging from L2 to VRF L3 is done in the
core node.
The tunnel between the PE nodes adopts the PTN static tunnel technology. It also inherits the PTN protection mechanism of the entire network.
Initiate L3VPN between core nodes. The VPN route can be done in the following two ways:
MP-BGP distribution and learning
Static configuration of the network management

PTN can Satisfy L3 Requirements of the LTE
Provincial
equipment room
City C
S-GW
MME
Network section route:

routes between core PTNs in
different domains
Core layer
PTN
The capital city

of a province
PTN (access and aggregation)
City A
The requirements of the PTN route in the core layer:

section route + host route
Host route: routes between the
LTE base station and the local
core PTN.
City B
The host route is often decided by the number of the base station (M)of the core PTN node. The M is usually less than 1000.
The network section route is mainly used between the PE nodes of the L3VPN. Each node may generate a section route. So if there are N PE nodes in total, there would
be N-1 network section routes.
As a result, the number of the routing table item should be MN1, which is around 1K. Even in the extreme situation, the number wont exceed 2K.
The routing capability of ZTE ZXCTN 6500 the PTN device in the core layer, is 64K, which totally satisfies the bearer requirements in the LTE stage.
China Mobile PTN L3 VPN Test

Test contents:
The test of the bridging from L2 to L3
The test of the routing protocols between PEs, including both

dynamic and static protocols
The test of L3VPN service entities, including route specifications,

VRF numbers, DGCP-Relay, equipment-class protection
capability, throughput, latency and jitter
The test of S1 and X2 end-to-end bearer service and

performance
The test of S1 and X2 end-to-end protection, including the tests

of access, aggregation and core failure protection capability
The test of OAM capability
The test of end-to-end time synchronization service
The test of end-to-end service performance
The test of network management services, including end-toend service configuration, and management.
Test results:
Routing table capability: ZTE PTN devices support60K.
VRF number: PTN devices support 1024.
End-to-end PTN Solution VS. PTN+CE Solution

Services
End-to-end PTN solution
PTN+CE solution
Service transport
Satisfied
Satisfied
Carrier-class PAM and protection switchover
Satisfied
Weak
Latency
Highly precise clock transport
Network maintenance
Configuration
Service scheduling
Network management capability
Satisfied
Weak
Satisfied
Weak
Satisfied
Hard for failure location, weak
Satisfied
and simple
Satisfied, complicated
Satisfied
Satisfied, Big impact onto the private

network
Satisfied
Satisfied. But there are 2 network

management systems. Besides, the end-toend service configuration cant be
implemented (note 1).
The comparisons of the technologies show the PTN end-to-end solution is more suitable for China Mobile LTE service bearer.
Note1: When the PTN and CE devices are from the same vendor, a shared network management is announced available. But in fact, due to the weak
network management service of the CE router, the service configuration and failure location services have to be done in the manner of cmd line.
Also, the network management does not give support to the in-batch VRRP creation service of the CE router, thus, the end-to-end management cant
be implement in practice.
LTE Service Bearing Encapsulation Mode

L2VPN
L3VPN
PE3
PE1
L3VPN
BTS
PE4
BTS
IP head
VLAN
Eth head
IP head
VLAN
Eth head
PW label
LSP label
NNI Eth head
L2/L3 VPN
bridging
sGW
PE2
LTE load
IP head
VRF label
LSP label
NNI Eth head
LTE load
IP head
Eth head
Access/Aggregation layer adopts PW encapsulation, transmitted via E-Line mode.

Core nodes adopt L3VPN encapsulation.
L2/L3 Inner Bridging Solution

L3VE
L3VE
ETH PW
VRF
ETH
PW
VSI
ETH
PW
VLAN
Agg
ETH
PW
VLAN
Agg
VRF
VRF
ETH
PW
One to one
solution
L3VE
VSI
Multiple to one VSI

solution
Multiple to one VLAN

aggregation solution
In one to one solution, L2/L3 bridging point should configure lots of IP address, under this solution, IP
address and routing plan is complicated.
Multiple to one solution has the problem of broadcasting.
In multiple to one VLAN aggregation solution, one BTS adopts one independent VLAN. To avoid
broadcasting, in L2/L3 bridging point, convergence multiple VLAN and configure one IP address.
It is suggested to adopt multiple to one VLAN aggregation solution.
L2/L3 VPN Bridging Loopback

Physical
port
ETH
PW
VLAN
Agg
ETH
PW
VLAN
Agg
VRF
Solution 1External loopback
ETH
PW
VLAN
Agg
ETH
PW
VLAN
Agg
Solution 2: Internal physical Port loopback
Logical
port
ETH
PW
VLAN
Agg
ETH
PW
VLAN
Agg
VRF
VRF
Solution 3: Internal logical Port loopback
L2/L3 VPN Bridging Solution 1: External Loopback
External Port
loopback
L2 PW flow
L3VPN flow
L2VPN
Slot 1
2*10GE
Slot 2
2*10GE
eNB
Switching
L3VPN
Slot 4
2*10GE
Slot 3
2*10GE
sGW
L2 /L3 VPN
bridging
Solution 1: external loopback

When PW is ended, from external port, loopback the fiber to the other port, go to L3 VPN VRF processing, which is
wasting switch ports with low efficiency.
If existing equipment has high ports usage rate, it will not be upgraded to L3VPN smoothly
L2/L3 VPN Bridging Solution 2: Internal Physical Port Loopback

The switch port of slot 2 is assigned to
L2/L3 VPN bridging, can not use for
other connection
L2 PW flow
L3VPN flow
L2VPN
Slot 1
2*10GE
Slot 2
2*10GE
eNB
Swith
L3VPN
Slot 4
2*10GE
Slot 3
2*10GE
sGW
L2 /L3 VPN bridging
Solution 2: Internal Physical Port Loopback

As similar as solution 1, it is false internal bridging, bridge Port adopts physical Port of switch network(no need external
fiber), which is wasting switch ports with low efficiency.
The ports used for internal loopback can not provide external connection, as slot 2 in above figure.
If existing equipment has high ports usage rate, it will not be upgraded to L3VPN smoothly.
L2/L3 VPN Bridging Solution 3: Internal logical Port Loopback

Through internal logical Port,
realizing L2/L3 service flow
connection
L2VPN
L3VPN
Slot 1
2*10GE
eNB
Slot 2
2*10GE
Switch
Slot 4
2*10GE
Slot 3
2*10GE
L2 PW flow
L2 /L3 VPN
bridging
L3VPN flow
Solution 3: Internal logical Port loopback

Ending PW in equipment, access to L3 VPN VRF processing via logical ports, not wasting ports resource.
Existing equipment could be upgrade to L3VPN smoothly, no matter the existing ports have been used out or not.
It could realize L2 and L3 UNI connection, without the VLAN limitation.
The highest efficient, most flexible bridging solution
ZTE CTN 6500 series products adopt internal logical port loopback
sGW
LTE Bearing Route Table Requirement Analysis

L3VE
ETH
PW
VLAN
Agg
VRF
L2 PTN
ETH
PW
L3 PTN
VLAN
Agg
ETH
PW
VLAN
Agg
sGW
ETH
PW
VRF
L2 PTN
sGW
VLAN
Agg
In L2/L3 VPN bridging point, L3 VE port adopts 24 mask address(generate one section route A.B.C.0/24), ending one group
of eNB, it could support 253 eNB at most in the group, calculate according to 100 eNB in average.
Calculate according 10000 eNB, it will take 10000/100=100 section routes.
LTE bearing L3 PTN routing number is in the hundreds level.
PTN L3VPN E2E protection Solution
Testing shows it could provide 50ms

carrier class protection
eNB Side Protection
L2VPN
Master/slave node
provide gateway
protection through
VRRP for eNB
L3VPN
PE3
L3VPN
eNB
eNB
PE1
PE4
sGW
PE2
L2 /L3 VPN
bridging
Each eNode configure working and protection PW to master/slave core node.

L2 /L3 VPN bridging run VRRP, for eNB, the next hop is virtual IP address of VRRP protection
group.
To improve VRRP switching speed by PTN fast OAM and VRRP bundling.
sGW Side Protection

Solution 1VRRP
L3VPN
L3VPN
L2 /L3 VPN
bridging
Solution 2IP FRR
Master/slave nodes
provide gateway
protection for eNB
through VRRP
Configure IP
FRR protection
L3VPN
Make L2 bundling in the

two ports of sGW ,
configure one IP address
Make L2 bundling in the two ports of sGW ,

configure one IP address, providing protection
for downlink services through L2 switching.
PE node run VRRP, providing gateway protection
for sGW.
L3VPN
sGW
L2 /L3 VPN
bridging
sGW
Configure two
ports of sGW in
different network
section
Configure two ports of sGW in different network

section, adopt IP FRR to provide protection for
downlink services.
PE node run IP FRR, providing protection for uplink
services.
L3VPN FRR Protection
L2VPN
L3 VPN FRR is used

between core L3
PTN nodes,
L3VPN
PE3
L3VPN
eNB
eNB
PE1
PE4
sGW
PE2
L2 /L3 VPN
bridging
When S1 or X2 need cross core nodes, it need L3 VPN forwarding in core nodes.
For one L3 VPN route, there are two remote PE, system will generate one master and
one slave route according to related rules.
When remote PE node failed in master route, it will switch to slave route, service will
be sent to slave remote PE.
L2 to L3 Protection Scenario 1- Access Link Failed
L2VPN
L3VPN
PE3
PE1
L3VPN
eNB
eNB
working
protection
PE4
sGW
PE2
L2 /L3 VPN
bridging
When access link is failed, downlink service is protected/switched by sGW/MME; if sGW adopt
L2 bundling, protected from L2 switching; if sGW adopt IP, protected from IP FRR.
Uplink services is protected/switched by PE1 IP FRR locally, and forward to sGW/MME
through.
L2 to L3 Protection Scenario 2- Access PE failed

Working
Protection
L2VPN
L3VPN
PE3
L3VPN
eNB
eNB
PE1
PE4
sGW
PE2
L2 /L3 VPN
bridging
For downlink services, when PE1 failed, if VRRP is used, PE2 will become master
through VRRP switching, it will send free ARP message to sGW, refresh sGW ARP
table, switching downlink services to PE2.
For uplink services, when PE3 detect PE1 failure, through L3 VPN FRR, switching
uplink services to PE2.
L2 to L3 Protection Scenario 3- L3 VPN Internal Network Failed
Working
Protection
L2VPN
L3VPN
PE3
eNB
eNB
PE1
L3VPN
PE4
sGW
PE2
L2 /L3 VPN
bridging
When L3 VPN internal network failed, service is protected through PTN tunnel by liner
1:1 or 1+1, or by ring network protection.
L2 to L3 Protection Scenario 4- L2 to L3 Bridging PE Failed
L2VPN
L3VPN
PE3
PE1
L3VPN
eNB
eNB
Working
Protection
PE4
sGW
PE2
L2 /L3 VPN
bridging
For downlink services, when PE3 failed, PE1 detected PE3 failed, through L3 VPN FRR,
downlink services is switched to slave PE4.
For uplink services, when PE5 detect PE3 failure, through PW switching, L2 VPN services will
be switched to PE4, at the same time, PE4 detected PE3 failed, open VRRP master/slave
protection, PE4 will become master, ending the L2 services switched from PE5.
L2 to L3 Protection Scenario 5- L2 VPN Internal Network Failed
L2VPN
L3VPN
PE3
PE1
L3VPN
eNB
eNB
Working
Protection
PE4
sGW
PE2
L2 /L3 VPN
bridging
When L2 VPN internal network failed, service is protected through PTN tunnel by liner 1:1
or 1+1, or by ring network protection.
Gateway Protection Optimization Solution

Configure the same IP, MAC
L2VPN
L3VPN
L3VPN
eNB
eNB
sGW
L2 /L3 VPN
bridging
Not configure VRRP in master/slave nodes, L2 and L3 VPN bridging point not care PW state.
Configure the same IP, MAC address in master/slave nodes, as eNB gateway.
Service protection switching is controlled by access point.
It is requested that master PW should have tunnel protection, to ensure when master L2/L3 bridging is
not down, the master PW is always up.
sGW/MME Centralized Deployment SolutionPTN Backbone

Capital sGW/MME
sGW/MME
L3 PTN
OTN Path
IP
L3VPN
PTN backbone
IP
L3VPN
Vendor A
L3 PTN
Vendor B
L3 PTN
L2VPN
L2 PTN
L2 PTN
City 1
Vendor A
L3 PTN
Vendor B
L3 PTN
L2 PTN
L2 PTN
City N
sGW/MME deployed in capital, connecting to capital L3 PTN network.

City core layer L3 PTN adopt IP which transmit LTE service to PTN backbone network, PTN
backbone open L3 VPN for LTE services, and transmit it to capital L3 PTN network.
sGW/MME Centralized Deployment SolutionOTN Backbone

Capital sGW/MME
sGW/MME
OTN Path
L3 PTN
OTN Backbone
IP
L3VPN
Vendor A
L3 PTN
Vendor B
L3 PTN
L2VPN
L2 PTN
L2 PTN
City 1
Vendor A
L3 PTN
Vendor B
L3 PTN
L2 PTN
L2 PTN
City N
sGW/MME deployed in capital, connecting to capital L3 PTN network.

City core layer L3 PTN adopt IP which transmit LTE service to capital L3 PTN network
Agenda
Demand Analysis
LTE Bearer Solution
Implementation of LTE L3 Functions

Area A
Area B
L3 function in core scheduling layer:
BSC/RNC
aGW
BSC/RNC
aGW
S1
PTN scheduling
layer
WDM/OTN
Iub/Abis
X2
L3
VPN
L3 function is deployed at all nodes of the core PTN

scheduling layer
Support L3 route forwarding
Support VRF and achieve logical isolation capability of
IP forwarding between VRFs
Support internal termination of E-Line service, which
is then bound to VRF for IP forwarding
Support VRRP protocol and joint operation with PTN
CC OAM detection
WDM/OTN
Dynamic routing mode:
PTN
access/aggregati
on
eNB
eNB
VIP
BTS/NodeB customer
PTN
access/aggregati
on
E-line
Static routing mode:
eNB
3G/LTE service bearing
BTS/NodeB
Support LDP/RSVP/BGP signaling

Support OSPF/ISIS routing protocols
Support static route configuration

The egress Port of static route can be static MPLS-TP
tunnel
Inherit 3G bearer network architecture to achieve smooth evolution of bearer network

LTE Bearer Network Implementation VLAN Assignment Mode
10.1.2.1
Bearer
network
10.1.3.1
S-GW
MME
10.1.1.1
10.1.4.1
Each eNodeB is assigned with a separate VLAN to be borne through E-Line at the access/aggregation layer.
Terminate E-Line through different virtual VLAN sub-Ports inside the core node to completely isolate broadcast.
Each virtual VLAN sub-Port is configured with an IP address that is in the same network section of the corresponding base station. For example, for base
station 10.1.1.1, the IP address of the corresponding virtual VLAN sub-Port can be configured as 10.1.1.2 with 24-bit mask.
The access/aggregation layer is completely compatible with the constructed PTN network; no change is needed.
Enable Super Vlan on the core node to reduce the number of internal IP addresses to be configured at the core node.
Inherit VLAN assignment mode of 3G bearer network to achieve smooth evolution of bearer network
LTE Bearer Network Implementation IP Address Assignment
10.1.1.1
Bearer
network
10.1.2.1
10.1.3.1
S-GW
MME
10.1.1.1
Virtual VLAN subPort address:
10.1.1.2
10.1.2.2
10.1.3.2
Each eNodeB is assigned with an IP address of a separate network section. Each virtual VLAN sub-Port at the core node is
configured with an IP address that is in the same network section of the corresponding base station. For example, for base
station 10.1.1.1, the IP address of the corresponding virtual VLAN sub-Port can be configured as 10.1.1.2.
If the core node enables Super Vlan, configure IP address on Super Vlan at the core node.
Inherit IP address assignment mode of 3G bearer network to achieve smooth evolution of bearer network
LTE Bearer Network Implementation Protection

Hardware protection
Clock, switching, control
process cards 1+1 hot
backup.
Power, fan 1+1 hot backup.
TPS protection
BTS/NodeB
BSC/RNC
Area B
PTN Core
sGW
eNB
PTN Agg
PTNAcc
eNB
BSC/RNC
Area A
Service
UNI
LTE
LAG protection
IMA protection
ML-PPP
NNI Core layer
NNI(Access/aggregation layer)
2G/3G
sGW
E2E LSP/PW protection

PW dual-home protection
SNC 1+1/1:1 protection
MPLS-TP section protection
VRRP redundant protection
MSP1+1/1:1 protection
Core UNI
N/A
VRRP
VPN FRR protection
LSP protection
MPLS-TP section protection
LAG protection
IP FRR protection
MSP1+1/1:1
China Mobile Full Service Bearer Network Overview

IP/MDCN
CMNet+
Backbone
CR
Core
CR
IP over OTN/WDM
BRAS
PTN Core
SR
MGW
SR
MSC
BSC/RNC
SGSN
sGW
Agg/Acc
OTN/WDM
PTN Agg
MSTP Agg
OLT
Switch
Splitter
ONU
ONU
FTTB
PTN
Acc
Splitter
FTTH
IPTV
IPTV
Public Service
HSI
eNB
BTS/NodeB
2G/3G/LTE Service
High/low value services have separate planes

PTN provides service bearing for 2G/3G/LTE and VIP customers
MSTP
Acc
PTN
Acc
VIP
NodeB
BTS/NodeB
Existing MSTP Network
LTE Bearing Solution Conclusion

ZTE fully supports the two bearing solutions. Consider the following three aspects to select
the one that better suits China Mobile.
High quality
Low cost
Easy to
implement
Meet overall LTE bearing requirements

Carrier-class protection
Little time delay
1588V2 clock
Low construction cost, reduced CAPEX

Easy to maintain, reduced OPEX
Little effect on existing network and services
Inherit 3G bearer network architecture

Inherit the original network planning principle and
resource allocation mode to the utmost extent
Agenda
Demand Analysis
LTE Bearer Solution
PTN TrendLarge Bandwidth

2G/3G stage
3G/LTE Early Stage
BSC
STM-1/4
STM-1/4
2.5/10G
RNC
GE
LTE Stage
S-GW
10GE
MME
GE
40GE/
100GE
10GE
Agg/Core
Acc
155M
E1
BTS
622M
1GE
E1
E1
NodeB
NodeB
1GE
FE
eNB
10GE
GE
eNB
10GE
GE
eNB
From 2G to 3G, the to LTE, BTS bandwidth is increasing dramatically, in LTE stage, the bandwidth of each eNB is more than
100M. eNB adopts GE port.
In LTE stage, it takes great the bandwidth pressure to Agg/Core layer, 10GE networking can not meet the requirement,
40G/100G should be adopted.
PTN TrendIntelligent
WDM/OTN
Control Plane
PE Router
GMPLS
P Router
P Router
PE Router
PTN
PTN
OTN/WDM
IP/PTN
Control Plane
OTN/WDM
OTN/WDM
The future control plane will be unified of multi-layer and multi-domain.

GMPLS will be core control protocol of unified control plane.
GMPLS provide unified path from service to bearing.
GMPLS is integrated protocol of features of data, optical transmission , ASON etc.
PTN Trend Integration

P-OTN optical platform that integrated SDH, PTN and WDM/OTN, supporting unified
control plane and NMS.
PTN
MPLSTP
PWE3
SDH
P-OTN
TDM
GFP
Sync
SDH
Ethernet/ATM
FC
OTN
SDH
Switch
Fabric
Ethernet/ATM
FC
OTN
ROADM
G.709
WDM/OTN
ROADM
The advantage of PTN and OTN integration.

Reduce equipment, save investment, simple network structure and easy management and maintenance.
ZTE PTN Product Portfolio

Agg
Acc
Core
ZXCTN 6120
ZXCTN 6220
ZXCTN
6100/6110
ZXCTN 6200
ZXCTN 6300
Packet core, high integration, and low power consumption.

Capacity from 5G to 1.28T.
Support traditional TDM/ATM services, and standard carrier Ethernet
services.
Support hardware OAM and network fast protection.
E2E QoS differentiation Services.
High Precision packet clock / Synchronization.
Unified transmission NMS, supporting E2E service management.
ZXCTN 6500 series product support L3VPN, bearing TD-LTE services
perfectly.
ZXCTN 6500 series product support 40GE, providing large bandwidth for
LTE services
ZXCTN 6500-8
ZXCTN 6500-16
ZXCTN 6500-32

S2OB - LTE Bearer Solution (PTN) - 20130510 PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

S2OB - LTE Bearer Solution (PTN) - 20130510 PDF

Загружено:

Авторское право:

Доступные форматы

LTE Bearer Solution------MPLS-TP

(High Quality & Low Costs & Simple Implementation)

LTE Bearer Solution

Implementation of The Bearer Solutions

PTN Development Trend

Aggregate global mobile traffic forecast

Changes Brought by LTE

Broadband mobile application

High-quality network bearer

ZTE Corporation. All rights reserved.

Broadband Mobile application Estimated Bearer Bandwidth

LTE throughput (Theoretical value)

The number of uplink

The downlink peak speed of single

The uplink peak speed of single

Estimated transport bandwidth of 2DL:2UL subframe

Estimated transport bandwidth of 3DL:1UL subframe

Throughput of single community (theoretically)

Throughput of single community (theoretically)

81.938 + 17.526 = 99.464Mbps

111.893 + 8.763 = 121.656Mbps

Transport bandwidth of single community (theoretically)

Transport bandwidth of single community (theoretically)

99.464 (1+10%+5%) = 114.384Mbps

121.656 (1+10%+5%) = 139.904Mbps

(Taking the consumption as 10% and the X2 service as 5%)

(Taking the consumption as 10% and the X2 service as 5%)

Transport bandwidth of single base station (theoretically, S1/1/1)

Transport bandwidth of single base station (theoretically, S1/1/1)

Transport bandwidth of single base station (estimated,

Transport bandwidth of single base station (estimated,

considering the coverage)

considering the coverage)

Indoor situation: 343.152 42% = 144.124Mbps

Indoor situation: 419.712 42% = 176.279Mbps

Outdoor situation: 343.152 32% = 109.809Mbps

Outdoor situation: 419.712 32% = 134.308Mbps

Flat Network Architecture

One BTS/NodeB only belongs to one BSC/RNC. The flows are

Wireless networks are between BTS/NodeBs.

One eNB belongs to multiple S-GW/MMEs at the same time. X2

More than 95% RAN services belong to S1 services. there are

Self-Organization Wireless Network

SON has the following four services:

Automatic software installation,

Implement automatic calculation

Find out failures through

wireless and transport parameters,

of network parameters and

automatic alarm association.

automatic detection, automatic

performance dynamically. Make

Implement isolation and

management of neighbor relations

Changes to Network Service Requirements

Differentiated services and QoS requirements

Packet loss rate

IMS signaling and OAM information (including protection and synchronization

Session video (real-time services)

Non-session video (buffer services)

Video (buffer services)

Voice, video (real-time services) and interactive games