Message Routing Engine for Device-Independent Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current electronic communication systems lack the ability to send messages independently of the sending or receiving devices and interfaces, requiring senders to specify the method and address of receipt, and do not allow for seamless communication between multiple users using different devices or interfaces.
Innovation Solution
A system with a routing engine that receives messages from various entry points, determines recipient identities and endpoints, translates messages for compatibility, and delivers them to multiple endpoints without the sender needing to know the specific addresses or interfaces, enabling device-independent point-to-multipoint communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a sender specifies the method and address of receipt for each message, then message delivery can be achieved, but the system lacks device independence and requires sender knowledge of receiver-specific interfaces
Solution Approach 1:
The patent introduces a message routing system that acts as an intermediary between senders and receivers. The routing engine receives messages from senders, determines the identities and endpoints of destination users, and delivers messages through appropriate channels without requiring senders to know receiver-specific addresses or interfaces. This mediator abstracts the complexity from senders while maintaining delivery capability.
Solution Approach 2:
The routing engine provides universal message delivery capability across multiple device types and communication interfaces (e-mail, SMS, IM, web input, API). A single messaging system can deliver to various endpoints without requiring separate sender knowledge for each interface, achieving multi-functionality in message distribution.
2Adaptability or versatility
If messages are sent to multiple users using different devices and interfaces, then communication coverage is improved, but the system lacks a general method for handling diverse endpoints
Solution Approach 1:
The routing engine serves as a central intermediary that manages complexity internally while providing simple sender interfaces. It handles the diverse endpoint requirements, determines appropriate delivery channels, and manages multiple communication protocols without exposing this complexity to senders, thus enabling cross-device communication without proportional system complexity increase.
Solution Approach 2:
The system segments the message delivery process into distinct functional components: message reception, routing determination, endpoint identification, and channel-specific delivery. This segmentation allows each component to handle specific aspects of multi-device communication independently, managing overall system complexity through modular architecture.
3Reliability
If senders must know receiver addresses for each device interface, then precise message delivery is achieved, but the ease of operation deteriorates due to address management burden
Solution Approach 1:
The routing engine acts as an intermediary that manages address and endpoint information internally. Senders provide only high-level recipient identification, and the routing engine resolves this to specific device addresses and interfaces, maintaining delivery accuracy while eliminating the burden of address management from senders.
Solution Approach 2:
The routing system performs self-service by automatically determining destination endpoints and selecting appropriate delivery channels based on recipient information. This automatic resolution of addresses and interface selection maintains precise message delivery without requiring manual address management by users.
Data Source
AI summary
An example system for device-independent point to multipoint communication is configured to receive a message addressed to one or more destination users, the message type being, for example, Short Message Service (SMS), Instant Messaging (IM), E-mail, web form input, or Application Program Interface (API) function call. The system also is configured to determine information about the destination users, the information comprising preferred devices and interfaces for receiving messages, the information further including message receiving preferences. The system applies rules to the message based on destination user information to determine the message endpoints, the message endpoints being, for example, Short Message Service (SMS), Instant Messaging (IM), E-mail, web page output, or Application Program Interface (API) function call. The system translates the message based on the destination user information and message endpoints and transmits the message to each endpoint of the message.