2.pptx

(1)

Baseband Radio

No

Nod

de -

e - O

Ope

perrat

atio

ion a

n and

nd

Configuration

Transpor

(2)

After this chapter the participants will be

After this chapter the participants will be able to:able to: 2

2 Describe tDescribe the The Transport Nransport Network functionalitieetwork functionalities and s and introduce introduce ECIM MOMECIM MOM.. 2.1 Describe the Mu, S1, X2, Iub

2.1 Describe the Mu, S1, X2, Iub and Abisand Abis protocol and recognprotocol and recognize the Managed objectize the Managed objects related to Ts related to Transportransport network.

network.

2.2 List the transmission capabilities f

2.2 List the transmission capabilities for Baseband Radio Node and Baseband or Baseband Radio Node and Baseband Radio TNode.Radio TNode. 2.3 Relate the IP and Ethernet functionalities of

2.3 Relate the IP and Ethernet functionalities of Baseband to the RAN Transport Network.Baseband to the RAN Transport Network. 2.4 Introduce and Explain in the

2.4 Introduce and Explain in the brief the Ericsson Common brief the Ericsson Common Information Model (ECIM)Information Model (ECIM) 2.5 Compare the Managed objects related to transport network in

2.5 Compare the Managed objects related to transport network in Baseband with CPP nodes.Baseband with CPP nodes. 2.6 List out

2.6 List out the different synchronizthe different synchronization options that are ation options that are supported by the Baseband.supported by the Baseband. 2.7 Explain what IP Securit

2.7 Explain what IP Security (IPsec) is and how it is supported in y (IPsec) is and how it is supported in RANRAN 2.8 Recognize Managed Objects related to IPsec

2.8 Recognize Managed Objects related to IPsec implementation and the some key attributes that implementation and the some key attributes that define thedefine the working of IPsec

working of IPsec

Objectives of Chapter 2

(3)

Mu Protocol Stack

TCP/UDP

Radio Node

O&M Appl

IP

L2

L1

TCP/UDP

OSS / PC

O&M Appl

IP

L2

L1

Mu

Operation and Configuration

The L1 and L2 may be implement over:

•• Local access (maintenance user)

Local access (maintenance user)

•• Remote access

Remote access

O&M Applications could include:

HTTPS, SSH, SFTP, SNMP, TLS, NTP

(4)

S1 Protocol Architecture

SCTP

Radio Node

S1-AP

IP

L2

L1

SCTP

MME

S1-AP

IP

L2

L1

S1

S1 Control Plane

UDP

Radio Node

GTP-U

IP

L2

L1

UDP

S-GW

GTP-U

IP

L2

L1

S1

S1 User Plane

(5)

X2 Protocol Architecture

UDP

Radio Node

GTP-U

IP

L2

L1

UDP

Radio Node

GTP-U

IP

L2

L1

X2

SCTP

Radio Node

X2-AP

IP

L2

L1

SCTP

Radio Node

X2-AP

IP

L2

L1

X2

X2 Control Plane

(6)

Iub Protocol Architecture

UDP

Radio Node

Iub-FP

IP

L2

L1

UDP

RNC

Iub-FP

IP

L2

L1

Iub

SCTP

Radio Node

NBAP

IP

L2

L1

SCTP

RNC

NBAP

IP

L2

L1

Iub

Control Plane

(7)

Abis

Abis Pro

Protoc

tocol

ol Arc

Archite

hitectur

cture

e

L2TP

Radio Node

L2TP

Transport

Protocol

IPv4

L2

L1

L2TP

BSC

L2TP

Transport

Protocol

IPv4

L2

L1

Abis

L2TP

Radio Node

L2TP

Control

Protocol

IPv4

L2

L1

L2TP

BSC

L2TP

Control

Protocol

IPv4

L2

L1

Abis

Control Plane

User Plane

LAPD

GSM APP

LAPD

GSM APP

(8)

••

Baseband 5216/5212 hardwar

Baseband 5216/5212 hardware is

e is equipped with 3

equipped with 3

Ethernet ports for transport

••

TN A: 1Gbps Electrical Ethernet (RJ45)

••

TN B and TN C: 1Gbps/10Gbps Electrical/Optical Ethernet

(SFP+) (on 5212 TN C is 1G)

••

All ports may be

All ports may be used simultaneously

used simultaneously, either for resiliency

, either for resiliency

or for connecting site equipment

••

Connectivity of site equipment may be achieved using

routing or bridging

••

Completely flexible IP address and VLAN configuration for

all traffic types

••

RPS is replaced by Bidirectional Forwarding Detection

(BFD)

••

Virtual Routing is supported as an

Virtual Routing is supported as an enabler for traffic

enabler for traffic

separation

Baseband 5216/5212

(9)

••

Flexible synchronization support &

RAN Grand Master for

synchronization (macro and small

cells)

••

Abis over IP support for legacy GSM

••

OAM interface security, element

management and network

management

management same as

same as Baseband

Baseband

5212/5216

Baseband T605

Transmission capabilities

›

Baseband unit for advanced routing

functionality & traffic aggregation

›

Dual power feed

›

8 x E1/T1 ports (TDM)

›

5 x 1/10G ports (SFP/SFP+)

5 x 1/10G

ports (SFP/SFP+)

›

4 x 1G ports (SFP)

›

4 x 1G RJ45 electrical ports

›

(10)

Baseband 6320 and 6330 Front

panel Interfaces

