Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


ONAP AwarenessSDNC (Access Discovery)SDN-C (Edge Discovery)SDC (Service Creation from Portal)DCAE Registration PNFSDN-C (Access Service)DCAE AuthenticA&AI

 Service (HSIA)  Input   Input   
 RG MAC Add  Input   Input   
 Service Type  Input   Input   
 Upstream Speed  Input     Input   
 Downstream Speed  Input    Input   
 Access ID  Input (Optional)  Input   Input  
 Status      Input Input  
          
 HSIA Access         
 CPE/ONT PNF       Input  
 CPE ID  Onboarded CSAR Artifact SourceName   Input  
 MAC Address    Input   Input  
 Manufacturer   Onboarded CSAR ArtifactInput    Input  
 Serial Number   Onboarded CSAR Artifact Input   Input  
 Model   Onboarded CSAR Artifact Input   Input  
 Type   Onboarded CSAR Artifact Input   Input  
 SW Version    Input   Input  
 ONT NNI (PORT) (Future?)     Input when PNF register/ re-register  Input  
 ODN Virtual Link (future- reuse SDC VL?)     Input when access connectivity is created  Input  
 Access Connectivity         
 PON UNI         
 CVLAN (Victor check)   Input (Optional) Input Input when access connectivity is created or CFS if not in DCAE Reg  Input  
 Expected ONT ID   Input (Optional)  Input (from CFS)  Input  

OLT Name

Input

Input

Input

OLT PON SlotInput

Input

Input

OLT PON PortInput

Input

Input

Service Type



Input (from CFS)



Upstream Speed



Input (from CFS)



Downstream Speed



Input (from CFS)



OLT NNIInput




Input

SVLAN (Victor?)Input
Input (Optional)Input Input when access connectivity is created or CFS if not in DCAE Reg
Input

OLT NameInput




Input

OLT NNI SlotInput




Input

OLT NNI PortInput







HSIA Edge








Transport Connection
Input?



Input (Just added after Edge/ Access Discovery)

BNG UNI
Input



Input





















































BBS use case aims at using ONAP for the design, creation and activation of the High Speed Internet Access CFS.

...

ONAP Table on information model 'storage' and discovery-inventory analysis

...

TOSCA models


Code Block
languageyml
firstline1
titleTOSCA model for HSIA Access RFS
linenumberstrue
collapsetrue
tosca_definitions_version: tosca_simple_yaml_1_0
description: Template for HSIA Access RFS

capability_types:
  org.onap.bbs.capabilities.ONTCapability:
    derived_from: onap.capabilities.PNFDevice
    description: Declaration of being an ONT PNF Device

