Page Comparison

Expand

title	Table of Contents

Table of Contents

Model Overview

Image Modified

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

Model Design

Image Removed

Gliffy

size	1200
name	BBS - ModelOverview
pagePin	10

Model Design

16

Representation in SDC

Image Added

Resource Representations

BNG

Modeled Resource	SDC Representation	A&AI object	TOSCA file
ONT NNI	Connection Point	cp	ontNni.yaml & ontNni.json (for import)
PON UNI	Connection Point	cp	ponUni.yaml & ponUni.json (for import)
OLT NNI	Connection Point	cp	oltNni.yaml & oltNni.json (for import)	BNG UNI	N/A	cp
ODN Connection	VNF Virtual Linkl3-network ??	Transport Connection	N/Al3-network ??
Access Connectivity	Virtual Function Component	generic-vnf	accessConnectivity.yaml
Internet Profile	Virtual Function Component	generic-vnf	internetProfile.yaml
N/A	vnfc	CPE (PNF)	PNFVirtual Function Component	pnf	cpePnf.yaml

Composition of services

ONAP AwarenessSDNC ( Edge RFSCPE PNFNNI
Access Connectivity VFCNNI

Service	Composed Of
HSIA	N/A
HSIA Internet	Internet Profile VFC
HSIA Access	CFS (BBS E2E Service)	CPE VF* - CPE VFC ONT-	NNI CP ODN Connection Vnf Virtual Link PON-UNI CP	Access Connectivity VF - Access Connectivity VFC OLT-	NNI CP
HSIA CFS	HSIA Internet Service HSIA Access Service (with a SDC workaround to allow nested services)

Open Issues

We cannot have one VNF composed of a PNF. So the HSIA Access must be a service and not a VNF. Victor will explain how we can nest one service inside other in SDC by utilizing a known workaround.
We need to discuss if the l3-network A&AI object is the proper way of representing SDC Virtual links (ODN Connection/Transport Connection) for our use case.
We need to clarify the steps on how to find the proper Transport Connection to connect the OLT-NNI Connection Point to. Not clear.

Representation in A&AI

Image Removed

Model Realization Example

Gliffy

name	ModelingOLTport
pagePin	5

Gliffy

name	topologyAbstraction
pagePin	10

Model Parameter Life-cycle

Table on information model 'storage' and discovery-inventory analysis for BBS use case parameters

BBS Parameter Table

Internet Profile VF
- Internet Profile VFC

(*) with workaround to model PNF in SDC

Representation in A&AI

Gliffy
name BBS in AAI
pagePin 3

Expand

title	Representation in AAI for next releases R4+

Image Added

Model Parameter Life-cycle

Table on information model 'storage' and discovery-inventory analysis for BBS use case parameters

BBS Parameter Table

Input (Just added after Edge/

ONAP Awareness	SDNC (Access Discovery)	SDC (Service Creation from Portal)	DCAE Registration PNF	SDN-C (Access Service)	DCAE CPE Auth	A&AI
Service (HSIA)
RG MAC Add				Input							Input
Service Type		Input		Input				Input				Input
Upstream Speed				Input							Input
Downstream Speed				Input							Input
Access Remote ID				Input (Optional)	Input			Input (used to find the CFS associated with PNF)	Input
Orch Status							Derived - Obtained from CFS associated with PNF in PNF Registration	Derived - Obtained from CFS associated w PNF and MAC Address	Input
HSIA Access
CPE/ONT PNF
PNF Name			Input (CorrelationID)	SourceName		SourceName	Input
MAC Address						Input			Input	Input
Manufacturer				Onboarded CSAR Artifact	Input				Input
Serial Number					Input			Input
Model			Input						Input			Input
Type				Onboarded CSAR Artifact	Input					Input
SW Version					Input (Optional)			Input (Optional)	Input
Attachment Point (new field)			Input			Input
CPE Authentication State					Input (Used to derive the CFS orchestration status)
ONT NNI (PORT) (Future?)								Input from response when access connectivity is created			Input
ODN Virtual Link (future- reuse SDC VL?)				Link					Input from response when access connectivity is created			Input
Access Connectivity
Service Type				Input (from CFS)
Upstream Speed				Input (from CFS)
Downstream Speed				Input (from CFS)
PON UNI
CVLAN				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		Derived (Attachment Point)			Input
OLT PON Slot	Input		Derived (Attachment Point)			Input
OLT PON Port	Input		Derived (Attachment Point)			Input
OLT NNI
SVLAN	Input	Input (Optional)	Input	Input when access connectivity is created or CFS if not in DCAE Reg		Input
OLT Name	Input					Input
OLT NNI Slot	Input					Input
OLT NNI Port	Input					Input
HSIA Edge
Transport Connection	Input

Expand

title	BBS Parameter Table for next releases R4+

BBS Parameter Table

TOSCA Models

Code Block

language	yml
firstline	1
title	TOSCA model for HSIA Access RFS
linenumbers	true
collapse	true

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:

ONAP Awareness	SDNC (Access Discovery)

BNG UNIInput

Input

SDN-C (Edge Discovery)	SDC (Service Creation from Portal)	DCAE Registration PNF	SDN-C (Access Service)	DCAE CPE Auth	A&AI
Service (HSIA)
RG MAC Add			Input				Input
Service Type			Input				Input
Upstream Speed			Input				Input
Downstream Speed			Input				Input
Remote ID			Input (Optional)	Input		Input (used to find the CFS associated with PNF)	Input
Orch Status					Derived - Obtained from CFS associated with PNF in PNF Registration	Derived - Obtained from CFS associated w PNF and MAC Address	Input
HSIA Access
CPE/ONT PNF
PNF Name			Input (CorrelationID)	SourceName		SourceName	Input
MAC Address				Input		Input	Input
Manufacturer			Onboarded CSAR Artifact	Input			Input
Serial Number				Input			Input
Model				Input			Input
Type			Onboarded CSAR Artifact	Input			Input
SW Version				Input (Optional)		Input (Optional)	Input
Attachment Point (new field)				Input			Input
CPE Authentication State						Input (Used to derive the CFS orchestration status)
ONT NNI (PORT)					Input from response when access connectivity is created		Input
ODN Virtual Link					Input from response when access connectivity is created		Input
Access Connectivity
Service Type					Input (from CFS)
Upstream Speed					Input (from CFS)
Downstream Speed					Input (from CFS)
PON UNI
CVLAN			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			Derived (Attachment Point)			Input
OLT PON Slot	Input			Derived (Attachment Point)			Input
OLT PON Port	Input			Derived (Attachment Point)			Input
OLT NNI
SVLAN	Input		Input (Optional)	Input	Input when access connectivity is created or CFS if not in DCAE Reg		Input
OLT Name	Input						Input
OLT NNI Slot	Input						Input
OLT NNI Port	Input						Input
HSIA Edge
Transport Connection		Input					Input (Just added after Edge/ Access Discovery)
BNG UNI		Input					Input

Service-instance-related information

See AAI-BBS Proposals for Dublin Release#BBSProposalsforDublinRelease-Item6.Specificdecisionsmadeforeachattribute

BBS Properties Per HSIA CFS Service Instance	Input Source	ONAP Components that must fetch the value from A&AI	Does it really need A&AI storage?	A&AI Metaname (for Metadata)
RG MAC Address	Service Order via Ext API It also comes in the CPE Authentication Event	bbs-event-processor DCAE microservice (it fetches existing value from A&AI to compare it with the new value coming from PNF CPE authentication event in order to deduce if there is any mismatch)	Yes, as metadata of CFS service instance	rgw-mac-address
Correlation ID (PNF-name)	Service Order via Ext API It also comes in the sourceName of the PNF registration event's commonEventHeader		Yes, as property of PNF object
Service Type	Service Order via Ext API	SO / bbs-apex-policy (during Access Connectivity and Internet Profile VFCs creation & update)	Yes, as metadata of CFS service instance	service-type
Access ID	PNF registration event	SDN-C or SO? / bbs-apex-policy (during Internet Profile VFC creation & update)	Yes, as metadata of CFS service instance	remote-id
Upstream Speed	Service Order via Ext API	SDN-C or SO? / bbs-apex-policy (during Internet Profile VFC creation & update)	Yes, as metadata of CFS service instance	up-speed
Downstream Speed	Service Order via Ext API	SDN-C or SO? / bbs-apex-policy (during Internet Profile VFC creation & update)	Yes, as metadata of CFS service instance	down-speed
OLT Name	PNF registration event (extracted from attachment point)
OLT PON port	PNF registration event (extracted from attachment point)
OLT PON slot	PNF registration event (extracted from attachment point)
CVLAN	PNF registration event Service Order via Ext API [optional - if not provided by Access SDN M&C]	SDN-C or SO? / bbs-apex-policy (during Internet Profile VFC creation & update)	Yes, as metadata of CFS service instance	cvlan
SVLAN	PNF registration event Service Order via Ext API [optional - if not provided by Access SDN M&C]	SDN-C or SO? / bbs-apex-policy (during Internet Profile VFC creation & update)	Yes, as metadata of CFS service instance	svlan
Expected ONT ID	Service Order via Ext API [optional]	SDN-C or SO? (for Access Connectivity VFC creation)	Yes, as metadata of CFS service instance	expected-ont-id
CPE Manufacturer	PNF registration event		Yes, as property of PNF object	Not Applicable
CPE Model	PNF registration event		Yes, as property of PNF object	Not Applicable
CPE Equipment Type	PNF registration event		Yes, as property of PNF object	Not Applicable
CPE Serial Number	PNF registration event		Yes, as property of PNF object	Not Applicable
CPE SW Version	PNF registration event (also present in CPE Authentication Event)		Yes, as property of PNF object	Not Applicable
Attachment Point (Not a real BBS modeling property, since its constituent parts are captured in other model properties)	PNF registration event	bbs-event-processor DCAE microservice (it fetches existing value from A&AI to compare it with the new value coming from PNF re-registration event in order to deduce if it is a true relocation)	Yes, as value of link-name property of a logical-link bridged to the PNF object	Not Applicable
ONT NNI Port	CPE PNF onboarding in SDC
OLT NNI Slot	PNF registration event
OLT NNI Port	PNF registration event

TOSCA Models

Code Block

language	yml
title	HSIA Access RFS : CPE
linenumbers	true
collapse	true

tosca_definitions_version: tosca_simple_yaml_1_0_0
node_types: 
  org.openecomp.resource.vfc.OntPnf: #we cannot use the namespace like "tosca.nfv.nodes" cause SDC's restriction
    derived_from: org.openecomp.resource.abstract.nodes.PNF
    properties:
      cpe_id:
        type: tranportLinkstring
    # Internet Profile VNF required: true
InternetProfile:     type: org.onap.bbs.InternetProfileNode

Code Block

language	yml
firstline	1
title	TOSCA model for HSIA Edge RFS
linenumbers	true
collapse	true

Info

HSIA Access RFS Proposal from Victor.

Pnf derived from existing pnf node type in SDC: org.openecomp.resource.abstract.nodes.PNF
UNI/NNI derived from tosca.nodes.nfv.vduCp
Connectivity will reuse tosca.nodes.nfv.vduVirtualLink

Code Block

language	yml
title	HSIA Access RFS : CPE
linenumbers	true
collapse	true

tosca_definitions_version: tosca_simple_yaml_1_0_0
node_types: 
  tosca.nodes.nfv.Cpepnf_name:
        type: string
        required: true
      mac_addr:
        type: string
        required: true
      manufacturer:
     derived_from: org.openecomp.resource.abstract.nodes.PNF   type: string
        propertiesrequired: true
      idserial_num:
        type: string
        required: false <--true
to be discussed       mac_addressmodel:
        type: string
        required: true
      manufacturerattachment_point:
        type: string
        required: true
      is_pnf: # temporary parameter
        modeltype: boolean
       type required: stringtrue
        requireddefault: falsetrue
#      serialont_number:
type: reuse nf_type in Generic_PNF
#        type: string
#        required: true
#      sw ont_sw_version: reuse software_versions in Generic_PNF
#        type: string
#        required: falsetrue
    capabilities:
        virtual_binding:
          type: tosca.capabilities.nfv.VirtualBindable
          occurrences:
          - 1
          - UNBOUNDED

CpePnf.yml

Code Block

language	yml
title	HSIA Access RFS : OLTAccessConnectivity
linenumbers	true
collapse	true

tosca_definitions_version: tosca_simple_yaml_1_0_0
node_types: 
  toscaorg.nodesopenecomp.nfv.AccessConnection: <-- to de discussed
 resource.vfc.accessConnectivity: 
    derived_from: tosca.nodes.rootRoot
    description: olt
    properties:
      service_type:
        type: string
        required: true
      upstream_speed:
        type: string
        required: true
      downstream_speed:
        type: string
        required: true
    capabilities:
        virtual_binding:
          type: tosca.capabilities.nfv.VirtualBindable
          occurrences:
          - 1
          - UNBOUNDED

access_connectivity.yml

Code Block

language	yml
title	HSIA Access RFS : ONTNNIOntNni
linenumbers	true
collapse	true

tosca_definitions_version: tosca_simple_yaml_1_0_0
node_types: 
  toscaorg.openecomp.nodesresource.nfvcp.OntNni: 
    derived_from: tosca.nodes.nfv.VduCp
    properties:
      ont_port:
        type: string
        required: true
    requirements:
        - virtual_link:
            capability: tosca.capabilities.nfv.VirtualLinkable
            relationship: tosca.relationships.nfv.VirtualLinksTo
            node: tosca.nodes.nfv.VnfVirtualLink
        - virtual_binding:
            capability: tosca.capabilities.nfv.VirtualBindable
            relationship: tosca.relationships.nfv.VirtualBindsTo
            node: toscaorg.openecomp.nodesresource.nfvvfc.OntPnf

OntNni.rar

Code Block

language	yml
title	HSIA Access RFS : PonUni
linenumbers	true
collapse	true

tosca_definitions_version: tosca_simple_yaml_1_0_0
node_types: 
  toscaorg.openecomp.nodesresource.nfvcp.PonUni: 
    derived_from: tosca.nodes.nfv.VduCp
    properties:
      expected_ont_id:
        type: string
        required: true
      cvlan_id:
        type: string
        required: true
      olt_name:
        type: string
        required: true
      olt_pon_port:
        type: string
        required: true
      olt_pon_slot:
        type: string
        required: true
    requirements:
        - virtual_link:
            capability: tosca.capabilities.nfv.VirtualLinkable
            relationship: tosca.relationships.nfv.VirtualLinksTo
            node: tosca.nodes.nfv.VnfVirtualLink
        - virtual_binding:
            capability: tosca.capabilities.nfv.VirtualBindable
            relationship: tosca.relationships.nfv.VirtualBindsTo
            node: tosca.nodes.nfv.OltPnf
org.openecomp.resource.vfc.accessConnectivity

PonUni.rar

HSIA Edge RFS proposal from Victor.

CP derived from tosca.nodes.nfv.vduCp

Connectivity will reuse tosca.nodes.nfv.VnfVirtualLink

To be edited, the requirements for virutal_binding depends on how to model the BNG itself.

Code Block

language	yml
title	HSIA Access RFS : OLTNNI
linenumbers	true
collapse	true

tosca_definitions_version: tosca_simple_yaml_1_0_0
node_types: 
  toscaorg.openecomp.nodesresource.nfvcp.OltNni: 
    derived_from: tosca.nodes.nfv.VduCp
    properties:
      olt_name:
        type: string
        required: true
      olt_nni_port:
        type: string
        required: true
      olt_nni_slot:
        type: string
        required: true
      svlan:
        type: string
        required: true        
    requirements:
        - virtual_link:
            capability: tosca.capabilities.nfv.VirtualLinkable
            relationship: tosca.relationships.nfv.VirtualLinksTo
            node: tosca.nodes.nfv.VnfVirtualLink
        - virtual_binding:
            capability: tosca.capabilities.nfv.VirtualBindable
            relationship: tosca.relationships.nfv.VirtualBindsTo
            node: toscaorg.openecomp.nodesresource.nfvvfc.OltPnfaccessConnectivity

Info

OltNni.rar

Code Block

language	yml
title	HISA Edge HSIA Access RFS : BngUniInternetProfile
linenumbers	true
collapse	true

tosca_definitions_version: tosca_simple_yaml_1_0_0
node_types: 
  toscaorg.openecomp.nodesresource.nfvvfc.BngUniInternetProfile: 
    derived_from: tosca.nodes.nfv.VduCpRoot
    properties:
      svlanrg_mac_addr:
        type: string
        required: true
      bngservice_uni_porttype:
        type: string
        required: true
      bngupstream_uni_slotspeed:
        type: string
        required: true
      
    requirementsdownstream_speed:
        - virtual_linktype: string
        required: true
 capability: tosca.capabilities.nfv.VirtualLinkable    remote_id:
        relationshiptype: tosca.relationships.nfv.VirtualLinksTostring
        required: true
  node: tosca.nodes.nfv.VnfVirtualLink
 capabilities:
       - virtual_binding:
            capabilitytype: tosca.capabilities.nfv.VirtualBindable
            relationship: tosca.relationships.nfv.VirtualBindsTooccurrences:
          -  node: tosca.nodes.nfv.BNG //To Be Edited, depends on how to model BNG itself


1
          - UNBOUNDED

InternetProfile.yaml

Versions Compared

Old Version 78

New Version Current

Key

Model Overview

Image Modified

Model Design

Model Design

Representation in SDC

Resource Representations

Composition of services

Open Issues

Representation in A&AI

Model Realization Example

Model Parameter Life-cycle

Representation in A&AI

Gliffy
name BBS in AAI
pagePin 3

Model Parameter Life-cycle

TOSCA Models

Service-instance-related information

TOSCA Models

Page Comparison

Versions Compared

Old Version 78

New Version Current

Key

Model Overview

Image Modified

Model Design

Model Design

Representation in SDC

Resource Representations

Composition of services

Open Issues

Representation in A&AI

Model Realization Example

Model Parameter Life-cycle

Representation in A&AI

GliffynameBBS in AAIpagePin3

Model Parameter Life-cycle

TOSCA Models

Service-instance-related information

TOSCA Models

Gliffy
name BBS in AAI
pagePin 3