Technology Profile and Speed Profile

Implementation
Shaun Missett (System Architect)
Radisys
VOLTHA Technical Lockdown Jan, 2018 AT&T Facility
San Ramon CA

• Much discussion around how addition of Specific

XPON Technology had migrated into VOLTHA Core and
general desire to make VOLTHA Core Technology
Agnostic to allow for support of a variety of Access
Technologies and Access Node Adapters.
 WT-385 model support added
Early 2018 It became apparent there were some architectural issues with
VOLTHA – the goal was for VOLTHA to be technology neutral, however Nokia
had added support for XPON Management which added very specific code and
technology specific knowledge to VOLTHA
 VOLTHA Technical Lockdown Meeting at AT&T
Dallas Facility April 2018
• Radisys and ONF propose a ‘Technology Profile’ and ‘Bandwidth Profile’
model to allow creation of a set of Profiles, containing Access Technology
specific information, which are loaded into the VOLTHA database and
referenced by OpenFlow for each Upstream and Downstream Flow created.
• Voltha Core neither sees nor interprets the ‘Technology Profile’ contents
only the OLT and ONU Adapters do that.
• Bandwidth (Speed) Profiles are maintained separately from the Technology
Profile as they can be highly variable.
• OpenFlow Meters and their Meter Bands are used to implement the
Subscriber Bandwidth (Speed) Profiles.
 OpenFlow and Technology Profiles
Tech. Profile Identifiers
XPON Technology Profile: 1. Name
2. OF Table Tech Profile ID
1. ITU: G.989.3/G.988 + 3. Profile Type
4. Profile Version
2. BBF: WT-385/TR-383+
3. Instance Control + Common Instance Control Instance Control =
1. ONU: Single/Multi 1) TR-156 4+1
4. OF Table ID (64-255 Metadata 2. UNI: Single/Multi
2) TR-280
3. # GEM Ports(Queues)
16-Bit Value) Enhanced QoS
U/S Scheduler D/S Scheduler
1. Additional Bandwidth {None | NA | BE | Auto}
1. Priority
2. T-CONT;Fixed Bandwidth RF
3. T-CONT; Priority 2. Weight
3. Queue Scheduling Policy
4. T-CONT; Weight
5. Queue Scheduling Policy

U/S GEM Config & Sched Attributes D/S GEM Config & Sched Attributes
1. Per GEM Port Attributes: 1. Per GEM Port Attributes:
I. P-Bit Map V. Weight I. P-Bit Map V. Weight
II. AES Encryption VI. Discard Policy II. AES Encryption VI. Discard Policy
a. Min Threshold a. Min Threshold
III. Scheduling Policy b. Max Threshold
III. Scheduling Policy
b. Max Threshold
IV. Priority c. Max Probability IV. Priority c. Max Probability
 BBF Standards and xPON Service Models
• Access Service Definition and Compliance Testing: N:1, 1:1, VBES,
Multicast, Wholesale Model
BBF TR-101

4+1 Service BBF.247

BBF TR-156 Model BBF TR-255
Certification

BBF TR-178

BBF.247 Certification Definition for

Issue 1 Focus on XG(S) PON/NGPON2
BBF TR-280 Enhanced QoS and Underway
Multicast
6
 BBF TR-156 4+1 Service Model
• TR-156 – OLT Allocates 4 Service T-CONTs(Alloc-IDs) per ONU + 1
default T-CONT(Alloc-ID) for OMCI. Each UNI gets 4 GEM Port-IDs,
1 per T-CONT.
Each Tech. Profile is a PON CoS:
OLT
150 Mb/s Common Instance Control:
Service T-CONTS
ONU = Single(TR-156)
ONU #16 Each UNI has a single GEM Mapped to each
BE AF-1 AF-2 EF CoS/T-CONT
50 Mb/s 100 Mb/s ONU #16
Per UNI GEM Ports U U Per UNI GEM Ports
N N
I I
# #
BE AF-1 AF-2 EF 1 2 BE AF-1 AF-2 EF
7
 BBF TR-280 Service Model
• TR-280 Enhanced QoS Model – OLT Allocates 1 Service T-CONT(Alloc-ID) per
ONU per Service. Each Service gets up to 8 GEM Port-Ids allocated.

Each Tech. Profile is a Service:

OLT Common Instance Control:
50 Mb/s
100 Mb/s
ONU = Multi(TR-280)
Service T-CONTS
ONU #16 Each T-CONT is a Single Service Scheduler
Service A 1
with 1 or more GEM Port ID associated with
Service A 2
it.
100 Mb/s ONU #16
Per UNI GEM Ports U U Per UNI GEM Ports
N N
I I
# #
CoS1 CoS2 CoS3 CoS4 1 2 CoS1 CoS2 CoS3 CoS4
8
 OpenFlow Meters and Upstream/Downstream
Bandwidth Profiles
The Meter referenced in the OpenFlow message are used to generate the Downstream
Bandwidth(Speed) Profile for the Service and also the Upstream DBA Bandwidth
Parameters.
Each OpenFlow Meter contains an unordered list of meter bands, where each meter band
specifies the rate of the band, burst size and the way to process the packet

Using the MEF (MEF 10.3 ) Service definitions we can allow for a Flow Bandwidth to have
the following attributes:
CIR – Committed Information Rate, CBS - Committed Burst Size
EIR - Excess Information Rate, EBS - Excess Burst Size
And for Upstream Bandwidth only the DBA parameters allow for an AIR component.

An Openflow Meter will have up to three Meter Bands. Initially we had up to two bands
but since the Fixed Bandwidth was moved out of the Technology Profile we ended up with
three. 9
 Upstream Bandwidth Profile Representation

G.989.3 defines a Strict priority hierarchy among

the forms of assigned bandwidth:
1) Fixed bandwidth (highest priority). RF
2) Assured bandwidth. RA
3) Non-assured bandwidth.
4) Best-effort bandwidth (lowest priority).
First, the OLT should assign the fixed bandwidth to all Alloc-IDs on the PON, regardless of their individual
offered loads and the overall traffic conditions.
Then the OLT completes the guaranteed bandwidth component assignment by allocating
assured bandwidth to each Alloc-ID until either the respective provisioned level RA is reached or the traffic
demand is satisfied.
After that, the OLT allocates non-assured bandwidth components to the eligible unsaturated Alloc-IDs until
either all the Alloc-IDs reach their saturation level (that is, the lesser of the respective maximum bandwidth RM
and offered load RL(t)), or the surplus bandwidth pool SNA(t) is exhausted.
Finally, the OLT allocates best-effort bandwidth components to the eligible unsaturated Alloc-IDs.
 Upstream Bandwidth Profile Representation
CIR/CBS = Fixed, AIR = Assured, EIR/EBS = RM
In general, the bandwidth and eligibility components of the Alloc-ID traffic descriptor may have different interrelations with each other.
The five combinations of Alloc-ID traffic descriptor parameters that, in practical terms, appear more important than the others are
identified and associated with the specific T-CONT types. The definition of the five T-CONT types is given in the Table below:

Traffic descriptor component Type 1 Type 2 Type 3 Type 4 Type 5

Fixed bandwidth (BW) RF RF

Meter Band 1 Meter Band 1
(CIR) (CIR)

Burst == 0
Assured BW RA RA RA
Meter Band 1 Meter Band 1 Meter Band 2
(AIR) (AIR) (AIR)

Maximum BW RM = RF RM = RA RM > RA RM RM ≥ RF + RA
Meter Band 1 Meter Band 2 Meter Band 2 Meter Band 1 Meter Band 3
(CIR) (AIR) (PIR) (PIR) (PIR)

Burst == 0 Burst > 0

Additional BW eligibility None None NA BE Any
(Tech. Profile Specified)
Downstream Bandwidth Profile Representation
CIR/CBS = CIR/CBS, EIR/EBS = EIR/EBS

CIR – Committed Information Rate, CBS - Committed Burst Size

EIR - Excess Information Rate, EBS - Excess Burst Size
 AT&T HSIA Example(TR-280 Service Model)
Single T-CONT with Four GEM Ports Example (4QueueHybridProfileMap1)
The AT&T Open OMCI document describes an High Speed Internet Access (HSIA) Service with a Single T-CONT and Four Gem Ports (Queues):

Service Traffic Priority PBIT Scheduling Upstream Downstream Traffic Type

GEM Class Queue Policy Weight Weight

GEM4 TC6 Q1(Higher 6,7 Strict Priority N/A N/A NC, H1

Priority)
(voice)

GEM3 TC4 Q2 5 Strict Priority N/A N/A EF

(igmp)