P Poorrttss QQuuaannttiittyy CCoommmmeennttss P Poowweerr 22 --4488VV E ECC 11 RRJJ4455 LLMMTT 11 RRJJ4455 T TN N 22++22 2 2 x x 1010G G ((SSFFPP//SSFFPP++)) 2 x 1G 2 x 1G (RJ45(RJ45)) IIDDLLee 22 XXCCeeddee C CPPRRII 1155 SSFFPP//SSFFPP++ S Syynncc 11 RRJJ4455 E

Exxtteerrnnaall aallaarrmmss 8 8 2 2 x x RRJJ4455

SAU 1

(11)

Multiple Ethernet ports and 10GE port capability

›

The Baseband 5216 product has two SFP+

cages supporting both SFP (1G) and SFP+

(10G) modules (TN_B and

(10G) modules (TN_B and TN_C).

TN_C).

›

The Baseband 5212 product has two SFP+

cages supporting both SFP and SFP+

modules. TN_B support SFP and

modules. TN_B support SFP and SFP+, TN_C

SFP+, TN_C

supports only SFP

›

With this feature it is

With this feature it is possible to add the

possible to add the

capability of supporting SFP+ modules

capability of supporting SFP+ modules which

which

then can provide a line speed of 10 Gbps

›

Default is 1Gbps

Benefit

›

Provide higher line speed rates

›

Increase node capacity and support TN

redundancy when used together with the basic

feature “Static Routing”

›

Traffic grooming on a single backhaul interface

using “Static Routing” or “Ethernet Switching”

from other units connected to the

from other units connected to the Baseband

Baseband

unit

Baseband 5216 Baseband 5216 1 Gbps 1 Gbps(RJ45)(RJ45) 1 Gbps 1 Gbps(SFP)(SFP) OR OR 10 Gbps 10 Gbps (SFP+)(SFP+) Baseband 5212 Baseband 5212 1 Gbps 1 Gbps(RJ45)(RJ45) 1 Gbps 1 Gbps(SFP)(SFP) OR OR 10 Gbps 10 Gbps (SFP+)(SFP+) 1 Gbps 1 Gbps(SFP)(SFP)

(12)

Static Routing

IP Transport

Network

Description

–

– Static routing for IPv4 traffic is Static routing for IPv4 traffic is supportedsupported

Benefit

–

– Enables layer 3 connectivity to other parts in the network , e.gEnables layer 3 connectivity to other parts in the network , e.g IP Loopback interfaceIP Loopback interface

and supports interface resilience and supports interface resilience

Baseband Baseband Static Static

L2

Source node Source node

L2

R1 R1 R2 R2 R3 R3 Destination Destination L2 = Layer 2 L2 = Layer 2 R1/R2/R3= Routers R1/R2/R3= Routers

(13)

Ethernet Switching

Description

›

L2 switching can be used to connect external equipment on

L2 switching can be used to connect external equipment on the site or aggregate

the site or aggregate

multiple IP traffic flows to the transport network without creating additional IP sub

--network

network

Benefit

›

Easy way to get connectivity to IP

Easy way to get connectivity to IP hosts without changing the IP address plan or adding

hosts without changing the IP address plan or adding

additional hardware

›

Switching will save number of IP addresses that is required for

Switching will save number of IP addresses that is required for connectivity

connectivity

IP Transport

Network

Baseband Baseband Bridge Bridge

(14)

••

Bridged Virtual Interface (BVI) makes it possible to

have IP host functionality on an L2 Bridge

••

The IP host acts

The IP host acts as an IP gateway to the routing

as an IP gateway to the routing

function

••

The IP host can also be used for remote connectivity

to the Baseband unit,

to the Baseband unit, for example by O&M

for example by O&M

configura

configuration management, and as an

tion management, and as an IP host for

IP host for

other internal applications

••

Supports IPv6

Bridged Virtual Interface

Baseband Baseband Bridge Bridge

BVI

(15)

IP loopback Interface

Switch-site

SE

IP

IP Loopback

Interface

Description

›

The IP Loopback interface is a The IP Loopback interface is a logical IP interface not connected to logical IP interface not connected to any particular physicalany particular physical interface or internal HW in the Baseband

interface or internal HW in the Baseband

›

Supports IPv6Supports IPv6

Benefit

›

The loopback interface can be used to The loopback interface can be used to test the connectivity beyond the physical interfacetest the connectivity beyond the physical interface

›

It can be used as an IPIt can be used as an IP -endpoint to support interface resilience together with the static routing-endpoint to support interface resilience together with the static routing feature preferably together with BFD

feature preferably together with BFD

SE

Baseband

(16)

Virtual Routers

••

Virtual Routers simplifies traffic

separation and adds support for

overlapping IP addresses

••

Possibility of overlapping IPPossibility of overlapping IP addresses/routes

addresses/routes

••

Default routes possible for both RAN andDefault routes possible for both RAN and RAN O&M traffic

RAN O&M traffic

••

Typical use case is:

••

Separate RAN traffic from O&M trafficSeparate RAN traffic from O&M traffic _Baseband_Baseband

OAM OAM VR VR LTE/WCDMA LTE/WCDMA VR VR

(17)

Bidirectional Forwarding Detection

Description

››

Bidirectional Forwarding Detection is used for fast link and

path failure detection

•• Single IP-hop supportedSingle IP-hop supported

•• Can be turned on/off per logical interfaceCan be turned on/off per logical interface

•• ConfigurConfigurable able TrTransmit/Receansmit/Receiveive intervalinterval

•• Supports IPv6Supports IPv6

Benefit

››

Fast and reliable industry

Fast and reliable industry standard, layer 3

standard, layer 3

based redundancy mechanism

››

Works together with vast majority of carrie

Works together with vast majority of carrie rr

grade routers

Ethernet

Router

Router Router Router

Switch Site

BSC BSC MME MME

X

RBS RBS RBS RBS RBS RBS RBS RBS

(18)

New Transport Use Cases

IP Transport

Network

Baseband Baseband

Routing or

Bridging

••

Built-in cell site router

functionality for cost

optimized connectivity of

site equipment

Multiple ports

IP Loopback

Interface

Baseband Baseband

BFD

_›

_{Support for transport}

network resiliency with BFD

and loopback IP interfaces

›

Single port or multiple

ports

Multiple ports

Static routing

IP Loopback

Interface

Baseband Baseband

BFD

Ethernet

Transport

Network

(19)

Site connectivity using Routing

and multiple ports

Baseband

•• Several IP addresses and subnets must be usedSeveral IP addresses and subnets must be used

•• Routing in the transport Routing in the transport network towards the RBS mustnetwork towards the RBS must include routes towards the site equipment and

include routes towards the site equipment and RBSRBS

10.10.20.2/24

10.10.20.1/24

10.10.10.2/24

_{10.10.10.1/24}

Route to 10.10.20.0/24

via 10.10.10.2

(20)

Site connectivity using Switching,

BVI and multiple ports

Baseband

••

Saving IP addresses and subnets

••

Easy routing in the transport network towards the RBS

10.10.10.2/24

10.10.10.3/24

10.10.10.1/24

No routes towards

the site equipment required

(21)

Jumbo Frames

S1 S1

Background

›

› User data on S1 is User data on S1 is tunneled using GTP-U, this will add packet overhead which can lead to IPtunneled using GTP-U, this will add packet overhead which can lead to IP packages larger than 1500 bytes (max 9000 Bytes)

packages larger than 1500 bytes (max 9000 Bytes)

Description

›

› Jumbo frames are Ethernet fJumbo frames are Ethernet frames carrying IP packages longer than 1500 bytesrames carrying IP packages longer than 1500 bytes

›

› Due to Ethernet Jumbo frames NO fragmentation of IP packages is required when larger than 1500Due to Ethernet Jumbo frames NO fragmentation of IP packages is required when larger than 1500

bytes

Benefit

›

› Remove costly processing for fragmentation and reassembly in Remove costly processing for fragmentation and reassembly in end nodes.end nodes.

›

› Increase throughput on routers and Core Network nodes by reducing the number of packets that haveIncrease throughput on routers and Core Network nodes by reducing the number of packets that have

Destination Destination Address Address Source Source Address Address VLAN VLAN TAG TAG Type/ Type/ Length

Length IP PacketIP Packet FSCFSC

Ethernet Jumbo Frame

>1500bytes >1500bytes Destination Destination Address Address Source Source Address Address VLAN VLAN id id Type/ Type/ Length Length IP Packet IP Packet fragment fragment FSCFSC Ethernet Frame Ethernet Frame 1500bytes 1500bytes Destination Destination Address Address Source Source Address Address VLAN VLAN id id Type/ Type/ Length Length IP Packet IP Packet fragment fragment FSCFSC Ethernet Frame Ethernet Frame <1500bytes <1500bytes + + OR OR EPC

EPC

Internet

Baseband Baseband

(22)

Description

››

Ingress and Egress traffic filters based on 7-tuple

››

White list and black list supported

››

One or more ACLs per

One or more ACLs per IPv4 / IPv6

IPv4 / IPv6 interface

interface

››

Counters per ACL and per rule

Benefits

››

Protects the nodes against unwanted and/or malicious

traffic

››

Basic defense against attacks from an outside

Basic defense against attacks from an outside network

network

(e.g. a leased

(e.g. a leased backhaul network)

backhaul network)

››

Ensures that traffic does not enter the node

Ensures that traffic does not enter the node via an

via an

unwanted interfaces

Access Control Lists

Ingress traffic Ingress traffic

Filters on 7-tuple:

1)

1) Source Source IP IP AddrAddressess 2)

