Creating a manifest file at a time of creating recorded content

Concepts and technologies are disclosed herein for creating a manifest file at a time of creating recorded content. A video device can request media content from a content source and receive the media content requested. The media content can be received with metadata from the content source. The video device can record the media content to generate recorded content and create, during the recording of the media content, a manifest file that includes at least a portion of the metadata that is received from the content source. The video device can store the recorded content and the manifest file.

BACKGROUND

Over the past several years, the delivery of media content such as movies, television shows, or the like, has changed drastically. Whereas in the past media content often was delivered via broadcast, video rentals, and the like, some modern consumers of media content may obtain the media content that is being consumed using various types of devices that can be configured to obtain the data via one or more data sessions.

Additionally, the prevalence of high speed Internet and other changes has enabled users to record content for consumption at various times and/or using various devices instead of “tuning in” to a broadcast stream. Thus, some modern consumers of media content may configure a video device (e.g., a digital video recorder (“DVR”) device) to obtain and record media content for consumption at some time in the future. Also, instead of watching a video or other media content on a television, some modern consumers may instead elect to stream the content to a user device such as a tablet, cellular telephone or smartphone, or the like.

These changes continue to evolve the way media content is consumed today. When a consumer wishes to view media content, the device from which the content is streamed may create a streaming manifest or manifest file. The manifest file can include information that may be needed or may be used to stream the content to a device used to view the media content. In particular, the manifest file can be provided to a recipient device being used to view the content and the recipient device may set up a data stream and/or data session using the manifest file. The recipient may use other information included in the manifest file to view the content, in some embodiments.

SUMMARY

The present disclosure is directed to creating a manifest file at a time of creating recorded content. A video device can execute a video application. The video application can be used to request media content from a source such as a server computer. The video application also can be used to record the media content as recorded content. In some embodiments, the video device can generate and/or send a media content request to the server computer or other source of the media content. In response to the request for the media content, the media content can be received at the video device. The media content can be received by the video device as a file, as part of a stream, or in another file format (or combination of file formats). The video device can be configured to record the media content as the recorded content. During the recording of the media content as the recorded content, the video device can capture data needed to create a manifest file and create the manifest file at recording time. This data may be included in metadata that is received by the video device with the media content, in some embodiments. Thus, when recording of the media content as the recorded content is completed, creation of the manifest file can also be completed. Thus, the video device can be configured to store the recorded content and the manifest file at substantially the same time.

The video device can receive a request for the recorded content such as a recorded content request from a requestor. The recorded content request can specify content that a user or other entity wishes to view or otherwise obtain from the video device. The vide device can use information included in the recorded content request to identify the recorded content associated with the recorded content request and to identify a manifest file associated with the recorded content requested by way of the recorded content request. The video device can provide the manifest file to the requestor and provide the recorded content. It can be appreciated that the manifest file can be used by the recipient device to set up the recipient device (e.g., a user device) for receiving and/or interpreting the recorded content. As such, various embodiments of the concepts and technologies disclosed herein can provide the recorded content without any delay that may otherwise result from having to create the manifest file.

A playback application can be executed by a recipient device such as the user device. This playback application can be used to generate the recorded content request and/or to present a movie, show, or other video represented by the recorded content to a user or other entity. According to various embodiments, the playback application can use the manifest file to set up or plan a video stream via which the video or movie can be streamed to the user device. The manifest file also can be used to present the movie, show, or other video associated with the recorded content. For example, the playback application can use the manifest file to identify advertising breaks in the video; to fill those advertising breaks with advertisements; to identify segments in the video; to identify, configure, and/or decode audio associated with the video and/or segments of the video; to determine frame rates, resolutions, and/or to decode video; combinations thereof; or the like. Thus, the recorded content can be presented by the user device using the manifest file where the manifest file is created during generation of the recorded content.

According to one aspect of the concepts and technologies disclosed herein, a video device is disclosed. The video device can include a processor and a memory. The memory can store computer-executable instructions that, when executed by the processor, cause the processor to perform operations. The operations can include requesting media content from a content source and receiving the media content requested. The media content can be received with metadata from the content source. The operations also can include recording the media content to generate recorded content, creating, during the recording of the media content, a manifest file that includes a portion of the metadata that is received from the content source, and storing the recorded content and the manifest file.

In some embodiments, the video device can request the media content in response to detecting a command to record the media content. In some embodiments, the command to record the media content can be received via a user interface that can be presented by the video device. In some embodiments, the metadata can include data that can define a segment associated with the media content, a frame rate of video associated with the media content, and information that can define an advertisement break associated with the video. In some embodiments, the computer-executable instructions, when executed by the processor, can cause the processor to perform operations that further can include receiving a request for the recorded content from a user device in communication with the video device; identifying the recorded content and the manifest file that was created during recording of the media content; and providing, to the user device, the recorded content and the manifest file that was created during recording of the media content. In some embodiments, providing the recorded content and the manifest file can include providing the manifest file to the user device, where the user device can use the manifest file to set up a video stream via which the recorded content is to be received; and streaming the recorded content to the user device using the video stream.

According to another aspect of the concepts and technologies disclosed herein, a computer storage medium is disclosed. The computer storage medium can store computer-executable instructions that, when executed by a processor, cause the processor to perform operations. The operations can include requesting media content from a content source and receiving the media content requested. The media content can be received with metadata from the content source. The operations also can include recording the media content to generate recorded content, creating, during the recording of the media content, a manifest file that includes a portion of the metadata that is received from the content source, and storing the recorded content and the manifest file.

