The document discusses next generation OSS/BSS architecture and tools. It describes the Telecom Management Network (TMN) reference model, which provided a standardized architecture for managing telecommunications networks. The TMN model includes functional, physical, informational, and logical layered architectures. It also discusses challenges with legacy OSS/BSS systems and introduces the NGOSS framework as a set of tools and lifecycle developed by the TM Forum to help design and implement next generation management systems, including the eTOM framework for defining business processes and the SID for defining shared information.

1. NGEN OSS/BSS
Architecture evolution
G r a z i o Pa n i c o
OSS/BSS Solution Delivery
grazio.panico@witech.it
1

2. Content
• Next Generation OSS/BSS
• Business Process Management (BPM)
• IP Multimedia Subsystem (IMS)
• Cloud Computing
2

3. Next GEN OSS/BSS
• Telecom Management Network
• Next Generation Operation Systems & Software
3

4. OSS & BSS: a definition
 Operation Support System
• suite of software designed specifically to manage a large network infrastructure,
connecting individual sub-systems
• supporting processes
• maintaining network inventory,
• Provisioning services
• configuring network components
• managing faults
 Business Support System
• complementary to OSS, typically refers to "business systems" dealing with customers
• supporting processes
• Order Management,
• Billing and Payments processing
• Customer care
• Sales support
• …
4

5. OSS & BSS: evolution history
2000
Next Generation
1990s OSS/BSS
TMN
Then come
computers
• Specialized Legacy
Applications
Before 1970 • Swivel Chair
• OSS activities were Integration
performed by
manual
administrative
processes
5

6. OSS/BSS: early needs
 Saving Investments
• For many operations, operational costs for network and service management are higher than
equipment costs
• Changing service and equipment needs within operational platforms are common practice
(competition)
 Competition
• Enable Time-to market
• Do More with Less
 Interoperability
 Integration
• Most as swivel chair integration
 Management
• Networks, Service and Business
6

7. TMN Reference Model
 (Hierarchical) Telecommunication Management Network
 Joint effort by ITU-T and ISO (from 1988 to 1996) - Recommendation M3010
 Objective
• The basic concept behind a TMN is to provide a organized architecture to achieve the
interconnection between various types of OS’s and/or telecommunications equipment for the
exchange of management information using an agreed architecture with standardized
interfaces including protocols and messages
Data Communcation
Network
Telecommunication
Other TMN Network
7

8. TMN Architecture
 Functional architecture
• Functional modules
Architecture
• Reference points between modules
 Physical architecture
• Physical Building Blocks Funzional Physical Informational Logical Layerd
• Physical interfaces between blocks
 Informational architecture
• Information exchange between entities
• Object oriented
 Logical Leyered architecture
• Responsabilities
8

9. TMN Architecture
 Functional architecture
• Role that a function performs
• OSF, NEF, MF, WSF, QAF
• Management function that is
performed
• Falt, Configuration, Accounting, Performance,
Security
• Reference points between modules
• Interface
• OSF (Operations System Functions): NMS, testing, accounting, trouble No TMN system
tracking
• NEF (Network Element Functions): NM agent, MIB, collision rate
• MF (Mediation Function): Operations on the information between network
elements; e.g. filtering, protocol conversion. MF can be shared between
multiple OSSs; e.g. RMON
• WSF (Workstation Functions): Human-TMN activities interface; e.g., GUI
9
• QAF (Adapter Functions): to accommodate non-TMN entities; e.g. proxy

10. TMN Architecture
 Informational architecture
• In order to allow effective definition of managed resources, TMN makes use of OSI Systems
Management principles and is based on an object-oriented paradigm.
• Management systems exchange information modeled in terms of managed objects (MO)
• Two type of communication services: interactive (rpc) and file oriented (ftp):
Managed object are identified by
• the attributes visible at its boundary
• the management operations which may be applied to it
• The behavior exhibited by it in response to management
operations or in reaction to other types of stimuli (e.g.,
threshold crossing)
• The notifications emitted by it
10

11. TMN Architecture
 Phisical architecture
• Identifies physical build block
• Define how function blocks and reference point can be implemented (maps)
• OS: Operations Systems
• MD: Mediation Device
• QA: Q-Adapter
• NE: Network Elements
• DCN: Data Communications Network
• WS: Work Station 11

12. TMN Architecture
 Logical Layered architecture
