Transcription

Interoperable Standards forTelecom e-BusinessJenny HuangAT&T LabsOSS Architecture and Strategic [email protected]

! The Telecom e-Business challenges! TMF and it’s collaboration with other industry groups! SummaryInterop Summit June 27, 2002Interoperable Standards for Telecom e-BusinessTopicsSlide 2

! Delivering Services rather than Physical Products.Most existing e-business approaches have focused on delivery physical goods.Service providers deliver telecommunications services that place additionalrequirements on e-commerce solutions such as assurance, SLA agreements,and security.! Service LifecycleInterop Summit June 27, 2002Interoperable Standards for Telecom e-BusinessThe Telecom e-Business ChallengesThe sale of telecommunications services is a process that starts with theprovisioning phase and continues in time for many aspects (e.g. billing,assurance). These aspects are not usually addressed by standard B2Bsolutions.! Telecommunication Service complexityTelecommunications services have many attributes amongst which are: thelocation of the service end point, the technical specification of the serviceinterfaces, the SLA and service wrap around a technical product, pricingpackages and volume discount offers.Based on Eurescom P1106 project feasibility studiesSlide 3

! Service Platform IntegrationThe complexity of the above lifecycle aspects of Telecom products, makes itmore difficult to integrate B2B platforms with legacy systems and networkmanagement systems.! General e-Business technologies can be leveraged but notenoughInterop Summit June 27, 2002Interoperable Standards for Telecom e-BusinessThe Telecom e-Business Challenges (cont’d)There is economic value in reusing the investment being made for many otherindustries, but Telecom specific context need to be introduced and interoperatewith generic set of standards. Need knowledge base from both camps.Slide 4

Universal BusinessDictionary ContentVertical TechnicalDictionary ContentBusiness DictionaryStructureTechnical DictionaryStructureBusiness ModelSpecific ProcessUniversalBusiness ProcessProcess Description LanguageDirectory ServiceCore XML Format StandardsSecurityInterop Summit June 27, 2002Business Document DefinitionSupply ChainBusiness ProcessTrading Partner AgreementInteroperable Standards for Telecom e-BusinessThe E-business Software ElementsProcess Coordination FrameworkMessagingService Oriented ArchitectureBackend IntegrationNon e-business specific Standards, Protocols & ToolsE-business Definitions, Format, Structure and ChoreographyAdopted from Derek Coleman’s RosettaNet Conceptual ArchitectureSlide 5

Vocabulary and structure defined forspecific technology domain e.g. T1M1 tMLand its artifacts for Telecom industryCommon business vocabulary Universal Businesse.g. ebXML core components Dictionary ContentRosettaNet bus. dictionarye.g. RosettaNet PIPOAG BODSupply ChainBusiness ProcessBusiness ModelSpecific Processbusiness process thatare specific to a givensupply chain.e.g. DSL ordering,provisioningbusiness process thatmay inherit fromuniversal or supplychain but for diff.Business model e.g.retailer, wholesaler,non-profitTelecom Domain SpecificVocabularies & ContentUniversalBusiness Dictionary Technical DictionaryStructureStructureBusiness Document DefinitionBusiness specific document structure built fromabove business vocabulariesCore XML Format StandardsBuilding blocks of XML content forbusiness document representationBusiness Processbusiness process that areapplicable to all businesse.g. invoice, orderProcess Description LanguageMethods to record repeatable business processTelecom Domain SpecificRequirements & Servicese.g. XML DTDXML schemaXSLTVertical TechnicalDictionary ContentTrading Partner AgreementSchema for businessdictionary structure.e.g. RosettaNet BDSDynamic creation and managementof trading partner agreemente.g. ebXML CPPADirectory Servicestructure and access protocol forregistries and repositories for partner discoveryProcess Coordination Frameworke.g. ebXML TRPSOAP-RPCe.g. J2EE.NETe.g. CORBA,MQseries adaptersTelecom ServiceSecuritySpecific RequirementsE-BUSINESSElementscomplements messaging layer for looselycoupled environmentSecuritymechanism spanthru all layers. E.gDigital signature,MIME enveloping,SSLv3, XMLsignaturee.g. UMLebXML BPSSe.g. UDDISi2 Registrye.g. WSDLXLANGMessagingSession management and transaction coordination including reliable and secured messagingService Oriented ArchitectureDevelopment platform for web-based servicesBackend IntegrationTechnology specific adapters, APIs, shared message busNon e-business specific Standards, Protocols & ToolsE-business Definitions, Format, Structure and Choreography

! The Telecom e-Business challenges! TMF and it’s collaboration with other industry groups! SummaryInterop Summit June 27, 2002Interoperable Standards for Telecom e-BusinessTopicsSlide 7

What is TM Forum! Non-profit global consortium providing leadership on OperationsSupport Systems (OSS) and management issues for the entirecommunications industry– 350 members in 38 countries– Service providers, software and hardware suppliers, systemsintegrators! Provides a collaborative environment where companies canaddress critical business and technical issues! Provides on-line access to industry information, marketconditions and technical solutions! Provides in person education,information and networkingopportunities– TeleManagement World Conference & ExpoThe voice of the OSS industry

