System and method for managing media content

FIELD OF THE DISCLOSURE

The present disclosure relates generally to media management techniques and more specifically to a system and method for managing media content.

BACKGROUND

A number of media formats are available for storing and distributing media content such as video, games, pictures, music, and so on. For example, movie content can be purchased or rented on a digital video disc commonly referred to as a DVD. Newer media formats are now offered with a higher quality of presentation such as high definition or HD DVDs, and Blu-ray DVDs. Music and games are commonly distributed in compact discs or CDs and DVDs at retail stores. Some consumers can choose to purchase media content over a communication medium (e.g., Internet Protocol TV, satellite TV or cable TV video on demand downloads to set-top boxes; iTunes™ to computers, Apple TV™ units and/or iPods™, etc.).

Media content such as described above can be recorded in some instances in computing devices such as laptops, set top boxes, portable media players, entertainment systems of automobiles, and so on.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idrefs="DRAWINGS">FIGS. 1-4</figref> depict illustrative embodiments of communication systems that provide media services;

<figref idrefs="DRAWINGS">FIG. 5</figref> depicts an illustrative embodiment of a portal interacting with at least one among the communication systems of <figref idrefs="DRAWINGS">FIGS. 1-4</figref>;

<figref idrefs="DRAWINGS">FIG. 6</figref> depicts an illustrative method operating in portions of the communication systems of <figref idrefs="DRAWINGS">FIGS. 1-4</figref>;

<figref idrefs="DRAWINGS">FIG. 7</figref> depicts an illustrative embodiment of media presentation devices and media sources coupled to a media distribution system by a wireline of wireless interface; and

<figref idrefs="DRAWINGS">FIG. 8</figref> is a diagrammatic representation of a machine in the form of a computer system within which a set of instructions, when executed, may cause the machine to perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

One embodiment of the present disclosure entails a media distribution system having a controller to identify a plurality of media presentation devices of a user of the MDS, identify one or more distribution preferences supplied by the user for distributing media content to the plurality of media presentation devices, receive media content from one of a plurality of media sources of the user, determine a media content type from the received media content, and distribute the received media content to one or more of the plurality of media presentation devices according to the one or more distribution preferences and the media content type. The one or more distribution preferences comprise in part media content distribution arrangements assigned by the user between the plurality of media sources of the user and the plurality of media presentation devices of the user.

Another embodiment of the present disclosure entails a computer-readable storage medium having computer instructions for receiving media content from one of a plurality of media sources of a user, identifying a media content type from the received media content, and distributing the received media content to one or more of a plurality of media presentation devices of the user according to the identified media content type and one or more media content distribution arrangements assigned by the user between the plurality of media sources of the user and the plurality of media presentation devices of the user.

Yet another embodiment of the present disclosure entails a method involving distributing media content supplied by one of a plurality of media sources of a user to one or more of a plurality of media presentation devices of the user according to a media content type determined from the supplied media content and one or more media content distribution arrangements assigned by the user between the plurality of media sources of the user and the plurality of media presentation devices of the user.

<figref idrefs="DRAWINGS">FIG. 1</figref> depicts an exemplary embodiment of a first communication system <b>100</b> for delivering media content. The communication system <b>100</b> can represent an IPTV broadcast media system. In a typical IPTV infrastructure, there is at least one super head-end office server (SHS) which receives national media programs from satellite and/or media servers from service providers of multimedia broadcast channels. In the present context, media programs can represent audio content, moving image content such as videos, still image content, and/or combinations thereof. The SHS server forwards IP packets associated with the media content to video head-end servers (VHS) via a network of aggregation points such as video head-end offices (VHO) according to a common multicast communication method.

The VHS then distributes multimedia broadcast programs via a local area network (LAN) to commercial and/or residential buildings <b>102</b> housing a gateway <b>104</b> (e.g., a residential gateway or RG). The LAN can represent a bank of digital subscriber line access multiplexers (DSLAMs) located in a central office or a service area interface that provide broadband services over optical links or copper twisted pairs to buildings <b>102</b>. The gateway <b>104</b> distributes broadcast signals to media processors <b>106</b> such as Set-Top Boxes (STBs) which in turn present broadcast selections to media presentation devices <b>108</b> such as computers or television sets managed in some instances by a media controller <b>107</b> (e.g., an infrared or RF remote control). Unicast traffic can also be exchanged between the media processors <b>106</b> and subsystems of the IPTV media system for services such as video-on-demand (VoD). It will be appreciated by one of ordinary skill in the art that the media presentation devices <b>108</b> and/or portable communication devices <b>116</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref> can be an integral part of the media processor <b>106</b> and can be communicatively coupled to the gateway <b>104</b>. In this particular embodiment, an integral device such as described can receive, respond, process and present multicast or unicast media content.

The IPTV media system can be coupled to one or more computing devices <b>130</b> a portion of which can operate as a web server for providing portal services over an Internet Service Provider (ISP) network <b>132</b> to fixed line media presentation devices <b>108</b> or portable communication devices <b>116</b> by way of a wireless access point <b>117</b> providing Wireless Fidelity or WiFi services, or cellular communication services (e.g., GSM, CDMA, UMTS, WiMAX, etc.).

Another distinct portion of the one or more computing devices <b>130</b> can be utilized as a media distribution system (MDS) <b>130</b> for collecting media content from a number of media sources, and for distributing said media content according to media content types and distribution preferences. Media content can represent audio content (e.g., MP3 music files, recordings made by a user with any number of audio recording devices), visual content (e.g., pictures, video, literature with text and graphics, news reports, etc.), or combinations thereof.

Media sources can represent any number of content sources such as Internet media content sources (e.g., VoD catalogs, music and movies from iTunes™, etc.), a portable media player (e.g., iPod™), still image recorders such as standalone digital cameras or digital cameras embedded in cell phones, moving image recorders such as standalone digital camcorders or video recorders in a cell phone, and/or audio recorders which can record radio programs, ambient sound, or otherwise. The above media sources can be communicatively coupled to the MDS <b>130</b> by a tethered wireline connection (e.g., broadband xDSL or cable, USB connection, etc.), or by way of a wireless interface such as wireless fidelity (WiFi), or common cellular access technologies (e.g., CDMA, GSM, UMTS, etc.).

