Introduction to the SID - POSTECH CSE DPNM …dpnm.postech.ac.kr/papers/TMW/TMW2004-LongBeach… ·...

All Rights ReservedPage No. - 1Copyright 2004 MDAPCE, MetaSolv, and

TeleManagement Forum. All Rights ReservedPage 1 Training Plus

TM Forum Training Plus at TeleManagement WorldLong Beach, USA - 11th October 2004

Introduction to the SID

John Reilly – [email protected] Strassner – [email protected]

mailto:[email protected]




Agenda9:00 – 9:10 – NGOSS and the SID9:10 – 9:30 – SID Framework9:30 – 9:40 – Mapping to eTOM 9:40 – 9:55 – SID Addenda and Model9:55 – 10:30 – SID Domain Whirlwind Tour10:30 – 11:00 – Break11:00 – 12:10 – Whirlwind Tour (cont.)12:10 – 12:30 – SID in Action12:30 – Course Ends



Housekeeping

CourtesyMobiles, Pagers, etc.

Q&ADuring Breaks, Start/End of Sessions, End of Day

FeedbackEvaluation Forms



NGOSS and the SID



Goals of the NGOSS ProgramSpecify an architecture for managing next generation communications networks to:

Reduce time to marketReduce integration taxReduce management time and costFacilitate introduction of new technologiesSupport multiple technology implementations

Must accommodate both “greenfield” and “brownfield” deployment strategies



Changing the Focus From…

BusinessLogic

Interfaces

Infrastructure

80%



Changing the Focus To…

Infra-structure

Interfaces

Business Logic80%



Why an NGOSS Lifecycle?To ensure that roles, requirements, models, implementations and deployments all contribute in a holistic manner to the solutionTo provide traceability throughout the lifetime of an NGOSS SolutionTo provide a documented means of extending and enhancing the NGOSS Knowledge Base



NGOSS Lifecycle and Methodology

Describes business operation Describes architecture and implementation of the business

Describes the conceptualdesign of the solution fromthe business perspective

Business View

Describes the conceptualdesign of the solution from

a system perspective

System View

Deployment View

Describes the actualdeployment of the solution

Implementation View

Describes the actualimplementation of the solution

Logi

cal V

iew

Tech

nolo

gyN

eutr

alTe

chno

logy

Spec

ific

Phys

ical

Vie

w

Service Providers View Service Developer View



Overview of the SID



What IS the SID?GB922 – Business View of the SID

SID Primer (Addendum 0)SID Business Contract (Addendum C)SID Business Root Entities (Addendum R)Using and Extending the SID (Addendum U)5 Domain-Specific Addenda

Addendum 1 – Common Business EntitiesAddendum 2 – CustomerAddendum 3 – ProductAddendum 4 – ServiceAddendum 5 – Resource

GB926 – System View of the SIDIDENTICAL structure to the business view, but focuses on behavior, architecture, andcomputational interactions

GB922 and GB926 cover concepts and principles for each view; content is in Addenda.



Built-In ExtensibilityDEN-ng and the SID make extensive use of software patterns for modeling

Patterns are used to capture common relationships and occurrences of physical connections and structuresPatterns make the model inherently extensible

Roles are used as a means of abstractionSuperior to specifying a particular entityExtensions to popular Role Patterns to suit

Telecommunications DomainNGOSS Approach



NGOSS Use of the SIDA Holistic Decompositional Information and Data Model, defined in UML, defining knowledge related to each NGOSS View

Enables information to be represented in a standard format using concepts and terminology defined by a particular set of stakeholdersEmphasizes extensibility through abstractionModels the Lifecycle of objects!

Conceptually, a set of related languages describing different aspects of an object



How the SID is Used in the TM Forum

As a common language and vocabulary for NGOSS Programs

Shared and reused data is defined by the SIDBusiness and system artifacts

As a means of relating different NGOSS viewpoints to each other

Enables the business, system, implementation, and runtime viewpoints to be related to each other

As a specification of how different concepts are modeled in various Catalysts

Fosters the reuse of domain information



The SID Framework



Enterprise

Strategy, Infrastructure &Product

Operations

Market/Sales, Product and Customer

Service

Resource(Application, Computing and Network)

Supplier/Partner

eTOM/SIM Level 0 Concepts/DomainsThe SID Framework

SID DomainSID DomainSID DomainSID DomainSID Domains



The SID Business Framework (GB922)

Product

Market / SalesMarket Strategy & Plan

Market Segment

Marketing Campaign

Competitor

Contact/Lead/Prospect

Sales Statistic Sales Channel

Product

Product Specification Product Offering

Strategic Product Portfolio Plan Product Performance

Product Usage Statistic

CustomerCustomer

Customer Interaction

Customer Order

Customer Statistic

Customer Problem

Customer SLA

ServiceService

Service Specification

Service Applications

Service Configuration

Service Performance

Service Usage

Resource

Supplier / PartnerSupplier/Partner

S/P Plan

S/P Interaction

S/P Product

S/P Order

S/P SLA

Enterprise Common BusinessParty

Location

Business Interaction

Policy Agreement

Applied Customer Billing Rate

Customer Bill

Customer Bill Collection

Customer Bill Inquiry

Service Strategy & Plan

Service Trouble Service Test

Resource

Resource Specification

Resource Topology

Resource Configuration

Resource Performance

Resource Usage

Resource Strategy & Plan

Resource Trouble Resource Test

S/P Problem

S/P Statistic

S/P Bill Inquiry

S/P Payment

S/P Performance S/P Bill

(Under Construction)

Product

Market / SalesMarket Strategy & Plan

Market Segment

Marketing Campaign

Competitor

Contact/Lead/Prospect

Sales Statistic Sales Channel

Product

Product Specification Product Offering

Strategic Product Portfolio Plan Product Performance

Product Usage Statistic

CustomerCustomer

Customer Interaction

Customer Order

Customer Statistic

Customer Problem

