PBX Mobile Device Registration via Service Management Platform
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems face challenges in correctly associating a telephone terminal's CLI with the correct call registration server, particularly when using a telephony link for PIN data transmission, leading to issues in identifying the correct port for call routing.
Innovation Solution
The system configures a PBX to respond to a configuration telephone number by routing call control to a Service Management Platform (SMP), determining the enterprise extension, and communicating an authentication token to associate the enterprise account with the correct PBX system port, using methods like DTMF signaling or public land-mobile network communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a telephony link is used to transmit PIN data for device registration, then authentication capability is improved, but the ability to correctly identify and associate the calling device with the registration server deteriorates due to CLI routing issues
Solution Approach 1:
The patent introduces a message gateway as an intermediary component that receives the calling line identification (CLI) from the telephony network and forwards it to the registration server. This mediator resolves the routing issue by ensuring the CLI information is properly transmitted through the message gateway, allowing the registration server to correctly identify and associate the calling device with the appropriate account, thus maintaining both authentication capability and device identification accuracy
2Device complexity
If traditional PBX routing is used for call management, then system simplicity is maintained, but the ability to dynamically associate mobile devices with enterprise accounts deteriorates
Solution Approach 1:
The patent segments the call management system into distinct functional components: the PBX handles traditional call routing and switching, while a separate message gateway handles mobile device registration and authentication. This segmentation allows the PBX to maintain its simplicity for core call management, while the message gateway provides dynamic device association capabilities through separate processing logic and database integration
Solution Approach 2:
The message gateway acts as an intermediary between the mobile communication network and the PBX system. It receives registration requests from mobile devices, performs authentication, and establishes associations with enterprise accounts without disrupting the PBX's traditional call routing functions. This intermediary approach enables dynamic device association while preserving system simplicity
3Ease of manufacture
If manual configuration methods are used for device registration, then implementation ease is improved, but registration accuracy and security deteriorate
Solution Approach 1:
The system implements self-service registration where mobile devices automatically initiate registration requests to the message gateway. The device provides its identity information, and the system automatically performs authentication, validates the calling line identification, and establishes the association with the enterprise account. This automated self-service process eliminates manual configuration errors while maintaining ease of implementation through standardized protocols
4Device complexity
If the PBX directly handles mobile device registration, then system complexity is reduced, but authentication security and call routing accuracy deteriorate
Solution Approach 1:
The patent divides authentication and registration functions into a separate message gateway component, distinct from the PBX call management system. The message gateway handles mobile device registration, authentication token verification, and CLI validation, while the PBX focuses on call routing and switching. This segmentation maintains relatively simple system architecture while significantly improving authentication security through dedicated security processing
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The application relates to communication systems comprising a Private Branch eXchange PBX (16) and a platform which performs some aspects of messaging or session control, like call control and advanced call processing features and in some cases, also performs some media handling. This platform is referred to as "Service Management Platform" SMP (18) and is connected to the PBX via either a PRI connection or a LAN employing protocols like SIP, ECMA-269, ECMA-232. Each user has an account comprising information such as his enterprise extension. The account information might not comprise the communication path of a user device. The communication path comprises a PBX system port. In order to record the PBX which is handling calls from the user device, the SMP is configured to direct the mobile communication device associated with the enterprise account to call a configuration telephone number which routes call control to the SMP (632,634). From this call (643), the SMP determines the PBX system port of the call and records it in the account information such that the account information provides a mapping between the account, the extension, and the PBX system port.