The media presentation devices are computing devices capable of presenting media content redistributed by the MDS <b>130</b>. Media presentation devices can be represented for example by a computing device (e.g., a laptop computer), a portable media player (e.g., iPod™), an entertainment system of an automobile coupled to for example a telemetry system of the automobile, a set top box such as the ones illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref>. Other media presentation devices suitable to the present disclosure can also be considered. Media presentation devices can receive media content from the MDS <b>130</b> over common tethered interfaces (e.g., broadband DSL or cable, USB connection, etc.), or by a wireless medium such as WiFi, or cellular.

In another illustrative embodiment, the MDS <b>130</b> can represent a computing device located in building <b>102</b>. The computing device can represent a laptop computer, a desktop computer, a set top box, or another suitable computing device that can exchange media content between media sources and media presentation devices.

From the foregoing embodiments, it should be apparent to one of ordinary skill in the art that the MDS <b>130</b> can reside in any location of the media communication system <b>100</b>. Additionally, the MDS <b>130</b> can operate as a distributed or centralized computing device. For example, large storage devices of the MDS <b>130</b> can be made accessible by way of the media communication system <b>100</b> and located outside of the premises of a subscriber, while the computing portion of the MDS can reside in building <b>102</b>.

It should be further understood that the terms media sources and media presentation devices can be interchangeable. That is, in some instances a media presentation device that has recently recorded new media content can serve as a media source to the MDS <b>130</b>, while a media source can serve as a media presentation device when new media content is available from another device. Accordingly, any computing device that can receive and/or present media content can serve as either a media source supplying media content or a media presentation device capable of presenting media content.

In yet another illustrative embodiment, a satellite broadcast television system can be used in place of the IPTV media system. In this embodiment, signals transmitted by a satellite <b>115</b> can be intercepted by a satellite dish receiver <b>131</b> coupled to building <b>102</b> which conveys media signals to the media processors <b>106</b>. The media receivers <b>106</b> can be equipped with a broadband port to the ISP network <b>132</b>. Although not shown, the communication system <b>100</b> can also be combined or replaced with analog or digital broadcast distributions systems such as cable TV systems.

<figref idrefs="DRAWINGS">FIG. 2</figref> depicts an exemplary embodiment of a second communication system <b>200</b> for delivering media content. Communication system <b>200</b> can be overlaid or operably coupled with communication system <b>100</b> as another representative embodiment of said communication system. The system <b>200</b> includes a distribution switch/router system <b>228</b> at a central office <b>218</b>. The distribution switch/router system <b>228</b> receives video data via a multicast television stream <b>230</b> from a second distribution switch/router <b>234</b> at an intermediate office <b>220</b>. The multicast television stream <b>230</b> includes Internet Protocol (IP) data packets addressed to a multicast IP address associated with a television channel. The distribution switch/router system <b>228</b> can cache data associated with each television channel received from the intermediate office <b>220</b>.

The distribution switch/router system <b>228</b> also receives unicast data traffic from the intermediate office <b>220</b> via a unicast traffic stream <b>232</b>. The unicast traffic stream <b>232</b> includes data packets related to devices located at a particular residence, such as the residence <b>202</b>. For example, the unicast traffic stream <b>232</b> can include data traffic related to a digital subscriber line, a telephone line, another data connection, or any combination thereof. To illustrate, the unicast traffic stream <b>232</b> can communicate data packets to and from a telephone <b>212</b> associated with a subscriber at the residence <b>202</b>. The telephone <b>212</b> can be a Voice over Internet Protocol (VoIP) telephone. To further illustrate, the unicast traffic stream <b>232</b> can communicate data packets to and from a personal computer <b>210</b> at the residence <b>202</b> via one or more data routers <b>208</b>. In an additional illustration, the unicast traffic stream <b>232</b> can communicate data packets to and from a set-top box device, such as the set-top box devices <b>204</b>, <b>206</b>. The unicast traffic stream <b>232</b> can communicate data packets to and from the devices located at the residence <b>202</b> via one or more residential gateways <b>214</b> associated with the residence <b>202</b>.

The distribution switch/router system <b>228</b> can send data to one or more access switch/router systems <b>226</b>. The access switch/router system <b>226</b> can include or be included within a service area interface <b>216</b>. In a particular embodiment, the access switch/router system <b>226</b> can include a DSLAM. The access switch/router system <b>226</b> can receive data from the distribution switch/router system <b>228</b> via a broadcast television (BTV) stream <b>222</b> and a plurality of unicast subscriber traffic streams <b>224</b>. The BTV stream <b>222</b> can be used to communicate video data packets associated with a multicast stream.

For example, the BTV stream <b>222</b> can include a multicast virtual local area network (VLAN) connection between the distribution switch/router system <b>228</b> and the access switch/router system <b>226</b>. Each of the plurality of subscriber traffic streams <b>224</b> can be used to communicate subscriber specific data packets. For example, the first subscriber traffic stream can communicate data related to a first subscriber, and the nth subscriber traffic stream can communicate data related to an nth subscriber. Each subscriber to the system <b>200</b> can be associated with a respective subscriber traffic stream <b>224</b>. The subscriber traffic stream <b>224</b> can include a subscriber VLAN connection between the distribution switch/router system <b>228</b> and the access switch/router system <b>226</b> that is associated with a particular set-top box device <b>204</b>, <b>206</b>, a particular residence <b>202</b>, a particular residential gateway <b>214</b>, another device associated with a subscriber, or any combination thereof.

