User Terminal Configuration via Vendor Identifier Redirection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for configuring user terminals in cloud-based voice-over-IP communication services are costly, logistically complex, and require significant involvement from both equipment vendors and service providers, especially when deploying terminals in networks where the DHCP server is not manageable by the service provider.
Innovation Solution
A method and system that allocates a device identifier and service provider identifier to user terminals, utilizing a configuration repository and front-end server within the service provider's domain to facilitate automatic configuration, minimizing user interaction and operational costs, and allowing terminals with basic interfaces to connect to the correct Application Server instance without pre-configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If pre-configuration of terminals is performed by the terminal vendor or CSP, then the terminal can be authorized on the configuration server, but costly operations and high operational and logistical expenses are required before terminals are delivered
Solution Approach 1:
The terminal is pre-configured with a vendor identifier during manufacturing, enabling it to automatically locate and connect to the appropriate CSP network and configuration server without requiring costly post-manufacturing customization operations
Solution Approach 2:
A redirection server acts as an intermediary between the terminal and the CSP configuration server. The redirection server receives the terminal's connection request, uses the vendor identifier to route the terminal to the correct CSP network, and enables automatic configuration without direct vendor-CSP coordination
2Adaptability or versatility
If a vendor central server tracks every deployed device, then configuration can be delivered to all vendor terminals, but high operational costs are required to maintain the database and track MAC addresses
Solution Approach 1:
The complex vendor central server tracking system is replaced by extracting only the essential vendor identifier information that is already present in the terminal. This eliminates the need for maintaining large databases of deployed devices while preserving the ability to deliver appropriate configuration
Solution Approach 2:
Instead of tracking actual device MAC addresses and maintaining detailed deployment databases, the system uses a simplified copy approach where the vendor identifier in the terminal maps to configuration parameters, eliminating the need for expensive centralized tracking infrastructure
3Ease of operation
If DHCP is used to provide the Configuration Repository server URL, then automatic configuration is possible, but the DHCP server must be manageable by the CSP which is not the case in many networks
Solution Approach 1:
The configuration process is segmented into two independent parts: network connectivity (handled by standard DHCP) and configuration server location (handled by the vendor identifier-based redirection mechanism). This segmentation allows the solution to work in any network environment regardless of DHCP server controllability
Solution Approach 2:
The terminal uses its embedded vendor identifier to autonomously locate the appropriate CSP network and configuration server without requiring external DHCP server configuration or CSP intervention in the local network infrastructure
4Ease of operation
If manual configuration is performed by the end user, then the Configuration Repository Server URL can be entered, but highly available helpdesk services are required which involve operating costs
Solution Approach 1:
The terminal automatically performs configuration by using its vendor identifier to locate and connect to the appropriate configuration server, eliminating the need for manual user input and reducing dependence on costly helpdesk services
Data Source
AI summary
A system for configuring a user terminal connected to an Internet Protocol network, comprises: a configuration repository (ASN) in a service provider domain, wherein the configuration repository is loaded with configuration information intended for a user terminal, a front-end server in the service provider domain, the front-end server comprising: a communication port connected to the Internet Protocol network, and a first controller arranged for mapping a predefined device identifier to the configuration repository, and a redirection server, the redirection server comprising: a communication port connected to the Internet Protocol network and reachable by a user terminal to be configured, a non-transitory computer-readable medium loaded with a service provider record, wherein the service provider record comprises a fully qualified domain name routable to the front-end server communication port, and a second controller arranged for mapping a predefined service provider identifier to the service provider record.