Blog Blog

OSSera Big Data Analytics & Reporting Tool (DART)

OSSera DART (Data Analytics & Reporting Tool) is a Big Data Analytics Platform which is used to examine large amounts of data of a variety of types to uncover hidden patterns, unknown correlations, and other useful information.  This timely product can provide a useful tool for communication service providers (CSPs) to solve their problems and challenges they often face daily, especially in the 4G/LTE era, such as:

·         How to analyze volumes of data in near real time that eclipse the capabilities of legacy infrastructures?

·         How to utilize near real time network and customer data to identify network and or customer problems and troubleshoot the problems?

·         How to determine behaviors that may ultimately create either customer or product churn?

·         How to understand customer experiences at a transactional level and determine investment criteria?

·         How to optimize offerings and portfolio in a highly competitive market targeting high value, high margin infrastructure and applications based on empirical data?


These are all Big Data related problems.  It is well understood that Big Data is an opportunity for CSPs to create the intelligence for operating network more efficiently to analyze the success of the services that they are offering, and to create a better personal experience for their customers.  Decision makers at CSPs are eager to exploit the large amount of information to achieve better business decision, and to provide analytic end-to-end solutions based on the data available in their IT and network infrastructure. 

OSSera DART is just such a useful tool that enables CSPs to analyze and make informed decision in near real time with unparalleled efficiency, performance, and scalability.  OSSera DART can store, access, analyze, and monetize the vast amounts of CSP customer and network data without sacrificing time, scale, or detail.  Thus it can help to deliver significantly higher customer satisfaction, retention, and profitability.  OSSera DART carries out this by collecting raw mobile user data, processing data, aggregating data, storing data, calculating data, and displaying results.  It also provides many tools so users of the software can manage KPI formulation setting, threshold value defining, threshold cross alarm (TCA) generation, and results presentation and displaying. 

OSSera DART includes the following components:

·           Client;

·           Big Data platform server;

·           Big Data aggregation server;

·           Big Data processing server.


The architecture for the OSSera DART system is as below:




An example of OSSera DART’s application is to analyze and report xDR data generated from 4G/LTE network.  The xDR data processing server provides the function as below:

·           Collecting the xDR raw data;

·           Transforming xDR raw data to data records;

·           Aggregating local data records and passing to data aggregation server;

·           KPI calculation and sending results to platform server for threshold management.


The relationships among functional components in the xDR processing server can be described as in the below figure:



The aggregation server provides the function of aggregating the processed xDR data from the xDR processing server then saving the result to the database for later use of producing table generation.



The platform server provides the CRUD function for KPI, threshold, report and authorization and the deployment function.  For the report without xDR raw data, it directly returns the data from database to the client.  For the report with xDR raw data, it sends the query condition to the raw data, and then returns the result and the calculation and aggregation result to the client.  The relationships among the functional components in the platform server can be depicted in the below figure:




The first project applying OSSera DART has accomplished User Acceptance Test (UAT) in an SEA operator in April 2014.  

OSSera Delivers Resource/Service Activation System

OSSera Delivers Resource/ServiceActivation System

Resource Activation and Service Activation Management are important components in Resource and Service Management Domain of Operations Support System (OSS).  Resource activation applications interpret the needs of a fulfillment request into specific control commands for a network or sub-network often handling proprietary messaging with individual resource elements, whereas service activation application is responsible for activation of specific services based on the specific service configuration.

OSSera has developed Service Activation System (OSSera SA) under the general guidance of TMF Frameworx to provide quick FFTH connections and services through efficient and effective tools that have the following functionalities:  

·       Update the resource instance to perform the activation or deactivation

·       Update the resource to activate Billing data collection

·       Notify Resource Provision / Control of the activation status

·       Update Resource Inventory with the resource status information

·       Queued / scheduled activation requests

·       Configuration validation and rollback

·       Manage dependencies within, and across network elements through rules

·       Multi-vendor and multi-technology activation

·       Multiple NE activation coordination

·       Confirm / identify available resources

  • Provide notifications on successful activation; in cases of exceptions send fallouts to Service Order Orchestration and manage rollbacks activities (if applicable)