In an illustrative embodiment, a set-top box device, such as the set-top box device <b>204</b>, receives a channel change command from an input device, such as a remoter control device. The channel change command can indicate selection of an IPTV channel. After receiving the channel change command, the set-top box device <b>204</b> generates channel selection data that indicates the selection of the IPTV channel. The set-top box device <b>204</b> can send the channel selection data to the access switch/router system <b>226</b> via the residential gateway <b>214</b>. The channel selection data can include an Internet Group Management Protocol (IGMP) Join request. In an illustrative embodiment, the access switch/router system <b>226</b> can identify whether it is joined to a multicast group associated with the requested channel based on information in the IGMP Join request.

If the access switch/router system <b>226</b> is not joined to the multicast group associated with the requested channel, the access switch/router system <b>226</b> can generate a multicast stream request. The multicast stream request can be generated by modifying the received channel selection data. In an illustrative embodiment, the access switch/router system <b>226</b> can modify an IGMP Join request to produce a proxy IGMP Join request. The access switch/router system <b>226</b> can send the multicast stream request to the distribution switch/router system <b>228</b> via the BTV stream <b>222</b>. In response to receiving the multicast stream request, the distribution switch/router system <b>228</b> can send a stream associated with the requested channel to the access switch/router system <b>226</b> via the BTV stream <b>222</b>.

The MDS <b>130</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> can be operably coupled to the second communication system <b>200</b> for purposes of collecting and distributing media content by way of the second communication system.

<figref idrefs="DRAWINGS">FIG. 3</figref> depicts an exemplary embodiment of a third communication system <b>300</b> for delivering media content. Communication system <b>300</b> can be overlaid or operably coupled with communication systems <b>100</b>-<b>200</b> as another representative embodiment of said communication systems. As shown, the system <b>300</b> can include a client facing tier <b>302</b>, an application tier <b>304</b>, an acquisition tier <b>306</b>, and an operations and management tier <b>308</b>. Each tier <b>302</b>, <b>304</b>, <b>306</b>, <b>308</b> is coupled to a private network <b>310</b>, such as a network of common packet-switched routers and/or switches; to a public network <b>312</b>, such as the Internet; or to both the private network <b>310</b> and the public network <b>312</b>. For example, the client-facing tier <b>302</b> can be coupled to the private network <b>310</b>. Further, the application tier <b>304</b> can be coupled to the private network <b>310</b> and to the public network <b>312</b>. The acquisition tier <b>306</b> can also be coupled to the private network <b>310</b> and to the public network <b>312</b>. Additionally, the operations and management tier <b>308</b> can be coupled to the public network <b>322</b>.

As illustrated in <figref idrefs="DRAWINGS">FIG. 3</figref>, the various tiers <b>302</b>, <b>304</b>, <b>306</b>, <b>308</b> communicate with each other via the private network <b>310</b> and the public network <b>312</b>. For instance, the client-facing tier <b>302</b> can communicate with the application tier <b>304</b> and the acquisition tier <b>306</b> via the private network <b>310</b>. The application tier <b>304</b> can communicate with the acquisition tier <b>306</b> via the private network <b>310</b>. Further, the application tier <b>304</b> can communicate with the acquisition tier <b>306</b> and the operations and management tier <b>308</b> via the public network <b>312</b>. Moreover, the acquisition tier <b>306</b> can communicate with the operations and management tier <b>308</b> via the public network <b>312</b>. In a particular embodiment, elements of the application tier <b>304</b>, including, but not limited to, a client gateway <b>350</b>, can communicate directly with the client-facing tier <b>302</b>.

The client-facing tier <b>302</b> can communicate with user equipment via an access network <b>366</b>, such as an IPTV access network. In an illustrative embodiment, customer premises equipment (CPE) <b>314</b>, <b>322</b> can be coupled to a local switch, router, or other device of the access network <b>366</b>. The client-facing tier <b>302</b> can communicate with a first representative set-top box device <b>316</b> via the first CPE <b>314</b> and with a second representative set-top box device <b>324</b> via the second CPE <b>322</b>. In a particular embodiment, the first representative set-top box device <b>316</b> and the first CPE <b>314</b> can be located at a first customer premise, and the second representative set-top box device <b>324</b> and the second CPE <b>322</b> can be located at a second customer premise.

In another particular embodiment, the first representative set-top box device <b>316</b> and the second representative set-top box device <b>324</b> can be located at a single customer premise, both coupled to one of the CPE <b>314</b>, <b>322</b>. The CPE <b>314</b>, <b>322</b> can include routers, local area network devices, modems, such as digital subscriber line (DSL) modems, any other suitable devices for facilitating communication between a set-top box device and the access network <b>366</b>, or any combination thereof.

In an exemplary embodiment, the client-facing tier <b>302</b> can be coupled to the CPE <b>314</b>, <b>322</b> via fiber optic cables. In another exemplary embodiment, the CPE <b>314</b>, <b>322</b> can include DSL modems that are coupled to one or more network nodes via twisted pairs, and the client-facing tier <b>302</b> can be coupled to the network nodes via fiber-optic cables. Each set-top box device <b>316</b>, <b>324</b> can process data received via the access network <b>366</b>, via a common IPTV software platform.

The first set-top box device <b>316</b> can be coupled to a first external display device, such as a first television monitor <b>318</b>, and the second set-top box device <b>324</b> can be coupled to a second external display device, such as a second television monitor <b>326</b>. Moreover, the first set-top box device <b>316</b> can communicate with a first remote control <b>320</b>, and the second set-top box device <b>324</b> can communicate with a second remote control <b>328</b>. The set-top box devices <b>316</b>, <b>324</b> can include IPTV set-top box devices; video gaming devices or consoles that are adapted to receive IPTV content; personal computers or other computing devices that are adapted to emulate set-top box device functionalities; any other device adapted to receive IPTV content and transmit data to an IPTV system via an access network; or any combination thereof.