In some embodiments, the video device can request the media content in response to detecting a command to record the media content. In some embodiments, the command to record the media content can be received via a user interface that can be presented by the video device. In some embodiments, the metadata can include data that can define a segment associated with the media content, a frame rate of video associated with the media content, and information that can define an advertisement break associated with the video. In some embodiments, the computer-executable instructions, when executed by the processor, can cause the processor to perform operations that further can include receiving a request for the recorded content from a user device in communication with the video device; identifying the recorded content and the manifest file that was created during recording of the media content; and providing, to the user device, the recorded content and the manifest file that was created during recording of the media content. In some embodiments, providing the recorded content and the manifest file can include providing the manifest file to the user device, where the user device can use the manifest file to set up a video stream via which the recorded content is to be received; and streaming the recorded content to the user device using the video stream.

According to yet another aspect, a method is disclosed. The method can include requesting, by a video device that can include a processor, media content from a content source and receiving, by the video device, the media content requested. The media content can be received with metadata from the content source. The method also can include recording, by the video device, the media content to generate recorded content; creating, by the video device and during the recording of the media content, a manifest file that includes a portion of the metadata that is received from the content source; and storing, by the video device, the recorded content and the manifest file.

In some embodiments, the video device can request the media content in response to detecting a command to record the media content. In some embodiments, the command to record the media content can be received via a user interface that can be presented by the video device. In some embodiments, the metadata can include data that can define a segment associated with the media content. In some embodiments, the metadata can include data that can define a segment associated with the media content, a frame rate of video associated with the media content, and information that can define an advertisement break associated with the video. In some embodiments, the method further can include receiving, by the video device, a request for the recorded content from a user device in communication with the video device; identifying, by the video device, the recorded content and the manifest file that was created during recording of the media content; and providing, by the video device and to the user device, the recorded content and the manifest file that was created during recording of the media content.

In some embodiments, providing the recorded content and the manifest file can include providing the manifest file to the user device. The user device can use the manifest file to set up a video stream via which the recorded content is to be received. Providing the recorded content and the manifest file further can include streaming the recorded content to the user device using the video stream. In some embodiments, the manifest file can be stored as a hypertext transfer protocol live streaming file.

DETAILED DESCRIPTION

The following detailed description is directed to creating a manifest file at a time of creating recorded content. A video device can execute a video application. The video application can be used to request media content such as the media content from a source such as a server computer and to record the media content as recorded content. In some embodiments, the video device can generate and/or send a media content request to the server computer or other source of the media content. In response to the request for the media content, the media content can be received at the video device. The media content can be received by the video device as a file, as part of a stream, or in another file format (or combination of file formats). The video device can be configured to record the media content as the recorded content. During the recording of the media content as the recorded content, the video device can capture data needed to create a manifest file and create the manifest file at recording time. Thus, when recording of the media content as the recorded content is completed, creation of the manifest file can also be completed. Thus, the video device can be configured to store the recorded content and the manifest file at substantially the same time.

The video device can receive a request for the recorded content such as a recorded content request from a requestor. The recorded content request can specify content that a user or other entity wishes to view or otherwise obtain from the video device. The vide device can use information included in the recorded content request to identify the recorded content associated with the recorded content request and to identify a manifest file associated with the recorded content requested by way of the recorded content request. The video device can provide the manifest file to the requestor and follow up with the recorded content. It can be appreciated that the manifest file can be used by the recipient device to set up the recipient device (e.g., a user device) for receiving and/or interpreting the recorded content. As such, various embodiments of the concepts and technologies disclosed herein can provide the recorded content without any delay that may otherwise result from having to create the manifest file.

A playback application can be executed by a recipient device such as the user device. This playback application can be used to generate the recorded content request and/or to present a movie, show, or other video represented by the recorded content to a user or other entity. According to various embodiments, the playback application can use the manifest file to set up a video stream via which the video or movie can be streamed to the user device. The manifest file also can be used to present the movie, show, or other video associated with the recorded content. For example, the playback application can use the manifest file to identify advertising breaks in the video; to fill those advertising breaks with advertisements; to identify segments in the video; to identify, configure, and/or decode audio associated with the video and/or segments of the video; to determine frame rates, resolutions, and/or to decode video; combinations thereof; or the like. Thus, the recorded content can be presented by the user device using the manifest file where the manifest file is created during generation of the recorded content.

Referring now toFIG. 1, aspects of an operating environment100for various embodiments of the concepts and technologies disclosed herein for creating a manifest file at a time of creating recorded content will be described, according to an illustrative embodiment. The operating environment100shown inFIG. 1includes a video device102. In various embodiments, the video device102can be configured to operate in communication with and/or as part of a communications network (“network”)104, though this is not necessarily the case.

According to various embodiments, the functionality of the video device102may be provided by one or more set-top boxes, customer premise equipment (“CPE”) devices, digital video recorder (“DVR”) devices, server computers, desktop computers, mobile telephones, laptop computers, tablet computing devices, other computing systems, and the like. It should be understood that the functionality of the video device102can be provided by a single device, by two similar devices, and/or by two or more dissimilar devices. For purposes of describing the concepts and technologies disclosed herein, the video device102is described herein as a CPE device, a DVR device, and/or a combination thereof. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.

The video device102can execute an operating system (not shown inFIG. 1) and one or more application programs such as, for example, a video application106. The operating system can include a computer program that can be configured to control the operation of the video device102. The video application106can include an executable program that can be configured to execute on top of the operating system to provide various functions as illustrated and described herein for creating a manifest file at a time of creating recorded content.

