Charging Trigger Function Metadata Injection for Service Chaining

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The current 3GPP charging architecture for service chaining faces scalability issues and delays in online charging, particularly affecting user plane traffic, and requires separate implementations for online and offline charging architectures, complicating integration with non-telco service functions.

Innovation Solution

Incorporating a Charging Trigger Function (CTF) that adds charging data to user IP packets as metadata within the Network Service Header (NSH), allowing collective charging data to be handled by a Charging Function (CF) within the service chain, which can request a single authorization for online charging or transmit aggregated records for offline charging, reducing interface complexity and delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate implementations for online and offline charging architectures are used, then charging functionality is provided, but device complexity and integration difficulty increase

Engineering Contradiction:
Improvecharging architecture supportVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service function is designed with a universal charging trigger function that can operate in both online and offline charging modes. The same service function infrastructure handles charging triggers for both architectures, eliminating the need for separate implementations and reducing complexity while maintaining adaptability to different charging scenarios

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

2Reliability

If service functions stop packets for authorization in online charging, then charging control is ensured, but user plane traffic delay increases

Engineering Contradiction:
Improvecharging controlVSAvoidtraffic delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The charging control function is extracted from the service function and relocated to the charging function. The service function triggers charging events by sending notifications to the charging function, which then handles authorization independently. This separation allows service functions to continue processing traffic without stopping packets for authorization, eliminating delays while maintaining charging control reliability

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If multiple charging data records are transmitted for each service function, then charging accuracy is improved, but interface traffic and processing overhead increase

Engineering Contradiction:
Improvecharging accuracyVSAvoidinterface traffic
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

Multiple charging data records from different service functions are merged into a single aggregated charging record. The charging function collects charging triggers from various service functions and combines them into one consolidated record for transmission to the charging system, maintaining charging accuracy while significantly reducing interface traffic and processing overhead

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3406090B1Charging for services in telecommunications networks
Publication Date: 2022.04.20 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3406090B1 patent drawingFigure 1
  • EP3406090B1 patent drawingFigure 2
  • EP3406090B1 patent drawingFigure 3

AI summary

Methods and apparatus for implementing a service function chain (401) of a mobile telecommunications network. The methods and apparatus comprise, at a plurality of service function means, which may be service functions (414a-414c), arranged sequentially, receiving, by a receiving means, which may be a receiver (604), a user packet from a service function forwarder in the service function chain. The methods and apparatus further comprise applying, by a service implementing means, which may be a service implementer (614), a service associated with the user packet and the service function. The methods and apparatus further comprise determining, by a charging trigger function means, which may be a charging trigger function, CTF, (616), charging data for the applied service. The methods and apparatus further comprise generating, by the CTF, an updated user packet comprising the charging data. The methods and apparatus further comprise returning, by a transmitting means, which may be a transmitter (602), the updated user packet towards the service function forwarder in the service function chain. The methods and apparatus further comprise, at a charging function (420, 428), receiving, by a further receiving means, which may be a receiver (504), from the service function forwarder, collective charging data comprising individual charging data determined by each of the plurality of service functions. The methods and apparatus further comprise controlling, by a charging controlling means, which may be a charging controller (518), charging for the applied services based on the collective charging data.