2) DestiDestinatination IP Addon IP Addressress 3)

3) PrPrototococolol 4)

4) SourSource pce portort 5)

5) DestinDestination ation portport 6)

6) ICMP ICMP tytypepe 7)

7) FraFragmegment tynt typepe

Transport Transport Baseband Baseband Permit Permit deny deny So So urc urc e: e: 10. 10. 1.2 1.2 2.0 2.0 3 3 White list White list Black list Black list S S o o ur ur c c e: e: 1 1 0. 0. 0. 0. 1 1 2. 2. 1 1 7 7

(23)

IPv6

Description

›

› Internet Protocol version 6 (IPv6) support onInternet Protocol version 6 (IPv6) support on

•

• Control and user plan trafficControl and user plan traffic

•

• IPv6 offers 128-bit addressesIPv6 offers 128-bit addresses

•

• support for Access Control Lists, Bidirectionalsupport for Access Control Lists, Bidirectional Forwarding Detection, Bridged Virtual Interface, Forwarding Detection, Bridged Virtual Interface, Loopback interface, and PTP Slave for Frequency Loopback interface, and PTP Slave for Frequency Synchronization

Synchronization

•

• support for Path MTU Discoverysupport for Path MTU Discovery

Benefit

›

› Provides support for IPv6 in the NodeProvides support for IPv6 in the Node

›

(24)

Two-Way Active Measurement Protocol Responder

(TWAMP)

Description

›

Support active monitoring of IP paths Between

Controller and Responder by injecting IP test

traffic into the network

›

Network configuration:

•

• A TWAMP responder in eNBA TWAMP responder in eNB

•

• TWAMP controller node in the networkTWAMP controller node in the network

Benefit

›

Provides monitoring support for key performance

indicators in the Transport Network

›

Ensure that SLAs (Service Level Agreements)

between the operator and their transport

network providers are being met

(25)

Two-Way Active Measurement Protocol

responder

•

• The feature works by Injecting IP test traffic intoThe feature works by Injecting IP test traffic into network from the Controller towards the

network from the Controller towards the Responder in the eNodeB (TWAMP test Responder in the eNodeB (TWAMP test packets). The Responder returns the test packets). The Responder returns the test packets to the Controller allowing the state & packets to the Controller allowing the state & performance of UP/CP paths to be analyzed performance of UP/CP paths to be analyzed

•

• The test packets are exchanged over UDP/IPv4The test packets are exchanged over UDP/IPv4 or UDP/IPv6 and follow the TWAMP protocol or UDP/IPv6 and follow the TWAMP protocol according to IETF RFC 5357

according to IETF RFC 5357

•

• The Ericsson IP Probe system can measure theThe Ericsson IP Probe system can measure the following metrics per QoS class:

following metrics per QoS class: •

• Two-way packet delayTwo-way packet delay

•

• One-way packet delayOne-way packet delay

•

• One-way packet delay variationOne-way packet delay variation

•

• One-way packet lossOne-way packet loss

•

• One-way packet reorderingOne-way packet reordering

•

(26)

TWAMP Initiator

The TWAMP Initiator in Baseband52

will enable controller functionality in

the eNB.

It will allow the possibility to actively

measure the characteristics in the

RAN backhaul links

RAN backhaul links towar

towards responder

ds responder

functionality in any node with a

TWAMP Reflector (e.g.X2

characteris

characteristics to

tics to a neighboring eNB)

a neighboring eNB)

All measurements shall be recorded as

statistics in eNB ROP files

(27)

Transport Path Characteristics Monitoring

••

To support the successful

deploymen

deployment and usage

t and usage of inter eNB

of inter eNB

co-ordination features that have

tight latency demands over X2, this

featur

feature allows t

e allows the monitori

he monitoring

ng of

of

the

the round t

round trip delay

rip delay in millis

in milliseconds

econds

between

between eNBs

eNBs which

which have

have X2

X2

connections.

••

Additionally, this feature may also

be used to mo

be used to monitor