In particular, the video application106can be configured to request and/or obtain media content108from a content source such as a content server or other type of server computer (hereinafter referred to as a “server computer”)110. According to various embodiments, the media content108can include data associated with video content. Thus, it can be appreciated that the media content108can include images, audio, and various types of data that can represent how the images and audio collectively represent a video. Thus, for example, the media content108can include one or more video file and one or more audio file, in some embodiments. As shown inFIG. 1, the media content108can include advertisements, and the video and/or audio can be divided into one or more segments, if desired. In some other embodiments, the media content108can include video and audio and various types of metadata or other data (labeled “MD” inFIG. 1). The metadata MD can define and/or identify one or more segments and/or segment information; one or more advertisements and/or advertisement information; one or more frame rate(s); one or more resolution(s); one or more lengths of segments, advertisements, breaks, audio, and/or video; time information; iframe index information; media information; protection information; break information; and/or other information.

According to various embodiments, the information that defines the segments can include information that defines segment durations and/or a segment index. Thus, the information that defines the segments can identify the chunks of the media content108. According to some embodiments, the size of the segments is configurable. In some embodiments, a smallest size of the segments can be equivalent to the group of pictures (“GOP”) structure of the file in a closed GOP formatted file. The segments information also can provide a byte offset and/or range in the content file to retrieve a segment of a configured size. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

The advertisements can include audio, video, and/or other information relating to one or more advertisements. The frame rate information can identify one or more frame rates for the video and/or segments of video. The length information can define or identify one or more lengths of videos, segments, breaks, and/or advertisements. The time information can define times at which breaks begin, end, and/or the durations of the breaks. The audio information can define various aspects of audio such as bit rates, sampling rates, durations, offsets, and the like. The media information can describe the content and/or details thereof. Thus, the media information can define one or more codecs and/or codec information, bit rates, resolution information, media titles, or the like.

The video information can define one or more videos, images, and/or sequences of images. The protection information can provide details of any content protection applied to the media content108, if any such protection is used. The break information can define details of content discontinuity within the media content108such as a beginning and/or end of an advertising break. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

According to various embodiments, the media content108can be provided to the video device102as or via a video stream or other data stream such as the data stream112shown inFIG. 1, though this is not necessarily the case. In some other embodiments, the media content108can be provided to the video device102as a file that is downloaded by the video device102. According to various embodiments of the concepts and technologies disclosed herein, the media content108can be streamed to the video device102in response to the video device102requesting the media content108, for example via a media content request114. It can be appreciated that the media content request114can be generated by the video device102in response to a request for the media content108at the video device102. For example, a user of the video device102may access a menu or ordering interface associated with the video device102(e.g., an ordering interface that can be presented by the video application106) and request a particular instance of content such as a particular movie, show, or the like. This request can be used to generate the media content request114, which can be transmitted to the server computer110by the video device102. Because the request for media content108can be made in additional and/or alternative manners (instead of or in addition to the media content request114), it should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

As noted above, the media content108can be streamed to, transmitted to, downloaded by, and/or otherwise transferred or transmitted to the video device102. According to various embodiments of the concepts and technologies disclosed herein, the video device102can be configured; by default, by request, by settings, by configurations, or in other manners; to record the media content108instead of, or in addition to, presenting the media content108for immediate consumption. Thus, for example, the video device102can be configured to record the media content108for later consumption by a user or device and therefore can capture and/or record the media content108as recorded content116. The recorded content116can include the video associated with the media content108as illustrated and described herein.

In various video recording devices, recorded content similar to the recorded content116can be captured by devices and later streamed to a requestor or other device. With those devices, however, prior to streaming the content to a requestor, the devices must obtain or generate a streaming manifest file (“manifest file”) such as the manifest file118shown inFIG. 1. The process of creating a manifest file118can take, on average, thirty to forty-five seconds. During this time, the streaming of the recorded content116can be delayed. Embodiments of the concepts and technologies disclosed herein create the manifest file118during recording of the media content108as the recorded content116and store the manifest file118for use if and when the recorded content116is streamed to another device. Thus, embodiments of the concepts and technologies disclosed herein provide almost instantaneous streaming of the recorded content116to a user device120upon request for the recorded content116by eliminating delays typically associated with creation of the manifest file118. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

In some embodiments of the concepts and technologies disclosed herein, the manifest file118illustrated and described herein can be formatted in an HTTP live streaming (“HLS”) format. In this contemplated example, an example manifest may be formatted as follows:

It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

In another example, an example manifest may include byte ranges and may be formatted as follows:

It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

In another example, an example manifest may include iframe byte ranges and may be formatted as follows:

It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

In particular, the video device102can be configured to receive a request (e.g., the recorded content request122) from a user device120. The recorded content request122can request streaming of the recorded content116from the video device102to the user device120. According to various embodiments, the recorded content request122can be generated by a playback application124that can be executed by the user device120. The playback application124can, for example, present a user interface with selectable user interface controls for selecting media that a user wants to view at the user device120, where the media presented in the user interface can correspond to the recorded content116and/or other content that may have previously been recorded. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

The recorded content request122can be transmitted from the user device120to the video device102via one or more network connections126. According to various embodiments, the network connection(s)126can be provided by the network104and/or other networks such as local area networks, wide area networks, the Internet, and/or other network connections. In response to receiving the recorded content request122, the video device102can identify recorded content116that is requested by way of the recorded content request122. The video device102also can identify a manifest file118associated with the recorded content116. It therefore can be appreciated that one or more instances of recorded content116and/or one or more manifest files118can be stored with information that can be used to associate the recorded content116and the manifest files118. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

In response to the recorded content request122, the video device102can transmit the manifest file118to the user device120. The manifest file118can indicate, to the user device120and as is known, various aspects of the recorded content116such as time information, length information, frame rates for video, video resolution, sampling rates for audio, information that identifies segments within the video, other information, combinations thereof, or the like. Thus, the manifest file118can be used to inform the user device120how to interpret the recorded content116when streamed and/or transmitted to the user device120by the video device102. After providing the manifest file118(or at substantially the same time), the video device102can transmit the recorded content116to the user device120. It can be appreciated that the recorded content116can be streamed, in various embodiments, from the video device102to the user device120via the one or more network connection(s)126. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

