Ptn network planning
This presentation is the property of its rightful owner.
Sponsored Links
1 / 76

PTN Network Planning PowerPoint PPT Presentation


  • 233 Views
  • Uploaded on
  • Presentation posted in: General

PTN Network Planning. V1.0. Contents. PTN Networking Scheme Device Features PTN Network Planning Flow. MME. MGW. S-GW. Residential. Business. BSC. Mobile. RNC. SR. BRAS. PTN Networking Scheme. ZXCTN 9008. ZXCTN 6100. ZXCTN 6200. ZXCTN 6300. ZXCTN 9004. Core layer.

Download Presentation

PTN Network Planning

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Ptn network planning

PTN Network Planning

V1.0


Contents

Contents

  • PTN Networking Scheme

  • Device Features

  • PTN Network Planning Flow


Ptn networking scheme

MME

MGW

S-GW

Residential

Business

BSC

Mobile

RNC

SR

BRAS

PTN Networking Scheme

ZXCTN 9008

ZXCTN 6100

ZXCTN 6200

ZXCTN 6300

ZXCTN 9004

Core layer

Access layer

Aggregation Layer

GE

Abis

STM-1/GE

Iub

STM-1/GE

10GE/new or legacy network

GE

GE/10GE

GE/10GE

PTN bearer network: access layer, aggregation layer and core service-landing layer


Ptn networking mode

PTN Networking Mode

CR

CE

CE

CE

MSCe

MSCe

MSCe

HLR

HLR

HLR

Core layer

RNC/B

RNC/B

RNC/B

SGSN

SGSN

SGSN

MGW

MGW

MGW

SC

SC

SC

Aggregation layer

PTN_10GE

PTN_10GE

Access layer

PTN_GE

OTN

PTN_GE

PTN_GE

SR/BRAS

PTN_10GE

PTN_10GE

OLT

OLT

PTN_10GE

OLT

  • PTN networking mode is similar to MSTP, at the preliminary stage, ring is the main network mode, and the structure is distinct.

  • For the large metro-network,PTN is set as three layers network : core layer, aggregation layer, and access layer.

  • For the small and medium size metro-network, PTN is set as end-to-end network on three layers: core 、aggregation and access layer, and some of the small size networks only include aggregation layer and access layer.


Analysis of ptn network structure

Analysis of PTN Network Structure

Core layer

Aggregation layer

Access layer

  • Provides inter-office relay circuits between core nodes and dispatches various services.

  • It should be able to dispatch services of a large capacity and transmit a variety of services.

  • For a 10GE ring, it is recommended to control 2–4 nodes; a mesh network can also be built in case of large traffic.

  • No more than 6 aggregation rings can be affiliated in the core layer.

  • The core layer and aggregation layer can be combined into one layer in a small-scale city network.

  • Be intended to aggregating and transmitting various service of a specific area and this layer features in powerful service aggregation ability and multi-service transmission ability.

  • For a 10GE ring, it is recommended to control 4–8 node.

  • No more than 8 access rings should be affiliated in this layer.

  • The access layer features flexible and quick access of various services

  • GE rings or ring network affiliated with chain network are employed.

  • For a PTN, the node amount should not exceed 15 for the sake of security; for an IP RAN, the node amount should not exceed 10.


Ptn networking planning

PTN Networking Planning

  • Networking Rules:

    • Networking separately , stop expansion of MSTP equipments as far as possible.

      • Take full consideration of the service requirement for next three years into network planning, so as to meet the unified bearing requirement of 3G and 2G base station.

      • The lead-in and evolution of PTN ask for environment-concerned treatmentand overall consideration, and newly build PTN mainly to ensure the rationality and economics .

      • If MSTPand PTN coexist, MSTP keeps stocks, while PTN meets with expansion requirement:

        • On access layer of metro-network , MSTP and PTN network will coexist for a long term, among which MSTP bears TDM service mainly,and PTN bears packet service mainly.

        • During the network evolution , service flow might cross different networks.

  • Networking Policy

    • Core layer and aggregation layer:

      • Newly build the 2nd PTN panel

        • newly build the entire network or step by step

    • Access layer:

      • In principle, it’s better to bear TDbase station、new-built nodeand IP-based service by IP devices .

      • Build the 2nd panel at crowded areas firstly, and then expand to suburban areas.


Ptn networking mode 1

Overlapping Networking:

Newly build PTN equipments based on the existing ring

Overlapping networking could meet fast development of 3Gand group customer’s requirement and avoid expansion and adjusting frequently in large and medium-sized cities, which is applicable to the scene with a lot of new-built sites and bandwidth requirement on access ring,

Requires enough assistant resources (such as equipment room、power supply、 pigtail etc.) at access layer sites.

Advantages :

less effect impact on existing services

gain abundant bandwidth.

10GE PTN

PTN

STM-64 MSTP

MSTP

GE PTN

GE PTN

STM-4 MSTP

STM-4 MSTP

PTN Networking Mode (1)

  • Disadvantages:

    • demanding assistant resources

    • much investment at the preliminary stage.


Ptn networking mode 2

Replacement

Replace MSTP by PTN if new expansion is required, which is applicable to the restricted scene lacking of fiber resource, equipment room, power supply etc.

