Patent Application
20090327241
Home networking refers to systems that allow users of computing devices, audio devices, and video devices to network the devices within their homes. The Digital Living Network Alliance (DLNA) was formed in recent years to generate standards for interaction and communication protocol usage between devices networked within a home environment.
Devices that store audio and video content within a DLNA-compliant home network are known as DLNA servers. Devices that are capable of accessing and rendering content stored on DLNA servers are known as DLNA clients. DLNA clients typically take the form of audio or video players. Users of conventional DLNA client devices access each DLNA server independently to determine what content is available on the respective DLNA server. User interfaces associated with conventional DLNA client devices provide a directory hierarchy representation of each DLNA server and the user independently accesses and traverses each directory component to determine what content is available on the respective DLNA server. Additionally, web and DLNA protocols are incompatible protocols. Accordingly, conventional web-based applications cannot access the audio and video content stored on DLNA servers within a DLNA network.
Certain illustrative embodiments illustrating organization and method of operation, together with objects and advantages may be best understood by reference detailed description that follows taken in conjunction with the accompanying drawings in which:
While this invention is susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detail specific embodiments, with the understanding that the present disclosure of such embodiments is to be considered as an example of the principles and not intended to limit the invention to the specific embodiments shown and described. In the description below, like reference numerals are used to describe the same, similar or corresponding parts in the several views of the drawings.
The terms “a” or “an”, as used herein, are defined as one or more than one. The term “plurality”, as used herein, is defined as two or more than two. The term “another”, as used herein, is defined as at least a second or more. The terms “including” and/or “having”, as used herein, are defined as comprising (i.e., open language). The term “coupled”, as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. The term “program” or “computer program” or similar terms, as used herein, is defined as a sequence of instructions designed for execution on a computer system. A “program”, or “computer program”, may include a subroutine, a function, a procedure, an object method, an object implementation, in an executable application, an applet, a servlet, a source code, an object code, a shared library/dynamic load library and/or other sequence of instructions designed for execution on a computer system having one or more processors.
Reference throughout this document to “one embodiment”, “certain embodiments”, “an embodiment” or similar terms means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of such phrases in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments without limitation.
The term “or” as used herein is to be interpreted as an inclusive or meaning any one or any combination. Therefore, “A, B or C” means “any of the following: A; B; C; A and B; A and C; B and C; A, B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or acts are in some way inherently mutually exclusive.
The present subject matter provides automated aggregation and filtering of audio and video (A/V) content information representing available A/V content located on multiple Digital Living Network Alliance (DLNA) servers within a home network environment. A DLNA client automatically aggregates the A/V content information when it enters the network, when DLNA servers enter the network, and when A/V content changes within any DLNA server on the network. The DLNA client filters the A/V content information in response to user queries for A/V content based upon A/V filter criteria, such as category, genre, title, runtime, date, or other filtering criteria. Additionally, the aggregated A/V content information may be presented as a pool of images, such as thumbnails, and categorized by alternative filtering criteria, such as movies, sports, or news, for selection by the user. As another alternative, the DLNA client automatically aggregates the A/V content by querying each DLNA server with a DLNA filtered search in response to the user query. The DLNA client presents a non-hierarchical pool of A/V identifier elements, such as thumbnail images or uniform resource identifiers (URIs), to a user. Each of the A/V identifier elements form a portion of and represent one item of filtered and aggregated A/V content information. As such, a user may select an A/V identifier element to access the associated A/V content for rendering without separately accessing or navigating a directory hierarchy for each DLNA server. Upon selection of the respective A/V identifier element, the associated URI is accessed to render the associated A/V content. The aggregated and filtered non-hierarchical pool of A/V identifier elements may be organized, categorized, and grouped in a variety of ways to facilitate increased A/V content navigational opportunities. Furthermore, a bridge component provides translation between web protocols and the DLNA protocol to allow web-based applications outside of the home network to access the aggregated A/V content information for filtering and rendering via the web-based applications.
Turning now to
For purposes of the present description, example aggregation and filtering queries generated by a user may include category, genre, title, runtime, date, or other filtering criteria. For example, a query may include a category for A/V content of movie and a genre of “western”. Additional example filtering criteria include a production date range, an actor name, a producer name, and a country of production. Many other aggregation and filtering criteria are possible and all are considered within the scope of the present subject matter.
Additionally, queries may be generated by a user of the DLNA client 102 or of a device in communication with the DLNA client 102 and the results of the queries may be presented or rendered on the respective client device. Example client devices include a personal digital assistant (PDA), mobile phone, or other mobile device (none shown). Alternatively, the results of the queries may be rendered on any other device associated with the home network 104.
At least two example modes of operation will be described for the DLNA client 102. In a first example mode of operation, the DLNA client 102 reduces filtering response time by aggregating information associated with available A/V content located on each of the DLNA server_1106 through the DLNA server_N 110 in advance of user queries for available A/V content. In this example mode of operation, the DLNA client 102 filters the previously aggregated A/V content information in response to a user query and presents the filtered A/V content information within a flat non-hierarchical representation that allows the user to more readily select A/V content for rendering without the need for engaging in the tedious process of separately accessing or navigating a separate directory hierarchy for each DLNA server.
In a second example mode of operation, the DLNA client 102 reduces local A/V content information storage resources by aggregating available A/V content in real time in response to user queries. For purposes of the present description, the term “real time” shall include what is commonly termed “near real time”—generally meaning any time frame of sufficiently short duration as to provide reasonable response time for on demand information processing acceptable to a user of the subject matter described (e.g., within a few seconds or less than ten seconds or so in certain systems). These terms, while difficult to precisely define are well understood by those skilled in the art. In this second example mode of operation, the DLNA client 102 performs specific queries of each of the DLNA server_1106 through the DLNA server_N 110 based upon a user query for available A/V content. Each of the DLNA server_1106 through the DLNA server_N 110 performs a filter operation and returns filtered A/V content information to the DLNA client 102. The DLNA client 102 presents the received filtered A/V content information within a flat non-hierarchical representation that allows the user to select the A/V content for rendering without separately accessing or navigating a directory hierarchy for each DLNA server.
Returning to the description of
It should be noted that the web-based rendering device 114 is illustrated within the
As described above and in more detail below, the display device 202 presents a non-hierarchical pool of A/V identifier elements, such as thumbnail images or URIs, to a user and allows the user to select an A/V identifier element to access the associated A/V content for rendering without separately accessing or navigating a directory hierarchy for each DLNA server. Upon selection of the respective A/V identifier element, the associated URI is accessed to render the associated A/V content.
A DLNA interface 206 encapsulates the aggregation and filtering capabilities of the present subject matter and provides communication capabilities for interaction with the DLNA server_1106 through the DLNA server_N 110 on the home network 104. The DLNA interface 206 includes a DLNA content aggregator 208 that provides the aggregation and filtering capabilities described above and in more detail below. A DLNA stack 210 provides the communication interface with the home network 104.
It should be noted that the DLNA interface 206 is illustrated with component-level modules for ease of illustration and description purposes. It is also understood that the DLNA interface 206 includes any hardware, programmed processor(s), and memory used to carry out the functions of the DLNA interface 206 as described above and in more detail below. For example, the DLNA interface 206 may include additional controller circuitry in the form of application specific integrated circuits (ASICs), processors, and/or discrete integrated circuits and components for performing electrical control activities associated with the DLNA interface 206. Additionally, the DLNA interface 206 also includes interrupt-level, stack-level, and application-level modules as appropriate. Furthermore, the DLNA interface 206 includes any memory components used for storage, execution, and data processing by these modules for performing processing activities associated with the DLNA interface 206. The DLNA interface 206 may also form a portion of other circuitry described below without departure from the scope of the present subject matter.
A memory 212 includes a DLNA user interface application 214 that organizes and displays the aggregated and filtered A/V content on the display device 202 or other display devices (not shown) as a non-hierarchical pool of A/V identifier elements, such as thumbnail images or URIs, and allows the user to select an A/V identifier element to access the associated A/V content for rendering without separately accessing or navigating a directory hierarchy for each DLNA server. Upon selection of the respective A/V identifier element, the associated URI is accessed to render the associated A/V content.
The DLNA user interface application 214 includes instructions executable by the processor 200 for performing these and other functions. The DLNA user interface application 214 may form a portion of an interrupt service routine (ISR), a portion of an operating system, or a portion of a separate application without departure from the scope of the present subject matter. Any firmware associated with a programmed processor that forms a portion of the DLNA interface 206 may be stored within, executed from, and use data storage space within the DLNA interface 206 or the memory 212 without departure from the scope of the present subject matter.
It is understood that the memory 212 may include any combination of volatile and non-volatile memory suitable for the intended purpose, distributed or localized as appropriate, and may include other memory segments not illustrated within the present example for ease of illustration purposes. For example, the memory 212 may include a code storage area, a code execution area, and a data area suitable for storage of the aggregated and filtered A/V content information and storage and execution of the DLNA user interface application 214 and any firmware associated with a programmed processor that forms a portion of the DLNA interface 206, as appropriate. It is also be understood that, though the aggregated A/V content information database 112 is illustrated as a separate component, the aggregated A/V content information may also be stored within the memory 212 as described above without departure from the scope of the present subject matter.
An HTTP-DLNA bridge interface 216 provides protocol mapping, conversion, and communication capabilities to allow the DLNA client 102 to communicate with external devices, such as the web-based rendering device 114, via the network 116. As described in more detail below beginning with
It should be noted that the HTTP-DLNA bridge interface 216 is illustrated as a component-level module for ease of illustration and description purposes. It is also understood that the HTTP-DLNA bridge interface 216 includes any hardware, programmed processor(s), and memory used to carry out the functions of the HTTP-DLNA bridge interface 216 as described above and in more detail below. For example, the HTTP-DLNA bridge interface 216 may include additional controller circuitry in the form of application specific integrated circuits (ASICs), processors, and/or discrete integrated circuits and components for performing electrical control activities associated with the HTTP-DLNA bridge interface 216. Additionally, the HTTP-DLNA bridge interface 216 also includes interrupt-level, stack-level, and application-level modules as appropriate. Furthermore, the HTTP-DLNA bridge interface 216 includes any memory components used for storage, execution, and data processing for performing processing activities associated with the HTTP-DLNA bridge interface 216. The HTTP-DLNA bridge interface 216 may also form a portion of other circuitry described below without departure from the scope of the present subject matter.
The processor 200, the display device 202, the input device 204, the DLNA interface 206, the memory 212, the aggregated A/V content information database 112, and the HTTP-DLNA bridge interface 216 are interconnected via one or more interconnections shown as interconnection 218 for ease of illustration. The interconnection 218 may include a system bus, a network, or any other interconnection capable of providing the respective components with suitable interconnection for the respective purpose.
Additionally, as described above, the web-based rendering device 114 may be located within the home network 104 or may form a portion of the DLNA client 102 without departure from the scope of the present subject matter. As such, for implementations where the web-based rendering device 114 forms a portion of the DLNA client 102, a reserved Internet protocol (IP) address of “127.0.0.1” may be used for internal communications between the web-based rendering device 114 and other components within the DLNA client 102, such as the processor 200.
Furthermore, components within the DLNA client 102 may be co-located or distributed within a network without departure from the scope of the present subject matter. For example, the components within the DLNA client 102 may be located within a stand-alone device, such as a personal computer (e.g., desktop or laptop) or handheld device (e.g., cellular telephone, personal digital assistant (PDA), email device, music recording or playback device, etc.). For a distributed arrangement, the display device 202 and the input device 204 may be located at a kiosk, while the processor 200 and memory 212 may be located at a local or remote server. Many other possible arrangements for the components of the DLNA client 102 are possible and all are considered within the scope of the present subject matter.
Upon receipt of a request to query one or more DLNA servers at decision point 404, the process 400 makes a determination at decision point 406 as to whether at least one filter criterion is associated with the query request. A filter criterion may include a criterion such as content type, genre, title, runtime, date of production, or other type of filtering criterion that may be used to filter and categorize available A/V content within the home network 104. When a determination is made that the query request does not include at least one filter criterion, the process 400 sends a DLNA search message to one or more DLNA servers, such as the DLNA server_1106 through the DLNA server_N 110, within the home network 104 at block 408.
DLNA search messages may include information such as container identifiers, search criteria, filter criteria, starting index, requested return item count, and sort criteria. A response message received from a DLNA server may include the number of entries returned, a list of A/V content information entries, and a total number of entries that matched the requested search criteria. The total number of entries that matched the requested search criteria may be used to determine whether to request additional A/V content information from a respective DLNA server as a user browses the aggregated A/V content information.
An example DLNA search message that requests A/V content information for video items stored at a given DLNA server is illustrated below. The DLNA search message below requests the return of A/V content information for one hundred (100) video items beginning at index zero (0) on the DLNA server sorted in ascending order based upon title.
Search(“0”, “upnp:class=object.item.videoItem”, “*”, 0, 100, “+dc:title”)
As can be seen from the example DLNA search message above, control of the search results returned by a given DLNA server may be managed from the DLNA client 102. Furthermore, as a user completes review of the returned A/V content information, a next group of A/V content information may be requested, such as A/V content information for the next one hundred (100) video items stored beginning at index one hundred and one (101) (e.g., video items indexed from 101 through 200). By reducing the amount of A/V content information requested, storage capacity may be reduced at the DLNA client 102. Additionally, search bandwidth requirements may be reduced by distributing A/V content searches over time.
Returning to the example of
As can be seen from this example DLNA filtered search message, filtering of the search results returned by a given DLNA server may be managed from the DLNA client 102. Furthermore, by requesting filtering of the A/V content information returned by the given DLNA servers, storage capacity may be further reduced at the DLNA client 102 and search bandwidth requirements may also be reduced. However, it should be understood that filtering may be performed at the DLNA client 102 without departure from the scope of the present subject matter.
As described above, there may be occasions for sending a single DLNA search message to a single DLNA server and there may also be occasions for sending a DLNA search message to each active DLNA server within the home network. For example, when a newly activated DLNA server enters the home network 104, the process 400 may receive a query request to query the newly activated DLNA server. Alternatively, an internal startup, scheduled, or other operation or event associated with the DLNA client 102 may result in a search of all active DLNA servers within the home network 104.
In either situation, the process 400 waits at decision point 412 for all responses to be received. It should be noted that time out procedures and other error control procedures are not illustrated within the example process 400 for ease of illustration purposes. However, it is understood that all such procedures are considered to be within the scope of the present subject matter for the example process 400 or any other process described below.
Within the present example, the responses received include A/V content information in the form of the URIs described above that form hyperlinks to the storage location of the referenced A/V content. Additionally, the A/V content information may include thumbnail images and other information, such as a category, genre, title, runtime, date, and server identifier without departure from the scope of the present subject matter.
Continuing with the present example, when the URIs are received, the URIs may be used to retrieve thumbnail images and other A/V content information. Accordingly, when a determination is made at decision point 412 that all anticipated responses have been received, the process 400 may request any additional information, such as thumbnail images, using the received URIs at block 414. When additional information is requested, the process 400 waits at decision point 416 for the requested A/V content information to be received.
When a determination is made at decision point 416 that the requested A/V content information has been received, the process 400 aggregates and stores the received A/V content information at block 418. It should be noted that while the present example illustrates receipt of both URIs and separate processing to retrieve additional A/V content information prior to aggregating the received information, the aggregation and storage at block 418 may be performed on the received URIs with or without receipt of additional A/V content information without departure from the scope of the present subject matter. When additional A/V content information is received after aggregation of the URIs, any received A/V content information may then be aggregated with the previously aggregated URIs.
Accordingly, the A/V content information may be aggregated based upon any one or more of the available information elements within the A/V content information. For example, the aggregation performed by the process 400 may include collecting images or links, such as thumbnail images or URIs, respectively, that form a portion of the A/V content information for each item returned. The collected thumbnail images or URIs may be organized into arrays or other data structures and stored within the aggregated A/V content information database 112 for representation and presentation to a user of the DLNA client 102. Furthermore, information such as the category, genre, title, runtime, and date may be used for sorting and categorizing purposes, and the sorted or categorized associations may be stored within the aggregated A/V content information database 112 and presented to the user.
The process 400 presents the aggregated A/V content information based upon any requested filter criteria to a user at block 420. The aggregated A/V content information may be presented on any display device, such as the display device 202. The process 400 returns to decision point 404 to await a new query request. Accordingly, the process 400 provides filtering and aggregation of A/V content information, while also reducing memory storage requirements for the filtered and aggregated A/V content information and reducing communication bandwidth.
As described above, the aggregated A/V content information database 112 may be built for purposes of locally storing A/V content information for all content available within the home network 104 to provide more rapid responses to A/V content query requests from a user for renderable A/V content. Accordingly, the aggregated A/V content information database 112 may be built during an internal startup operation for an A/V content information aggregation and filtering device, such as the DLNA client 102. Alternatively, the aggregated A/V content information database 112 may be built or updated based upon a scheduled operation or in response to other events, such as a user request to rebuild the aggregated A/V content information database 112. As such, the aggregated A/V content information database 112 may be created or rebuilt at any point during operation of the DLNA client 102. Accordingly, any such criteria may be used in association with decision point 504 to make a determination to build the aggregated A/V content information database 112.
To further facilitate higher level understanding of the process 500, a description of events associated within building the aggregated A/V content information database 112 and other lower level processing will be described further below after a description of higher level decision points within the process 500. Accordingly, when a determination is made that the aggregated A/V content information database 112 is not to be built, the process 500 makes a determination as to whether a user has requested an A/V content query at decision point 506.
When a determination is made that the user has not requested an A/V content query, the process 500 makes a determination as to whether an A/V content change has occurred within the home network 104 at decision point 508. When a determination is made that no change to any A/V content within the home network 104 has occurred, the process 500 makes a determination as to whether a server has entered the home network 104 at decision point 510. When a determination is made that there has not been a DLNA server entry into the home network 104, the process 500 makes a determination as to whether a DLNA server has exited the home network 104 at decision point 512. When a determination is made that there has not been a DLNA server exit from the home network 104, the process 500 returns to decision point 504 to make a determination as to whether to build or rebuild the aggregated A/V content information database 112. The process 500 iteratively processes the decisions associated with decision points 504 through 512 as described above until any of these decision points results in a positive determination.
It should be noted that content changes, DLNA server entries, and DLNA sever exits may be reported by DLNA servers, such as the DLNA server_1106 through the DLNA server_N 110, via DLNA messaging (not shown) similar to that described above. Additionally, subscription services that form a portion of the DLNA protocol may be used to cause update messages for content changes to be generated and sent from DLNA servers. Accordingly, it is assumed that appropriate DLNA messaging occurs between the DLNA client 102 and any of the DLNA server_1106 through the DLNA server_N 110 to trigger events that result in the associated determinations described above.
Returning to the description of decision point 504, when a determination is made to build or rebuild the aggregated A/V content information database 112, the process 500 queries all active DLNA servers for A/V content information at block 514. The process 500 waits at decision point 516 for a response from a first of the queried DLNA servers to be received. When the first response is received, the process 500 stores the received A/V content information, such as within the aggregated A/V content information database 112, at block 518. At decision point 520, the process 500 waits for an additional response to be received. When an additional response is received, the process 500 aggregates the received A/V content information with previously received A/V content information and stores the aggregated A/V content information to the aggregated A/V content information database 112 at block 522.
As described above, the A/V content information received may include thumbnail images, URIs forming hyperlinks to the storage location of the referenced A/V content, and other information, such as a category, genre, title, runtime, date, and server identifier. Accordingly, the A/V content information may be aggregated based upon any one or more of the available information elements within the A/V content information. For example, the aggregation performed by the process 500 may include collecting images or links, such as thumbnail images or URIs, respectively, that form a portion of the A/V content information for each item returned. The collected thumbnail images or URIs may be organized into arrays or other data structures and stored within the aggregated A/V content information database 112 for representation and presentation to a user of the DLNA client 102. Furthermore, information such as the category, genre, title, runtime, and date may be used for sorting and categorizing purposes, and the sorted or categorized associations may be stored within the aggregated A/V content information database 112 and presented to the user.
At decision point 524, the process 500 makes a determination as to whether all anticipated responses have been received. If a determination is made that not all anticipated responses have been received, the process 500 returns to decision point 520 to await another response. When a determination is made that all anticipated responses have been received or a timeout or other terminating event occurs, the process 500 returns to decision point 504 to continue with the higher level processing described above.
Returning to the description of decision point 506, when a determination is made that the user has requested an A/V content query, the process 500 continues processing as described in association with
When an A/V content filter has been requested as a portion of the user A/V content query, a determination is made at decision point 528 as to whether there is a local match within the aggregated A/V content information database 112 based upon the A/V content filter. When a determination is made that there is no local match for the requested A/V content filter, the process 500 queries all active DLNA servers, such as the DLNA server_1106 through the DLNA server_N 110, for pre-filtered A/V content information at block 530. These queries may be issued using DLNA messaging similar to that described above.
At decision point 532, the process 500 waits for a first response to be received from a one of the queried DLNA servers. When the first response is received, the process 500 stores the received pre-filtered A/V content information, such as within the aggregated A/V content information database 112, at block 534. At decision point 536, the process 500 waits for an additional response to be received. When an additional response is received, the process 500 aggregates the received pre-filtered A/V content information with previously received pre-filtered A/V content information and stores the aggregated pre-filtered A/V content information to the aggregated A/V content information database 112 at block 538. The aggregated pre-filtered A/V content information may be stored within a separate table from other A/V content information or may be otherwise identified within the aggregated A/V content information database 112 as appropriate.
At decision point 540, the process 500 makes a determination as to whether all anticipated responses have been received. If a determination is made that not all anticipated responses have been received, the process 500 returns to decision point 536 to await another response. When a determination is made that all anticipated responses have been received at decision point 540 (or a timeout or other terminating event has occurred) or that there is a local match within the aggregated A/V content information database 112 based upon the A/V content filter at decision point 528, the process 500 presents the filtered aggregated A/V content information to the user, such as via the display device 202, at block 542 and returns to decision point 504 (See
Returning to the description of decision point 526, when a determination is made that an A/V content filter has not been requested as a portion of the user A/V content query, the process 500 makes a determination at decision point 544 as to whether local A/V content information is available within the aggregated A/V content information database 112 for response to the request. The local A/V content information includes any A/V content information that was previously retrieved during a build operation of the aggregated A/V content information database 112 as described above. When a determination is made that local A/V content information is not available, the process 500 continues as described above beginning with block 514 (See
Returning again to
At block 548, the process 500 queries the DLNA server reporting changed content for updated A/V content information or the new DLNA server for A/V content information. The process 500 waits at decision point 550 for a response to be received. When a response is received, the process 500 aggregates and stores the received A/V content information with the other A/V content information stored within the aggregated A/V content information database 112 at block 552 and the process 500 returns to decision point 504 (See
Returning again to
As such, the process 500 provides for building and rebuilding of the aggregated A/V content information database 112, for filtering A/V content information stored within the aggregated A/V content information database 112, for pre-filtering queries to the DLNA server_1106 through the DLNA server_N 110. The process 500 also responds to A/V content changes within the home network 104, new DLNA server entry into the home network 104, and DLNA server exits from the home network 104.
When a request to aggregate A/V content information is received, the process 700 aggregates A/V content information received from multiple active DLNA servers at block 706. For ease of illustration purposes, intervening steps for querying active DLNA servers and related activities, such as those described above in association with other examples, are not illustrated within
At block 708, the process 700 formats the aggregated A/V content information into a non-hierarchical pool of A/V identifier elements that each represent one item of the aggregated A/V content information and stores the aggregated A/V content information and the resulting non-hierarchical pool of A/V identifier elements to a memory, such as the memory 212. For example, each item of aggregated A/V content information may be referenced by reference to a thumbnail image or URI associated with each item of formatted A/V content information. Accordingly, the non-hierarchical pool of A/V identifier elements may include the thumbnail images and URIs associated with each of item of aggregated A/V content. As such, the process 700 may organize each item of the non-hierarchical pool of A/V identifier elements into a list or other form of organizational structure. The resulting organization may be stored within the memory 212 for access, filtering, and other operations as described above and in more detail below.
At block 710, the process 700 determines a size of a viewable area of the display device 202. At block 712, the process 700 determines sizes of all associated thumbnail images. For purposes of the present description, a thumbnail image may be a still image received from a DLNA server, such as the DLNA server_1106 through the DLNA server_N 110, that represents the A/V content stored on the respective DLNA server. Accordingly, if any of the thumbnail images vary in size, the process 700 may determine the size variations of the respective thumbnail images.
At decision point 714, the process 700 makes a determination as to whether to scale any of the thumbnail images for consistency of size and identifies which of the thumbnail images to scale. If a determination is made to scale any of the thumbnail images, the process 700 scales the identified thumbnail images at block 716. When the scaling of the thumbnail images is completed or upon a determination at decision point 714 that no scaling is to be performed, the process 700 calculates and determines a number of thumbnail images that may be displayed at block 718.
At decision point 720, the process 700 makes a determination as to whether to sort any elements within of the non-hierarchical pool of A/V identifier elements. Sorting may be performed based upon the aggregated A/V content information, such as content type or genre, associated with the respective elements. When a determination is made to sort elements associated with the non-hierarchical pool of A/V identifier elements, the process 700 sorts the elements into groups based upon the selected sort criteria or criterion at block 722. At block 724, the process 700 displays thumbnails, associated with any group(s) created on the display device 202. When a determination is made not to sort any elements within the non-hierarchical pool of A/V identifier elements at decision point 720 or when the thumbnails associated with any group(s) created has been displayed, the process 700 presents the calculated number of thumbnail images to a user on the display device 202 at block 726 and continues with processing as described below in association with
Referring to
When a determination is made at decision point 730 that a focus event has occurred, the process 700 displays A/V content information associated with the focused thumbnail image at block 738. The displayed A/V content information may include a title, runtime, or other information associated with the thumbnail image. The A/V content information may be displayed within a status area of the display device 202 or in any other suitable manner without departure from the scope of the present subject matter. After the A/V content information associated with the focused thumbnail image has been displayed, the process returns to decision point 730 and iterates as described above.
Returning to the description of decision point 732, when a determination is made that a select event has occurred, the process 700 accesses and renders A/V content associated with the selected thumbnail image at block 740 using the URI associated with the thumbnail image gathered during and forming a portion of the non-hierarchical pool of A/V identifier elements. At decision point 742, the process 700 makes a determination as to whether the rendering of the A/V content has completed or whether there has been another menu request. In response to a determination that rendering of the A/V content has completed or that a menu request has been received, the process 700 returns to decision point 730 and iterates as described above.
Returning to the description of decision point 734, when a determination is made that a filter request has been received, the process 700 filters the non-hierarchical pool of A/V identifier elements and displays the thumbnail images associated with the filtered non-hierarchical pool of A/V identifier elements to the user at block 744. The process 700 returns to decision point 730 and iterates as described above.
Returning to the description of decision point 736, when a determination is made that a grouping event has occurred, the process 700 re-groups the non-hierarchical pool of A/V identifier elements and displays the thumbnail images associated with the re-grouped non-hierarchical pool of A/V identifier elements to the user at block 746. This re-grouping may be based upon a request from a user or an internal event indicating that re-grouping should be performed. For example, a user request to re-group A/V content information may be based upon a requested change of category associated with the aggregated A/V content, alphabetization of title, date re-grouping, or any other type of re-grouping. Additionally, an internal event for re-grouping may be generated in response to a DLNA server, such as the DLNA server_1106 through the DLNA server_N 110, entering or exiting the home network 104. For ease of illustration purposes, intervening steps for querying active DLNA servers and related activities, such as those described above in association with other examples, are not illustrated within
It should be understood that many variations on the process 700 and the other processes described in association with the present subject matter are possible. For example, within the process 700, a filter request may be combined with a grouping request without departure from the present subject matter. In such a case, appropriate actions similar to those described above for each action may be performed in response to receipt of the combined request. Accordingly, variations on the process 700 or variations on any other processes described herein are considered within the scope of the present subject matter.
As such, thumbnail images that form a portion of the aggregated and formatted A/V content information as represented by the non-hierarchical pool of A/V identifier elements are grouped into separate rows within this example for display on the display device 202. It should be understood that many other possible arrangements of the aggregated and formatted A/V content information are possible. For example, groups of thumbnail images may be presented in columns rather than in rows. Alternatively, groups of thumbnail images may be presented as a three-dimensional grouping that may then be selected and expanded for browsing without departure from the scope of the present subject matter. Accordingly, all such alternatives are considered to be within the scope of the present subject matter.
Based upon the example user interface illustrated within
The aggregated and formatted A/V content information may include additional information, such as a category, a genre, a title, a runtime, a date or other information associated with the represented A/V content. As described above, this information may be used to filter the aggregated A/V content information. Additionally, to facilitate access to this additional information for A/V content selection for rendering, the example user interface of
As can be seen from
Regarding selection of A/V content for rendering and viewing, as described above, the aggregated and formatted A/V content information may include a URI that forms a link to the respective A/V content represented by the respective thumbnail images 802-810, 814-822, and 826-834. The respective URI may be used to access the individual A/V content elements on the respective DLNA server_1106 through DLNA server_N 110. Within the example user interface, the respective URI is associated with each of the thumbnail images 802-810, 814-822, and 826-834 so that when a user selects the respective thumbnail image, the link formed by the URI is activated to access the associated A/V content for rendering. The selected A/V content may then be rendered on the DLNA client 102 or another device chosen by the user.
A navigation field 848 provides the user of the DLNA client 102 with additional navigation options to retrieve or view more video selections. Additionally, a navigation field 850 provides the user of the DLNA client 102 with instructions for returning to an additional menuing structure (not shown) for additional navigation capabilities, such as selecting a device other than the DLNA client 102 for rendering of selected A/V content. Many other navigation fields are possible, such as fields for switching between video and audio content, and all are considered within the scope of the present subject matter.
Additionally, when more aggregated A/V content information in the form of thumbnail images or URIs within the non-hierarchical pool of A/V identifier elements is available for presentation to the user than the viewable area of the display device 202 may accommodate, a portion of the non-hierarchical pool of A/V identifier elements may be presented initially. In such a situation, scrolling, paging, or other navigational activities may be employed to traverse the remaining elements of the non-hierarchical pool of A/V identifier elements without departure from the scope of the present subject matter.
Accordingly, the present subject matter provides automated aggregation and filtering of A/V content information representing available A/V content located on multiple DLNA servers within a the home network 104. The DLNA client 102 automatically aggregates the A/V content information when it enters the network, when DLNA servers enter the network, and when A/V content changes within any DLNA server on the network. The DLNA client 102 filters the A/V content information in response to user queries for A/V content based upon A/V filter criteria, such as category, genre, title, runtime, date or other filtering criteria. The DLNA client presents a non-hierarchical pool of A/V identifier elements, such as thumbnail images or uniform resource identifiers (URIs), to a user. Each of the A/V identifier elements form a portion of and represent one item of filtered and aggregated A/V content information. As such, a user may select an A/V identifier element to access the associated A/V content for rendering without separately accessing or navigating a directory hierarchy for each DLNA server. Upon selection of the respective A/V identifier element, the associated URI is accessed to render the associated A/V content. The aggregated and filtered non-hierarchical pool of A/V identifier elements may be organized, categorized, and grouped in a variety of ways to facilitate increased A/V content navigational opportunities.
It should be understood that the present subject matter as described above is not limited to aggregation and filtering of A/V content information for access by nodes within a home network, such as the DLNA client 102 within the home network 104. The present subject matter applies as well to aggregation and filtering of A/V content information for access by web-based devices located either outside of the home network 104, such as the web-based rendering device 114, or that are incorporated into the DLNA client 102. Devices such as the web-based rendering device 114 may access the aggregation and filtering capabilities of the DLNA client 102 via a connection to the network 116. An example of a web-based protocol suitable for providing the described access is the transmission control protocol over Internet protocol (TCP/IP). Hypertext transfer protocol (HTTP) and extensible markup language (XML) formatting may be used for messaging over the TCP/IP connection to the network 116. Other web protocols exist and all are considered within the scope of the present subject matter.
For purposes of the present description, it is assumed that the DLNA client 102 maintains a list of active DLNA servers and that this list is updated either periodically or as DLNA servers enter and leave the home network 104. Accordingly, the DLNA client 102 may issue queries to any active DLNA server in response to receipt of a web protocol request for aggregated and/or filtered A/V content information stored within the home network 104.
An example web protocol request for filtered A/V content information associated with A/V content stored within the home network 104 is illustrated below. While many potential formats may be used, the example filtered web protocol request below represents an example of an HTTP-formatted request message that requests the return of A/V content information for fifty (50) video items beginning at index offset zero (0) sorted in ascending order based upon title. It should be noted that the offset may be adjusted during subsequent web protocol requests to allow a user at the requesting node to page through the returned results using sequential web protocol requests. The example web protocol request is identified as a “GetContentList” message and requests filtering of available A/V content information associated with a type of “video,” a category of “movie,” a genre of “western,” and a rating of “PG-13.”
As can be seen from the example filtered web protocol request above, web-based devices, such as the web-based rendering device 114, located outside of the home network 104 may utilize a web protocol message format, such as HTTP, to request A/V content information for A/V content located within the home network 104. An IP address of “192.168.22.11” is used within the HTTP message to address the DLNA client 102. However, as described above, for implementations where the web-based rendering device 114 forms a portion of the DLNA client 102, a reserved IP address of “127.0.0.1” or other reserved IP address may be used for internal communications between the web-based rendering device 114 and other components within the DLNA client 102, such as the processor 200.
Furthermore, as described above, as a user completes review of the returned A/V content information, a next group of A/V content information may be requested, such as A/V content information for the next fifty (50) video items stored beginning at index fifty one (51) (e.g., video items indexed from 51 through 100), to allow the user to page through the aggregated and/or filtered A/V content information. By reducing the amount of A/V content information requested, storage capacity may be reduced at the DLNA client 102. Additionally, search bandwidth requirements may be reduced by distributing A/V content searches over time.
Returning to the example of
When a determination is made that the query request does include at least one filter criterion, at block 1010 the process 1000 converts the web protocol request to a DLNA filtered search message having a format similar to that described above in association with
In either situation, the process 1000 waits at decision point 1014 for all responses to be received. It should be noted that time out procedures and other error control procedures are not illustrated within the example process 1000 for ease of illustration purposes. However, it is understood that all such procedures are considered to be within the scope of the present subject matter for the example process 1000 or any other process described herein.
Within the present example, the responses received include A/V content information in the form of the URIs described above that form hyperlinks to the storage location of the referenced A/V content. Additionally, the A/V content information may include thumbnail images and other information, such as a category, genre, title, runtime, date, and server identifier without departure from the scope of the present subject matter.
Continuing with the present example, when the URIs are received, the URIs may be used to retrieve thumbnail images and other A/V content information. Accordingly, when a determination is made at decision point 1014 that all anticipated responses have been received, the process 1000 aggregates and stores the received A/V content information at block 1016. It should be noted that while the present example illustrates receipt of URIs without separate processing to retrieve additional A/V content information prior to aggregating the received information, the aggregation and storage at block 1016 may be performed on the received URIs with or without receipt of additional A/V content information without departure from the scope of the present subject matter. Furthermore, when additional A/V content information is received after aggregation of the URIs, any received A/V content information may then be aggregated with the previously aggregated URIs.
The process 1000 formats the aggregated and/or filtered A/V content information into a web protocol response to the received web protocol request at block 1018. The web protocol response may be in the form of a markup language (ML) response. For example, the following pseudo XML-formatted response message may be used to formulate a web protocol response suitable for communicating the aggregated and/or filtered A/V content information to a requesting web-based device, such as the web-based rendering device 114, located outside of the home network 104.
As can be seen from this example XML-formatted response message, an XML-formatted tag pair “response” and “/response” outline the response message content. A “header” tag pair identifies this example XML-formatted response message as a response to a “GetContentList” message previously received and described above. A “code” tag pair identifies an error code for the example XML-formatted response message. In the present example, an error code of zero (0) is shown. This zero error code may be used to indicate that there was no error with the previous request. An example of such a no-error condition occurs when the request size is less than or equal to the number of available A/V content items within the home network 104, as described in more detail below in association with the “num_items” tag pair. An example error condition may be indicated with any value other than the chosen no-error condition identifier, such as one hundred (100). Such an error condition may be indicated when the requested offset is greater than the available A/V content items within the home network 104. It is understood that any value may be used to indicate an error condition or a non-error condition without departure from the scope of the present subject matter.
A “list_header” tag pair includes two additional tag pairs, “type” and “num_items.” The “type” tag pair may indicate the type of A/V content listed within the XML-formatted response message. Example identifiers usable within the “type” tag pair are video, music, etc. Within the present example, video A/V content information is being returned. The number of available A/V content items that match the search criteria within the home network 104 may be communicated via the tag pair “num_items.” Within the present example two hundred (200) video items are available. As such, based upon the web protocol request described above with a requested size of fifty, two hundred items are available and a no-error condition zero is returned within the XML-formatted response message. For circumstances where fewer than the requested number of items are available, the “num_items” field may be used to indicate that fewer items are available than requested and that the number of available items has been returned. Such a situation may be considered a non-error situation and an error code of zero may be returned.
A “content list” tag pair delimits the payload for the XML-formatted response message. “Item” tag pairs identify each item of A/V content information and include an item index for reference. The present example only shows the first and last item in a list of fifty returned items indexed from zero (0) to forty nine (49) for ease of illustration purposes. However, it is understood that an actual message would include all of the returned items. Each item within the list includes tag pairs for identifying the title, description, icon identifier (e.g., a URI to the thumbnail image), source identifier (e.g., URI to actual content), a type (e.g., video, music, etc.), a rating, and a duration. Within the present example, a rating of “PG-13” is illustrated for each returned item in response to the web protocol request for PG-13 content described above.
Returning to the description of
Accordingly, the process 1000 provides filtering and aggregation of A/V content information in response to web protocol requests and returns search results in a web protocol format to a web-based device located outside of the home network 104, while also reducing memory storage requirements for the filtered and aggregated A/V content information and reducing communication bandwidth.
When a determination is made at decision point 1104 that a web protocol request has not been received, the process 1100 makes a determination at decision point 1106 as to whether a web protocol identifier request has been received. A web protocol identifier request may include an HTTP GET CONTENT command to allow the process 1100 to act as a proxy for the requesting device. An example HTTP GET CONTENT message is shown below.
As can be seen from this example of an HTTP GET CONTENT message, “192.168.11.22” is the IP address of the DLNA client 102 and the URI of the first returned item in the XML-formatted response message example above is being requested (e.g., the item with item id=“0”). Accordingly, the process 1100 may identify HTTP GET CONTENT messages or other message types of web protocol identifier requests that are received. Many types of web protocol identifier requests are possible and all are considered within the scope of the present subject matter.
Returning to the description of
When all anticipated responses have been received, the process 1100 aggregates and stores the received A/V content information at block 1116. This aggregated A/V content information may be used to form or begin formation of a local A/V content database, depending upon whether all available A/V content information has been requested from all DLNA servers or whether only a portion has been requested, respectively.
When the aggregated A/V content information has been stored at block 1116 or when a determination is made at decision point 1108 that a local aggregated A/V content database has already been built, the process 1100 formats the aggregated A/V content information into a web protocol response, such as the XML-formatted response message described above, at block 1118 as described above. At block 1120, the process 1100 sends the web protocol response to the requesting web-based device and returns to decision point 1104 and iterates as described above.
Returning to the description of decision point 1106, when a determination is made that a web protocol identifier request has been received, processing continues as illustrated within
As with the incoming web protocol identifier request, HTTP formatting may be used to retrieve the requested A/V content or thumbnail image from the respective DLNA server. An example HTTP GET message that may be generated by the DLNA client 102 including the URI for a thumbnail image or A/V content is shown below.
As can be seen from this example of an HTTP GET message, “10.22.1.182” is the IP address of the respective DLNA servers and is the same IP address identified in the first returned item in the XML-formatted response message example above is being requested (e.g., the item with item id=“0”). Accordingly, the process 1100 may convert incoming web protocol identifier requests to requests for content and forward those requests to storage devices within the home network 104.
The process 1100 waits at decision point 1124 for the response from the respective DLNA server. When then response is received, the process 1100 formats the A/V content or thumbnail image to a web protocol response at block 1126. The web protocol response may be similar to the example described above in association with
Accordingly, the process 1100 provides aggregation of A/V content information in response to web protocol requests and returns search results in a web protocol format to the requesting web-based device. The process 1100 also responds to web protocol requests including URIs associated with specific A/V content or thumbnail images and returns the requested items to the requesting web-based device using a web protocol response format. As described above, the example process 1100 does not detail filtering operations for ease of illustration purposes. However, filtering may be implemented as described above without departure from the scope of the present subject matter.
It should be understood that when the web-based rendering device 114 is incorporated into and/or a part of the DLNA client 102, the web-based rendering device 114 may utilize the returned content list to select an item of A/V content or a thumbnail image for rendering. In such a situation, the web-based rendering device 114 may send a web protocol identifier request directly to the respective DLNA server, such as the DLNA server_1106 through the DLNA server_N 110, for the selected item of A/V content or the associated thumbnail image using the respective URI.
Accordingly, the present subject matter provides automated aggregation and filtering of A/V content information representing available A/V content located on multiple DLNA servers within a the home network 104. The DLNA client 102 automatically aggregates the A/V content information when it enters the network, when DLNA servers enter the network, and when A/V content changes within any DLNA server on the network. The DLNA client 102 filters the A/V content information in response to user queries for A/V content based upon A/V filter criteria, such as category, genre, title, runtime, date or other filtering criteria. The DLNA client presents a non-hierarchical pool of A/V identifier elements, such as thumbnail images or uniform resource identifiers (URIs), to a user. Each of the A/V identifier elements form a portion of and represent one item of filtered and aggregated A/V content information. As such, a user may select an A/V identifier element to access the associated A/V content for rendering without separately accessing or navigating a directory hierarchy for each DLNA server. Upon selection of the respective A/V identifier element, the associated URI is accessed to render the associated A/V content. The aggregated and filtered non-hierarchical pool of A/V identifier elements may be organized, categorized, and grouped in a variety of ways to facilitate increased A/V content navigational opportunities. Furthermore, a bridge component provides translation between web protocols and the DLNA protocol to allow web-based applications outside of the home network to access the aggregated A/V content information for filtering and rendering via the web-based applications.
So, in accord with the above description, one or more active DLNA servers are queried for A/V content information associated with A/V content stored at each of the one or more active DLNA servers. Associated A/V content information is received from each of the one or more active DLNA servers.
Thus, in accord with certain implementations, a method of Digital Living Network Alliance (DLNA) audio and video (A/V) content aggregation within a DLNA home network involves querying a plurality of active DLNA servers for A/V content information associated with A/V content stored at each of the plurality of active DLNA servers; receiving the associated A/V content information from each of the plurality of active DLNA servers; aggregating the received A/V content information; and filtering the received A/V content information.
In certain implementations, querying the plurality of active DLNA servers further comprises sending a DLNA search message to each of the plurality of active DLNA servers. In certain implementations, the process further involves receiving a user request for renderable A/V content within the home network, where the user request comprises at least one A/V filter criterion. In certain implementations, filtering the received A/V content information further involves filtering the received A/V content information based upon the at least one A/V filter criterion. In certain implementations, the at least one A/V filter criterion further has at least one of a content type, a genre, and a date of production, and where filtering the received A/V content information based upon the at least one A/V filter criterion further categorizes the aggregated A/V content based upon the at least one of the content type, the genre, and the date of production. In certain implementations, querying the plurality of active DLNA servers further involves sending a DLNA filtered search message including the at least one A/V filter criterion to each of the plurality of active DLNA servers. In certain implementations, receiving the associated A/V content information from each of the plurality of active DLNA servers further involves receiving A/V search results in response to the DLNA filtered search message from each of the plurality of active DLNA servers and aggregating the received A/V content information further involves aggregating the received A/V search results.
In certain implementations, the method further involves querying at least one of the plurality of active DLNA servers for updated A/V content information in response to an indication of changed A/V content associated with the at least one of the plurality of active DLNA servers; receiving the updated A/V content information from the at least one of the plurality of active DLNA servers; and aggregating the updated A/V content information with the A/V content information received from active DLNA servers other than the at least one of the plurality of active DLNA servers.
In certain implementations, the method further involves querying an activated DLNA server for A/V content information associated with the activated DLNA server in response to the activated DLNA server entering the home network; receiving the A/V content information associated with the activated DLNA server; and aggregating the A/V content information associated with the activated DLNA server with the A/V content information received from the plurality of active DLNA servers. In certain implementations, querying the plurality of active DLNA servers further involves querying the plurality of active DLNA servers from a DLNA client device.
A Digital Living Network Alliance (DLNA) audio and video (A/V) content aggregation device consistent with certain implementations has a memory adapted to store representations of A/V content distributed within a home network environment. A processor is programmed to query a plurality of active DLNA servers for A/V content information associated with A/V content stored at each of the plurality of active DLNA servers; receive the associated A/V content information from each of the plurality of active DLNA servers; aggregate the received A/V content information; filter the received A/V content information; and store the aggregated A/V content information to the memory.
In certain implementations, the processor is further programmed to send a DLNA search message to each of the plurality of active DLNA servers. In certain implementations, an input device is adapted to provide input requests from a user to the processor and the processor is further programmed to receive a user request via the input device for renderable A/V content within the home network and the user request involves at least one A/V filter criterion. In certain implementations, the processor is further programmed to filter the received A/V content information based upon the at least one A/V filter criterion. In certain implementations, the at least one A/V filter criterion further has at least one of a content type, a genre, and a date of production, and the processor is further adapted to categorize the aggregated A/V content based upon the at least one of the content type, the genre, and the date of production. In certain implementations, in being programmed to filter the received A/V content information, the processor is further programmed to send a DLNA filtered search message including the at least one A/V filter criterion to each of the plurality of active DLNA servers. In certain implementations, the processor is further programmed to receive A/V search results in response to the DLNA filtered search message from each of the plurality of active DLNA servers and to aggregate the received A/V search results.
In certain implementations, the processor is further programmed to query at least one of the plurality of active DLNA servers for updated A/V content information in response to an indication of changed A/V content associated with the at least one of the plurality of active DLNA servers; receive the updated A/V content information from the at least one of the plurality of active DLNA servers; and aggregate the updated A/V content information with the A/V content information received from active DLNA servers other than the at least one of the plurality of active DLNA servers.
In certain implementations, the processor is further programmed to query an activated DLNA server for A/V content information associated with the activated DLNA server in response to the activated DLNA server entering the home network; receive the A/V content information associated with the activated DLNA server; and aggregate the A/V content information associated with the activated DLNA server with the A/V content information received from the plurality of active DLNA servers. In certain implementations, the processor comprises a portion of a DLNA client device.
A Digital Living Network Alliance (DLNA) audio and video (A/V) content aggregation device consistent with certain implementations has a memory adapted to store representations of A/V content distributed within a home network environment. An input device is adapted to provide input requests from a user. A processor is programmed to receive a user request via the input device for renderable A/V content within the home network, where the user request comprises at least one A/V filter criterion including at least one of a content type, a genre, and a date of production; send a DLNA filtered search message including the at least one A/V filter criterion to each of the plurality of active DLNA servers to query the plurality of active DLNA servers for pre-filtered A/V content information associated with A/V content stored at each of the plurality of active DLNA servers; receive the associated pre-filtered A/V content information from each of the plurality of active DLNA servers; aggregate the received pre-filtered A/V content information; categorize the aggregated A/V content based upon the at least one of the content type, the genre, and the date of production; and store the aggregated A/V content information to the memory.
While certain embodiments herein were described in conjunction with specific circuitry that carries out the functions described, other embodiments are contemplated in which the circuit functions are carried out using equivalent executed on one or more programmed processors. General purpose computers, microprocessor based computers, micro-controllers, optical computers, analog computers, dedicated processors, application specific circuits and/or dedicated hard wired logic and analog circuitry may be used to construct alternative equivalent embodiments. Other embodiments could be implemented using hardware component equivalents such as special purpose hardware, dedicated processors or combinations thereof.
Certain embodiments may be implemented using one or more programmed processors executing programming instructions that in certain instances are broadly described above in flow chart form that can be stored on any suitable electronic or computer readable storage medium (such as, for example, disc storage, Read Only Memory (ROM) devices, Random Access Memory (RAM) devices, network memory devices, optical storage elements, magnetic storage elements, magneto-optical storage elements, flash memory, core memory and/or other equivalent volatile and non-volatile storage technologies). However, those skilled in the art will appreciate, upon consideration of the present teaching, that the processes described above can be implemented in any number of variations and in many suitable programming languages without departing from embodiments of the present invention. For example, the order of certain operations carried out can often be varied, additional operations can be added or operations can be deleted without departing from certain embodiments of the invention. Error trapping can be added and/or enhanced and variations can be made in user interface processing and information presentation without departing from certain embodiments of the present invention. Such variations are contemplated and considered equivalent.
While certain illustrative embodiments have been described, it is evident that many alternatives, modifications, permutations and variations will become apparent to those skilled in the art in light of the foregoing description.
This application is related to the application titled “USER INTERFACE TO DISPLAY AGGREGATED DIGITAL LIVING NETWORK ALLIANCE (DLNA) CONTENT ON MULTIPLE SERVERS,” filed contemporaneously herewith on ______ and assigned application Ser. No. ______, and to the application titled “BRIDGE BETWEEN DIGITAL LIVING NETWORK ALLIANCE (DLNA) PROTOCOL AND WEB PROTOCOL,” filed contemporaneously herewith on ______ and assigned application Ser. No. ______, which are both hereby incorporated by reference as if fully set forth herein. The documents titled “ContentDirectory:1 Service Template Version 1.01,” by the UPnP™ Forum, dated Jun. 25, 2002, “MediaServer:1 Device Template Version 1.01,” by the UPnP™ Forum, dated Jun. 25, 2002, and “UPnP™ Device Architecture 1.0, Version 1.0.1,” by the UPnP™ Forum, dated Dec. 2, 2003 are incorporated in their entireties by reference as if fully set forth herein.
