Service Discovery Record for Digital Content Transmission
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital content transmission and reception systems face limitations in efficiently transmitting and receiving service event information, particularly in hybrid services combining digital broadcasting and IPTV, due to the conventional method's network burden and restrictions on providing such services.
Innovation Solution
A method and apparatus for transmitting and receiving digital contents using IP protocol, which involves generating and parsing service discovery records to obtain service event information, including identifiers, start times, durations, and parental ratings, allowing for efficient transmission and reception of digital content services over IP networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If service event information is included in a multicast stream of live media broadcasting, then service event information can be transmitted, but a large amount of service event information places a burden on network usage
Solution Approach 1:
The patent segments service event information from the main digital content stream by introducing a separate service discovery record structure. This allows service event information to be extracted and processed independently from the multicast stream, reducing the network burden while maintaining reliable transmission of essential service information.
Solution Approach 2:
The patent extracts service event information from the multicast stream and places it into a dedicated service discovery record. This extraction separates the service information transmission from the content delivery, allowing efficient handling of service event data without burdening the network with redundant information in both streams.
2Loss of information
If service event information is acquired using the conventional method, then event information can be obtained, but it places restrictions on the provision of hybrid services
Solution Approach 1:
The service discovery record structure is designed to be universal and adaptable, supporting multiple service types including hybrid services that combine digital broadcasting and IPTV. The record can accommodate various service event information formats and types, enabling flexible provision of diverse services without restriction.
Solution Approach 2:
The patent introduces a dynamic service discovery mechanism where the service discovery record can be updated and parsed independently of the multicast stream. This dynamic approach allows the system to adapt to different service configurations and types, including hybrid services, by flexibly processing service event information as needed.
3Loss of information
If a large amount of service event information is transmitted through the multicast stream, then complete service information is available, but it increases network load and reduces transmission efficiency
Solution Approach 1:
The patent extracts service event information from the multicast stream and consolidates it into a separate service discovery record. This extraction ensures that complete service information is preserved while transmitting it through a dedicated, efficient channel that does not burden the network with redundant data in both the content stream and service information.
Data Source
AI summary
A method of transmitting/receiving digital contents and an apparatus for receiving the digital contents are disclosed. In a system connected with an Internet protocol (IP) network, service event information may be included in a service discovery record and transmitted/received. Accordingly, the apparatus for receiving the digital contents can receive a service using the service event information in a service discovery step when receiving the service including the digital contents. Since the service event information can be processed independence of the digital contents included in the service, the service can be rapidly provided and unnecessary service event information does not need to be parsed.


