KR100978050B1 - Codec and session parameter change - Google Patents

Codec and session parameter change Download PDF

Info

Publication number
KR100978050B1
KR100978050B1 KR1020087014185A KR20087014185A KR100978050B1 KR 100978050 B1 KR100978050 B1 KR 100978050B1 KR 1020087014185 A KR1020087014185 A KR 1020087014185A KR 20087014185 A KR20087014185 A KR 20087014185A KR 100978050 B1 KR100978050 B1 KR 100978050B1
Authority
KR
South Korea
Prior art keywords
time
parameters
set
sdp
service
Prior art date
Application number
KR1020087014185A
Other languages
Korean (ko)
Other versions
KR20080073330A (en
Inventor
마티 타칼라
자니 포이켈라
레이노 주하니 힐투넨
Original Assignee
노키아 코포레이션
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US11/304,639 priority Critical
Priority to US11/304,639 priority patent/US20070168534A1/en
Application filed by 노키아 코포레이션 filed Critical 노키아 코포레이션
Publication of KR20080073330A publication Critical patent/KR20080073330A/en
Application granted granted Critical
Publication of KR100978050B1 publication Critical patent/KR100978050B1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network, synchronizing decoder's clock; Client middleware
    • H04N21/435Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/40Services or applications
    • H04L65/4069Services related to one way streaming
    • H04L65/4076Multicast or broadcast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/60Media handling, encoding, streaming or conversion
    • H04L65/608Streaming protocols, e.g. RTP or RTCP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/235Processing of additional data, e.g. scrambling of additional data or processing content descriptors
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/235Processing of additional data, e.g. scrambling of additional data or processing content descriptors
    • H04N21/2355Processing of additional data, e.g. scrambling of additional data or processing content descriptors involving reformatting operations of additional data, e.g. HTML pages
    • H04N21/2358Processing of additional data, e.g. scrambling of additional data or processing content descriptors involving reformatting operations of additional data, e.g. HTML pages for generating different versions, e.g. for different recipient devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/236Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H04N21/23614Multiplexing of additional data and video streams
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/236Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H04N21/2362Generation or processing of Service Information [SI]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network, synchronizing decoder's clock; Client middleware
    • H04N21/434Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
    • H04N21/4348Demultiplexing of additional data and video streams
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643Communication protocols
    • H04N21/6437Real-time Transport Protocol [RTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1003Signalling or session protocols
    • H04L65/1006SIP

Abstract

Apparatuses and methods are provided for transmitting and receiving timing information corresponding to updating parameters of an electronic service guide (ESG) fragment. The parameters may be associated with a session of a program or service corresponding to the ESG fragment. In one example, the parameters can be updated and timing information, such as an RTP timestamp, can be provided to indicate the time when the parameters can be loaded or fulfilled. In this example, when the RTP timestamp is greater than or equal to the timestamp of the data packet in the data stream, the time for parameter change can be obtained. At this time, new or updated parameters may be loaded into the receiver.

Description

Codec and session parameter change

The present invention generally relates to a communication network. More specifically, the present invention is provided to provide updated parameters corresponding to a session of a program or service.

In general, an electronic service guide (ESG) allows a terminal to communicate to the end-user what services are available and how to access them. ESG fragments are pieces that exist independently of the ESG. Traditionally, ESG fragments include XML documents, but more recently they include numerous items such as, for example, session description protocol (SDP) descriptions, textual files or images. ESG fragments describe one or several aspects of currently available (or future) services or broadcast programs. Such aspects may include, for example, free text descriptions, schedules, geographic availability, prices, purchase methods, genres, and additional information such as preview images or clips. Other types of data, including audio, video and ESG fragments, may be transmitted in accordance with many different protocols over various types of networks. For example, data may be transmitted over a set of networks commonly referred to as the "Internet" using Internet Protocol Suite's protocols, such as Internet Protocol (IP) and User Datagram Protocol (UDP). Data is often sent over the Internet to a single user. But it can be sent to a group of users, commonly known as multicasting. When data is sent to all users it is called broadcast (broadcasting). ESG data may be transmitted using other types of wireless digital networks, including digital broadband broadcast and / or multicast networks.

The service provider provides information about current or future services or content by transmission of corresponding ESG fragments in the data stream corresponding to the event to the subscriber terminal. However, as time passes, changes are made to the event by the service provider. For example, the service provider may change the corresponding service guide or parts thereof, change the service schedule, or promote a particular broadcast service. In addition, it may be desired to change the parameters describing the session rather than having static parameters that remain valid only during the availability of the corresponding service. However, the exact time of the parameter change may not be known so that the corresponding session description files may be loaded at an inappropriate time or the desired content may be unexpectedly unavailable. Users or groups of users often need to be informed of the information that such information or parameter changes are currently supplied.

Thus, there is a need for a method and system for signaling a change in session or some other program or service changes, such as parameters related to a change in content.

The following presents a simplified overview to provide a basic understanding of some aspects of the present invention. This summary is not an extensive overview of the invention. It is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. The following summary merely presents some concepts of the invention in a simplified form as a prelude to the more detailed description that follows.

In one example, a transmitter is provided for transmitting parameters corresponding to a session of a program or service. In this example, a timestamp can be included in a session description protocol (SDP) file and sent to a receiver or subscriber terminal.

In another example, a receiver is provided to receive timing information in an SDP file. Timing information may correspond to time when a set of parameters corresponding to a session of a program or service may be valid. At this time, the set of parameters may be loaded into the receiver.

In another example, updated or new parameters may be sent in the SDP file prior to the time indicated by the timing information in the SDP file. The SDP file may additionally be included in the ESG fragment.

In another example, a transmitter is provided for transmitting an SDP file containing timing information for transmitting a data packet corresponding to a program or service and for loading parameters associated with the program or service at the receiver.

In another example, a receiver is provided to receive a data packet corresponding to a program or service and to load an updated parameter at a time indicated by a timing parameter of an SDF file received from the network.

In another example, a computer readable medium is provided for receiving timing information in an SDP file and for controlling the device to load updated parameters at a desired time.

A more complete understanding of the present invention and its advantages will be obtained by reference to the following detailed description, in view of the following accompanying drawings in which like reference numerals indicate like features.

1 illustrates a block diagram of a wireless communication system in which various aspects of the present invention may be implemented.

2 illustrates a suitable digital broadband broadcast receiver in which one or more illustrative embodiments of the invention may be implemented.

3 shows a schematic diagram of an example of a transport object in which one or more illustrative embodiments of the invention may be implemented.

4 illustrates examples of sending a single transport object in which one or more illustrative embodiments of the invention may be implemented.

5 illustrates an example of a system for generating an SDP file for signaling the time of parameter changes related to a program or service in which one or more illustrative embodiments of the invention may be implemented.

6 illustrates an example of a receiver or subscriber terminal receiving an ESG fragment containing an SDP file in which one or more illustrative embodiments of the invention may be implemented.

7 illustrates an example of an SDP file for transmitting parameters corresponding to a program or service in which one or more exemplary embodiments of the present invention may be implemented.

8 illustrates an example of an SDP file containing timestamp parameters in which one or more illustrative embodiments of the invention may be implemented.

9 illustrates an example of an extension of an SDP file for describing audio parameters in which one or more illustrative embodiments of the present invention may be implemented.

10 illustrates the example of FIGS. 7, 8 and 9 in which new parameters may be transmitted to a receiver or subscriber terminal in an SDP file in which one or more illustrative embodiments of the invention may be implemented.

11 illustrates an example of an updated SDP file in which one or more illustrative embodiments of the present invention may be implemented.

12 is a flowchart illustrating an example of receiving and loading updated parameters in which one or more illustrative embodiments of the invention may be implemented.

13 is a timing diagram illustrating an example of receiving and loading updated parameters in which one or more illustrative embodiments of the invention may be implemented.

14 is a timing diagram illustrating another example of receiving and loading updated parameters in which one or more illustrative embodiments of the present invention may be implemented.

In the following description of the various embodiments, reference is made to the accompanying drawings, which form a part hereof, and which illustrate various embodiments in which the invention may be practiced. It is understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope and spirit of the invention.

Aspects of the present invention may be utilized over a large number of networks and communication protocols. 1 illustrates an example of a wireless communication system 110 in which the systems and methods of the present invention may be employed. One or more network-enabled mobile devices 112, such as personal digital assistants (PDAs), cellular telephones, mobile terminals, personal recorders, portable televisions, personal computers, digital cameras, digital camcorders, portable audio devices, portable radios, or them Are in communication with the service source 122 via the broadcast network 114 and / or the cellular network 116. Mobile terminal / device 112 may comprise a digital broadband broadcast receiver. The service source 122 may be connected to several service providers, which may provide their actual program content or information or a description of their services and programs to the service source and the service source further goes to that content. Or provide information to the mobile device 112. Some service providers may include, but are not limited to, one or more television and / or digital television service providers, digital AM / FM radio service providers, SMS / MMS push service providers, Internet content or access providers.

One way of broadcasting data is to use an IP broadcasting (IPDC) network. IPDC is a combination of digital broadcast and Internet protocol. Through such an IP-based broadcast network, one or more service providers may provide other types of IP services, including online newspapers, radio, and television. These IP services are organized into one or more media streams in the form of audio, video and / or other types of data. To determine when and where these streams occur, users consult the Electronic Service Guide (ESG). One example used in digital video broadcast (DVB) streams is Electronic Program Guide (EPG). One type of DVB is Digital video broadcasting-handheld (DVB-H), which is a recently developed technology that augments the capabilities and services available in small handheld devices, such as mobile phones. DVB-H is designed to deliver 10 Mbps of data to battery powered terminal devices.

DVB transport streams deliver compressed audio, video and data to the user via third party delivery networks. Moving Picture Experts Group (MPEG) is a technology that multiplexes encoded video, audio, and data in a single program with other programs into a transport stream (TS). TS is a packetized data stream comprising a header with fixed length packets. Individual elements of the program, audio and video are each transmitted in packets with a unique packet identification (PID). In order to enable the receiver to place other elements of a particular program in the TS, program specific information (PSI) embedded in the TS is supplied. In addition, a set of tables that adhere to the Supplementary Service Information (SI), MPEG Personal Area Syntax, may be incorporated into the TS. This allows the receiver to correctly process the data contained in the TS.

However, aspects of the invention are also applicable to other digital broadband broadcast systems such as, for example, T-DAB, T / S-DMB, ISDB-T, ATSC, Forward Link Only (FLO), 3GPP MBMS, and 3GPP2BCMCS. Do.

A typical broadcast network (broadcast network) 114 may include wireless transmission of IP datacasting over DVB-H. The broadcast network 114 may broadcast a service, such as a digital or analog television signal, and supplemental content associated with the service via the transmitter 118. The broadcast network may also include a radio, television or IP datacasting broadcast network. The broadcast network 114 may also transmit supplemental content, which may include television signals, audio and / or video streams, data streams, video files, audio files, software files, and / or video games. In the case of transmitting the datacasting service, the service source 122 transmits the actual program content to the user device 112 through the broadcast network 114 and additional information such as user rights and access information for the actual program content to the cellular network ( 116).

The mobile device 112 can also contact the service source 122 via the cellular network 116. The cellular network 116 may include a wireless network and a base station transmitter and receiver 120. The cellular network may include a 2/3 generation (2G / 3G) cellular data communication network, a mobile communication globalization system (GSM) network, a universal mobile communication system (UMTS) or other wireless communication network such as a WLAN network.

In one aspect of the invention, mobile device 112 may include a wireless interface configured to transmit and / or receive digital wireless communications within cellular network 116. Information received by the mobile device 112 via the cellular network 116 or the broadcast network 114 may be configured to transmit user selections, applications, services, electronic images, audio clips, video clips, and / or wireless telephone application interface (WTAI) messages. It may include. As part of the cellular network 116, one or more base stations (not shown) may support digital communication with the receiver 112 while the receiver is located within the management area of the cellular network 116.

As shown in FIG. 2, mobile device 112 may include a processor 128 that is coupled to user interface 130, memory 134 and / or other storage, and display 136. The mobile device 112 may also have a battery 150, a speaker 152 and an antenna 154. The user interface 130 may further include a keypad, a touch screen, a voice interface, one or more arrow keys, a joystick, a data glove, a mouse, a roller ball, a touch screen, and the like.

Computer-executable instructions and data used by processor 128 and other components in mobile device 112 may be stored in computer-readable memory 134. The memory may be implemented in any combination including read only memory modules or random access memory modules and optionally both volatile and nonvolatile memory. Software 140 may be stored in memory 134 and / or storage to provide instructions to processor 128 to enable mobile device 112 to perform various functions. Instead, some or all of the computer executable instructions of mobile device 112 may be implemented in hardware or firmware (not shown).

Mobile device 112 receives, via DVB receiver 141, digital broadband broadcast transmissions based on, for example, a digital video broadcasting (DVB) standard, such as DVB-H, DVB-T, or DVB-MHP, It can be configured to decrypt and process. The mobile device may also be provided with other types of receivers for digital broadband broadcast transmissions. Additionally, receiver 112 may also be configured to receive, decode, and process transmissions via FM / AM radio receiver 142, WLAN transceiver 143, and telecommunications transceiver 144. In one aspect of the invention, mobile device 112 may receive Radio Data Stream (RDS) messages.

In one example of the DVB standard, one DVB 10 Mbit / s transmission may have 200, 50 kbit / s audio program channels or 50, 200 kbit / s video (TV) program channels. Mobile device 112 may be a digital video broadcast-handheld (DVB-H) standard or other DVB standards, such as DVB-MHP, DVB-satellite (DVB), DVB-terrestrial (DVB-T), or DVB-cable (DVB- And may be configured to receive, decode and process the transmission based on C). Similarly, other digital transport formats may be supplementary services such as Advanced Television Systems Committee (ATSC), National Television System Committee (NTSC), Integrated Services Digital Broadcasting (Terrestrial), Digital Audio Broadcasting (DAB), Digital Multimedia Broadcasting. (DMB), Forward Link Only (FLO) or DIRECTV's availability of information and content can be used instead. In addition, digital transmission is time sliced, such as in DVB-H technology. Time-slicing can reduce the average power consumption of the mobile terminal and enable smooth and seamless handover. Time-slicing consists of sending data in bursts using the instantaneous bit rate higher than the required bit rate if the data was transmitted using a traditional streaming mechanism. In this case, the mobile device 112 may have one or more buffer memories to store the decoded time sliced transmission before the presentation.

In one example of the invention, ESG fragments may be delivered to the subscriber station in one or more data streams or channels. In this example, a plurality of channels (such as IP packet streams) can be used to convey the ESG information to the subscriber terminal. For example, an ESG fragment may send a subscriber terminal a notification of upcoming events provided by a service provider, changes in current events provided by a service provider, or updated or ongoing information for a user or group of users. Can provide.

ESG fragments may be delivered to a transport object capable of transmitting ESG information to the container. Thus, ESG fragments can be placed in a container that can be delivered to its own transport object. The container may further include a container header and a container payload, for example, in the container, the container header may provide information about where each container is located in the transport object. In one example, the transport object may include a single container or a plurality of containers, each container including at least one ESG fragment. 3 is a diagram of an example transport object in accordance with at least one aspect of the present invention. As shown in the example of FIG. 3, the transport object 300 may include a container that may have a container header 310 and a container payload 320. In one example, container header 310 and container payload 320 are integrated into a single container 305, which may be integrated into a single transport object 300 such that container header 310 is a transported object where each container is different from the other. They do not need to be recombined with information about where they are located. Instead, the transport object 300 may include a plurality of containers and the container may include any number of ESG fragments 340. Container header 310 may include information related to a corresponding ESG fragment, such as, for example, information about container header 310 itself and / or container payload 320.

In the example shown in FIG. 3, the ESG fragment 340 is contained in the container payload 320. The container header 310 may contain descriptors for identifying and describing the ESG fragment in the corresponding container payload 320. Thus, the properties of the ESG fragment may be identified by, but not limited to, the location of the ESG fragment in the transport object 300 or the length of each contained ESG fragment 340. For example, in one embodiment, the field specifies when a particular ESG starts within the container payload 320 by, for example, providing offset values, start and end points, and the like. In other embodiments, metadata 350 may be associated with individual ESG fragments 340, descriptor entities, ESG fragment 340, or a combination thereof located in or near header 310. In one exemplary embodiment, the association of the 3GPP metadata envelope with the ESG fragment 340 may replace or negate the need for additional metadata located in the header 310 with respect to that particular ESG fragment.

4 shows an example of transmitting a plurality of single transport objects. As illustrated in FIG. 4, the transport object TO of the present invention may be carried in, for example, File Delivery over Unidirectional Transport (FLUTE) sessions, or a pure asynchronous layer encoding (ALC) session. In the example of FIG. 4, ESG root channel data such as IP address, port number and transport session identifier (TSI) may be carried as one of the SI tables of DVB-H, for example in the SI / PSI stream of DVB-H. In the IP / MAC notification table (INT table). The FLUTE session of an ESG root channel includes a file delivery table (FDT) and one or more transport objects (TO) of the session. These transport objects, delivered in announcement carousels, contain access parameters for mapping between different parts of the ESGs and other ESG methods in which ESG data is transmitted. ESGs can be different. For example, ESGs may be in different languages, genres or encodings.

Examples of access parameters may include, for example, an IP address, port number, TSI, start and end times, and the like. So a FLUTE session declares how ESG data is distributed to other sessions. The TOs of the FLUTE session carrying this mapping data are described in the FDT of the FLUTE session. ESG mapping data may be delivered to one or multiple TOs. The mapping can be made as a binary number with XML schemas, plain ASCII text, structured ASCII text such as multipart MIME or MIME headers with enumerated types or through various other means as known in the art. ESG data may in this example be delivered to one or more TOs, which may be, for example, in pure ALC sessions. ESG data or portions thereof may be delivered in one or more FLUTE sessions in addition to or instead of an ALC session in some embodiments of the present invention.

The ESG may further contain a timestamp associated with the transmitted or received data stream. Real time protocol (RTP) timestamps are one such example of timestamps. The time stamp may, for example, indicate a time at which data can be presented or used. For example, an audio or video data stream may contain timestamps indicating the time at which data can be played. The time of presentation or display of the data associated with the timestamp may be further presented with respect to previously received data packets.

The transmitted data stream may further contain parameters for describing the session. Examples of such parameters include decryption parameters that describe the session and / or the corresponding session. These parameters can additionally be sent to receivers in SDP files and SDP files can be grouped with other files in an ESG fragment. SDP files may be sent to the receiver in various ways. For example, one way of transferring an SDP file is to make it a burst separate from the data stream. In this example, a time slice can be created for each service that sends parameters (eg, service parameters) to the SDP file. The time slice transmitting the parameters may be close but separate from the burst or time slice corresponding to the service. Thus, the receiver may receive a burst containing parameters in an SDP file associated with that service prior to receiving a separate time slice burst that transmits the service.

In another example of transferring an SDP file, the SDP file may be included in the same burst as a session. In this example, the SDP file may be included for service, for example at the beginning of a time slice burst. In this way, the receiver or subscriber station receiving the service can receive the corresponding SDP file (and corresponding parameters) as a service at about the same time.

The SDP file and corresponding parameters can be sent to the ESG fragment. The parameters of the SDP file may describe the characteristics of the corresponding program or service, including, for example, session name, purpose, time, media type, format, transport protocol, port number, bandwidth requirement, and the like. However, it may be difficult to update parameters effectively if changes or updates to the parameters are needed. This can be especially problematic in the case of schedule changes, since the exact moment of parameter changes may not be known. Thus, since the exact time of the parameter (or program or service content) may not be known, the corresponding program or service may be loaded at the wrong time or the receiver or subscriber terminal may not be able to play the program or service content. Can be.

In one example of the invention, the time of the desired parameter change associated with the transmitted program or service may be signaled before the time that the change is implemented. In this example, the time of parameter change is signaled with the timestamp of the media stream (eg, RTP timestamps). The time stamp may be included in an SDP file, which may be, for example, in an ESG fragment.

The SDP file can thus provide session and parameter information as well as timing information corresponding to the program or service. As an example of an SDP file for providing such information, the SDP file may include, for example, a parameter corresponding to the origin of the session, which may include a name, a session identifier, an indication of the version of the session, an origin address, or the like. May contain information. The SDP file may also contain parameters or identifiers relating to the location of any information of interest. For example, an SDP file may contain a reference to a web page associated with a program or service. The SDP file may also include a reference to the ESG fragment associated with the program or service.

The SDP file may also contain other parameters or identifiers, such as a destination address or start time for the program or service. In this example, the corresponding program or service becomes available after the indicated start time, but not before the indicated start time. The SDP file may also contain media specific parameters.

In an example of the present invention, the SDP file may further include a parameter for a time stamp. For example, parameters may be provided in the SDP file to indicate when the parameters have changed. The timestamp may be sent to the receiver as soon as a decision on the timestamp is made and prior to the parameter change time. So, in this example, when the correct time for parameter change comes, new or changed parameters may be set as described herein.

Similarly, an ESG fragment containing parameters for time stamps may be received at the receiver or subscriber terminal. This parameter may be contained in an SDP file within an ESG fragment. In this example, after the data packet is received at the receiver or subscriber terminal, the timestamp of the ESG fragment may indicate when the corresponding program or service can be provided or played. The corresponding program or service may be associated with new (or changed) parameters that may change at the start time of the program or service. In this example, the ESG fragment contains a timestamp that signals the parameter change ahead of the time of the parameter change. Thus, even if the exact time of parameter change is not known, the receiver or subscriber terminal may receive parameter change information in advance. In addition, the receiver or subscriber terminal may have an internal delay, such as a buffering delay, that may affect the exact time of parameter change. In this example, parameter change is signaled in advance so that new or changed parameters can be loaded at the appropriate time.

5 shows an example of a system for creating an SDP file to signal the time of parameter change associated with a program or service. In this example, a service is created in service creation module 501. This service can be created with associated parameters for describing the corresponding session. In this example, the generated service may have multiple components including a video component and an audio component. As shown in the example of FIG. 5, a service may include multiple audio components or multiple video components. In this example, two audio components 502 and 503 are provided in the service and one video component is provided 504. Each of the audio components is encoded in audio encoders 505 and 506 and video components are encoded in video encoder 507. Data packets corresponding to a service or media stream may be packetized at packetizers 508, 509, 510. There are many types of encoding that can be implemented. For example, if the original audio is in an analog format, it is digitally encoded (eg, Advanced Audio Coding (AAC), Adaptive Multirate Wideband (AMR-WB) and / or MP3 (MPEG-2, layer 3)). Digitally encoded audio may be transcoded with other codecs and parameters. The resulting audion may have codecs and parameters that may be suitable for the terminal. In another example, a video signal is provided and encoding can include, for example, H.264 or Video Expert Group 4 (MPEG-4), Advanced Video Coding (AVC) or VC-1. . The resulting data packets can be sent to the receiver or subscriber terminal.

In addition, the service may have associated session information. As an example of session information, a service may have a use of a corresponding expected duration. Any description of the session associated with the service may be described as one or more parameters that may be included in the corresponding SDP file. The SDP file corresponding to the service may be generated by the SDP generating module 511. The SDP generation module can receive the corresponding parameters from the service generation module 501 and incorporate those parameters into the SDP file. The SDP generation module 511 may transmit an SDP file to a receiver or a subscriber station. The SDP file can be integrated into the ESG fragment. As mentioned above, the SDP file can be sent in the same burst as the program or service information or in a separate burst.

The time the new parameters are used in this example is added to the SDP file. The SDP file so generated may be transmitted to the receiver or subscriber terminal. Thus, at the indicated time, the parameters can be updated or changed. The parameters can be changed and sent from the encoders 505, 506, 507 to the SDP generation module 511. In addition, a corresponding timestamp may be sent to the SDP generation module 511 at the time of parameter change.

6 shows an example of a receiver or subscriber terminal receiving an ESG fragment containing an SDP file. In this example, the SDP file received at the receiver or subscriber terminal may contain parameters associated with the program or service. The program or service may be associated with parameters that may be changed based on various factors such as, for example, but not by way of limitation, duration of the session or start time of the session. In this example, an ESG fragment is received and SDP information is detected at SDP management module 601. In addition, data packets associated with a program or service may be received at an unpacketizer 602, 603, 604, which may send the data packets to decoders 605, 606, 607. Decoders 605, 606, 607 may further receive parameters from SDP management module 601. The received parameters may describe the corresponding program or service. In addition, the timestamp and / or buffering information may be received by the SDP management module 601 from the depackets 602, 603, 604.

In one example of the present invention, a session and parameter information and timing information describing the exact time for a parameter change associated with a program or service are provided in the SDP file. 7 shows an example of an SDP file for transmitting parameters corresponding to a program or service. In this example, the SDP file may contain other fields or lines for providing the desired information. For example, a typical SDP file may include an "o" line to provide a starting point for a session for a program or service. This line may include the name, session ID, version, and origin address as shown in the example of FIG. In addition, the SDP file may contain a "u" line to provide the location of the identifier or additional information. This may include, for example, a reference to a web page or ESG fragment associated with or describing the program or service. The SDP file may further include a "c" line to provide a destination address. This destination address may describe where the data stream is to be delivered. A "t" line may be provided to provide traditional coarse timing information. This traditional coarse timing information may be a decimal representation of the Network Time Protocol (NTP) and may provide the time the session is available. This field can provide timing information with a precision of 1 second.

The SDP file as illustrated in FIG. 7 may also include an “m” line that can provide any media specific parameters associated with the program or service. The media specification parameters provided in the SDP file may be many and may continue from the "m" line of the SDP file to the end or may continue on a subsequent "m" line. Media specific parameters may include any parameter for describing the characteristics of the program or service. This may include, for example, parameters for indicating audio encoding, video encoding, and the like. Some examples of media specific parameters include IP address and port, encoding (codec), sampling frequency, bit rate, and mode (e.g. mono, stereo, etc.).

As shown in the example of FIG. 8, timestamp parameters are provided in the SDP file. The time stamp in this example is an RTP time stamp to provide the exact start time of the corresponding program or service. In the example shown in FIG. 8, the RTP timestamp is called startRtpStamp and is provided with a typical value of 12345678. In this example, the extended SDP file is shown including a description of the video parameters including the startRtpStamp RTP timestamp.

9 shows an example of extension of an SDP file to describe an audio parameter including a startRtpStamp typical timestamp. In the examples shown in FIGS. 7, 8 and 9, a receiver or subscriber receiving an SDP file having timestamp parameters as described (eg, video timestamp parameter of 12345678 and audio timestamp parameter of 12345432). The terminal may use the coarse timing parameter "t" as an approximation of the time of initiation of the program or service.

10 shows an example of FIGS. 7, 8 and 9 in which new parameters may be transmitted to a receiver or subscriber terminal in an SDP file. In this example, the new session version is displayed. The new session version data may indicate that the SDP contains new information. In this example, the SDP file contains new information containing new information in the "u" line to indicate an address for additional information corresponding to the ESG fragment. Also, in this example, the "t" line (ie, coarse timing information) as well as various media specific parameters have been updated.

After the exact time for parameter change is known, an updated SDP file can be provided. 11 shows an example of an updated SDP file after the exact time stamp of the parameter change is known. In this example, the session version was updated as well as the timestamp parameter.

12 shows another example of one aspect of the present invention. In this example, the parameters describing the program or service of the ESG fragment are included in the ESG fragment to provide time when the parameters can be changed or updated. This timestamp may be included in the SDP file in the ESG fragment. As shown in FIG. 12, the receiver or subscriber station may receive a data packet containing a timestamp (step 1201). The receiver may also receive the timestamp of the SDP file as an ESG fragment signaling a time for change of parameters associated with the corresponding program or service (step 1202). The receiver may compare the timestamp of the data packet with the timestamp received in the SDP file indicating the time for parameter change (step 1203). If the timestamp of the data packet is less than the timestamp in the SDP file indicating the time of parameter change (“No” branch in step 1203), the receiver can wait for the timestamp of subsequent data packets to increase. If the timestamp of the data packet is greater than the timestamp in the SDP file indicating the time for parameter change (“YES” branch in step 1203), the time for parameter change has been reached and new parameters can be loaded. (Step 1205). In addition, the receiver can estimate the processing delay (step 1204) and wait for an appropriate amount of time before loading new parameters. One example of a processing delay may include a buffering delay.

13 is a timing diagram illustrating another example. In this example, the encoder generates a data stream at time t (0). This initial data stream may contain an ESG fragment containing parameters describing the session. These parameters may be in the SDP file of the ESG fragment. The parameters may include RTP (O) which is a timestamp parameter as shown with initial values. The data stream may be transmitted to a receiver or subscriber terminal as shown in FIG. In this example, the receiver / terminal receives the data stream with initial parameters at time t (0) when the data stream is transmitted in the network. As described above, the data stream may contain a timestamp parameter (eg, RTP (O)).

At time t (l) later than time t (0), a change in the parameters of the SDP file or the ESG fragment may be desired at some time. In this example, new parameters may be determined but the transition time of the new parameters may not be determined. For example, the exact time of the new program or the end of the current program or service may not yet be determined at time t (l) so that the time for the implementation of the corresponding new parameter may not be known at time t (l). . Examples of new parameters include, for example, schedule information or validity information. Thus, in this example, the receiver / terminal receives via the network new parameters starting at time t (l). However, at time t (l), the time for the implementation of the new parameters is not yet known so the receiver / terminal does not load new parameters this time. Rather, the receiver / terminal loads the currently valid current parameters. New or future parameters may be available but may not be shown as valid at this time.

At time t (2) in this example (later than time t (1)), the exact time for the parameter change is determined and thus the parameters of the SDP file or ESG fragment can be updated. In this example, the timestamp parameter of the SDP file of the ESG fragment can be updated to indicate the time for the parameter change. The timestamp parameter is updated at time t (2) and sent to the receiver / terminal. In this example, the time for parameter change is time t (3) which is after time t (2). Thus, the data stream received at time t (2) at the receiver / terminal contains a timestamp parameter indicating time t (3) as the time for parameter change. At this point, the receiver / terminal continues to load the current parameters because the time for parameter change (ie time t (3) in this example) has not yet occurred.

Thus, as described, the receiver / terminal decodes the ESG fragment and SDP of this example containing a timestamp parameter indicating the exact time for parameter change (e.g., RTP (1) in this example). To receive). Also at this time, the receiver / terminal receives the new parameters with a timestamp RTP 1 indicating the exact time for the implementation of the new parameters. Thus, the time for changing the parameter of the ESG fragment is represented as RTP 1 by the timestamp parameter of the SDP file of the ESG fragment in this example. New parameters may be implemented at time t (3) at the receiver / terminal based on the timestamp RTP (1) received in the ESG fragment. For example, when the timestamp of the received data packet is greater than or equal to the timestamp RTP (I) received by the ESG fragment (ie, t (3) has been reached), new parameters are set in the encoders and the receiver / terminal is Set new parameters to the decoder.

14 shows a timing diagram of another example. In this example, data or RTP packets are sent from the transmitter to the receiver or subscriber terminal. Each of the RTP packets contains an RTP timestamp for indicating the time of the RTP packet. In addition, SDP files are transmitted to the receiver / terminal. As FIG. 14 shows in this example, the SDP file, SDP curr1, is sent to the receiver / terminal and contains parameter set 1 for describing the corresponding session. The parameters of SDP curr1 are valid for the current RTP packet stream. In this example, each of the TRP time stamps of the RTP packet stream is compared with the time stamp parameter of SDP curr1. At this time, the timestamp parameter of SDP curr1 is less than the timestamp of the RTP packet stream.

SDP next1 represents the SDP file that is sent when it is determined that a parameter change has occurred. SDP next1 is transmitted in advance of the time when the parameter change occurs as shown in FIG. 14, however, the exact time of the parameter change may not be known at this time. SDP next1 may contain a new set of parameters (ie, parameter set 2 in this example) and coarse timing information to provide an approximate time of parameter change. At subsequent times, the exact time of the parameter change can be determined. In this example, after the exact time of the parameter change has been determined, SDP next1.1 containing the correct time information is sent. For example, SDP next1.1 may contain an updated timestamp parameter to indicate the exact time of the parameter change. Any number of updates to the time for parameter change can be made. For example, additional SDP files following SDP next1.1 may be sent with additionally updated time stamp information as the exact time of the parameter change is changed. Instead, the exact time of the parameter change can be known initially and an updated RTP timestamp indicating the correct time can be included in the SDP next1 SDP file.

At the time of parameter change, the timestamp of the RTP packet stream can be compared with the timestamp parameter of the SDP file (in this example, SDP next1.1). The timestamp of the RTP packet stream, which is less than or equal to the timestamp parameter of the SDP file, may indicate to the receiver / terminal that the time for parameter change has been reached. In this case, the receiver / terminal may know what parameter set is currently present from the timestamp information. Since the time of parameter change has been reached, parameter set 2 is now the current parameter set in this example. In another example, there may be different versions of parameters and different versions of parameter sets may overlap in time. There are many ways to determine the proper set of parameters when different versions exist. For example, the version number can be associated with the SDP file or with parameter sets in the SDP files. In one example, the highest version number indicates the current set of parameters. Instead, the additional information may indicate a current set of parameters, such as information corresponding to the ESG fragment.

In the current example shown in Fig. 14, a new parameter set (set (parameter set 2) is loaded after the time of parameter change. So, SDP curr2 contains a new parameter set 2. If subsequent parameters If a change is desired, SDP next2 may be sent, which may contain the exact time for the second parameter change, which may further include coarse timing information to indicate an approximate time for the parameter change. When the exact time for the parameter change is known, the timestamp parameter can be updated into the SDP file and SDP next2 can be transferred In this example, SDP next2 can contain the next set of parameters. When a time for a second parameter change is reached (e.g., a comparison of timestamps may be performed to compare the timestamps of the RTP packet stream with the timestamps of the SDP files). Based on T), the following set of parameters may be implemented.

The present invention includes any novel feature or combination of features disclosed herein, either expressly or by generalization thereof. Although the present invention has been described with respect to specific examples, including presently preferred forms of carrying out the invention, those skilled in the art will recognize that there may be numerous modifications and substitutions of the systems and techniques described above. Thus, the spirit and scope of the invention should be construed broadly as mentioned in the appended claims.

Claims (30)

  1. A method for transmitting parameters for describing a session of a program or service, the method comprising:
    Receiving a timestamp corresponding to the exact time for updating a parameter corresponding to the program or service;
    Inserting the timestamp in a session description protocol (SDP) file; And
    Transmitting the SDP file.
  2. The method of claim 1, wherein transmitting the SDP file comprises transmitting the SDP file in an electronic service guide (ESG) fragment.
  3. 2. The method of claim 1, wherein the timestamp is a real time protocol (RTP) timestamp.
  4. The method of claim 1, wherein the SDP file includes a first set of parameters at a first time and a second set of parameters and a time parameter at a second time later than the first time, wherein the time parameter is And when the second set of parameters is valid.
  5. A method for changing a first set of parameters corresponding to a session of a program or service to a second set of parameters, the method comprising:
    Receiving a data packet corresponding to a program or service, the data packet comprising a time of the data packet;
    Receiving a session description protocol (SDP) file, the SDP file including first timing information corresponding to a time for changing a first set of parameters; And
    Changing a first set of parameters based on first timing information and time of the data packet.
  6. 6. The method of claim 5, wherein changing comprises updating the first set of parameters based on comparing first timing information to the time of the data packet.
  7. 7. The method of claim 6, wherein the SDP file includes a second set of parameters.
  8. 8. The method of claim 7, wherein updating comprises loading a second set of parameters if first timing information is greater than the time of the data packet.
  9. 6. The method of claim 5, wherein the method further comprises estimating a processing delay, wherein the changing comprises updating the first set of parameters after the processing delay has elapsed.
  10. 6. The method of claim 5, wherein the SDP file includes a second set of parameters and modifying includes loading the second set of parameters into a receiver.
  11. 6. The method of claim 5, wherein the first set of parameters is a source of the session, name of the session, version, address, identifier, location of additional information, destination address, coarse timing, schedule information, validity information, or medium-specific parameters. At least one of the origins of the variables.
  12. 6. The method of claim 5, wherein the time of the data packet includes a real time protocol (RTP) timestamp.
  13. 6. The SDP file of claim 5, wherein the SDP file comprises a first set of parameters and the step of receiving the SDP file comprises the step of receiving the SDP file at a current time, wherein the current time is greater than the time corresponding to the first timing information. Method characterized by preceding.
  14. 15. The apparatus of claim 13, wherein the SDP file includes a second set of parameters preceding a time corresponding to the first timing information, wherein the second set of parameters corresponds to the first set of modified parameters. Way.
  15. 14. The method of claim 13, further comprising receiving a second set of parameters at a current time.
  16. 14. The method of claim 13, wherein the SDP file includes a second set of parameters after the current time.
  17. 15. The method of claim 14, wherein the method comprises loading a second set of parameters into a receiver at or after a time corresponding to the first timing information.
  18. In the transmitter for transmitting the parameter for describing the session of the program or service,
    A session description protocol (SDP) module for generating an SDP file;
    An encoder for transmitting a data packet corresponding to a program or service,
    The SDP file includes a first set of parameters at a first time and a second set of parameters and a time parameter at a second time later than the first time, wherein the time parameter is a valid second set of parameters. Transmitter to indicate when.
  19. 19. The transmitter of claim 18, wherein the time parameter indicates a corresponding third time when the second set of parameters is valid, wherein the third time is later than the second time.
  20. 20. The transmitter of claim 19, wherein the SDP file includes a second set of parameters between a second time and a third time.
  21. A receiver for receiving parameters corresponding to a session of a program or service, the receiver comprising:
    An SDP manager for receiving an SDP file, the SDP file including a first set of parameters corresponding to session and time parameters of a program or service; And
    A decoder for decoding a data packet corresponding to a program or service, wherein the data packet includes a decoder including a timestamp,
    And the SDP manager loads the first set of parameters into the decoder when the time parameter is greater than or equal to the timestamp.
  22. 22. The receiver of claim 21 wherein the SDP manager loads a first set of parameters into the decoder after a delayed period after the timestamp.
  23. 23. The receiver of claim 22 wherein the period corresponds to a buffering delay.
  24. 22. The receiver of claim 21 wherein the SDP manager receives a timestamp from the decoder and compares the timestamp with a time parameter received in the SDP file.
  25. 22. The receiver of claim 21 wherein the time stamp comprises a real time protocol (RTP) time stamp.
  26. 22. The receiver of claim 21 wherein the SDP file includes a first set of parameters at a first time, wherein the first time corresponds to a time indicated by a timestamp and is less than a time indicated by a time parameter.
  27. 27. The receiver of claim 26 wherein the SDP file includes a time parameter at a first time.
  28. A computer readable storage medium having stored thereon a computer program comprising computer readable instructions, the computer readable instructions being executed by a computer,
    Receiving at the receiver a data packet corresponding to a program or service, the data packet comprising a time of the data packet;
    Receiving a session description protocol (SDP) file, the SDP file comprising a first set of parameters and the first timing information corresponding to a time for loading the first set of parameters; And
    And loading the first set of parameters into a receiver based on first timing information and time of the data packet.
  29. 29. The computer readable storage medium of claim 28, wherein the first set of parameters is loaded into a receiver when a time of the data packet is greater than or equal to first timing information.
  30. 30. The computer readable storage medium of claim 29, wherein the SDP file includes a first set of parameters prior to a time corresponding to timing information.
KR1020087014185A 2005-12-16 2006-11-16 Codec and session parameter change KR100978050B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US11/304,639 2005-12-16
US11/304,639 US20070168534A1 (en) 2005-12-16 2005-12-16 Codec and session parameter change

Publications (2)

Publication Number Publication Date
KR20080073330A KR20080073330A (en) 2008-08-08
KR100978050B1 true KR100978050B1 (en) 2010-08-25

Family

ID=38163277

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020087014185A KR100978050B1 (en) 2005-12-16 2006-11-16 Codec and session parameter change

Country Status (6)

Country Link
US (1) US20070168534A1 (en)
EP (1) EP1961217A4 (en)
JP (1) JP2009519654A (en)
KR (1) KR100978050B1 (en)
CN (1) CN101529895A (en)
WO (1) WO2007069009A2 (en)

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE0402876D0 (en) * 2004-11-25 2004-11-25 Ericsson Telefon Ab L M TV-like standards-compliant unicast streaming over IP
FR2880716A1 (en) * 2005-01-13 2006-07-14 Gemplus Sa Personalization service in a terminal device
US7624417B2 (en) 2006-01-27 2009-11-24 Robin Dua Method and system for accessing media content via the internet
US20070207727A1 (en) * 2006-02-01 2007-09-06 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving notification message in a mobile broadcast system
CN100571438C (en) * 2006-02-22 2009-12-16 华为技术有限公司 Method for subscribing to and buying objects in mobile broadcasting multicast service
US20070260674A1 (en) * 2006-05-02 2007-11-08 Research In Motion Limited Push framework for delivery of dynamic mobile content
KR100827100B1 (en) * 2006-06-20 2008-05-02 삼성전자주식회사 Method and system for providing esg in dvb-h
KR101419287B1 (en) * 2006-07-07 2014-07-14 삼성전자주식회사 Apparatus and method for providing IPDC service and apparatus and method for processing IPDC service
KR100800857B1 (en) * 2006-08-18 2008-02-04 삼성전자주식회사 Method for providing notification message in dvb-h system and the system therefor
EP1901455B1 (en) * 2006-09-18 2018-10-31 Samsung Electronics Co., Ltd. Digital video broadcasting system, digital video broadcasting terminal, and method for providing file information in file download service
KR100810359B1 (en) * 2006-09-19 2008-03-04 삼성전자주식회사 Method for transmitting notification data in dvb-h system and the system therefor
US8046479B2 (en) * 2006-11-07 2011-10-25 Telefonaktiebolaget Lm Ericsson (Publ) Media channel management
US7903574B2 (en) * 2007-03-15 2011-03-08 Nokia Corporation Service discovery mechanism in broadcast telecommunication network
US20100130122A1 (en) * 2007-06-01 2010-05-27 Thomson Licensing Llc Apparatus and method for performing power managment in a receiver
KR101461958B1 (en) * 2007-06-29 2014-11-14 엘지전자 주식회사 Digital broadcasting system and method of processing data in digital broadcasting system
KR101429767B1 (en) * 2007-09-21 2014-08-19 삼성전자주식회사 Method for transmitting and receiving electronic service guide and digital broadcasting system therefor
CN100550860C (en) * 2007-11-27 2009-10-14 华为技术有限公司 Media resource reservation method and service package information acquisition method and device
WO2011075670A1 (en) * 2009-12-18 2011-06-23 Google Inc. Matching encoder output to network bandwidth
SG185678A1 (en) * 2010-06-21 2012-12-28 Nokia Corp Method and apparatus for changing the configuration of an ongoing streaming session
US9712891B2 (en) * 2011-11-01 2017-07-18 Nokia Technologies Oy Method and apparatus for selecting an access method for delivery of media
US9608893B2 (en) * 2012-02-27 2017-03-28 The Boeing Company Methods and systems for parsing data objects
US9544641B2 (en) * 2012-05-10 2017-01-10 Humax Co., Ltd. Hybrid transmission method through MMT packet format extension
US9258287B2 (en) * 2012-12-20 2016-02-09 Broadcom Corporation Secure active networks
KR101752435B1 (en) 2013-11-01 2017-07-03 엘지전자 주식회사 Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals
JP6454683B2 (en) * 2014-02-28 2019-01-16 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America Voice communication terminal, intermediate node, processing device, connection method and program
WO2016060416A1 (en) * 2014-10-12 2016-04-21 엘지전자 주식회사 Device for transmitting broadcast signal, device for receiving broadcast signal, method for transmitting broadcast signal, and method for receiving broadcast signal

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050090235A1 (en) * 2003-10-27 2005-04-28 Larri Vermola Apparatus, system, method and computer program product for service selection and sorting

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60233822D1 (en) * 2001-12-11 2009-11-05 Ericsson Telefon Ab L M Method of right management for streaming media
US20030211856A1 (en) * 2002-05-08 2003-11-13 Nokia Corporation System and method for facilitating interactive presentations using wireless messaging
GB2390785B (en) * 2002-07-12 2005-10-19 * Nokia Corporation Information service broadcasting or multicasting
KR100742244B1 (en) * 2002-12-18 2007-07-24 노키아 코포레이션 Method of announcing sessions
WO2004077790A1 (en) * 2003-02-26 2004-09-10 Koninklijke Philips Electronics N.V. System for broadcasting multimedia content
US20040260827A1 (en) * 2003-06-19 2004-12-23 Nokia Corporation Stream switching based on gradual decoder refresh
WO2005045603A2 (en) * 2003-10-27 2005-05-19 Nokia Corporation Apparatus, system, method and computer program product for service selection and sorting
GB2407745A (en) * 2003-10-28 2005-05-04 Nokia Corp Method of providing an electronic service guide in a datacasting system
US20050283535A1 (en) * 2004-06-17 2005-12-22 Michele Covell Method and system for interactive control of media over a network
US7827579B2 (en) * 2004-09-09 2010-11-02 Nokia Corporation Mobile television electronic service guide delivery system
US7613112B2 (en) * 2005-06-28 2009-11-03 Nokia Corporation Optimizing playback startup time of bursty real-time streams
US8994879B2 (en) * 2005-10-21 2015-03-31 Thomson Licensing Method and apparatus for audio and video synchronization timestamp rollover correction

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050090235A1 (en) * 2003-10-27 2005-04-28 Larri Vermola Apparatus, system, method and computer program product for service selection and sorting

Also Published As

Publication number Publication date
WO2007069009A3 (en) 2007-09-27
JP2009519654A (en) 2009-05-14
EP1961217A4 (en) 2011-02-09
EP1961217A2 (en) 2008-08-27
KR20080073330A (en) 2008-08-08
WO2007069009A2 (en) 2007-06-21
US20070168534A1 (en) 2007-07-19
CN101529895A (en) 2009-09-09

Similar Documents

Publication Publication Date Title
EP2854408B1 (en) Information processing apparatus, data management method, and program
KR100831657B1 (en) Method, network element and system for transmitting a burst in communication network, method of operating a receiving device in a communication network, computer readable medium therefor and a handset
US10356453B2 (en) Apparatus and method for configuring a control message in a broadcast system
RU2486678C2 (en) Mapping network information between data link and physical layer
US8159982B2 (en) Method, system and network entity for providing digital broadband transmission
KR20100037659A (en) Method and apparatus for hierarchical transmission/reception in digital broadcast
RU2384953C2 (en) Method of delivering message templates in digital broadcast service guide
Kornfeld et al. DVB-H and IP datacast—broadcast to handheld devices
KR100922532B1 (en) Method, apparatus, and storage medium for datacasting and operating terminal for receiving datacast services, and the terminal
EP2259494A2 (en) Method and system for transmitting and receiving access information for a broadcast service
CA2518034C (en) Method, system and network entity for indicating hierarchical mode for transport streams carried in broadband transmission
US20050129042A1 (en) System and associated terminal, method and computer program product for controlling memory for storage of content
EP1916842B1 (en) Program guide browser
EP1922827B1 (en) Signalling of cell id in digital mobile broadcast service guide for localized broadcasting
US9955220B2 (en) Device and method for receiving media content
JP6092122B2 (en) Transmission method and apparatus for broadcasting / communication integrated service
US8498220B2 (en) Service discovery mechanism in broadcast telecommunication network
US8320819B2 (en) Mobile TV channel and service access filtering
US9900166B2 (en) Methods for delivery of flows of objects over broadcast/multicast enabled networks
KR100923061B1 (en) Method and computer readable medium for transporting fragments of an ESG and constructing an ESG at a mobile terminal, system for distributing ESG data and mobile device for receiving ESG data
KR20080041728A (en) Enhanced signaling of pre-configured interaction message in service guide
US8270343B2 (en) Broadcasting of textual and multimedia information
KR20060108700A (en) System and associated terminal, method and computer program product for providing broadcasting content
KR20090009922A (en) Method and system for providing quick service access
US7614068B2 (en) Prioritization of electronic service guide carousels

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant
LAPS Lapse due to unpaid annual fee