Systems and methods for inserting breakpoints and reference links into a media file

BACKGROUND

Video on demand (“VOD”) services are systems which allow users to select and watch video content when they choose to as opposed to having the users watch at a specific broadcast time. Similarly, audio on demand services may allow users to select and listen to content when they choose. Accordingly, on-demand services such as television VOD systems may stream content through a set-top box, a computer or other device, allowing viewing in real time. In addition, VOD services may allow the user to download the content to a device such as a computer, digital video recorder (“DVR”) or portable media player for viewing at any time. The majority of content providers offer streaming VOD, such as pay-per-view and free content, wherein a user buys or selects a movie or television program and it begins to play on the television set immediately. Content providers may also offer the ability to download the content to a DVR or other device (e.g., personal computer (“PC”), tablet, smartphone, etc.) for viewing in the future via a multimedia player application.

The term “application software” refers to any computer software that causes a computer to perform functional tasks beyond the running of the computer itself. Application software applies the power of a particular computing platform or system software to a particular purpose. Specific instance of this software are called software applications, applications or simply “apps.” The term app is used in contrast to system software that typically manages and integrates the capabilities of a computing device but does not directly perform tasks that benefit the user. In other words, the system software serves the app, while the app in turn serves the user.

In recent years, the term “mobile app” has been used to primarily refer to applications for mobile computing devices such as smartphones, tablets, etc. Mobile apps are usually available to a consumer through various application distribution platforms, such as “app stores,” that are typically operated by the owner of the mobile operating system for the mobile computing device. While mobile apps were originally offered for general productivity and information retrieval (e.g., email, calendar, contacts, etc.), the functionality of mobile apps has expanded into other categories such as stock market and weather information, GPS and location-based services, banking, order-tracking, and entertainment such as mobile games and media presentation. In the field of media presentation, mobile apps are used to provide an end user with streaming multimedia to the mobile computing device. Streaming multimedia refers to media that is constantly received by and presented to an end-user while being delivered by a content provider.

Furthermore, the term “social media” has been used primarily to refer to the techniques for interacting among people by creating, sharing, and exchanging information and ideas in virtual communities and networks. Social media may include a group of Internet-based applications (e.g., mobile apps) that allow this creation and exchange of such user-generated content. Those skilled in the art would understand that social media may rely on mobile and web-based technologies to create increasingly interactive platforms for individuals and communities share, create, discuss, and modify user-generated content. Accordingly, mobile technologies, such as mobile apps, introduce substantial changes and a broader reach in the communication between organizations, communities, and individuals within a social media network.

SUMMARY

Described herein are systems and methods for inserting breakpoints and reference links into a multimedia file. A method may comprise receiving breakpoint information from a content provider, wherein the breakpoint information is specific to a first digital media file of a plurality of digital media files, inserting a plurality of breakpoints into the first digital media file based on the breakpoint information, wherein the plurality of breakpoints designate at least one clip within the first digital media file, receiving a user share request from a user device to share the at least one clip within the first digital media file, and providing the user device with a sharable reference link to the at least one clip.

Further described herein is a non-transitory computer readable storage medium with an executable program stored thereon, wherein the program instructs a processor to perform actions. The actions may include receiving breakpoint information from a content provider, wherein the breakpoint information is specific to a first digital media file of a plurality of digital media files, inserting a plurality of breakpoints into the first digital media file based on the breakpoint information, wherein the plurality of breakpoints designate at least one clip within the first digital media file, receiving a user share request from a user device to share the at least one clip within the first digital media file, and providing the user device with a sharable reference link to the at least one clip.

Further described herein is a media on-demand server comprising a memory storing a plurality of rules and a processor coupled to the memory and configured to perform actions. The actions may include receiving breakpoint information from a content provider, wherein the breakpoint information is specific to a first digital media file of a plurality of digital media files, inserting a plurality of breakpoints into the first digital media file based on the breakpoint information, wherein the plurality of breakpoints designate at least one clip within the first digital media file, receiving a user share request from a user device to share the at least one clip within the first digital media file, and providing the user device with a sharable reference link to the at least one clip.

DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> shows an exemplary system for inserting breakpoints and reference links into a media file according to an exemplary embodiment described herein.