Customer SLA

ServiceService

Service Specification

Service Applications

Service Configuration

Service Performance

Service Usage

Resource

Supplier / PartnerSupplier/Partner

S/P Plan

S/P Interaction

S/P Product

S/P Order

S/P SLA

Enterprise Common BusinessParty

Location

Business Interaction

Policy Agreement

Applied Customer Billing Rate

Customer Bill

Customer Bill Collection

Customer Bill Inquiry

Service Strategy & Plan

Service Trouble Service Test

Resource

Resource Specification

Resource Topology

Resource Configuration

Resource Performance

Resource Usage

Resource Strategy & Plan

Resource Trouble Resource Test

S/P Problem

S/P Statistic

S/P Bill Inquiry

S/P Payment

S/P Performance S/P Bill

(Under Construction)



Example of the Evolving SID Framework

Resource

PhysicalResource

LogicalResource

PhysicalResource

LogicalResource

ResourceSpecification

ResourceTopology

PhysicalTopology

LogicalTopology

PhysicalConfig

LogicalConfig

ResourceConfiguration

ResourceStatistics

ResourcePerformance

ResourcePerformance

PhysicalUsage

LogicalUsage

ResourceUsage

ResourceFault

ResourceAlarm

ResourceTrouble

ResourceOutage

Resource Domain – Level 2

Network NetworkUsage

Network NetworkConfig NetworkPerformance

NetworkFault

NetworkAlarm

NetworkOutage

NetworkTopology



The SID System Framework (GB926)

Product

Market / Sales

Customer

Service

Resource

Supplier / Partner

Enterprise Common System Entities

Architecture



System View Transformation Example (1)Card

daughterCardInstallStatus : IntegerdaughterCardRequirements : IntegerslotLayout : StringslotsRequired : Integer = 1uniqueRequirementsPhysical : String

0..n

0..10..1

0..n

CardOnCard

CardcardCompatibilityResults : StringdaughterCardInstallStatus : IntegerdaughterCardOperatingStatus : IntegerdaughterCardRequirements : IntegerisConfigurablePhysically : BooleanisMotherBoard : BooleanmaxDataWidth : IntegerslotLayout : StringslotsRequired : Integer = 1uniqueRequirementsPhysical : String

getAllPhysicalPorts()

0..n

0..10..1

0..n

CardOnCard



System View Transformation Example (2)

UnknownCardSystemCardNetworkCardMemoryCard

CardcardCompatibilityResults : StringdaughterCardInstallStatus : IntegerdaughterCardOperatingStatus : IntegerdaughterCardRequirements : IntegerisConfigurablePhysically : BooleanisMotherBoard : BooleanmaxDataWidth : IntegerslotLayout : StringslotsRequired : Integer = 1uniqueRequirementsPhysical : String

getAllPhysicalPorts()

0..n0..n

0..10..1CardOnCard

CardOnCardDetails



SID is a Framework of Frameworks

Each framework is built according to a set of common generalized concepts

Roles, Patterns, Specifications

Each framework is designed to accept domain-specific “blades”

Ensures that each blade is compatible with other blades

Core FrameworkParty Model Location

ModelResource

FrameworkService

FrameworkPolicy

Framework …CFS RFSPR LR



SID – eTOM Mapping



SID/eTOM Level 0 Concepts

Enterprise

Strategy, Infrastructure &Product

Operations

Market/Sales, Product and Customer

Service

Resource (Application, Computing and Network)

Supplier/Partner



SID/eTOM Mapping



SID/eTOM Mapping



SID Addenda and Model



Inside a SID AddendumDesign Approach, Rationale, and Use Cases

Enables the model to be better understood and extended to model project-specific entities

ReferencesMore information about key concepts

Data DictionaryConsistent business definition for all classes and attributes in the modelUML ModelsContains aliases and cross-references to other industry models and concepts



GB926 System Model AddendaAimed at satisfying the needs of system designers, implementers and architectsPopulated by

Extending existing business entitiesAdding attributes not relevant at the business viewDefining methods and constraintsFurther specification of semantics (e.g., turn an association into an association class)

Defining new entities relevant for the system viewA business concept may be further refined by splitting it into multiple system classes, or defining new system entities that interact with existing business entitiesSemantics may be further refined using tagged data, constraints,and/or stereotypes



Quick Look at the SID Model



Key Points of the SID Approach



SID and Its Use in the IndustrySID is a federation of models

NOT “home-grown”Material mined from company contributions as well as DEN-ng, ITU, and IETF

SID is already being used byVendors (e.g. MetaSolv and Intelliden)Service Providers (e.g. BT and Telstra)TM Forum Catalyst Projects (e.g. SFT)OSS/J Core Business Entity ModelOMG Telecom Domain Task Force (DTF)European IST, 5th and 6th Framework Programs



TM Forum Project SupportService Framework TeamServices over IP Team (part of SPLC)Building NGOSS From Legacy and Off-the-shelf Components CatalystMulti-Technology Network ManagementIP Network Management



SID Domain and ABE “Whirlwind Tour”



Root Business EntitiesPurpose is to root the SID hierarchy

RootEntity is the top of the hierarchyEach major hierarchy has its own base class

This enables consistent characteristics and behavior to be defined to new subclasses

Defining a set of base classes in turn defines a set of characteristics and behavior for a group of similar classesThis in turn is the basis for defining new patternsthat can address the needs of NGOSS



Overview of the Root Business Entities

RootEntity

Specification

Characteristic RoleEntity

PartyIdentification

ManagementDomainPolicy

Location



Main Root Entities SemanticsEntity – Products, Resources, and Services

Always defined by a specificationSpecification – the invariant characteristics and behavior of an object

Specifications are templates, and entities are instancesCharacteristics – salient features of an entityIdentification – how an object is recognizedRole – the function(s) played by an object

Not limited to just people roles!Party – users and organizationsPolicy – uses and/or manages the behavior of objects Location – geographic areas, locations, positionManagementDomain – represents a special grouping of ManagedEntities that scopes their use and application