In practice, the video device102can request media content such as the media content108from a source such as the server computer110. In some embodiments, the video device102can generate and/or send a media content request114to the server computer110or other source of the media content108. In response to the request for the media content108, the media content108can be received at the video device102(either as a file or as part of a stream). The video device102can be configured to record the media content108as the recorded content116. During the recording of the media content108as the recorded content116, the video device102can capture data needed to create a manifest file118and create the manifest file118at recording time. The data needed to create the manifest file118can be included, in some embodiments, as metadata MD that can be included with the media content108and/or otherwise included in a stream or data associated with the media content108. Thus, when recording of the media content108as the recorded content116is completed, creation of the manifest file118can also be completed, in some embodiments. Thus, the video device102can be configured to store the recorded content116and the manifest file118at substantially the same time. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

The video device102can receive a request for the recorded content116such as the recorded content request122from a requestor or requestor device. The recorded content request122can specify content that a user or other entity wishes to view or otherwise obtain from the video device102. The video device102can use information included in the recorded content request122to identify the recorded content116associated with the recorded content request122and to identify a manifest file118associated with the recorded content116requested by way of the recorded content request122. The video device102can provide the manifest file118to the requestor and follow up with the recorded content116. It can be appreciated that the manifest file118can be used by the recipient device to set up the device for receiving and/or interpreting the recorded content116. As such, various embodiments of the concepts and technologies disclosed herein can provide the recorded content116to a recipient or recipient device without any delay that otherwise may result from having to create the manifest file118. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

The playback application124executed by the user device120also can be configured to present a movie, show, or other video represented by the recorded content116to a user or other entity. According to various embodiments, the playback application124can use the manifest file118to set up a video stream with the video device102. The video stream can be used to stream the video from the video device102to the user device120and the user device120can present the movie, show, or other video associated with the recorded content116. For example, the playback application124can use the manifest file118to identify advertising breaks in the video; to fill those advertising breaks with advertisements; to identify segments in the video; to identify, configure, and/or decode audio associated with the video and/or segments of the video; to determine frame rates, resolutions, and/or to decode video; combinations thereof; or the like. Thus, the recorded content116can be presented by the user device120using the manifest file118where the manifest file118is created during generation of the recorded content116.

FIG. 1illustrates one video device102, one network104, one server computer110, one data stream112, one user device120, and one network connection126. It should be understood, however, that various implementations of the operating environment100can include zero, one, or more than one video device102; zero, one, or more than one network104; zero, one, or more than one server computer110; zero, one, or more than one data stream112; zero, one, or more than one user device120; and/or zero, one, or more than one network connection126. As such, the illustrated embodiment should be understood as being illustrative, and should not be construed as being limiting in any way. It should be understood that the numbers labeling the communications inFIG. 1are illustrative of one contemplated embodiment and that other orders of the described operations and communications are possible and are contemplated. Thus, the illustrated embodiment is illustrative and should not be construed as being limiting in any way.

Thus, it should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These states, operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. As used herein, the phrase “cause a processor to perform operations” and variants thereof is used to refer to causing a processor of a computing system or device, such as the video device102, the server computer110, the user device120, or other device, to perform one or more operations and/or causing the processor to direct other components of the computing system or device to perform one or more of the operations.

For purposes of illustrating and describing the concepts of the present disclosure, the methods disclosed herein are described as being performed by the video device102via execution of one or more software modules such as, for example, the video application106. It should be understood that additional and/or alternative devices and/or network nodes can provide the functionality described herein via execution of one or more modules, applications, and/or other software including, but not limited to, the video application106. Thus, the illustrated embodiments are illustrative, and should not be viewed as being limiting in any way.

The method200begins at operation202. At operation202, the video device102can request media content such as the media content108. According to various embodiments of the concepts and technologies disclosed herein, the video device102can request the media content108from a content server or other source of media content such as the server computer110illustrated and described herein. According to various embodiments of the concepts and technologies disclosed herein, the video device102can create a request such as the media content request114in response to receiving a request or detecting an interaction that can be interpreted by the video application106and/or the video device102as a request for the media content108. As explained above, for example, a user or other entity may interact with a user interface that can be presented by the video device102such as, for example, a programming guide or the like. The user or other entity can select a particular movie, show, or other content for recording by the video device102. In some embodiments, the video device102can request the media content108from the data source in response to this request from the user or other entity, though this is not necessarily the case.

In some embodiments, in response to detecting selection of the movie, show, or other content, the video device102can generate a request for media content108that corresponds to the requested content and send the request (e.g., the media content request114) to a source of the content such as the server computer110illustrated and described herein. In response to receiving the media content request114, the server computer110can be configured to stream, transmit, or otherwise provide the media content108to the video device102. According to various embodiments of the concepts and technologies disclosed herein, the media content108can be provided with metadata MD that can describe the media content108and/or one or more aspects of the data that corresponds to the media content108. Because the media content108can be requested in additional and/or alternative manners, and because the media content request114illustrated and described herein can be generated in response to additional and/or alternative actions, it should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

From operation202, the method200can proceed to operation204. At operation204, the video device102can receive the media content108requested in operation202. In accordance with the description herein, it can be appreciated that the video device102can receive the media content108as part of a content or data stream such as the data stream112, though this is not necessarily the case. As explained herein, the media content108can also be provided to the video device102as a file or other form of data. In some embodiments, as illustrated and described inFIG. 1, the media content108can be provided with one or more instances of metadata MD, which can include various types of information about the media content108.

