Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Media files such as MPEG-4 files are fragmented to allow for media and live media creation and delivery. A MPEG-4 standard description box includes synchronization information, end of file information, and chapter information to provide signaling information for near live playback of fragments. Playback can begin upon receiving a first MPEG-4 file fragment. A second MPEG-4 file fragment can be requested using information included in the first MPEG-4 file fragment.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Media such as live media streams can be efficiently delineated and distributed to a variety of devices using a number of different mechanisms. A particular media sequence can be identified by a device user to allow a content server or fragment server to generate a media segment that can be shared or distributed using mechanisms such as social networks. A device user may provide marker indicators, time frames, event triggers, etc., that indicate to a content server where a media segment can be delineated. A link to the media segment may be provided along with pre-roll and post-roll targeted or content-specific advertising to a variety of other users.

Abstract: A media stream delivery system encodes and fragments media streams into numerous media stream fragments maintained on fragment servers. Playlist information, media data, and bandwidth adaption data is provided as box information with media stream fragments to reduce the number of client requests required to begin playback or perform a channel change. A client no longer needs to make separate requests for bandwidth adaptation data, media data, or playlist information. Playback can begin as soon as sufficient media stream fragments are received.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Mechanisms are provided to manage media stream transmissions at a content server. A content server detects that a user on a device such as a mobile device has stopped playing a live media stream. The content server maintains information associating the user with the media stream and time information. When the content server detects that a user wishes to resume playing a media stream, the user can continue viewing the media stream from where stoppage occurred. In many instances, the content server stores many hours of live media stream data and allows a user to select a particular starting point.

Abstract: Techniques and mechanisms are described herein for facilitating cowatching and connected platforms using a push architecture. According to various embodiments, a first message from a first client device may be received at a server. The first message may include first update information for updating first shared media context information at the server. The server may be operable to provide a shared media environment across a plurality of client devices based on the first shared media context information. The plurality of client devices may include the first client device and a second client device. The first message may be transmitted via a push communications framework. The first shared media context information may be updated based on the first message. A second message may be transmitted to the second client device via the push communications framework. The second message may include second update information.

Abstract: A media stream delivery system encodes and fragments media streams into numerous media stream fragments maintained on fragment servers. Playlist information, media data, and bandwidth adaption data is provided as box information with media stream fragments to reduce the number of client requests required to begin playback or perform a channel change. A client no longer needs to make separate requests for bandwidth adaptation data, media data, or playlist information. Playback can begin as soon as sufficient media stream fragments are received.

Abstract: Media such as live media streams can be efficiently delineated and distributed to a variety of devices using a number of different mechanisms. A particular media sequence can be identified by a device user to allow a content server or fragment server to generate a media segment that can be shared or distributed using mechanisms such as social networks. A device user may provide marker indicators, time frames, event triggers, etc., that indicate to a content server where a media segment can be delineated. A link to the media segment may be provided along with pre-roll and post-roll targeted or content-specific advertising to a variety of other users.

Abstract: Media files such as MPEG-4 files are fragmented to allow for media and live media creation and delivery. A MPEG-4 standard description box includes synchronization information, end of file information, and chapter information to provide signaling information for near live playback of fragments. Playback can begin upon receiving a first MPEG-4 file fragment. A second MPEG-4 file fragment can be requested using information included in the first MPEG-4 file fragment.

Abstract: Media files such as MPEG-4 files are fragmented to allow for media creation, delivery, quality adjustment, and place shifting. Playback on a device can begin upon receiving a first MPEG-4 file fragment. Playback stoppage is detected and media stream position information along with quality level information is maintained at a content server. Playback can continue using the same device and media stream quality, a different media stream quality, or with a different device and different media stream quality. Additional MPEG-4 file fragments requested may be fragments corresponding to a higher or lower bit-rate stream configured for a different device associated with the user to allow a user to resume playback on a different device.

Abstract: A media convergence platform allows time-shifting and place-shifting of live, video on demand, and recorded content across multiple devices, displays, etc. Users are able to pause content on one device and resume where they left off on another device. The media convergence platform allows users to record, select, consume, add, delete, manage, and manipulate media content including live programming across user authorized devices such as set top boxes, computer systems, mobile devices, etc.

Abstract: A client device receiving a media stream from a remote content server can fast forward and rewind the media stream without storing the media stream on the client device. In some examples, the client sends index, direction, and speed information to the content server based on desired fast forward and rewind operation. The content server transmits selected sets of frames to the client devices based on the index, direction, and speed information to allow a client to play a fast forward or rewind media stream that provides a user with discernible portions of content.