Example – Entity Identification

RootEntity

IdentificationEntity Specification

EntityIdentificationManagedEntity EntitySpecification

0..n1 0..n1

SpecifiesIdentificationMechanism

0..10..n 0..10..n

SpecifiesManagedEntity



Party



Party – Basic Model

Party

Organization Individual

0..n

0..10..1

HasPeopleOrOrgs

0..n



Party – Party Names

OrganizationNameIndividual IndividualName

1..n1 1..n1

IndividualINamedUsing

PartyName

Organization

1..n1 1..n1

OrganizationNamedUsing

Party0..n

0..1

0..n

0..1

HasPeopleOrOrgs



Party – Party RolesParty PartyRole

0..n1 0..n1

HasPartyRoles

ValueNetworkRoleCustomer

IntermediaryFunctionOrProcessProvider

Employee

VendorServiceProvider

ThirdPartyServiceProvider

ComplementaryProvider



Party – Contact Medium

PartyRole ContactMedium0..n0..n 0..n0..n

PartyRoleContactableVia

EmailContact FaxNumber PostalContact TelephoneNumber



Location



A Capsule View of Locations

PhysicalLocationDetails

Position Address GeographicRegionStructure

PhysicalResourceLocation0..n0..1 0..n0..1

HasLocationElements

0..n 0..n0..n 0..nPhysicalResourceLocatedAt

DEN-ng attaches semantics to Locations…

CPERouter

Colorado SpringsBldg 2

10.212.17.1

Rack 1 Room 17Slot 2

Same pattern for LogicalResource, Service, Product, etc.



Business Interaction and Agreement



Business Interaction and Agreement

Response Notification Agreement

BusinessInteractionComposite

BusinessInteraction

BusinessInteractionAtomicBusinessInteractionItem

Inquiry

0..1

0..n

0..1

0..n

HasBusinessInteractions

10..n 10..n

BusinessInteractionComprisedOf



Business Interaction Participants

BusinessInteractionRole

PartyInteractionRole

BusinessInteraction0..n0..n 0..n0..n

BusinessInteractionReferences

0..1 0..n0..1 0..n

BusinessInteractionInvolves

ResourceInteractionRole

PartyRole0..1

0..n

0..1

0..n

BIInvolvesPartyRoles

ResourceRole0..1

0..n

0..1

0..n

BIInvolvesResourceRoles

ServiceRole

ServiceInteractionRole

0..n

0..1

0..n

BIInvolvesServiceRoles

0..1



Business Interaction Items

Service

BusinessInteractionAtomic

ServiceSpecification

0..n 0..n0..n

InvolvedServiceSpecs

0..n

ResourceResourceSpecification

0..n 0..n0..n

InvolvedResourceSpecs

0..n

ProductProductOffering ProductSpecification

BusinessInteractionItem

0..n

0..n

0..n

0..n

BIItemInvolvesService

10..n 10..n

BusinessInteractionComprisedOf0..n

0..n

0..n

0..n

BIItemInvolvesServiceSpec0..n

0..n

0..n

0..n

BIItemInvolvesResource

0..n

0..n

0..n

0..n

BIItemInvolvesResourceSpec

0..n

0..n

0..n

0..n

BIItemInvolvesProduct

0..n

0..n

0..n

0..n

BIItemInvolvesProductOffering

0..n

0..n

0..n

0..n

BIItemInvolvesProductSpec



BusinessInteractionPriceValuedBy

Business Interaction Item Price1 New VPN2 New Routers2 New Connections30 New Users

World-Wide Roamer VPNVPN RoutersVPN Connections (Circuits)VPN Remote Users

Get first 10 Roamers Free

BusinessInteractionPriceInfluencedByBusinessInteractionItem

BusinessInteractionItemInvolvesProductOffering

ProductOffering

0..n

0..1

0..n

0..1

ProductOfferingPrice

0..n

0..n

0..n

0..n

ProdOfferValuedByPrice

BusinessInteractionItemPricequantity : Quantityprice : moneydescription : string

0..n

1

0..n

1

BusinessInteractionPriceValuedBy

PolicySet(from Policy Framework)

0..n

0..1

0..n

0..1

BusinessInteractionItemPriceInfluencedBy

1 New World-Wide Roamer VPN($500 setup fee)

2 New VPN Router($7500)

2 New VPN Connection($500 per month)

10 New VPN Remote Users($0 per month)

20 New VPN Remote Users($50 per month)World-Wide Roamer VPN ($500 setup fee)

VPN Router ($7500)VPN Connection ($500 per month)VPN Remote Users ($50/month, $0/month)



Agreement Business Entities

1

0..n


BusinessInteractionAtomic

1

0..n

1

0..n

BusinessInteractionComprisedOf

AgreementVersion

Agreement

1

0..n

AgreementModifiedBy

AgreementItem

10..n 10..n

AgreementConsistsOf

AgreementTermOrCondition

1

0..n

1

0..n

AgreementGovernedBy

0..n

0..n

0..n

0..n

AgreementItemGovernedBy

AgreementAuthorization

AgreementApproval

1 0..n1 0..nAgreementAcceptedVia

1

0..n

1

0..n

AgreementApprovalRepresentedBy



Customer



Customer

CustCred itProfi leReferencefinancialInstitutionNamefinancialInstitutionAccoutNumberfinancialInstitutionAccountTypefinancialInstitutionContactNamefinancialinstitutionContactMedium

CustomerQuote/Offer(f rom Customer Interaction ABE)

CustomerCreditProfilecreditProfileIDcreditProfileDatevalidFor : TimePeriod 0..n1 0..n1

CustCreditProfileIncludes

CustomercustomerIDcustomerStatuscustomerRank

0..n1 0..n1CustomerRequests

0..n

1

0..n

1 CustomerStabilityMeasuredBy

PartyRole(from Entities)

