The subject disclosure relates to a method and apparatus for controlling a media device.
Media communication systems such as interactive television systems can deliver media content to media processors such as set-top boxes. Generally, media content can be broadcast by these systems and delivered according to the type of services users have subscribed to. In interactive media communication systems, users can also request services on demand. Portable media devices such as mobile phones or media players can be adapted to communicate with media processors over a wireless medium. The combined services of portable and fixed media devices can provide users a rich environment for utilizing multimedia services.
Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
The subject disclosure describes, among other things, illustrative embodiments for controlling a media center by way of a portable communication device executing a web server executed by the portable communication device. Other embodiments are included in the subject disclosure.
One embodiment of the subject disclosure includes a portable communication device comprising a memory to store instructions, and a processor coupled to the memory. Upon execution of the instructions the processor can perform operations comprising detecting a wireless network, transmitting a query message to the wireless network to identify devices communicatively coupled to the wireless network, receiving a response message by way of the wireless network, and detecting according to the response message that a media device is communicatively coupled to the wireless network. The operations can further include submitting to a remote server a request for a key to enable communications with the media device, receiving the key from the remote server, monitoring an event associated with use of the media device, and detecting the event. The operations can also include generating a command according to the key, transmitting to the media device the command, where the command directs the media device to request web page information from a web server executed by the processor, receiving a request for web page information from the media device responsive to transmitting the command, and transmitting the web page information to the media device by way of the web server responsive to receiving the request.
One embodiment of the subject disclosure includes a method for transmitting a query message to identify devices communicatively coupled to a communication network, receiving a response message by way of the communication network, and detecting according to the response message that a media device is communicatively coupled to the communication network. The method can also include submitting to a remote server a request for a key to enable communications with the media device, receiving the key from the remote server, and detecting an event associated with use of the media device, generating a command responsive to detecting the event. The method can further include transmitting to the media device the command, where the command directs the media device to request web page information from a web server, receiving a request for the web page information from the media device, and transmitting the web page information to the media device by way of the web server.
One embodiment of the subject disclosure includes a computer-readable storage device, comprising computer instructions. A processor that executes the instructions can perform operations including detecting a communication network, broadcasting a query message by way of the communication network, receiving a response message from the communication network, and detecting from the response message that a media device is communicatively coupled to the communication network. The operations can also include receiving a key from a remote server to enable communications with the media device, detecting an event requiring use of the media device, generating a command responsive to the event, transmitting to the media device the command to direct the media device to request information from a web server executed by the processor, receiving from the media device a request for information to be provided by the web server, and transmitting to the media device by way of the web server the information requested.
The request sent by the portable communication device 104 to the remote server 112 can include an identity of the media device such as, for example, a serial number, a media access control address, a globally unique identifier, or some other identifier of the media device that is recognizable to the server 112. The server 112 can utilize the identifier of the media device to index through the database 114 to retrieve a key associated with the media device if the identifier is recognized. The request sent by the portable communication device 104 can also include authentication information to verify that the portable communication device 104 is authorized to request a key for communicating with the media device. The server 112 can use the authentication information to retrieve subscriber account information from database 114 to identify which services the portable communication device 104 is authorized to use, and thereby determine whether the portable communication device 104 is authorized to communicate with the media device and utilize its resources.
Once the server 112 has authorized the portable communication device 104 and has found a key associated with the media device based on the supplied identity of the media device, the server 112 transmits the key to the portable communication device 104 over a secure channel using for example secure socket layer (SSL) encryption, which the portable communication device 104 receives in step 214. With the key, the operating system 101 of the portable communication device 104 can now engage in communications with the media device.
At step 216 the operating system 101 of the portable communication device 104 can prompt a user to configure services with the newly detected media device.
For a media device such as a set top box, the portable communication device 104 can present a number of services which can be enabled by a user with a slideable On/Off switch for interacting with the media device. For example, in section 304, a user can enable a caller ID feature between the portable communication device 104 and the media device by sliding the On/Off switch to the on position. The caller ID feature can be used during call processing. For example, when the operating system 101 of the portable communication device 104 detects an incoming call, and is aware that the media device is accessible and that the caller ID feature is enabled, the portable communication device 104 can submit to the media device a command including the key as will be described in steps 224-230 in order to cause the media device to present the caller ID of the caller at a presentation device such as display device 107 of
Referring back to
In section 310, the user can also enable finding the portable communication device 104 in the event the user cannot readily find the portable communication device 104. This option can be presented in section 109 of the presentation device 107. When this feature is selected with the remote control device 105, the media device can direct the portable communication device 104 to generate audible alerts to assist the user in locating the portable communication device 104. In section 310, the user can further enable answering calls at the portable communication device 104. This option is also shown in section 109 of the presentation device 107, which is selectable with the remote control device 105.
In section 314, the user can also enable an intercom feature. This feature allows the portable communication device 104 to broadcast a user's voice to more than one media device detected by the portable communication device 104, or selectively at a media device specified by the user (e.g., at a set-top box in a child's room). In section 314, the user can also enable parental control features. This feature allows the portable communication device 104 to control media content presented by the media device on a per user basis. For example, parental controls can establish for a particular user of the media device time limits for use of the media device, limit media content presentations to specific ratings (e.g., G rated content only), limit media content to specific shows, and so on. In section 316, the user can enable a voicemail redirection feature. For example, when an incoming call is detected, GUI section 109 of the display device 107 of
The selectable features shown in the GUI of
Referring back to
As a result of these embodiments, the next time the portable communication device 104 enters a communication range of the wireless network, the operating system 101 of the portable communication device 104 can recognize known devices in step 208, and proceed to step 210 where it retrieves a profile for each media device detected in the network. In addition to retrieving a profile for each media device, the operating system 101 of the portable communication device 104 can present an indicator 301 as shown in
Once all media devices have been discovered and configured by way of steps 202 through 220, the operating system 101 of the portable communication device 104 can proceed to step 222 where it monitors user initiated events or events initiated without user intervention. The operating system 101 can perform many functions, among them, call processing, user input processing, event management processing, and so on. A user-initiated event can be an event caused by user input provided to the portable communication device 104 by way of a user interface such as a keyboard or touch screen. A user initiated event can prompt, for example, an intercom session responsive to user input received by the portable communication device 104. The user input can be generated as a result of the user selecting an icon presented by a display of the portable communication device 104, which when selected invokes the intercom feature. A user-initiated event can also be invoked by way of the media device. For example, the remote control device 105 can be configured with custom buttons to initiate functions of the portable communication device 104. For instance, a user may request sending a text message to a targeted device.
An incoming call can be an instance of an event detected by the operating system 101 of the portable communication device 104 without user intervention. Similarly, an incoming text message can be an event detected by the operating system 101 of the portable communication device 104 without user intervention. Other similar events not involving user intervention can be monitored by the operating system 101 of the portable communication device 104 in step 222.
When an event is detected in step 222 by the operating system 101, the portable communication device 104 can proceed to step 224 where the operating system 101 generates a command responsive to the event, which it conveys to the media device. The command generated by the operating system 101 can, for example, include a uniform resource locator (URL) for selecting one of several web pages managed by a web server application 103 executed by the portable communication device 104. The web page can be preconfigured by the operating system 101 to include information associated with the detected incoming call, such as the caller ID. The operating system 101 can encrypt the command with the key of the media device for which the event is directed, and cause the portable communication device 104 to transmit the encrypted command to the media device to direct the media device to request the web page from the web server application 103 according to the URL generated by the operating system 101. Alternatively, the operating system 101 can transmit a command with the URL without encryption and provide the key in the transmitted command with the URL for authentication purposes. Upon receiving the encrypted (or unencrypted) command, the media device processes the command and determines from the command that it must retrieve the web page from the web server 103 according to the URL provided by the operating system 101. In one embodiment, the web page request generated by the media device can be encrypted with the key of the media device to maintain communications secure. In another embodiment, the URL request can be unencrypted.
Once the web server 103 of the portable communication device 104 receives the web page requested by the media device according to the URL in step 226, it retrieves the web page information and provides it to the media device. As noted earlier, the operating system 101 can configure the web page with the caller ID of the incoming call. The web page can present the caller ID along with selectable response options that are presented by the media device by way of the GUI 109. In step 228, the web server application 103 causes the portable communication device 104 to transmit the web page to the media device according to the URL provided by the media device.
To better understand what may be presented by way of GUI 109, suppose that the caller ID feature, the call response message feature, and the find phone feature are enabled by way of the GUI 300 shown in
Once the media device processes the HTML data and thereby presents GUI 109 at the presentation device 107, the media device can monitor at step 232 user input generated by the remote control device 105. For instance, upon a presentation of the caller ID via GUI 109, the user can choose to select via the remote control device 105 the “answer” option in GUI 109. The user can initiate this action by navigating in GUI 109 with up and down arrows and depressing an OK button of the remote control device 105 to select a desirable option. Once the media device detects user input at step 232, the media device can proceed to step 234 where it transmits the user input to the web server application 103 which in turn sends an event to the operating system 101 of the portable communication device 104. At step 236, the operating system 101 detects the selection of the answer call option. The operating system 101 then asserts the ring tone of the portable communication device 104 so that the user can locate the portable communication device 104 and thereby answer the incoming call.
Other functions can be executed by the operating system 101 of the portable communication device 104 when detecting events for sending media content (e.g., still pictures or video) to the media device for presentation at the presentation device 107, finding the portable communication device 104 by causing an assertion of the ring tone of the portable communication device 104, initiating the intercom feature in broadcast mode or specific to one of several media devices known to the portable communication device 104, and so on. The web server application 103 can be preloaded with a plurality web page templates that can be configured by the operating system 101 each time it detects and event. Once a web page is configured by the operating system 101, the operating system 101 can convey a URL to the media device as previously described above to enable the media device to present the web page at the presentation device 107 as GUI 109 with selectable options.
The aforementioned embodiments provide advantages for portable communication devices to detect media devices, to interact with media devices in a secure manner, and to present users automatic detection of media devices and options to configure such media devices with less effort than is required today. The above embodiments also enable service providers of media devices to control which portable communication devices are authorized to control the media devices by limiting the distribution of keys only to portable communication devices known to the service provider. Such knowledge can be based on the service provider offering media device services as well as portable communication device services in combination, which enables the service provider control access to both devices. Alternatively, the service provider can offer media device services, and broker agreements with distributors of portable communication devices that provide the service provider information to track portable communication devices authorized to use the media devices of the service provider. Other suitable arrangements can be used for implementing method 200 of
It should be noted that the web server application 103 referred to above can represent a hypertext transfer protocol (HTTP) web server application implemented in software, hardware or combinations thereof executed by a processor of the portable communication device 104. Other types of web server applications that can be used by the portable communication device 104.
The UI 404 can include a depressible or touch-sensitive keypad 408 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 400. The keypad 408 can be an integral part of a housing assembly of the communication device 400 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth. The keypad 408 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 404 can further include a display 410 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 400. In an embodiment where the display 410 is touch-sensitive, a portion or all of the keypad 408 can be presented by way of the display 410 with navigation features.
The display 410 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 400 can be adapted to present a user interface with graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The touch screen display 410 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 410 can be an integral part of the housing assembly of the communication device 400 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.
The UI 404 can also include an audio system 412 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high volume audio (such as speakerphone for hands free operation). The audio system 412 can further include a microphone for receiving audible signals of an end user. The audio system 412 can also be used for voice recognition applications. The UI 404 can further include an image sensor 413 such as a charged coupled device (CCD) camera for capturing still or moving images.
The power supply 414 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 400 to facilitate long-range or short-range portable applications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.
The location receiver 416 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 400 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 418 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 400 in three-dimensional space. The orientation sensor 420 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 400 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).
The communication device 400 can use the transceiver 402 to also determine a proximity to a cellular, WiFi, Bluetooth, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 406 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 400.
Other components not shown in
The communication device 400 as described herein can operate with more or less of the circuit components shown in
It will be appreciated that the communication device 400 can also represent other devices that can operate in communication system 100 of
It should be understood that devices described in the exemplary embodiments can be in communication with each other via various wireless and/or wired methodologies. The methodologies can be links that are described as coupled, connected and so forth, which can include unidirectional and/or bidirectional communication over wireless paths and/or wired paths that utilize one or more of various protocols or methodologies, where the coupling and/or connection can be direct (e.g., no intervening processing device) and/or indirect (e.g., an intermediary processing device such as a router).
The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet PC, a smart phone, a laptop computer, a desktop computer, a control system, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. It will be understood that a communication device of the subject disclosure includes broadly any electronic device that provides voice, video or data communication. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein.
The computer system 500 may include a processor (or controller) 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU, or both), a main memory 504 and a static memory 506, which communicate with each other via a bus 508. The computer system 500 may further include a display unit 510 (e.g., a liquid crystal display (LCD), a flat panel, or a solid state display. The computer system 500 may include an input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), a disk drive unit 516, a signal generation device 518 (e.g., a speaker or remote control) and a network interface device 520. In distributed environments, the embodiments described in the subject disclosure can be adapted to utilize multiple display units 510 controlled by two or more computer systems 500. In this configuration, presentations described by the subject disclosure may in part be shown in a first of the display units 510, while the remaining portion is presented in a second of the display units 510.
The disk drive unit 516 may include a tangible computer-readable storage medium 522 on which is stored one or more sets of instructions (e.g., software 524) embodying any one or more of the methods or functions described herein, including those methods illustrated above. The instructions 524 may also reside, completely or at least partially, within the main memory 504, the static memory 506, and/or within the processor 502 during execution thereof by the computer system 500. The main memory 504 and the processor 502 also may constitute tangible computer-readable storage media.
Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices that can likewise be constructed to implement the methods described herein. Application specific integrated circuits and programmable logic array can use downloadable instructions for executing state machines and/or circuit configurations to implement embodiments of the subject disclosure. Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations.
In accordance with various embodiments of the subject disclosure, the operations or methods described herein are intended for operation as software programs or instructions running on or executed by a computer processor or other computing device, and which may include other forms of instructions manifested as a state machine implemented with logic components in an application specific integrated circuit or field programmable array. Furthermore, software implementations (e.g., software programs, instructions, etc.) can include, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein. It is further noted that a computing device such as a processor, a controller, a state machine or other suitable device for executing instructions to perform operations or methods may perform such operations directly or indirectly by way of one or more intermediate devices directed by the computing device.
While the tangible computer-readable storage medium 622 is shown in an example embodiment to be a single medium, the term “tangible computer-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “tangible computer-readable storage medium” shall also be taken to include any non-transitory medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methods of the subject disclosure.
The term “tangible computer-readable storage medium” shall accordingly be taken to include, but not be limited to: solid-state memories such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories, a magneto-optical or optical medium such as a disk or tape, or other tangible media which can be used to store information. Accordingly, the disclosure is considered to include any one or more of a tangible computer-readable storage medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.
Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Each of the standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) represent examples of the state of the art. Such standards are from time-to-time superseded by faster or more efficient equivalents having essentially the same functions. Wireless standards for device detection (e.g., RFID), short-range communications (e.g., Bluetooth, WiFi, Zigbee), and long-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used by computer system 500.
The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Figures are also merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure.
The Abstract of the Disclosure is provided with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.
This application is a continuation of and claims priority to U.S. patent application Ser. No. 13/705,894, filed Dec. 5, 2012, now U.S. Patent Publication No. 2014/0155030. The contents of the foregoing is hereby incorporated by reference into this application as if set forth herein in full.
Number | Name | Date | Kind |
---|---|---|---|
5689559 | Park | Nov 1997 | A |
5761421 | Van Hoff | Jun 1998 | A |
6006303 | Barnaby et al. | Dec 1999 | A |
6167513 | Inoue et al. | Dec 2000 | A |
6463153 | Sako et al. | Oct 2002 | B1 |
6938156 | Wheeler et al. | Aug 2005 | B2 |
7016951 | Longworth et al. | Mar 2006 | B1 |
7127619 | Unger et al. | Oct 2006 | B2 |
7194438 | Sovio et al. | Mar 2007 | B2 |
7260597 | Hofrichter et al. | Aug 2007 | B1 |
7391866 | Fukami et al. | Jun 2008 | B2 |
7412727 | Kim | Aug 2008 | B2 |
7430753 | Gray | Sep 2008 | B2 |
7492899 | Qiao | Feb 2009 | B2 |
7590703 | Cashman et al. | Sep 2009 | B2 |
7634076 | Lee et al. | Dec 2009 | B2 |
7720986 | Savoor | May 2010 | B2 |
7756130 | Lee | Jul 2010 | B1 |
7761531 | Johnson et al. | Jul 2010 | B2 |
8015253 | Zapata et al. | Sep 2011 | B1 |
8108916 | Fink et al. | Jan 2012 | B2 |
8116808 | Amine | Feb 2012 | B2 |
8130738 | Chan et al. | Mar 2012 | B2 |
8169958 | Torres et al. | May 2012 | B2 |
8332905 | Jenkin et al. | Dec 2012 | B2 |
8392947 | Grannan et al. | Mar 2013 | B2 |
8396475 | Bonner | Mar 2013 | B1 |
8443420 | Brown et al. | May 2013 | B2 |
8989055 | Simpson et al. | Mar 2015 | B2 |
20020143773 | Spicer et al. | Oct 2002 | A1 |
20020157002 | Messerges et al. | Oct 2002 | A1 |
20020184301 | Parent | Dec 2002 | A1 |
20030026423 | Unger et al. | Feb 2003 | A1 |
20030051041 | Kalavade et al. | Mar 2003 | A1 |
20030095664 | Asano et al. | May 2003 | A1 |
20030190024 | Ju | Oct 2003 | A1 |
20040133794 | Kocher et al. | Jul 2004 | A1 |
20040215746 | McCanne et al. | Oct 2004 | A1 |
20040240668 | Bonan et al. | Dec 2004 | A1 |
20040253923 | Braley | Dec 2004 | A1 |
20050010637 | Dempski et al. | Jan 2005 | A1 |
20050044223 | Meyerson | Feb 2005 | A1 |
20050125819 | Ono et al. | Jun 2005 | A1 |
20050138192 | Encarnacion et al. | Jun 2005 | A1 |
20050177515 | Kalavade et al. | Aug 2005 | A1 |
20050235329 | Karaoguz et al. | Oct 2005 | A1 |
20050251821 | Pina | Nov 2005 | A1 |
20060009247 | Kelley et al. | Jan 2006 | A1 |
20060031451 | Lortz et al. | Feb 2006 | A1 |
20060046714 | Kalavade | Mar 2006 | A1 |
20060098593 | Edvardsen et al. | May 2006 | A1 |
20060123099 | Paila | Jun 2006 | A1 |
20060150251 | Takashima et al. | Jul 2006 | A1 |
20060172700 | Wu | Aug 2006 | A1 |
20060193456 | Light et al. | Aug 2006 | A1 |
20060209773 | Hundal | Sep 2006 | A1 |
20060220838 | Wakim et al. | Oct 2006 | A1 |
20060262913 | Cook et al. | Nov 2006 | A1 |
20060271968 | Zellner | Nov 2006 | A1 |
20070005506 | Candelore et al. | Jan 2007 | A1 |
20070019670 | Falardeau | Jan 2007 | A1 |
20070022469 | Cooper | Jan 2007 | A1 |
20070055783 | Gourraud | Mar 2007 | A1 |
20070097860 | Rys | May 2007 | A1 |
20070130476 | Mohanty et al. | Jun 2007 | A1 |
20070140448 | Lin et al. | Jun 2007 | A1 |
20070142036 | Wikman et al. | Jun 2007 | A1 |
20070157281 | Ellis | Jul 2007 | A1 |
20070180082 | Abraham et al. | Aug 2007 | A1 |
20070180111 | Chmaytelli et al. | Aug 2007 | A1 |
20070263853 | Pearson et al. | Nov 2007 | A1 |
20070298842 | Kamada et al. | Dec 2007 | A1 |
20080074258 | Bennett et al. | Mar 2008 | A1 |
20080195406 | Matsumoto | Aug 2008 | A1 |
20080281926 | Walter et al. | Nov 2008 | A1 |
20080320534 | Wang et al. | Dec 2008 | A1 |
20090019492 | Grasset | Jan 2009 | A1 |
20090031360 | Kidd et al. | Jan 2009 | A1 |
20090063193 | Barton et al. | Mar 2009 | A1 |
20090088197 | Stewart | Apr 2009 | A1 |
20090089183 | Afram et al. | Apr 2009 | A1 |
20090093237 | Levenshteyn | Apr 2009 | A1 |
20090106366 | Virtanen et al. | Apr 2009 | A1 |
20090171985 | Tischer | Jul 2009 | A1 |
20090193486 | Patel et al. | Jul 2009 | A1 |
20090204617 | Benson et al. | Aug 2009 | A1 |
20090282098 | Karaoguz | Nov 2009 | A1 |
20090288122 | Zellner | Nov 2009 | A1 |
20090298514 | Ullah | Dec 2009 | A1 |
20090298535 | Klein et al. | Dec 2009 | A1 |
20090327702 | Schnell | Dec 2009 | A1 |
20090328118 | Ravishankar | Dec 2009 | A1 |
20090328228 | Schnell | Dec 2009 | A1 |
20100031298 | Iwanami et al. | Feb 2010 | A1 |
20100031366 | Knight et al. | Feb 2010 | A1 |
20100052853 | Hilton | Mar 2010 | A1 |
20100058398 | Ojala et al. | Mar 2010 | A1 |
20100071021 | Friedman | Mar 2010 | A1 |
20100076274 | Severson | Mar 2010 | A1 |
20100194335 | Kirby et al. | Aug 2010 | A1 |
20100197238 | Pathuri et al. | Aug 2010 | A1 |
20100275249 | McCann et al. | Oct 2010 | A1 |
20100328547 | Mayorga | Dec 2010 | A1 |
20110022522 | Sege | Jan 2011 | A1 |
20110043326 | Lee et al. | Feb 2011 | A1 |
20110055901 | Karaoguz et al. | Mar 2011 | A1 |
20110130118 | Fan | Jun 2011 | A1 |
20110131398 | Chaturvedi et al. | Jun 2011 | A1 |
20110197264 | McDade | Aug 2011 | A1 |
20110209221 | Hanson et al. | Aug 2011 | A1 |
20110258437 | McKelvey | Oct 2011 | A1 |
20120030034 | Knapp et al. | Feb 2012 | A1 |
20120036549 | Patel et al. | Feb 2012 | A1 |
20120062796 | Roberts et al. | Mar 2012 | A1 |
20120081209 | Brown et al. | Apr 2012 | A1 |
20120084834 | Brown | Apr 2012 | A1 |
20120246214 | Ogawa et al. | Sep 2012 | A1 |
20130031261 | Suggs et al. | Jan 2013 | A1 |
20130254353 | Liu et al. | Sep 2013 | A1 |
20140298418 | Cronk et al. | Oct 2014 | A9 |
20160212739 | Brown et al. | Jul 2016 | A1 |
Entry |
---|
B. Zimmerly, , ““A Tiny Cloud in Android—Exploring the Android File System from Your Browser”,”, pp. 1-17, http://www.ibm.com/developeworks/opensource/library/os-tinycloud/index.htm, website last visited Oct. 1, 2010. |
Davies, C. , ““i-Jetty Turns Android Cellphone Into Mobile Webserver”,”, pp. 1-6, http://www.phonemag.com/i-jetty-turnsandroid-cellphone-into-mobile-webserver-031762 . . . , posted Mar. 17, 2008, website last visited Oct. 1, 2010. |
Davies, C. , “i-Jetty Turns Android Cellphone Into Mobile Webserver”, 6 pages, http://www.phonemag.com/i-jetty-turns-android-cellphone-into-mobile-webserver-031762 . . . , posted Mar. 17, 2008, website last visited Oct. 1, 2010. |
Lin, et al., ““On Controlling Digital TV Set-Top-Box by Mobile Devices via IP Network”,”, pp. 1-8, Proceedings of the Seventh IEEE International Symposium on Multimedia (ISM '05), Computer Society, 2005. |
Lin, et al., “On Controlling Digital TV Set-Top-Box by Mobile Devices via IP Network”, 8 pages, Proceedings of the Seventh IEEE International Symposium on Multimedia (ISM '05), Computer Society, 2005. |
Linux, Devices , ““iNTEL ‘Personal Server’ Research: Mobile Computing in the Palm of your Hand”,”, pp. 1-4, http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Intel-Personal-Server-res . . . , website last visited Oct. 1, 2010. |
Linux Devices, , “Intel ‘Personal Server’ Research: Mobile Computing in the Palm of your Hand”, pp. 1-4, http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Intel-Personal-Server-res . . . , website last visited Oct. 1, 2010. |
Opensource, , ““MWS:Rationale—A Website on a Mobile Personal Device is Different”,”, pp. 1-4, http://wiki.opensource.nokia.com/projects/MWS:Rationale, website last visited Oct. 1, 2010. |
Opensource, , “MWS: Rationale—A Website on a Mobile Computing in the Palm of your Hand”, pp. 1-4, http://wiki.opensource.nokia.com/projects/MWS:Rationale, website last visited Oct. 1, 2010. |
Rendon, et al., “Architecture for Web Services Access from Mobile Devices”, Web Congress, LA-WEB 2005, Third Latin American, 2005. |
Soroko, , ““Web Server on Your Cellphone—A New Design Space”,”, Popular Logistics, Feb. 16, 2010, 4 pages. |
Soroko, Jonathan , “Web Server on Your Cellphone—a New Design Space”, pp. 1-4, Popular Logistics, Feb. 16, 2010. |
Toorani, et al., ““LPKI—A Lightweight Public Key Infrastructure for the Mobile Environments””, pp. 162-166, IEEE 2008, ICCS 2008. |
Toorani, et al., “LPKI—A Lightweight Public Key Infrastructure for the Mobile Environments”, pp. 162-166, IEEE 2008, ICCS 2008. |
Wikipedia, , ““Mobile Web Server (Symbian OS)”,”, 1 page, http://en.wikipedia.org/wiki/Mobile—Web—Server—(Symbian—OS), website last visited Oct. 1, 2010. |
Wikipedia, , ““Mobile Web Server”,”, pp. 1-3, Page last modified Sep. 11, 2010. |
Wikipedia, , “Mobile Web Server”, pp. 1-3, website last visited Oct. 1, 2010. |
Wikipedia, “Mobile Web Server (Symbian OS)”, 1 page, http://en.wikipedia.org/wiki/Mobile—Web—Server—(Symbian—Os), website last visited Oct. 1, 2010. |
Zimmerly, Bill , “A Tiny Cloud in Android”, 17 pages article, website last visited Oct. 1, 2010, http://www.ibm.com/developerworks/opensources/library/os-tinycloud/index.html. |
Number | Date | Country | |
---|---|---|---|
20160366467 A1 | Dec 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13705894 | Dec 2012 | US |
Child | 15248908 | US |