In an exemplary, non-limiting embodiment, each set-top box device <b>316</b>, <b>324</b> can receive data, video, or any combination thereof, from the client-facing tier <b>302</b> via the access network <b>366</b> and render or display the data, video, or any combination thereof, at the display device <b>318</b>, <b>326</b> to which it is coupled. In an illustrative embodiment, the set-top box devices <b>316</b>, <b>324</b> can include tuners that receive and decode television programming signals or packet streams for transmission to the display devices <b>318</b>, <b>326</b>. Further, the set-top box devices <b>316</b>, <b>324</b> can each include a STB processor <b>370</b> and a STB memory device <b>372</b> that is accessible to the STB processor <b>370</b>. In one embodiment, a computer program, such as the STB computer program <b>374</b>, can be embedded within the STB memory device <b>372</b>.

In an illustrative embodiment, the client-facing tier <b>302</b> can include a client-facing tier (CFT) switch <b>330</b> that manages communication between the client-facing tier <b>302</b> and the access network <b>366</b> and between the client-facing tier <b>302</b> and the private network <b>310</b>. As illustrated, the CFT switch <b>330</b> is coupled to one or more distribution servers, such as Distribution-servers (D-servers) <b>332</b>, that store, format, encode, replicate, or otherwise manipulate or prepare video content for communication from the client-facing tier <b>302</b> to the set-top box devices <b>316</b>, <b>324</b>. The CFT switch <b>330</b> can also be coupled to a terminal server <b>334</b> that provides terminal devices with a point of connection to the IPTV system <b>300</b> via the client-facing tier <b>302</b>.

In a particular embodiment, the CFT switch <b>330</b> can be coupled to a video-on-demand (VOD) server <b>336</b> that stores or provides VOD content imported by the IPTV system <b>300</b>. Further, the CFT switch <b>330</b> is coupled to one or more video servers <b>380</b> that receive video content and transmit the content to the set-top boxes <b>316</b>, <b>324</b> via the access network <b>366</b>. The client-facing tier <b>302</b> may include a CPE management server <b>382</b> that manages communications to and from the CPE <b>314</b> and the CPE <b>322</b>. For example, the CPE management server <b>382</b> may collect performance data associated with the set-top box devices <b>316</b>, <b>324</b> from the CPE <b>314</b> or the CPE <b>322</b> and forward the collected performance data to a server associated with the operations and management tier <b>308</b>.

In an illustrative embodiment, the client-facing tier <b>302</b> can communicate with a large number of set-top boxes, such as the representative set-top boxes <b>316</b>, <b>324</b>, over a wide geographic area, such as a metropolitan area, a viewing area, a statewide area, a regional area, a nationwide area or any other suitable geographic area, market area, or subscriber or customer group that can be supported by networking the client-facing tier <b>302</b> to numerous set-top box devices. In a particular embodiment, the CFT switch <b>330</b>, or any portion thereof, can include a multicast router or switch that communicates with multiple set-top box devices via a multicast-enabled network.

As illustrated in <figref idrefs="DRAWINGS">FIG. 3</figref>, the application tier <b>304</b> can communicate with both the private network <b>310</b> and the public network <b>312</b>. The application tier <b>304</b> can include a first application tier (APP) switch <b>338</b> and a second APP switch <b>340</b>. In a particular embodiment, the first APP switch <b>338</b> can be coupled to the second APP switch <b>340</b>. The first APP switch <b>338</b> can be coupled to an application server <b>342</b> and to an OSS/BSS gateway <b>344</b>. In a particular embodiment, the application server <b>342</b> can provide applications to the set-top box devices <b>316</b>, <b>324</b> via the access network <b>366</b>, which enable the set-top box devices <b>316</b>, <b>324</b> to provide functions, such as interactive program guides, video gaming, display, messaging, processing of VOD material and other IPTV content, etc. In an illustrative embodiment, the application server <b>342</b> can provide location information to the set-top box devices <b>316</b>, <b>324</b>. In a particular embodiment, the OSS/BSS gateway <b>344</b> includes operation systems and support (OSS) data, as well as billing systems and support (BSS) data. In one embodiment, the OSS/BSS gateway <b>344</b> can provide or restrict access to an OSS/BSS server <b>364</b> that stores operations and billing systems data.

The second APP switch <b>340</b> can be coupled to a domain controller <b>346</b> that provides Internet access, for example, to users at their computers <b>368</b> via the public network <b>312</b>. For example, the domain controller <b>346</b> can provide remote Internet access to IPTV account information, e-mail, personalized Internet services, or other online services via the public network <b>312</b>. In addition, the second APP switch <b>340</b> can be coupled to a subscriber and system store <b>348</b> that includes account information, such as account information that is associated with users who access the IPTV system <b>300</b> via the private network <b>310</b> or the public network <b>312</b>. In an illustrative embodiment, the subscriber and system store <b>348</b> can store subscriber or customer data and create subscriber or customer profiles that are associated with IP addresses, stock-keeping unit (SKU) numbers, other identifiers, or any combination thereof, of corresponding set-top box devices <b>316</b>, <b>324</b>. In another illustrative embodiment, the subscriber and system store can store data associated with capabilities of set-top box devices associated with particular customers.

In a particular embodiment, the application tier <b>304</b> can include a client gateway <b>350</b> that communicates data directly to the client-facing tier <b>302</b>. In this embodiment, the client gateway <b>350</b> can be coupled directly to the CFT switch <b>330</b>. The client gateway <b>350</b> can provide user access to the private network <b>310</b> and the tiers coupled thereto. In an illustrative embodiment, the set-top box devices <b>316</b>, <b>324</b> can access the IPTV system <b>300</b> via the access network <b>366</b>, using information received from the client gateway <b>350</b>. User devices can access the client gateway <b>350</b> via the access network <b>366</b>, and the client gateway <b>350</b> can allow such devices to access the private network <b>310</b> once the devices are authenticated or verified. Similarly, the client gateway <b>350</b> can prevent unauthorized devices, such as hacker computers or stolen set-top box devices from accessing the private network <b>310</b>, by denying access to these devices beyond the access network <b>366</b>.