CustomerAccountaccountIDaccountNameaccountTypeaccountStatus

0..n

1..n

0..n

1..n

CustomerPosseses

Intelliden

Intelliden British AccountIntelliden United States Account



Customer Account

CustomerAccountReferencesDetail

Customer

CustomerAccountBillCycle

CustomerAccountTaxExemption

CustomerAccount

PartyRole

0..n 0..n0..n

CustomerAccountReferences0..n

1..n

0..n

1..n

0..n

CustomerPossesses

1

0..n

1

0..n

CustomerIsBilledDuring

1

0..n

1

0..n

CustomerExemptedFromTaxesVia

0..n

0..n

0..n

0..n

CustomerAcctContactedVia

CustomerAccountContactDetails

ContactMedium0..n 0..n0..n 0..n

PartyRoleContactableVia

0..n

0..n

0..n

ContactMediumForCustomerAccount

0..n



Customer Order

CustomerOrder1 0..n1

Request

AccessServiceRequest

DirectoryServiceRequest

LocalServiceRequest

ProductOrder

CustomerOrderComprisedOf

0..nCustomerOrderItem




Product



Product Spec-Offering Pattern

ProductSpecification(from Product Specification ABE)

0..n 0..n0..n

ProdSpecReferences

0..n

ProductOffering(from Product Offering ABE)

1

0..n

1

0..n

ProdSpecMadeAvailableAs

Product(from Product ABE)

1

0..1

1

0..1

ProdOfferDescribes

0..n 0..n0..n

ProductReferences

0..n

World-Wide Roamer VPNVPN RouterVPN Connection (Circuit)VPN Remote User

Intelliden’s World-Wide Roamer VPNIntelliden’s VPN Router 1Intelliden’s VPN Router 2Intelliden’s VPN Connection 1Intelliden’s VPN Connection 2Intelliden’s VPNRemote Users (30 instances)

VPNRouterConnection (Circuit)Remote User



Product Specification

ProductSpecificationRelationship

AtomicProductSpecification

ProductSpecificationTypeProductSpecificationCost

CompositeProductSpecification

ProductSpecification

ProductLine ProductCategory

10..n 10..nProdSpecTypeCategorizes

0..n0..n 0..n

ProdSpecReferences

0..n10..n 10..nProdSpecDevelopmentIncurs

0..n

0..n

0..n

0..n

ProdSpecCompositeComprisedOf



Product Spec Characteristic

ProductSpecificationVersion

ConfigurableProductSpecCharacteristic

ProductSpecCharacteristic

ProductSpecCharacteristicValue


0..n 0..n0..n

ProdSpecCharacteristicReferences

0..n

1

0..n

1

0..nProdSpecCharacteristicTakesOn

0..n

0..n

0..n

0..n

ProdSpecCharacteristicDescribes

0..n

0..n

0..n

0..n

ProdSpecDescribedBy

1 0..n1 0..n

ProdSpecModificationsRecordedAs



Product Offering

0..n

SimpleProductOfferingBundledProductOffering


DistributionChannel

MarketStrategy

MarketSegment

ProductCatalog

ProductOfferingPrice

Location

ProductOffering

0..n 0..n0..n 0..nProdCatalogAvailableVia

0..n

0..n

0..n

0..n

BundledProdOfferComprisedOf

1 0..n1 0..n

ProdSpecMadeAvailableAs

0..n

0..n

0..n

ProdOfferingProvidedBy

0..n 0..n0..n 0..nProdOfferingSupportedBy

0..n0..n 0..n0..nProductOfferingTargetedTo

0..n

0..n

0..n

0..n

ProdOfferingPublicizedIn0..n

0..n

0..n

0..n


0..n0..n 0..n0..nProdOfferingLocatedAt



Product Offering Price

CompositeProdOfferPriceCom prisedOf

ComponentProdOfferPrice- name- value

ProductOffering(f rom Produc t Off er ing ABE)

ProductOfferingPrice+ currencyType+ validFor : TimePeriod

0..1

0..n

0..1

0..n


Composi teProdOfferPrice

0..n

0..1

0..n

0..1

World-Wide Roamer VPNVPN RouterVPN Connection (Circuit)VPN Remote User

World-Wide Roamer VPN ($500 setup fee)VPN Router ($7500)VPN Connection ($500 per month)VPN Remote Users ($50/month, $0/month)



Product Offering Price Rule

PolicyOperator(from Policy Statement Ent...)

PolicyValue(from Policy Value Entities)

PolicyStatement(from Policy Statement Entities)

PolicyVariable(from Policy Variable Entities)

1..n 1..n1..n 1..n

OperatorConstrai ntInVari .. .

1..n1..n 1..n

0..n

1..n

0..n

1..nUsesVariable

PolicyVariable(from Policy Variable Entities)

PolicyOperator(from Policy Statement Ent...)

1..n 1..n1..n 1..n

OperatorConstrai ntInVari .. .

PolicyValue(from Policy Value Entities)

1..n1..n 1..n

ValueConstraintInVariable

PolicyActionAtomic(from Policy Action Entities)

PolicyStatement(from Policy Statement Entities)

0..n

1..n

0..n

1..nUsesVariable

0..n

1

0..n

1

UsesOperator0. .n

1..n

0. .n

UsesVal ue

0..11 0..11

PolicyStatementInPolicyAction

0..111

PolicyStatementInPoli cyCondit ion

PolicyCondition(from Policy Condition Entities)

PolicyRule(from Policy Framework)

0..n

1..n

0..n{ordered}

1..nPolicyConditionInPolicyRule

Pol icyAction(from Policy Action Entit ies)

0..n

1..n

0..n {ordered}

1..nPolicyActionInPolicyRule

ProdOfferPriceAction(from Product Offering Price Ru...)

ProductOf f eringPrice(f rom Pr oduc t Of fering Price A BE)

0..n

0..n

0..n

0..n

ProdOfferPri ceActi onResultsInProdOf