Regardless of how the media content108is provided to the video device102, the video device102can receive the media content108in operation204. As shown inFIG. 1, the media content108(or data representing the media content108) received in operation204can include data (e.g., the metadata MD and/or other data) that can represent a length of a show, advertisement, movie, episode, or other video that corresponds to the media content108; one or more times associated with the show, advertisement, movie, episode, or other video that corresponds to the media content108; one or more frame rates associated with the show, advertisement, movie, episode, or other video that corresponds to the media content108; one or more segments associated with the show, advertisement, movie, episode, or other video that corresponds to the media content108; one or more audio files associated with the show, advertisement, movie, episode, or other video that corresponds to the media content108and/or associated audio file information such as bit rates, sampling rates, or the like; one or more images or video sequences associated with the show, advertisement, movie, episode, or other video that corresponds to the media content108; one or more advertisements associated with the show, advertisement, movie, episode, or other video that corresponds to the media content108; other data associated with the show, advertisement, movie, episode, or other video that corresponds to the media content108; combinations thereof; or the like.

Thus, it can be appreciated that the media content108provided in operation204can include data that defines and/or represents various aspects of the media content108that may be needed to create the manifest file118illustrated and described herein. It should be understood, however, that the data used to create the manifest file118can be provided as part of the media content108, with the media content108, by the server computer110, by other devices (not shown inFIG. 1), and the like, and therefore may not be provided separately in some embodiments. As such, the illustrated embodiment ofFIG. 1is illustrative and should not be construed as being limiting in any way.

From operation204, the method200can proceed to operation206. At operation206, the video device102can record the media content108to generate the recorded content116illustrated and described herein. During recording of the media content108to create the recorded content116, the video device102can create the manifest file118based on the media content108and/or based on information that can be provided with the media content108such as, for example, the metadata MD. According to various embodiments of the concepts and technologies disclosed herein, the video device102can be configured to determine various aspects of the media content108that are used to create the manifest file118during recording of the media content108without receiving information that indicates these aspects separately and/or as part of the media content108. Thus, for example, the video device102can determine the length of the media content108during recording of the media content108. Similarly, the video device102can determine the frame rate, resolution, and/or the like of the media content108during recording of the media content108. Similarly, the video device102can identify one or more segments and/or times associated with the media content108during recording of the media content108. Still further, the video device102can identify one or more advertisements and/or advertisement breaks of the media content108during recording of the media content108. Thus, it can be appreciated that the video device102can identify any aspects of the media content108needed for the manifest file118during recording of the media content108as the recorded content116.

From operation206, the method200can proceed to operation208. At operation208, the video device102can store the recorded content116and the manifest file118created in operation206. According to various embodiments, the recorded content116and the manifest file118can be stored in a memory, mass storage device, and/or other data storage device associated with the video device102. In some other embodiments, the recorded content116and the manifest file118can be stored in a memory, mass storage device, and/or other data storage device that can be remote from the video device102. As explained above, the recorded content116and the manifest file118generated in operation206can be stored with data that associates (or can be used to associate) the recorded content116and the manifest file118. At any rate, multiple instances of recorded content116and/or multiple manifest files118can be stored simultaneously by the video device102.

From operation208, the method200can proceed to operation210. The method200can end at operation210.

Turning now toFIG. 3, aspects of a method300for providing, to a recipient, a manifest file118that was created at the time of creating recorded content116will be described in detail, according to an illustrative embodiment. The method300begins at operation302. At operation302, the video device102can receive a request for recorded content116such as, for example, the recorded content request122illustrated and described herein. According to various embodiments of the concepts and technologies disclosed herein, the video device102can receive the recorded content request122from a user device120or other requestor. According to various embodiments of the concepts and technologies disclosed herein, the user device120can create the recorded content request122in response to receiving a request or detecting an interaction that can be interpreted by the playback application124and/or other application executed by the user device120as a request for the recorded content116. For example, a user or other entity may interact with a user interface that can be presented by the user device120to select a particular movie, show, or other content that has been recorded by the video device102as the recorded content116. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

In response to detecting selection of the movie, show, or other content, the user device120can generate a request for recorded content116that corresponds to the requested content and send the request (e.g., the recorded content request122) to the video device102. In response to receiving the recorded content request122, the video device102can be configured to stream, transmit, or otherwise provide the recorded content116to the user device120. Because the recorded content116can be requested in additional and/or alternative manners, and because the recorded content request122illustrated and described herein can be generated in response to additional and/or alternative actions, it should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

From operation302, the method300can proceed to operation304. At operation304, the video device102can identify the recorded content116and the manifest file118associated with the request received in operation302. Thus, in operation304, the video device102can identify a show, movie, or other video associated with the recorded content request122(or other request) received in operation302. As explained above, the recorded content116and the manifest file118can be stored with data that associates the recorded content116and the manifest file118with one another and/or that identifies an associated title or other identifying information associated with the movie, show, and/or other video represented by the recorded content116. Thus, in operation304, the video device102can identify the recorded content116and the manifest file118requested in operation302.

From operation304, the method300can proceed to operation306. At operation306, the video device102can provide the manifest file118and the recorded content116to a requestor or recipient such as, for example, the user device120. It can be appreciated that the user device120(and/or the playback application124) can use the manifest file118to interpret and/or decode the recorded content116, in some embodiments. Regardless, it can be appreciated that the user device120can use the manifest file118and the recorded content116to present the movie, show, episode, or other video. It should be understood that this example is illustrative, and therefore should not be construed as being limiting in any way.

From operation306, the method300can proceed to operation308. The method300can end at operation308.

