Remote UI Message Delivery via Multicast Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In remote control environments, existing message delivery schemes, such as TCP sockets and XML HTTP Requests, are inadequate for directly forwarding notification messages from a second device connected to a remote server to a specific third device, as the address of the second device is not included in the UI page provided from the remote server.
Innovation Solution
A new message delivery system where a second device provides notification messages generated in itself or a remote server to a specific third device, using URL information extracted from notification message events in multicast transmissions, allowing for targeted message delivery through a remote server application and embedded server handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If multicast transmission is used to send notification messages to all third devices, then message delivery coverage is improved, but message delivery precision deteriorates
Solution Approach 1:
The notification message is segmented into two parts: a multicast notification event that alerts all third devices, and a subsequent unicast message request that is sent only to the specific third device identified by device handle. This segmentation allows the system to first achieve broad coverage through multicast, then refine delivery precision through targeted unicast communication.
Solution Approach 2:
The second device acts as an intermediary between the notification source and third devices. It receives the multicast notification event, extracts the device handle to identify the specific target third device, then initiates a targeted message request to that specific device. This intermediary role enables the transition from broad multicast notification to precise unicast delivery.
2Reliability
If TCP socket or polling schemes are used for message delivery, then message delivery reliability is improved, but device complexity increases
Solution Approach 1:
The solution uses universal HTTP message requests that can be handled by any third device with web browsing capability, rather than requiring specialized TCP socket implementations or polling mechanisms. The embedded server in the second device provides a universal interface that simplifies the communication protocol while maintaining reliable message delivery through standardized HTTP transactions.
3Ease of operation
If XML HTTP Request is used for message delivery, then ease of operation is improved, but message delivery efficiency deteriorates
Solution Approach 1:
The system performs preliminary action by including device handle information in the multicast notification event itself. This allows the subsequent message request to be immediately targeted to the specific third device without requiring additional discovery or identification steps, thereby maintaining ease of operation while improving delivery efficiency through pre-configured routing information.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
A method and device for providing a message in a remote User Interface (UI) system are provided. The method includes, if a notification message to be sent to a second device connected to a first device is generated in a remote server or the first device communicating with the remote server, the first device generates access information to the notification message, includes the access information in a notification message event indicating occurrence of the notification message, and sends the notification message event to a plurality of second devices in a multicast transmission. Upon receiving a request for the notification message from the plurality of second devices, the first device sends the notification message to the second device whose IDentifier (ID) is identical to a device ID included in the access information, among the plurality of second devices.