1 / 76

PTN Network Planning

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.

turner
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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PTN Network Planning V1.0

  2. Contents • PTN Networking Scheme • Device Features • PTN Network Planning Flow

  3. 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

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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 .

  9. Contents • PTN Networking Scheme • Device Features • PTN Network Planning Flow

  10. 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.

  11. 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)

  12. 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)

  13. 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)

  14. 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)

  15. Contents • PTN Networking Scheme • Device Features • PTN Network Planning Flow

  16. 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

  17. Naming Rules • PTN network involves naming of the following four parts: • Subnets (packet name) • Sites (NE name) • Hosts (host name) • Services (circuit name)

  18. 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).

  19. 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

  20. 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

  21. 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.

  22. 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.

  23. 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.

  24. 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.

  25. 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.

  26. 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.

  27. 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

  28. 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:

  29. 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.

  30. 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.

  31. 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

  32. 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

  33. 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.

  34. 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.

  35. 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.

  36. 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

  37. 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).

  38. 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

  39. 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

  40. 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

  41. 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

  42. 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

  43. 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

  44. 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.

  45. 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：

  46. 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

  47. 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

  48. 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

  49. 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

  50. 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

More Related