Multi-tier Push Service Control for Large-Scale ICN Conferences
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual conferencing technologies face challenges in real-time performance, scalability, and interactive communication, particularly in supporting large-scale conferences with thousands of participants, due to high data traffic concentration, inefficient bandwidth utilization, and complex data updates in server-centric and pull-based models.
Innovation Solution
A multi-tier conference service control architecture employing a push mechanism for synchronizing conference updates, utilizing a centralized service controller, distributed service proxies, and participants, with digest logs to track updates and leverage ICN features like name-based routing and in-network caching for efficient and real-time communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If server-centric architecture is used for virtual conferencing, then centralized control is achieved, but data traffic concentration increases and scalability deteriorates
Solution Approach 1:
The patent segments the centralized server architecture into distributed service proxies deployed at multiple network locations. Each proxy independently handles conference data for its local users, dividing the previously concentrated data traffic into distributed segments. This maintains centralized control through the service controller while eliminating data traffic concentration at a single point.
Solution Approach 2:
The patent introduces a hierarchical dimension to the architecture, with service controllers at the control plane and service proxies at the data plane. This dimensional separation allows centralized control signaling to flow through the controller while data traffic is handled locally at the proxy level, effectively moving data traffic from a single concentration point to a distributed multi-dimensional structure.
2Ease of operation
If pull-based model is used for data retrieval, then clients can request data on demand, but real-time performance deteriorates due to request-response latency
Solution Approach 1:
The patent implements preliminary action by having service proxies proactively push conference data updates to clients as soon as changes occur, without waiting for client requests. The digest log mechanism pre-computes and prepares data updates, which are then immediately pushed to subscribed clients, eliminating the request-response latency inherent in pull-based models.
Solution Approach 2:
The patent employs feedback mechanisms where service controllers monitor digest log changes and trigger automatic push notifications to service proxies, which in turn notify clients of data updates. This feedback loop ensures real-time data synchronization without requiring clients to continuously poll for updates, achieving both real-time performance and operational simplicity.
3Reliability
If digest log updates are pushed to all service proxies, then real-time synchronization is achieved, but control traffic increases
Solution Approach 1:
The patent applies local quality by having service proxies maintain local copies of the digest log and process updates locally rather than forwarding all update traffic to every proxy. Each proxy tailors the synchronization to its local context, pushing only relevant updates to local clients. This maintains synchronization accuracy while reducing redundant control traffic across the network.
Solution Approach 2:
The patent implements partial action by having service controllers push digest log updates only to the specific service proxies that need them, rather than broadcasting to all proxies. The controller determines which proxies require updates based on the digest log changes, sending targeted notifications only where necessary. This reduces control traffic while maintaining the reliability of synchronization for affected proxies.
Data Source
AI summary
A network element (NE) comprising a memory configured to store a digest log for a conference, a receiver coupled to the memory and configured to receive a first message from a first of a plurality of service proxies of the conference, wherein the first message comprises a signature profile of a first of a plurality of participants of the conference associated with the first service proxy, a processor coupled to the receiver and the memory and configured to track a state of the conference by updating the digest log according to the first message, and a transmitter coupled to the processor and configured to send a plurality of second messages to indicate the digest log update to the service proxies without a transmission request from the service proxies.