-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: Next for SEBA 2.0
-
Component/s: NEM, ONOS & Apps, VOLTHA
-
Labels:None
-
Story Points:8
-
Epic Link:
Currently SADIS-SERVER component responds to the subscriber requests. (c-tag, s-tag etc)
When SADIS wants to learn subscriber information from its remote server, it gets the subscriber information from r-cord synchronizer (from XOS). – This component must support bandwidth-profile information (PIR, CIR, AIR and burst sizes) using the bandwidth profile id and responds to the SADIS app. (to support tech profile integration) – Or, a new component can be implemented such as BandwidthProfile-Server.
1.
|
Configure the Sadis app to read Bandwidth Profiles from sadis-server |
|
To Do | Unassigned |