We Serve the Entire OSS Value ChainMiddlewaresuppliers: PlatformsuppliersMediationsuppliers Databasesuppliers iers: Point systems Small solutionsuitesSolutionssuppliers: Systemsintegrators Computercompanies Ex telco groups EquipmentsuppliersService andnetworkoperators: Fixed Mobile ISP ASP MVNO Etc.

Value Chains are Fluid and mersNetworkTransportOperatorsWholesaleToday! Partnerships get created, dissolved & re-createdin real time to meet market opportunities! New suppliers brought in to offer newcapabilities but must “fit in”! Mergers & acquisitions keep the situation in aconstant state of fluxBackboneSuppliersCustomersContentProviders! In the past, systems were deployed in a preciseand known environmentAccessProviders

What areas does TM Forum address?! Provides strategic leadership and guidance on:–––––New Generation Operations Systems and Software (NGOSS)Business Process Modeling and AutomationShared Information and Data Modeling and UsageService Creation, Provisioning & DeliveryWeb-Based Customer Care (E-Care) and Customer Relationship Management(CRM)– Service Level Management & Quality of Service– Managing Next Generation Network Technologies (Broadband, Mobile, etc.)– Systems Integration and Implementation! Enables collaborative, business-driven solutions based on commerciallyavailable software and industry standards

TM Forum - Industry Group Advisory BoardIGAB Objectives– To provide a focal point within TM Forum for knowledge on the work of other IndustryGroups who are particularly relevant to the work programme of TM Forum– To build a picture of the working of TM Forum in relation to a selection of other IndustryGroups. This picture to include both technical content and method of working– To provide advice to TM Forum working teams on the developments available from otherIndustry Groups in order that TM Forum may take full account and build upon this workwhere appropriate– To advise TM Forum Management (including Board of Directors) on benefits of workingrelationships with selected Industry Groups– To provide a focus for the dissemination of TM Forum’s work into other Industry Groups inorder that they may take full account and build upon this work where appropriate.– To assist TM Forum in the operation of its work-programme evaluation in relation to theplacement of work from other Industry Groups. For example, evaluation of new workproposals – as specified within TM Forum Project Charters.Through all of the above help to build closer working relationships between selected IndustryGroups in order to reduce duplication and confusion within the Information CommunicationsIndustry.Contact: Tony Richardson, TMForum Director Strategic Liaison, [email protected]

A Rough Mapping of TMF/IGAB Industry PartnersUniversal Business Vertical TechnicalDictionary Content Dictionary ContentSupply ChainBusiness ModelBusiness Process Specific Document Definition OBFCore XML Format StandardsBusiness ProcessProcess Description LanguageDirectoryebXMLServiceW3CSecurityTrading Partner AgreementtML DictionaryBusiness Dictionary TechnicalStructureGTDDStructureProcess Coordination FrameworkMessagingOMGDMTFOSS/JFORMService Oriented ArchitectureOpenGroupBackend IntegrationIETFANSIITU-TOfficial liaison establishedETSI3GPP3GPP2TTC

Overview TMF Next Generation OperationsSystems and Software (NGOSS)! What is NGOSS ? A TMF initiative which provides a standardized integration frameworkbased on commercial off-the-shelf information technologies, instead oftechnologies unique to the telecommunications industry for OSS. NGOSS Program - Key Elements– Definition of business processes and process models– Definition of the systems framework upon which these business solutions willbe built– Definition of a shared information model that enables different NGOSScomponents to interoperate– Practical implementations and multi vendor demonstrations via a series ofcollaborative projects– Creation of a resource base of documentation, models and code tosupport developers, integrators and users.

NGOSS Design Principles - Business Context OSS Operations and Interactions Driven by agreed BusinessProcesses and Information Flows (Top-down Business Driven) Need Framework of Agreed Business Processes (TM Forum BusinessProcess Model) Framework to support various Industry ‘Actors’ (TM Forum BusinessReference Model) Need to support linkage (Flow - Through) of business processes toprovide efficient business operation (TM Forum “Flow-Through / FAB”Model) Need detail of the Information Flows / Model associated with eachBusiness Process (TM Forum “Spider Diagrams”)

NGOSS Design Principles - System Context!!!!!!Apply Commercial off-the-shelf (COTS) productsTechnology neutral architectureThe separation of Business Process from the system functions.Will be built from distributed components with well-defined contracts.Integrated using a shared information model.Service discovery via component trading on the basis of publishedcontracts.

! The Telecom e-Business challenges! TMF and it’s collaboration with other industry groups! SummaryInterop Summit June 27, 2002Interoperable Standards for Telecom e-BusinessTopicsSlide 17

