Motorola Mobility Confidential Restricted.

Media Player URL Format

When starting to play,record or distribute streaming media the source location of the media and associated source parameters are required. This information is passed in by the application using source URLs. The following describes the format of these URLs for different types of service formats. The current KreaTV extended URI format is explained below:

foo: This part of the URL defines the scheme. The current schemas that are supported include http, dvr, rtsp, dvb, rtp, atsc and ip. Please note that not all schemes are supported on all KreaTV platform variants. The scheme must be specified.

streaming_source: This part of the URL defines either the DVR asset, tuning_parameters or address and port information associated with the source content. The streaming_source must be specified for all schemes.For more details see each scheme definition.

query parameters: This part of the URL definition provides optional parameters. These parameters are initially delimited by using the '?' delimiter. For backwards compatability, a '&' is still accepted in this position. For more details see each scheme definition.

morequeryparams: This part of the URL definition provides for additional parameters. Additional parameters are delimited by using the '&' delimiter. For more details see each scheme definition.

optional parameters: This part of the URL definition provides for optional parameters. The beginning of the optional parameter list is delimited by using the '|' delimiter in place of a '&', or if the first parameter, in place of the '?'. This delimiter has a special meaning when constructing streaming sessions; for purposes of session reuse, all parameters after the '|' will NOT be considered when determining if a session URL is duplicated (and can thus be reused). For more details see each scheme definition.

In general, the URL passed in to create a media session will be functionally available to all interested parties by calling TToiMediaSession->GetUrl(). This is true except in the case if the URL has "SessionMode" parameter or "Reusable" parameter. When these parameters are included in the URL string, they will be stripped out before the URL is stored in the created media session.

"Reusable" parameter typically used as 'Reusable=NO', indicates the session is exclusively owned by the creator and will not be considered for session reuse."SessionMode" parameter is used to carry session specific details in the url. 'SessionMode=AttachOnly' indicates the session should only be attached to an existing session with the matching URL.

RTSP

RTSP is a session management protocol for streaming and is implemented by many video servers including Kasenna MediaBase, Concurrent and NCUBE. RTSP URLs have the following syntax:

rtsp://<host>[:<port>]/<content path>[?<queryparam>=value][&<queryparam>=value]*][|<parameter>=value[&<parameter>=value]*]

where

  • <host> is the video server IP number or host name
  • <port> is the relevant port number for the server. If no port is specified, then 554 (the standard for RTSP) is used.
  • <content path> is the path and file name for the content
  • Player parameters (<parameter>) are optional. For details see the list of parameters.

Each parameter is separated by an ampersand (&). For details see the list of parameters.

Example:

rtsp://my-vod-server.com/movies/shrek

Multicast

Multicast streaming is in many ways similar to RTSP but sessions are managed with the standard IGMP multicast join and leave operations. Multicast URLs have the following simplified syntax:

igmp://<multicast address>:<port>[?<queryparam>=value][&<queryparam>=value]*][|<parameter>=value[&<parameter>=value]*]

where

  • <multicast address> is the IP address of the multicast stream

Note! Address digits must be written without initial zeros to be treated as dotted decimal form. The following address is NOT in correct dotted decimal form: 0224.010.01.01 (it is actually in dotted octal form)

  • <port> is the destination port number of the multicast stream

Note! Port number must be above 1024

For details see the list of parameters.

Example:

igmp://239.1.1.1:5201

Singlecast

Singlecast streaming accepts unicast UDP encapsulated streams sent to a local IP address. Singlecast URLs have the following syntax:

udp://<singlecast_address>:<port>[?<queryparam>=value][&<queryparam>=value]*][|<parameter>=value[&<parameter>=value]*]

