IoT Data Record Aggregation Mechanism for Billing Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for generating data records for IoT devices in mobile networks are inefficient, leading to a high volume of charging data records that overwhelm billing systems and increase processing costs due to frequent, small data transfers from IoT devices.

Innovation Solution

Implementing an aggregation mechanism that groups IoT devices with similar characteristics under a shared identifier, allowing for the aggregation of network resource usage events into a single aggregate data record, reducing the number of generated data records and processing requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If individual data records are generated for each IoT device, then detailed billing information is captured, but the volume of data records becomes unmanageably large and processing costs increase

Engineering Contradiction:
Improvebilling information accuracyVSAvoidnumber of data records
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent combines multiple individual charging data records from IoT devices into a single aggregate charging data record. The network function groups records by aggregation identifiers and consolidates usage data (data volume, session duration, packet counts) from multiple devices into one record, reducing the total number of records processed by the billing system while preserving essential billing information at the group level.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal aggregation mechanism that can handle multiple types of charging data from different IoT devices under a single record structure. The aggregate record serves multiple purposes: it provides billing information for groups of devices, reduces processing load on the billing system, and maintains flexibility to include various usage metrics (data volume, time, packets) in a standardized format.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If aggregation is implemented to reduce data record volume, then processing efficiency improves, but individual device billing detail may be lost

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidindividual device billing data
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements a two-level segmentation strategy: individual charging data records are maintained at the device level for detailed tracking, while aggregate records provide summarized billing information at the group level. The network function segments the billing process into individual record generation (for detailed tracking) and aggregation (for efficient processing), allowing both individual and group billing needs to be met simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the granularity parameter of billing data from individual device level to group level through aggregation. By controlling the aggregation identifier and grouping criteria, the system can adjust the level of detail in billed information, providing flexibility to balance processing efficiency with billing detail requirements based on specific service needs.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12113928B2Process-efficient generation of data records for data communications involving groups or aggregates of IoT devices
Publication Date: 2024.10.08 CISCO TECHNOLOGY INC
  • US12113928B2 patent drawing
  • US12113928B2 patent drawing
  • US12113928B2 patent drawing

AI summary

Methods, apparatus, and systems for the process-efficient generation of data records for data communications involving groups or aggregates of user equipment (UE), such as IoT devices, are described. In one illustrative example, for each one of a plurality of UEs associated with a group or aggregation identifier (ID), a request which includes data indicative of a network resource usage event of the UE is received and the data are stored in association with the group or aggregation ID. In response to identifying a predetermined condition, the data indicative of the network resource usage events associated with the group or aggregation ID are aggregated, and a request for generating a data record based on the aggregated data is sent to a data function for generating the data record. The generated data record (e.g. a CDR) may be stored for subsequent retrieval for reporting, analysis, network/communications management, or billing.