! Standards which support real business solutions! Standards which can be placed within a bigger systemspicture and understanding of the positioning of anystandards in relation to other appropriate Industry GroupeffortsInterop Summit June 27, 2002Interoperable Standards for Telecom e-BusinessWhat Do We Need from Standards?! Standards which are ensured to have practical realizationpotential – e.g. linkage to the TMF Catalyst program! Standards with the widest possible industry endorsementStandards that are interoperable !!!Slide 18

Slide 19Interop Summit June 27, 2002Interoperable Standards for Telecom e-Business

Backup Slides

Driven by eTOM Business Process ModelCustomerInfrastructure ProductSupply ChainLifecycleLifecycleLifecycleManagement Management ManagementFulfillmentAssuranceBillingCustomer Relationship ManagementService Management and OperationsResource Management and OperationsSupplier/Partner Relationship ManagementMarketing, Sales and Offer ManagementEnterprise Management

eTOMCustomerCustomerInfrastructureand CapabilityPlanning andDeliveryProductManagementandDevelopmentI&C PlanningCRM PlanningandDevelopmentOrderHandlingService Planningand DevelopmentI&C DeploymentCustomerQoSManagementBilling e ProblemManagementService QualityManagementRating andDiscountingResource and Systems ManagementNetwork, Computing and Application Resource InfrastructuresProduct Plan &PerformanceMeasurement &ReportingResource Planningand DevelopmentResourceProvisioningOffer and/orProgramManagementI&C ProgramManagementProblemHandlingService Development and OperationsProduct PlanExecutionI&C PerformanceMeasurement ion and LoyaltyNew ProductDevelopmentI&C PlanExecutionBillingAssuranceFulfillmentCustomer Relationship Management Customer Interface ManagementProduct andOffer PlanningNew ResourceMaintenance andRestorationResource DataManagementResource Element ManagementSupplier/Partner Relationship opment entDevelopment andAutomation SupportChange andProblem MgmtValue/ContractMeasurement /ManagementSettlements andBillingManagementMarketing, Sales and Offer ManagementMarketResearch andAnalysisChannelManagementMarketManagementand StrategySales ManagementProduct and OfferDevelopment ionsand BrandManagementEnterprise SupportBusinessStrategy.FinancialManage .HR ManagementKnowledge Manag .LegalManage .PR andCommunity Relatio .ProcessArchitecture Mana .Procurement Man .R&D/Technology .RealEstate M .Regulatory Manag .Stockholder Relati .Securityand FraudManage .

The Business Reference ModelService ProviderCustomerInternal ProcessesE.g. Service andNetwork MgmtCustomer / Service ProviderOther Providers/OperatorsService Provider / Service ProviderService Provider / Network ProviderNetworkSuppliersE.g. Element MgmtSystems or NetworkEquipment

Typical Fulfillment ActivitiesCustomerPre-orderService ProviderBOrderConfigureAssign llTestAccount buildActivateSupplier-provided equipment and systems

Service ngPre-orderOrderOrder Status and Completion3 Order(Customer enabledreconfiguration)Network Config RequestNetwork Config& RoutingConfigure1112SecurityAccess19 Service6.Network Config. Complete79 10RequestConfigure5 Assignment Request18 Assignment CompleteUpdate13 Test Request16 Test CompleteInstallRequest &CompleteAssurance& BillingProcesses4 eNetworkProvisioning17NetworkAccessCheck &CompleteOther SPOrder Status andCompletionSellingNetworkInventory Mgt.InstallNetworkInventory MgmtTest MgmtTest14 15Element Config & CompleteNetwork Element Mgmt& Network ElementsPerform Test &Test DataKEYActivityProcess/ Sub-processNote: Security is shown in only one interaction,but applies on every interface.Cross-FABDomain InterfaceInter/Intra Process/Sub-process Interface

Ordering Process ders/CancelsChange requestsStatus inquiriesDesired Due DateOUTPUTSEstimated Due DateEstimated PriceConfirmed Due dateOrder StatusCompletion NotificationRegister QoS & SLAterms, profilesRequired reportsQoS & SLA termsCreditCheckCreditOrder HandlingCompletion- Accept ordersResponseBureauNotification- Determine pre-order feasibilityService- Prepare price estimateOtherService orderorder &- Develop order planProvider(s)- Perform credit check& statusstatus- Request customer depositNew/changed- Initiate service installationServiceOptionsservice notificationEstablishSLAtermsPlanning/and activationPrices- Track order statusDevelopment- Complete order, notify customerPre-service- Initiate billing processServicefeasibility requestFeasibilityActivate serviceConfiguration Due date,CompletionSalesPre-order NetworkProvisioningSpecial discountsCustomer record andlingCustomer erviceConfigurationRating/DiscountingCredit CheckCreditRequestBureauService orders to other providers can either be generated by the ordering process or bythe service configuration process, depending on the nature of the service ordered by the customer.“Spider Diagram”

[email protected] Interoperable Standards for Telecom e-Business Interop Summit June 27, 2002 Slide 2 Topics! The Telecom e-Business challenges . e.g. DSL ordering, provisioning Business Model Specific Process business process that may inherit from universal or supply chain but for diff. Business model e.g. retailer, wholesaler,