• The most valuable idea of TMN model
• Hierarchy of management responsibilities
• Layers of management functionality
• To deal with the management complexity
12

13. TMN Architecture
 Logical Layered architecture
• The most valuable idea of TMN model
• Hierarchy of management responsibilities
• Layers of management functionality
• To deal with the management complexity
Element Management Layer
• Function of NE are managed by OPFs in EML
• EML deal with vendor specific functions
• Hide NE function to NML
Example
• Detection of equipment errors,
• Measuring the temperature of equipment,
• Measuring the resources that are being used, like CPU-
time, buffer space, queue length etc.,
• Updating firmware
13

14. TMN Architecture
 Logical Layered architecture
• The most valuable idea of TMN model
• Hierarchy of management responsibilities
• Layers of management functionality
• To deal with the management complexity
Network Management Layer
• manages interaction between equipments
• is vendor independent
• provision, terminate, modify network capabilities
• Provide to SML informatio about performance, usage,
availability, etc.
Example
• creation of the complete network view,
• monitoring of link utilization,
• optimizing network performance, and
• detection of faults 14

15. TMN Architecture
 Logical Layered architecture
• The most valuable idea of TMN model
• Hierarchy of management responsibilities
• Layers of management functionality
• To deal with the management complexity
Service Management Layer
• Responsible for aspect facing directly with with
Customer or other Providers
Example
• Quality of Service (delay, loss, etc.),
• Accounting,
• Addition and removal of users
The most valuable contribute to other framework
15

16. TMN Architecture
 Logical Layered architecture
• The most valuable idea of TMN model
• Hierarchy of management responsibilities
• Layers of management functionality
• To deal with the management complexity
Business Management Layer
• Responsible for management of whole Enterprise
• Define Policies and Strategies to manage services
(and networks)
• Deal with Legislation, Economics factors (pricings,
competitors, etc.)
16

17. TMN Architecture: an example
17

18. TMN strengths/weakness
 Strengths
• TMN is a very suitable framework for telecommunications management purpose since:
• It identifies different abstraction levels
• It is component based
• It forces a structured approach when faces with the problem of network and service management
• It is a widely adopted standard, which ensures that everyone speaks the same language
• Hight Interoperability, by standardizing
• Protcols, Information models, Services
• Scalability
• using the power of OSI systems management and the associated object approach
• Security, which is essential at Element Management Layer (EML)
 Weakness
• Implementation of TMN isn’t so easy
• TMN functional architecture does not map very well to service management. It originates from the
bottom layers of the pyramid
• TMN is particularly strong at the bottom layers 18

19. Next GEN OSS/BSS
• Telecom Management Network
• Next Generation Operation Systems & Software
19

20. OSS/BSS: new challenges
20

21. OSS/BSS: new challenges
 Pressure
• More productivity
 No time for new systems
• More Customers and Services
 System overloaded
• More authomation
 Business Process Management & re-
ingineering
21

22. OSS/BSS: new challenges
 Pressure
• More functionalities
• Tailored services
 Systems become patchwork of
functionalities
22

23. OSS/BSS: new challenges
 Pressure
• Short time-to market
 No time to build new infrastructure,
simply adapting old systems to new
requirement
23

24. OSS/BSS: new challenges
 Pressure
• New network technology are quickly
introduced
• Each has its own management
system
 More complexity to manage
 Configuration, Activation, … become
a challenge
24

25. OSS/BSS: new challenges
 Pressure
• New Technology are available
 Need for a new approach
25

26. OSS/BSS: system health
 Legacy OSS systems
• Proliferation
• High cost to maintain and evolve
• No clear scope
• No open interface
 No integration infrastructure
• Point to point integration
• spaghetti integration
• Swivel chain Integration
26

27. OSS/BSS: system health
 Silos of OSS end BSS
• New Technology  New OSS Silos
• New Service  New OSS Silos
 High manpower costs
• because of a lack of automated process flow-
through
• Duplication of Systems, Functions, Data
• Much more maintenance cost
It is much more convenient to build an entire set of
OSS system instead of integrating or extend existing
ones!!
27

28. OSS/BSS: system health
 High manpower costs
• because of a lack of automated process flow-through
 Poor time-to-revenue
• because of have rigid and inflexible business processes
 Weak customer service
• because of poorly integrated & systems with inaccurate data
 Slow growth
