Server Multicast Reliability via Dynamic Unicast Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for distributing electronic program guides from a server system to client systems, such as set top boxes, rely on multicast, which fails if the client system is not configured correctly or if network nodes are not multicast-enabled, preventing the delivery of new files or updates.

Innovation Solution

A method where a server system multicasts information items to client systems, with a comparison of identification lists to detect failures, allowing unicasting of missing items, ensuring data exchange and delivery even in non-multicast enabled networks by using IP-multicasting and IP-unicasting, and dynamically tracking client IP-addresses for accurate delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multicast is used to distribute information items to client systems, then data distribution efficiency is improved, but delivery reliability deteriorates when network nodes are not multicast-enabled or client configuration is incorrect

Engineering Contradiction:
Improvedata distribution efficiencyVSAvoiddelivery reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically switches between multicast and unicast transmission modes based on delivery success. The server system monitors whether information items were successfully delivered via multicast and automatically transitions to unicast for specific clients when multicast fails, making the transmission mechanism adaptive rather than static

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The client system sends back identification information about received information items to the server system. The server system compares this feedback with its records of transmitted items to identify delivery failures and triggers retransmission via unicast, creating a closed-loop feedback mechanism that ensures reliable delivery

Inventive Principle:
Principle #23Feedback

2Ease of operation

If client systems are pre-configured with static URLs for downloading files, then initial file retrieval is simplified, but adaptability to new files and location changes deteriorates

Engineering Contradiction:
Improveinitial file retrieval simplicityVSAvoidadaptability to new files and location changes
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The server system pre-generates and sends identification information about information items to client systems before actual download is needed. This preliminary action includes sending item identifiers and metadata that enable clients to request specific items later without having pre-configured URLs

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The server system serves multiple functions: it acts as both a multicast distribution system and a unicast request-response system. The same server that multicasts information items also handles individual client requests for specific items, making the system universally capable of handling both broadcast and targeted delivery scenarios

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP1936876B1Method and system for ensuring data exchange between a server system and a client system
Publication Date: 2016.12.07 NOKIA SIEMENS NETWORKS GMBH & CO KG
  • EP1936876B1 patent drawingFigure 1

AI summary

In order to ensure data exchange between a server system (10) and a client system (22, 23, 32, 33) a new method, a server system (10) and a data network (1) are presented. The client system (22, 23, 32, 33) is comprised by a plurality of client systems (22, 23, 32, 33), which are connected to the server system (10). The method comprises the steps of: - multicasting a first plurality of information items from the server system (10) to the plurality of client systems (22, 23, 32, 33) ; - storing in the server system (10) a first identification of the first plurality of information items; - storing in the client system (22, 23, 32, 33) a second identification of a second plurality of information items which effectively were registered to have arrived at the client system (22, 23, 32, 33); - identifying a failure of the multicasting of at least one of the information items of the first plurality of information items by comparing the first identification with the second identification; - unicasting said at least one of the information items of the first plurality of information items to the client system (22, 23, 32, 33).