Session Identifier Verification in Mobile Network Charging Records

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current charging trigger function (CTF) devices in mobile networks occasionally insert incorrect session identifiers in accounting request records, leading to mismatches and the generation of erroneous records, which result in processing overheads and superfluous accounting records.

Innovation Solution

A SIP back-to-back user agent (B2BUA) device ensures correct outgoing session identifiers by comparing received and expected Call-IDs, noting errors, and populating error messages to prevent incorrect session identifiers from being used in accounting records, thereby reducing erroneous records and processing overheads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If CTF devices handle multiple SIP transactions without verification mechanisms, then processing speed is maintained, but session identifier correctness deteriorates leading to erroneous records

Engineering Contradiction:
Improveprocessing speedVSAvoidsession identifier correctness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by implementing verification of session identifiers against expected values before generating accounting records. The CTF device checks whether the session identifier in the ACR message matches the expected Call-ID stored in its context, and only generates records when verification succeeds. This preventive check prevents erroneous records from being created in the first place, resolving the contradiction by maintaining reliability without significantly impacting processing speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by comparing the session identifier received in ACR messages against the expected Call-ID values stored in the CTF device's context. This feedback mechanism allows the system to detect mismatches and discard erroneous records, ensuring that only accurate accounting records are persisted. The feedback loop maintains reliability while keeping the processing efficient by avoiding unnecessary complex validations.

Inventive Principle:
Principle #23Feedback

2Device complexity

If CCF devices generate records without error indication mechanisms, then device complexity is reduced, but data quality deteriorates due to undetected erroneous records

Engineering Contradiction:
ImproveCCF device complexityVSAvoidaccounting record accuracy
Core Design Contradiction:
Device complexityVSManufacturing precision

Solution Approach 1:

The patent applies the taking out principle by extracting the error detection and indication functionality from the CCF device and placing it in the CTF device. The CTF device now performs the verification of session identifiers and generates error indications before sending records to the CCF. This extraction reduces the complexity of the CCF device while improving accounting record accuracy, as the CCF simply processes records without needing complex verification logic.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism where the CTF device acts as a mediator between the SIP transaction processing and the CCF device. The CTF device verifies session identifiers and filters erroneous records before forwarding to the CCF, thereby improving data quality without requiring the CCF to become more complex. This intermediary layer maintains a clear separation of concerns while ensuring record accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If session identifier verification is implemented, then accounting record accuracy is improved, but processing overhead increases due to additional verification steps

Engineering Contradiction:
Improveaccounting record accuracyVSAvoidprocessing overhead
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent applies partial action by implementing verification only for the critical session identifier field rather than validating all fields in the ACR message. The CTF device checks whether the session identifier matches the expected Call-ID stored in context, which is a targeted and efficient approach. This partial verification improves accounting record accuracy while minimizing processing overhead by focusing only on the most critical validation.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the parameter being verified from a comprehensive validation of all ACR message fields to a specific check of the session identifier against the expected Call-ID. This parameter change reduces the computational complexity of the verification process while maintaining high accuracy for the most critical aspect of record correctness. The verification becomes a simple string comparison rather than a complex multi-field validation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11108576B2Ensuring correctness of session identifiers in call duration records in mobile networks
Publication Date: 2021.08.31 AT&T INTELLECTUAL PROPERTY I L P
  • US11108576B2 patent drawing
  • US11108576B2 patent drawing
  • US11108576B2 patent drawing

AI summary

A mechanism to insert a correct call identifier as a session identifier in an accounting request (AR) record and a mechanism for a charging control function (CCF) device to check the value and generate an error as required. A method can comprise receiving a session initiation protocol packet representing a first attribute value pair; based on the session initiation protocol packet, checking for an existence of an identity between a first field associated with the session initiation protocol packet and a second field associated with a second attribute value pair; and in response to a result of the checking being that the existence of the identity is not determined to be presents between the first field and the second field, updating a third attribute value pair.