Turning now toFIG. 4, additional details of the network104are illustrated, according to an illustrative embodiment. The network104includes a cellular network402, a packet data network404, for example, the Internet, and a circuit switched network406, for example, a publicly switched telephone network (“PSTN”). The cellular network402includes various components such as, but not limited to, base transceiver stations (“BTSs”), Node-B's or e-Node-B's, base station controllers (“BSCs”), radio network controllers (“RNCs”), mobile switching centers (“MSCs”), mobile management entities (“MMEs”), short message service centers (“SMSCs”), multimedia messaging service centers (“MMSCs”), home location registers (“HLRs”), home subscriber servers (“HSSs”), visitor location registers (“VLRs”), charging platforms, billing platforms, voicemail platforms, GPRS core network components, location service nodes, an IP Multimedia Subsystem (“IMS”), and the like. The cellular network402also includes radios and nodes for receiving and transmitting voice, data, and combinations thereof to and from radio transceivers, networks, the packet data network404, and the circuit switched network406.

A mobile communications device408, such as, for example, a cellular telephone, a user equipment, a mobile terminal, a PDA, a laptop computer, a handheld computer, and combinations thereof, can be operatively connected to the cellular network402. The cellular network402can be configured as a 2G GSM network and can provide data communications via GPRS and/or EDGE. Additionally, or alternatively, the cellular network402can be configured as a 3G UMTS network and can provide data communications via the HSPA protocol family, for example, HSDPA, EUL (also referred to as HSDPA), and HSPA+. The cellular network402also is compatible with 4G mobile communications standards as well as evolved and future mobile standards.

The packet data network404includes various devices, for example, servers, computers, databases, and other devices in communication with one another, as is generally known. The packet data network404devices are accessible via one or more network links. The servers often store various files that are provided to a requesting device such as, for example, a computer, a terminal, a smartphone, or the like. Typically, the requesting device includes software (a “browser”) for executing a web page in a format readable by the browser or other software. Other files and/or data may be accessible via “links” in the retrieved files, as is generally known. In some embodiments, the packet data network404includes or is in communication with the Internet. The circuit switched network406includes various hardware and software for providing circuit switched communications. The circuit switched network406may include, or may be, what is often referred to as a plain old telephone system (POTS). The functionality of a circuit switched network406or other circuit-switched network are generally known and will not be described herein in detail.

The illustrated cellular network402is shown in communication with the packet data network404and a circuit switched network406, though it should be appreciated that this is not necessarily the case. One or more Internet-capable devices410, for example, a PC, a laptop, a portable device, or another suitable device, can communicate with one or more cellular networks402, and devices connected thereto, through the packet data network404. It also should be appreciated that the Internet-capable device410can communicate with the packet data network404through the circuit switched network406, the cellular network402, and/or via other networks (not illustrated).

As illustrated, a communications device412, for example, a telephone, facsimile machine, modem, computer, or the like, can be in communication with the circuit switched network406, and therethrough to the packet data network404and/or the cellular network402. It should be appreciated that the communications device412can be an Internet-capable device, and can be substantially similar to the Internet-capable device410. In the specification, the network104is used to refer broadly to any combination of the networks402,404,406. It should be appreciated that substantially all of the functionality described with reference to the network104can be performed by the cellular network402, the packet data network404, and/or the circuit switched network406, alone or in combination with other networks, network elements, and the like.

FIG. 5is a block diagram illustrating a computer system500configured to provide the functionality described herein for creating and/or using a manifest file118that is created at a time of creating recorded content116, in accordance with various embodiments of the concepts and technologies disclosed herein. As such, it can be appreciated that the computer system500illustrated and described herein can correspond to an architecture for the video device102and/or the user device120illustrated and described herein. The computer system500also can correspond to an architecture for the server computer110, in some embodiments. The computer system500includes a processing unit502, a memory504, one or more user interface devices506, one or more input/output (“I/O”) devices508, and one or more network devices510, each of which is operatively connected to a system bus512. The bus512enables bi-directional communication between the processing unit502, the memory504, the user interface devices506, the I/O devices508, and the network devices510.

The processing unit502may be a standard central processor that performs arithmetic and logical operations, a more specific purpose programmable logic controller (“PLC”), a programmable gate array, or other type of processor known to those skilled in the art and suitable for controlling the operation of the server computer. As used herein, the word “processor” and/or the phrase “processing unit” when used with regard to any architecture or system can include multiple processors or processing units distributed across and/or operating in parallel in a single machine or in multiple machines. Furthermore, processors and/or processing units can be used to support virtual processing environments. Processors and processing units also can include state machines, application-specific integrated circuits (“ASICs”), combinations thereof, or the like. Because processors and/or processing units are generally known, the processors and processing units disclosed herein will not be described in further detail herein.

The memory504communicates with the processing unit502via the system bus512. In some embodiments, the memory504is operatively connected to a memory controller (not shown) that enables communication with the processing unit502via the system bus512. The memory504includes an operating system514and one or more program modules516. The operating system514can include, but is not limited to, members of the WINDOWS, WINDOWS CE, and/or WINDOWS MOBILE families of operating systems from MICROSOFT CORPORATION, the LINUX family of operating systems, the SYMBIAN family of operating systems from SYMBIAN LIMITED, the BREW family of operating systems from QUALCOMM CORPORATION, the MAC OS, iOS, and/or other families of operating systems from APPLE CORPORATION, the FREEBSD family of operating systems, the SOLARIS family of operating systems from ORACLE CORPORATION, other operating systems, and the like.

The program modules516may include various software and/or program modules described herein. In some embodiments, for example, the program modules516include the video application106and/or the playback application124. These and/or other programs can be embodied in computer-readable media containing instructions that, when executed by the processing unit502, perform one or more of the methods200,300described in detail above with respect toFIGS. 2-3and/or other functionality as illustrated and described herein. It can be appreciated that, at least by virtue of the instructions embodying the methods200,300and/or other functionality illustrated and described herein being stored in the memory504and/or accessed and/or executed by the processing unit502, the computer system500is a special-purpose computing system that can facilitate providing the functionality illustrated and described herein. According to embodiments, the program modules516may be embodied in hardware, software, firmware, or any combination thereof. Although not shown inFIG. 5, it should be understood that the memory504also can be configured to store the media content108, the media content request114, the recorded content116, the manifest file118, the recorded content request122, and/or other data, if desired.