GEM2 TC2 Q3 1,3,4 WRR 75% 90% H2, L1

(vod/icc)

GEM1 TC0 Q4(Lower 0,2 WRR 25% 10% BE,AF

Priority)
(HSIA)

13
 Technology Profile Example(AT&T HSIA Service)
Name: ‘4QueueHybridProfileMap1’
OpenFlow Table ID; 64
Profile Type: xPON, Profile Version: 1.0
Upstream Aggregate Scheduler Attributes:
• T-CONT; Single Instance per ONU or multi-instance: Multi-instance(BBF TR-280)
• T-CONT; Single Instance per UNI or multi-instance: Single-instance
• T-CONT; xPON Fixed Bandwidth upstream guaranteed bandwidth RF (Section 7
G.989.3): 0 b/s
• T-CONT; xPON Priority (DBA Scheduling Priority): 0
• T-CONT; xPON Weight (DBA Scheduling weight): 0
• Queue Scheduling Policy; {WRR | Strict Priority | Hybrid}: Hybrid
Upstream GEM Port configuration and scheduling attributes:
• GEM Ports (Queues) per Service: 4 14
 AT&T HSIA Upstream GEM Port Configuration
• GEM Port 1 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (00000101), PBits 0 and 2
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: WRR
iv. GEM Port (Queue) Priority: 0
v. GEM Port (Queue) Weight: 25%
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
• GEM Port 2 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (00011010), PBits 1, 3 and 4
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: WRR
iv. GEM Port (Queue) Priority: 1
v. GEM Port (Queue) Weight: 75%
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
• GEM Port 3 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (00100000), PBit 5
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: Strict Priority
iv. GEM Port (Queue) Priority: 2
v. GEM Port (Queue) Weight: 0
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
• GEM Port 4 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (11000000), PBits 6 and 7
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: Strict Priority
iv. GEM Port (Queue) Priority: 3
v. GEM Port (Queue) Weight: 0 15
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
 AT&T HSIA Downstream Scheduler Configuration

• Priority (Scheduling Priority) : 0

• Weight (Scheduling weight) : 0
• Queue Scheduling Policy; {WRR | Strict Priority | Hybrid}: Hybrid

16
 AT&T HSIA Downstream GEM Port Configuration
• GEM Port 1 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (00000101), PBits 0 and 2
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: WRR
iv. GEM Port (Queue) Priority: 0
v. GEM Port (Queue) Weight: 10%
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
• GEM Port 2 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (00011010), PBits 1, 3 and 4
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: WRR
iv. GEM Port (Queue) Priority: 1
v. GEM Port (Queue) Weight: 90%
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
• GEM Port 3 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (00100000), PBit 5
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: Strict Priority
iv. GEM Port (Queue) Priority: 2
v. GEM Port (Queue) Weight: 0
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
• GEM Port 4 Attributes:
i. P-Bit Map to GEM Port: PBit Mask (11000000), PBits 6 and 7
ii. AES Encryption: True
iii. GEM Port Scheduling Policy; {WRR | Strict Priority}: Strict Priority
iv. GEM Port (Queue) Priority: 3
v. GEM Port (Queue) Weight: 0
vi. Queue Discard Policy; {Tail-drop | WTail-drop | RED | WRED}: Tail-drop
17
 AT&T HSIA Service: Mapping to Service profile
‘4QueueHybridProfileMap1’ Using OpenFlow Table ID
• The ‘4QueueHybridProfileMap1’ Service Profile is assigned the Table ID value
of 64, and assume that the Service Flow associated with Table ID 64 is a HSIA
and the Customer C-TAG to be used is 122, with an S-Tag of 2.
• The Customer has signed up for a 1G Upstream and 1G Downstream Service.
• OpenFlow will create a Meter in the Meter Table for the Customer HSIA
Downstream Service Flow: Single Meter Band:
• Band Type : NA(No actions on the Packet when Band Exceeded) (Best Effort Service)
• Rate: 1Gb/s (EIR)
• Burst: 384 Kbits (EBS)

18
 AT&T HSIA Service: Mapping to Service profile
‘4QueueHybridProfileMap1’ Using OpenFlow Table ID
• The Customer has signed up for a 1G Upstream and 1G Downstream
Service.
• OpenFlow will create a Meter in the Meter Table for the Customer
HSIA Upstream Service Flow: Single Meter Band:
• Meter Band 1:
• Rate: 1Gb/s (EIR)
• Burst: 384 Kbits (EBS)