For example, when the first representative set-top box device <b>316</b> accesses the client-facing tier <b>302</b> via the access network <b>366</b>, the client gateway <b>350</b> can verify subscriber information by communicating with the subscriber and system store <b>348</b> via the private network <b>310</b>. Further, the client gateway <b>350</b> can verify billing information and status by communicating with the OSS/BSS gateway <b>344</b> via the private network <b>310</b>. In one embodiment, the OSS/BSS gateway <b>344</b> can transmit a query via the public network <b>312</b> to the OSS/BSS server <b>364</b>. After the client gateway <b>350</b> confirms subscriber and/or billing information, the client gateway <b>350</b> can allow the set-top box device <b>316</b> to access IPTV content and VOD content at the client-facing tier <b>302</b>. If the client gateway <b>350</b> cannot verify subscriber information for the set-top box device <b>316</b>, e.g., because it is connected to an unauthorized twisted pair, the client gateway <b>350</b> can block transmissions to and from the set-top box device <b>316</b> beyond the access network <b>366</b>.

As indicated in <figref idrefs="DRAWINGS">FIG. 3</figref>, the acquisition tier <b>306</b> includes an acquisition tier (AQT) switch <b>352</b> that communicates with the private network <b>310</b>. The AQT switch <b>352</b> can also communicate with the operations and management tier <b>308</b> via the public network <b>312</b>. In a particular embodiment, the AQT switch <b>352</b> can be coupled to one or more live Acquisition-servers (A-servers) <b>354</b> that receive or acquire television content, movie content, advertisement content, other video content, or any combination thereof, from a broadcast service <b>356</b>, such as a satellite acquisition system or satellite head-end office. In a particular embodiment, the live acquisition server <b>354</b> can transmit content to the AQT switch <b>352</b>, and the AQT switch <b>352</b> can transmit the content to the CFT switch <b>330</b> via the private network <b>310</b>.

In an illustrative embodiment, content can be transmitted to the D-servers <b>332</b>, where it can be encoded, formatted, stored, replicated, or otherwise manipulated and prepared for communication from the video server(s) <b>380</b> to the set-top box devices <b>316</b>, <b>324</b>. The CFT switch <b>330</b> can receive content from the video server(s) <b>380</b> and communicate the content to the CPE <b>314</b>, <b>322</b> via the access network <b>366</b>. The set-top box devices <b>316</b>, <b>324</b> can receive the content via the CPE <b>314</b>, <b>322</b>, and can transmit the content to the television monitors <b>318</b>, <b>326</b>. In an illustrative embodiment, video or audio portions of the content can be streamed to the set-top box devices <b>316</b>, <b>324</b>.

Further, the AQT switch <b>352</b> can be coupled to a video-on-demand importer server <b>358</b> that receives and stores television or movie content received at the acquisition tier <b>306</b> and communicates the stored content to the VOD server <b>336</b> at the client-facing tier <b>302</b> via the private network <b>310</b>. Additionally, at the acquisition tier <b>306</b>, the video-on-demand (VOD) importer server <b>358</b> can receive content from one or more VOD sources outside the IPTV system <b>300</b>, such as movie studios and programmers of non-live content. The VOD importer server <b>358</b> can transmit the VOD content to the AQT switch <b>352</b>, and the AQT switch <b>352</b>, in turn, can communicate the material to the CFT switch <b>330</b> via the private network <b>310</b>. The VOD content can be stored at one or more servers, such as the VOD server <b>336</b>.

When users issue requests for VOD content via the set-top box devices <b>316</b>, <b>324</b>, the requests can be transmitted over the access network <b>366</b> to the VOD server <b>336</b>, via the CFT switch <b>330</b>. Upon receiving such requests, the VOD server <b>336</b> can retrieve the requested VOD content and transmit the content to the set-top box devices <b>316</b>, <b>324</b> across the access network <b>366</b>, via the CFT switch <b>330</b>. The set-top box devices <b>316</b>, <b>324</b> can transmit the VOD content to the television monitors <b>318</b>, <b>326</b>. In an illustrative embodiment, video or audio portions of VOD content can be streamed to the set-top box devices <b>316</b>, <b>324</b>.

<figref idrefs="DRAWINGS">FIG. 3</figref> further illustrates that the operations and management tier <b>308</b> can include an operations and management tier (OMT) switch <b>360</b> that conducts communication between the operations and management tier <b>308</b> and the public network <b>312</b>. In the embodiment illustrated by <figref idrefs="DRAWINGS">FIG. 3</figref>, the OMT switch <b>360</b> is coupled to a TV2 server <b>362</b>. Additionally, the OMT switch <b>360</b> can be coupled to an OSS/BSS server <b>364</b> and to a simple network management protocol monitor <b>386</b> that monitors network devices within or coupled to the IPTV system <b>300</b>. In a particular embodiment, the OMT switch <b>360</b> can communicate with the AQT switch <b>352</b> via the public network <b>312</b>.

The OSS/BSS server <b>364</b> may include a cluster of servers, such as one or more CPE data collection servers that are adapted to request and store operations systems data, such as performance data from the set-top box devices <b>316</b>, <b>324</b>. In an illustrative embodiment, the CPE data collection servers may be adapted to analyze performance data to identify a condition of a physical component of a network path associated with a set-top box device, to predict a condition of a physical component of a network path associated with a set-top box device, or any combination thereof.

In an illustrative embodiment, the live acquisition server <b>354</b> can transmit content to the AQT switch <b>352</b>, and the AQT switch <b>352</b>, in turn, can transmit the content to the OMT switch <b>360</b> via the public network <b>312</b>. In this embodiment, the OMT switch <b>360</b> can transmit the content to the TV2 server <b>362</b> for display to users accessing the user interface at the TV2 server <b>362</b>. For example, a user can access the TV2 server <b>362</b> using a personal computer <b>368</b> coupled to the public network <b>312</b>.