nitor PDV (P

PDV (Packet

acket

Delay Variation) and optionally may

be used for S1 interface monitoring

also

(28)

Ericsson Common Information Model

••

ECIM

(Ericsson Common Information Model)

••

is a platform independent information model for

use by all Ericsson nodes.

••

ECIM based fragments are used for everything that

is common on all Ericsson nodes (e.g. SwM, PM

counter

counters, PM

s, PM events, FM, Licens

events, FM, Licenses, Tr

es, Transport (TN),

ansport (TN),

Sync. security, inventory, backup & restore, ..

(29)

OAM functions

ECIM Structure

ME ME SF SF FF T T EE

System Functions

Common transport

functions

Transport

Hardware entities

Equipment

Application specif

Application specific

ic

model

Function

Root class

Managed Element

Model

(30)

ECIM based MOM

ManagedElement ManagedElement SystemFunctions SystemFunctions ENodeBFunction ENodeBFunction NodeBFunction NodeBFunction BtsFunction BtsFunction NodeSupport NodeSupport Pm Pm FmFm SwM SwM Transport Transport

Common fragments for all ECIM based nodes

Node specific fragments

Equipment Equipment

…

(31)

DU Ba

DU Based n

sed nodes -

odes - CPP b

CPP based M

ased MOM

OM

ManagedElement ManagedElement IpSystem IpSystem ENodeBFunction ENodeBFunction EquipmentSupport-Function Function MceFunction MceFunction NodeManagement-Function Function Equipment Equipment TransportNetwork TransportNetwork

Common fragments for all CPP based nodes

Node specific fragments

IpOam IpOam ManagedElement-Data Data ResourceAllocation-Function Function SectorEquipment-Function

Function SupportSystem-SupportSystem-_{Configuration}_{Configuration}

SwManagement SwManagement

SystemFunctions SystemFunctions

(32)

CPP DU

CPP DU –

– COM Based

COM Based

Baseband MOM comparison:

›› Baseband MOM consists of EricssonBaseband MOM consists of Ericsson standardized fragments from ECIM standardized fragments from ECIM for:

for:

•• System FunctionsSystem Functions

•• SynchronizationSynchronization

•• TransportTransport

›› Baseband MOM has a new RBSBaseband MOM has a new RBS specific version of Equipment specific version of Equipment fragment

fragment

›› Application specific MOM for eachApplication specific MOM for each RAT common for CPP DU and RAT common for CPP DU and Baseband

Baseband

Ericsson Common

Ericsson Common Informa

Information Model

tion Model

(ECIM)

SystemFunctions SystemFunctions Equipment Equipment Managed element Managed element Transport Transport SysM SysM SwInventory SwInventory SwM SwM SecM SecM HwInventory HwInventory H Hbbm m BBrrMM Fm Fm Pm Pm PMEventM PMEventM

ECIM superset, all MOs may not be used for

ECIM superset, all MOs may not be used for every RATevery RAT

RfBranch RfBranch IuA

IuAntUntUnit nit CcCCcCablablee

R o

R ou tu te r e r H oH os ts t Ethern

EthernetPoretPort t AggregAggregator ator VlanPort VlanPort

RAT unique MO’s RAT unique MO’s

eNodeBFunction

eNodeBFunction BTSFunctionBTSFunction NodeBFunctionNodeBFunction

SectorEquipmentFunc SectorEquipmentFunc Cabinet Cabinet FRU FRU

(33)

Baseband MOM

EC

ECIM Common IM Common MOMsMOMs

ECIM Base Common: ECIM Base Common: Top Model Top Model Fault Management Fault Management Performance Management Performance Management System Management System Management SNMP SNMP

ECIM Optional Common: ECIM Optional Common: License Management License Management Security Management Security Management Security

Security – – LDAP AuthenticationLDAP Authentication Security

Security – – Local AuthorizationLocal Authorization Software Inventory Management Software Inventory Management Hardware Inventory Management Hardware Inventory Management Software Management Software Management Backup and Restore Management Backup and Restore Management Event Trace Management Event Trace Management Equipment Equipment File Management File Management Certificate Management Certificate Management Subscriber Equipment Trace Subscriber Equipment Trace

Management Management Transport Transport[1][1]

•• One XML per One XML per FragmentFragment

•• No “Node MOM”, i.e.No “Node MOM”, i.e. No overall version No overall version MOM-wise of the node MOM-wise of the node

MIM

MOM

Application

Application MO

Application MOM

M

Applic

Application MOMsation MOMs

LRAT/WRAT LRAT/WRAT Equipment Equipment FieldReplacableUnit FieldReplacableUnit AntennaUnitGroup AntennaUnitGroup SectorEquipmentFunction SectorEquipmentFunction

(34)

Some differences CPP/ECIM MOM

C

CP

PP

P D

DU

U M

MO

OM

M

Ba

B

asse

eb

ba

an

nd

d M

MO

OM

M

Common

Common non-trafficalnon-traffical relatedrelated objects.

objects.

CPP MOM with application CPP MOM with application extensions

extensions

ECIM MOM fragments ECIM MOM fragments E

Eququipipmmeennt rt reelalatetedd oobjbjeectctss CoCommplpleex (x (SuSubbrracack, k, SlSlotot,, RbsSlot, PlugInUnit, RbsSlot, PlugInUnit, AuxPlugInUnit, HwUnit, ..) AuxPlugInUnit, HwUnit, ..) Simplified. The MO Simplified. The MO FieldReplaceableUn

FieldReplaceableUnitit for for allall types of boards

types of boards T

Trraannssppoorrt t & & SSyynncc A pA paarrt t oof f tthhe e CCPPP P MMOOMM ECIMECIMTransport fragmentsTransport fragments P

PM M ccoouunntteerrss AAttttrriibbuuttees s iin rn reegguullaar Mr MOOss IInnssttaannccees s oof f MMO O ccllaassssees s iinn ECIM

ECIMPM fragmentPM fragment P

PM M eevveennttss NNoot t mmooddeelllleed d iin n MMOOMM IInnssttaannccees s oof f MMO O ccllaassssees s iinn ECIM

ECIMPM fragmentPM fragment A

Allaarrmmss NNoot t mmooddeelllleed d iin n MMOOMM IInnssttaannccees s oof f MMO O ccllaassssees s iinn ECIM

ECIMFM fragmentFM fragment LLiicceennssees s aanndd HHWWAACC LLTTEE aapppplliiccaattiioon n aaddddeed d ssppeecciiffiicc

MOs to CPP MOM MOs to CPP MOM

Instances of generic MO Instances of generic MO classes in

classes in ECIMECIMLM fragmentLM fragment E

Exxcceeppttiioonns s oon n aaccttiioonnss TThhrroowwn n wwhheen n aaccttiioon n ffaaiilleedd.. EExxcceeppttiioonns s nnoot t uusseedd iinnsstteeaad d aann error string returned on NBI. error string returned on NBI.

(35)

Ericsson Common Information Model

(36)

ECI

ECIM S

M Syst

ystem

em Fun

Functi

ctions

ons -- 1

1 Sy

Sy

st

em F

un

cti

on

s

De

scr

ip

ti

on

BrM: Backup and restore Mgmt

BrM: Backup and restore Mgmt -Create, delete and restore backups -Create, delete and restore backups on a on a ManagedElemenManagedElement.t. -Export + import of backups in file

-Export + import of backups in file format to/from a remote locationformat to/from a remote location FM: Fault Mgmt

FM: Fault Mgmt -Fetch the set of alarm types supported by a -Fetch the set of alarm types supported by a ManagedElemenManagedElementt -Fetch the list of active alarms which are present on the

-Fetch the list of active alarms which are present on the ManagedElemenManagedElement at a t at a givengiven point in time

point in time HwIM: Hardware

HwIM: Hardware InventoryInventory

Mgmt

-Check which hardware items are present on a

-Check which hardware items are present on a ManagedElemenManagedElementt

LicM: License Mgmt

LicM: License Mgmt -Download and activate license key files-Download and activate license key files -Fetch an inventory of the licenses

-Fetch an inventory of the licenses on a ManagedElement.on a ManagedElement. PM: Performance Mgmt

PM: Performance Mgmt -Determine the PM capabilities of -Determine the PM capabilities of the ManagedElement, for examplethe ManagedElement, for example



 Supported job types: MeasuremenSupported job types: Measurement Job (periodic collection), real time t Job (periodic collection), real time jobs orjobs or

threshold monitoring jobs threshold monitoring jobs



 System limits: max number of jobs System limits: max number of jobs or files or or files or measurementsmeasurements

-Determine the set of

-Determine the set of counters (instances of PmGroup + MeasurementTcounters (instances of PmGroup + MeasurementType) supportedype) supported by the

by the ManagedElemenManagedElementt

-Configuration of PM jobs on the

-Configuration of PM jobs on the ManagedElemenManagedElementt PM EventM: PM Event Mgmt

(37)

ECI

ECIM S

M Syst

ystem

em Fun

Functi

ctions

ons -- 2

2

SecM: Security Mgmt

SecM: Security Mgmt --Configuration of authentication and authorization methods and data used for Configuration of authentication and authorization methods and data used for verifyingverifying user credentials and permissions.

user credentials and permissions. -- LDAP LDAP AuthenticationAuthentication

-- Local AuthoriLocal Authorizatizationon



 Retrieval of predefined user roles and the associated rulesRetrieval of predefined user roles and the associated rules 

 Configuration of custom user roles and the associated rulesConfiguration of custom user roles and the associated rules

-CertM: Certificate Mgmt -CertM: Certificate Mgmt



 Management of node credentials and Management of node credentials and trusted certificatestrusted certificates

SwIM: Software Inventory

Mgmt

-Check which software it

-Check which software items are loaded on a ManagedElemenems are loaded on a ManagedElementt and which of thoseand which of those items are active

items are active SwM: Software Mgmt

SwM: Software Mgmt -Download, activate and delete -Download, activate and delete upgrade packagesupgrade packages

SysM: System Mgmt

SysM: System Mgmt -SNMP: SNMP Mgmt-SNMP: SNMP Mgmt -Configure the use of

-Configure the use of the SNMP protocol by the the SNMP protocol by the ManagedElemenManagedElementt -Configure NTP client association to remote NTP servers

-Configure NTP client association to remote NTP servers -Find the schema files

-Find the schema files for ECIM MIM fragments supported by the ManagedElementfor ECIM MIM fragments supported by the ManagedElement -OSS uses this to determine which MIM fragments + versions are supported by a -OSS uses this to determine which MIM fragments + versions are supported by a ManagedElemen

(38)

••

Simplified MOM handling by introduction of FieldReplacableUnit MO

••

Replaces

••

PlugInUnitPlugInUnit

••

AuxPlugInUnitAuxPlugInUnit

••

HwUnitHwUnit

••

The next table summarize the MO

The next table summarize the MO translation between CPP DU and

translation between CPP DU and

Baseband

Equipment Handling

-DU vs Baseband

DU vs Baseband

M MO O ttrreeeeCCPPPPDDUU MMO O ttrreeeeBBaasseebbaanndd E

Eqquuiippmmeenntt==11,,SSuubbrraacckk==11,,SSlloott==11,,PPlluuggIInnUUnniitt==11 EEqquuiippmmeenntt==11,,FFiieellddRReeppllaacceeaabblleeUUnniitt==11 Eq

Equipmuipmentent=1,=1,RbsRbsSubSubracrack=1k=1,Rbs,RbsSlotSlot=1,=1,AuxAuxPluPlugInUgInUnitnit=RU-=RU-1-11-1 EqEquipmuipmentent=1,=1,FieFieldRldRepleplaceaceableableUnitUnit=RU=RU-1--1-11 E

(39)

Connectivity MOM

-DU vs Baseband

DU vs Baseband

_••

_{Due to the}

_{Due to the new MO FieldReplaceableUnit, all the Connectivity MOM}

_{new MO FieldReplaceableUnit, all the Connectivity MOM}

changes the structure. Some examples below.

M

MO O ttrreeeeCCPPPPDDUU MMO O ttrreeeeBBaasseebbaanndd

E

Eququipipmementnt=1=1,S,Sububrarackck=1=1,S,Slolot=t=1,1,PlPlugugInInUnUnitit=1=1,E,EcPcPorort=t=11 EqEquiuipmpmenent=t=1,1,FiFieleldRdRepeplalaceceabableleUnUnitit=1=1,E,EcPcPorort=t=11 E

Eququipipmmenent=t=1,1,SuSubrbracack=k=1,1,SlSlotot==1,1,PPlulugIgInUnUninit=t=1,1,RiRiPPorortt EEququipipmementnt==1,1,FiFieeldldReReplplacaceaeablbleUeUnnitit==1,1,RiRiPPorortt

Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,DeviceGroup=ru,RfPort

1,DeviceGroup=ru,RfPort Equipment=1,FieldReplaceableUnit=RU-1-1,RfPortEquipment=1,FieldReplaceableUnit=RU-1-1,RfPort Equip

Equipmentment=1,Rb=1,RbsSubrsSubrack=1ack=1,RbsSl,RbsSlot=1,Aot=1,AuxPluuxPlugInUnitgInUnit=RU-1-1=RU-1-1,RiPo,RiPortrt EquipEquipmentment=1,Fie=1,FieldRepldReplaceablaceableUnitleUnit=RU-1-=RU-1-1,RiP1,RiPortort Eq

Equipuipmementnt=1=1,A,AuxuxPlPlugugInUInUnitnit=R=RRU-RU-1,D1,DeveviciceGeGroroupup=r=ru,u,RfRfPoPortrt EqEquiuipmpmenent=t=1,F1,FieieldldReReplplacaceaeablbleUeUninit=t=RRRRU-1U-1,R,RfPfPortort E

Eqquuiippmmeenntt==11,,AAuuxxPPlluuggIInnUUnniitt==RRRRUU--11,,RRiiPPoorrtt EEqquuiippmmeenntt==11,,FFiieellddRReeppllaacceeaabblleeUUnniitt==RRRRUU--11,,RRiiPPoorrtt E

Eqquuiippmmeenntt==11,,RRiiLLiinnkk EEqquuiippmmeenntt==11,,RRiiLLiinnkk E

(40)

Feature MOM

-DU vs Baseband

DU vs Baseband

The features are below “

The features are below “FeatureState

FeatureState” MO instead of

” MO instead of Optio

OptionalFea

nalFeatures

tures and the name

and the name

corresponds to the CXC code.

F

Feeaattuurre e NNaamme e CCPPPPDDUU FFeeaattuurreeNNaamme e BBaasseebbaanndd

LLiicceennssiinngg==11,,OOppttiioonnaallFFeeaattuurreess==11,,IIrrcc==11 SSyysstteemmFFuunnccttiioonnss==11,,LLmm==11,,FFeeaattuurreeSSttaattee==CCXXCC44001100331199 Li

Licecensnsining=g=1,1,OpOptitiononalalFeFeataturureses=1=1,A,AdvdvCeCellllSuSup=p=11 SystSystememFuFuncnctitionons=s=1,1,LmLm=1=1,F,FeaeatuturereStStatate=e=CXCXC4C4010103032020 Li

Licecensnsining=g=1,O1,OptptioionanalFlFeaeatuturereLiLicecensense=Bn=BnrIrIraratOtOffffloloadad SySyststememFuFuncnctitionsons=1=1,L,Lm=m=1,1,FeFeataturureSeStatatete=C=CXXC4C4010105051212

In the “description” attribute, the feature type can be seen

(41)

••

Equipment

••

TnPort

••

Transport

••

Layer 2

••

EthernetPort

••

VlanPort

••

Layer 3

••

Router

••

InterfaceIPv4

••

RoutingTable

Transport configuration

-Baseband vs DU

Baseband vs DU

›

Equipment

GigabitEthernet

configuredSpeedDuplex

›

IpInterface

›

vid=200

defaultRouter0 = 10.10.20.1

IpAccessHostEt

IpOaM

Baseband

(42)

Managed Objects for RAN Traffic and

O&M (using different vlans and IP v4/v6)

(43)

TN MOM

TN MOM –

– DU

DU

vs Baseband

›

Baseband

(44)

TN Configuration

••

Traffic and OAM on Different VLANs

›

DUs

›

Baseband

›

› OAMOAM:: A2

-A2 - Local Local IpIp AdresAdresss P2

-P2 - PrefiPrefix lengthx length A4

-A4 - DefaulDefault routert router V2

-V2 - VlaVlann Id OAId OAMM A6

-A6 - DNS serDNS serverver ›

› User PlaneUser Plane:: A1

-A1 - Local Local IpIp AdresAdresss P1

-P1 - PrefiPrefix lengthx length A3

-A3 - DefaulDefault routert router V1

(45)

Equipment=1 Equipment=1 FieldReplaceableUnit=1 FieldReplaceableUnit=1 TnPort=TN_A TnPort=TN_A TnPort=TN_B TnPort=TN_B TnPort=TN_C TnPort=TN_C

Baseband: Basic configuration for equipment

and Layer 2 transport

Transport=1 Transport=1 EthernetPort=TN_A EthernetPort=TN_A administrativeState=UNLOCKED administrativeState=UNLOCKED autoNegEnable=true autoNegEnable=true admOperatingMode=ANY admOperatingMode=ANY encapsulation=Manag

encapsulation=ManagedElement=1,EqedElement=1,Equipment=1,FieldReuipment=1,FieldReplaceableUnit=1, placeableUnit=1, TnPort=TN_ATnPort=TN_A VlanPort=OAML/OAMW/OAMG

VlanPort=OAML/OAMW/OAMG encapsulation=Man

encapsulation=ManagedElement,TranagedElement,Transport=1,EthernetPort=TNsport=1,EthernetPort=TN_A_A vid=100

vid=100

VlanPort=LTE/WCDMA/GSM VlanPort=LTE/WCDMA/GSM

encapsulation=Man

(46)

••

IpInterface, IpAccessHostEt, IpHostLink and GigabitEthernet MO are

removed

••

New MOs replace the previous one (similar

New MOs replace the previous one (similar to TCU MO structure)

to TCU MO structure)

••

Router (one traffic, one OAM)Router (one traffic, one OAM)

••

InterfaceIPv4InterfaceIPv4

••

AddressIPv4AddressIPv4

••

RouteTableIPv4StaticRouteTableIPv4Static

••

DstDst

••

NextHopNextHop

••

VlanPortVlanPort

••

EthernetPortEthernetPort

Routing

M MO O nnaammee IInntteerrffaaccee R

Roouutteerr LLTTEE//WWCCDDMMAA// GSM, OAM GSM, OAM IInntteerrffaacceeIIPPvv44 LLTTEE//WWCCDDMMAA//

GSM, OAM GSM, OAM A

AddddrreessssIIPPvv44 LLTTEE//WWCCDDMMAA// GSM, OAM GSM, OAM R

RoouutteeTTaabblleeIIPPvv44SSttaattiicc LLTTEE//WWCCDDMMAA// GSM, OAM GSM, OAM D Dsstt LLTTEE//WWCCDDMMAA// GSM, OAM GSM, OAM N

NeexxttHHoopp LLTTEE//WWCCDDMMAA// GSM, OAM GSM, OAM O

(47)

Router=1 Router=1 InterfaceIPv4=OAM InterfaceIPv4=OAM encapsulation=ManagedElement=1,Transport=1,VlanPort=OAM encapsulation=ManagedElement=1,Transport=1,VlanPort=OAM AddressIPv4=OAM address=“10.10.10.2/24" AddressIPv4=OAM address=“10.10.10.2/24"

OamAccessPoint binds here

RouteTableIPv4Static=1

Dst=OSS

Dst=OSS dst=“20.20.20.1/24"

dst=“20.20.20.1/24"

NextHop=GW_to_OSS nexthop=“10.10.10.1“

Dst=MME dst=“20.20.30.1/24“

NextHop=GW_to_MME nexthop=“10.10.20.1”

Dst=SGW

Dst=SGW dst=“20.20.40.1/24“

dst=“20.20.40.1/24“

NextHop=GW_to_SGW nexthop=“10.10.30.1”

Dst=X2_1

NextHop=GW_to_X2_1 nexthop=“10.10.40.1”

…

Dst=X2_n

SctpEndpoint,

EnodeBFunction or Iub or

AbisIp binds her

AbisIp binds here

e

Baseband transport Basic configuration for layer 3

transport

InterfaceIPv4=LTE/WCDMA/GSM

encapsulation=ManagedElem

encapsulation=ManagedElement=1,Transp

ent=1,Transport=1,VlanPort=L

ort=1,VlanPort=LTE/WCDMA/GSM

TE/WCDMA/GSM

AddressIPv4=UP/CP

AddressIPv4=UP/CP address=“10.10.20.2/24"

address=“10.10.20.2/24"

SGW SGW

IP Transport

RBS RBS RBS RBS RBS RBS OSS OSS

(48)

IP transport configuration:

Virtual Router in Baseband

Transport=1 Transport=1

EthernetPort=TN_A; VlanPort=OAM; VlanPort=WCDMA EthernetPort=TN_A; VlanPort=OAM; VlanPort=WCDMA Router=OAM

Router=OAM InterfaceIPv4=OAM InterfaceIPv4=OAM

encapsulation=ManagedE

encapsulation=ManagedElement=1,Tlement=1,Transport=1,ransport=1,VlanPort=OAMVlanPort=OAM AddressIPv4=OAM AddressIPv4=OAM address=“10.10.10.2/24" address=“10.10.10.2/24" RouteTableIPv4Static=Routes_OAM RouteTableIPv4Static=Routes_OAM Dst=1 Dst=1 dst=“0.0.0.0/0" dst=“0.0.0.0/0" NextHop=Gw_to_OSS NextHop=Gw_to_OSS nexthop=“10.10.10.1“ nexthop=“10.10.10.1“ Router=WCDMA Router=WCDMA InterfaceIPv4=WCDMA InterfaceIPv4=WCDMA encapsulation=Manag

encapsulation=ManagedElement=1,TredElement=1,Transport=1,VlanPort=Lansport=1,VlanPort=LTETE AddressIPv4=WCDMA AddressIPv4=WCDMA address=“10.10.20.2/24" address=“10.10.20.2/24" RouteTableIPv4Static=Routes_WCDMA RouteTableIPv4Static=Routes_WCDMA Dst=1 Dst=1 dst=“0.0.0.0/0" dst=“0.0.0.0/0" NextHop=Gw_to_WCDMA NextHop=Gw_to_WCDMA

(49)

Baseband Radio Node MOM for

WCDMA

(50)

Baseband Radio Node MOM for GSM

(51)

AbisIp

attri

butes

DescriptionDescription

abisIpId

abisIpId This attribute represenThis attribute represents the key of the AbisIpts the key of the AbisIp MO, used to identify an uniqueMO, used to identify an unique AbisIp

AbisIp MO MO instance.instance. bscBrokerIpAddress

bscBrokerIpAddress The BSC IP addrThe BSC IP address the GsmSectoress the GsmSector shall contact when making the initial contacshall contact when making the initial contact.t. dscpSectorControlUL

dscpSectorControlUL= 46= 46 { 0..63 }

{ 0..63 }

DSCP code for L2TP control connection between the RBS and BSC/PGW. DSCP code for L2TP control connection between the RBS and BSC/PGW. gsmSectorName

gsmSectorName[ [ 1..20 1..20 ] ] gsmSectorNamegsmSectorName is is used used as as identification identification when when contacting contacting the the BSC.BSC. The gsmSectorNam

The gsmSectorNamee is sent as attribuis sent as attribute HostNamete HostName in L2TP message Sin L2TP message SCCRQ andCCRQ and hence max string length

hence max string length is 20 characters.is 20 characters. The same name must be configured in the BSC. The same name must be configured in the BSC. Default gsmSe

Default gsmSectorNamectorName is the same is the same as gsmSectorIdas gsmSectorId (last 20 charact(last 20 characters).ers).

GRA

GRAT MOM

T MOM Configurat

Configuration

ion –

–

AbisIp 1 (2)

The AbisIp MO handles the configuration for

The AbisIp MO handles the configuration for the L2TP tunnels for the L2TP tunnels for GsmSector.GsmSector.

The L2TP tunnels between BSC and GsmSector carriers Abis traffic over IP transport network between The L2TP tunnels between BSC and GsmSector carriers Abis traffic over IP transport network between RBS and BSC.

(52)

AbisIp

attri

butes

DescriptionDescription

initialRetransmissionPeriod

initialRetransmissionPeriod= 1 { 1..10 }_{= 1 { 1..10 } Initial period from the original transmission to the}_{Initial period from the original transmission to the first retransmission}_{first retransmission} on L2TP control messages. Unit: 1 s

on L2TP control messages. Unit: 1 s ipv4Address

ipv4Address ReferenReference to AdressIPv4 MO which represents the ce to AdressIPv4 MO which represents the IPv4 address theIPv4 address the RBS shall use.

RBS shall use. keepAlivePeriod

keepAlivePeriod= = 1 1 { { 1..100 1..100 } } Number Number of of seconds seconds between between L2TP L2TP keep keep alive alive procedures. procedures. Unit: Unit: 1 1 ss maxRetransmission

maxRetransmission= = 5 5 { { 1..10 1..10 } } Maximum Maximum number number of of retransmisionsretransmisions on on L2TP L2TP control control messages.messages. retransmissionCap

retransmissionCap= = 4 4 { { 1..10 1..10 } } Capability Capability on on the the exponentially exponentially increased increased interval interval betweenbetween retransmission on L2TP control messages.

retransmission on L2TP control messages. The parameter specifies the

The parameter specifies the maximum retransmission interval.maximum retransmission interval. Unit: 1 s

Unit: 1 s

GRA

GRAT MOM

T MOM Configurat

Configuration

ion –

–

AbisIp 2 (2)

(53)

Q

o

S

S Co

Conf

nfig

igur

urat

atio

ion

n

››

QoS

QoS configur

configuration in the RBS for S1, X2, Iub and Mu traffic (mapping DSCP to

ation in the RBS for S1, X2, Iub and Mu traffic (mapping DSCP to

PCP/Pbit)

›

Baseband

›

DU

GigabitEthernet

GigabitEthernetMO (1 MO for botMO (1 MO for both Interfaces,h Interfaces,

traffic and OAM)

S Sttrruucctt AAttttrriibbuuttee EExxaammppllee d dssccppPPbbiittMMaapp ((00--6633)) 0 0 ddssccpp 00 p pbbiitt 00 5 566 DDssccpp 5566 P Pbbiitt 77 Ds DsccpPpPccpMpMapap==11(t(trrafaffficic)) DDscscpPpPccpMpMapap=2 =2 (O(OAMAM)) A Attttrriibbuuttee EExxaammppllee AAttttrriibbuuttee EExxaammppllee p pccpp00 00,,11,,22,, ppccpp00 p pccpp11 99,,1100,,1111 ppccpp11 88 … … …… p pccpp77 556 6 5577 ppccpp77

(54)

Priority Code Point (PCP) priority

P

PC

CP

P

Prriio

orriitty

y

A

Accrro

on

ny

ym

m

T

Trra

affffiic

c tty

yp

pe

ess

1

0 0 ((llo

ow

we

esstt))

B

BK

K

B

Ba

acckkg

grro

ou

un

nd

d

0

1

1 B

BE

E

B

Be

esst

t

E

Effffo

orrtt

2

2 E

EE

E

Exxcce

elllle

en

nt

t

E

Effffo

orrtt

3

3 C

CA

A

C

Crriittiicca

al

l

A

Ap

pp

plliicca

attiio

on

nss

4

4 V

VII

V

Viid

de

eo

o,

, <

< 1

10

00 0 m

mss lla

atte

en

nccy

y a

an

nd

d jjiitttte

err

5

5 V

VO

O

V

Vo

oiicce

e,

, <

< 1

10 0 m

mss lla

atte

en

nccy

y a

an

nd

d jjiitttte

err

6

6 IIC

C

IIn

ntte

errn

ne

ettw

wo

orrk

k

C

Co

on

nttrro

oll

7

(55)

DSCP mapping to P-bit vs PCP

P

-

b

i

t

D

S

C

P

0

0 0,

, 4

48 8,

, 5

56

6

1

10 0,

, 1

12 2,

, 1

14

4

2

2 S

Sp

pa

arre

e

3

1

18 8,

, 2

20 0,

, 2

22

2

4

2

26 6,

, 2

28 8,

, 3

30

0

5

3

34 4,

, 3

36 6,

, 3

38

8

6

46

7

7 N

Nw

w cco

on

nttrro

oll

P

C

P

D

S

C

P

0

1

1 Em

E

mp

pttyy

2

10

1 0,,1

12 2,,1

14

4

3

18

1 8,

, 2

20 0,

, 2

22

2

4

4 8, 1

8 , 16

6,

, 2

26 6,

, 2

28

8

5

34

3 4,

, 3

36 6,

, 3

38 8,

, 4

46

6

32

3 2,

, 4

40 0,

, 4

48

8

7

51

5 1,

,

5

54

4

(56)

Egr

Egress tr

ess traff

affic sh

ic shaping

aping -- 1

1 Description

Description

›› Limiting the bandwidth taking QoSLimiting the bandwidth taking QoS into considerinto consideration. Supportination. Supporting queues per Ethernet port with strict org queues per Ethernet port with strict or deficit weighted round robin priority

deficit weighted round robin priority

›› Queue Manager supports both Random Early Detection and Tail dropQueue Manager supports both Random Early Detection and Tail drop

›› Configurable Committed Information Rate and Committed Burst Size and depth per queueConfigurable Committed Information Rate and Committed Burst Size and depth per queue

›› Buffering up to 100ms per portBuffering up to 100ms per port

›› 32 queues per port32 queues per port

Benefit

›› Enable quality of service treatment to traffic when using “nonEnable quality of service treatment to traffic when using “non -QoS-QoS aware” transport, for backhaul withaware” transport, for backhaul with known bandwidth, e.g. SLA based transport services

known bandwidth, e.g. SLA based transport services D D S S C C P P / / P P C C P P t t o o Q Q u u e e u u e e / / P P H H B B M M a a p p p p i

i n n g g Tail dropTail drop

Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Tail drop Queue Queue Manager* Manager* Strict Strict Priority Priority and/or and/or Weighted Weighted Priority Priority T T T T T T T T T T TT T T TT TT Mean Rate Mean Rate Burst Size Burst Size

…

T T TT Queue Queue System System SScchheedduulleerr SShhaappeer r Classifier Classifier 1 1 6 6 SP1 SP1 SP1 SP1 SP1 SP1 WP WP WP WP WP WP SP2 SP2 SP2 SP2 7 7 8 8 5 5 4 4 2 2 3 3

* RED or Tail Drop * RED or Tail Drop possible

(57)

Egr

Egress t

ess tra

raffic

ffic shap

shaping -

ing - 2

2



32 queues per EthernetPort



PcpToQueue per egress VlanPort



Queues may be shared by VlanPorts

E E t t _h_h e e_r_r n n e e t t _P_P o o_r_r t t S S h h a a p p e e_r_r S S c c _h_h e e d d u u l l e e_r_r s s I I P P I I f f

DscpTo

_Pcp

V V l l a

a_n_n

PcpTo

Queue

I I P P I I f f

DscpTo

_Pcp

V V l l a

a_n_n

PcpTo

Queue

DscpTo

Pcp

E E t t _h_h e e_r_r n n e e t t _P_P o o_r_r t t S S h h a a p p e e r r S S c c _h_h e e d d u u_l_l e e_r_r s s I I P P I I f f 



DscpToPcp instance reuse



DscpToPcp per InterfaceIPv4



PCP2Queue per EthernetPort

P

c

p

2

2 Q

Q

u

e

u

e

I I P P I I f f

DscpTo

_Pcp

E E t t _h_h e e_r_r n n e e t t _P_P o o_r_r t t S S h h a a p p e e_r_r S S c c _h_h e e d d u u_l_l e e_r_r s s