In case of mode 1, replacement is also adapted due to the restriction on assistant resources : equipment room、power supply、fiber etc.Replace MSTP by PTN/IP RAN equipment;

Advantages :

overcome the restriction on various resources

less reformation to existing resources;

10GE PTN

PTN

STM-64 MSTP

MSTP

GE PTN

GE PTN

PTN Networking Mode (2)

  • Disadvantages :

    • circuit need cutover

    • network need adjustment

    • engineering implementation complex .


Contents1

Contents

  • PTN Networking Scheme

  • Device Features

  • PTN Network Planning Flow


Device characteristics

Device Characteristics

A philosopher said: “a rubbish is resource if in a right place”. Franklin said: “a cowry in a wrong place will be rubbish”.

  • Everything needs to be within measures.

  • We need to find out the features of different devices before planning and put them in proper place.


Zxctn 9008

ZXCTN 9008

  • ZXCTN 9008:

  • Backplane Bandwidth:

    48 x 8 x6.5625 x 64/66=2.443Tbps

  • Slot Bandwidth:

    48 x6.5625 x 64/66=305Gbps

  • Switching Capacity:

    44 x 8 x6.5625 x 64/66=2.24Tbps

  • Interface Capacity:

    48 x8=384Gbps

  • Packet transmission rate:

    40(wire speed) x8 x1.488095=476Mpps

  • Equipment power consumption:

    3200W Max

  • Equipment dimension:

    442 mm(w) x 889 mm(H) x 540 mm(D)


Zxctn 9004

ZXCTN 9004

ZXCTN 9004:

  • Backplane Bandwidth:

    48 x 4 x6.5625 x 64/66=1.222Tbps

  • Slot Bandwidth:

    48 x6.5625 x 64/66=305Gbps

  • Switching Capacity:

    44 x 4 x6.5625 x 64/66=1.12Tbps

  • Interface Capacity:

    48 x4=192Gbps(V2.8.03A)

  • Packet transmission rate:

    40(wire speed) x4 x1.488095=238Mpps

  • Equipment power consumption:

    1500W Max

  • Equipment dimension:

    442 mm(w) x 400 mm(H) x 540 mm(D)


Zxctn 6300 6200

ZXCTN 6300/6200

  • ZXCTN 6200:

  • Access capacity :

    44G

  • Service interface:

    TDM E1,IMA E1,ch STM-1/4,ATM STM-1,FE,GE,10GE

  • Equipment power consumption:

    300W Max

  • Equipment dimension:

    3U, 444 mm(w) x 130.5 mm(H) x 240 mm(D)

  • ZXCTN 6300:

  • Access capacity :

    88G

  • Service interface:

    TDM E1,IMA E1,ch STM-1/4,ATM STM-1,FE,GE,10GE

  • Equipment power consumption:

    550W Max

  • Equipment dimension:

    8U, 441 mm(w) x 352.8 mm(H) x 240 mm(D)


Zxctn 6100

ZXCTN 6100

  • ZXCTN 6100:

  • Access capacity :

    5G

  • Service interface:

    TDM E1,IMA E1,FE,GE

  • Equipment power consumption:

    40W Max

  • Typical power consumption:

    30W

  • Equipment dimension:

    1U, 442 mm(w) x 43.6 mm(H) x 225 mm(D)


Contents2

Contents

  • PTN Networking Scheme

  • Device Features

  • PTN Network Planning Flow


Ptn network planning flow

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Naming rules

Naming Rules

  • PTN network involves naming of the following four parts:

    • Subnets (packet name)

    • Sites (NE name)

    • Hosts (host name)

    • Services (circuit name)


Subnet name packet name

Subnet Name (Packet Name)

  • Format of the sub network name:

    • ring name_Num/area name

  • Format of site name:

    • PTN_site name_[Num]

  • Format of host name:

    • device type_pinying of the site name_[Num]

  • Service naming:

    • Format of a tunnel name: Tunnel_[W/P]_source site name_to_sink site name_Num(service number)_[S(unidirectional)].

    • Format of a pseudo wire (PW) name: PW_service type_source site name_to_sink site name_Num(service number).

    • Format of a pseudo wire (PW) name: PW_service type_source site name_to_sink site name_Num(service number).


Ptn network planning flow1

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Dcn networking planning

DCN Networking Planning

  • PTN NMS communicates with NEs through DCN (Data Communication Network), whereby the NEs are managed and maintained.

  • DCN is classified into two types:

    • Inband

    • Outband


Inband dcn networking

NMS Server

NMS Client

Inband DCN Networking

  • This networking scheme accomplishes network management through service channels.

  • It is able to manage NEs of:

    • A network totally composed of ZTE PTN devices;

    • Or a network composed of both ZTE devices and the third-party devices if only the devices can interconnect with each other normally.


Inband dcn networking1

Inband DCN Networking

Advantages

  • Flexible layout;

  • No need to install other devices.

Disadvantages

  • Network monitoring will be affected in case of PTN network failure because network management is accomplished using service channel bandwidth.


Inband dcn networking2

