Service Contact Identifier Retrieval System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users are required to possess multiple service contact identifiers for different electronic services, such as telephone numbers and bank account numbers, which can be inconvenient and limit access to services if one identifier is missing.
Innovation Solution
A system and method that allows users to retrieve the necessary service contact identifier by transmitting an arbitrary service contact identifier along with a service identifier, enabling the system to trace and provide the required contact details for various services, including telephony, payment, and navigation, regardless of the initial identifier provided.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single telephone number is used as service contact identifier for multiple services (telephony, internet, payment), then the number of contact identifiers to remember is reduced, but the system fails when the user does not possess the telephone number for non-telephony services
Solution Approach 1:
The server system is designed to accept multiple types of service contact identifiers (telephone numbers, bank account numbers, email addresses) and universally translate them into the required contact identifier for any service. This multi-functional capability allows the system to handle diverse identifier types through a single unified interface, resolving the contradiction by making the system adaptable to different identifier types while maintaining ease of operation.
Solution Approach 2:
The server system acts as an intermediary between the user and the service providers. Instead of requiring users to directly possess and manage multiple service-specific contact identifiers, the server receives any identifier type from the user, translates it to the required format, and forwards it to the appropriate service provider. This mediator approach allows users to access multiple services with a single identifier type while the system handles the complexity of identifier translation.
2Adaptability or versatility
If multiple service contact identifiers are required for different services, then each service can be accessed with its specific identifier, but users must possess and manage multiple identifiers which reduces convenience
Solution Approach 1:
The patent merges the functionality of multiple service contact identifier management systems into a single server system. Instead of requiring separate systems for telephone, internet, and payment services each with their own identifier requirements, the patent combines them into one unified server that handles all identifier types through a single translation mechanism, reducing the burden on users while maintaining service-specific accuracy.
Solution Approach 2:
The server system provides universal service across multiple service domains (telephony, internet, payment, etc.) by accepting any service contact identifier type and translating it to the appropriate format for each service. This universal approach allows users to access all services through a single identifier without sacrificing the specific identifier requirements that each service needs for proper operation.
3Ease of operation
If a service contact identifier translation system is implemented, then users can access multiple services with a single identifier, but the system complexity increases due to database and translation requirements
Solution Approach 1:
The patent extracts the complex identifier translation logic from the user device and places it in a centralized server system. This extraction allows user devices to remain simple while the server handles all the complexity of maintaining databases, mapping relationships between different identifier types, and performing translations. The complex functionality is taken out of the user's responsibility and managed centrally.
Solution Approach 2:
The server system automatically performs the translation between different service contact identifier types without requiring user intervention or manual configuration. The system self-manages the database updates, mapping relationships, and translation processes, reducing the operational complexity for users while maintaining the sophisticated translation capabilities needed for multi-service access.
Data Source
AI summary
Aspects of the invention relate to a system and method of retrieving a service contact identifier for providing a service to a user is proposed. The method is performed in a system comprising at least one server system configured for connecting to a user device of said user. The server system has access to a database comprising at least a first service contact identifier required for providing a first service and a second service contact identifier required for providing a second service. The first service is identified by a first service identifier. The first service contact identifier and second service contact identifier are different service contact identifiers. The first service identifier and a service contact identifier are received from the user device of said user. The first service contact identifier may then be retrieved in dependence of the received first service identifier and the received service contact identifier, irrespective of whether said received service contact identifier is said first service contact identifier or said second service contact identifier.