Operations Support System Functions and Components

An operations support system (OSS) is a crucial tool for telecommunications companies, helping them manage their networks and services efficiently.

OSS functions include network management, service management, and resource management, which are all essential for providing high-quality services to customers.

Network management involves monitoring and controlling network devices, such as routers and switches, to ensure they are functioning properly.

Service management, on the other hand, focuses on managing the services offered by the telecommunications company, including provisioning, activation, and deactivation.

Resource management is responsible for allocating and managing resources, such as bandwidth and network capacity.

The key components of an OSS include a service management system, network management system, and a data management system.

Check this out: Why Database Management System Is Important

An operational support system (OSS) is the backbone of any telecom service provider, allowing them to create, organize, provision, maintain, and manage network services and orders.

OSS is a collection of systems that support the day-to-day operations of a telecom service provider, including order administration, service control, network management, and invoicing.

For another approach, see: Azure Service Operator

These systems are implemented to reduce operating costs while optimizing efficiency, output, and availability.

OSS ensures accurate operations for set up, configuration, and testing, inventory and allocation, maintenance, defect detection, and resolution, and security, fraud data compilation, and detection.

Here are some key functions of OSS:

OSS helps telcos oversee technical and operations activities, supports network management functions and infrastructure, and allows organizations to monitor, analyze, and automate operations like network performance and fault management.

It enables telcos to analyze and control all network connections and components, including computers, servers, and routers.

OSS includes several computer programs telecom providers use to analyze, manage, and monitor their networks, including hardware and software tools like servers, routers, and computers.

By using OSS, telecom companies can manage all of their activities and operations from a centralized location, improving efficiency, reducing costs, and delivering a better customer experience.

Take a look at this: Azure Operations Management Suite

Before about 1970, many OSS activities were performed by manual administrative processes, but computers soon replaced much of this activity. The telephone companies created computer systems that automated OSS activities, driving the development of the Unix operating system and the C programming language.

The Bell System purchased PDP-11 computers for OSS applications, which included systems like AMATPS, CSOBS, and EADAS. These systems were initially not linked to each other and often required manual intervention, leading to inefficiencies like "swivel chair integration".

OSS integration aimed to automate interfaces between applications, and cheap and simple integration remains a major goal of telecom companies. The ITU Telecommunication Standardization Sector (ITU-T) defined a 4-layer model of the Telecommunications Management Network (TMN) in the 1990s, which included levels for Business Management, Service Management, Network Management, and Element Management.

The TMN model was later adopted by the ISO, which added a Functional model for the technology base of the TMN standards. This model included Fault, Configuration, Accounting, Performance, and Security (FCAPS) as key elements of network management.

If this caught your attention, see: Low Voltage Systems

Before 1970, many OSS activities were performed by manual administrative processes, which were time-consuming and prone to errors.

The telephone companies created computer systems to automate these activities, driving the development of the Unix operating system and the C programming language.

One of the first OSS systems was AMATPS, which was used by the Bell System for various applications.

OSS systems from this era are described in the Bell System Technical Journal, Bell Labs Record, and Telcordia Technologies (now part of Ericsson) SR-2275.

These early OSS systems were often not linked to each other and required manual intervention, leading to inefficiencies like "swivel chair integration".

The focus shifted to creating automated interfaces between OSS applications, known as OSS integration, to improve efficiency.

Cheap and simple OSS integration remains a major goal of most telecom companies today.

A fresh viewpoint: Wireless Video Security Cameras

The TM Forum's TAM is a widely used framework for understanding the functional building blocks of OSS/BSS. It's a comprehensive analysis of around 75 main functional building blocks.

The TM Forum's TAM is a simplified view of the full TAM, which is represented by the shaded boxes in the background. The simplified TAM is represented by the blue boxes in the foreground.

The TM Forum's TAM is organized into several key functional blocks, including Lead Generation & Marketing, Channel & Sales Management, Product Management, Customer Management, and many others. These functional blocks are grouped into high-level workflows such as Fulfilment, Assurance, Design & Planning, and Billing / Revenue.

Here's a breakdown of the key functional blocks of OSS and BSS, as described in the Simplified TAM:

The TM Forum's TAM is a useful tool for understanding the complexities of OSS/BSS, but it's worth noting that it doesn't provide a complete picture of how these systems should be made interoperable.

Frameworx models are a key part of the TM Forum's NGOSS work, providing a framework for building reference models to support a business stakeholder view on process, information, and application interaction. The main reference models of Frameworx include an application model (the Telecom Applications Map), a process model (the enhanced Telecom Operation Map), an information model (the Shared Information/Data model), and a system integration framework (the Technology Neutral Architecture).