<figref idref="DRAWINGS">FIG. 2</figref> shows an exemplary graphical user interface (“GUI”) on a user device running a multimedia application according to an exemplary embodiment described herein.

<figref idref="DRAWINGS">FIG. 3</figref> shows an exemplary method inserting breakpoints and reference links into a media file according to an exemplary embodiment described herein.

DETAILED DESCRIPTION

The exemplary embodiments may be further understood with reference to the following description and the appended drawings, wherein like components are referred to with the same reference numerals. The exemplary embodiments show systems and methods for inserting breakpoints and reference links into a media file.

According to the exemplary embodiments described herein, the systems and methods for inserting breakpoints and reference links into a media file may allow for multimedia content, such as VOD, to be delivered to a user (e.g., viewer) with embedded markers. For instance, these markers embedded into the content serve as starting points and ending points of an abbreviated clip, or “moment,” within the media file. Furthermore, each of these moments may be associated with a sharable reference link. In other words, the user may select a specific moment or clip within the media file and receive a link, such as a hyperlink, to share with other users via various social media networks.

As opposed to sharing the entire duration of the media file, the viewing user may share a particular moment of the file through the use of the sharable reference link. Therefore, the exemplary embodiments may provide the user with the ability to use existing social connections of the user to share interesting moments within multimedia content. While the exemplary embodiments describe the use of social media networks, one skilled in the art will understand that the content may be shared between user across any type of network or multiple networks and services, such as, but not limited to, electronic mail networks, Facebook™, Twitter™, etc.

It may be noted that while the embodiments discussed above relate to a media file featuring embedded markers to designate certain moments within the media file, additional embodiments may include the use of multiple stand-alone files, such as discrete short form content. In other words, as opposed to sharing markers in a single large media file, such as an entire episode of a program, the users may share these discrete short form clips from the episode.

According to an exemplary embodiment of the systems and methods described herein, the content may be presented to the user via an interactive multimedia player application, wherein the content may include instant video files, on-demand videos, full-length episodic video content, music/audio files, news and media feeds, recorded performances, etc. Furthermore, one exemplary embodiment described herein may relate to a dedicated multimedia application executing on a user device, such as a streaming video player. However one skilled in the art will understand that the abilities to view media content, select designated moments, and share moments with other users may be implemented on any number of applications executing on various computer devices, such as set-top boxes, DVR devices, PCs, tablets, smartphones, etc.

<figref idref="DRAWINGS">FIG. 1</figref> shows an exemplary system <b>100</b> for inserting breakpoints and reference links into a media file according to an exemplary embodiment described herein. The system <b>100</b> may include a VOD server <b>110</b>, such as a streaming music/audio and video content application. One skilled in the art will understand that streaming multimedia technology allow users to watch live or on-demand video without downloading a copy directly to a computing device. For instance, the exemplary VOD server <b>110</b> may include interactive features, such as the ability for the user to play, pause, resume, stop, fast-forward, rewind, etc. In addition, the VOD server <b>110</b> may be used in connection to a subscription-based VOD service, wherein the service is offered to users through payment systems that charge subscribers a periodic (e.g., monthly) fee for accessing unlimited content.

In addition to the VOD server <b>110</b>, the exemplary system <b>100</b> may include a multimedia storage component <b>120</b> in communication with the VOD server <b>110</b>. It may be noted that while the storage component <b>120</b> is depicted in system <b>100</b> as a separate component from the VOD server <b>110</b>, additional embodiments of the systems described herein are not limited to the illustrations of <figref idref="DRAWINGS">FIG. 1</figref>. Accordingly, the storage component <b>120</b> may be integrated into the VOD server <b>110</b> as a single stand-alone component. Alternative, each of the components may be located remotely from one another and connected via a network, such as the Internet <b>130</b>. Regardless of the various configurations, the storage component <b>120</b> may store and maintain any number of multimedia content files, such as video content. The VOD server <b>110</b> may access these content files based on requests received by users.

As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, the system <b>100</b> may include additional networks, or sub-networks, such as a social media network <b>140</b>, connected to a plurality of user devices, such as a primary user device <b>150</b> and a secondary user device <b>160</b>. For instances, both of the users of the devices <b>150</b> and <b>160</b> may be members of the same social media network <b>140</b>. In the alternative to the social media network <b>140</b>, the users may be connected to one another simply via the internet <b>130</b>, such as through e-mail correspondence, short message service (“SMS”), enhanced messaging service (“EMS”), multimedia message service (“MMS”), etc.

