Apparatuses and methods consistent with the exemplary embodiments relate to providing a remote user interface (UI) service, and more particularly, to a method and an apparatus for providing a remote UI service, such as Multimedia Messaging Service (MMS) and Simple Message Service (SMS), for controlling message-related functions of a remote UI server device, by using a remote UI client device.
Mobile devices, such as cellular phones, perform communications services, such as telephone calls and message exchange, between other devices, by using communication technologies including global system for mobile communication (GSM) and code division multiple access (CDMA).
A mobile device performs various controls, such as connection or termination of telephone calls and confirming, forwarding, or replying to messages, via a user interface (UI) embodied in the mobile device.
Meanwhile, a mobile device may be remote-controlled by a control device within a home network by transmitting commands according to a predetermined protocol to the mobile device using home network technology. In this case, new functions according to the predetermined protocol should be embodied in the control device and the mobile device.
Exemplary embodiments address at least the above problems and/or disadvantages and other disadvantages not described above. Also, the exemplary embodiments are not required to overcome the disadvantages described above, and an exemplary embodiment may not overcome any of the problems described above.
The exemplary embodiments provide a method and an apparatus for providing a remote UI service, such as MMS and SMS, for controlling message-related functions of a remote UI server device, by using a remote UI client device.
The exemplary embodiments also provide a computer readable recording medium having recorded thereon a computer program for executing the method.
According to an aspect of the exemplary embodiments, there is provided a method by which a remote user interface (UI) client device provides a remote UI service, the method including the steps of receiving an event message, which includes a URL for accessing a first UI resource providing a UI notifying the receipt of a message, from a remote UI server device; obtaining the first UI resource from the remote UI server device by using the URL; receiving external inputs of message control commands via the first UI resource; and transmitting the message control command to the remote UI server device.
The message may include multimedia messaging service (MMS) messages and simple messaging service (SMS) messages.
The first UI resource may include a web page or bitmaps of an application and provides a UI which partially displays the content of the message and receives external inputs of message control commands for controlling the message.
The message control commands may include confirm commands, playback commands, stop commands, reply commands, forward commands, delete commands, save commands, and move commands, but are not limited thereto.
The method may further include obtaining a second UI resource providing a UI, which displays the complete content of the message, from the remote UI server device in the case where the control command is either a confirm or play back.
The method may further include obtaining a third UI resource providing a UI, which receives external inputs of texts and a control command for transmitting a message, from the remote UI server device; receiving external inputs of texts and the control command for transmitting a message by using the third UI resource; and transmitting the texts and the control command for transmitting the message to the remote UI server device, in the case where the control command is a reply.
The method may further include the steps of obtaining a fourth UI resource providing a UI, which displays a list of commonly used phrases and receives inputs of commands for selecting commonly used phrases, from the remote UI server device; receiving an external input of a command for selecting a commonly used phrase; and transmitting the command for selecting the commonly used phrase to the remote UI server device.
The method may further include obtaining a fifth UI resource providing a UI, which displays a list of telephone numbers and receives external inputs of commands for selecting telephone numbers, from the remote UI server device; receiving external inputs of the control command for selecting telephone number; and transmitting the control commands for selecting telephone numbers to the remote UI server device, in case where the control command is a forward command.
The method may further include a step of displaying the first UI resource.
The step of displaying the first UI resource may include displaying a web page by using a web browser or bitmaps of a UI application by using a bitmap browser.
The event message may be composed according to universal plug and play (UPnP) Remote UI or consumer electronics association (CEA) 2014 standards, but is not limited thereto, and the event message may be received via a unicast transmission or a multicast transmission.
According to another aspect of the exemplary embodiments, there is provided a method by which a remote user interface (UI) server device provides a remote UI service, the method including the steps of receiving a message from a message transmitting device; transmitting an event message, which includes a URL for accessing a first UI resource providing a UI notifying the receipt of the message, to a remote UI client device; transmitting the first UI resource to the remote UI client device by using the URL in response to a request form the remote UI client device; receiving a control command for controlling the message from the remote UI client device; and controlling the message by executing control functions related to the message.
The message includes multimedia messaging service (MMS) messages and simple messaging service (SMS) messages.
The first UI resource includes a web page or bitmaps of an application and provides a UI which partially displays the content of the message and receives external inputs of message control commands for controlling the message.
The message control commands include confirm commands, playback commands, stop commands, reply commands, forward commands, delete commands, save commands, and move commands, but are not limited thereto.
The method may further include a step of transmitting a second UI resource providing a UI, which displays the complete content of the message, to the remote UI client device, in the case where the control command is either a confirm command or a play back command.
The method may further include transmitting a third UI resource providing a UI, which receives external inputs of texts and a control command for transmitting a message, to the remote UI client device, in the case where the control command is a reply command.
The method may further include transmitting a fourth UI resource providing a UI, which displays a list of commonly used phrases and receives inputs of commands for selecting commonly used phrases, to the remote UI client device.
The method may further include transmitting a fifth UI resource providing a UI, which displays a list of telephone numbers and receives external inputs of commands for selecting telephone numbers, to the remote UI client device, in the case where the control command is a forward command.
The event message may be composed according to universal plug and play (UPnP) Remote UI or consumer electronics association (CEA) 2014 standards, but is not limited thereto, and the event message may be transmitted via a unicast transmission or a multicast transmission.
According to another aspect of the exemplary embodiments, there is provided a computer readable recording medium having recorded thereon a computer program for executing the method.
According to another aspect of the exemplary embodiments, there is provided a remote user interface (UI) client device including an event handler unit receiving an event message, which includes a URL for accessing a first UI resource providing a UI notifying the receipt of a message, from a remote UI server device; a UI resource obtaining unit obtaining the first UI resource from the remote UI server device by using the URL; a control command inputting unit receiving external inputs of message control commands via the first UI resource; and a control command transmitting unit transmitting the message control command to the remote UI server device.
According to another aspect of the exemplary embodiments, there is provided a remote user interface (UI) server device including a message receiving unit receiving a message from a message transmitting device; an event handler unit transmitting an event message, which includes a URL for accessing a first UI resource providing a UI notifying the receipt of the message, to a remote UI client device; a UI resource transmitting unit transmitting the first UI resource to the remote UI client device by using the URL in response to a request form the remote UI client device; and a control command receiving unit receiving a control command for controlling the message from the remote UI client device; and a control unit controlling the message.
The above and other aspects of the exemplary embodiments will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which:
The exemplary embodiments will now be described more fully with reference to the accompanying drawings, in which exemplary embodiments are shown. In the drawings, the thicknesses of layers and regions are exaggerated for clarity. Like reference numerals in the drawings denote like elements, and thus their description will be omitted.
A remote UI server device 120 remotely provides a UI resource via a network. The UI resource provides a UI for notifying receipt of messages and for receiving external inputs of message control commands, and includes a web page or bitmaps of an application. A remote UI client device 110 receives notifications of messages and receives external inputs of message control commands via the UI resource provided by the remote UI server device 120. The remote UI client device 110 transmits input commands to the remote UI server device 120. Message control commands include confirm commands, playback commands, stop commands, reply commands, forward commands, delete commands, save commands, and move commands, but are not limited thereto. The remote UI server device 120 controls corresponding messages by using transmitted commands.
The remote UI server device 120 may be a device for receiving messages from a message transmitting device via a network including a cellular network and a data network. Examples of the remote UI server device 120 include a handheld phone and an IP phone, but this is not limited thereto. Examples of messages received by the remote UI server device 120 include multimedia messaging service (MMS) messages and simple messaging service (SMS) messages, but this is not limited thereto.
The remote UI client device 110 is a device including a display unit for displaying messages, and is a network-based device to which a user may easily input message control commands and texts. Examples of the remote UI client devices 110 include a DTV and a PC, but this is not limited thereto.
According to the present exemplary embodiment, messaging services of the remote UI server device 120 may be extended to other devices within a home network by enabling the remote UI client device 110 to use and control message-related functions including the MMS and the SMS.
Furthermore, the present exemplary embodiment provides a user convenience that a user may easily control message-related functions of the remote UI server device 120 by using the remote UI client device 110.
The remote UI server device 120, which received a SMS message, transmits an event message, which includes a uniform resource locator (URL) for accessing a UI resource providing a UI notifying the receipt of the message, to the remote UI client device 110.
The remote UI client device 110 obtains the UI resource from the remote UI server device 120 by using the URL. In the example shown in
In the case where the remote UI client device 110 receives an external input of a message control command to confirm the message, the remote UI client device 110 transmits the message control command to confirm the message to the remote UI server device 120. Then, then remote UI client device 110 obtains a UI resource providing a UI, which displays the complete content of the SMS message, from the remote UI server device 120 and displays the corresponding UI resource indicated by the reference numeral 220 in
Furthermore, although a UI for receiving SMS message control commands, such as reply, forward, delete, and save, may either be provided via the UI resource partially displaying the content of a SMS message or the UI resource displaying the complete content of the SMS message, it would have been obvious to one of ordinary skill in the art that the UI for receiving SMS message control commands, such as reply, forward, delete, and save, may be embodied otherwise.
In the case where the remote UI client device 110 receives an external input of a message control command to reply the message, the remote UI client device 110 transmits the message control command to reply the message to the remote UI server device 120. Then, the remote UI client device 110 obtains a UI resource providing a UI, which displays a list of commonly used phrases and receives inputs of commands for selecting commonly used phrases, from the remote UI server device 120 and displays the corresponding UI resource indicated by the reference numeral 310 in
In the case where the remote UI client device 110 receives an external input of a command for selecting a commonly used phrase, the remote UI client device 110 transmits the command for selecting a commonly used phrase to the remote UI server device 120. Then, the remote UI client device 110 obtains a UI resource providing a UI, which displays selected commonly used phrases, from the remote UI server device 120, and displays the corresponding UI resource indicated by the reference numeral 320 in
In the case where the remote UI client device 110 receives an external input of a message control command to forward the message, the remote UI client device 110 transmits the message control command to forward the message to the remote UI server device 120. Then, the remote UI client device 110 obtains a UI resource providing a UI, which displays a list of telephone numbers and users associated with each telephone number, and receives inputs of commands for selecting telephone numbers, from the remote UI server device 120, and displays the corresponding UI resource indicated by the reference numeral 410 in
In the case where the remote UI client device 110 receives an external input of a command for selecting a telephone number, the remote UI client device 110 transmits the command for selecting a telephone number to the remote UI server device 120. Then, the remote UI client device 110 obtains a UI resource providing a UI, which displays selected telephone numbers, from the remote UI server device 120, and displays the corresponding UI resource indicated by the reference numeral 420 in
The remote UI server device 120, which received a MMS message, transmits an event message, which includes a URL for accessing a UI resource providing a UI, which notifying the receipt of the message, to the remote UI client device 110.
The remote UI client device 110 obtains the UI resource from the remote UI server device 120 by using the URL. In the example shown in
In case where the remote UI client device 110 receives an external input of a message control command to confirm the message, the remote UI client device 110 transmits the message control command to confirm the message to the remote UI server device 120. Then, then remote UI client device 110 obtains a UI resource providing a UI, which displays the complete content of the MMS message, from the remote UI server device 120 and displays the corresponding UI resource indicated by the reference numeral 520 in
Furthermore, although a UI for receiving MMS message control commands, such as reply, forward, delete, and save, may be either provided via the UI resource displaying information regarding the sender of the MMS message or the UI resource displaying the complete content of the MMS message, it would have been obvious to one of ordinary skill in the art that the UI for receiving MMS message control commands, such as reply, forward, delete, and save, may be embodied otherwise.
The remote UI server device 120, which received a MMS message, transmits an event message, which includes a URL for accessing a UI resource providing a UI, which notifies the receipt of the message, to the remote UI client device 110.
The remote UI client device 110 obtains the UI resource from the remote UI server device 120 by using the URL. In the example shown in
In the case where the remote UI client device 110 receives an external input of a message control command to confirm the message, the remote UI client device 110 transmits the message control command to confirm the message to the remote UI server device 120. Then, the remote UI client device 110 obtains a UI resource providing a UI, which displays the complete content of the MMS message, from the remote UI server device 120 and displays the corresponding UI resource (not shown).
Furthermore, although a UI for receiving MMS message control commands, such as reply, forward, delete, and save, may be either provided via the UI resource partially displaying the content of the MMS message or the UI resource displaying the complete content of the MMS message, it would have been obvious to one of ordinary skill in the art that the UI for receiving MMS message control commands, such as reply, forward, delete, and save, may be embodied otherwise.
The remote UI client device 700 includes an event handler unit 710, a UI resource obtaining unit 720, a display unit 730, a control command inputting unit 740, and a control command transmitting unit 750.
In the case where the remote UI server device 800 receives a message, the event handler unit 710 receives an event message, which includes a URL for accessing a UI resource providing a UI notifying the receipt of the message, from a remote UI server device 800. Examples of the messages received by the remote UI server device 800 include MMS messages and SMS messages, but this is not limited thereto.
The UI resource partially displays the content of the message, provides a UI for receiving external inputs of message control commands, and includes a web page or bitmaps of an application.
An event message may be composed according to any of various home network standards, including universal plug and play (UPnP) Remote UI and consumer electronics association (CEA) 2014 standards, and is received via a unicast transmission or a multicast transmission.
The UI resource obtaining unit 720 obtains a UI resource from the remote UI server device 800 by using a URL. Protocols via which the UI resource obtaining unit 720 obtains a UI resource include extended remoting technology (XRT), remote desktop protocol (RDP), and hypertext transfer protocol (HTTP). However, it will be obvious to one of ordinary skill in the art that other protocols may also be used.
A capability matching unit (not shown) obtains capability information with respect to a UI resource from the remote UI server device 800. Capability information includes resolution information and codec information with respect to a UI resource. The UI resource obtaining unit 720 may obtain a UI resource that can be processed by the remote UI client device 700 with reference to capability information obtained by the capability matching unit.
Meanwhile, if a device (e.g., an UPnP control point device) acting as a negotiator between the remote UI server device 800 and the remote UI client device 700 exists, the capability matching unit transmits capability information with respect to a UI resource that can be processed by the remote UI client device 700 to the negotiating device. In this case, the capability matching unit obtains capability information negotiated between the remote UI server device 800 and the remote UI client device 700 from the negotiating device. The UI resource obtaining unit 720 may obtain a UI resource that can be processed by the remote UI client device 700 with reference to the negotiated capability information obtained by the capability matching unit.
The display unit 730 displays a UI resource. The display unit 730 displays either a web page by using a web browser or bitmaps of a UI application by using a bitmap browser.
The control command inputting unit 740 receives external inputs of message control commands via a UI resource. Message control commands includes confirm commands, playback commands, stop commands, reply commands, forward commands, delete commands, save commands, and move commands, but are not limited thereto. The control command inputting unit 740 receives the external inputs of message control commands via a web page or an application with a message control command inputting interface.
The control command transmitting unit 750 transmits an externally input control command to the remote UI server device 800 by using a UI resource. The control command transmitting unit 750 may use either the same session as a session for obtaining a UI resource, or an asynchronous session independent from the session for obtaining the UI resource. An asynchronous session may be embodied by using asynchronous JavaScript and XML (AJAX). However, it will be obvious to one of ordinary skill in the art that an asynchronous session may be embodied by using any of various other methods. AJAX refers to a web developing technique for authoring a communicative web application and is capable of exchanging and manipulating data asynchronously with a web server. Detailed descriptions of AJAX are omitted here.
In the case where a control command transmitted by the control command transmitting unit 750 is either a control command to confirm a message or a control message to play back a message, the UI resource obtaining unit 720 obtains a UI resource providing a UI, which displays the complete content of the message, from the remote UI server device 800.
In the case where a control command transmitted by the control command transmitting unit 750 is a control command to reply to the message, the UI resource obtaining unit 720 obtains a UI resource providing a UI, which receives external inputs of texts and a control command for transmitting a message, from the remote UI server device 800. The control command inputting unit 740 receives external inputs of texts and a control command for transmitting a message. The control command transmitting unit 750 transmits the texts and the control command for transmitting the message to the remote UI server device 800.
Meanwhile, the texts may include commonly used phrases. Thus, the UI resource obtaining unit 720 obtains a UI resource providing a UI, which displays a list of commonly used phrases and receives inputs of commands for selecting commonly used phrases, from the remote UI server device 800. The control command inputting unit 740 receives an external input of a command for selecting a commonly used phrase. The control command transmitting unit 750 transmits the command for selecting a commonly used phrase to the remote UI server device 800. The UI resource obtaining unit 720 obtains a UI resource providing a UI, which displays reply texts including selected commonly used phrases, from the remote UI server device 800.
In the case where a control command transmitted by the control command transmitting unit 750 is a control command to forward the message, the UI resource obtaining unit 720 obtains a UI resource providing a UI, which displays a list of telephone numbers and associated users, and receives external inputs of commands for selecting telephone numbers, from the remote UI server device 800. The control command inputting unit 740 receives external inputs of the control command for selecting telephone numbers. The control command transmitting unit 750 transmits the control commands for selecting telephone numbers to the remote UI server device 800. The UI resource obtaining unit 720 obtains a UI resource providing a UI, which displays selected telephone numbers and reply texts, from the remote UI server device 800.
The remote UI server device 800 includes a message receiving unit 810, an event handler unit 820, a UI resource transmitting unit 830, a control command receiving unit 840, and a control unit 860.
The message receiving unit 810 receives messages from a message transmitting device via a cellular network, including a global system for mobile communication (GSM) network and a code division multiple access (CDMA) network. Examples of the messages received by the message receiving unit 810 include MMS messages and SMS messages, but are not limited thereto.
The event handler unit 820 transmits an event message, which includes a URL for accessing a UI resource providing a UI notifying the receipt of a message, to a remote UI client device 700.
The UI resource transmitting unit 830 transmits a UI resource to the remote UI client device 700 in response to a request from the remote UI client device 700. Protocols via which the UI resource transmitting unit 830 transmits a UI resource include XRT, RDP, and HTTP. However, it will be obvious to one of ordinary skill in the art that other protocols may also be used.
A capability matching unit (not shown) transmits capability information with respect to a UI resource to the remote UI client device 700. Capability information includes resolution information and codec information with respect to a UI resource. The remote UI client device 700 may obtain a UI resource that can be processed by the remote UI client device 700 with reference to capability information obtained by the capability matching unit.
Meanwhile, if a device (e.g., an UPnP control point device) acting as a negotiator between the remote UI server device 800 and the remote UI client device 700 exists, the capability matching unit transmits capability information with respect to a UI resource to the negotiating device. In this case, the capability matching unit obtains capability information negotiated between the remote UI server device 800 and the remote UI client device 700 from the negotiating device. The UI resource transmitting unit 830 may transmit a UI resource that can be processed by the remote UI client device 700 with reference to the negotiated capability information obtained by the capability matching unit.
Meanwhile, an event message may be composed according to any of various home network standards, including universal plug and play (UPnP) Remote UI and consumer electronics association (CEA) 2014 standards, and is received via a unicast transmission or a multicast transmission.
The control command receiving unit 840 receives external inputs of control commands from the remote UI client device 700. The control command receiving unit 840 may use either the same session as a session for transmitting a UI resource or an asynchronous session independent from the session for transmitting the UI resource. An asynchronous session may be embodied by using AJAX. However, it will be obvious to one of ordinary skill in the art that an asynchronous session may be embodied by using any of various other methods. The control commands include confirm commands, playback commands, stop commands, reply commands, forward commands, delete commands, save commands, and move commands, but are not limited thereto. The control command inputting unit 740 receives the external inputs of message control commands via a web page or an application with a message control command inputting interface.
A control unit 860 executes control functions related to corresponding messages.
In the case where a control command received by the control command receiving unit 840 is either a control command to confirm a message or a control message to play back a message, the UI resource transmitting unit 830 transmits a UI resource providing a UI, which displays the complete content of the message, to the remote UI client device 700.
In the case where a control command received by the control command receiving unit 840 is a control command to reply to the message, the UI resource transmitting unit 830 transmits a UI resource providing a UI, which receives external inputs of texts and a control command for transmitting a message, to the remote UI client device 700.
Meanwhile, the texts may include commonly used phrases. Thus, the UI resource transmitting unit 830 transmits a UI resource providing a UI, which displays a list of commonly used phrases and receives inputs of commands for selecting commonly used phrases, to the remote UI client device 700.
In the case where a control command received by the control command receiving unit 840 is a control command to forward the message, the UI resource transmitting unit 830 transmits a UI resource providing a UI, which displays a list of telephone numbers and associated users of the telephone numbers, and receives external inputs of commands for selecting telephone numbers, to the remote UI client device 700.
In operation 910, in the case where the remote UI server device 800 receives a message, the remote UI client device 700 receives an event message, which includes a URL for accessing a UI resource providing a UI notifying the receipt of the message, from a remote UI server device 800.
In operation 920, the remote UI client device 700 obtains a UI resource from the remote UI server device 800 by using a URL.
In operation 930, the remote UI client device 700 receives external inputs of message control commands via a UI resource. Message control commands include confirm commands, playback commands, stop commands, reply commands, forward commands, delete commands, save commands, and move commands, but are not limited thereto. The remote UI client device 700 receives the external inputs of message control commands via a web page or an application with a message control command inputting interface.
In operation 940, the remote UI client device 700 transmits an externally input control command to the remote UI server device 800 by using a UI resource.
In the operation 940, in the case where a control command transmitted by the remote UI client device 700 is either a control command to confirm a message or a control message to play back a message, the remote UI client device 700 obtains a UI resource providing a UI, which displays the complete content of the message, from the remote UI server device 800 (not shown in
In the operation 940, in the case where a control command transmitted by the remote UI client device 700 is a control command to reply to the message, the remote UT client device 700 obtains a UI resource providing a UI, which receives external inputs of texts and a control command for transmitting a message, from the remote UI server device 800 (not shown in
Meanwhile, the texts may include commonly used phrases. Thus, the remote UI client device 700 obtains a UI resource providing a UT, which displays a list of commonly used phrases and receives inputs of commands for selecting commonly used phrases, from the remote UI server device 800 (not shown in
In the operation 940, in the case where a control command transmitted by the remote UI client device 700 is a control command to forward the message, the remote UI client device 700 obtains a UI resource providing a UI, which displays a list of telephone numbers, and associated users of the telephone numbers, and receives external inputs of commands for selecting telephone numbers, from the remote UI server device 800 (not shown in
In an operation 1010, the remote UI server device 800 receives messages from a message transmitting device via a cellular network, including a GSM network and a CDMA network. Examples of the messages received by the remote UI server device 800 include MMS messages and SMS messages, but are not limited thereto.
In an operation 1020, the remote UI server device 800 transmits an event message, which includes a URL for accessing a UI resource providing a UI notifying the receipt of a message, to a remote UI client device 700.
In an operation 1030, the remote UI server device 800 transmits a UI resource to the remote UI client device 700 in response to a request from the remote UI client device 700.
In an operation 1040, the remote UI server device 800 receives external inputs of control commands from the remote UI client device 700. The control commands include confirm commands, playback commands, stop commands, reply commands, forward commands, delete commands, save commands, and move commands, but are not limited thereto.
In an operation 1050, the remote UI server device 800 executes control functions related to corresponding messages.
In the operation 1040, in the case where a control command received by the remote UI server device 800 is either a control command to confirm a message or a control message to play back a message, the remote UI server device 800 transmits a UI resource providing a UI, which displays the complete content of the message, to the remote UI client device 700 (not shown in
In the operation 1040, in the case where a control command received by the remote UI server device 800 is a control command to reply to the message, the remote UI server device 800 transmits a UI resource providing a UI, which receives external inputs of texts and a control command for transmitting a message, to the remote UI client device 700 (not shown in
Meanwhile, the texts may include commonly used phrases. Thus, the remote UI server device 800 transmits a UI resource providing a UI, which displays a list of commonly used phrases and receives inputs of commands for selecting commonly used phrases, to the remote UI client device 700.
In the operation 1040, in case where a control command received by the remote UI server device 800 is a control command to forward the message, the remote UI server device 800 transmits a UI resource providing a UI, which displays a list of telephone numbers, and associated users of the telephone numbers, and receives external inputs of commands for selecting telephone numbers, to the remote UI client device 700.
While the exemplary embodiments have been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the exemplary embodiments as defined by the following claims.
For example, each of the remote UI client device 700 and the remote UI server device 800 according to exemplary embodiments may include a bus coupled with each of components, at least one processor coupled with the bus, and a memory, which is coupled to the bus to store commands, received messages, or generated messages and is coupled with the at least one processor to perform the commands described above.
The exemplary embodiments may be written as computer programs and can be implemented in general-use digital computers that execute the programs using a computer readable recording medium. Examples of the computer readable recording medium include magnetic storage media (e.g., ROM, floppy disks, hard disks, etc.), and optical recording media (e.g., CD-ROMs, or DVDs).
The invention may also be embodied in other exemplary embodiments as computer readable codes on a computer readable transmission medium which may include carrier waves (such as data transmission through the Internet).
Further, expressions such as at least one of, when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list.
Number | Date | Country | Kind |
---|---|---|---|
10-2009-0109695 | Nov 2009 | KR | national |
This is a continuation of U.S. application Ser. No. 17/200,054, filed Mar. 12, 2021, which is a continuation of U.S. application Ser. No. 16/585,334 filed Sep. 27, 2019, now U.S. Pat. No. 10,951,432, issued Mar. 16, 2021, which is a continuation of U.S. application Ser. No. 14/819,094 filed Aug. 5, 2015, now U.S. Pat. No. 10,454,701, issued Oct. 22, 2019, which is a continuation application of U.S. application Ser. No. 12/770,226 filed Apr. 29, 2010, which claims priority from Korean Patent Application No. 10-2009-0109695, filed Nov. 13, 2009, in the Korean Intellectual Property Office. The disclosures of the above-named applications are incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5880732 | Tryding | Mar 1999 | A |
5959543 | LaPorta et al. | Sep 1999 | A |
5960367 | Kita | Sep 1999 | A |
5974300 | LaPorta et al. | Oct 1999 | A |
6014429 | LaPorta et al. | Jan 2000 | A |
6044134 | De La Huerga | Mar 2000 | A |
6181326 | Takahashi | Jan 2001 | B1 |
6292668 | Alanara | Sep 2001 | B1 |
6529744 | Birkler | Mar 2003 | B1 |
6724872 | Moore | Apr 2004 | B1 |
6870910 | Armstrong | Mar 2005 | B1 |
7010312 | Zechlin | Mar 2006 | B1 |
7039393 | Kite | May 2006 | B1 |
7061470 | Sharp | Jun 2006 | B1 |
7076057 | Sharp | Jul 2006 | B1 |
7092370 | Jiang | Aug 2006 | B2 |
7120474 | Sharp | Oct 2006 | B1 |
7215975 | Sharp | May 2007 | B1 |
7251318 | Henderson | Jul 2007 | B1 |
7313389 | Sharp et al. | Dec 2007 | B1 |
7328031 | Kraft | Feb 2008 | B2 |
7437179 | Sharp | Oct 2008 | B1 |
7487248 | Moran | Feb 2009 | B2 |
7519681 | Edwards et al. | Apr 2009 | B2 |
7571458 | Eyal | Aug 2009 | B1 |
7577910 | Husemann et al. | Aug 2009 | B1 |
7605801 | Sharp | Oct 2009 | B1 |
7627642 | Horstmann | Dec 2009 | B1 |
7689649 | Heikes | Mar 2010 | B2 |
7793233 | Sellers et al. | Sep 2010 | B1 |
7822188 | Kirchhoff | Oct 2010 | B1 |
7889185 | Blumenberg et al. | Feb 2011 | B2 |
7912972 | Park et al. | Mar 2011 | B2 |
8089503 | Bruce et al. | Jan 2012 | B2 |
8150387 | Klein et al. | Apr 2012 | B2 |
8181226 | Lohr | May 2012 | B2 |
8185139 | Mangal | May 2012 | B1 |
8195243 | Kim et al. | Jun 2012 | B2 |
8201196 | Michael et al. | Jun 2012 | B2 |
8243636 | Myllynen et al. | Aug 2012 | B2 |
8266664 | Qiu et al. | Sep 2012 | B2 |
8295865 | Kirchhoff et al. | Oct 2012 | B1 |
8316308 | Sherman et al. | Nov 2012 | B2 |
8332475 | Rosen | Dec 2012 | B2 |
8341681 | Walter et al. | Dec 2012 | B2 |
8350887 | Bruce et al. | Jan 2013 | B2 |
8352544 | Fang et al. | Jan 2013 | B2 |
8359014 | Olincy et al. | Jan 2013 | B2 |
8385975 | Forutanpour et al. | Feb 2013 | B2 |
8498657 | Delker et al. | Jul 2013 | B1 |
8504637 | Kim et al. | Aug 2013 | B2 |
8543161 | Spalink | Sep 2013 | B2 |
8543927 | McKinley | Sep 2013 | B1 |
8626829 | Franco | Jan 2014 | B2 |
8630625 | Bi et al. | Jan 2014 | B2 |
8738047 | Choi et al. | May 2014 | B2 |
8751938 | Conley | Jun 2014 | B2 |
8813112 | Cibula et al. | Aug 2014 | B1 |
8874677 | Rosen | Oct 2014 | B2 |
8971860 | Olincy et al. | Mar 2015 | B1 |
8977255 | Freeman et al. | Mar 2015 | B2 |
8983551 | Worick | Mar 2015 | B2 |
9071945 | Rubin et al. | Jun 2015 | B1 |
9100807 | Rosen | Aug 2015 | B2 |
9154606 | Tseng et al. | Oct 2015 | B2 |
9176651 | Schubert et al. | Nov 2015 | B2 |
9185212 | Soo et al. | Nov 2015 | B2 |
9204423 | Kim et al. | Dec 2015 | B2 |
9225524 | Singh et al. | Dec 2015 | B2 |
9225540 | Jung et al. | Dec 2015 | B2 |
9285968 | Schubert et al. | Mar 2016 | B2 |
9577968 | Rosen | Feb 2017 | B2 |
9614809 | Rosen | Apr 2017 | B2 |
9620001 | Brunolli | Apr 2017 | B2 |
9628432 | Rosen et al. | Apr 2017 | B2 |
9665242 | Kim | May 2017 | B2 |
9686145 | Sherman et al. | Jun 2017 | B2 |
9692865 | Youn et al. | Jun 2017 | B2 |
9733804 | Huang et al. | Aug 2017 | B2 |
9756170 | Liu et al. | Sep 2017 | B2 |
10354518 | Brunolli | Jul 2019 | B2 |
10454701 | Kim et al. | Oct 2019 | B2 |
20010031633 | Tuomela et al. | Oct 2001 | A1 |
20010043514 | Kita | Nov 2001 | A1 |
20020115478 | Fujisawa et al. | Aug 2002 | A1 |
20020144273 | Reto | Oct 2002 | A1 |
20030043787 | Emerson, III | Mar 2003 | A1 |
20030048381 | Glatt | Mar 2003 | A1 |
20030051083 | Striemer | Mar 2003 | A1 |
20030064716 | Gailey | Apr 2003 | A1 |
20030095521 | Haller et al. | May 2003 | A1 |
20030103088 | Dresti et al. | Jun 2003 | A1 |
20030123634 | Chee | Jul 2003 | A1 |
20030140343 | Falvo et al. | Jul 2003 | A1 |
20030154256 | Hadano et al. | Aug 2003 | A1 |
20030154446 | Constant | Aug 2003 | A1 |
20030195814 | Striemer | Oct 2003 | A1 |
20030226143 | Michael et al. | Dec 2003 | A1 |
20030232593 | Wahlroos et al. | Dec 2003 | A1 |
20040075698 | Gao et al. | Apr 2004 | A1 |
20040103032 | Maggio | May 2004 | A1 |
20040117821 | Karaoguz et al. | Jun 2004 | A1 |
20040130580 | Howard et al. | Jul 2004 | A1 |
20040130581 | Howard et al. | Jul 2004 | A1 |
20040185915 | Ihara | Sep 2004 | A1 |
20040203794 | Brown et al. | Oct 2004 | A1 |
20040209614 | Bright et al. | Oct 2004 | A1 |
20040214568 | Anderson | Oct 2004 | A1 |
20040230659 | Chase | Nov 2004 | A1 |
20050123118 | Terry | Jun 2005 | A1 |
20050153729 | Logan et al. | Jul 2005 | A1 |
20050163108 | Moore et al. | Jul 2005 | A1 |
20050170869 | Slemmer et al. | Aug 2005 | A1 |
20050221771 | Himeno | Oct 2005 | A1 |
20050222933 | Wesby | Oct 2005 | A1 |
20050228887 | Wang et al. | Oct 2005 | A1 |
20050237308 | Autio et al. | Oct 2005 | A1 |
20050261034 | Punaganti et al. | Nov 2005 | A1 |
20050266793 | Grossman et al. | Dec 2005 | A1 |
20050268003 | Wang et al. | Dec 2005 | A1 |
20050272408 | Wilkes-Gibbs | Dec 2005 | A1 |
20050278750 | Grossman et al. | Dec 2005 | A1 |
20050285934 | Carter | Dec 2005 | A1 |
20060009243 | Dahan et al. | Jan 2006 | A1 |
20060026088 | Grossman et al. | Feb 2006 | A1 |
20060028582 | Zahn | Feb 2006 | A1 |
20060036672 | Cha et al. | Feb 2006 | A1 |
20060041615 | Blank et al. | Feb 2006 | A1 |
20060062172 | Grossman et al. | Mar 2006 | A1 |
20060073816 | Kim et al. | Apr 2006 | A1 |
20060080704 | Le Huerou et al. | Apr 2006 | A1 |
20060092037 | Neogi et al. | May 2006 | A1 |
20060098634 | Umemoto et al. | May 2006 | A1 |
20060098650 | Beninato et al. | May 2006 | A1 |
20060149818 | Odell et al. | Jun 2006 | A1 |
20060165092 | Wilson et al. | Jul 2006 | A1 |
20060179118 | Stirbu | Aug 2006 | A1 |
20060206833 | Capper | Sep 2006 | A1 |
20060212519 | Kelly et al. | Sep 2006 | A1 |
20060225108 | Tabassi et al. | Oct 2006 | A1 |
20060253330 | Maggio et al. | Nov 2006 | A1 |
20060257840 | Risch | Nov 2006 | A1 |
20070026798 | Hoogstra | Feb 2007 | A1 |
20070042812 | Basir | Feb 2007 | A1 |
20070060054 | Romesburg | Mar 2007 | A1 |
20070079345 | McEnroe | Apr 2007 | A1 |
20070080931 | Chen et al. | Apr 2007 | A1 |
20070080933 | Chen et al. | Apr 2007 | A1 |
20070080934 | Chen et al. | Apr 2007 | A1 |
20070087790 | Worick | Apr 2007 | A1 |
20070089055 | Ko et al. | Apr 2007 | A1 |
20070089158 | Clark | Apr 2007 | A1 |
20070100948 | Adams et al. | May 2007 | A1 |
20070162930 | Mickle et al. | Jul 2007 | A1 |
20070165554 | Jefferson et al. | Jul 2007 | A1 |
20070207782 | Tran | Sep 2007 | A1 |
20070236613 | Foss | Oct 2007 | A1 |
20070236615 | Tanaka et al. | Oct 2007 | A1 |
20070265006 | Washok | Nov 2007 | A1 |
20070281759 | Choi | Dec 2007 | A1 |
20070288576 | Illg | Dec 2007 | A1 |
20070293206 | Lund | Dec 2007 | A1 |
20070298770 | Lee | Dec 2007 | A1 |
20080014869 | Demirbasa et al. | Jan 2008 | A1 |
20080034081 | Marshall et al. | Feb 2008 | A1 |
20080052347 | Jung et al. | Feb 2008 | A1 |
20080077468 | Raskin | Mar 2008 | A1 |
20080085675 | Rao | Apr 2008 | A1 |
20080092199 | McCarthy et al. | Apr 2008 | A1 |
20080114845 | Rao | May 2008 | A1 |
20080133671 | Kalaboukis | Jun 2008 | A1 |
20080147803 | Krzyzanowski | Jun 2008 | A1 |
20080180228 | Wakefield et al. | Jul 2008 | A1 |
20080232336 | Elkady et al. | Sep 2008 | A1 |
20080233932 | Sapp | Sep 2008 | A1 |
20080244681 | Gossweiler et al. | Oct 2008 | A1 |
20080246733 | Henty | Oct 2008 | A1 |
20080259829 | Rosenblatt | Oct 2008 | A1 |
20080261564 | Logan | Oct 2008 | A1 |
20080263158 | Del Cacho | Oct 2008 | A1 |
20080274743 | Kim | Nov 2008 | A1 |
20080281926 | Walter et al. | Nov 2008 | A1 |
20080288600 | Clark | Nov 2008 | A1 |
20080288618 | Vardi et al. | Nov 2008 | A1 |
20080305742 | Basir | Dec 2008 | A1 |
20080305815 | McDonough | Dec 2008 | A1 |
20080307315 | Sherman et al. | Dec 2008 | A1 |
20080313050 | Basir | Dec 2008 | A1 |
20090037385 | Min et al. | Feb 2009 | A1 |
20090044216 | McNicoll | Feb 2009 | A1 |
20090044252 | Kashima | Feb 2009 | A1 |
20090051649 | Rondel | Feb 2009 | A1 |
20090061943 | Kamgaing-Kouam | Mar 2009 | A1 |
20090088207 | Sweeney | Apr 2009 | A1 |
20090125598 | Sun | May 2009 | A1 |
20090138564 | Beddus | May 2009 | A1 |
20090144378 | Cassanova et al. | Jun 2009 | A1 |
20090144379 | Cassanova et al. | Jun 2009 | A1 |
20090150903 | Cassanova et al. | Jun 2009 | A1 |
20090156170 | Rossano et al. | Jun 2009 | A1 |
20090157886 | Lee et al. | Jun 2009 | A1 |
20090158136 | Rossano et al. | Jun 2009 | A1 |
20090160694 | Di Flora | Jun 2009 | A1 |
20090164914 | Chen | Jun 2009 | A1 |
20090178078 | Daigle et al. | Jul 2009 | A1 |
20090187620 | Kisel et al. | Jul 2009 | A1 |
20090189971 | Yoder | Jul 2009 | A1 |
20090217365 | Daigle | Aug 2009 | A1 |
20090235317 | Igarashi | Sep 2009 | A1 |
20090239528 | Ryley et al. | Sep 2009 | A1 |
20090248883 | Suryanarayana | Oct 2009 | A1 |
20090248913 | Salokannel | Oct 2009 | A1 |
20090251526 | Book | Oct 2009 | A1 |
20090262088 | Moll-Carrillo et al. | Oct 2009 | A1 |
20090264070 | Lim | Oct 2009 | A1 |
20090264140 | Bain | Oct 2009 | A1 |
20090289917 | Saunders | Nov 2009 | A1 |
20090325609 | Rosen | Dec 2009 | A1 |
20090327910 | Black et al. | Dec 2009 | A1 |
20090328118 | Ravishankar et al. | Dec 2009 | A1 |
20100035594 | Vendrow | Feb 2010 | A1 |
20100035640 | Lew et al. | Feb 2010 | A1 |
20100041424 | Osborn | Feb 2010 | A1 |
20100042692 | Irwin et al. | Feb 2010 | A1 |
20100057882 | Haartsen et al. | Mar 2010 | A1 |
20100064333 | Blackburn et al. | Mar 2010 | A1 |
20100066677 | Garrett et al. | Mar 2010 | A1 |
20100071053 | Ansari et al. | Mar 2010 | A1 |
20100087172 | Klassen et al. | Apr 2010 | A1 |
20100095332 | Gran et al. | Apr 2010 | A1 |
20100097239 | Campbell | Apr 2010 | A1 |
20100138503 | Ishikawa | Jun 2010 | A1 |
20100159967 | Pounds | Jun 2010 | A1 |
20100179991 | Lorch et al. | Jul 2010 | A1 |
20100182994 | Rahman et al. | Jul 2010 | A1 |
20100205539 | Gestsson | Aug 2010 | A1 |
20100222102 | Rodriguez | Sep 2010 | A1 |
20100227631 | Bolton et al. | Sep 2010 | A1 |
20100251134 | Van Seggelen | Sep 2010 | A1 |
20100268828 | Pahlavan et al. | Oct 2010 | A1 |
20100269057 | Pahlavan et al. | Oct 2010 | A1 |
20100278345 | Alsina et al. | Nov 2010 | A1 |
20100285775 | Klein et al. | Nov 2010 | A1 |
20100287241 | Swanburg et al. | Nov 2010 | A1 |
20100293462 | Bull et al. | Nov 2010 | A1 |
20100298012 | Damarla | Nov 2010 | A1 |
20100311443 | Abuelsaad | Dec 2010 | A1 |
20100312769 | Bailey et al. | Dec 2010 | A1 |
20100317332 | Bathiche et al. | Dec 2010 | A1 |
20100330975 | Basir | Dec 2010 | A1 |
20100332984 | Tzruya | Dec 2010 | A1 |
20110040838 | Damarla | Feb 2011 | A1 |
20110047487 | DeWeese et al. | Feb 2011 | A1 |
20110059769 | Brunolli | Mar 2011 | A1 |
20110067059 | Johnston et al. | Mar 2011 | A1 |
20110072477 | Foti et al. | Mar 2011 | A1 |
20110074794 | Felt et al. | Mar 2011 | A1 |
20110081007 | Bar-Yoav | Apr 2011 | A1 |
20110111741 | Connors et al. | May 2011 | A1 |
20110151851 | Foley | Jun 2011 | A1 |
20110167359 | Weisberg | Jul 2011 | A1 |
20110179129 | McKissick et al. | Jul 2011 | A1 |
20110238766 | Lew et al. | Sep 2011 | A1 |
20110265003 | Schubert et al. | Oct 2011 | A1 |
20110314134 | Foti | Dec 2011 | A1 |
20120021784 | Meunier et al. | Jan 2012 | A1 |
20120072996 | Svendsen et al. | Mar 2012 | A1 |
20120077518 | Logan | Mar 2012 | A1 |
20120159546 | Klein et al. | Jun 2012 | A1 |
20120274508 | Brown | Nov 2012 | A1 |
20120315880 | Peitrow | Dec 2012 | A1 |
20130051538 | Qiu et al. | Feb 2013 | A1 |
20130070044 | Naidoo et al. | Mar 2013 | A1 |
20130080553 | Rosen | Mar 2013 | A1 |
20130110955 | Brady et al. | May 2013 | A1 |
20130150004 | Rosen | Jun 2013 | A1 |
20130238165 | Garrett et al. | Sep 2013 | A1 |
20130244708 | Andrus et al. | Sep 2013 | A1 |
20130252646 | Jang | Sep 2013 | A1 |
20140033059 | Schubert et al. | Jan 2014 | A1 |
20140057610 | Olincy et al. | Feb 2014 | A1 |
20140208223 | Schubert et al. | Jul 2014 | A1 |
20140267020 | Ishibashi | Sep 2014 | A1 |
20140359003 | Sullad et al. | Dec 2014 | A1 |
20140365362 | Dua | Dec 2014 | A1 |
20140378175 | Rosen | Dec 2014 | A1 |
20140379794 | Rosen | Dec 2014 | A1 |
20150040007 | Schubert et al. | Feb 2015 | A1 |
20150061862 | Lee | Mar 2015 | A1 |
20150143262 | Norwood et al. | May 2015 | A1 |
20150371306 | Besson | Dec 2015 | A1 |
20160036742 | Rosen | Feb 2016 | A1 |
20160036743 | Rosen | Feb 2016 | A1 |
20160036744 | Rosen | Feb 2016 | A1 |
20160036745 | Rosen | Feb 2016 | A1 |
20160036746 | Rosen | Feb 2016 | A1 |
20160269350 | Rosen | Sep 2016 | A1 |
20160330154 | Rosen | Nov 2016 | A1 |
20170041273 | Marcellino | Feb 2017 | A1 |
20170213452 | Brunolli | Jul 2017 | A1 |
20170235477 | Sherman et al. | Aug 2017 | A1 |
20170243195 | Aug 2017 | A1 | |
20170289810 | O'Meara et al. | Oct 2017 | A1 |
Number | Date | Country |
---|---|---|
1842103 | Oct 2006 | CN |
1 069 500 | Jan 2001 | EP |
2474168 | Jul 2012 | EP |
3082345 | Oct 2016 | EP |
09-152924 | Jun 1997 | JP |
9325992 | Dec 1997 | JP |
2001-100972 | Apr 2001 | JP |
2002-175170 | Jun 2002 | JP |
2002-535932 | Oct 2002 | JP |
2002328872 | Nov 2002 | JP |
2002344568 | Nov 2002 | JP |
2003-234783 | Aug 2003 | JP |
2008242827 | Oct 2008 | JP |
2010-530572 | Sep 2010 | JP |
2011514697 | May 2011 | JP |
1020060015378 | Feb 2006 | KR |
1020080038726 | May 2008 | KR |
2007023494 | Mar 2007 | WO |
2008148222 | Dec 2008 | WO |
2009008578 | Jan 2009 | WO |
2009092511 | Jul 2009 | WO |
2011029098 | Mar 2011 | WO |
Entry |
---|
Communication dated Jan. 9, 2018, from the Japanese Patent Office in counterpart application No. 2017-020166. |
Communication dated Feb. 13, 2018, from the State Intellectual Property Office of People's Republic of China in counterpart Application No. 201510479230.5. |
Communication dated Jul. 3, 2017, from the European Patent Office in counterpart European Application No. 16191610.1. |
Communication dated Dec. 2, 2016 issued by European Patent Office in counterpart European Patent Application No. 16191610.1. |
Communication dated Dec. 15, 2016 issued by European Patent Office in counterpart European Patent Application No. 16 191 610.1. |
Communication dated Sep. 6, 2016, issued by the Japanese Patent Office in counterpart Japanese Application No. 2015-160252. |
Communication dated Feb. 18, 2016 issued by the Korean Intellectual Property Office in counterpart Korean Patent Application No. 10-2009-0109695. |
“CEA Standard. Web-Based Protocol and Framework for Remote User Interface on UPNP Networks and the Internet (WEB4CE)”; Consumer Electronics Association; XP002431656; Jul. 2007; 194 pgs. |
Communication dated Dec. 6, 2012, issued by the European Patent Office in counterpart European Patent Application No. 10830116.9. |
Communication dated May 27, 2014 issued by the Japanese Patent Office in counterpart Japanese Patent Application No. 2010-235482. |
Communication dated Nov. 15, 2014 issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Patent Application No. 201010548480.7. |
Communication dated Nov. 25, 2014 issued by the Japanese Patent Office in counterpart Japanese Patent Application No. 2010-235482. |
Communication, dated Mar. 12, 2014, issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Patent Application No. 201010548480.7. |
International Search Report dated Jun. 27, 2011 from the International Searching Authority in counterpart international application No. PCT/KR2010/007170. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Apr. 12, 2017. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Aug. 30, 2016. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Oct. 20, 2015. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Apr. 7, 2015. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Jan. 10, 2014. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Aug. 14, 2012. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Nov. 17, 2016. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Apr. 5, 2016. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Jun. 20, 2014. |
Office Action issued in parent U.S. Appl. No. 12/770,226 dated Jan. 25, 2013. |
Non Final Office Action issued in U.S. Appl. No. 14/819,094 dated Nov. 7, 2016. |
Non Final Office Action issued in U.S. Appl. No. 14/819,094 dated Nov. 28, 2017. |
Non Final Office Action issued in U.S. Appl. No. 14/819,094 dated Nov. 3, 2015. |
Office Action issued in U.S. Appl. No. 14/819,094 dated Nov. 15, 2018. |
Office Action issued in U.S. Appl. No. 14/819,094 dated Apr. 18, 2016. |
Office Action issued in U.S. Appl. No. 14/819,094 dated Apr. 3, 2017. |
Office Action issued in U.S. Appl. No. 14/819,094 dated May 14. 2018. |
Notice of Allowance issued in U.S. Appl. No. 14/819,094 dated Jun. 12, 2019. |
Corrected Notice of Allowability issued in U.S. Appl. No. 14/819,094 dated Jun. 28, 2019. |
Japanese Office Action dated May 27, 2014 in the Japanese Patent Application No. 2010-235482. |
Notice of Allowance issued in U.S. Appl. No. 16/585,334 dated Nov. 10, 2020. |
Number | Date | Country | |
---|---|---|---|
20220321377 A1 | Oct 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17200054 | Mar 2021 | US |
Child | 17848449 | US | |
Parent | 16585334 | Sep 2019 | US |
Child | 17200054 | US | |
Parent | 14819094 | Aug 2015 | US |
Child | 16585334 | US | |
Parent | 12770226 | Apr 2010 | US |
Child | 14819094 | US |