For your interest: Are the Most Important Part of an Information System

The TM Forum describes Frameworx as an architecture that is loosely coupled, distributed, and component-based. The components interact through a common communications vehicle, using an information exchange infrastructure such as EAI, Web Services, or EJB. The behavior can be controlled through the use of process management and/or policy management to orchestrate the functionality provided by the services offered by the components.

The four main reference models of Frameworx are:

The Telecommunications Management Network (TMN) is a key concept in the field of telecommunications management. It was developed by the ITU-T in 1988 to bring standardization to OSS integration.

The TMN Logical Model is presented in Recommendation M.3010 and is commonly referenced as the TMN pyramid. It identifies four logical layers of network management: Business Management Layer (BML), Service Management Layer (SML), Network Management Layer (NML), and Element Management Layer (EML).

The TMN pyramid provides a framework for understanding the different layers of network management. It's like a pyramid, with the Business Management Layer at the top and the Element Management Layer at the bottom.

The Business Management Layer (BML) represents the functionality relating to strategic business planning, such as trending, quality, and billing. It provides the basis for goal-setting and budgeting.

The Service Management Layer (SML) is responsible for defining the services offered by carriers, including definition, administration, and charging. It provides the interface between a customer's services and the network.

The Network Management Layer (NML) provides the overall management view of the network as a sum of component parts. It's responsible for end-to-end supervision, configuration, and control of the network.

The Element Management Layer (EML) provides definition and coordination of a collection of network devices, including consolidation of alarm management, backup, logging, and maintenance of the systems that support the network devices.

The TMN also identifies a fifth layer, the Network Element Layer (NEL), which represents the network devices themselves that customers' services traverse.

Here are the Management Functional Areas presented in ITU/T Recommendation M.3400:

Frameworx models are the foundation of the TM Forum's architecture, providing a structured approach to building and managing OSS/BSS systems. The main reference models of Frameworx are the Information Framework, Business Process Framework, Application Framework, Technology Neutral Architecture, and lifecycle model.

The Information Framework, also known as the Shared Information/Data model (SID), defines the essential entities, relationships, and attributes of data objects prevalent in telecommunications applications and databases. This framework provides a common language for use by OSS developers and integrators.

The Business Process Framework, also known as the enhanced Telecom Operation Map (eTOM), aims to provide a common language and catalogue of business processes used in telecommunications environments. This level of standardization aims to simplify the lines of communication between service providers and associated systems integrators.

The Application Framework, also known as the Telecom Applications Map (TAM), provides a modular framework of management functional blocks. This helps to provide greater consistency and compatibility between the product suites of different vendors.

The Technology Neutral Architecture (TNA) provides architectural standardization while remaining technology neutral, including common interfaces, mechanisms, and policies. Integration is also commonly known as the TM Forum Integration Program (TIP).

Here is a summary of the main reference models of Frameworx:

Registration Authorities play a crucial role in telecommunications networks. The IEEE acts as the registration authority for many unique identifiers used in these networks.

IEEE maintains a number of different identifiers, including OIDs used by SNMP. Tutorials for these registers can be found here.

Operational support systems (OSS) are crucial for managing large-scale networks, and they perform several key functions. These functions include providing backend support for mobile networks, enabling scalability of networks, and paving the way for automated network management.

OSS supports all operational activities within a mobile network, utilizing specialized hardware and software to monitor, analyze, develop, and manage the operational activities inside a network. This includes identifying and alerting operators of critical network issues that demand urgent attention.

Here are some of the key benefits of OSS:

Data Insights are crucial for making informed decisions in the telecom industry. With the ability to collect vast amounts of data, OSS/BSS tools can provide valuable insights into network performance, customer behavior, and service quality.

The TM Forum has compiled GB988, which contains over 2,600 commonly used metrics that can be used to measure and analyze network performance. This resource has been instrumental in helping operators derive actionable insights from their data.

OSS/BSS tools can collect data on network functionality, customer interactions, and service performance, providing a comprehensive view of the network. By analyzing this data, operators can identify trends, detect issues, and make data-driven decisions.

The sheer volume of data collected by OSS/BSS tools can be overwhelming, but with the right tools and metrics, operators can extract valuable insights and improve their decision-making processes. By using data to drive their decisions, operators can improve network efficiency, reduce downtime, and enhance the overall user experience.

