-
Type: Story
-
Status: Resolved (View Workflow)
-
Priority: High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.0
-
Component/s: ofagent-py
-
Labels:
-
Story Points:8
-
Epic Link:
-
Sprint:VOLTHA 2.0 Sprint 5, VOLTHA 2.0 Sprint 6, VOLTHA 2.0 Sprint 7, VOLTHA 2.0 Sprint 8, VOLTHA 2.0 Sprint 9, VOLTHA 2.0 Sprint 10, VOLTHA 2.0 Sprint 11, VOLTHA 2.0 Sprint 12, VOLTHA 2.0 Sprint 13, VOLTHA 2.0 Sprint 14
Once an ONU is discovered and a Logical Port ID created for a UNI Port and reported as a ‘Port Status’ – with a Reason of ‘OFPPR_ADD’ – Port Add Message. The Port Add Message contains (currently) Logical Port ID (32 bits), MAC address of Port, Serial Number of ONU. These attributes are used to look up the SADIS record of the Subscriber. At this point the Technology Profile for the Subscriber can be known (this may need some consolidation of the Subscriber Records) and ONOS will configure the Authentication stage match/action rules for the Subscriber and also add the Technology Profile/Bandwidth Profile information to use as the final Flow ID.Note: Registration ID will be also added for ONU authentication.
Once Authentication is successfully completed the actual Subscriber Flow Rules are added and since they reference the same Technology Profile/Bandwidth Profile the same TCONT and GEM ports are used. The Technology Profile 'Instance Control' should indicate that either the 'Data' Service is 'Single Instance per ONU' or 'Single Instance per UNI Port' so that subsequent Service flows referencing the same Tech. Profile per UNI (or ONU) use the same TCONT/GEMs which will already have been allocated by the Authentication path referencing the Same Tech. Profile.
- blocks
-
VOL-731 Technology Profiles provide a mechanism for defining Technology specific information required above and beyond OpenFlow programming in support of Subscriber Service creation.
- Resolved