Two major tools of OSSera SA are the flow designer and flow executor.  The flow designer is for user to design service activation process flow.  This involves the processes of understanding the network technology, network topology, device (interface and command set), EMS functions (interface and command set), and the service provided to customer.  For each service activation process, identify the steps to provision the network (devices) and commit the resource to activate the service.  Each step includes the processes to identify the devices (or EMS) to be involved and corresponding interface and command set to be used to provision the device then commit the change of configuration in device. It also involves the process to understand and carry out the roll back steps when failure happens.  With all these processes done and knowledge collected, the service activate process flow can be designed using the flow designer.  The designed flow then will be debugged to ensure each step is correctly implemented in the debugger tool of OSSera flow designer. When the service activation flow is verified, it is ready to be executed in production environment by operators. The flow designer also comes with tools to design flow execution reports.  Flow execution details can be designed into reports so that management team and technical team can look at the reports to help them to make business and technical decisions.

The flow executor is another set of tools for operators to carry out the service activation process.  The processes include find the proper service activation flow, providing correct information then monitor the flow execution.  In the case of abnormality, service activation flow can be manually interrupted or completely stopped. The flow executer also comes with report viewer so that user can view past flow execution. 

The following diagram shows the software architecture of OSSera SA:


OSSera SA is mainly consisted of the following components:

·           SAServer – SA server is the back-end process for service activation.  It takes order from user, maps the order a circuit then calls the activation flow to carry out the provisioning process.  If the service activation process fails in flow execution, it will roll back any changes.  If the service activation process succeeds, it will update inventory to reflect the status of devices in service.

·           CORBA – The communication technology used among OSSera systems.

·           Flow Engine – The engine to execute process flow.  It is choreographs works done inside the server (OSSera program) as well as orchestrate calls to external system or command by using OS utilities or 3rd party API. 

·           Report Viewer – The graphic interface to view flow execution reports.

·           Object Viewer – The GUI component for operator to view MO (managed object) in graphical view, such as network or service topology view.

·           MO View – The tree view to see and edit MO attributes as well as relationships to other objects.

·           User Management View – A set of GUI components to view, create, update and delete user and related information such as authentication and authorization.



OSSera SA can be deployed in the form of primary-secondary (see diagram below) or symmetric distribution.

OSSera is implementing OSS project in Asia

OSSera won the phase-I OSS project from one of the new Fiber Network Operators in Asia in 2012. Currently OSSera is implementing its 4 products at the Operator, including Inventory Management, Resource/Service Activation, Fault Management, and Performance Management.  The oeprator is expected to provide FTTH services to its customers in Spring 2014.

OSSera Delivers Resource Inventory Management System

Resource Inventory Management is an important component in Resource Management Domain of Operations Support System (OSS). Resource Inventory applications manage information of all resources used to implement services and products. This application area is typically linked to various element management systems (EMS) (i.e. building inventory for actual server, applications, network and resource assets) and resource inventory database systems.

OSSera Inventory Manager (OSSera IM) is designed and implemented under the general guidance of TMF Frameworx. The main function of OSSera IM is to host all network information/network data correctly and efficiently. OSSera IM has followed TMF SID in the data model definition for the resources to be managed. OSSera IM can accurately describe the state of resources (network elements and their components, IT systems and applications, resources defined within systems etc.). OSSera IM can track status of all resources. OSSera IM also interacts with Resource Activation and Resource Provisioning, and manages under-utilized or “stranded” assets. OSSera IM also allows for client operations support (service assurance and billing systems) to retrieve part or the entire resource inventory.

OSSera Inventory Manager (OSSera IM), like all other inventory management systems, is basically a Configuration Management Database (CMDB). It hosts all information about the network. In order to get the information and keep the information accurate, OSSera IM first needs to load in all configuration information from EMS then periodically synchronize with EMS. Since each EMS may have its own data model by device vendor’s choice, OSSera IM has to first convert the raw data from EMS to OSSera IM data model (designed following TMF SID). Like other OSSera framework products, OSSera IM relies on OSSera Platform’s common data conversion process in handling data as follows:

     Step 1: Connect to data source using connecter;

     Step 2: Define data mode classes to describe the data;

     Step 3: Convert data into instance of defined classes;

     Step 4: Pass the data model class instances to application logic engine.

For above Step 1 to 3, the process is very similar to the process in OSSera Fault Manager (OSSera FM) or Performance Manager (OSSera PM). For Step 4, OSSera IM is a repository for other applications to retrieve data. Extensions can be made to provide specialized information for specific applications. For example, service fulfillment application needs IM to be capable of reserving resource in CMDB for a service. The following diagram shows the system architecture of OSSera IM:

