Mobile Handset Carrier Identification via Local Exchange Code Lookup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for determining whether an incoming call is from the same mobile network as the recipient are either costly, inaccurate, or do not provide timely in-network notifications, especially when mobile numbers are portable and caller identification is needed for cost-saving promotions.
Innovation Solution
A system and method that determines the mobile communications network associated with an incoming call on a mobile device using caller identification and local exchange codes, with optional validation against an exceptions list for ported numbers, and provides visual, audible, or haptic notifications to the subscriber, allowing for in-network calls to be identified and potentially free or reduced-cost communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a network-based GTT query is used to identify the carrier, then the carrier can determine in-network calls, but there is a cost associated with the GTT search and no display indicator is provided to the call recipient
Solution Approach 1:
The system performs preliminary actions by storing local exchange code to carrier mappings in the handset's memory before calls occur. When a call comes in, the handset immediately checks the stored data locally without requiring a costly real-time GTT query, thus reducing operational costs while maintaining identification capability
Solution Approach 2:
The handset autonomously performs carrier identification by comparing the incoming call's local exchange code against its stored database of carrier mappings. This self-service approach eliminates the need for continuous network-based GTT queries, reducing both cost and network dependency
2Adaptability or versatility
If mobile numbers are portable and callers switch networks, then number portability is enabled, but network-based determination methods introduce errors in carrier identification
Solution Approach 1:
The system updates the local database with current carrier information for ported numbers in advance. When a call is received, the handset checks against this pre-updated database rather than relying on potentially outdated network-based lookups, ensuring accurate identification even for ported numbers
Solution Approach 2:
The system incorporates feedback mechanisms where the handset can update its local database with corrected carrier information for ported numbers. This feedback loop ensures that the local database remains accurate despite number portability, improving identification precision over time
3Reliability
If a network database query is performed prior to call termination, then carrier information can be determined, but the data is only available after the call has been established requiring side channels
Solution Approach 1:
The system performs carrier determination in advance by maintaining an up-to-date local database of carrier mappings. When a call is incoming, the handset immediately queries its local database using the caller's local exchange code, providing instant carrier identification without delaying call establishment or requiring post-call side channels
4Measurement precision
If the phone performs a database lookup at startup for numbers in the address book, then in-network status can be determined for stored numbers, but new callers and their numbers are not identified as in-network
Solution Approach 1:
The system creates a universal solution by maintaining a local database that can identify in-network status for any caller, not just those in the address book. The handset uses its local exchange code database to determine carrier affiliation for any incoming call number, making the identification capability universal across all callers including new ones
Data Source
AI summary
Systems and method for determining if a network of a call page has been ported to another network. The mobile communications network associated with a received call page is determined based on caller identification (CID) included in the call page and information of local exchange codes and associated mobile carriers stored in local memory of the mobile device. The method determines if the mobile communications network associated with the received call page is valid with regard to an exceptions list. Next it is determined if the determined mobile communications network associated with the call page matches the mobile communications network associated with the mobile device based on the validity determination. The exceptions list identifies phone numbers that have been ported to a mobile communications network that is different that the determined network.