According to the exemplary embodiments of the system <b>100</b>, the primary user may request media content from the content provider. For instance, the primary user <b>150</b> may visit a webpage of the content provider and view user-selected media through the user's internet browser interface. Alternatively, the primary user may download the multimedia content application for their computing device (e.g., PC, tablet, smartphone, etc.) and initiate streaming media for viewing via the application interface.

As will be described in greater detail below, the primary user <b>150</b> may transmit a user request through the internet <b>130</b> to the VOD server <b>110</b>. Specifically, the user request may indicate specific media content. Examples of the media content accessible by the software application may include instant videos, on-demand videos, full-length episodic video content, behind-the-scenes videos, photographs, news and media feeds, games, puzzles, user polls, advertisements, etc. In addition, it may be noted that certain content (e.g., full-length episodes of content) may be available to the user via a subscriber authentication process.

Upon receiving the user request, the VOD server <b>110</b> may respond be sending the specific content. For instance, the VOD service <b>110</b> may utilize a streaming media protocol to deliver the content to the user device <b>150</b>. The user device <b>150</b> may then utilize a media player to view the content. As discussed above, the media player may be available through an internet browser, a multimedia application (e.g., a mobile app), a plugin, etc.

<figref idref="DRAWINGS">FIG. 2</figref> shows an exemplary GUI <b>200</b> on the primary user device <b>150</b> running the multimedia application according to an exemplary embodiment described herein. The exemplary multimedia application on the user device <b>150</b> may present an interactive media player to the user via the GUI <b>200</b>. The GUI <b>200</b> may include a video playback area <b>230</b>, a progress bar <b>240</b>, and a location marker <b>250</b>. In addition, the GUI <b>200</b> may feature any number of standard elements, such as play/pause buttons, skip buttons, minimize/maximize display buttons, etc. In other words, by receiving user input (e.g., touch screen interactions, point and click input, etc.), the user may control the operation and display of various media content via the GUI <b>200</b> on the user device <b>150</b>.

The progress bar <b>240</b> may include a plurality of breakpoints, or discrete moment markers <b>210</b>, throughout the duration of the media content. These moment markers <b>210</b> may correspond to short clips, or moments, within the media file. For instance, the moments may relate to a brief scene within a full-length episode of a television program. Accordingly, these moment markers <b>210</b> may be designated by the content provider and inserted into the playback of the media file. While the GUI <b>200</b> depicted in <figref idref="DRAWINGS">FIG. 2</figref> includes four separate moments <b>210</b>, it may be noted that the content provider for various media files may designate any number of moments having different lengths.

The GUI <b>200</b> may also feature a plurality of share buttons <b>220</b> to allow the user to share or distribute a specific moment to another user over a variety of communication networks (e.g., social media networks, e-mail correspondence, text messaging, etc.). For instance, while a user is viewing a specific moment of a television as depicted by the moment markers <b>210</b>, the user may select one of the share buttons <b>220</b> to allow a secondary user to view the same moment within the media file. Specifically, each of the moments within the moment markers <b>210</b> may feature an individualize reference link that is specific to the moment, as well as to the selected form for sharing the content.

It may be noted that the shareable moment that is viewed by the secondary user may be in the form of a media file featuring the moment markers <b>210</b> embedded into the file at designated locations. These embedded moment markers <b>210</b> may serve as indicators for starting and stopping the moment selected by the primary user. Alternatively, the shareable moment may be contained in a stand-alone clip, such as an abbreviated media file (e.g., shorter than a full-length episode media file). In other words, an episode of a program may include a plurality of several discrete short-form media files or video clips. Each of these short-form clips may serve as the shareable moment between the primary user and the secondary user.