The MDS <b>130</b> of <figref idrefs="DRAWINGS">FIGS. 1-2</figref> can be operably coupled to the third communication system <b>300</b> for purposes of collecting and distributing media content by way of the third communication system.

It should be apparent to one of ordinary skill in the art from the foregoing media communication system embodiments that other suitable media communication systems for distributing broadcast media content as well as peer-to-peer exchange of content can be applied to the present disclosure.

<figref idrefs="DRAWINGS">FIG. 4</figref> depicts an exemplary embodiment of a communication system <b>400</b> employing a IP Multimedia Subsystem (IMS) network architecture. Communication system <b>400</b> can be overlaid or operably coupled with communication systems <b>100</b>-<b>300</b> as another representative embodiment of said communication systems.

The communication system <b>400</b> can comprise a Home Subscriber Server (HSS) <b>440</b>, a tElephone NUmber Mapping (ENUM) server <b>430</b>, and network elements of an IMS network <b>450</b>. The IMS network <b>450</b> can be coupled to IMS compliant communication devices (CD) <b>401</b>, <b>402</b> or a Public Switched Telephone Network (PSTN) CD <b>403</b> using a Media Gateway Control Function (MGCF) <b>420</b> that connects the call through a common PSTN network <b>460</b>.

IMS CDs <b>401</b>, <b>402</b> register with the IMS network <b>450</b> by contacting a Proxy Call Session Control Function (P-CSCF) which communicates with a corresponding Serving CSCF (S-CSCF) to register the CDs with an Authentication, Authorization and Accounting (AAA) support by the HSS <b>440</b>. To accomplish a communication session between CDs, an originating IMS CD <b>401</b> can submit a SIP INVITE message to an originating P-CSCF <b>404</b> which communicates with a corresponding originating S-CSCF <b>406</b>. The originating S-CSCF <b>406</b> can submit the SIP INVITE message to an application server (AS) such as reference <b>410</b> that can provide a variety of services to IMS subscribers. For example, the application server <b>410</b> can be used to perform originating treatment functions on the calling party number received by the originating S-CSCF <b>406</b> in the SIP INVITE message.

Originating treatment functions can include determining whether the calling party number has international calling services, and/or is requesting special telephony features (e.g., *72 forward calls, *73 cancel call forwarding, *67 for caller ID blocking, and so on). Additionally, the originating S-CSCF <b>406</b> can submit queries to the ENUM system <b>430</b> to translate an E. <b>164</b> telephone number to a SIP Uniform Resource Identifier (URI) if the targeted communication device is IMS compliant. If the targeted communication device is a PSTN device, the ENUM system <b>430</b> will respond with an unsuccessful address resolution and the S-CSCF <b>406</b> will forward the call to the MGCF <b>420</b> via a Breakout Gateway Control Function (BGCF) <b>419</b>.

When the ENUM server <b>430</b> returns a SIP URI, the SIP URI is used by an Interrogating CSCF (I-CSCF) <b>407</b> to submit a query to the HSS <b>440</b> to identify a terminating S-CSCF <b>414</b> associated with a terminating IMS CD such as reference <b>402</b>. Once identified, the I-CSCF <b>407</b> can submit the SIP INVITE to the terminating S-CSCF <b>414</b> which can call on an application server <b>411</b> similar to reference <b>410</b> to perform the originating treatment telephony functions described earlier. The terminating S-CSCF <b>414</b> can then identify a terminating P-CSCF <b>416</b> associated with the terminating CD <b>402</b>. The P-CSCF <b>416</b> then signals the CD <b>402</b> to establish communications. The aforementioned process is symmetrical. Accordingly, the terms “originating” and “terminating” in <figref idrefs="DRAWINGS">FIG. 4</figref> can be interchanged.

IMS network <b>450</b> can also be operably coupled to the MDS <b>130</b> previously discussed for <figref idrefs="DRAWINGS">FIG. 1</figref>. In this representative embodiment, the MDS <b>130</b> can be accessed over a PSTN or VoIP channel of communication system <b>400</b> by common techniques such as described above.

<figref idrefs="DRAWINGS">FIG. 5</figref> depicts an exemplary embodiment of a portal <b>530</b>. The portal <b>530</b> can be used for managing services of communication systems <b>100</b>-<b>400</b>. The portal <b>530</b> can be accessed by a Uniform Resource Locator (URL) with a common Internet browser such as Microsoft's Internet Explorer using an Internet-capable communication device such as references <b>108</b>, <b>116</b>, or <b>210</b> of <figref idrefs="DRAWINGS">FIGS. 1-2</figref>. The portal <b>530</b> can be configured to access a media processor such as references <b>106</b>, <b>204</b>, <b>206</b>, <b>316</b>, and <b>324</b> of <figref idrefs="DRAWINGS">FIGS. 1-3</figref> and services managed thereby such as a Digital Video Recorder (DVR), an Electronic Programming Guide (EPG), VOD catalog, a personal catalog stored in the STB (e.g., personal videos, pictures, audio recordings, etc.), and so on. The portal <b>530</b> can also be used by the subscriber to provision the MDS <b>130</b> with media content distribution preferences.

<figref idrefs="DRAWINGS">FIG. 6</figref> depicts an exemplary method <b>600</b> operating in portions of communication systems <b>100</b>-<b>400</b>. Method <b>600</b> illustrates one of several embodiments for collecting media content from media sources and distributing said media content to some or all media presentation devices accessible by the MDS <b>130</b>. <figref idrefs="DRAWINGS">FIG. 7</figref> provides an illustration of media presentation devices and media sources coupled to the MDS <b>130</b> by a wireline or wireless interface. As noted earlier, the MDS <b>130</b> can reside in the premises of a subscriber, remotely in any of the media communication systems of <figref idrefs="DRAWINGS">FIGS. 1-4</figref>, or decentralized with portions of the MDS distributed in disparate locations. In the case where the MDS <b>130</b> is remotely situated from a user, the user can access the MDS <b>130</b> by way of portal <b>530</b>.