Operational support systems (OSS) perform several key functions for CSPs and other organizations/teams that manage large-scale networks. These functions enable the efficient management and monitoring of networks, services, and customers.

All the information needed to offer a service is input into the service provider's systems via the procurement software. This includes services such as plain old telephone service (POTS) lines, integrated services digital network (ISDN), and asynchronous digital subscriber line (ADSL), among others.

OSS supports all operational activities within a mobile network, utilizing specialized hardware and software to monitor, analyze, develop, and manage the operational activities inside a network.

OSS enables scalability of networks and drives digital transformation by providing sophisticated analytics and visualization tools to identify and diagnose issues swiftly and easily.

Automation is another significant advantage of OSS in larger networks, which minimizes the workload of network administrators and increases the network's efficiency.

OSS extends far beyond service activation, with network management and troubleshooting being indispensable aspects of any OSS infrastructure. These systems track traffic moving through a network and capture performance statistics.

Here are the key functions of OSS:

These functions work together to provide a comprehensive management of telecommunications services and operations, supporting everything from the initial customer interaction and service orders to the backend management of the network and associated data.

The components of an operations support system (OSS) are crucial for its functionality. The TM Forum ODA Component Library aims to standardize cloud-native OSS/BSS building blocks.

The FCAPS framework, defined by the International Organization for Standardization (ISO), breaks down the OSS into five key components: Fault, Configuration, Accounting, Performance, and Security.

Here's a breakdown of these components:

TM Forum ODA Components are a crucial part of the TM Forum's efforts to standardize cloud-native OSS/BSS building blocks. This attempt to bring standardization to the industry has been a game-changer for many organizations.

The TM Forum ODA Component Library is a key resource for anyone looking to understand and implement these standards. It cross-references with Open APIs to fast-track deployment patterns, making it a valuable tool for anyone looking to streamline their operations.

One of the key benefits of the TM Forum ODA Components is that they are designed to be flexible and adaptable to different use cases. For example, they can be used to support large transformation programs aiming to decouple systems.

Here are some of the key TM Forum ODA Components:

These components are designed to work together seamlessly, providing a robust and scalable framework for managing complex networks and services.

Inventory storage is crucial for handling orders efficiently. The inventory management system must be queried to determine if the requested service is available.

Does the necessary equipment exist? The OSS validates this information using the inventory. Fresh machinery should be installed if it doesn't.

The OSS checks if high-capacity facility circuits, which offer backbone transmission, are already allotted. They require configuration if not.

A customer order for a new phone service is a great example of how an Operations Support System (OSS) and a Business Support System (BSS) work together.

The BSS receives the order and creates a new customer account, which is a crucial step in the process.

The BSS then sends the order to the OSS, which provisions the new service on the network. This is where the OSS kicks in to make sure the service is set up correctly.

A unique perspective: Emailing Ebay Customer Support

The OSS verifies that the new service is working properly, which is a critical check to ensure the customer gets the service they paid for.

The OSS and BSS work together seamlessly to get the job done, with the BSS sending a confirmation to the customer once the OSS has verified the service is working.

Here's a step-by-step breakdown of how this process works:

Choosing and implementing OSS and BSS solutions can be a daunting task, but with the right approach, you can simplify telecom workflows and achieve operational efficiencies. Simplifying telecom workflows is crucial to operational efficiency.

To start, you need to gain access to customer and operational insights that help you monitor business performance, predict outcomes, and make informed decisions to fuel growth. This can be achieved through telecommunications business intelligence.

A data-driven culture is essential in today's business landscape, and OSS and BSS solutions can help you create one. By leveraging industry-tailored cloud solutions, you can build a hyper-connected business.

Additional reading: Network Solutions Dns Records

Here are some key considerations to keep in mind when choosing and implementing OSS and BSS solutions:

By considering these factors and choosing the right OSS and BSS solutions, you can set your business up for success and prepare for the future.

Standards Compliance is crucial in the OSS industry, and one organization that takes it seriously is the TM Forum. They provide thorough testing and certification of a vendor's product against their recommendations and principles. This ensures that the product meets the required standards.

TM Forum's certification process is more rigorous than just adhering to recommendations, making it a trusted benchmark in the industry. A list of certified products can be found on the TM Forum website (www.tmforum.org).

In contrast, other standards like 3GPP and ECOMP/ONAP/LFN are simply recommendations that can be followed in an ad-hoc manner. This means that vendors may claim to be compliant, but it's not always a guarantee.

