Business Server Message Routing via Shared Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business messaging systems face cost inefficiencies and inability to route reply messages to intended users due to the requirement of unique public identifiers for each user, especially in systems with a large number of users, leading to high costs and misrouting of messages.
Innovation Solution
A system and method that uses a business server to manage public identifiers, allowing multiple business users to exchange messages with messaging devices using a limited number of public identifiers, and uniquely identifies business users through associations with messaging devices, enabling duplex message exchange without the need for individual public identifiers for each user.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a unique public identifier is rented for each business user to enable message exchange and reply routing, then message routing reliability is improved, but system cost increases significantly
Solution Approach 1:
The patent merges multiple business users under a single public identifier (the business server's identifier). Instead of each user having a unique identifier, multiple users share the business server's identifier, and the server internally routes messages to the correct user using user-specific routing information stored in its database.
Solution Approach 2:
The business server acts as an intermediary between the SMS system and individual business users. It receives messages addressed to its identifier, determines the intended recipient using routing information, and delivers the message to the correct user. This mediator approach allows cost-effective message exchange without requiring unique public identifiers for each user.
2Quantity of substance
If a limited number of public identifiers are rented for the business server, then system cost is reduced, but the ability to route reply messages to specific users is lost
Solution Approach 1:
The patent adds another dimension to message routing by including user-specific information (such as user identifiers, names, or other routing data) within the message body or metadata, in addition to the sender and recipient identifiers. This allows the server to route replies to specific users even when using a limited set of public identifiers.
Solution Approach 2:
The business server pre-establishes routing information for each user in its database before messages are exchanged. This preliminary setup allows the server to quickly and accurately route incoming messages and replies to the correct users without needing unique public identifiers for each user.
3Adaptability or versatility
If public identifiers are rented for each user to enable duplex message exchange, then communication versatility is improved, but operational cost increases prohibitively
Solution Approach 1:
The business server's single public identifier serves multiple functions: it identifies the business server to the SMS system, enables incoming messages to be addressed to the server, and allows the server to forward messages to multiple different users. This multi-functionality eliminates the need for each user to have their own public identifier while maintaining full duplex messaging capability.
Solution Approach 2:
The business server autonomously handles message routing and user identification without requiring external infrastructure or unique identifiers for each user. The server uses its internal database and routing logic to manage communication between multiple users and the SMS system, making the system self-sufficient and cost-effective.
Data Source
AI summary
A system for exchanging messages between a business user and another messaging-capable device, and associated methods are presented. The system may include a business server, an application programming interface (“API”) and/or an SMS database. The business server may be configured to exchange messages with the business user and to obtain a public identifier for the business user to enable duplex message exchange between the business user and the messaging-capable device by either retrieving the public identifier or associating the business user with the messaging-capable device and a public identifier. The system may accommodate temporary events, such as emergencies, by associated a public identifier with a business user initiating the temporary event and one or more messaging-capable devices involved in the event.