Event Identifier Generation Using Time-Partitioned Counters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing DVB standard's limited event identifiers lead to non-unique identifiers over time, causing issues in referencing events, especially when program schedules change, and requiring additional bandwidth and infrastructure support for unique identification.
Innovation Solution
Generating a unique identifier based on a function of the original time reference and the first identifier, using a set of identifiers with a predetermined repetition period, and partitioning time into blocks with different classes to ensure identifier uniqueness across time changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If event identifiers are reused periodically to save bandwidth, then bandwidth usage is reduced, but identifier uniqueness over time is lost
Solution Approach 1:
The identifier system is segmented into two distinct parts: a compact periodic event identifier (for bandwidth efficiency) and a monotonically increasing counter (for uniqueness). This segmentation allows each component to fulfill its specific function - the periodic identifier saves bandwidth while the counter ensures uniqueness across time periods.
Solution Approach 2:
The solution adds a temporal dimension to the identifier system by introducing a monotonically increasing counter that evolves over time. This transforms the identifier from a static periodic value to a dynamic composite identifier that incorporates time-based uniqueness, resolving the contradiction between periodic reuse and long-term uniqueness.
2Adaptability or versatility
If program schedules change, then adaptability is improved, but identifier reliability deteriorates
Solution Approach 1:
The system performs preliminary action by pre-generating a large space of unique identifier combinations through the counter mechanism. This allows the system to adapt to schedule changes without collision risks, as the pre-established unique identifier space can accommodate rescheduling without affecting reference accuracy.
3Reliability
If additional infrastructure is added to ensure unique identifiers, then identifier uniqueness is improved, but system complexity increases
Solution Approach 1:
The system achieves self-service by generating unique identifiers through a deterministic algorithm that combines the periodic event identifier with a monotonically increasing counter. This eliminates the need for external infrastructure or centralized assignment mechanisms, as each system can independently generate unique identifiers using the defined algorithm.
Solution Approach 2:
The solution changes the parameters of the identifier system by introducing a temporal parameter (the counter) that evolves independently of the periodic identifier. This parameter change allows the system to maintain uniqueness without additional infrastructure, as the counter provides the necessary differentiation across time periods.
Data Source
AI summary
A method in a network entity associates a unique identifier with an event, for example a television program. The method comprises the steps of receiving an original time reference allocated to the event, for example an original start time for the event, and generating a first identifier (event_ID) to identify the event, wherein the first identifier is based on a set of first identifiers (event_IDs) that have a predetermined repetition period. The method further comprises the step of generating a second identifier (program_ID) to identify the event, wherein the second identifier is unique over time and based on a function of the first identifier and the original time reference allocated to the event. Various embodiments describe how changes to the original time reference can be made, yet still allow the unique event identifier to be determined.