The user interface devices506may include one or more devices with which a user accesses the computer system500. The user interface devices506may include, but are not limited to, computers, servers, personal digital assistants, cellular phones, or any suitable computing devices. The I/O devices508enable a user to interface with the program modules516. In one embodiment, the I/O devices508are operatively connected to an I/O controller (not shown) that enables communication with the processing unit502via the system bus512. The I/O devices508may include one or more input devices, such as, but not limited to, a keyboard, a mouse, or an electronic stylus. Further, the I/O devices508may include one or more output devices, such as, but not limited to, a display screen or a printer.

The network devices510enable the computer system500to communicate with other networks or remote systems via a network, such as the network104. Examples of the network devices510include, but are not limited to, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface, a bridge, a router, or a network card. The network104may include a wireless network such as, but not limited to, a Wireless Local Area Network (“WLAN”) such as a WI-FI network, a Wireless Wide Area Network (“WWAN”), a Wireless Personal Area Network (“WPAN”) such as BLUETOOTH, a Wireless Metropolitan Area Network (“WMAN”) such a WiMAX network, or a cellular network. Alternatively, the network104may be a wired network such as, but not limited to, a Wide Area Network (“WAN”) such as the Internet, a Local Area Network (“LAN”) such as the Ethernet, a wired Personal Area Network (“PAN”), or a wired Metropolitan Area Network (“MAN”).

Turning now toFIG. 6, an illustrative mobile device600and components thereof will be described. In some embodiments, the user device120and/or the video device102described above with reference toFIGS. 1-5can be configured as and/or can have an architecture similar or identical to the mobile device600described herein inFIG. 6. It should be understood, however, that the video device102and/or the user device120may or may not include the functionality described herein with reference toFIG. 6. While connections are not shown between the various components illustrated inFIG. 6, it should be understood that some, none, or all of the components illustrated inFIG. 6can be configured to interact with one another to carry out various device functions. In some embodiments, the components are arranged so as to communicate via one or more busses (not shown). Thus, it should be understood thatFIG. 6and the following description are intended to provide a general understanding of a suitable environment in which various aspects of embodiments can be implemented, and should not be construed as being limiting in any way.

As illustrated inFIG. 6, the mobile device600can include a display602for displaying data. According to various embodiments, the display602can be configured to display various graphical user interface (“GUI”) elements such as, for example, programming guides, recording interfaces, playback application interfaces, text, images, video, virtual keypads and/or keyboards, messaging data, notification messages, metadata, internet content, device status, time, date, calendar data, device preferences, map and location data, combinations thereof, and/or the like. The mobile device600also can include a processor604and a memory or other data storage device (“memory”)606. The processor604can be configured to process data and/or can execute computer-executable instructions stored in the memory606. The computer-executable instructions executed by the processor604can include, for example, an operating system608, one or more applications610such as the video application106, the playback application124, other computer-executable instructions stored in a memory606, or the like. In some embodiments, the applications610also can include a UI application (not illustrated inFIG. 6).

The UI application can be executed by the processor604to aid a user in entering content, in requesting the media content108, to requesting recorded content116, to causing the video device102to record the media content108to create the recorded content116and/or the manifest file118, configuring settings, multimode interactions, interacting with other applications610, and otherwise facilitating user interaction with the operating system608, the applications610, and/or other types or instances of data612that can be stored at the mobile device600. The data612can include, for example, the video application106, the playback application124, and/or other applications or program modules. According to various embodiments, the data612can include, for example, presence applications, visual voice mail applications, messaging applications, text-to-speech and speech-to-text applications, add-ons, plug-ins, email applications, music applications, video applications, camera applications, location-based service applications, power conservation applications, game applications, productivity applications, entertainment applications, enterprise applications, combinations thereof, and the like. The applications610, the data612, and/or portions thereof can be stored in the memory606and/or in a firmware614, and can be executed by the processor604.

It can be appreciated that, at least by virtue of storage of the instructions corresponding to the applications610and/or other instructions embodying other functionality illustrated and described herein in the memory606, and/or by virtue of the instructions corresponding to the applications610and/or other instructions embodying other functionality illustrated and described herein being accessed and/or executed by the processor604, the mobile device600is a special-purpose mobile device that can facilitate providing the functionality illustrated and described herein. The firmware614also can store code for execution during device power up and power down operations. It can be appreciated that the firmware614can be stored in a volatile or non-volatile data storage device including, but not limited to, the memory606and/or a portion thereof.

The mobile device600also can include an input/output (“I/O”) interface616. The I/O interface616can be configured to support the input/output of data such as location information, the media content108, the media content request114, the recorded content116, the manifest file118, the recorded content request122, user information, organization information, presence status information, user IDs, passwords, and application initiation (start-up) requests. In some embodiments, the I/O interface616can include a hardwire connection such as a universal serial bus (“USB”) port, a mini-USB port, a micro-USB port, an audio jack, a PS2 port, an IEEE 1394 (“FIREWIRE”) port, a serial port, a parallel port, an Ethernet (RJ45 or RJ48) port, a telephone (RJ11 or the like) port, a proprietary port, combinations thereof, or the like. In some embodiments, the mobile device600can be configured to synchronize with another device to transfer content to and/or from the mobile device600. In some embodiments, the mobile device600can be configured to receive updates to one or more of the applications610via the I/O interface616, though this is not necessarily the case. In some embodiments, the I/O interface616accepts I/O devices such as keyboards, keypads, mice, interface tethers, printers, plotters, external storage, touch/multi-touch screens, touch pads, trackballs, joysticks, microphones, remote control devices, displays, projectors, medical equipment (e.g., stethoscopes, heart monitors, and other health metric monitors), modems, routers, external power sources, docking stations, combinations thereof, and the like. It should be appreciated that the I/O interface616may be used for communications between the mobile device600and a network device or local device.

