Circuit-Switched Switching Node Naming Information Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for providing naming information of a called party to a circuit-switched mobile terminal in a mobile telecommunication network are complex, user-unfriendly, and costly, often requiring users to manually retrieve and manage phone numbers, leading to confusion and reliance on operators for repeated calls to the same parties.
Innovation Solution
A method and system where a circuit-switched switching node receives a call setup request from a mobile terminal, obtains the called party's identifier, and sends a request for naming information to a database, allowing the delivery of naming information, such as names associated with phone numbers, back to the terminal, which can replace phone numbers in the outgoing call list for easier identification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If existing address book solutions are used for circuit-switched phones, then naming information can be provided, but the system becomes complex and requires considerable CAPEX
Solution Approach 1:
The patent introduces a database as an intermediary component that stores naming information and a switching node that mediates between the mobile terminal and the database. This intermediary architecture allows the terminal to simply store and retrieve names without implementing complex address book synchronization systems, thereby reducing overall system complexity while providing naming information functionality.
Solution Approach 2:
The patent extracts the naming information storage and management function from the mobile terminal and places it in a centralized database. The terminal only needs to store minimal identifying information (like phone number), while the database handles the complex tasks of storing, retrieving, and managing naming information, thus simplifying the terminal device.
2Ease of operation
If manual phone number entry is required for repeated calls, then device complexity is reduced, but user operation becomes cumbersome and time-consuming
Solution Approach 1:
The patent implements preliminary action by automatically retrieving and displaying the called party's name from the database before the call is placed. The system proactively provides the naming information when the user initiates a call to a number stored in the outgoing call list, eliminating the need for the user to manually look up names or contact operators for repeated calls.
Solution Approach 2:
The patent establishes a feedback mechanism where the system automatically queries the database for naming information based on the called party's identifier and returns the name to the terminal. This automated feedback loop provides the user with the needed information without requiring manual intervention, significantly improving ease of operation and reducing time for repeated calls.
3Loss of information
If outgoing call list contains only phone numbers, then device complexity is minimized, but the user cannot easily recognize and identify called parties
Solution Approach 1:
The patent merges the phone number storage function with the naming information retrieval function. The outgoing call list continues to store only the phone number (minimal data), but the system combines this with automated database queries to retrieve and display the corresponding name. This merging approach provides comprehensive identification information without requiring the terminal to store or manage complex data structures.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Methods and devices for providing naming information of a called party to a circuit-switched mobile terminal (300, 600, 900, 1000) of a calling party via a mobile telecommunication network are described. In particular, a method performed by a circuit-switched switching node (310, 610, 910, 1010) comprises the steps of receiving (S100) from the mobile terminal a request for setting up a call to a terminal (340, 640, 940-948) of the called party, obtaining (S110) an identifier of the called party, sending (S120) a request for naming information of the called party to a database (330, 630, 930, S22, S33) wherein the naming information of the called party is registerable in association with the called party identifier, the request comprising the identifier, receiving (S130) the naming information from the database, and executing (S140) a delivery of the naming information to the mobile terminal.