node_types:

  # New ONT PNF Node Types
  org.onap.bbs.OntDeviceNode:
    derived_from: onap.nodes.PNFDevice
    description: A PNF ONT device
 
  org.onap.bbs.OntNode:
    derived_from: onap.nodes.Function
    description: An ONT Resource
    properties:
      OntID:
        type: string
        description: ID of ONT
      rgMacAddress:
        type: string
        description: RG MAC address for which Internet is offered
 	  OntType:
        type: string
        description: Type of ONT
        required: false
      OntSwVersion:
        type: string
        description: Software version of ONT
        required: false

  # New Type for HSIA Access Fevice
  org.onap.bbs.AccessConnectivityNode:
    derived_from: onap.nodes.Function
    metadata:
      type: VNF
    properties:
 	  serviceType:
        type: string
        description: Type of HSIA service offered to customer
      upstreamSpeed:
        type: integer
        description: Speed for upstream traffic
      downstreamSpeed:
        type: integer
        description: Speed for downstream traffic
    capabilities:
      PON_UNI_Binding:
        type: onap.capabilities.Bindable
      OLT_NNI_Binding:
        type: onap.capabilities.Bindable 

  # New Types for HSIA Acces Connection Points
  org.onap.bbs.PonUniConnectionPoint:
    derived_from: onap.nodes.CP
    properties:
      CVLAN:
        type: string
        description: CVLAN of customer of HSIA service
        required: false
      ExpectedOntID:
        type: string
        description: Expected ONT ID (in case of pre-provisioned ONTs)
        required: false
    attributes:
      oltName:
        type: string 
        description: Name of OLT hosting this CP
      oltPonSlot:
        type: integer
        description: OLT PON Slot number hosting this CP
      oltPonPort:
        type: integer
        description: OLT PON Port number hosting this CP

  org.onap.bbs.OltNniConnectionPoint:
    derived_from: onap.nodes.CP
    properties:
      SVLAN:
        type: string
        description: SVLAN of HSIA service
        required: false
    attributes:
      oltName:
        type: string 
        description: Name of OLT hosting this CP
      oltNniSlot:
        type: integer
        description: OLT NNI Slot number hosting this CP
      oltNniPort:
        type: integer
        description: OLT NNI Port number hosting this CP

  org.onap.bbs.OntNniConnectionPoint:
    derived_from: onap.nodes.CP
    attributes:
      ontNniPort:
        type: integer
        description: ONT NNI Port number hosting this CP 

  # New Type for HSIA Internet Profile
  org.onap.bbs.InternetProfileNode:
    derived_from: onap.nodes.Function
    metadata:
      type: VNF
    properties:
      rgMacAddress:
        type: string
        description: RG MAC address for which Internet is offered
      serviceType:
        type: string
        description: Type of HSIA service offered to customer
      upstreamSpeed:
        type: integer
        description: Speed for upstream traffic
      downstreamSpeed:
        type: integer
        description: Speed for downstream traffic
    attributes:
      accessID:
        type: string
        description: Access ID assigned for this internet service

############################
# HSIA Access RFS Topology #
############################
topology_template:

  node_templates:
 
  # ONT
  OntPhysical:
    type: org.onap.bbs.OntDeviceNode
    capabilities:
      pnf_device:
        type: org.onap.bbs.capabilities.ONTCapability

  OntPNF:
    type: org.onap.bbs.OntNode
    capabilities:
      bindOntNNI:
        type: onap.capabilities.Bindable
    requirements:
      - pnf_device:
          node: OntPhysical
          capability: org.onap.bbs.capabilities.ONTCapability 
 
  # ONT Connection Point
  OntNNI:
    type: org.onap.bbs.OntNniConnectionPoint
    requirements:
      - OntBinding:
          node: OntPNF
          capability: onap.capabilities.Bindable
      - ODNConnectionLinking:
          node: ODNConnection
          capability: onap.capabilities.Linkable

  # ODN Connection between ONT PNF and Access Device VNF
  ODNConnection:
    type: onap.nodes.VL
    capabilities:
      link:
        type: onap.capabilities.Linkable

  # Access Device VNF
  AccessConnectivity:
    type: org.onap.bbs.AccessConnectivityNode
    capabilities:
      bindPonUNI:
        type: onap.capabilities.Bindable
      bindOltNNI:
        type: onap.capabilities.Bindable 

  # Access Device Connection Points
  PonUNI:
    type: org.onap.bbs.PonUniConnectionPoint
    requirements:
      - accessDeviceBinding:
          node: AccessDevice
          capability: bindPonUNI
      - ODNConnectionLinking:
          node: ODNConnection
          capability: onap.capabilities.Linkable

  OltNNI:
    type: org.onap.bbs.OltNniConnectionPoint
    requirements:
      - accessDeviceBinding:
          node: AccessDevice
          capability: bindOltNNI
      # "TransportConnectionLinking" stays unsatisfied, providing only filtering info 
      # of a VL with a property of "type=tranportLink"
      # Orchestrator must satisfy it
      - TransportConnectionLinking:
          node_filter:
            capabilities: onap.nodes.VL
            properties:
              type: tranportLink
 
  # Internet Profile VNF
  InternetProfile:
    type: org.onap.bbs.InternetProfileNode

...