Inband DCN Networking

  • Planning rules:

    • One gateway NE allows no more than 128 non-gateway NEs to access;

    • One OSPF area can include NEs of no more than 64;

    • If the network is composed of both ZTE devices and the third-party devices, the third-party devices should allow VLAN setting (default setting: 4094, adjustable on NMS) of the DCN packets.

    • DCN bandwidth allocation

      • It is recommended to set the ETH port DCN bandwidth of non-gateway NE to 2Mbit/s and that of gateway NE to 4Mbit/s. The lowest setting is 2Mbit/s.

      • It is recommended to set the E1 port DCN bandwidth of aggregation devices to 512Kbit/s and that of access devices to 192Kbit/s.

      • To secure the reliability of telecommunication network, ring network structure is highly recommended for DCN to make sure routes are protected in case of fiber break or NE exception.


Outband dcn networking

NMS SERVER

NMS CLIENT

Outband DCN Networking

  • The outband NMS is similar to the data communication device and it transmits network management information through dedicated channels other than service channels.

  • PTN devices are connected to existing DCN network of the client and the server of NMSgets access to devices totally through the DCN network of client.

  • This kind of NMSis used to manage NEs of PTN network in the aggregation layer or core layer; it is also able to manage a network wholly composed of ZTE devices.


Outband dcn networking1

Outband DCN Networking

Advantages

  • The network management is more reliable owing to the dedicated management channels.

  • The NMSis able to acquire management information and accomplish real-time monitoring even if service channels fail.

Disadvantages

  • The user needs to provide DCN network additionally.


Outband dcn networking2

Outband DCN Networking

  • Planning rules:

    • If outband DCN networking scheme is applied to the core layer or aggregation layer, all devices at the core or aggregation nodes (mainly ZXCTN 6200 and ZXCTN 6300) should be configured as gateway NEs. An NE gets access to the NMSthrough the DCN network of client, which is connected to the ETH ports of each NE.

    • At present, ZXCTN 6200 and ZXCTN 6300 use FE and GE as network management interface. If the device has no electrical port, an electrical/optical converter should be configured.

    • Besides, ZXCTN 6200 and ZXCTN 6300 may also get access to the NMSthrough LCT port.

    • It is recommended to set the ETH interface outband DCN bandwidth of non-gateway NE to 2Mbit/s and that of gateway NE to 4Mbit/s. The lowest setting is 2Mbit/s.


Ptn network planning flow2

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Vlan and ip planning

  • Level 1: 10GE core/aggregation ring

Composed of ZXCTN 9008、9004、 6300 and 6200

  • Level 2: 10GE access ring

Composed of ZXCTN 6300 and 6200

  • Level 3: GE access ring or link

Composed of ZXCTN 6300, 6200 and 6100

VLAN and IP Planning

  • PTN ring has three levels:


Vlan and ip planning1

VLAN and IP Planning

  • PTN devices distribute information based on MPLS static labels.

  • Two kinds of VLAN are respectively used in PTN network:

    • Network monitoring VLAN for managing network management data flow.

      • Network monitoring VLAN should be configured with corresponding NMS (logical) IP address.

    • Service encapsulation VLAN for managing service flow.

      • Service encapsulation VLAN should be configured with service (logic) IP address.

        Note:

    • Being different from VLAN of the client side, service encapsulation VLAN is used for internal data forwarding of the PTN network.


Network management vlan planning rule

Network Management VLAN Planning Rule

  • Each network node interface (NNI) of the PTN device should be configured with network management VLAN .

  • Each VLAN should be configured with corresponding network management IP address.

  • Two ends of each link belong to the same VLAN area and the same IP network segment.

  • The devices should enable the LOOPBACK address as the NE IP address of network management channel. When an NNI is down, the network management can continue. The LOOPBACK must be unique in the whole network.

  • To protect the monitoring of network manager, the physical link of an access ring should form a loop.


Network management vlan planning rule1

Network Management VLAN Planning Rule

  • The value range of network management VLANID is 3001–4093

    • For 10GE Ring:

      • It is suggested to configure one VLAN for each link, the starting VLANID is 4093, and the VLANIDs are in descending order.

    • For GE Ring:

      • It is suggested to configure one VLAN for each link, the starting VLANID is 3001, and the VLANIDs are in ascending order.

        Note:

    • For a ring, VLANID of both network management VLAN and service encapsulation VLAN can repeat but the following rules must be followed:

      • Neighboring links cannot use the same VLANID;

      • Non-adjacent linkscan use the same VLAN ID

    • VLAN 4094 is specially used by 1588


Network management ip planning rule

Network Management IP Planning Rule

  • IP Address of NE

    (1) The IP address of the NE should be the same with that of the loopback address, and be different from that of the Network Management port.

    (2) The IP address of the NE (the loopback address) should be unique in the entire network (Here, the entire network refers to the network related to the service).

  • IP Address of Network Management Port

    (1)The IP addresses of the two Network Management ports of each link (or the IP addresses of the service ports) must belong to the same network segment.

    (2) The IPs of different links should belong to diffrent network segments


Network management ip planning rule1

Network Management IP Planning Rule

  • Supposed Network Management IP Address as: A.B.C.D

    • A: If the customer has special requirement, distribute the IPs as required; if no special required, follow this sequence:

      • 192 > 192-223 > 100-191 >1-99 (except for service IP)

    • B: it indicates the area/city number.

      • for instance, 1-9 refers to area/city M and 11-19 refers to area/city N; the difference between numbers may change flexibly according to actual network scale. 10 and 20 should be preserved independently for the use of layer 3 network management LOOPBACK network segment address.

    • C: it indicates the ring or link number; C>=1.

    • D:

      • for layer 3 network management monitoring, use 100-101 to respectively indicate the IP addresses of two terminals of a link;

      • for layer 2 network management monitoring, use 1-99 to respectively indicate the access devices of a ring.

        Note:

    • The last bit of network management LOOPBACK is proposed as 188, such as 192.10.1.188.