PolicyConditionAtomic(from Policy Condition Entities)

Get first 10 Roamers Free

VPN Remote User (Product Offering related to rule)

$0 per month$50 per month

1 to 1011 and above



ProductComponent

ProductSpecCharacteristicValue(f rom Product Specif ication ABE)

ProductSpecCharacteristic(f rom Product Specif ication ABE)

ProductOffering(from Produc t Offer ing ABE)

ProductBundle

ProductCharacteristicproductCharacteristicValuevalidFor

0..1

0..n

0..1

0..n

ProdSpecCharValueInstantiatedAsProductCharacteristic

0..1

0..n

0..1

0..n

ProdSpecCharDescribesProdCharacteristic

Productname : StringdescriptionproductStatusproductSerialNumbervalidFor : TimePeriod

1

0..n

1

0..n

ProdOfferDescribes

0..1

0..n

0..1

0..n

ProductBundleComprisedOf

0..n 0..n0..n

ProductReferences

0..n

0..n 10..n 1ProdCharDe finesTheConfigu rat io nOf

Place(from Entities)

0 ..n

0..n

0 ..n

0..n

ProductLocatedVia

Product

Intelliden’s World-Wide Roamer VPN

Sample User Instance Characteristics



Service



High-Level Service Concepts

Service

ResourceFacingService

CustomerFacingService

0..n1..n1..n 0..n

CFServiceRequiresRFServices

Services required by CFS but which are invisible to Customers

Services directly visible to and consumable by Customers




ServiceSpecificationType0..n 0..n0..n

InvolvedServiceSpecTypes

0..n

ServiceSpecVersion

ServiceSpecCharacteristic

ServiceSpecCharacteristicValue

Service

Specification

ResourceFacingServiceSpecResourceFacing

Service1

0..n1

0..n

SpecifiesResourceFacingService


0..n1..n 0..n1..n


CustomerFacingServiceSpec

0..n 1..n0..n 1..n

RequiresResourceFacingServiceSpec

10..n

10..n

SpecifiesCustomerFacingService

ServiceSpecificationRole

ServiceSpecification0..n

0..n

0..n


0..n

0..10..n 0..10..nCategorizesServiceSpecs

1

0..n

1

0..nServSpecModifications

10..n 10..n

ServiceSpecCharacterizedBy

10..n

10..n

ServiceSpecDescribedBy

10..n

10..n SpecifiesService

1

0..n

1

0..nSpecifiesServiceSpecRoles

Template for defining the invariant characteristics and behavior of a Service



ServiceCharacteristics


S ervice Sp ecCharacteristicValue0 ..n

1

0 ..n

1

ServiceSpecDescribedBy

Service

1

0..n

1

0..n

S pe cifiesS ervice

ServiceSpecCharacteristic10..n 10..n

ServiceSpecCharacterizedBy

1

0..n

1

0..n

ServiceSpecTakesOn

ServiceCharacteristic

10 ..n 10 ..nServiceCharacterizedBy

1

0 ..n

1

0 ..n

specifiesServiceCharacteristics

ServiceCharacteristicValue0..n

1

0..n

1

ServiceDescribedBy

0..n

1

S erviceTa kesOn

0..n

1

Key Instance-Specific Service Features

Key Invariant ServiceSpec Features

Limitations of ServiceCharacteristics

Limitations of ServiceSpecCharacteristics



ServiceRole

CustomerFacingServiceRole

ResourceFacingServiceRole

0..n0..n 0..n0..n

CFSRoleRequiresRFSRoles

CustomerFacingServiceSpecRole

ResourceFacingServiceSpecRole

0..n 0..n0..n 0..n

RequiresResourceFacingServiceSpecRoles

ServiceSpecificationRole0..n0..n 0..n

InvolvedServiceSpecRoles

0..nServiceRole0..n 0..n0..n

InvolvedServiceRoles

0..n

1 0..n1 0..nspecifiesServiceRolesServiceSpecification

0..n 0..n0..n


0..n

10..n

10..n

SpecifiesServiceSpecRoles

Service

10..n 10..nUsesServiceRoles

1

0..n

1

0..n

SpecifiesService

Abstracts invariant behavior and characteristics and in terms of roles

Abstracts Service with respect to how it is used

Defines roles as part of the “template”



The Concept of a ServicePackageService OfferingService OfferingService OfferingService Offering

Service Level

Service Quality

Highest Lowest

Different CoSDifferent CoSDifferent CoS



ServicePackageSpec – ServiceBundleSpecServiceSpecification0..n

0..n

0..nInvolvedServiceSpecs

0..n

CustomerFacingServiceSpecAtomic

ResourceFacingServiceSpecAtomic

CustomerFacingServiceSpecComposite

CustomerFacingServiceSpec

0..1

0..n

0..1

0..n

HasCustomerFacingServiceSpecs

ResourceFacingServiceSpecComposite

ResourceFacingServiceSpec

0..n 1..n0..n 1..nRequiresResourceFacingServiceSpec

0..1

0..n

0..1

0..n

HasResourceFacingServiceSpecs

ServiceBundleSpecAtomic

ServicePackageSpecAtomic

ServiceBundleSpecComposite

ServiceBundleSpec

0..1

0..n

0..1

0..n

HasServiceBundleSpecs

ServicePackageSpecComposite

ServicePackageSpec 0..n 0..n0..n 0..nServicePackageSpecUsesServiceBundleSpecs

0..1

0..n

0..1

0..n

HasServicePackageSpecs

CoS1BundleSpec

CoS2BundleSpec

CoS3BundleSpec

CoS4BundleSpecService Offerings

CoS Definitions



QoS – High-Level Concepts

ResourceFacingServiceAtomic

ToSService

802Service

DiffServService


ResourceFacingServiceComposite

0..n

0..1

0..n

0..1

RFSCompositeHasRFServices

TrafficCondition ingService

TrafficIdentificationService

QoSService

0..1

0..n