19
 Flow Decomposition Issue
When ONOS Configures an Upstream or Downstream Flow the Flow is Split into Two
Parts:
• Table 0 ;Ingress/Egress Port and Match Action Rule and Transition to Table 1
• Table 1; Ingress/Egress Port Match Action Rules and Transition to Tech Profile Table with Meter Band

The Flow Decomposer in the vCore sends each Table Data to either the ONU or OLT
Adapter:
• Upstream ONU gets Table 0 (No Tech Profile or Meter Ref), OLT gets Table 1
• Downstream OLT get Table 0 (No Tech Profile or Meter Ref), ONU gets Table 1

20
Transition from Table ID Reference to Tech. Profile ID to
Using Metadata
OpenFlow Customer 2/122 Downstream Messages:
Table 64 (The Service Profile Reference) contains a Default Rule of Match-All, No Action.

ADDED, bytes=0, packets=0, table=0, priority=1000, selector=[IN_PORT:129, METADATA:15, VLAN_VID:2],

treatment=[immediate=[VLAN_POP], transition=TABLE:1]

ADDED, bytes=0, packets=0, table=1, priority=1000, selector=[IN_PORT:129, VLAN_VID:122], treatment=[immediate=[VLAN_ID:0],

deferred=[OUTPUT:21], meter=ID, transition=TABLE:64]

OpenFlow Customer 2/122 Upstream Messages:

ADDED, bytes=0, packets=0, table=0, priority=1000, selector=[IN_PORT:21, VLAN_VID:0], treatment=[immediate=[VLAN_ID:122], transition=TABLE:1]

ADDED, bytes=0, packets=0, table=1, priority=1000, selector=[IN_PORT:21, VLAN_VID:122], treatment=[immediate=[VLAN_PUSH:vlan, VLAN_ID:2],

deferred=[OUTPUT:129], meter=ID, transition=TABLE:64]

21
 Transition from Table ID Reference to Tech. Profile ID to
Using Metadata
Ingress Packet at OLT NNI (In Port = 65536), STAG = 4, CTAG = 2, Match on Tags 4, 2 POP outer Tag(4), modify Inner Tag to be 0(Priority Tagged; 2->0); Apply Technology Profile Reference = 1,
and Downstream Meter Reference = 2, Egress Port =30736, Downstream Metadata to write : CTAG = 2, TPID = 1, Egress Port = 30736; 0x0002000100007810 (02/01/30736)

Ingress Packet at ONU UNI (In Port = 30736), Priority Tagged, QTAG = 0, Match on Tag 0, Change Outer Tag to be 2 (CTAG; 0->2), PUSH STAG 4; Apply Technology Profile Reference = 1,
and Upstream Meter Reference = 1, Egress Port =65536 Upstream Metadata to write : STAG = 4, TPID = 1, Egress Port = 65536; 0x0004000100010000 (04/01/65536)

Metadata 8 bytes:
Most Significant 2 Bytes = Inner VLAN
Next 2 Bytes = Tech Profile ID(TPID)
Least Significant 4 Bytes = Port ID

Downstream Flow Example:

-------------------------

(OLT Flow) id=ac0000d0fc7486, state=ADDED, bytes=0, packets=0, duration=4, liveType=UNKNOWN, priority=1000, tableId=0, appId=org.opencord.olt, payLoad=null, selector=[IN_PORT:65536, VLAN_VID:4],
treatment=DefaultTrafficTreatment{immediate=[VLAN_POP], deferred=[], write metadata=METADATA:02/01/30736}, transition=TABLE:1, meter=[METER:2], cleared=false, StatTrigger=null,

(ONT Flow) id=ac00001801d6d1, state=ADDED, bytes=0, packets=0, duration=4, liveType=UNKNOWN, priority=1000, tableId=1, appId=org.opencord.olt, payLoad=null, selector=[IN_PORT:65536, VLAN_VID:2],
treatment=DefaultTrafficTreatment{immediate=[VLAN_ID:0, OUTPUT:30736], write metadata=METADATA:0/01/0, transition=None, meter=[METER:2], cleared=false, StatTrigger=null}

Upstream Flow Example:

-------------------------

