flexipacket mw - e-line & e-lan handbook - 150211

1 Copyright 2007 Nokia Siemens Networks. All rights reserved.

Ethernet services (ELAN - Eline) w FlexiPacket MWHandbookV1.2

NWS Product Management Microwave Transport February 2011


FlexiPacket - Carrier Ethernet Architecture

User-Network Interface (UNI): interface between a Carrier Ethernet device and external equipments (i.e. BTSs and RNCs);Network-Network Interface (NNI): interface between Carrier Ethernet devices;Ethernet Virtual Connection (EVC): connectivity service between two or more UNIs

UNI

UNI

BTS

ControllerUNI

UNI UNI

BTS NNI

NNI

NNI

NNI NNI

NNI

EVC

Carrier Ethernet Transport

CoreNetwork


backgroundE-Line and ELANSingle CoS and Multi CoS servicesScalability (#services)


FlexiPacket - Connectivity Services for payload

E-LinePoint to Pointconnection

FPFM200 Rel 1.0FPH800 Rel 2.0FPH1200 Rel 4.5FPH2200 Rel 4.5

E-LANMultipoint to Multipoint connection

FPFM200 Rel 1.0FPH800 Rel 2.0FPH1200 Rel5.0Drop3 FPH2200 Rel 5.0

UNI

UNI

BTS

ControllerUNI

UNI UNI

BTS


UNI

UNI

BTS

ControllerUNI

UNI UNI

BTS



FlexiPacket - Connectivity Services for payload

E-Line

E-LAN

Tight Traffic control each BTS has dedicated transport services connectivity and perf.monitoring w EthOAM

Simple configuration (Minimum number of EVC in the network)

Higher network scalability (number of BTS)

BTS to BTS L2 direct connectivity (if required)

Protection with MSTP or G.8032

Protection with G.8031 or CCM

User experience in TDM to packet migrationPoint-to-point, TDM circuit like design

UNI

UNI

BTS

ControllerBTS

UNI

UNI

BTS

ControllerUNI

UNI UNI

BTS


EVC: Single CoS - Multi CoS/ACP

UNIEVC1

EVC2

EVC3

Single CoS

UNI EVC1

criteria 1.a

criteria 1.b

criteria 1.c

EVC2

Multi CoS /ACP

CoS1

CoS2

CoS3

CoS1

CoS2

CoS3

Each EVC is associated to a single Class of Service (CoS)

Each EVC can be associated to multiple Class of Services (CoS)

MultiCoS ACP

Supported by FPFM200 R1.0EP1FPH800 R2.0

FPH1200 R5.0D2FPH2200R5.0(E-line only)

Policing per EVC per CoS

Per EVC PIR only

CoS Criteria All criteria used for EVC

PCP

ACP=Apply Customer Priority; PCP=Priority Code Point, i.e. p- bits of 802.1q VLAN


VLAN manipulation: Preservation vs. Translation

S-VLAN

Translation mode

Preservation mode (Transparent VLAN)

A Service VLAN (S-VLAN) is added in ingress at UNI port and removed in egress at UNI port

UNI UNI

UNI UNI

UNI UNI

UNI UNI

Customer VLAN (C-VLAN) is replaced with Service VLAN (S-VLAN) in ingress at UNI portService VLAN is replaced with Customer VLAN in egress at UNI port

Mandatory when ACP/MultiCos is used


FlexiPacket Network Service dimensioning

Single-CoS Multi-CoS/ACPE-Line MxN M

E-LAN (one E-LAN for K BTS)

N x (M/K) M/K

BTS#2

ControllerBTS #1 Carrier Ethernet Transport

Network parameters:

M x BTS

N x CoS for each BTS

BTS#... BTS#M

Number of required Ethernet Virtual Connection (EVC):

CoS1

CoS

CoSN

UNI

K depends on the desired limitation of broadcast domain in the access


Use Cases


Problem statement Radio Acces transport design and transport requirements

#VLAN/IP subnet at controller side interface

1x C-VLAN/subnet 1x BTS Use Case 2 (UC2)

1x C-VLAN/subnet KxBTSUse Case 1 (UC1)

:BTS #K Controller

BTS #1

BTS #K+1MWR Network

#VLAN/IP subnet at BTS interface 1 x C-VLAN/subnet

n x C-VLAN/subnet

:BTS #2K

:

:

Following slides focus on 1 x

Easy to extend results to n x

Same VLAN IDs for all BTS?

Yes No

VLAN tagged frame color symbolizes VLAN ID

Direct BTS to BTS L2 connectivity

:

:

:

:

Yes No

Radio Access Class of services:

N x Class of Services (CoS)

CoS differentiation via DSCP and PCP bits. 1k

1

k

Yes VLAN translationNo VLAN preservation

Yes E-LAN No E-Line


Use cases and MW network parameters dependency

#VLAN/IP subnet at controller side interface

1x C-VLAN/subnet 1x BTS Use Case 2 (UC2)

1x C-VLAN/subnet KxBTSUse Case 1 (UC1)

:

:

MW network design parameters

Direct BTS to BTS L2 connectivity?

:

:

:

:

Yes No

1

k

1

k

Connectivity Services:Yes (required) E-LANNo (not accepted) E-Line

Radio Acces transport design

Transport solution matrix (see next slide)

Same VLAN IDs for all BTS?

Yes No Yes VLAN translationNo VLAN preservation

VLAN manipulation

Single CoS or MultiCos/ACP services


Transport solutions vs Use Cases

Transportsolutions

Use Case

E-Line E-LANNx E-Line for each BTS Single QoS

One E-Line for each BTS Multi QoS

One E-LAN for K BTS for each service Single QoS

One E-LAN for K BTS, for all services Multiple QoS

UC11x C-VLAN/subnet

KxBTS1A 1B 1C 1D

UC21x C-VLAN/subnet 1xBTS

2A 2B 1C (w K=1) poor practical interest (*)

1D (w K=1) poor practical interest (*)

FPH1200 R4.5FPH2200 R4.5FPFM R1.0EP1FPH800 R2.0

FPH1200 R5.0D2FPH2200 R5.0FPFM R1.0EP1FPH800 R2.0

FPH2200 R5.0FPH1200 R 5.0D3 FPFM R2.0

FPH800 R2.0

(*) implementation would result in E-LAN with two UNI E-line recommended instead

Each transport solution has different Mapping rules at

UNI interface


Detailed transport solutions description vs use casesUNI MappingQoS criteria


Use Case 1- Transport solution 1A: N x E-Line for each BTS- single CoS

UNIBTS #2

Controller

UNI

UNI

BTS #1

EVC-#1

EVC-#5

(IP #1)

BTS #3 BTS #4

(IP #2)

(IP #3) (IP #4)

UNI interface at BTS side:Per C-PCP Mapping (*)- SingleCoS

UNI interface at RNC side :-Per C-PCP & Dest IP address Mapping

QoS in all devices: Based on S-PCP

Edge site

Mapping Criteria Service (S-VID) S-PCPC-PCP=1 EVC#3 (E-Line) 3C-PCP=2 EVC#4 (E-Line) 6

Mapping Criteria Service (S-VID) S-PCPIP #1 & C-PCP=1 EVC#1 (E-Line) 3IP #1 & C-PCP=2 EVC#2 (E-Line) 6IP #2 & C-PCP=1 EVC#3 (E-Line) 3IP #2 & C-PCP=2 EVC#4 (E-Line) 6IP #3 & C-PCP=1 EVC#5 (E-Line) 3

EVC-#2

EVC-#3EVC-#4

EVC-#6

EVC-#7

NNI (*)

EVC-#8UNI

(*): an equivalent mapping criteria can be based on DSCP VLAN tagged frame color symbolizes VLAN ID

For simplicity, picture shows only two CoS for each BTS


UNI interface at BTS side with FPHx200:Per VLAN Mapping with ACP

Use Case 1- Transport solution 1B: 1xE-Line for each BTS- MultiCoS/ACP

UNI UNIBTS #2

Controller

UNI

UNI NNI (*)

BTS #1

EVC-#1

EVC-#2EVC-#3

EVC-#4

(IP #1)

BTS #3 BTS #4

(IP #2)

(IP #3)(IP #4)UNI interface at BTS side with

FPFM200/FPH800 :Per C-PCP Mapping-MultiCoS

UNI interface at RNC sidewith FPFM200/FPH800 :Per C-PCP & Dest IP address Mapping -MultiQoS


Edge site

Mapping Criteria Service (S-VID) S-PCPC-PCP=1 EVC#2 (E-Line) 1C-PCP=2 EVC#2 (E-Line) 2C-PCP=3 EVC#2 (E-Line) 3C-PCP=4 EVC#2 (E-Line) 6

C-PCP S-PCP

1 12 23 34 6

Mapping Criteria

Service (S-VID)

C-VID=blue EVC#1 (E-Line)

Mapping Criteria Service (S-VID) S-PCPIP #1 & C-PCP=1 EVC#1 (E-Line) 1IP #1 & C-PCP=2 EVC#1 (E-Line) 2IP #1 & C-PCP=3 EVC#1 (E-Line) 3IP #1 & C-PCP=4 EVC#1 (E-Line) 6IP #2 & C-PCP=1 EVC#2 (E-Line) 1

ACPUNI interface at RNC side with FPHx200:Per Dest IP address with ACP

Mapping Criteria

Service (S-VID)

IP #1 EVC#1 (E-Line)IP #2 EVC#2 (E-Line)IP #3 EVC#3 (E-Line)IP #4 EVC#4 (E-Line)

C-PCP S-PCP

1 12 23 34 6

ACP


UNI interface at BTS side with FPHx200:Per C-PCP (*) Mapping

Use Case 1 - Transport solution 1C: 1xE-LAN for KxBTS and for each service- Single CoS

UNI interface at RNC side with FPHx200:Per C-PCP (*) mapping

UNI

UNI

BTS #2

Controller

UNI

UNI NNI (*)

BTS #1(IP #1)

BTS #3 BTS #4

(IP #2)

(IP #3)(IP #4)


Edge site

Mapping Criteria Service (S-VID) S-PCP

C-PCP=1 EVC#1 (E-LAN) 1C-PCP=2 EVC#2 (E-LAN) 2C-PCP=3 EVC#3 (E-LAN) 3C-PCP=4 EVC#4 (E-LAN) 6

Mapping Criteria Service (S-VID) S-PCPC-PCP=1 EVC#1 (E-LAN) 1C-PCP=2 EVC#2 (E-LAN) 2C-PCP=3 EVC#3 (E-LAN) 3C-PCP=4 EVC#4 (E-LAN) 6


(*): an equivalent mapping criteria can be based on DSCP

EVC-#2

EVC-#NEVC-#1


Use Case 1 - Transport solution 1D: 1xE-LAN for KxBTS and for all services- MultiCoS

UNI

UNI

BTS #2

Controller

UNI

UNI NNI (*)

BTS #1

EVC-#1

(IP #1)

BTS #3BTS #4

(IP #2)

(IP #3)(IP #4)



Edge site

UNI interface at BTS and RNC sidewith FPFM200/FPH800: Service Mapping Criteria

Service (S-VID)

C-VLAN=blue EVC#1 (E-LAN)

CoS Mapping Criteria

S-PCP

C-PCP=1 1C-PCP=2 2C-PCP=3 3


Use Case 2- Transport solution 2A: N x E-Line for each BTS- single CoS

UNIBTS #2

Controller

UNI

UNI

BTS #1

EVC-#1

EVC-#5

(IP #1)

BTS #3 BTS #4

(IP #2)

(IP #3) (IP #4)

port #a

UNI interface at BTS side:Per C-PCP Mapping (*)- SingleCoS

UNI interface at RNC side :-Per C-PCP & VLAN Mapping


Edge site

Mapping Criteria Service (S-VID) S-PCPC-PCP=1 EVC#3 (E-Line) 1C-PCP=2 EVC#4 (E-Line) 2

Mapping Criteria Service (S-VID) S-PCPVLAN=green & C-PCP=1 EVC#1 (E-Line) 1VLAN=green & C-PCP=2 EVC#2 (E-Line) 2VLAN=pink & C-PCP=1 EVC#3 (E-Line) 1VLAN=pink & C-PCP=2 EVC#4 (E-Line) 2

EVC-#2

EVC-#3EVC-#4

EVC-#6

EVC-#7

NNI (*)

EVC-#8UNI

(*): an equivalent mapping criteria can be based on DSCP

For simplicity, picture shows only two CoS for each BTS


Use Case 2- Transport solution 2B: one E-Line for each BTS- MultiCoS/ACP

UNI UNIBTS #2

ControllerUNI

UNI NNI (*)

BTS #1

EVC-#1

EVC-#2EVC-#3

EVC-#4

(IP #1)

BTS #3 BTS #4

(IP #2)

(IP #3) (IP #4)

Edge site

-UNI interface at RNC side with FPFM200/ FPH800:- Per VLAN+C-PCP Mapping with MultiQoS

UNI interface at RNC side with FPHx200:Per VLAN Mapping with ACP

Mapping Criteria Service (S-VID) S-PCPVLAN=green & PCP=1 EVC#1 (E-Line) 1VLAN=green & PCP=2 EVC#1 (E-Line) 2VLAN=green & PCP=3 EVC#1 (E-Line) 3VLAN=green & PCP=4 EVC#1 (E-Line) 6VLAN=pink & PCP=1 EVC#2 (E-Line) 1

C-PCP S-PCP1 12 23 34 6

Mapping Criteria Service (S-VID)C-VID=green EVC#1(E-Line)C-VID=pink EVC#2 (E-Line)

ACP

UNI interface at BTS side with FPFM200/ FPH800 : Per C-PCP Mapping withMultiCoS

Mapping Criteria Service (S-VID) S-PCPC-PCP=1 EVC#2 (E-Line) 1C-PCP=2 EVC#2 (E-Line) 2C-PCP=3 EVC#2 (E-Line) 3C-PCP=4 EVC#2 (E-Line) 6


UNI interface at BTS side with FPHx200:Per VLAN Mapping with ACP

C-PCP S-PCP1 12 23 34 6

Mapping Criteria

Service (S-VID)

C-VID=blue EVC#1 (E-Line)

ACP


Network scalability vs transport solution


Services Scalability FlexiPacket Hub x200

(*): max 128 (out of 200) with L3 mapping rule(**):max 128 (out of 369) with L3 mapping rule max 255 on LAG UNI

FlexiPacket Hub 1200 FlexiPacket Hub 2200

R 4.5 R5.0D2 R 4.5 R5.0

Max # of Eth services (E- LAN + E-line)

200 (UNI) 800 (NNI)

384 (UNI)2K (NNI)

Max # of E-Line services 200 (UNI)800 (NNI)

384 (UNI)2K (NNI)

Max # of E-LAN services None (only one Management ELAN)

planned (R5.0Drop3) None (only one Management ELAN)

49

Max number of services per UNI port

64 (R4.5) 200 (*) 64 369 (**)


Services Scalability FPFM200 and FPH800FirstMile200 R1.0 FlexiPacket Hub 800 R2.0

Max # of services: 264 (256 Ethernet + 8 CES) 632 (504 Ethernet + 128 CES)

Max # of Eth services (E-LAN + E- line)

256 504

Max # of E-Line services 256 504

Max # of E-LAN services 128 256

service number calculation See below

Max number of services per port 256 504

Real Service number:Weigth of a Service depends on: Number of classification rules (in OR; not in AND): R Number of Classes of Services: C Maximum Service number depends on Connectivity Service= E-Line/E-LAN Service number= Maximum Service number / Max [R; C]

Example1: FlexiPacket FirstMile 200 1 E-Line for BTS with 4 CoS (C=4); classification rule: VLAN ID (VLAN=10 E-Line=1; VLAN=20 E-Line=2; ) (R=1) # E-line= 256/ max [1, 4]= 256/4= 64

Example2: FlexiPacket FirstMile 200 4 E-LAN for BTS with 1 CoS each (C=1); classification rule: PCP bits AND Dest IP address/subnet it is a unique classification

rule (R=1)(PCP=1 AND IP dest=x E-LAN=1; PCP=2 AND IP dest=x E-LAN=2; PCP=1 AND IP dest=y E-LAN=3 )

# E-LAN = 128/ max [1, 1]= 128

Example3: FlexiPacket FirstMile 800 1 E-Line for BTS with 4 CoS (C=4); each BTS is identified by 3 IP addresses; classification rule: IP dest (IP dest=x1 OR IP dest=y1 OR IP dest=z1) E-Line=1; ) (R=3) # E-line= 504/ max [3, 4]= 504/4= 128


Network scalability- main concepts

UNI UNIBTS #2

controllerUNI

UNI

BTS #1

EVC-#1

EVC-#2EVC-#3 EVC-#4

(IP #1)

BTS #3 BTS #4

(IP #2)

(IP #3) (IP #4)

Edge site

In a Mobile backhauling scenario, network scalability is limided by the number of services which can be managed by a single FlexiPacket device at Edge site on a UNI interface (where all services are collected)

More devices can be stacked at Edge site to increase network scalability

In the depicted example network scalability is doubled. Half a services go through violet path, half a services go through blue path.

Edge site

NNI#1 UNI #1

NNI #2

UNI #2

FPH1

FPH2


Services Scalability vs Transport network solution

(Note 1): 128/N when mapping criteria is based on IP address (UC2)

N= Number of CoSK= Number of BTS for each E-LAN

(Note 2): 128 when mapping criteria is based on IP address (UC2)

Transportsolutions

device at Edge site

E-Line E-LANNx E-Line for each BTS Single QoS


One E-LAN for K BTS for each service Single QoS


FPFM R1.0 EP1 256/N 256/N -- 128 /N x K (Rel2.0)

FPH800 R2.0 504/N 504/N -- 256/N x K

FPH1200 R5.0D2 200/N(Note 1)

200(Note 2)

planned (R5.0Drop3) --

FPH2200 R5.0 369/N (Note 1)

369(Note 2)

49/N x K --

# Managed BTS vs Transport solution and device at Edge site


Example 1: number of managed BTS with E-Line

Network parameters:

N = # CoS / BTS (example: N=4; N=8)

1 x Classification rule @ UNI

E- Line Transport solutions:

1 x E-Line / BTS with Multi-CoS/ACP

N x E-Line / BTS with Single CoS

Max number of managed BTS (M):

CoS1

CoS

CoSN

UNI

UNI

BTS

controllerUNI

UNI UNI

BTS

when mapping criteria is based on IP address (UC2) the following values apply:(*): 32; (**): 16; (***): 128

Transportsolutions

device at Edge site

E-LineNx E-Line for each BTS Single QoS


FPFM R1.0 EP1 64 64

FPH800 R2.0 128 128FPH1200 R5.0D2 50 (*) 200 (***)

FPH2200 R5.0 92 (*) 369 (***)

Transportsolutions

device at Edge site

E-LineNx E-Line for each BTS Single QoS


FPFM R1.0 EP1 32 32

FPH800 R2.0 64 64FPH1200 R5.0D2 25 (**) 200 (***)

FPH2200 R5.0 46 (**) 369 (***)

Example 1A: # CoS/BTS =4 Example 1B: # CoS/BTS =8


Example 2: number of managed BTS with E-LAN

Network parameters:

N =# CoS / BTS (ex: N=4; N=8)

1 x Classification rule @ UNI

K = # BTS / E-LAN

E- LAN Transport solutions:

1 x E-LAN for K x BTS MultiCoS

1 x E-LAN for K x BTS- Single CoS

Max number of managed BTS (M):

CoS1

CoS

CoSN

UNI

UNI

BTS

UNI

UNI UNI

BTS

Transportsolutions

device at Edge site

E-LANOne E-LAN for K BTS for each service Single QoS


FPFM -- 1600

FPH800 -- 3200

FPH1200 planned --

FPH2200 600 --

Example 2A: # CoS/BTS =4; K=50;Transportsolutions

device at Edge site

E-LANOne E-LAN for K BTS for each service Single QoS


FPFM -- 800

FPH800 -- 1600

FPH1200 planned --

FPH2200 300 --

Example 2B: # CoS/BTS =8; K=50

controller


Further Material and IMS links

For more details about protection of E-Line and E-LAN services:https://sharenet- ims.inside.nokiasiemensnetworks.com/Open/D420423509

More details about UNI mapping and QoS setting for Interoperability among MWR products is available in the attached file:

Adobe Acrobat 7.0 Document

Ethernet services (ELAN - Eline) w FlexiPacket MWFlexiPacket - Carrier Ethernet ArchitecturebackgroundFlexiPacket - Connectivity Services for payloadFlexiPacket - Connectivity Services for payloadEVC: Single CoS - Multi CoS/ACPVLAN manipulation: Preservation vs. TranslationFlexiPacket Network Service dimensioningUse CasesProblem statement Radio Acces transport design and transport requirementsUse cases and MW network parameters dependencyTransport solutions vs Use CasesDetailed transport solutions description vs use casesUse Case 1- Transport solution 1A: N x E-Line for each BTS- single CoSUse Case 1- Transport solution 1B:1xE-Line for each BTS- MultiCoS/ACPUse Case 1 - Transport solution 1C: 1xE-LAN for KxBTS and for each service- Single CoSUse Case 1 - Transport solution 1D: 1xE-LAN for KxBTS and for all services- MultiCoSUse Case 2- Transport solution 2A: N x E-Line for each BTS- single CoSUse Case 2- Transport solution 2B:one E-Line for each BTS- MultiCoS/ACPNetwork scalability vs transport solutionServices Scalability FlexiPacket Hub x200Services Scalability FPFM200 and FPH800Network scalability- main conceptsServices Scalability vs Transport network solutionExample 1: number of managed BTS with E-LineExample 2: number of managed BTS with E-LANFurther Material and IMS links

flexipacket mw - e-line & e-lan handbook - 150211

Documents

nokia siemens networks

services4 copyright

uni portservice vlan

used8 copyright

vlan manipulation

access9 copyright

0fph800 rel

pointconnectionfpfm200