Service encapsulation vlan planning rule

Service Encapsulation VLAN Planning Rule

  • Each NNI of PTN device should be configured with a service encapsulation VLAN and each VLAN needs an IP address.

  • The two terminals of each link in a ring belong to the same VLAN area and the same IP network segment.

  • All the PTN devices should enable the service LOOPBACK address and use it as the NE identifier for service forwarding. The LOOPBACK must be unique in the whole network.

  • The value range of service encapsulation VLANID is 17–3000.

    • For 10GE ring: VLANID starts from 3000 and increases by degrees; each link has a VLAN.

    • For GE ring: VLANID starts from 101 and increases by degrees; each access ring has a VLAN.


Service encapsulation ip planning rule

Service Encapsulation IP Planning Rule

  • Supposed Service Encapsulation IP Address as: A.B.C.D

    • A: follow this sequence.

      • 10 > 11-99 > 1-9

    • B: it indicates the area/city number.

      • for instance, 1-9 refers to area/city M and 11-19 refers to area/city N; the difference between numbers may change flexibly according to actual network scale. 10 and 20 should be reserved specially for the use of service LOOPBACK network segment address.

    • C: it indicates the ring or link number; C>=1.

    • D:

      • for a 10GE ring, use 100-101 to respectively indicate the IP addresses of two terminals of a link;

      • for a GE ring, use 1-99 to respectively indicate the access devices of a ring.

        Note:

    • The last bit of service LOOPBACK is proposed as 188, such as 192.10.1.188.


Ptn network planning flow3

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Service and traffic planning

Service and Traffic Planning

  • Service Model Analysis

    • 2G/3G Non-IP-based Base Station Service Access Mode

      • The BTS and BSC of a 2Gbase station communications via TDM line, ZTE CTN devices transmit service using the PWE3 circuit emulation technology.

      • Base station access side: ZXCTN6100/6200 interconnects with BTS via its E1 interface. In simple mode, every E1 2M service is mapped to the pseudo wire upon circuit emulation and is then transmitted to ZXCTN 6300, which is the pre-node of BSC.

      • Network side: Master/Slave MPLS tunnel protection enables end-to-end service monitoring and protection.

      • Base station controller access side: ZXCTN 6300 carries out PWE3 decapsulation via the c-STM-1 interface to recover E1 service.

    • 3G IP-based Base Station Service Access Mode

      • 3G IP-based base station and BSC interconnects over the Ethernet line.

      • NodeB base station outputs IP-based service directly and it distinguishes voice, data and other services by VLAN and priority.

      • ZXCTN 6100/6200 connects to base station through its FE interface. It maps the service of base station to pseudo wire (PW) using PORT and PORT+VLAN, maps the COS or DSCP priority of IP-based service to the field EXP of label, and transmits service using end-to-end tunnel (master/slave tunnel).


Service and traffic planning1

Interface Configuration

2G GSM base station interface is nxE1;

3G ATM base station interface is nxE1、 IP-based interface is FE,LTE base station interface is FE/GE;

Group customer interface is E1、FE、GE;

xPONinterface is GE;

RNC interface is cSTM-1、GE; BSC interface is cSTM-1、E1;

BRAS and SR interface is GE;

GE/10GE is adoptedfor networking.

SR

Service and Traffic Planning

10GE

10GE

GE

RNC/BSC

Aggregation layer

Access layer

Core layer

Service access link

Service access link

PW/LSP

  • TDM/IMA E1

  • cSTM-1

  • GE

  • TDM/IMA E1

  • cSTM-1

  • FE

Access ring link

  • GE

Aggregation ring link

  • 10GE

Core ring link

  • 10GE


3g 2g service flow planning

3G/2G Service Flow Planning

2G/3G base station service is aggregation flow.

End-to-end LSP is used to transmit service.

The 2G/3Gservices on core layer are dropped at the centralized site.

The services among any relay sites are scheduled by the core ring.

As the core node and RNC/BSC are located at different sites,the services are scheduled by the relay.

Backbone core network

IP/MPLS

RNC/BSC

RNC/BSC

SR

SR

Service dropped directly

Core layer

Service scheduled via core layer

Aggregation

layer

Aggregation

layer

Access

layer

Access

layer


Group customer service flow planning

Group customer Service Flow Planning

Core layer provide L2/L3 VPN

Group customer Service is decentralized.

End-to-end LSP is used to transmit service.

Intra-domain service:provide L2 VPN service instance based on PTN network directly ;provide tunnel to bear intra-domain group customer service.

Cross-domain service: without VPN instance, PTN works just as a tunnel; SRstarts L2/L3 VPN instance.The PTN core layer will not forward the cross-domain group customer service in principle.

Backbone core network

IP/MPLS

BSC/RNC

BSC/RNC

SR

SR

Core layer

Aggregation

layer

Aggregation

layer

Cross-domain service, PTN just as tunnel