TM Forum also offers Frameworx Implementation Conformance Assessment, which verifies a service provider's internal business processes and data model. This ensures that the service provider's systems are aligned with the TM Forum's standards.

Here's a comparison of the different types of compliance:

This highlights the importance of choosing the right standards and compliance processes for your OSS implementation. By selecting the right standards, you can ensure that your systems are aligned with industry best practices and meet the required level of compliance.

Transformation is a complex process that requires careful planning and execution. It involves modernizing OSS and/or BSS systems, which can be a daunting task due to their intricate nature and decades-long history.

One of the biggest challenges in OSS transformation is integration with legacy systems, which can lead to complexities and potential service disruptions if not managed carefully. This is because legacy systems may not be designed to work together seamlessly.

Take a look at this: Sim Not Supported Iphone X

Managing multi-vendor environments is another significant challenge in OSS transformation. Telecom companies often operate within ecosystems with diverse systems, each with its own protocols and interfaces, making interoperability a major hurdle.

Updating OSS/BSS is a key element of enabling digital transformation, and legacy systems may lack the flexibility and automation capabilities required to support new technologies and services. This can hinder innovation and responsiveness to market demands.

Here are the key challenges in OSS/BSS transformation:

These challenges highlight the importance of careful planning and execution in OSS transformation. By understanding these challenges, telecom companies can develop effective strategies to overcome them and achieve successful transformation.

Operations support systems (OSS) have a complex architecture that's been shaped by various standards and models over the years. The ITU Telecommunication Standardization Sector (ITU-T) defined a 4-layer model of Telecommunications Management Network (TMN) applicable within an OSS: Business Management Level (BML), Service Management Level (SML), Network Management Level (NML), and Element Management Level (EML).

The TMN model was later adopted by the ISO using the FCAPS model, which stands for Fault, Configuration, Accounting, Performance, and Security. This model was originally conceived for IT enterprise networks but was adapted for use in public networks run by telecommunication service providers.

The TM Forum's Frameworx model is another key architecture for OSS, which consists of four main components: an information model (Shared Information/Data model, or SID), a process model (enhanced Telecom Operation Map, or eTOM), an application model (Telecom Applications Map), and a lifecycle model.

Frameworx is described as "loosely coupled", distributed, and component-based, with components interacting through a common communications vehicle. The behavior of these components can be controlled through process management and/or policy management.

Here are some common architecture models for an OSS/BSS stack:

These models provide a foundation for building, buying, or blending OSS/BSS components, and can help guide your decision-making process when transforming your operations support system.

Cloud Native and Orchestration is a game-changer for Operations Support Systems (OSS). It's a shift to more cloud-native application technology practices, allowing for immense scalability and elasticity to cope with varying demands.

The traditional 3-tier monolithic OSS stack is being replaced by a cloud-native, distributed, and modular architecture. This model offers numerous benefits, including business and workforce agility, speed to market, and cost optimisation.

Orchestration is a key enabler of on-demand change, allowing automation of the underlying infrastructure and resources. Some service changes can be fully automatable and done rapidly in software, while others may still require human intervention.

Here are some key characteristics of cloud-native OSS/BSS in cloud-hosted environments:

Cloud Native OSS/BSS is becoming the new standard in the industry. This shift is driven by the need for business and workforce agility, speed to market, and cost optimization.

The traditional 3-tier monolithic OSS/BSS stack is being replaced by a cloud-native, distributed, and modular architecture. This new model offers numerous benefits, including immense scalability, inherent resilience, and speed to innovate.

On a similar theme: Cloud Sql Supported Databases

Cloud-native OSS/BSS is also being driven by the need for on-demand change and automation of underlying infrastructure and resources. Orchestration plays a key role in this process, allowing for the automation of infrastructure and resources.

Some of the key characteristics of cloud-native OSS/BSS include containerization, managed services, and elastic scaling. This approach is particularly suited to organizations with a strong software development capability and a need for rapid deployment and scalability.

Here are some key use cases for cloud-native OSS/BSS:

By adopting cloud-native OSS/BSS, organizations can take advantage of the numerous benefits offered by this approach, including improved scalability, resilience, and innovation speed.

AIOps solutions are enhancing network management by integrating AI, ML, and big data analytics. These frameworks automate network monitoring, preventative maintenance, incident resolution, and troubleshooting, freeing up operator time to focus on incident resolution and fix.

AIOps is proving to be successful in automating some steps of incident management. This allows operators to focus on more complex issues.

The aim for most carriers is to use physical infrastructure and programmable networks to ensure that changes can be done in software almost instantaneously.