Address Book Segmentation for Unique Device Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current address book systems fail to efficiently route sessions to specific devices with desired features and properties, particularly in SIP environments, as they lack a mechanism for uniquely identifying devices across multiple users and networks, leading to inefficient session setup and potential connectivity issues.
Innovation Solution
The introduction of an instance identifier (Instance_ID) system, which uses unique identifiers like IMEI, MAC addresses, or PINs, along with device ID nicknames, to establish a relationship between public user identities and device capabilities, allowing users to selectively connect to devices with specific features and properties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a common address book is used to store contact information, then the address book structure remains simple, but the system cannot uniquely identify devices across multiple users and networks
Solution Approach 1:
The address book structure is segmented into multiple tables: a first table stores contact information with public user identities, while a second table stores device information with unique device identifiers. This segmentation allows unique device identification without making the entire address book structure overly complex, as each table has a specific function and the tables are linked through relationships.
Solution Approach 2:
The patent introduces an intermediary relationship between the first and second tables through shared fields. The first table contains a field that references the second table, creating a link between contact information and device information. This intermediary linkage enables unique device identification while maintaining a manageable address book structure.
2Productivity
If traditional address book systems are used, then the system remains simple to implement, but session routing to specific devices with desired features is inefficient
Solution Approach 1:
The address book is segmented into functional tables: one for contact information and another for device information. This allows the system to efficiently query and route sessions to specific devices by searching the device information table for devices with desired features and properties, rather than searching through all contact information, thereby improving session setup efficiency.
Solution Approach 2:
Device information including capabilities and properties is pre-stored in the second table with unique device identifiers. This preliminary organization of device data allows the system to quickly identify and route sessions to the correct devices based on their stored characteristics, improving productivity without requiring complex real-time analysis.
3Measurement precision
If unique device identifiers are added to the address book, then device identification accuracy improves, but the address book structure becomes more complex
Solution Approach 1:
The address book is divided into separate tables: the first table stores contact information and the second table stores device information with unique device identifiers. This segmentation allows high-precision device identification through the unique identifiers in the second table while keeping the overall structure manageable, as each table has a clear purpose and the relationship between tables is well-defined.
Solution Approach 2:
The patent adds a new dimension to the address book structure by introducing a second table for device information that is separate from the contact information table. This dimensional expansion allows unique device identifiers to be stored and queried independently, improving identification accuracy while the tabular structure provides a systematic way to manage the increased complexity.
Data Source
AI summary
A method and system for addressing a unique device from an address book, the method having the steps of: receiving a message having a root token and a secondary token; checking whether the root token exists within the address book, if no, creating a record in the address book with the root and secondary token; and if yes, checking whether the secondary token exists within the address book, if yes, providing a representation of the unique device; and if no, storing the secondary token against the root token in the address book.