Intra-domain service,

L2 VPN

Access

layer

Access

layer


Service and traffic planning2

Service and Traffic Planning

  • Traffic model Analysis

    • E1 service transmission

      • 2G base station traffic :

        • Suppose the base station bandwidth is 2.5M

      • 3G base station traffic (rough estimation)

        • Base station peak bandwidth of densely populated city=14M

        • Base station peak bandwidth of average city=10M

        • Base station peak bandwidth of suburban city area=6M

        • Base station peak bandwidth of county area=2M

    • Ethernet service transmission


Service and traffic planning3

PTN network capacity analysis

How to calculate network bandwidth

Access ring bandwidth

=amount of sites in the ring × site bandwidth (master/slave tunnel protection)

Aggregation layer bandwidth

=amount of sites in the access ring × site bandwidth (master/slave tunnel protection)

When 1:1 protection is configured, the resource utilization rate is 50%

RNC

RNC

Service and Traffic Planning

10GE Aggregation layer

GEaccess ring


Service and traffic planning4

Service and Traffic Planning

RNC

RNC

  • Capacity Layered Planning

    • Access ring (GE ring)

      • The effective bandwidth is 80% when various encapsulations are concerned; the effective transmission efficiency of line is generally 70% when administration overheads such as OAM are concerned.

      • Amount of access ring node: n=800M/bandwidth of a node. The amount of access rings is recommended to be no more than 15 for the sake of circuit emulation, clock, service planning and bandwidth reservation

GE

cSTM-1

Core

10GbE

Aggregation

Access

GbE

GbE


Service and traffic planning5

Service and Traffic Planning

  • Capacity Layered Planning

    • Aggregation ring (10GE ring)

      • Normally, an aggregation ring contains 4–8 nodes;

      • Suppose the service bandwidth of an access ring is 800M, an aggregation ring can be connected to ten access rings at most, including around 100–200 base stations. The amount of access rings connected to one aggregation ring is subject to change depending on actual bandwidth requirement and multiplexing situation, but it is recommended to be no more than 8.

      • An access ring gets access to an aggregation ring at the shortest path. It is recommended that the master and slave path for traffic transmission pass through different nodes to avoid service interruption in case that one node fails.

    • The actual network bandwidth depends on the peak and average traffic of base station bandwidth, the amount of access rings and aggregation rings, access of other services, reserved bandwidth, service quality and so on.


Service and traffic planning6

Service and Traffic Planning

If Convergence rate is taken into consideration , the actual service bandwidth on access ring and aggregation ring will be less than the planning values.

Convergence rate :At the beginning, convergence rate can be ignored, but after a certain actual service operating, it is defined by the empirical value.

GE

10GE

10GE

GE

RNC/BSC

RNC

SR

SR

  • PTN networking bandwidth calculating case:


Service and traffic planning7

Circuit Configuration Rules

PTN support circuit that is different from traditional MSTP network

The SDH circuits are configured at different segments and the circuit configuration of access ring and aggregation ring can be considered independently.

The circuit configuration of PTN network, however, is end-to-end; that is to say an integrated path (LSP) goes all the way from a base station to the node where 2M /GE traffic is dropped.

GE

RNC

RNC

10GE

10GE

SR

SR

Service and Traffic Planning


Service and traffic planning8

Circuit Configuration Rules

Circuit Configuration Rules

Every service model of a site is configured with an LSP independently; the amount of LSP to be configured for a site depends on the service types going through the site. Multiple E1 or FE services of the same office direction should be regarded as one service and be configured on one LSP.

How to choose master and slave directions of LSP ?

Take full consideration of the condition of every node and the access and aggregation rings. Try to choose the path passing through the least nodes (including both devices and patch cord nodes) with shortest fiber-optic routing and highest security as the master LSP and the opposite direction as the slave one.

The physical routings of master and slave LSPs should be separated to avoid that two routings pass through the same network segment. In an aggregation ring, the routings of two directions should not pass the same network segment.

The master and slave LSPs of IP-based base station service should be separated completely at the access and aggregation layers to make sure an access ring is connected to an aggregation ring through two physical nodes.

Service and Traffic Planning


Service and traffic planning9

Tunnel and PW Planning

Suppose each node supports 2G、3G and group customer service at the same time, the requirements for tunnel and PW are shown below:

GE

10GE

10GE

GE

RNC/BSC

LSP Tunnel

PW

RNC

SR

SR

Service and Traffic Planning


Ptn network planning flow4

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Reliability planning

Reliability Planning

ACLpolicy

DCN

  • LAG

  • VRRP

  • LAG

  • IMA protection

PTNNetwork

RNC/BSC/SR/BRAS

  • Main /Clock/ Power board

    • 1+1 hot backup

  • Switch board

    • 3+1or 1+1hot backup

  • Service Board

    • 1:N TPS protection

  • 1+1/1:1 trail protection

  • 1+1/1:1 SNCprotection

  • STM-1 MSPlinear protection

  • MPLS-TP Ring protection

  • PW Dual-home protection

  • PTNProtection Introduction

  • PTNService Security Plan

  • VLANinsulation

  • LSPinsulation

  • VPNinsulation

  • Against Eth VLAN/MAC attacking

  • Against DDOSattacking

  • Report CPU bandwidth

  • Port CAR line speed

  • Analyze and filter packet address

  • Restrain broadcast packets


