Video Service Model Sharing in Home Network Gateways

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches to supporting multiple users interacting with interactive digital video services in a home network are expensive due to the need for multiple instantiations of presentation software, leading to increased memory usage and resource requirements.

Innovation Solution

The method involves splitting the video service application into a shareable model component and non-shareable view/controller modules, where a single instance of the model component is instantiated and shared among multiple view/controller modules, reducing resource usage and costs by centralizing the application components in a home network gateway.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent OCAP environments are provisioned per user to support multiple users interacting with interactive digital video services simultaneously, then each user can access video services independently with full functionality, but the cost and resource usage increase linearly with the number of users

Engineering Contradiction:
Improveindependent video service accessVSAvoidmemory footprint
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The application is divided into two distinct parts: a model component that contains shared functionality and a view/controller component that handles user-specific interactions. This segmentation allows the model to be instantiated once and shared among multiple users, while each user gets their own view/controller instance, thereby reducing memory footprint while maintaining independent access to video services.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple view/controller instances are merged to share a single model instance. Instead of each user having a completely independent OCAP environment, the view/controller components from multiple users are combined to interact with a common model, allowing resource sharing while preserving user independence.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If a complete OCAP environment is replicated per user to ensure all cable resources are available at all times, then reliability and functionality are maintained, but the complexity and cost of the system increase

Engineering Contradiction:
Improveresource availabilityVSAvoidsystem architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The OCAP environment is segmented into model and view/controller components, where only the view/controller part is replicated per user while the model remains shared. This reduces system complexity by eliminating the need to replicate entire OCAP environments while maintaining resource availability through the shared model.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The shared model instance serves multiple users simultaneously, acting as a universal resource that provides cable service functionality to all users. This multi-functional approach replaces the need for dedicated OCAP environments for each user, simplifying the overall system architecture.

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

Data Source

PatentUS8776164B2Distributed presentation software for multiple instantiations in home network
Publication Date: 2014.07.08 SONY GROUP CORP
  • US8776164B2 patent drawing
  • US8776164B2 patent drawing
  • US8776164B2 patent drawing

AI summary

One and only instance of a video service model component (for example, an electronic program guide (EPG) model description) is executed in a home network gateway, with multiple instantiations of a view/controller module associated with the model module being generated, one for each display device seeking to simultaneously display the video service. In this way the functionality of a single video service model is shared in the network without requiring the underlying model module itself to be replicated.