0..1

0..nConditionsQoSService

0..n

0..1

0..n

HasQoSSubServices

0..1

0..1

0..n

0..1

0..nIdentifiesQoSService

NetworkForwardingService 0..n

0..n

0..n

NextForward ingService

0..n

0..11..n

0..11..n ForwardingDefinedBy

ServiceBundle

How traffic is treated Class of Service

Technical approach to traffic differentiation and conditioning

How traffic is limited, shaped, queued and dropped compared to other traffic

How traffic is identified



Services and CompoundResources

Resource CompoundResource

ResourceManagementPo licyDeta ilsresourcePolicyValidFor : TimePeriod

ResourceManagementPolicy

1

1..n

1

1..n

usesResourcePolicy

ManagedEntity

Service

PartyRole 1..n 11..n 1resourceManagedBy

0..n

0..n

0..n

0..nserviceManagedBy

Administrator, Technician, etc.Resource being managed

Policy for managing a resource

Service being managed



SLA-SLO-SLS

TemplateServiceLevelSpec NegotiatedServiceLevelSpec

ServiceLevelSpecConsequenceServiceLevelSpecification

1 0..n1 0..nServiceLevelSpecsUnmetObjectiveResultIn

ServiceLevelAgreement

ServiceLevelObjective

0..n

0..n

0..n

0..n

SLOViolationResultsIn

0..1

1..n

0..1

1..n

SLOImplementedBy

0..n

0..1

0..n

SLAGoalsMetBySLO

0..1

A contractual agreement

How to meet SLA goals

How to implement SLO

What happens if SLS is not met



Resource



High-Level Resource Concepts

ResourceElement

PhysicalAspectCompoundResourceDetails

LogicalAspectCompoundResourceDetails

PhysicalResource LogicalResource

0..n 0..n0..n 0..n

ResourceCollection

Resource

CompoundResource1..n

0..1

1..n

0..1

HasCompoundResources

2..n

0..1

2..n

0..1

CompoundResourceAspects

CompoundResourceAspectDetails

CompoundAspectCompoundResourceDetails

PResourceSupportsLResource

Generic abstractions of laptops, routers, PDAs, …

Reusable library of physical aspects

Reusable library of logical resource aspects

Recombined into a single entity

Semantics of therecombination




ResourceSpecA tomic

LogicalResourceSpecAtomic

LogicalResourceSpecComposite

PhysicalResourceSpecAtomic

PhysicalResourceSpecComposite

LogicalPhysicalResourceSpec

ResourceSpecComposite


0..1

1..n

0..1

1..nContainsResourceSpecs

0..n0..n 0..n


0..n

0..n

0..n

0..n

PhysicalLogicalResSpecBinding

0..n

Defines invariant behavior and characteristics of this dependency association



ResourceSpecVersions

ResourceSpecVersionresSpecRevisionName : StringresSpecRevisionFormat : StringresSpecRevisionNumber : S tringresSpecRevisionReason : StringresSpecRevisionSemantics : StringresSpecRevisionTimestamp : TimeS tampresSpecRevisionValid ityP eriod : TimeP eriod


0..n 10..n 1ModifiesResourceS pec

ResourceSpecVersionDetailsresourceSpecVerValidFor : TimePeriodpreferredVersionToUse : StringminVersionForUse : String

Log icalResourceSpecVersion

Specification



ResourceCharacteristics

LogicalResourceCharacteristic

LogicalResourceSpecCharacteristic

LogicalResource

ResourceCharacteristicValue

ResourceCharacteristic

0..n

1

0..n

1

resourceTakesOn

Resource0..n 10..n 1

resourceCharacterizedBy

0..n

1

0..n

1

resourceDescribedBy

ResourceSpecCharacteristic

0..n

0..1

0..n

0..1

specifiesResourceCharacteristics

ResourceSpecCharacteristicValue0..n

1

0..n

1

resourceSpecTakesOn


1

0..n

1

0..n

SpecifiesResource

0..n

0..n

0..n


0..n0..n 10..n 1

resourceSpecCharacterizedBy

0..n

1

0..n

1

resourceSpecDescribedBy



PhysicalResourcePhysicalResource

ManagedHardware

PhysicalContainerPhysicalPort

PhysicalDevice Hardware

0..1 0..n0..1 0..nconsistsOf

PhysicalConnector

EquipmentEquipmentHolderAuxiliaryComponent PhysicalComponent

Complete deviceswhich are Products

Components of a PhysicalDevice

Manageable components

Physical comminterface

Manageable components that contain other components



LogicalResource Overview

LogicalResource

ManagedTransmissionEntity OperatingSystemLogicalDevice

ResourceSpecification0..n 0..n0..n


0..n

CompoundResource

Resource

1 0..n1 0..nSpecifiesResource

0..1

2..n

0..1

2..n

CompoundResourceAspects

PhysicalResource


LogicalResourceRole

Location

0..n0..n

0..n0..n


0..11..n

0..11..n

LogicalResourcesImplementRFS

0..1 0..n0..1 0..n

RolesDescribeLogicalResource

0..n

0..n

0..n

0..n

LogicalResourceLocatedAt

LogicalLocationDetails

Services that depend on this LogicalResource

The BRAINS!

PhysicalResources that depend on this LogicalResource

Root class for representing communications Carries out the wishes of the BRAIN

A specific Location that this LogicalResource resides at



DeviceInterfaces

DeviceInterfaceRolePhysicalPort

LogicalDevice

DeviceInterface 1 0..n1 0..nDeviceInterfaceTakesOn

1 0..n1 0..nPPortHasInterfaces

1

1..n

1

1..n

LogicalDeviceHasDeviceInterfaces

NetworkAddress

1

0..n

1

0..n

In terfaceContainsNetworkAddress

DeviceInterfaces are logical entities and must exist in a physical container

DeviceInterfaces are how a LogicalDevice communicates with other ManagedEntities

NOT just IP!

