ACCESS POD:
...
OSAM GW:
For the first phase, OSAM GW is going to be stored in OSAM DB.
- id(string) identiier for OSAM GW
- Ip address(String) ip address of the OSAM GW
ACCESS POD:
Access Pod is a PNF that will be fetched from ONAP(AAI). Its relation such as subscribers and devices will be kept in OSAM DB. CorrelationId will play a key role for that purpose. Moreover, PNF location could be kept in AAI or OSAM DB.(depends on use case).
DEVICE:
Device is an abstract model definition of a physical device. A device can be an OLT or an ONT Device. It consists of the following properties:
...
Subscriber is a model object that allows us to provision customer. It will be kept in OSAM DB.
- Id(string) -property refers to ONT uniport also it is an identifier for a subscriber. Must be given
- c-tag(int) -it is used by ONT device. Must be given
- s-tag(int) -it is used by ONT device. Must be given
- techProfileId refers to technology profile id. To provision, the subscriber technology profile is required. (Technology profile details will be fetched from Access Pod.)
- upstreamBandwidthProfile refers an upstream(ONT to OLT) traffic bandwidth profile id. (Traffic bandwidth profile details will be fetched from Access Pod.)
- downstreamBandwidthProfile refers a downstream(OLT to ONT) traffic bandwidth profile id. (Traffic bandwidth profile details will be fetched from Access Pod.)
- nasPortIdrefers a radius server port.
- Subscriber must be matched with OLT. OLT match is done with ConnectionPoint model.
- Connection Point indicates a bridge between OLT-device and Subscriber's ONT. Subscriber model has ConnectionPoint model as property.
...
ConnectionPoint is a model that connects the Subscriber to OLT-Device. It will be kept in OSAM DB
- Id -property refers to a serial number of OLT device
- hardwareIdentifier -refers a mac address of OLT device
- ipAddress -indicates an IP address of OLT device
- nasId -indicates a radius server.
...