The mobile device600also can include a communications component618. The communications component618can be configured to interface with the processor604to facilitate wired and/or wireless communications with one or more networks such as the network104and/or the network connection(s)126described herein. In some embodiments, other networks include networks that utilize non-cellular wireless technologies such as WI-FI or WIMAX. In some embodiments, the communications component618includes a multimode communications subsystem for facilitating communications via the cellular network and one or more other networks.

The communications component618, in some embodiments, includes one or more transceivers. The one or more transceivers, if included, can be configured to communicate over the same and/or different wireless technology standards with respect to one another. For example, in some embodiments one or more of the transceivers of the communications component618may be configured to communicate using GSM, CDMAONE, CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, and greater generation technology standards. Moreover, the communications component618may facilitate communications over various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, TDMA, FDMA, W-CDMA, OFDM, SDMA, and the like.

In addition, the communications component618may facilitate data communications using GPRS, EDGE, the HSPA protocol family including HSDPA, EUL or otherwise termed HSDPA, HSPA+, and various other current and future wireless data access standards. In the illustrated embodiment, the communications component618can include a first transceiver (“TxRx”)620A that can operate in a first communications mode (e.g., GSM). The communications component618also can include an Nthtransceiver (“TxRx”)620N that can operate in a second communications mode relative to the first transceiver620A (e.g., UMTS). While two transceivers620A-N (hereinafter collectively and/or generically referred to as “transceivers620”) are shown inFIG. 6, it should be appreciated that less than two, two, and/or more than two transceivers620can be included in the communications component618.

The communications component618also can include an alternative transceiver (“Alt TxRx”)622for supporting other types and/or standards of communications. According to various contemplated embodiments, the alternative transceiver622can communicate using various communications technologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared, infrared data association (“IRDA”), near field communications (“NFC”), other RF technologies, combinations thereof, and the like. In some embodiments, the communications component618also can facilitate reception from terrestrial radio networks, digital satellite radio networks, internet-based radio service networks, combinations thereof, and the like. The communications component618can process data from a network such as the Internet, an intranet, a broadband network, a WI-FI hotspot, an Internet service provider (“ISP”), a digital subscriber line (“DSL”) provider, a broadband provider, combinations thereof, or the like.

The mobile device600also can include one or more sensors624. The sensors624can include temperature sensors, light sensors, air quality sensors, movement sensors, orientation sensors, noise sensors, proximity sensors, or the like. As such, it should be understood that the sensors624can include, but are not limited to, accelerometers, magnetometers, gyroscopes, infrared sensors, noise sensors, microphones, combinations thereof, or the like. Additionally, audio capabilities for the mobile device600may be provided by an audio I/O component626. The audio I/O component626of the mobile device600can include one or more speakers for the output of audio signals, one or more microphones for the collection and/or input of audio signals, and/or other audio input and/or output devices.

The illustrated mobile device600also can include a subscriber identity module (“SIM”) system628. The SIM system628can include a universal SIM (“USIM”), a universal integrated circuit card (“UICC”) and/or other identity devices. The SIM system628can include and/or can be connected to or inserted into an interface such as a slot interface630. In some embodiments, the slot interface630can be configured to accept insertion of other identity cards or modules for accessing various types of networks. Additionally, or alternatively, the slot interface630can be configured to accept multiple subscriber identity cards. Because other devices and/or modules for identifying users and/or the mobile device600are contemplated, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.

The mobile device600also can include an image capture and processing system632(“image system”). The image system632can be configured to capture or otherwise obtain photos, videos, and/or other visual information. As such, the image system632can include cameras, lenses, charge-coupled devices (“CCDs”), combinations thereof, or the like. The mobile device600may also include a video system634. The video system634can be configured to capture, process, record, modify, and/or store video content. Photos and videos obtained using the image system632and the video system634, respectively, may be added as message content to an MMS message, email message, and sent to another mobile device. The video and/or photo content also can be shared with other devices via various types of data transfers via wired and/or wireless communication devices as described herein.

The mobile device600also can include one or more location components636. The location components636can be configured to send and/or receive signals to determine a geographic location of the mobile device600. According to various embodiments, the location components636can send and/or receive signals from global positioning system (“GPS”) devices, assisted-GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellular network triangulation data, combinations thereof, and the like. The location component636also can be configured to communicate with the communications component618to retrieve triangulation data for determining a location of the mobile device600. In some embodiments, the location component636can interface with cellular network nodes, telephone lines, satellites, location transmitters and/or beacons, wireless network transmitters and receivers, combinations thereof, and the like. In some embodiments, the location component636can include and/or can communicate with one or more of the sensors624such as a compass, an accelerometer, and/or a gyroscope to determine the orientation of the mobile device600. Using the location component636, the mobile device600can generate and/or receive data to identify its geographic location, or to transmit data used by other devices to determine the location of the mobile device600. The location component636may include multiple components for determining the location and/or orientation of the mobile device600.

The illustrated mobile device600also can include a power source638. The power source638can include one or more batteries, power supplies, power cells, and/or other power subsystems including alternating current (“AC”) and/or direct current (“DC”) power devices. The power source638also can interface with an external power system or charging equipment via a power I/O component640. Because the mobile device600can include additional and/or alternative components, the above embodiment should be understood as being illustrative of one possible operating environment for various embodiments of the concepts and technologies described herein. The described embodiment of the mobile device600is illustrative, and should not be construed as being limiting in any way.