Method and apparatus for managing bookmark information for content stored in a networked media server
A method and apparatus for managing bookmark information of a media server through a network based on the UPnP AV standard is disclosed. If a request for bookmarking a content item is made, a bookmark item is created and the created bookmark item is linked to the content item by adding the ID of the created bookmark item to the property information of the content item and recording the ID of the content item to be bookmarked in the created bookmark item.
Latest LG Electronics Patents:
- METHOD AND APPARATUS FOR MANAGING RANDOM ACCESS RESOURCE SETS BY CONSIDERING POTENTIAL FEATURES IN WIRELESS COMMUNICATION SYSTEM
- IMAGE DISPLAY APPARATUS AND OPERATING METHOD THEREOF
- DISPLAY DEVICE
- DEVICE AND METHOD FOR PERFORMING, ON BASIS OF CHANNEL INFORMATION, DEVICE GROUPING FOR FEDERATED LEARNING-BASED AIRCOMP OF NON-IID DATA ENVIRONMENT IN COMMUNICATION SYSTEM
- MAXIMUM POWER REDUCTION
This application is a continuation of U.S. application Ser. No. 11/120,930, filed May 2, 2005, now U.S. Pat. No. 8,010,620, which claims benefit of earlier filing date and right to priority to Korean Application No. 0031151/2004, filed on May 3, 2004, the contents of which are all hereby incorporated by reference herein in their entirety.
BACKGROUND OF THE INVENTION1. Field of the Invention
The present invention relates to bookmarking a content object and, more particularly, but not by way of limitation, to a method and apparatus for managing bookmark information for content objects stored in a media server through a network based on the UPnP AV standard.
2. Description of the Related Art
As the computing power of small devices improves, various inexpensive and universal networking techniques are appearing and being commercialized.
With the addition of Plug and Play (PnP) capabilities to the PC operating system it became a great deal easier to setup, configure, and add peripherals to a PC. Universal Plug and Play (UPnP) is an extension of the PnP technique to the entire network with a view to enabling discovery and control of networked devices and services, such as network-attached printers, Internet gateways, and consumer electronics equipment. The UPnP is based upon Internet technologies such as TCP/IP, HTTP, and XML.
The UPnP AV architecture defines three main logical entities: a media server (MS), a media renderer (MR), and an AV control point (CP). The media server (MS) has access to entertainment content and can send that content to another UPnP AV device via the network. The media renderer (MR) is able to receive external content from the network and render it on its local hardware. The AV control point (CP) coordinates the operation of the media server (MS) and the media renderer (MR).
In the UPnP architecture, each time a UPnP action such as a browsing action from the AV control point (CP) comes in, the media server (MS) exposes information on its content. The content selected through the user interface of the AN control point (CP) is transferred to the media renderer (MR) from the media server (MS) using a streaming technique and played by the media renderer (MR).
The playback of the content can be stopped by user's request while the content is being played and then resumed afterward. For example, a user may turn off an MP3 player while listening to music and want to resume playing of the music from the stopped position later. Similarly, a user may stop a DVD player while watching a DVD movie and want to resume the movie from the stopped position later. To this end, content players automatically store information about the state of the content being played when power is turned off or playback is stopped. Such a function is called automatic bookmarking.
Generally, bookmarking refers to storing the URL (uniform resource locator) of a web page that you visit using a web browser such as the Netscape navigator so that you can revisit the page easily at a later time. Once the URL of a web page is stored in the bookmark, the user can select the URL from the bookmark to visit the web page without entering the URL.
The media server in a home network can store a lot of contents, i.e., media files and can provide the same content to a plurality of users simultaneously through the network. The simple bookmarking function which stores the position at which the playing of the content is stopped is not appropriate when a plurality of users are playing the same content. The media server, therefore, requires an improved bookmarking function.
SUMMARY OF THE INVENTIONIn view of the shortcomings of the prior art, it is an object of the present invention to provide a method and apparatus that allows a plurality of users to bookmark contents stored in a media server individually.
It is another object of the invention to provide a method and apparatus that allows individual bookmarking of media contents based on the UPnP AV standard.
According to the present invention, if a request for bookmarking a content object is received, a bookmark object is created and an ID of the created bookmark object is added to property information of the content object.
According to the present invention, when a bookmark object is created, the ID of the content object to be bookmarked is included in the created bookmark object.
In one embodiment of the invention, the directory for storing bookmark objects is separated from the directory for storing content objects.
In another embodiment, bookmark objects are stored in a container placed in the directory for storing content objects.
In one embodiment of the invention, a bookmark object comprises a bookmark object ID for uniquely identifying the bookmark object, an ID of the bookmarked object, a title written in a user-readable format, a bookmark object class, a UDN for storing the ID of rendering control service (RenderingControl Service) and/or the ID of AVTransport service (AVTS) of a media renderer which was presenting the bookmarked object, and a list of state variables for storing the state variables of the RenderingControl service and AVTransport service.
In one embodiment of the invention, if a content object is bookmarked, a bookmark object is created and the ID thereof is added to metadata indicating the property of the bookmarked object.
In one embodiment of the invention, if a request for bookmarking a content is received, the control point sends a request for creating a bookmark to the media server. Receiving the request, the media server creates a bookmark object based upon the received information and adds the ID of the created bookmark object to metadata of the content object to be bookmarked.
In another embodiment of the invention, if a request for bookmarking a content is received, the control point sends a request for creating a bookmark to the media server. Receiving the request, the media server creates a bookmark object and sends the ID of the created object to the control point. The control point adds the ID of the bookmark object to metadata of the content object to be bookmarked and requests the media server to update metadata of the content object.
In one embodiment of the invention, the ID of a created bookmark object is determined according to a rule defined by the media server storing content objects.
In one embodiment of the invention, the class of the bookmark object is defined to “object.item.bookmarkitem”.
The above features and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
In order that the invention may be fully understood, preferred embodiments thereof will now be described with reference to the accompanying drawings.
The preferred embodiments of the present invention satisfy the following conditions for implementing a bookmark functionality based upon the UPnP AV standard.
1. Every object provided by the media server in the UPnP AV architecture can be bookmarked.
(1-1) Because it is not that the media server provides only a single content to users, contents can be bookmarked individually.
(1-2) One content can be bookmarked at several different locations within the content.
2. The list of saved bookmarks can be displayed to allow a bookmark can be selected therefrom.
(2-1) Information on all of the saved bookmarks can be provided to the users and all of the bookmarks are placed in a single container for making it easy to select one bookmark from among the bookmarks.
(2-2) Because the number of bookmarks that can be displayed may be limited, information specifying the number of bookmarks to be displayed can be provided.
(2-3) Information on the starting index specifying the starting position for searching bookmarks can be provided.
(2-4) Information on the number of the saved bookmarks can be provided.
3. If a bookmark is selected, a content can be played or removed using the information of the selected bookmark.
The bookmark object structure shown in
The bookmark object ID (BM objectID) 210 is determined automatically according to a predefined rule when a bookmark object is created. Information to be recorded in the bookmark title (Title) 212, the bookmark object class (Object Class) 213, the unique device number (UDN) 214, and the list of state variables (State Variable List) 215 is provided by the AV control point (CP) when the AV control point (CP) makes a request for the creation of a bookmark. The information to be contained in the list of state variables (State Variable List) 215, etc. is received from the media renderer (MR) and provided to the media server (MR).
The procedure for creating a bookmark object of the above structure and managing the information thereof will now be described in detail.
If a user makes a request for bookmarking the content 311 that is being played by a media renderer (not illustrated), a bookmark object (also called bookmark item) is created by using “CreateObject” action defined by the UPnP AV standard.
The procedure will be described in more detail. If the user makes a request for bookmarking the content being played, (S301), the control point 320 requests the RenderingControl service and AVTS of the media renderer to provide the state variables for the content and receives the state variables through “GetStateVariables( )” action (S302). The control point 320 is a control application capable of detecting and controlling other devices and/or services. The control point 320 is executed on a device having a user-friendly environment such as a PDA. The control point 302 can be incorporated into the media renderer.
If the streaming from the media server 310 to the media renderer is done in push mode wherein AVIS is executed on the media server 310, the control point 320 receives the state variables of AVTS from the media server 310.
The control point 320 calls “CreateObject action” so that the content directory service (CDS) of the media server 310 creates a bookmark object. Bookmark information to be contained in the bookmark object is also provided as arguments to the action (S303). The bookmark information is information to be recorded in the fields of the ID of the bookmarked object 211, the title 212, the object class 213, the unique device number (UDN) 214, and the list of state variables 215 shown in
The information to be stored in the title 212 may be organized into a vendor-specific part and a user input part. If the title 212 contains separate room for the user input part, the control point 320 requests the user to enter a desired string for easy identification of the content and transfers the user-entered string to the media server 310 as an input argument to “CreateObject” action. Alternatively, the control point 320 can transfer the title of the object to be bookmarked to the media server 310. The information to be stored in the object class 213 is “object.item.bookmarkitem” as mentioned above. Additional information can be transferred in different embodiments.
“CreateObject” action for creating the bookmark object and input arguments thereof are written in a markup language such as XML and delivered to the media server 310.
Receiving the action, the content directory service (CDS) of the media server 310 creates a bookmark object based on the information contained in the input arguments to the action. The ID of the bookmark object is generated according to a predefined rule and recorded in the bookmark object ID (BM ObjectID) field 210 (S304).
Before creating the bookmark object, the content directory service (CDS) of the media server 310 first determines if bookmark objects having the same information contained in the input arguments to the “CreateObject” action exist. A bookmark object is newly created only when there is no such bookmark.
The existing UPnP AV standard requires that every content should be contained in a root object having the ID of “0”. In the preferred embodiment of the present invention shown in
It is also possible to place the container for storing bookmark objects in a special container under the root container “0”.
If the control point 320 set the parentobjectID to “bookmark_holder” when calling the “CreateObject” action, the content directory service (CDS) of the media server 310 creates the bookmark object under the root container 312 the ID of which is “bookmark_holder”.
After creating the bookmark object as described above, the content directory service (CDS) of the media server 310 adds the ID of the created bookmark object to the metadata describing the property of the bookmarked object, i.e., the content being played. In other words, the content directory service (CDS) updates the information about the bookmarked object (S305). The reason for linking the bookmark object and the bookmarked object by storing the ID of the bookmark object in the bookmarked object is to update also the bookmark object linked to the content object when the content object is changed.
For example, if the content object linked to the bookmark object is removed, the bookmark object is not valid any more. In this case, when the content object is removed, the bookmark object linked to the content object is detected using the stored bookmark object ID and the linked bookmark object is removed as well.
After creating the bookmark object and updating the metadata of the linked content object, the content directory service (CDS) of the media server 310 transfers the ID of the created bookmark object and the updated metadata of the content object to the control point 320 (S306 and 5307) so that the control point 320 can update its information about objects and bookmarks that have been received through a previous browsing action. The information transfer can be done through a reply to the “CreateObject action for creating the bookmark object or through an event generated by a change in the information about objects managed by the content directory service (CDS).
If more than one request for bookmarking one content is received, the media server 310 creates bookmark objects as many as the number of the requests in the corresponding bookmark container as shown in
In the example shown in
The procedure for searching bookmarks registered as described above is described below.
To search a bookmark object, the control point 320 makes a request for browse action to the media server 310 with setting the parentobjectID field to “bookmark_holder” (or the ID of the container wherein bookmark objects are stored). If the directory for bookmark objects is separated from the directory for contents, only the bookmark objects are found while the content items and/or containers are found together when the request for “browse” action is made with parentobjectID field set to “0”.
The control point 320 may make a request for “browse bookmark” action, which has the same function as “browse” action, to the media server 310 with setting the root ID to “0” instead of setting to the root ID of the bookmark object directory structure (e.g., “bookmark_holder”). If “browse bookmark” action is requested, the content directory service (CDS) of the media server 310 interprets the value of the parentobjectID field which is set to “0” as the root ID of the bookmark object directory structure (e.g., “bookmark_holder”) and searches the child items, i.e., bookmark objects, wherein the parentobjectID is delivered as an input argument to the action. The detected bookmark objects are transferred to the control point 320 as the result of “browse bookmark” action.
The syntax for specifying the number of bookmark objects to retrieve and from which object the search operation starts in “browse bookmark” action is the same as the syntax of “browse” action.
To delete a bookmark object, “DestroyObject” action is used with the same syntax for deleting a content object. When a bookmark object is deleted, the content directory service (CDS) of the media server 310 removes the ID of the bookmark object from the metadata of the bookmarked object linked to the bookmark object. The updated object information is provided to the control point 320 in an appropriate manner so that media server 310 and the control point 310 can synchronize their object information.
The present invention allows a user to bookmark content objects as many as required at any position, thereby providing a more convenient environment for playing contents.
The present invention automatically executes editing operations required for management of bookmarks and contents by effectively linking created bookmarks and content objects, thereby facilitating the bookmark management.
While the invention has been disclosed with respect to a limited number of embodiments, those skilled in the art, having the benefit of this disclosure, will appreciate numerous modifications and variations therefrom. It is intended that all such modifications and variations fall within the spirit and scope of the invention.
Claims
1. A method for creating a bookmark item in a Universal Plug and Play (UPnP) network including a server, a player and a controller for controlling the server and the player, the method performed by the controller and comprising:
- performing a requesting operation to request rendering state information and transporting state information, the rendering state information and the transporting state information associated with playback of a content item,
- wherein when the UPnP network is configured in a specific mode, the requesting operation comprises: transmitting a request for the rendering state information and the transporting state information to a player; and receiving the rendering state information and the transporting state information from the player: and
- transmitting a creating request to a server, the creating request including the rendering state information and the transporting state information,
- wherein the creating request instructs the server to create the bookmark item in the server and to update the content item, the bookmark item used for recovering the rendering state information and the transporting state information,
- wherein the bookmark item comprises the rendering state information, the transporting state information, a bookmark identifier (ID) and a content ID of the content item to associate the bookmark item with the content item, and
- wherein the content item is updated to include the bookmark ID to associate the content item with the bookmark item.
2. The method of claim 1, wherein the rendering state information includes at least audio volume or display luminance.
3. The method of claim 1, wherein the bookmark ID is generated by the server.
4. The method of claim 1, wherein the bookmark item is created under a container assigned by the controller.
5. A controller for creating a bookmark item in a Universal Plug and Play (UPnP) network including a server, a player and a controller for controlling the server and the player, the controller comprising:
- an interface unit configured to at least transmit or receive data; and
- a control unit configured to: perform a requesting operation to request rendering state information and transporting state information, the rendering state information and the transporting state information associated with playback of a content item, wherein, when the UPnP network is configured in a specific mode, the requesting operation comprises: transmitting, via the interface unit, a request for the rendering state information and the transporting state information to a player; and receiving, via the interface unit, the rendering state information and the transporting state information from the player; and transmit, via the interface unit, a creating request to a server, the creating request including the rendering state information and the transporting state information,
- wherein the creating request instructs the server to create the bookmark item in the server and to update the content item, the bookmark item used for recovering the rendering state information and the transporting state information,
- wherein the bookmark item comprises the rendering state information, the transporting state information, a bookmark identifier (ID) and a content ID of the content item to associate the bookmark item with the content item, and
- wherein the content item is updated to include the bookmark ID to associate the content item with the bookmark item.
6. The controller of claim 5, wherein the rendering state information includes at least audio volume or display luminance.
7. The controller of claim 5, wherein the bookmark ID is generated by the server.
8. The controller of claim 5, wherein the bookmark item is created under a container assigned by the controller.
5524193 | June 4, 1996 | Covington et al. |
5655117 | August 5, 1997 | Goldberg et al. |
5922045 | July 13, 1999 | Hanson |
6064380 | May 16, 2000 | Swenson et al. |
6144380 | November 7, 2000 | Shwarts et al. |
6173317 | January 9, 2001 | Chaddha et al. |
6178440 | January 23, 2001 | Foster et al. |
6185588 | February 6, 2001 | Olson-Williams et al. |
6202025 | March 13, 2001 | Harada |
6219679 | April 17, 2001 | Brisebois et al. |
6289346 | September 11, 2001 | Milewski et al. |
6332144 | December 18, 2001 | deVries et al. |
6360057 | March 19, 2002 | Tsumagari et al. |
6460038 | October 1, 2002 | Khan et al. |
6480669 | November 12, 2002 | Tsumagari et al. |
6492998 | December 10, 2002 | Kim et al. |
6519764 | February 11, 2003 | Atkinson et al. |
6543053 | April 1, 2003 | Li et al. |
6556773 | April 29, 2003 | Tsumagari et al. |
6556774 | April 29, 2003 | Tsumagari et al. |
6564008 | May 13, 2003 | Tsumagari et al. |
6574421 | June 3, 2003 | Tsumagari et al. |
6584277 | June 24, 2003 | Tsumagari et al. |
6628892 | September 30, 2003 | Tsumagari et al. |
6647389 | November 11, 2003 | Fitch et al. |
6654933 | November 25, 2003 | Abbott et al. |
6678700 | January 13, 2004 | Moore et al. |
6725227 | April 20, 2004 | Li |
6798976 | September 28, 2004 | Tsumagari et al. |
6868225 | March 15, 2005 | Brown et al. |
6944391 | September 13, 2005 | Tsumagari et al. |
6988245 | January 17, 2006 | Janevski |
6990671 | January 24, 2006 | Evans et al. |
6992687 | January 31, 2006 | Baird et al. |
6996329 | February 7, 2006 | Tsumagari et al. |
7032177 | April 18, 2006 | Novak et al. |
7143353 | November 28, 2006 | McGee et al. |
7194677 | March 20, 2007 | Rizk et al. |
7222154 | May 22, 2007 | Dowling |
7269604 | September 11, 2007 | Moore et al. |
7286747 | October 23, 2007 | Lewis et al. |
7289812 | October 30, 2007 | Roberts et al. |
7319806 | January 15, 2008 | Willner et al. |
7320137 | January 15, 2008 | Novak et al. |
7324997 | January 29, 2008 | Yamada |
7392481 | June 24, 2008 | Gewickey et al. |
7406656 | July 29, 2008 | Schroeder |
7454515 | November 18, 2008 | Lamkin et al. |
7506022 | March 17, 2009 | Wang et al. |
7546022 | June 9, 2009 | Sawada |
7564956 | July 21, 2009 | Holtzberg |
7584290 | September 1, 2009 | Ruskin et al. |
7602379 | October 13, 2009 | Lemon |
7616946 | November 10, 2009 | Park et al. |
7623824 | November 24, 2009 | Anttila et al. |
7624337 | November 24, 2009 | Sull et al. |
7636705 | December 22, 2009 | Kim |
7725919 | May 25, 2010 | Thiagarajan et al. |
7774797 | August 10, 2010 | Evans et al. |
7801850 | September 21, 2010 | Moore et al. |
7849160 | December 7, 2010 | Hayward |
7890599 | February 15, 2011 | Kalmanje et al. |
7904797 | March 8, 2011 | Wong et al. |
7958093 | June 7, 2011 | Anderson et al. |
8010579 | August 30, 2011 | Metsatahti et al. |
8010620 | August 30, 2011 | Ahn et al. |
8028037 | September 27, 2011 | Ahn et al. |
8065335 | November 22, 2011 | Min et al. |
8126897 | February 28, 2012 | Sznajder et al. |
20020069218 | June 6, 2002 | Sull et al. |
20020076014 | June 20, 2002 | Holtzberg |
20020078144 | June 20, 2002 | Lamkin et al. |
20020083035 | June 27, 2002 | Pearl et al. |
20020091675 | July 11, 2002 | Shimokawa et al. |
20020159640 | October 31, 2002 | Vaithilingam et al. |
20020163532 | November 7, 2002 | Thomas et al. |
20020194608 | December 19, 2002 | Goldhor |
20030028892 | February 6, 2003 | Gewickey et al. |
20030078986 | April 24, 2003 | Ayres et al. |
20030088422 | May 8, 2003 | Denenberg et al. |
20030122966 | July 3, 2003 | Markman et al. |
20030126599 | July 3, 2003 | Novak et al. |
20030144984 | July 31, 2003 | Dunbar |
20030229900 | December 11, 2003 | Reisman |
20040003403 | January 1, 2004 | Marsh |
20040008970 | January 15, 2004 | Junkersfeld et al. |
20040044745 | March 4, 2004 | Shimizu et al. |
20040139047 | July 15, 2004 | Rechsteiner et al. |
20040165483 | August 26, 2004 | Unger |
20040220926 | November 4, 2004 | Lamkin et al. |
20040223737 | November 11, 2004 | Johnson |
20040230636 | November 18, 2004 | Masuoka et al. |
20040236774 | November 25, 2004 | Baird et al. |
20050047756 | March 3, 2005 | Evans |
20050081159 | April 14, 2005 | Gupta et al. |
20050097623 | May 5, 2005 | Tecot et al. |
20050108233 | May 19, 2005 | Metsatahti et al. |
20050114897 | May 26, 2005 | Cho et al. |
20050135341 | June 23, 2005 | Kim |
20050155077 | July 14, 2005 | Lawrence et al. |
20050172018 | August 4, 2005 | Devine et al. |
20050182828 | August 18, 2005 | Lamkin et al. |
20050193322 | September 1, 2005 | Lamkin et al. |
20050198574 | September 8, 2005 | Lamkin et al. |
20050210145 | September 22, 2005 | Kim et al. |
20050246622 | November 3, 2005 | Ahn et al. |
20050251749 | November 10, 2005 | Lamkin et al. |
20050265701 | December 1, 2005 | Lamkin et al. |
20050278435 | December 15, 2005 | Lamkin et al. |
20050278458 | December 15, 2005 | Berger et al. |
20050278729 | December 15, 2005 | Lamkin et al. |
20050289465 | December 29, 2005 | Matsuda |
20060041639 | February 23, 2006 | Lamkin et al. |
20060041640 | February 23, 2006 | Lamkin et al. |
20060089981 | April 27, 2006 | Ahn et al. |
20060168000 | July 27, 2006 | Bodlaender |
20060242161 | October 26, 2006 | Ten Kate et al. |
20060242306 | October 26, 2006 | Boro et al. |
20060277316 | December 7, 2006 | Wang et al. |
20060293991 | December 28, 2006 | Jenzowsky et al. |
20060294192 | December 28, 2006 | Mao et al. |
20070027926 | February 1, 2007 | Kinouchi et al. |
20070027949 | February 1, 2007 | Park et al. |
20070031109 | February 8, 2007 | Tsuboi et al. |
20070033292 | February 8, 2007 | Sull et al. |
20070033533 | February 8, 2007 | Sull |
20070044010 | February 22, 2007 | Sull et al. |
20070094376 | April 26, 2007 | Ahn et al. |
20070104461 | May 10, 2007 | Cho |
20070244903 | October 18, 2007 | Ratliff et al. |
20090049118 | February 19, 2009 | Stevens |
20090106356 | April 23, 2009 | Brase et al. |
20090205006 | August 13, 2009 | Lopez |
20090228569 | September 10, 2009 | Kalmanje et al. |
20090254823 | October 8, 2009 | Barrett |
20090319672 | December 24, 2009 | Reisman |
20090320073 | December 24, 2009 | Reisman |
20100027966 | February 4, 2010 | Harrang et al. |
20100036888 | February 11, 2010 | Carter et al. |
20100042702 | February 18, 2010 | Hanses |
20100042746 | February 18, 2010 | Keum et al. |
20100121941 | May 13, 2010 | Harrang et al. |
20100217827 | August 26, 2010 | Ahn et al. |
20100217828 | August 26, 2010 | Ahn et al. |
20100217829 | August 26, 2010 | Ahn et al. |
20100217830 | August 26, 2010 | Ahn et al. |
20100217831 | August 26, 2010 | Ahn et al. |
20100217832 | August 26, 2010 | Ahn et al. |
20100217833 | August 26, 2010 | Ahn et al. |
20100218079 | August 26, 2010 | Ahn et al. |
20100223316 | September 2, 2010 | Ahn et al. |
20100223353 | September 2, 2010 | Ahn et al. |
20100241703 | September 23, 2010 | Ahn et al. |
20100241704 | September 23, 2010 | Ahn et al. |
20100241706 | September 23, 2010 | Ahn et al. |
20100241735 | September 23, 2010 | Ahn et al. |
20100250667 | September 30, 2010 | Ahn et al. |
20110029597 | February 3, 2011 | Morinaga |
20110047571 | February 24, 2011 | Zhang et al. |
20110078234 | March 31, 2011 | Engel |
20110131332 | June 2, 2011 | Bouazizi |
20110137976 | June 9, 2011 | Poniatowski et al. |
20110158606 | June 30, 2011 | Lin et al. |
20110314502 | December 22, 2011 | Levy et al. |
20120011551 | January 12, 2012 | Levy et al. |
2001-209602 | August 2001 | JP |
2000-0058779 | October 2000 | KR |
2001-0107082 | July 2001 | KR |
2003-0004926 | January 2003 | KR |
2003-0097095 | December 2003 | KR |
00-58967 | October 2000 | WO |
02-102079 | December 2002 | WO |
- Ritchie J., et al.; “UPnP AV Architecture: 0.83, For Universal Plug and Play Version 1.0”; Jun. 12, 2002; XP-002271673.
- Greer, T., et al.; “ADOBE: Acrobat—Programmatically Insert Bookmark, thread 223-639638”; Aug. 27, 2003; XP002426873.
- Ritchie J., et al.; “UPnP AV Architecture: 1, For Universal Plug and Play Version 1.0”; Jun. 25, 2002.
- Debique, K., et al.; “Content Directory: 1 Service Template Version 1.01”; Jun. 25, 2002.
Type: Grant
Filed: May 28, 2010
Date of Patent: Jul 31, 2012
Patent Publication Number: 20100250667
Assignee: LG Electronics Inc. (Seoul)
Inventors: Sung Joon Ahn (Kyunggi-do), Chang Hyun Kim (Seoul)
Primary Examiner: Zarni Maung
Attorney: Lee, Hong, Degerman, Kang & Waimey
Application Number: 12/790,719
International Classification: G06F 15/16 (20060101); G06F 12/00 (20060101);