IMEI Validation in Mobile Networks for Billing Accuracy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Invalid international mobile equipment identity (IMEI) information can lead to incorrect call detail records (CDRs), resulting in billing issues for network service providers due to changes in device software, type, make, or model, and potential tampering or theft of mobile devices.
Innovation Solution
Implementing a validation component within core network entities such as the mobility management entity (MME), packet gateway (PGW), serving-call session control function (S-CSCF), and IP multimedia session home subscriber subsystem (IMS-HSS) to verify the validity of the IMEI by checking its format, length, and matching it against a list of valid TAC codes, and performing identity checks to detect blacklisted devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If IMEI information is collected and used for billing without validation, then billing processes can be performed efficiently, but incorrect CDRs are generated leading to revenue loss
Solution Approach 1:
The patent applies preliminary action by implementing IMEI validation checks before CDR generation and billing processes. The validation component verifies IMEI format, length, and TAC code legitimacy in advance, preventing invalid IMEIs from propagating through the billing system. This early validation ensures billing accuracy without compromising processing efficiency, as the validation is integrated into the existing data flow rather than adding separate verification steps.
2Reliability
If IMEI validation checks are implemented to ensure accuracy, then billing reliability improves, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary validation component that sits between the IMEI collection point and the CDR generation system. This intermediary performs focused validation checks on IMEI format, length, and TAC code legitimacy, isolating the complexity of validation logic from both the data collection and billing systems. The component acts as a mediator that simplifies integration while ensuring billing accuracy.
3Speed
If basic IMEI format checking is performed, then processing speed is maintained, but stolen or tampered devices cannot be detected
Solution Approach 1:
The patent segments the IMEI validation process into distinct functional checks: format validation (length and structure), TAC code legitimacy verification, and blacklist database matching. This segmentation allows the system to perform rapid format checks for speed while also conducting more intensive authenticity verifications. The segmented approach enables parallel processing of different validation aspects, maintaining overall processing speed while comprehensively detecting stolen or tampered devices.
Data Source
AI summary
A control plane entity can perform validation checks to confirm the validity of a device identifier, for example, an international mobile equipment identity (IMEI), received from a user equipment (UE) during registration of the UE with a communication network. In one aspect, the control plane entity can verify that the IMEI conforms to a defined format; for example, the IMEI is fifteen digits long, does not comprise alphabets and/or symbols, and/or comprises a valid type allocation code (TAC) of eight decimal digits, etc. The validation of the IMEI can reduce errors in billing that can otherwise result in revenue loss for the service provider.