According to one exemplary embodiment, the user may select to share a moment of an episode with a friend via e-mail correspondence. Using this example, the user may select the “mail” button of the share buttons <b>220</b> while the location marker <b>250</b> is within a certain moment and the playback area <b>230</b> displays that moment. Upon selecting the “mail” button, the user may be provided with a reference link, such as a hyperlink, that is specific to the designated moment. Furthermore, the selection of the “mail” button may automatically open an e-mail application with the hyperlink in the body of a new message and a pre-written subject line in the header. The user may then select one or more recipients of the message and share the reference link to the specific moment with any number of other users. While the example described above relates to sharing moments via e-mail correspondence, one skilled in the art will understand that similar methods may be utilized for sharing reference links to moments via text messaging, social media outlets, etc. Accordingly, the interactive share buttons <b>220</b> of the GUI <b>200</b> may lead the user off the multimedia application to other user interfaces, such as a new e-mail/text message interface, a social media website or third party application.

The exemplary GUI <b>200</b> may also include a metadata tag <b>260</b> (e.g., #Reference) that is specific to the clip being viewed on the video playback area <b>230</b>. Accordingly, this metadata tag <b>260</b> may be included in the sharable reference link provided to the user device <b>150</b>. The GUI <b>200</b> may further include an external link <b>270</b>, such as a “Watch this episode” button, that links the viewing user device <b>150</b> to additional content. Therefore, the user may easily access further related content from a viewed clip of an episode. For instance, if the secondary user device <b>160</b> receives a reference link to this short clip from the primary user device <b>150</b>, the secondary user may be interested in more clips or the entire episode of content. By selecting the external link <b>270</b> from the GUI <b>200</b>, the secondary user device <b>160</b> may then be linked to the multimedia application and/or additional multimedia files available from the content provider.

The exemplary GUI <b>200</b> may also feature any number of additional links, such as a home page link for promoting specific content to the user. In addition, the multimedia application may allow for the user to select specific content or content theme to follow as a user favorite. For instance, the user may select one or more individual pieces of content as a user favorite. In addition, the user may select all content related to a specific theme (e.g., property, actor, character, etc.) as being user favorite content. The user favorite option may allow for the user to easily track or follow all of the content that is most interesting to that user.

<figref idref="DRAWINGS">FIG. 3</figref> shows an exemplary method <b>300</b> for inserting breakpoints and reference links into a media file according to an exemplary embodiment described herein. The steps performed by the method <b>300</b> will be described in reference to the exemplary system <b>100</b> and GUI <b>200</b> and their respective elements as described above with reference to <figref idref="DRAWINGS">FIGS. 1 and 2</figref>. For instance, the VOD server <b>110</b> may a processor and a memory storing a set of instructions executable by the processor.

As described above, the interactive GUI <b>200</b> may be displayed on the primary user device <b>150</b> to interface with the multimedia application provided by the VOD server <b>110</b>. The GUI <b>200</b> may include buttons, such as soft keys, for receiving user requests such as user file requests and user share requests. Furthermore, the GUI <b>200</b> may feature buttons for allowing the user to control the playback of the media file within the multimedia application. The media available to the user device <b>150</b> via the VOD server <b>110</b> may include information content, entertainment content, educational content, advertising and promotional content, commerce content, etc. Examples of the content may include music/audio files, video files, full-length programming episodes, social media and/or news feeds, learning aids and tools, advertisements, etc. According to one embodiment, the media file may be in the form a single full-length episode featuring designated breakpoints or moments markers <b>210</b>. According to a further embodiment, the media file may contain multiple short-form files (e.g., video clips of the full-length episode).

One skilled in the art will understand that the exemplary method <b>300</b> describes one of any number of methods for distributing multimedia content to the user device <b>150</b>. While method <b>300</b> describes the use of a multimedia application, such as a mobile app, in communication with the VOD server <b>110</b>, alternative methods may be implemented by the exemplary systems and methods. For instance, a stand-alone multimedia application is not required, as the user may also provide the VOD server <b>110</b> with user requests via an internet browser. Thus, the delivery of the multimedia content to the user device <b>150</b> is not limited to the method <b>300</b> described in <figref idref="DRAWINGS">FIG. 3</figref>.

In step <b>310</b>, the first digital media file may be stored in the multimedia storage component <b>120</b>. As noted above, the storage component <b>120</b> may be a stand-alone component that is remotely connected to the VOD server <b>110</b> via a network (e.g., an intranet, the internet, etc.). Alternatively, the storage component <b>120</b> may be integrated within the VOD server <b>110</b>. In addition to storing media files, the multimedia storage component <b>120</b> may also maintain, catalog, categorize and organize the files according to any number of characteristics, such as, but not limited to, media types, specific programs and artists, etc. Furthermore, as noted above, the first digital media file may include a plurality of short-form media files, such as video clips designated as shareable moments.

In step <b>320</b>, a plurality of breakpoints may be inserted into a first digital media file stored on the storage component <b>120</b> based on the breakpoint information. These breakpoints may be designated by the content provider to segregate at least one clip, or moment, within the first digital media file. Specifically, the VOD server <b>110</b> may receive breakpoint information from the content provider, wherein the breakpoint information may be specific to the first digital media file of a plurality of digital media files. Furthermore, within the embodiments wherein the first digital media file contains multiple short-form files, the starting points and ending points of these files may serve as the breakpoints.

In step <b>330</b>, a user file request may be received for the first digital media file. Specifically, the user may interact with the VOD server <b>110</b> through the user device <b>150</b>. For instance, the interactions of the user may be performed through the multimedia application or a web browser interface. The VOD server <b>110</b> may provide the user device <b>150</b> with a display of all available multimedia content files, such as a listing of serial television programs including season and episode information.

In step <b>340</b>, the user device <b>150</b> may be provided with the requested media file including the inserted breakpoints. Specifically, the VOD server <b>110</b> may retrieve the first digital media file from the media storage component and transmit the first digital media file to the user device. According to one exemplary embodiment, the user may select a specific episode of a specific season of television program available from the VOD server <b>110</b> of the content provider. Upon receiving the episode, the user device <b>150</b> may be provided with the interactive GUI <b>200</b> to allow the user to control the playback of the media file.

In step <b>350</b>, a user share request may be received from a user device to share the moment or clip within the selected digital media file. Specifically, the user may select one of the share buttons <b>220</b> on the GUI <b>200</b> to initiate a sharing process for distributing the moment to a secondary user on the secondary user device <b>160</b>. Any number of communication options may be available to the user via the share buttons <b>220</b>. The communication options may include e-mail and text correspondence, social media interactions such as broadcast messages and direct messages, blog and message board postings, etc.

In step <b>360</b>, the user device may be provided with a sharable reference link to the at least one clip, thereby allowing the user of the primary user device <b>150</b> to share the requested moment with another user of the secondary user device <b>160</b>. Specifically, the reference link may be formatted to instruct the secondary device <b>160</b> on how to access the clip of the media file. For instance, examples of a sharable reference link may include a uniform resource locator (“URL”), a hyperlink and a direct link to a software application. According to one exemplary embodiment, the sharable reference link may instruct the secondary user device <b>160</b> to open a media player, such as the multimedia application of the content provider or a third-party media player. The reference link may correspond to the specific program episode (e.g., media file) and moment (e.g., abbreviated clip) of the episode.

According to the exemplary systems and methods described herein, the VOD server <b>110</b> may serve as an interactive tool for delivering episodic and branded content to the user on a recurring basis. The VOD server <b>110</b> may allow for new material to be introduced to a user base and shared with new users in a fun and interactive manner. For instance, the sharable content may include memorable moments within existing programming. For instance, the sharable content or moment from a program may include a very funny scene, highly controversial scene, a viral video, or otherwise popular clip from a media file of the content provider. The sharable content may also serve as an innovative way to reach users through different mediums, thereby providing the user with a more in-depth viewing experience. Furthermore, the ability to share moments between users may be tracked and analyzed by the content provider in order to gauge the usage and popularity of the available content, the multimedia application, performers and artists, and the content provider itself.

Those of skill in the art will understand that the above-described exemplary embodiments may be implemented in any number of matters, including as a software application, as a software program, etc. For example, the exemplary method <b>300</b> may be embodied in a program stored in a non-transitory storage medium and containing lines of code that, when compiled, may be executed by a processor (e.g., a processor of the VOD server <b>110</b>). Furthermore, one skilled in the art will understand that the exemplary software application may be coded in any computer readable language, such as, for example, a markup language (e.g., HTML5, etc.).

It will be apparent to those skilled in the art that various modifications may be made in the present invention, without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.