Logical Layer Pipes for Broadcast Service Component Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current broadcast protocols require all service components of a service to be mapped to the same physical layer pipe, limiting resource efficiency and inhibiting the application of different error correction or error protection protocols to different components, as well as preventing the sharing of service components between services.
Innovation Solution
The implementation of logical layer pipes (LLPs) allows service components to be mapped to multiple physical layer transmission channels, enabling different services to share components and apply varying error correction protocols, while also enabling receivers to discover and access the appropriate physical layer pipes (PLPs) for each service component.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If all service components of a service are mapped to the same physical layer pipe, then the protocol implementation is simple, but resource utilization is poor and components cannot be shared between services
Solution Approach 1:
The patent segments the mapping relationship by introducing logical layer pipes (LLPs) as an intermediate layer between service components and physical layer pipes (PLPs). This segmentation allows service components to be independently mapped to different PLPs through multiple LLPs, enabling component sharing between services while maintaining protocol simplicity through the structured LLP-PLP mapping framework
Solution Approach 2:
The patent implements universality by allowing a single service component to be shared across multiple services through multiple LLPs. The service component becomes a universal resource that can be accessed by different services via their respective LLPs, eliminating the need for duplicate components and improving resource utilization
2Device complexity
If all service components are mapped to the same physical layer pipe, then the mapping structure is uniform, but different error correction or error protection protocols cannot be applied to different components
Solution Approach 1:
The patent segments the error correction application by allowing different LLPs to apply different error correction or error protection protocols to different service components, even when those components are mapped to the same PLP. This segmentation enables tailored error protection for each component while maintaining the uniform PLP structure
Solution Approach 2:
The patent implements local quality by allowing different error correction protocols to be applied to different service components based on their specific requirements. Each component can have its own error protection characteristics while being transmitted through the same physical layer pipe, optimizing reliability for each component type
3Reliability
If service components cannot be shared between services, then each service has dedicated resources, but the resources necessary to broadcast multiple services increase
Solution Approach 1:
The patent merges service components across multiple services by allowing the same component to be shared through multiple LLPs. This merging reduces the total quantity of resources required to broadcast multiple services, as duplicate components are eliminated while maintaining service integrity through the LLP mapping structure
Solution Approach 2:
The patent enables service components to serve multiple services simultaneously through the LLP mechanism. A single service component can be universally accessed by multiple services via their respective LLPs, reducing resource duplication while maintaining dedicated access paths for each service
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Services and service components in a broadcast network may be mapped to disparate physical layer transmission channels (PLPs) using logical layer pipes (LLPs). The use of LLPs allows different service components of a single service to be mapped to physical layer transmission channels (PLPs). Accordingly, service components may be shared among different services. Additionally or alternatively, different functions (e.g., different error detection or correction protocols) may be applied to each service components of a service. A receiver may identify services, service components and corresponding PLPs based on LLP identifiers. The receiver may then access and receive desired services and service components through the identified PLPs.