Where

  • <singlecast_address> is the destination IP address of the singlecast stream
  • <port> is the destination port number of the singlecast stream
  • Query parameters (<queryparam>) are optional and may contain 0 or more of the following:
    1. "if=<flag>" - Interface binding flag. If present and <flag> is non-empty, destination filtering is performed against the singlecast address and destination port. Otherwise, destination filtering is performed against the destination port only.
    2. "source=<sourceIp>:<sourcePort>" - Stream source information. If present, source filtering is performed against the source IP and Port. Otherwise, no source filtering is performed.
  • Query parameters and player parameters (<parameter>) are optional. For details see the list of parameters.

Note! Address digits must be written without initial zeros to be treated as dotted decimal form. The following address is NOT in correct dotted decimal form: 192.168.01.02 (it is actually in dotted octal form)

Note! Port number must be above 1024

Examples:

  udp://192.168.1.2:5201
  
udp://192.168.1.2:5201?source=10.10.11.2:46218

RTP

Multicast and Singlecast streaming can also be done using the Real-time Transport Protocol (RTP). For this to work the URL must start with rtp://. Other than that, everything that applies to multicast and singlecast applies to RTP as well.

Example:

rtp://239.1.5.10:20000

HTTP

Standard HTTP URLs may be used to stream audio/video from a web server. The file is identified by its MIME type (audio/mpeg, video/mpeg):

http://<host>[:<port>]/<content path>[?<queryparam>=value][&<queryparam>=value]*][|<parameter>=value[&<parameter>=value]*]

where

  • <host> is a domain name or an IP address
  • <port> is the relevant port number for the server. If no port is specified, then 80 (the standard for HTTP) is used.
  • <content path> is the path and file name for the media file.
  • Query parameters and player parameters (<parameter>) are optional. For details see the list of parameters.

Example:

http://myserver.mydomain.com/fun_movie.mpg

DVB

DVB-T sources are specified on the form: 

dvb://<original-network-id>.<transport-stream-id>.<service-id>[?<queryparam>=value][&<queryparam>=value]*][|<parameter>=value[&<parameter>=value]*]

where

  • <original-network-id> The original network id.
  • <transport-stream-id> The transport stream id.
  • <service-id> The service id.
  • Query parameters and player parameters (<parameter>) are optional. For details see the list of parameters.

These parameters can be obtained after performing a channel scan.

Example:

dvb://F7A7.5C24.43B1

DVR

The DVR URI is used to open recorded assets in the system. The preferred way to obtain the URI is to use the designated functions. They will return on the following form:

dvr://<asset path>

where the <asset path> is the path to the asset on the harddrive.

Example:

dvr:///dvr/storage/asset_bls558

ATSC QAM Sources using Tuning Triplet

ATSC QAM Sources using Tuning Triplet are specified on the form: 

atsc://fr<frequency>.<modulation>.<mpegservice-id>[?<queryparam>=value][&<queryparam>=value]*][|<parameter>=value[&<parameter>=value]*]

where

  • <frequency> The QAM INBAND frequency associated with the ATSC service to be acquired. The application must pre-pend the frequency value with an 'fr' prefix. The frequency value in most cases is provided by the TEI Channel Service interface. The format is a positive value decimal number expressed in Hertz.
  • <modulation> The modulation mode associated with the ATSC service to be acquired. The modulation value in derived from the TEI Channel Service interface for DCII systems. The format is a positive value decimal number representing the QAM modulation type and can only be 64 or 256 for DCII systems.
  • <mpegservice-id> The MPEG Service Identifier or MPEG Program Number associated with the ATSC service to be acquired. The mpeg service number value in most cases is provided by the TEI Channel Service interface. The format is a positive value decimal number.
  • Query parameters (<queryparam>) are optional and may contain the following:
    1. tuner_id=value - The tuner id associated with the tuner number used to acquire the ATSC service. The format value is a positive decimal number between 0 to the maximum number of tuners supported by the platform (minus 1, since its zero based). This is an optional parameter and should be used in multituner products; if not specified in a multituner platform, a free tuner will automatically be assigned, if available.
  • Player parameters (<parameter>) are optional. For details see the list of parameters.

Example:

atsc://fr477000000.256.23?tuner_id=0