With these principles in mind, method <b>600</b> begins with step <b>602</b> in which the MDS <b>130</b> receives software applications associated with media sources and/or media presentation devices. The software applications can represent common libraries and/or plug-ins to facilitate at the MDS <b>130</b> receiving and processing media content from media sources as well as for distributing media content to the media presentation devices. The software applications can also provide a means for the MDS <b>130</b> to detect the entry of a media source or media presentation device in a network from which the MDS is operating.

Once these software applications have been installed in the MDS <b>130</b>, the MDS can proceed to step <b>604</b> where it monitors for the entry of a media source in its network with new media content not previously available to the media presentation devices. If a media source is detected, but the MDS <b>130</b> has in its data banks a copy of the media content recorded in the media source or is aware that the media content has already been distributed to the media devices, the MDS ignores the detection and continues to search for media sources with new media content. Once a media source with new media content is detected by the MDS <b>130</b>, the MDS proceeds to step <b>606</b> where it retrieves the new media content (using the software applications of step <b>602</b> to facilitate the retrieval) and determines in step <b>608</b> one or more media content types.

A media content type can represent an audio content type (e.g., MP3, WAV, etc.), a visual content type (e.g., MP4, JPEG, GIF, etc.), or combinations thereof. In step <b>610</b>, the MDS <b>130</b> identifies one or more distribution preferences established by a subscriber. The distribution preferences can represent user-defined macros for directing a distribution of media content according to media content distribution arrangements assigned by the user between a plurality of media sources of the user and the plurality of media presentation devices of the user.

For example, suppose a subscriber enters a network from which the MDS <b>130</b> is operating with a cell phone that has a digital camera that can capture still pictures as well as videos in JPEG and MP4 formats respectfully. Also assume the subscriber has a media player built into the phone such as is available with iPhones™ with a library of songs (MP3 files) and videos (MP4 files) which the user has purchased from iTunes™. In this hypothetical example the cell phone can serve as a media source detected in step <b>604</b> with new media content.

Further suppose that the subscriber has an STB in his or her residence such as the ones illustrated in <figref idrefs="DRAWINGS">FIGS. 1-3</figref> which can present still pictures, videos, and music in the abovementioned formats. Also, assume that the subscriber has an automobile entertainment system that can play MP3 music files and can wirelessly communicate with the MDS <b>130</b> over a cellular network such as <b>117</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>.

With the above devices in mind, the subscriber can provision the MDS <b>130</b> from a common interface such as a portal <b>530</b> with distribution preferences to address how the media content of the above illustration is to be distributed. The portal <b>530</b> can present the subscriber a common graphical user interface (GUI) to enter and define macros for assigning a distribution arrangement between the media sources and the media presentation devices of the subscriber. Referring back to the illustration, the subscriber can specify that all new media files in the cellular phone (MP3, MP4, and JPEG files) are to be distributed to the STB, while only MP3 files are to be distributed to the entertainment system of the automobile. If the automobile has a video system such as a DVD player which can present MP4 files, the subscriber can also define in the distribution preferences that MP4 files are to be distributed to the entertainment system of the automobile.

By way of the GUI interface of the portal <b>530</b> the subscriber can also identify a number of possible media sources and media presentation devices which the MDS <b>130</b> can communicate with. The descriptions of the media sources and media presentation devices can include among other things one or more communication identifiers (e.g., IP address, SIP URI, URL, telephone number, etc.), model numbers, computing resource capabilities, and so on.

Under circumstances where media sources and media presentation devices are supplied to the subscriber by a service provider of one of the media communication systems of <figref idrefs="DRAWINGS">FIGS. 1-4</figref>, the portal <b>530</b>, acting as a subsystem of the media communication system, can automatically populate provisioning fields describing said media sources and media presentation devices by retrieving information about these devices from a subscriber database of the media communication system. In situations, where some of the media sources and/or media presentation devices are exclusively owned by the subscriber (e.g., an iPod, camera, etc.) and not managed by the service provider of the media communication system, the subscriber will have to populate provisioning fields in the portal <b>530</b> for each identified media source and/or media presentation device.

Once the media sources and media presentation devices have been identified and described, the portal <b>530</b> can inform the MDS <b>130</b> of these descriptions which in turn can prompt the MDS to request, as previously discussed in step <b>602</b>, software applications and/or plug-ins from websites that support these devices.

After the MDS <b>130</b> has identified the distribution preferences in step <b>610</b>, the MDS can identify in step <b>612</b> the media presentation devices capable of receiving the new media content detected in step <b>604</b>, and determine which of the media presentation devices are communicatively coupled to the MDS by utilizing the communication identifiers (discussed earlier) to attempt establishing communications with the media presentation devices. Once the MDS <b>130</b> identifies which of the media presentation devices is available to receive media content, the MDS proceeds to step <b>616</b> where it distributed all or portions of the media content to the media presentation devices according to the distribution preferences and the media content types determined in step <b>608</b>.

In the illustrative example previously discussed, the MDS <b>130</b> would distribute all media files to the STB, and only the MP3 and MP4 files to the automobile entertainment system as directed by the distribution preferences established by the subscriber by way of the portal <b>530</b>. The distribution of media content to the STB as previously noted can occur over a wireline interface (e.g., Ethernet) or WiFi, while the distribution to the automobile entertainment system can occur over a cellular interface.

Suppose however that the automobile is turned off at the time that the MDS <b>130</b> checked the availability of entertainment system in step <b>614</b>, and said system did not respond to the MDS's communication prompt. Under these circumstances, step <b>616</b> would apply only to the STB. To address this situation, the MDS <b>130</b> can be directed to step <b>618</b> to determine if other media presentation devices have been targeted to receive portions of the media content, but were not detected in step <b>614</b>. If all targeted media presentation devices have been found, and have successfully received the media content, then method <b>600</b> ends and is repeated for subsequently detected media sources with new media content.