Abstraction enables similar DeviceInterfacesto be managed in a common way



Software

SoftwareInteractionDeta ilsosVersionMinReq : String

Resource

LogicalResource

SoftwareAtomic

LogicalDevice OperatingSystem

SoftwareComposite

SoftwarebuildNumber : Stringcategory : IntegerisExperimental : BooleanmaintenanceVersion : StringmajorVersion : StringminorVersion : StringotherDesignator : String

compareVersion()

1

1..n

1

1..n

hasSoftwareFeatures

0..n

0..n

0..n

0..n

softwareInteractsWIthOS

0..1

0..n

0..1

0..n

containsSoftwareComponents

Individual commands

Dependency semanticsSets of similar commands (“features”)



Protocol

Protocol

ManagementProtocol

RoutedProtocol

RoutingProtocol SignalingProtocol WANProtocol

LANProtocol BridgingProtocolSwitchingProtocol

e.g., SNMP

e.g., BGP, OSPF e.g., COPS, RSVPe.g., ATM, FR, PPP

e.g., IP, DecNET e.g., MPLS e.g., Ethernet, TokenRing e.g., SRT Bridging



Putting It Together



Product – Service – Resource

ProductComponent

ResourceService

LogicalResourceResourceFacingService

0..1 1..n0..1 1..n

LogicalResourcesImplementRFS

ProductBundle


0..n1..n 0..n1..n


PhysicalResource

0..n0..n 0..n0..n


0..1 1..n0..1 1..n

PhysicalResourcesHostRFS

Product0..n0..n 0..n

ProductReferences

0..n

0..1

0..n

0..1

0..n

ProductBundleComprisedOf

0..n

0..1

0..n

0..1

ProductHasCustomerFacingServices

0..n

0..1

0..n

0..1

ProductHasPhysicalResources

Services and Resources are delivered through Products



Managing Resources and ServicesEntity

ResourceStateInfo

ResourceStatisticalIn fo

FaultEntity

ConfigurationEntity

AccountingEntity

PerformanceEntity

SecurityEntity

CLIMethod

RMONMethod

SNMPMethod

TL1Method

ProprietaryMethod

DescribedMgmtInfoDetails

ManagementEntityManagementMethodEntity

1..n

1

1..n

1mgmtInfoObtainedBy

ManagedEntity

0..n1 0..n1describedByMgmtInfo

1..n 11..n 1

supportedMgmtMethods

Management informationHow you get it



Owning & Administering Resources & Services

Administrator Technician

OwnsServiceDetails

AdministerServiceDetails0..n

0..1

0..n

0..1

GrantsServiceAdminRights

ServiceManagementPolicyservicePolicyValidFor : TimePeriod

0..n

0..n

0..n

0..n

ManagementPolicyForService

OwnsResourceDetails

ResourceManagementPolicyresourcePolicyValidFor : TimePeriod

AdministerResourceDetails

0..1

0..n

0..1

0..n

GrantsResourceAdminRights

0..n

0..n

0..n

0..n

ManagementPolicyForResource

ValueNetworkRole Resource

0..n0..n 0..n0..n

AdministersResource

Service

0..n 0..n0..n 0..n

AdministersService

PartyRole

0..n

1

0..n

1OwnsResource

0..n

1

0..n

1OwnsService



SID in Action



SID in Action - IntellidenIntelliden is using the SID as a basis of its product offering…

Using the Resource model to manage heterogeneous routers and switchesWill be using the Policy, Service, and other models to expand our product offerings

…and as the basis of new products



Intelliden Basic ArchitectureBillingProvisioning Network

ManagementInventory OrderEntry

FCAPS

Integration Bus/ Middleware

OpticalSwitching

Module

CiscoSwitching

Module

CiscoSwitching

Module

JuniperRoutingModule

CiscoRoutingModule

OtherModules

Middleware

Common API and SDK

CommonGUI

J2EE App Server

Directory

Copyright Intelliden



DEN-ng Model Driven Code GenerationDEN-ng

UML Model

Schema PreparationProcess

ModelMapping

Rules

Schema GeneratorProcess

ParsedOutput

Documentationand Help Files

Errors andWarnings

Java Mappingfor Session

Computation

DirectoryMapping forPersistence

DirectoryMapping forPersistence

Directory and JavaSpace

Mappings forPersistence



SID in Action - MetaSolvMetaSolv is using the SID in two ways:

As the basis for new development and enhancements to our applicationsAs part of the MetaSolv Integration Platform (shown on the next slide)



SID in Action - MetaSolv

MIM Core

TM Forum SID

MetaSolv Common

MetaSolv Application-Specific

Extensions

MIM Core

TM Forum SID

MetaSolv Common

MetaSolv Application-Specific

Extensions



SID in Action - MetaSolv



SID in Action in BTBT is using the SID model in two ways

for business integrationin a model-driven prototype implementation in the IP network

Some business areas are considering mandating its use

For more information, contact [email protected]



SID in Action in BTFor business integration, work is at an early stage. Data design started with the SID Framework and two major areas of BT are now using the detail of the SID addenda. The next stage is working on how to manage a common model into multiple implementations. The IP prototype is using the full detail of the SID Policy, Service and Resource addenda and feeding back issues to the SID team.



SID in Action at TelstraTelstra Corporation is a full service providerTelstra is currently using the TSIM (Telstra specific version of the TMF SIM) as a classification method for management systemsTelstra is currently using the TeTOM (Telstra specific version of the TMF eTOM) as a process modelTMF releasing a SID to eTOM mapping will improve the value of the TeTOM and help provide a migration path for Telstra to adopt and socialise the SID within TelstraThe release of the planned SID System View will trigger Telstra’s migration from TSIM

For More information, contact [email protected]



More SID in ActionMajor Canadian service provider using the SID as the foundation for its corporate information architectureAnother Canadian service provider using the SID as the framework for Service Oriented Architecture (SOA)Australasian service provider using the SID as the basis for a new order management applicationAnd there are more…



