Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?

id=9283

Feature Description 151/221 04-LZA 701 6014/1 Uen AX

Egress IP Traffic Shaping

Baseband Radio Node
Contents

1 Egress IP Traffic Shaping Overview

This optional feature protects the RAN from overloading its transmission network according to an SLA.

Fe a t u r e
Egress IP Traffic Shaping Egress IP Traffic Shaping Egress IP Traffic Shaping Egress IP Traffic Shaping
Name
Fe a t u r e
FAJ 121 1823 FAJ 121 1823 FAJ 121 2117 FAJ 121 1823
I d e nti ty
Va l u e
P a c ka g e NR Base Package LTE Base Package WCDMA Base Package GSM RAN Base Package
Name
Va l u e
P a c ka g e FAJ 801 4002 FAJ 801 0400 FAJ 801 0359 FAJ 801 0386
I d e nti ty
Node Type Baseband Radio Node Baseband Radio Node Baseband Radio Node Baseband Radio Node
Access Type NR LTE WCDMA GSM
License-controlled License-controlled License-controlled License-controlled
Licensing feature. One license is feature. One license is feature. One license is feature. One license is
required for each node. required for each node. required for each node. required for each node.

Note: In case of WCDMA, The name of the feature is Egress Traffic Shaping.

Summary
The Egress IP Traffic Shaping feature is necessary in networks where resources in the transmission network are limited.
It enables controlling packet drops in networks with low bandwidth, while still allowing for a high-quality RAN.
The Ingress Remarking function can be used to change QoS marking for incoming frames and packets. If the incoming
traffic does not follow the network QoS policy, this function can be used to mitigate such scenarios.

Additional Info rmation

For more information about this feature and related topics, see Manage Quality of Service.

2 Dependencies of Egress IP Traffic Shaping

An attribute of this feature is dependent on an attribute of the Admission Control feature.

Table 1 Feature Dependencies

Fe a t u r e Rela tio n sh ip Description

Admission Control (FAJ 121 1857)
The Shaper.committedInformationRate
attribute used by the Egress IP Traffic Shaping
feature and the
Related
AdmissionControl.ulTransNwBandwidth
attribute used by the Admission Control feature
must indicate the same transport network

1 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

Fe a t u r e Rela tio n sh ip Description

bandwidth.

H a rd wa re
No specific hardware requirements.

Limitations
No known limitations.

N e t wo r k Re q u i re m e nt s
No specific network requirements.

3 Feature Operation of Egress IP Traffic Shaping

This feature enables scheduling and queuing configuration.

Configurable scheduling is used to give priority between QoS classes. For example, strict-priority scheduling can be
used to give traffic with hard latency requirements high priority. Also, DWRR scheduling can be used to share
bandwidth between QoS classes. Configurable queues are used to even out bursts to a selected level if latency is too
high and dropping packets is preferred.

The Egress IP Traffic Shaping feature consists of the following mandatory parts:

– Shaper

– Scheduler

– Queue hierarchy

– PCP to queue mapping

The feature can include the following parts as well:

– DSCP to PCP mapping

– PCP to PCP ingress remarking

– DSCP to DSCP ingress remarking

Ingress remarking of PCP is only valid for a bridged case. It is configurable for each Ethernet and VLAN interface. DSCP
to DSCP remarking can be used for both routed and switched traffic. It is configurable through Ethernet, VLAN, and IP
interface.

For more information, see Manage Quality of Service.

3.1 Shaper
Shaper behavior defines the egress bandwidth as defined in MEF 10.2 (27 October 2009).

The CIR is the Bandwidth Profile parameter. It defines the average rate of Service Frames in bps up to which the
network delivers Service Frames and meets the performance objectives. These objectives are defined by the CoS
attribute. This is the average flow described in bps. CoS is defined by the PCP for Ethernet frames.

The CBS is a bandwidth profile parameter. It limits the maximum number of bytes available for a burst of service
frames sent at the UNI. The limit determines the number of bytes that can be used for bursts in a time period. The burst
of Service Frames is sent at the UNI speed to remain conformant to CIR.

Note: CBS uses bytes, while CIR uses bits.

2 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