Today’s Communication Service Providers (CSP) often operates large networks. Thus it is not practical to input network/device data manually to IM. An automated process must be used to speed up the process. Common practice is to develop ways to load data automatically from EMS. OSSera IM has developed an efficient and effective layer called Gateway to facilitate the automatic data input process. OSSera Gateway can be easily built using tools provided by OSSera IM and by using many pre-built data collectors and data convertors. Using OSSera Gateway, OSSera IM can easily connect to EMS, input data automatically, and convert raw data automatically to IM data model class instances for each EMS.

Once OSSera IM loaded in data, OSSera MO View, MO Property View and Object Viewer (common components of OSSera products such as OSSera FM, OSSera PM) can present the data in many different meaningful ways. For example, MO View presents all MOs (Managed Objects) by class. MO Property View presents details of MO. Object Viewer presents network topology and object relationship diagram.

OSSera IM is mainly consisted of the following components:

     • OSSera IM Server – IM server is the back-end process for Inventory Management. It loads in inventory data from data sources such as EMS, file, etc. It provides services to other systems as the CMDB.

     • Data Loader – Data Loader connects to EMS or any other data source to load in inventory data. It is part of Gateway in IM.

     • Data Converter – Data Converter converts EMS raw data into IM data model class instances for each EMS. It is part of Gateway in IM.

     • Report Viewer – The graphic interface to view inventory reports.

     • Topology Viewer – The GUI component for user to view MO in graphical view, e.g., network view or service topology view.

     • MO View – The tree view for user to see and edit MO attributes as well as relationships to other objects.

     • User Management View – A set of GUI components for user authentication and authorization management, such as view, create, update and delete user and related information.

     • Search View – A set of GUI components to search and view IM data.

OSSera IM can be deployed in the form of primary-secondary or symmetric distribution.

OSSera Delivers Network Management System

Download our latest NMS Brochure

The OSSera Network Management System (OSSera NMS) is a software platform that can manage network with large number of Network Elements (NE) and multiple Element Management Systems (EMS). It provides a complete and powerful solutions for managing multi-vendor, multi-device, multi-EMS telecommunication networks. The system supports FCAPS functions of network management that allows the operators and engineers to operate and manage NE and EMS efficiently and effectively.

OSSera NMS is built upon its OSS Explorer Platform with a layered system architecture to enable clear separation among data collection, network management functionality, and applications. Figure 1 illustrates the architecture of OSSera OSS Explorer.

Figure 1: OSS Explorer Platform

On the bottom layer of the system, there is a large set of pre-built data collectors and data convertors that can directly communicate with and receive data from various network elements and element management systems.  The middle layer consists of data model, orchestrators and object manager that provide FCAPS (fault, configuration, accounting, performance, security) functionalities. 

On the top layer of the system, it provides north bound interfaces with OSS and BSS systems. 


Download our latest NMS Brochure

Showing 1 - 5 of 64 results.
Items per Page 5
of 13


About Us  -  OSSera, Inc. is a global provider of Operational Support System (OSS) solutions for IT organizations, service planning, service operations, and network operations.  OSSera's multi-threaded symmetrically distributed platform fully leverages modern multi-core server hardware to provide higher flexibility, reliability, and scalability for service and resource management solutions.  OSSera's products support the TM Forum's suite of standards especially in the area of Service Management, Fault Management, Performance Management, Data Mediation, and Configuration Management.   Meet the management team.

Twitter Twitter

Blogs Aggregator Blogs Aggregator

  Feb. 25-28, 2013 in Barcelona, Spain, the  Mobile World Congress  features the mobile ecosystem which continues to expand at lightning speed, with rapid innovation and new telecom
  OSSera's Service Quality Management Case Study has been featured in the TMF Case Study Handbook 2012.  The TMF Case Study is only available to TMF Members.  
Click to Download PDF. Read article on: About InterComms Magazine The International Communications Project International Communications ( InterComms ) is an
IPTV has seen steady growth in the broadband market but with growth there are increasing challenges with customer experience management and overall quality of service.  Some problems
Green IT is a major concern for service providers as they look forward to storing more content, managing and monitoring the resources required to operate these data centers, networks, and
RSS (Opens New Window)
Showing 6 - 10 of 20 results.
of 4