Reliability planning1

Reliability Planning

50ms

BRAS

Residential

SR

Business

BSC/RNC

BTS/NodeB

aGW

E-NB

Working route

Protection route

Service flow

  • 1+1/1:1 TunnelProtection

    • Adopt OAM detection only at the Ingress node and the Egress node, with fast detection configured either, for example, 3.3ms detection time.

    • Meet the end-to-end 50ms switching requirements.

    • Support MPLS-TP、MPLS 1+1/1:1 Tunnelprotection.


Ptn network planning

BTS

Several LSP on Section layer

CTN 6100/6200

E1

E1/FE

BSC/RNC

MSC

CTN 9000

SGSN

CTN 6300

CTN 6100/6200

MGW

CTN 6300

E1/FE

aGW

MME

CTN 9000

OAMservice flow for LSP1+1

GE

CTN 6100/6200

CTN 6100/6200

eNB

CTN 6300

Resilient protection tunnel

OAMservice flow for Ring protection

Reliability Planning

  • Ring protection

    • Advantages : Switchfast(50ms)、safe 、 reliable 、Configure simplyand efficient ,especially when LSP number is huge.

    • Similar to MSP in SDH ,avoid abundant LSP protection switching jam caused by fiber broken.

    • OAM saves costs 、 less device load 、save fiber resources .When LSP >= 1000,adopt LSP1+1protection mode, and the total bandwidth of OAM is 1000*0.2=200M; If OAM adopts the ring network protection mode, the OAM bandwidth is 1*0.2=0.2M.


Reliability planning2

Reliability Planning

Dual-homing protection

Dual-homing protection is a protection mechanism that combines the LSP 1:1/1+1 path protection and PW protection:

Protect normal network failure

Protect node-failure

Occupy a lot of resource

configuration complex

Broken fiber1: belongs to an internal failure of the PTN network; TMP-LOC triggers the tunnel switchover.

Broken fiber2: belongs to a failure between PTN and the service-side network layer; TMC-CSF triggers the PW switchover.

Broken fiber2

Protection tunnel path

Work tunnel path

Protection PW

10 GE convergence ring

GE access ring

RNC

Broken fiber1

PWprotect core-site node failure

1:1/1+1trail protect network failure with higher priority

Work tunnel

Protection tunnel 1

Work PW

Protecting PW

Protection tunnel 2


Reliability planning3

Reliability Planning

SR

RNC

GE/FE:LAG protection

STM-1: MSP protection

LAG protection

Core layer

10GE

MSTP

GE/FE:LAG protection

STM-1: MSP protection

Convergence layer

10GE

LAG protection

Access layer

GE

Protection path

Work path

IMAprotection

  • Equipment Level Protection

  • 2G/3G、Group customer service protection


Ptn network planning flow5

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Clock synchronization planning

Clock Synchronization Planning

  • ZXCTN System Clock Functions

    • Providing BITS external clock input and output interfaces;

    • Supporting SyncE interface and the SyncE clock source setting;

    • Supporting extracting the clock signal from the E1 interface and providing the clock signal compliant with the ITU-T G.813 standard;

    • Supporting the transparent transmission of customer clock on the circuit emulation E1 interface;

    • Supporting transmitting the SSM information, achieving the whole network clock synchronization according to the SSM information, supporting automatically selecting high-priority clock, and preventing timing looping, and to achieve the auto protection of the clock link and ensure the clock's reliable transmission.

    • Supporting multiple working modes, such as fast capture mode, tracing mode, holding mode and free oscillation mode;

    • Supporting monitoring and reporting the clock alarms on the system and cards;

    • Supporting the GPS interface and providing 1PPS+TOD signal, and the GPS clock recovery and 1PPS lock phase loop;

    • Supporting 1588V2time synchronousfunctions;


Clock synchronization planning1

Clock Synchronization Planning

  • Clock Protection Function

    • ZXCTN adopts the protocol mode based on SSM and BMC to realize the automatic protection switching of the clock links, thus guaranteeing the reliable transmission of synchronization.

    • The algorithm is selected in accordance with the clock path to calculate the optimal synchronization path for the synchronous messages, so as to prevent the clock from forming into rings.

    • Protection switching is conducted for the clock messages in accordance with the clock path algorithm in case of network failure.

    • Synchronous locking, holding and free oscillation of the clock massages are provided.


Clock synchronization planning2

Clock Synchronization Planning

  • Planning Principles

    • The backbone layer and convergence layer networks should be configured with the clock protection, with the active/standby clock reference sources set for the active/standby clocks switching. And the access layer tracks the synchronous Ethernet line source sent from the backbone layer and the convergence layer from both directions of the ring.

    • As for the equipment with BITS (Building Integrated Timing Supply System) or the other external clock of high accuracy available, it is proposed to adopt the external timing mode; While for the equipment with no BITS or the other external clock of high accuracy, it is proposed to adopt the line timing mode; and it is proposed to adopt the lowest clock tracking mode for the internal timing.

    • As for the equipment with BITS (Building Integrated Timing Supply System) or the other external clock of high accuracy available, it is proposed to adopt the external timing mode; While for the equipment with no BITS or the other external clock of high accuracy, it is proposed to adopt the line timing mode; and it is proposed to adopt the lowest clock tracking mode for the internal timing.