If a targeted media presentation device was not available as in the present illustration, the MDS <b>130</b> proceeds to step <b>620</b> to determine if the media presentation device has subsequently become communicatively available. If a device is detected, the MDS <b>130</b> can proceed to step <b>622</b> to determine if it is one of the targeted media presentation devices of step <b>616</b>. If it is not, the MDS <b>130</b> can return to step <b>620</b> and continue the monitoring process. If in step <b>622</b> the MDS <b>130</b> determines that the media presentation device detected in step <b>620</b> is a targeted media presentation device, the MDS can proceed to step <b>624</b> to distribute media content according to the distribution preferences and media content types as previously discussed in step <b>616</b>. After step <b>624</b>, the MDS <b>130</b> can return to steps <b>620</b> and <b>618</b> to repeat the monitoring process until all targeted media presentation devices have been found. Steps <b>618</b>-<b>624</b> can operate as a background process of the MDS <b>130</b>.

Upon reviewing the aforementioned embodiments, it would be evident to an artisan with ordinary skill in the art that said embodiments can be modified, reduced, or enhanced without departing from the scope and spirit of the claims described below. For example, method <b>600</b> can be adapted so that the monitoring process of steps <b>618</b>-<b>620</b> is performed proactively. For example, the MDS <b>130</b> can be directed to submit one or more prompt messages (e.g., SMS messages) to the entertainment system of the automobile by way of for example its telemetry system to inform it that new media content is available from the MDS. Once the subscriber has turned on the automobile, the entertainment system can receive the queued SMS message from the cellular system, thereby prompting it to submit a response message (e.g., another SMS) to the MDS <b>130</b> indicating it is ready to receive the media content. At that point, the MDS <b>130</b> can proceed to step <b>624</b> to transmit the media content according to the distribution preferences and media content types detected in step <b>608</b>.

In yet another illustrative embodiment, method <b>600</b> can be adapted so that media content is categorized by the MDS <b>130</b> before its transmission to the targeted media presentation devices. Returning to the previously mentioned illustration, the cellular phone serving as a media source can include MP4 files which were generated by the subscriber using the digital camera of the cellular phone. These MP4 files can be distinguished from commercial MP4 files delivered by an Internet content source such as iTunes™. The MDS <b>130</b> can be adapted to create metadata (if the metadata is not already supplied by the cellular phone) to describe these differences, and attach the metadata to the media files before it is transmitted to the targeted media presentation devices. The metadata can also indicate the source of the media content (e.g., subscriber's cell phone). The media presentation devices in turn can use this information to categorize the received media content so the subscriber can readily distinguish the source of the media content, separate commercial content from personal recordings.

In another illustrative embodiment, method <b>600</b> can be adapted to define more complex distribution preferences. For instance, if the media content includes metadata with tags and/or description of the media content, the subscriber can define macros for distributing content between media players. For instance, the subscriber can define macros so that media content of only certain music performers is to be distributed to the automobile of the subscriber.

In yet another illustrative embodiment, method <b>600</b> can be adapted so that distribution preferences can be defined on a per user basis. In this embodiment, media content can be distributed by the MDS <b>130</b> among media devices of multiple subscribers according to the distribution preferences of each corresponding subscriber.

Other suitable modifications that can be applied to the present disclosure without departing from the scope of the claims below. Accordingly, the reader is directed to the claims section for a fuller understanding of the breadth and scope of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 8</figref> depicts an exemplary diagrammatic representation of a machine in the form of a computer system <b>800</b> within which a set of instructions, when executed, may cause the machine to perform any one or more of the methodologies discussed above. In some embodiments, the machine operates as a standalone device. In some embodiments, the machine may be connected (e.g., using a network) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client user machine in server-client user network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet PC, a laptop computer, a desktop computer, a control system, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. It will be understood that a device of the present disclosure includes broadly any electronic device that provides voice, video or data communication. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The computer system <b>800</b> may include a processor <b>802</b> (e.g., a central processing unit (CPU), a graphics processing unit (GPU, or both), a main memory <b>804</b> and a static memory <b>806</b>, which communicate with each other via a bus <b>808</b>. The computer system <b>800</b> may further include a video display unit <b>810</b> (e.g., a liquid crystal display (LCD), a flat panel, a solid state display, or a cathode ray tube (CRT)). The computer system <b>800</b> may include an input device <b>812</b> (e.g., a keyboard), a cursor control device <b>814</b> (e.g., a mouse), a disk drive unit <b>816</b>, a signal generation device <b>818</b> (e.g., a speaker or remote control) and a network interface device <b>820</b>.

The disk drive unit <b>816</b> may include a machine-readable medium <b>822</b> on which is stored one or more sets of instructions (e.g., software <b>824</b>) embodying any one or more of the methodologies or functions described herein, including those methods illustrated above. The instructions <b>824</b> may also reside, completely or at least partially, within the main memory <b>804</b>, the static memory <b>806</b>, and/or within the processor <b>802</b> during execution thereof by the computer system <b>800</b>. The main memory <b>804</b> and the processor <b>802</b> also may constitute machine-readable media.

Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations.

In accordance with various embodiments of the present disclosure, the methods described herein are intended for operation as software programs running on a computer processor. Furthermore, software implementations can include, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.

The present disclosure contemplates a machine readable medium containing instructions <b>824</b>, or that which receives and executes instructions <b>824</b> from a propagated signal so that a device connected to a network environment <b>826</b> can send or receive voice, video or data, and to communicate over the network <b>826</b> using the instructions <b>824</b>. The instructions <b>824</b> may further be transmitted or received over a network <b>826</b> via the network interface device <b>820</b>.

While the machine-readable medium <b>822</b> is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure.

The term “machine-readable medium” shall accordingly be taken to include, but not be limited to: solid-state memories such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories; magneto-optical or optical medium such as a disk or tape; and carrier wave signals such as a signal embodying computer instructions in a transmission medium; and/or a digital file attachment to e-mail or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a machine-readable medium or a distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.

Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Each of the standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same functions are considered equivalents.

The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Figures are also merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.