3.2 Scheduler
A scheduler manages its child nodes, which are either queues or schedulers. The scheduler selects the child nodes to
serve at the next transmission. When a node has a backlog of packets, it has the next transmission opportunity.

A scheduler always tries to use all available bandwidth. If a queue is empty, other queues that are not empty share the
unused bandwidth.

There are two major scheduler types, the SP scheduler and the DWRR scheduler.

In case of an SP scheduler, its child node n always has priority over child node n+1.

The DWRR scheduler follows a deficit round robin schedule, where each child queue has its own weight. It is possible
that none of the child queues are empty. In such cases, the scheduler assures the servicing of queues at the rate
specified by their weights.

3.3 Queues
A queue is a buffer used by the system to temporarily store packets that are to be forwarded.

A queue is characterized by the following entities:

– Size of the queue.

– An enqueuing behavior, which defines how data is inserted in the queue.

– A dequeuing behavior, which defines how data is extracted from the queue.

The traffic selector selects the Ethernet frames to enqueue. Traffic can be selected by the tuple {PCP, egress port
(VLAN or Ethernet)}.

The enqueuing behavior is defined by the queue type, which is either Tail Drop or RED.

A Tail Drop queue drops frames when it is full. A RED queue begins to drop frames with a probability <P> value, when it
reaches the <min> threshold. When a RED queue is full it reaches its <max> threshold. It means that <P=100%>. In
such cases, the RED queue drops all frames.

The dequeuing behavior is defined by the hierarchy of the following elements:

– Shaper

– Scheduler

– Queue

The dequeuing behavior occurs as a program that is executed every time a frame is to be forwarded.

By default, there are eight queues for each Ethernet interface in the system. The queues are denoted as Q1 to Q8. All
queues are of the QueueTailDrop MO. The default queue system is not visible in the MOM configuration.

When new Baseband units are introduced, the size of each queue in the default queue system depends on the port
capacity of the Baseband units and queue levels. For older Baseband units, each queue has a default size of 1 MB.
Table 2 shows the relationship between queue sizes and the port capacity for new Baseband units.

Table 2 Queue Size in the Default System

Por t Capacity Q u e u e Le ve l 1 Queue Level 2-5 Queue Level 6- 8 Total

(Gbps) (MB) (MB) (MB) (MB)
1 0.5 1 1 7.5
10 0.5 1 1.5 9

3 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

Por t Capacity Q u e u e Le ve l 1 Queue Level 2-5 Queue Level 6- 8 Total

(Gbps) (MB) (MB) (MB) (MB)
25 0.5 1 3.5 15

Note: The new Baseband units include the following ones and newer products:

– Baseband 6631

– Baseband 6641

– Baseband 6648

– Radio Processor 6337

– Radio Processor 6347

The memory budget for egress queue system accounts for all queue systems, which include default queue systems and
custom-created queue system, within the Baseband. For the Baseband units that support up to 25 Gbps link speed, the
total memory is up to 60 MB. For the Baseband units supporting up to 10 Gbps link speed, the total memory is up to 36
MB.

Configuration of large queues can cause latency issues, which are difficult to detect. Therefore, custom egress queue
systems must be created with caution. For a new Baseband unit, besides the queue size, a lower link capacity can
increase latency.

Note: Queue memory in the system is a shared resource. If many large queues are configured, the system can run out
of available queue memory.

The following counters provide feedback on whether the queue size setting is adequate:

– QueueRed.filledLowerThreshold

– QueueTailDrop.filledLowerThreshold

– QueueRed.filledUpperThreshold

– QueueTailDrop.filledUpperThreshold

3.4 Hierarchies
A hierarchy of five levels is supported. The hierarchy may contain the following nodes:

– A Shaper with an SP Scheduler, a DWRR Scheduler or a Queue as child.

– A DWRR Scheduler with an SP Scheduler, a DWRR Scheduler, a Shaper and/or Queues as children.

– An SP Scheduler with an SP Scheduler, a DWRR Scheduler, a Shaper and/or Queues as children. (An SP
Scheduler can have up to four children.)

– A Queue.

A Scheduler or a Shaper cannot have more than two Scheduler ancestors in the hierarchy.

3.5 PCP to Queue Maps