• because processes and systems can’t scale
 Slow new service introduction
• because of high risks & costs to make system changes
 Poor economies of scale
• because of using hundreds of suppliers
28

29. OSS/BSS: process automation landscape
change
integration Limited by
complexity of
changing systems
to keep up with
# application Integration of process
multiple enhancements
Applications
Hundreds or to achieve Changes not
# process thousands of automation affordable
discrete of a single
Thousands
OSS/BSS process Process
of
discrete
applications Automation is
processes not optimized
29

30. Flexible, Automated Business Processes
 Optimizing processes requires a multi- TMF Views
step approach
• Defining and engineering processes
• Defining information in a common fashion
• Defining systems to implement processes
• Defining the interfaces between systems
• Defining the way the systems plug together
(architecture)
 The tools to achieve these steps are provided by NGOSS
from end-to-end
30

31. Who Needs a New Way to Do OSS?
 Service Providers
• Operational agility
• Cost effective OSS/BSS implementations
• Long term direction for IT strategy
• IT systems that support rapidly evolving integrated services
 OSS Software Vendors
• Affordable development costs
• Supportable Software
• Fitting into the OSS/BSS puzzle
 Systems Integrators
• Predictable, repeatable, scalable, implementation projects
• Broader ISV portfolio without steep learning curve
31

32. NGOSS framework: Tools and Lifecycle
 New Generation Operations Systems and Software
 TM Forum program since 2000
• International non-profit Association
• Organize, guide, design and develop
Next Generation Management Systems
32

33. NGOSS framework: Tools and Lifecycle
The way (Lifecycle)
Business View
• Identification of Business Needs
(Business Requirement)
• Artifacts:
• eTOM (Process)
• SID (Information)
33

34. NGOSS framework: Tools and Lifecycle
The way (Lifecycle)
Business View
System View
• Modeling the system solution
• System as “grey box”
• Interoperability
• COTS capabilities and policy
• Process flow between systems
• Artifacts:
• SID (Information)
• TNA (Distributed Architecture)
34

35. NGOSS framework: Tools and Lifecycle
The way (Lifecycle)
Business View
System View
Implementation view
• Validating the proposed solution
• COTS mapping
• Thecnology mapping
• Pilot
• Artifacts:
• Proposed solution
• Proposed architecture
35

36. NGOSS framework: Tools and Lifecycle
The way (Lifecycle)
Business View
System View
Implementation view
Deployment View
• Realizing the solution
36

37. NGOSS framework: Tools and Lifecycle
eTOM (Tool)
 Business Process Framework for Enterprise
process
 Common language between Service Providers
and their suppliers about what problem they are
trying to solve
• Define classification system for business
processes
• Inventory how processes are done today
• Design how SP wants processes to work
ITU Standad!
Problems to solve
• Define and prioritize problems in terms of business processes
• Where are the lines drawn around products? 37
37

38. eTOM: the big picture
Customer
Strategy, Infrastructure & Product Operations
Strategy &
Commit
Infrastructure
Lifecycle
Product
Lifecycle
Operations
Support and
Fulfillment Assurance Billing
Management Management Readiness
Marketing & Offer Management Customer Relationship Management
Service Development & Management Service Management & Operations
Resource Development and Management Resource Management & Operations
(Application, Computing and Network) (Application, Computing and Network)
Supply Chain Development and Management Supplier/Partner Relationship Management
Enterprise Strategic & Brand Management, Stakeholder & External Disaster Recovery,
Management Enterprise Market Research & Relations Management Security & Fraud
Planning Advertising Management
Research &
Financial & Asset Human Resources Development, Enterprise Quality
Management Management Technology Management, Process & IT
Acquisition Planning & Architecture 38

39. eTOM: Ops horizontal Level 1 processes
eTOM (Tool) – e Telecom Operation Map
 Customer Management
• Acquisition
• Up selling
 Service Management
• Service Configuration
• Service Assurance
 Resource Management
• Resource provisioning
 Partner/Supplier Management
• Supply chain processes
39

40. eTOM: Ops vertical Level 1 processes
eTOM (Tool)
 Fulfillment (or provisioning)
• Customer Need into Solution
 Assurance
• Network monitoring
• SLA management
• Trouble Ticketing
• Problem handling
 Billing
• Rating
• Billing
• Usage collections
 Operation Support & Readiness 40

