Source: Geoff Caryer BT

1. TISPAN NGN OSS Service Interfaces (NOSI)TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15th 2007. Source: Geoff CaryerBT

2. Table of Contents • SOA • What is a NOSI • Comparison of NOSIs to TMN reference points/interfaces • Proposed contents of a NOSI • Co-operation with TMF • Summary

3. SOA • Service Oriented Architecture (SOA): software architecture of services, policies, practices and frameworks in which components can be reused and repurposed rapidly in order to achieve shared and new functionality • NOTE 1: This enables rapid and economical implementation in response to new requirements thus ensuring that services respond to perceived user needs. SOA uses the object oriented principle of encapsulation in which entities are accessible only through interfaces and where those entities are connected by well defined interface agreements or contracts. • Relationship of NOSI with other SOA initiatives • Equivalent to the Service in the SOA Reference Model • Equivalent to the “Contract” in Telemanagement Forum

4. NGN OSS Functional/Information View Reference Model

5. Definitions of NOSI (TS 188001) • NGN OSS Service Interface (NOSI) (depicted as a lollipop): well defined grouping of related NGN OSS Operations and constant data which are necessary to deliver coherent business or system functionality • NGN OSS Service (depicted as an ellipse): behaviour or set of behaviours, made available through a profilable aggregation of NGN Service Interfaces, offered by one entity for use by others through their NGN OSS Service Interface Consumers; this usage is governed by a service description • NGN OSS Service Interface Consumer (NGN OSS SIC) (depicted as a crescent): a well defined grouping of related NGN OSS Operations and constant data which represent the user/consumer of an NGN OSS Service Interface.

6. A NOSI is • The fundamental unit of standardization. • An aggregation of functionality required for managing some coherent aspect of the NGN network or services. This functionality is provided through a set of related behaviour/functionality and is made publicly available for use by consumers of this service interface. An example is an Alarm Reporting service interface that offers the functionality supporting the NGN OSS Operations "getAlarmList" and "acknowledgeAlarms". • Comprised of a set of NGN OSS Operations which must be all present. • Equivalent to the SOA service interface concept.

7. Simplified TMN Functional Architecture Function Function Reference Point

8. Proposed NOSI Contents • What is being managed (Nouns) • Specific Information Object Classes could be imported from Resource Models (including 3GPP NRM) • How it is Managed (Verbs) • Specific Interface Object Classes (e.g. imported from 3GPP Interface IRPs)

9. Issues • How do we package NGN Resources • How many entities (nouns) per NOSI? • 1, few, many ? • 1 per NGN Entity or 1 per subsystem (e.g. RACS)? • How many actions per NOSI? • If we are to keep everything in a NOSI mandatory, we need small logical groupings

10. Co-operation with TMF • The NOSI is equivalent to the “Contract” in TeleManagement Forum • The TMF are developing Contract templates • The TMF have a list of 180 possible contracts • TISPAN WG8 are co-operating with the TMF in the development of the NOSI

11. Summary • TISPAN WG8 are committed to an SOA approach • ITU have also adopted this approach (see M.3060) • TMF have also adopted this approach (Contracts) • IT industry has adopted this approach • Within TISPAN WG8 NOSIs are still work in progress • Co-operation with TMF is ongoing