Browse Prior Art Database

System for collecting, aggregating and producing reports about, data related to usage of network

IP.com Disclosure Number: IPCOM000245656D
Publication Date: 2016-Mar-24
Document File: 2 page(s) / 136K

Publishing Venue

The IP.com Prior Art Database

Related People

Erwan Gereec: INVENTOR

Abstract

In the Network on Demand context where communication equipment providers move from traditional CAPEX/OPEX model to a pay-per-use by their customers model, there is a need for not only a monthly invoice to customer based on real network consumption, but also systems to produce enriched reports allowing customers and business partners alike, to have an in-depth understanding of how a network is really used.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 59% of the total text.

Date : 17/03/2016

Inventor: Erwan Gereec

Title: system for collecting, aggregating and producing reports about, data related to usage of network

In the Network on Demand context where communication equipment  providers move from traditional CAPEX/OPEX model to a pay-per-use by their customers model, there is a need for not only a monthly invoice to customer based on real network consumption, but also systems to produce enriched reports allowing customers and business partners alike, to have an in-depth understanding of how a network is really used.

One such system is described in relation to the following figure:

The reference numerals 1, 2 and 3 refer to the following functions:

  1. Collect process : The collect process is responsible to load into the aggregation system (could be a Datalake), all data comes from all configured sources :

- Step 1 : OmniVista Master (OVM) posts daily usage data to aggregation system using an HTTP POST request.

- Step 2 : When all usage data have been received, aggregation system gets the list of external services associated to the subscription of a Customer/Partner, from the “External services database”. It starts to make outgoing API requests to all managed external services for the subscription, to get the value returned by each service. For example :

                                                               i.     A weather external service API: useful to get the environment in which usage data have been generated

                                                             ii.     End customer data API : get additional values from the end customer database, in relation to other parts of its own business (ex: the room occupancy rate for a hotel)

                                                            iii.     Or some other services data, as previously configured by a Customer/Partner in the system.

  1. Aggregate and crossing data process : When all usage data have been retrieved, crossing data (usage and external data services) allows to produce an enriched report, plus recommended actions as the case may be.

To be able to cross these data, the syst...