PCP to Queue Maps are used to specify the queue in which an Ethernet frame is to be temporarily stored. The mapping
can be configured by the operator. In the default queue system, the PCP number describes priority. PCP 7 is the highest
value. Priority descends from PCP 7 downwards. The only deviation from this rule is that PCP 1 has a lower priority
than PCP 0.

4 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

VLAN can have their own PCP to Queue Maps, which result in the following functionalities:

– More than eight queues for each EthernetPort.

– Traffic with the same PCP can be prioritized differently, if they are on different VLANs.

– Queues can be shared between PCP to Queue Maps.

– Separate PCP to Queue Maps can be used. This means that each PCP to queue map has its own queue.

It is possible that the VlanPort.egressQosQueueMap attribute on a VLAN is not set. In such cases, the PCP to
Queue Map for the underlying Ethernet interface is used.

An Ethernet interface can have more than one PCP to Queue Maps. In this case, the
EthernetPort.egressQosQueueMap attribute is to be set on the Ethernet interface to determine which map to use.
If only one map is available, the Ethernet interface uses that.

3.6 DSCP to PCP Maps

The DSCP can be mapped to the PCP in the two following ways:

– By DSCP to PCP Maps with IP interfaces (IPv4 and IPv6) not under license control

– By Ethernet-port DSCP to PCP Maps, under license control

DSCP to PCP Maps associated with the IP interfaces mark each Ethernet frame with a PCP value. This PCP value
corresponds to the DSCP value. The functionality does not require licensing.

DSCP to PCP Maps can be associated with both the IP interface and the Ethernet port. In such cases, the map
associated with the Ethernet Port overrides the map associated with the IP Interface.

It is possible that the DSCP to PCP Map is not defined for an IP interface. In this case, the IP interface uses the default
DSCP to PCP Map.

Table 3 The DSCP to PCP Map of the Default Queue System

DSCP P C P Q u e u e Le ve l
51, 54 7 Q1
32, 40, 48 6 Q2
34, 36, 38, 46 5 Q3
8, 16, 26, 28 4 Q4
18, 20, 22 3 Q5
10, 12, 14 2 Q6
none 1 Q8
0, other 0 Q7

3.7 Ingress Remarking

Ingress remarking makes it possible to handle incoming traffic that does not follow the Network QoS Policy. Such
incoming traffic can be the following, for example:

– Traffic coming from another QoS domain

– Traffic coming from nodes with poor QoS configuration possibilities

Ingress remarking can be configured to remark the following fields:

5 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

– Ingress PCP to PCP remarking (for bridging)

– Ingress DSCP to DSCP remarking (for routing and bridging)

Note: Remarking applied only to forwarded traffic and not to terminated traffic.

4 Parameters of Egress IP Traffic Shaping

This feature introduces parameters to map PCP values to a queue and to control hierarchical schedulers.

Table 4 Parameters

P arame ter Type Description

DscpDscpMap.defaultDscp
DscpDscpMap.dscp0 to
DscpDscpMap.dscp63
DscpSetToPCP.dscpSet
DscpSetToPCP.pcp
DscpToPCPMap.defaultPCP
PcpPcpMap.defaultPcp
PcpPcpMap.pcp0
PcpPcpMap.pcp1
PcpPcpMap.pcp2
PcpPcpMap.pcp3
PcpPcpMap.pcp4
PcpPcpMap.pcp5
PcpPcpMap.pcp6
PcpPcpMap.pcp7
PcpSetToQueue.pcpSet Introduced See MOM description.
PcpSetToQueue.queue
PcpToQueueMap.defaultQueue
QueueRed.exponentWeight
QueueRed.maxThreshold
QueueRed.minThreshold
QueueRed.order
QueueRed.queueSize
QueueTailDrop.order
QueueTailDrop.queueSize
SchedulerDwrr.order
SchedulerDwrr.schedulingWeight
SchedulerSp.order
Shaper.committedBurstSize
Shaper.committedInformationRate
Shaper.order

5 Network Impact of Egress IP Traffic Shaping

This feature is used to control network resources and make the network more robust. However, if this feature is
configured incorrectly, it can have a negative impact on the network.

6 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

Capacity and Perfo rmance

The Egress IP Traffic Shaping feature indirectly affects all functions that communicate over Ethernet. This feature
controls which Ethernet frames are dropped because of resource constraints, and which ones are forwarded. When
introducing the feature in a network, the network must be monitored, and it must be reconfigured if other functions
start to perform inadequately.