NGOSS-SID and OSS/J-CBE



In the beginning …

Any J2EE CompliantApplication Server

API

NativeImplementation

API

J2EEApplication

API


APIAPI


API

J2EEApplication

API

J2EEApplication

JavaAPI

Java upon JMS/IIOP/RMI


JavaAPI



XMLAPI

XML upon JMS

XML upon JMS

XMLAPI

XML upon JMS

XML upon JMS

ebXMLSOAPUDDIWSDL

B2BWeb

Servicesenabled

Application

ebXMLSOAPUDDIWSDL

B2BWeb

Servicesenabled

Application

B2BWeb

Servicesenabled

Application

EAI

JMS Bridge

Connector

LegacyApplication

EAI

JMS Bridge

Connector

LegacyApplication

Connector

Wrapping andAdapters Strategies

LegacyApplication

Connector

Connector


LegacyApplication

Connector


ConnectorConnector


LegacyApplication

LegacyApplication

Connector

There was a vision …



And along comes reality …



Functionality … we got it coveredJSR 144: The OSS Common APICommon base for all APIsDesign Guidelines for:

Java Value interfacesXML interfaces

Provides framework components …

But wait a minute Johns we all know the real problem of integration is in the information …



The DilemmaThe OSS/J Initiative Common Team looked at the three initial APIs and there was no overlapAlong comes the Inventory Management API …Short term solution …

Inventory Management Expert Group decided that that the inventory implementation of service would implement the Service Activation Service interface as well…

A long term solution was needed …



SID Provides the Optimal SolutionHow to bridge the gap …

Service Activation DefinesInventory Management DefinesDefine a common view of service

TMF SID has a rich Service model …Given that the problem being faced by the OSS/J technical teams would be endemic, the SID provided a ready-made answer



Why Use the SID ?Rich information models take a great deal of time and effort to develop

OSS through Java is an implementation body, not a modeling forum

SID is a key aspect of NGOSSAdoption is the key to successOSS through Java is working to make NGOSS real

OSS/J Common Business Entities map the SID analysis (GB922) and design (GB926) models to Java data models



CBE and the OSS/J APIsOSS/J Core

Business Entities

Vendor and Technology Information

Model

Customer Management

API

InventoryAPI

ServiceActivation

API

OtherOSS/J

API

Functional Partition of OSS Business Logicinto APIsAnd RealizationOf the Vendor orTechnology SpecificInformation Model

Vendor or TechnologySpecificInformationModel is an Extensionof the Core SID/CBE Entities

OSS/J Core SID/CBE Entities



CBE EssentialsCBE means Core Business EntitiesCBE defines a CORE information model

CORE Information Model of shareable Data Transfer Objects in CBE aligned with SID from which the Vendor Specific Information Model must derive

CBE defines interfaces that are reusable across multiple OSS components (Activation, Inventory, TroubleTicket, QoS, etc…)

Common Managed Entities:Service, Resource, Product, Alarms

Common Types Addresses, TimePeriods etc.



CBE Core ModelThe CBE Core Model is composed of:

EntityEntities are value type objects representing inventory concepts such as “Product”, “Service” and “Resource”

Entity SpecificationEntity Specifications are value type objects representing specifications of CBE entities

AssociationAssociations are value type objects representing CBE associations, e.g. “ResourceSupportsServiceAssocValue”



So Where do I Find the CBE ?javax.oss.cbe

The CBE package defines a set of interfaces that represents the upper layers of a generic information model within the OSS domainThe CBE package defines a set of shareable Data Transfer Objects, via interfacesImplementations of CBE aware APIs provide the implementation; Java™ and J2EE™ do the rest …

The CBE paper …http://java.sun.com/products/oss/

… follow the link in the right hand column

http://java.sun.com/products/oss/



A Glimpse at SID Phase VI



SID Phase VI Model Proposed Work (1)

Harmonization of other TM Forum effortsIntegrate MTNM into the SIDIntegrate IPNM into the SIDAdjust the SID as necessary to meet other team needs

Continued TM Forum project supportContinued industry group liaisonsGB928

End-to-end VPN exampleDescribes how to build an NGOSS model covering the complete lifecycle of a VPN solutionIncludes glimpses at Implementation and Deployment views



SID Phase VI Model Proposed Work (2)GB922

Development of Market/Sales DomainDevelopment of Billing and Invoicing Details

GB926Service and QoS AddendaPolicy, Product and Party from a system viewpoint

Focused work on supporting the NGOSS Lifecycle and Methodology

Ties back into the end-to-end VPN example

Detailed modeling of managementOwning vs Using vs Administrating vs. …

Focused effort on Performance ABE



Contacting the TM ForumIn North AmericaTel.: +1 973-292-1901

In EuropeTel:+44-1473-288595

[email protected]:Web: www.tmforum.orgTraining Plus: [email protected]

T+ @ Long Beach (2004), Intro to the SID


http://www.tmforum.org/




Next StepsTraining Plus at TeleManagement World, Nice, France, 16-19 May, 2005:

http://www.tmforum.org/browse.asp?catID=2194

TeleManagement Regional Summit, Bangalore, India, 5-6 December, 2004:

http://www.tmforum.org/browse.asp?catID=1118&linkID=29688

TM Forum “We Come to You” courses: http://www.tmforum.org/browse.asp?catID=1565Contact [email protected] if you would like us to provide a SID course to you and your colleagues

TM Forum Webinar series:http://www.tmforum.org/browse.asp?catID=2065

SID on the web: http://www.tmforum.org/browse.asp?catID=1684


http://www.tmforum.org/browse.asp?catID=1118&linkID=29688





Date post:	26-May-2018
Category:	Documents
Upload:	dohuong
View:	220 times
Download:	0 times

Introduction to the SID - POSTECH CSE DPNM …dpnm.postech.ac.kr/papers/TMW/TMW2004-LongBeach… ·...

Documents