Registration of 3rd Party Controller (Access & Edge SDN M&C)

Description:

  • Domain specific M&C (Access, Edge) are registered in ONAP as External Systems (3rd party controller).

Assumptions:

  • Infrastructure (OLT, Transport tunnel, BNG, AAA, DHCP) is configured and provisioned. 

BBS-Topology_Discovery

  1. Register the 3rd party Access SDN Management & Controller to ESR.
  2. ESR triggers a 3rd party Controller registration event to DMaaP.
  3. SDN-C subscribes to the event and gets an event notification.

Success Criteria:

  • The External System is registered in ONAP

HSIA Service Creation and Activation (includes ONT PnP)

Description: 

  • The Service Provider provisions Broadband Internet Access Service using ONAP. ONT registration triggers the CFS HSIA provisioning, OLT and PON port are announced with the ONT registration 

Assumptions:

  • OLT/ONT/BNG related resources already modeled in SDC and distributed in ONAP
  • ONT and CPE/RG functions are combined in a single device (PNF) that can be easily installed by the end customer
  • Optical fiber circuit to customer premises exists 
  • Infrastructure (OLT, Transport tunnel, BNG, AAA, DHCP) is configured and provisioned

BBS-HSIA Creation and Activation

  1. Customer orders HSIA service through BSS portal. BSS registers CPE info and posts the device to the customer address.
  2. BSS/OSS sends a CFS HSIA service instance creation request to ONAP External API including BSS's external ID for the new service instance, service type ID in ONAP catalog, HSIA and CPE attributes 
  3. External API triggers a service instance create in SO.
  4. SO decomposes the CFS into RFSs
  5. SO inserts the service information into A&AI and sets service instance orchestration status to 'planned'.
  6. SO subscribes to CPE (ONT) PNF registration event and waits for it
  7. Customer receives CPE device, installs it and powers it on.
  8. CPE (ONT) becomes online.
  9. OLT detects a new CPE (ONT) and initiates the ONT registration process
  10. Access SDN M&C reports the ONT registration event to PRH using a VES event message that includes additional fields, such as PON UNI (OLT attachment port) and AccessID (ID for OLT-ONT pair)
  11. PRH checks if there is an existing PNF entry in AAI for the new ONT and updates the received PNF info in AAI. The PON UNI in the Attachment Point is updated as a relationship link. Other additional information elements is not updated.
  12. PRH publishes an PNF_READY event with the VES registration additional information field that is consumed by SO via DMaaP
  13. SO continues with the provisioning of the CFS HSIA (PNF Activation Stage 5: Service Configuration)
  14. SO via SDN-C triggers the creation of the RFS Access Connectivity, which will configure the ONT and the OLT via the Access SDN M&C
  15. SO via SDN-C triggers the creation/configuration of the RFS Internet Profile (e.g. customer's speed profile)
  16. SO updates CFS HSIA info in AAI.
  17. CPE(RG) becomes online and initiates the CFS HSIA activation procedure via the CPE Authentication Notification

Success Criteria:

  • The CFS HSIA order is successfully completed. The customer gets Internet access with the requested rate, quality of service and protection scheme 

Nomadic ONT Service

Description: 

  • The Service Provider provisions Broadband Internet Access Service using ONAP. One day, the customer moves the ONT to a new location without notifying the SP. The ONT (PNF) will re-register in a new location and ONAP needs to re-provision/reconfigure the customer's broadband service.

Assumptions:

  • The CFS HSIA exists and is active before user moves to new location
  • New location can provide the same level of service as in the previous location, e.g. fiber access is available. We assume unlimited resources

BBS - Nomadic ONT

See PNF Registration and Re-registration NotificationCPE Authentication Notification

Success Criteria:

  • The CFS HSIA is automatically reconfigured after user moves and plugs ONT in a new location. The customer gets Internet access with the requested rate, quality of service and protection scheme 

Service Termination

WIP

Subscription Plan Change (stretch goal for Dublin)

Description: 

  • Service Provider ONAP provisions Broadband Internet Access Service. The customer needs higher bandwidth Broadband Internet Access Service and request a bandwidth upgrade via the customer portal, the service provider upgrades the already existing Broadband service to the new subscription plan (e.g. 1Gbps to 10Gbps)

Assumptions:

  • The CFS HSIA exists and is active before the customer requests a subscription plan change, e.g. upgrade Internet speed
  • The existing CFS HSIA is reconfigured to accommodate the customer request
  • We assume unlimited resources

BBS - Subscription Plan Change

Success Criteria:

  • The CFS HSIA is automatically reconfigured according to the requested internet access speed 

HSIA Service Assurance (not for Dublin)

Description: 

  • Service Provider ONAP provisions Broadband Internet Access Service. ONAP monitors CFS HSIA service instance KPIs and triggers closed loop policies when a predefined threshold is crossed

Assumptions:

  • -
  • No labels

12 Comments

  1. The flow for the subscription change will also need to be sent to the Access SDN M&C - there are deployments where the access network needs configured when a subscribers subscription changes for elements like Bandwidth and QoS

  2. In the creation and activation interaction - the Access SDN M&C sends an RG activation event.

    But if I read the flow correctly  the “RGactivated”  - comes after:

    1. AAA Authentication
    2. IPAM address
    3. RG is configured via TR-069

     

    So at this stage the only entities that can report a RG is activated is the ACS (successful configuration) or the RG itself

    Can’t we say an RG is activated after the AAA verifies access – we could then send it based on the AAA RG authorization event? – An authorized event would set the status active, unauthorized would set the status to something else like “Errored” or “Unauthorized”  - If we were intercepting the control packets the Access SDN M&C could do that as well but I don’t think that is the interaction scenario here…

  3. If I am not mistaken, in the normal VID service instantiation procedure, we have two ways of passing service data (which are different per service instance) as input.

    We either have to pre-load data in SDN-C and click the 'Use SDN-C preload' option so that SO can take data from SDN-C, or we have to upload a JSON file in VID while instantiating. I have never experimented with the latter.

    At least this is the procedure for VNF instantiations as taken from some community discussions.


    In the HSIA service creation flow, are we simulating the passing of service instance data in the body of the REST call originated from External API towards SO? Can you explain what is the exact mechanism here?

    Is the 'Add Service Info' interaction from SO towards A&AI how we store service instance data in A&AI (split in the various RFS resource instances)?


    1. As stated in the following link, SDN-C pre-loading is no longer required.

      SO Building blocks

      Key differences from Amsterdam/Beijing

      • Pre-loading data into SDNC is no longer required - the service inputs, or VNF/C attributes & properties can be supplied in the SO request in a structured format (JSON).
  4. David Perez Caparros can you place the source power point or whatever you use to generate the PNG diagrams in the attachments. That will allow anyone to take the source and suggest modifications - its alittle more efficient.

    1. done. I linked to the original Gliffy diagrams, so everyone should be able to edit now. I will do the same with nomadic ONT flow (working on it right now)

      1. It shows :Gliffy Macro Error, You do not have permission to view this diagram. Is it my own problem?

        1. Please try again, I used the Gliffy diagram as template instead of linking them

          1. ok,it‘s solved

  5. What is the value of accessID existence? I find it is for identifying ONT-OLT pair above .

    What i want to say is Access SDN M&C has already announced ONT SN and PON-UNI(includes OLT Name) data to ONAP, so ONAP can generate accessID by itself without passing in an additional AccessID from Access SDN M&C.

    Please correct me if i'm wrong.


    1. Hi Bryan,

      Sorry for the late reply. AccessID will be used later on for service pairing at the BNG. We can let the Access SDN M&C generate that value or do it in ONAP. I think the first option is simpler, as generating the AccessID requires extra-logic. We cannot use ONAP's uuid or invariant-uuid for that.

  6. Hey,

    A comment to HSIA Service Creation and Activation (includes ONT PnP) message flow.
    Within 5G PNF PnP case, we assumed, that a standard waiting time between the service instantiation (include a resource instance entry creation in AAI), and a reception of  a PNF registration message equals 14 days.
    I thinik, it would make sense to keep this "de-facto standard" time-out value as well in case of BBS.


    Damian