(ONT Flow) id=ac000000f780f6, state=ADDED, bytes=0, packets=0, duration=4, liveType=UNKNOWN, priority=1000, tableId=0, appId=org.opencord.olt, payLoad=null, selector=[IN_PORT:30736, VLAN_VID:0],
treatment=DefaultTrafficTreatment{immediate=[VLAN_ID:2], deferred=[], write metadata=METADATA:04/01/65536, transition=TABLE:1, meter=[METER:1], cleared=false, StatTrigger=null}

(OLT Flow) id=ac0000c9fd17bf, state=ADDED, bytes=0, packets=0, duration=4, liveType=UNKNOWN, priority=1000, tableId=1, appId=org.opencord.olt, payLoad=null, selector=[IN_PORT: 30736 , VLAN_VID:2],
treatment=DefaultTrafficTreatment{immediate=[VLAN_PUSH:vlan, VLAN_ID:4, OUTPUT: 65536 ], write metadata=METADATA:0/01/0, transition=None, meter=[METER:1], cleared=false, StatTrigger=null}
22
Traffic Management:
: BAL 2.6 Edgecore
 BAL 2.6 Downstream Queue Scheduling Limitation -
Desired
FlowQueues Flow UNI ONU PON
Scheduler Scheduler Scheduler Scheduler
P 6.7 TM_Q P0
ONU#1 P 5 TM_Q
P1
P 4,3,1 TM_Q

Flows P 2,0 TM_Q

TM-Sched
P2

P3

4 TM_Queues
NNI
: PON TM
: Sched PON#
1

: P0

: P1
P 6,7 TM_Q
P 5 TM_Q
ONU#128 P 4,3,1 TM_Q
TM-Sched
P2

Flows P 2,0 TM_Q P3

4 TM_Queues
 BAL 2.6 Downstream Queue Scheduling Limitation -
Actual
ONU
FlowQueues Flow UNI PON
Scheduler
Scheduler Scheduler P0 Scheduler
P 6.7 TM_Q
ONU#1 P 5 TM_Q P1
P 4,3,1 TM_Q
P 2,0 TM_Q
Flows TM-Sched
P2

P3

4 TM_Queues
NNI
: PON TM

: Sched PON#1

P0
:
P1
:
P 6,7 TM_Q
P 5 TM_Q TM-Sched
ONU#128 P 4,3,1 TM_Q
P2

P 2,0 TM_Q P3
Flows

4 TM_Queues
 Technology Profiles; AT&T
: Service Model-OLT ;Upstream -
Desired – BAL 2.6
NNI FlowQueues Flow Spec TCONT(DBA)
Scheduler

P0

P1 TM _SCHED(DBA) ONU#1
GEM Port ID
o_pbits=7,6

P 7,6 TM _Q GEM Port ID

NNI TM o_pbits=5 :
NNI Sched GEM Port ID
o_pbits=4,3,1
: PON#1
P 5 TM _Q

GEM Port ID
GEM Port ID
o_pbits=7,6
:
o_pbits=2,0
P2
S GEM Port ID :
o_pbits=5
P 4,3,1 TM _Q

GEM Port ID
o_pbits=4,3,1
TM _SCHED(DBA) ONU#128
GEM Port ID
P 2,0 TM _Q o_pbits=2,0

P3

4 TM_Queues NNI
 :
Technology Profiles; AT&T Service Model-OLT ;Upstream – Actual BAL 2.6
Flow Spec
NNI FlowQueues (More complex until TCONT(DBA)
PBIT Map Supported) Scheduler
P0 pbits=0
P 0 TM _Q
TM _SCHED(DBA)-Service 1
pbits=1

P1 P 1 TM _Q TM _SCHED(DBA )-Service 2
pbits=2 ONU#1
pbits=3 Services
P2 P 2 TM _Q TM _SCHED(DBA )-Service 3

TM _SCHED(DBA )-Service 4

P 3 TM _Q
P3 pbits=4

NNI TM
pbits=5
:
pbits=6
NNI Sched pbits=7
: PON#1

:
pbits=0

P4 :
P 4 TM _Q
pbits=1

pbits2 TM _SCHED(DBA )-Service 1

S
P5 P 5 TM _Q pbits3

TM _SCHED(DBA)-Service 2
pbits=4
ONU#128
P6
P 6 TM _Q pbits=5
TM _SCHED(DBA )-Service 3
Services
pbits=6

TM _SCHED(DBA )-Service 4
P7 P 7 TM _Q
pbits=7

8 TM_Queues NNI