Clock synchronization planning3

Clock Synchronization Planning

  • Planning Principles

    • The line clock tracking should follow the principle of shortest path:

      • For the ring network composed of less than 6 NEs, track the reference clock source from one direction;

      • For the ring network composed of 6 or more than 6 NEs, make sure the tracking path for the line clock is the shortest. That is, in the network containing N NEs there should be N/2 NEs that track the reference clock source from the same direction, with the other N/2 NEs tracking the reference clock source from another direction.

    • For the clock long chain, clock compensation should be made. The amount of G812 slave clocks in the transmission link should not exceed 10; the amount of G813 clocks between two G812 slave clocks should not exceed 20; and the total amount of G813 clocks should not exceed 60.

    • It is proposed to adopt the extended SSM protocol (self-defined mode 2) in the entire network, configure the clock protection and prevent the clocks from forming into a ring. SSM messages can only be received within a certain attenuation scope; otherwise, it will be unable to receive them. So, it is better that the nodes on the planned ring are not more than 15.

    • It is advisable to extract clocks from the STM-N synchronous Ethernet rather than adopt the tributary signal timing between exchanges.

    • In respect of CES service clock synchronization solution, it is preferable to choose the PE synchronization mode and secondary the adaptive mode.


Ptp solution

PTPSolution

  • outband:1PPS+TOD

  • inband:FEinterface(recommended)

active timing resource

NodeB

GEring

10GEring

FE/IMA E1

FE

NodeB

outband:1PPS+TOD

10GEring

FE

FE

NodeB

GEring

FE/iMA E1

standby timing resource

NodeB

  • The timing resource which adopts active/standby clock mode is inserted into PTN network via outband 1PPS+TOD interface or 1588V2 interface.

  • SyncEthernet and 1588V2 are recommended for transmitting timing messages at the base station side.

  • We suggest adopting SyncEthernet+1588BC clock mode to speed up convergence of timing synchronization、to reduce the bottleneck and resource wasting caused by 1588 packet sending frequency.

  • Need to guarantee the accumulated offset of timing precision are not more than 900ns as passing through 15 nodes on bear network .


Ptp deployment planning application 1

PTP Deployment Planning(Application 1)

Time Synchronization route

High precision time resource

Core layer

Aggregation layer

Aggregation layer

Access layer

Access layer

Access layer

Access layer

PTNequipment 1588 V2and 3G base station link up successfully whose performance meet the requirement of 3G base station’s timing synchronization .

PTN end-to-end network

  • The word’s time resource is deployed on the core layer of the PTN end-to-end network.

  • Adopting the shortest synchronized routing principle (least hops ) according to the advanced planning.

  • Enable BMCor SSM protection rules.

  • GPS is used as a standby synchronized plan.


Ptp deployment planning application 2

PTP Deployment Planning(Application 2)

Core layer

OTN

Core layer

Aggregation layer

Time Synchronization route

High precision time resource

Aggregation layer

Aggregation layer

Access layer

Access layer

Access layer

Access layer

PTNequipment 1588 V2and 3G base station link up successfully whose performance meet the requirement of 3G base station’s timing synchronization .

When OTNequipment 1588 V2 is unavailable for commercialapplication

  • Enable several synchronized time resourcesor distribute synchronized time resources on aggregation layer.

  • Adopting the shortest synchronized routing principle (least hops ) according to the advanced planning.

  • Enable BMCor SSM protection rules.

  • GPS as a standby synchronized plan.


Ptp deployment planning application 3

PTP Deployment Planning(Application 3)

High precision time resource

Core layer

Time Synchronization route

OTN

Aggregation layer

Aggregation layer

Access layer

Access layer

Access layer

Access layer

PTNequipment 1588 V2and 3G base station link up successfully whose performance meet the requirement of 3G base station’s timing synchronization .

When OTNequipment 1588 V2 is available for commercialapplication

  • Set the high precision time resource at one of the core layer site.

  • Adopting the shortest synchronized routing principle (least hops ) according to the advanced planning.

  • Enable BMCor SSM protection rules.

  • GPS as a standby synchronized plan.


Ptn network planning flow6

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Quality of service qos planning

EF

DSCP>55

Traffic : DSCP >55

1

1

Traffic : VCI=20,30

2

AF

VCI=20,30, AF

2

Traffic : VLAN=20,30

3

VLAN=20,30

3

BE

Quality of Service (QOS) Planning

  • Single site QOS processing procedure

    • Classify customer’s services according to simple flow and complex flow

    • Define PHB processing behavior according to the flow classification result.

    • Monitor the rate according to SLA parameter for each ingress packet flow.

    • Adopt SP,SP+WRR algorithm to classify and forward service flow ,and support WRED function for congestion avoidance.

(Expedited Forward)

(Assured Forward)

(Best Effort)


Quality of service qos planning1

EF

Queue 0

PQ

WFQ

CBWFQ

AF

Classifier

Queue 1

EF

BE

Queue 2

WRR

DWRR

AF

Drop

BE

Queue N

P

P

PE

PE

IP Network

Quality of Service (QOS) Planning

  • End to End Guaranteed QoS

  • Intermediate:service dispatch according to tunnel priority, can use PQ, PQ + WFQ schedule policies

  • Egress:Pop tunnel label, restore native custom service and QoS information

  • Ingress:Identify custom services, CAC processing and service priority mapping to tunnel priority;