I n te r fa c e s
No impact.

Othe r Net work El e ments

No impact.

6 Performance of Egress IP Traffic Shaping

The feature is associated with performance management entities measuring queue utilization and queue drop rate.

KPIs
Table 5 Key Performance Indicators

KPI
Queue Utilization on Physical interfaces
Queue Utilization on Shaped Interfaces
Queue Utilization on Queue Reservation
Queue Drop rate/queue
Description
This performance indicator monitors the queue bandwidth
ratio to physical link interface.
This performance indicator monitors the queue bandwidth
ratio to SLA, that is the configured shaping value per
uplink.
This performance indicator monitors the queue bandwidth
to reserved queue bandwidth ratio of a DWRR scheduler
of an egress Queue System.
This performance indicator monitors the drop ratio caused
by traffic shaping for a specific queue.

For more information, see Transport Network Performance Indicators.

C o u nter s
There are counters associated with this feature. More information can be found in Managed Object Model (MOM).

Eve nt s
This feature has no associated events.

7 Activate Egress IP Traffic Shaping

To use the feature, it must be activated following the usual feature activation procedure.

P re re q u i s i te s

– The license key is installed in the node.

– CCTR is active for at least one week before this procedure to collect enough troubleshooting data.

S te p s

1. Set the FeatureState.featureState attribute to ACTIVATED in the FeatureState=CXC4040005 MO

instance.

After This Task

Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.

7 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

8 Deactivate Egress IP Traffic Shaping

If the feature is no longer needed, it can be deactivated following the usual feature deactivation procedure. It must
also be deactivated before the activation of any conflicting feature.

P re re q u i s i te s
CCTR is active for at least one week before this procedure to collect enough troubleshooting data.

S te p s

1. Set the FeatureState.featureState attribute to DEACTIVATED in the FeatureState=CXC4040005 MO

instance.

After This Task

Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.

Appendix A: Feature Change History

This section lists changes that affected this feature and the impact it had on the network.

Appendix A.a: 20.Q2: Egress IP Traffic Shaping Updates and Enhancements

The updates and enhancements provide egress IP traffic shaping for Baseband units with a port capacity of 25
gigabits per second (Gbps) and for legacy Baseband units.

Feature Name: Egress IP Traffic Shaping

Feature Identity: FAJ 121 1823
LTE Base Package
Value Package Name: NR Low/Mid-Band Base Package
NR High-Band Base Package
FAJ 801 0400
Value Package Identity: FAJ 801 4002/5LM
FAJ 801 4002/5H
Node Type: Baseband Radio Node
Access Type: LTE, NR

The egress IP traffic shaping update introduces the following enhancements:

– The maximum supported rate for the Shaper MO is increased to 25 Gbps

– If the configured value for CIR in the Shaper MO is between 1 byte to 1 MB, the value is still realized internally
as 1 MB

– The maximum number of child MOs for the SchedulerDwrr MO is limited to eight

Note: The child MO limitation also applies for legacy Baseband versions.

Benefits
The benefit of the egress IP traffic shaping optimization is that it provides Transport Network egress QoS functionality
for Baseband units with a port capacity of 25 Gbps.

Capacity and Perfo rmance

No impact.

8 sur 9 21/03/2024, 13:11

Egress IP Traffic Shaping https://opomenmso3.so3.vend2.ran.mob.orange.net/elex?id=9283

Operation
The SchedulerDwrr.schedulingWeight attribute can accept values from 1 up to 1000. For precise scheduling
behavior, it is recommended to use weight values up to a maximum of 200. This recommendation is only applicable for
Baseband units with a port capacity of 25 Gbps.
Note: The DWRR scheduling behavior can be imprecise if any of the SchedulerDwrr.schedulingWeight
parameter values are set to more than 200.
The shaper allows bursting a maximum of 64,000 bytes even if the Shaper.committedBurstSize attribute is set to
more than 64,000 bytes.

I n te r fa c e s
No impact.

H a rd wa re
No special hardware requirements.

Othe r Net work El e ments

No impact.

Legal | © Ericsson AB 2016-2022

9 sur 9 21/03/2024, 13:11