41. eTOM: Ops horizontal Level 2 processes
41

42. eTOM: Ops horizontal Level 3 processes
42

43. eTOM: process flow: Ordering (Fulfillment)
43

44. NGOSS framework: Tools and Lifecycle
SID(Tool) – Shared Information Data
 Common language of NGOSS-based
OSS/BSS systems
 A reference manual defining the thousands
of pieces of information needed to map out
business processes
44
44

45. SID: an example - Customer
Customer is one of the SID
“things” called “entities”
“Entities” under customer
45
45

46. SID: example of bad Information modeling
Billing CRM
Customer: Customer:
1. Last Name, First Name 1. First name, middle init, last name
2. Customer ID number 2. Street Address, Zip code
3. Street Address, Zip code 3 Last 4 digits SSN
4. Social Security number 4. Customer Account number
Translator Translator
Trouble Ticketing Service Ordering
Translator Translator
Customer: Customer:
1. Customer ID number 1. Customer ID number
2. Social Security number 2. Last name, first name, middle
3. First name, last name init
4. Street Address, Zip code 3. Zip code, street address
46

47. SID: applying NGOS principle
Billing CRM
Customer: Customer:
1. Last Name, First Name 1. Last Name, First Name
2. Customer ID number 2. Customer ID number
3. Street Address, Zip code 3. Street Address, Zip code
4. Social Security number 4. Social Security number
Customer:
Trouble Ticketing
1. Last Name, First Name Service Ordering
2. Customer ID number
3. Street Address, Zip code
Customer: 4. Social Security number
1. Last Name, First Name Customer:
2. Customer ID number 1. Last Name, First Name
3. Street Address, Zip code 2. Customer ID number
4. Social Security number 3. Street Address, Zip code
4. Social Security number
47

48. The SID Framework
48

49. NGOSS framework: Tools and Lifecycle
TNA(Tool) – Technology Neutral Architecture
 Guidelines support the analysis, design,
implementation and deployment of
NGOSS-based open distributed
computing solutions
 Defines contracts, the fundamental unit of
interoperability within an NGOSS solution
49

50. TNA: principles
 The NGOSS supports the following TNA
requirements
1. An NGOSS system must have re-useable
software entities that offer their services via open,
well-defined interfaces known as contracts.
2. An NGOSS system must have all its external
dependencies explicitly defined.
3. An NGOSS system must be characterized by a
separation of the services offered by the
constituent components from the software that
automates business processes across the
components.
4. An NGOSS system must support data
stewardship. For each datum, there is a steward
that controls access and modification of the datum.
5. An NGOSS system must support a common
communication mechanism like Java Message
Service (JMS).
50

51. Traditional OSS/BSS Architecture
 Complex systems (overloaded)
 Data + Process
 Tightly coupled with each other (pair-wide
interfaces)
 No communication BUS
 No data ownership
A small change in one system typically would affect
all the systems which interfaced with the system
where the change was made.
51

52. TNA OSS/BSS Architecture
WiTech BPM.-enabled architecture Open Source Ready!
 Communication Bus (ESB) Cloud Ready!
 Application Services
 Framework Services
 BPMS (SOA)
 Portals
52

53. NGOSS framework: Tools and Lifecycle
Compliance
 Tests for Compliance to eTOM, SID and
Architecture
 Can test against parts or whole NGOSS
elements
 Tests products and solutions
53

54. NGOSS Compliance Testing
 Focused on defining what is
testable in NGOSS and how to
test it
 Working on defining an industry
testing commercial strategy
54
54

55. NGOSS Sample Applications
• Business process redesign
• Map and analyze business processes to improve efficiency
• Component development
• Software engineering to create a new OSS component
• Component integration
• Integrating disparate OSS components
• RFP process
• Design and specify new OSS solutions using NGOSS
• Create a new service
• Modify OSS/BSS to add or change service parameters
55
55

56. Who’s backing NGOSS?
56

57. Thank you for your interest!
For more information, please visit our web site, call us or WiTech Spa
send us an e-mail! Via Giuntini 25
56023 Cascina Loc. Navacchio (PISA)
Italy
www.witech.it
Grazio Panico
NGOSS solution delivery manager Phone: +39 050 775 056
Fax: +39 050 75 47 22
grazio.panico@witech.it Mobile: +39 347 516 44 01
E-mail: info@witech.it
57