Zte qos deployment suggestions

ZTE QOS Deployment Suggestions

  • Different bearer multi-service , different requirement

  • Overall situation needs to be taken into consideration for QoS planning

    • Voice Service

      • Less requirement for bandwidth

      • High requirement for QoS.

      • Such as low delay, low jitter and low frame loss ratio;

      • Sufficient bandwidth needs to be reserved for voice services, providing rigid tunnels similar to those in SDH.

      • It is suggested to configure the QoS as EF according to CIR parameters, so as ensure no service packet loss.

    • Data Service

      • High bandwidth requirement and high burst, it raises a relatively low requirement for QoS, for example, statistical multiplexing of services are allowable, and it is not sensitive to delay and packet loss.

      • Regarding the advanced data services such as video, it is proposed to configure the QoS as AF according to CIR+EIR parameters, guaranteeing the bandwidth.

      • Regarding the general online services, it is proposed to configure the QoS as BE according to PIR parameters.

    • Control message

      • Less requirement for bandwidth

      • High requirement for QoS.

    • Management message

      • Less requirement for bandwidth

      • High requirement for QoS.

  • As regards the bandwidth requirement for each specific service, it should be calculated and planned according to the wireless network services.


Quality of service qos planning2

Quality of Service (QOS) Planning

Deployment Planning

Configure CIR、PIR or EIR according to the actual network bandwidth requirement.


Ptn network planning flow7

PTN Network Planning Flow

Naming Rules

DCN Networking Planning

VLAN and IP Planning

Service and Traffic Planning

Reliability Planning

Clock Synchronization Planning

Quality of Service (QOS) Planning

Operation and Maintenance (OAM)Planning


Operation and maintenance oam planning

Operation and Maintenance (OAM) Planning

  • OAM Application Mode

    • Supports the hierarchy OAM TMP/TMC/TMS (optional) , and provides the end-to-end service management, failure detection and performance monitoring.

    • In this moment, PTN network is used to bear OLE accessing from family customer and B/C group customer service. As for convergence and transparent, so careful control based on service rules is not necessary .Just the OAM(TMP)function based on LSP is enough.

    • Maybe in the future,if several kinds of PW-encapsulated services are required to transmitted in the same LSP tunnel,OAM(TMC) monitoring for PW need adding. In addition ,if MPLS-TP ring protections have been configured in the network , OAM(TMS) monitoring for section need adding.


Operation and maintenance oam planning1

Operation and Maintenance (OAM) Planning

  • OAM Failure Management Functions


Operation and maintenance oam planning2

Operation and Maintenance (OAM) Planning

  • OAM Performance Management Functions

  • OAM Other Management Functions


Operation and maintenance oam planning3

Operation and Maintenance (OAM) Planning

  • OAM and Protection Deployment Planning Rules

    • At the early stage of 3G, it is suggested to adopt the LSP 1+1 or 1:1 path protection for the number of base stations is small; and at the mid and late stage of 3G, with the increment of base stations and perfection of PTN ring network protection standards (inter-ring interconnection protection) it is suggested to adopt the ring network protection, so as to enhance the protection efficiency.

    • When the protection mode is stared, the default setting is CC detection function is on.

    • When the linear 1+1/1:1 protection mode is adopted, it is generally required to configure TMP OAM as well as fast detection (such as 3.3ms detection time); meanwhile, MIP should be set for the critical network node, so as to realize the maintenance function of loopback monitoring.

    • When the ring network protection is adopted, it is required to configure TMS OAM and fast detection as well.

    • When the protection mode is not enabled, it is required to configure at least TMP OAM; and it is suggested to configure the detection time to be 100ms.


Operation and maintenance oam planning4

OAM Deployment Planning

Enable CC function for all LSP routes that need monitoring:

If trail protection is required, enable TMP fast CC(3.3ms) function;

If ring protection is required,enable TMSfast CC(3.3ms) functionto ensure switch time is less than 50ms;

Otherwise, enable slow CC function whose CV packet forwarding frequency is 100ms instead.

Enable AIS/RDIfunction on the channels of equipment and service layer, when fault happens suddenly, AIS message will be sent out along the service flow, and RDI to the other side.

LB and LCK function can be used when locating the fault or debugging the network.

Operation and Maintenance (OAM) Planning

Working route

Working route

CC on the working route

RNC

OAM

Protecting route

Protecting route

CC on the protecting route


Operation and maintenance oam planning5

Operation and Maintenance (OAM) Planning

  • OAM Performance Management Planning

    • For the channels bearing important service, start LM function to inspect frame loss rate and long-term performance statistics

    • As service testing, start DM(On-demandworking mode) to measure frame delay and frame delay vibration.

  • OAM Other Management Planning

    • enable Automatic Protection Switching (APS)OAM cooperate with 1:1protection.

    • enable Synchronization State Information (SSM)OAM cooperate with clock/time synchronization.

    • enable Signaling Communication Channel (SCC) OAM when control panel is adopted in the future.

  • If PTN network connects to another network via ETH ,OAMfunction of 802.3ah can be started at both sides to inspect the link status , as well as loopback function etc.


  • Login