The present disclosure relates generally to device communication techniques and more specifically to a system for establishing communications with a mobile device server.
Media communication systems such as interactive television (iTV) systems can deliver media content to media processors such as set-top boxes (STBs). 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 such as the iPod™ can also 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.
The present disclosure describes, among other things, illustrative embodiments of a mobile device server for establishing communications and exchanging messages with media devices capable of supplying media content of various forms.
One embodiment of the present disclosure includes a portable telephone having a controller to execute a web server application in the portable telephone. The web server application can be operable to detect a set-top box (STB), and transmit a message to a server by way of a gateway assigned to a first Internet Protocol (IP) responsive to detecting the STB. The server can operate in an interactive television network remote from a location of the STB. The message can include an identifier of a software application in the portable telephone and a second IP address associated with the software application. The server can be operable to identify the STB and media services assigned thereto according to the first IP address of the gateway, and direct the STB to invoke the software application in the portable telephone according to the second IP address. The web server application can further be operable to receive a request from the STB to execute the software application according to the second IP address, and execute the software application to establish media communication services between the portable telephone and the STB.
One embodiment of the present disclosure includes a server having a controller to receive a message from a web server application operating in a portable telephone by way of a gateway communicatively coupled to the server, detect an identifier of the gateway, and establish communications with a media processor according to the identifier of the gateway; and direct the media processor to invoke the software application in the portable telephone according to the IP address. The message can include a request to invoke a software application in the portable telephone, and wherein the software application is associated with an Internet Protocol (IP) address.
One embodiment of the present disclosure includes a non-transitory computer-readable storage medium operating in a mobile device server having computer instructions to execute a web server application in the mobile device server. The web server application can be operable to cause a media processor to invoke a software application in the mobile device server. The mobile device server can support voice communications over a cellular communication system.
The VHS 114 can distribute multimedia broadcast content via an access network 118 to commercial and/or residential buildings 102 housing a gateway 104 (such as a common residential or commercial gateway). The access network 118 can represent a group of digital subscriber line access multiplexers (DSLAMs) located in a central office or a service area interface that provide broadband services over optical links or copper twisted pairs 119 to buildings 102. The gateway 104 can use common communication technology to distribute broadcast signals to media processors 106 such as Set-Top Boxes (STBs) which in turn present broadcast channels to media devices 108 such as computers or television sets managed in some instances by a media controller 107 (such as an infrared or RF remote control).
The gateway 104, the media processors 106, and media devices 108 can utilize tethered interface technologies (such as coaxial or phone line wiring) or can operate over a common wireless access protocol such as Wireless Fidelity (WiFi). With these interfaces, unicast communications can be invoked between the media processors 106 and subsystems of the IPTV media system for services such as video-on-demand (VoD), browsing an electronic programming guide (EPG), or other infrastructure services.
A satellite broadcast television system 129 can be used also in the media system of
In yet another embodiment, an analog or digital cable broadcast distribution system such as cable TV system 133 can be overlaid, operably coupled with, or replace the IPTV system and/or the satellite TV system 129 as another representative embodiment of communication system 100. In this embodiment the cable TV system 133 can provide Internet, telephony, and interactive media services also.
It is contemplated that the present disclosure can apply to any present or next generation over-the-air and/or landline media content services system.
Some of the network elements of the IPTV media system can be coupled to one or more computing devices 130, a portion of which can operate as a web server for providing portal services over an Internet Service Provider (ISP) network 132 to wireline media devices 108 or wireless communication devices 116. The portal services can be provided using various components and/or techniques, including by way of a wireless access base station 117 operating according to common wireless access protocols such as Wireless Fidelity (WiFi), or cellular communication technologies (such as GSM, CDMA, UMTS, WiMAX, Software Defined Radio or SDR, and so on).
System 100 can provide for all or a portion of the computing devices 130 to function as a remote server (herein referred to as server 130). The server 130 can use common computing and communication technology to perform the function of processing requests generated by a web server application operating in portable communication devices, such as those shown in reference 108 or 116 as will be described further below.
Communication system 200 can comprise a Home Subscriber Server (HSS) 240, a tElephone NUmber Mapping (ENUM) server 230, and other common network elements of an IMS network 250. The IMS network 250 can establish communications between IMS compliant communication devices (CD) 201, 202, Public Switched Telephone Network (PSTN) CDs 203, 205, and combinations thereof by way of a Media Gateway Control Function (MGCF) 220 coupled to a PSTN network 260. The MGCF 220 is not used when a communication session involves IMS CD to IMS CD communications. Any communication session involving at least one PSTN CD requires the use of the MGCF 220.
IMS CDs 201, 202 can register with the IMS network 250 by contacting a Proxy Call Session Control Function (P-CSCF) which communicates with a corresponding Serving CSCF (S-CSCF) to register the CDs with at the HSS 240. To initiate a communication session between CDs, an originating IMS CD 201 can submit a Session Initiation Protocol (SIP INVITE) message to an originating P-CSCF 204 which communicates with a corresponding originating S-CSCF 206. The originating S-CSCF 206 can submit queries to the ENUM system 230 to translate an E.164 telephone number in the SIP INVITE to a SIP Uniform Resource Identifier (URI) if the terminating communication device is IMS compliant.
The SIP URI can be used by an Interrogating CSCF (I-CSCF) 207 to submit a query to the HSS 240 to identify a terminating S-CSCF 214 associated with a terminating IMS CD such as reference 202. Once identified, the I-CSCF 207 can submit the SIP INVITE to the terminating S-CSCF 214. The terminating S-CSCF 214 can then identify a terminating P-CSCF 216 associated with the terminating CD 202. The P-CSCF 216 then signals the CD 202 to establish communications.
If the terminating communication device is instead a PSTN CD such as references 203 or 205, the ENUM system 230 can respond with an unsuccessful address resolution which can cause the originating S-CSCF 206 to forward the call to the MGCF 220 via a Breakout Gateway Control Function (BGCF) 219. The MGCF 220 can then initiate the call to the terminating PSTN CD by common means over the PSTN network 260.
The aforementioned communication process is symmetrical. Accordingly, the terms “originating” and “terminating” in
System 200 can include or otherwise be coupled with server 130 of
It is contemplated by the present disclosure that the web portal 302 can be utilized to manage operations of a mobile device server and/or operate as a remote server as described below.
The UI 404 can include a depressible or touch-sensitive keypad 408 with a navigation mechanism such as a roller ball, joystick, mouse, or 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 dialing 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.
The UI 404 can also include an audio system 412 that utilizes common audio technology for conveying low volume audio (such as audio heard only in the 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 charging system technologies for supplying energy to the components of the communication device 400 to facilitate long-range or short-range portable applications. The location receiver 416 can utilize common location technology such as a global positioning system (GPS) receiver for identifying a location of the communication device 400 based on signals generated by a constellation of GPS satellites, thereby facilitating common location services such as navigation.
The communication device 400 can use the transceiver 402 to also determine a proximity to a cellular, WiFi or Bluetooth access point by common power sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or a signal time of arrival (TOA) or time of flight (TOF). The controller 406 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), and/or a video processor with associated storage memory such a Flash, ROM, RAM, SRAM, DRAM or other storage technologies.
The communication device 400 can be adapted to perform the functions of the media processor 106, the media devices 108, or the portable communication devices 116 of
A web server application can represent a hypertext transfer protocol (HTTP) web server application implemented in software, hardware or combinations thereof operating from the controller 406 of the mobile device server 604. A web server application can also be represented by any web server application used by a server or hosting computer system. Accordingly, any type of web server application operational in a mobile device server 604 is contemplated by the present disclosure.
With this in mind, attention is redirected to
The web server application of the mobile device server 604 can scan for the presence of media resources such as the media processor 606 by requesting information from the residential gateway 608. The residential gateway 608 can transmit to the mobile device server 604 a list of the active devices on the WiFi network. Alternatively, or in combination, the web server application of the mobile device server 604 can transmit a broadcast message on the WiFi network requesting identification of the devices communicatively coupled to the WiFi network. Other identification techniques are contemplated by the present disclosure.
Once the media processor 106 has been discovered by the web server application operating from the mobile device server 604, the web server application can present the detected media resource(s) to a user over the UI 404 of the mobile device server 604. The user can manipulate the UI 404 as previously described to indicate a desire to establish communications with the media processor 606, thereby establishing the need described in step 504 of
In step 506, the web server application in the mobile device server 604 can initiate a URL directed to the remote server 612 by way of the residential gateway 608. The following URL is an illustrative embodiment of a URL that can be initiated by the mobile device server 604: http://someServer.com/launchApp?special_app=http://<IP address of MDS x.x.x.x>/mrml.xml.
The illustrative URL can include a domain name of the remote server 612 and instructions to launch a specific software application executable by the web server application in the mobile device server 604. The URL can also include an IP address of the mobile device server 604 which can be used to launch the software application.
In step 508, the residential gateway 608 can invoke the URL and insert therewith the IP address assigned to the residential gateway 608. The server 612 can receive the URL message by way of the ISP network 610 of
In step 512, the remote server 612 can authenticate the request from the mobile device server 604 with the IP address of the mobile device server 604 or some other identifier added to the URL message (e.g., MAC address of the mobile device server 604). If the server 612 does not recognize the mobile device server 604 in step 614, method 500 can cease. Otherwise, if authentication is successful, the server 612 can proceed to step 516. Authentication of the mobile device server 604 can be delegated to the media processor 606, in which case steps 512 and 514 would be bypassed.
At step 516, the server 612 can be operable to locate the media processor 606 and media services associated therewith according to the detected IP address of the residential gateway 608. The server 612 can locate the media processor 606 from a look-up table in a database 614 operating as a Domain Name Server (DNS), a subscriber database, or combinations thereof. Once the media processor 606 and services associated therewith have been identified, the server 612 can transmit to the media processor 606 in step 518 a URL message to invoke the software application in the mobile device server 604 according to the IP address of the mobile device server 604. The following is an illustrative embodiment of a URL message that can be transmitted to the media processor 606: http://<IP address of MDS x.x.x.x>/mrml.xml.
Once the media processor 606 invokes this URL in step 520, the web server application in the mobile device server 604 can be operable to execute the software application in step 522 and thereby establish an initial state of communications with the media processor 606. Authentication of the mobile device server 604 can take place in steps 524-526 prior to enabling media communication services between the mobile device server 604 and the media processor 606. In step 524, the mobile device server 604 can transmit authentication data to the media processor 606. The authentication data can comprise, for example, a security key provided by the service provider of the interactive communication systems of
If the authentication data is invalid or not recognized, method 500 ceases. Otherwise, the media processor 606 proceeds to step 528 where it enable media communication services between the mobile device server 604 and the media processor 606. Media communication services can conform to a markup language such as multimedia retrieval markup language (MRML) or an extensible markup language (XML). Other markup languages are contemplated by the present disclosure. In step 530, the web server application operating in the mobile device server 604 can control media services of the media processor with an exchange of markup language instructions transmitted over the WiFi network in the premises 602. The web server application, for example, can direct the media processor 606 to store and/or present media content supplied by the mobile device server 604, or can request media content from the media processor 606. Other exchanges between the mobile device server 604 and the media processor 606 are contemplated by the present disclosure.
The aforementioned disclosure contemplates a mobile device server 604 that among other things is capable of detecting media resources which it can prompt by way of a server 612 to invoke one or more software applications operating from the mobile device server 604. By mobilizing a web server by way of a mobile device server 604 as described above it is no longer necessary for media resources to be managed exclusively by way of infrastructure devices such as those shown in
Upon reviewing the aforementioned embodiments, it would be evident to an artisan with ordinary skill in the art that said embodiments can be modified, reduced, or enhanced without departing from the scope and spirit of the claims described below. For example, method 500 can be adapted so that a mobile device server 604 can communicate with other mobile device servers. In this configuration one of the mobile device servers 604 can function in part as the media processor 606 of
Other suitable modifications can be applied to the present disclosure without departing from the scope of the claims below. Accordingly, the reader is directed to the claims section for a fuller understanding of the breadth and scope of the present disclosure.
The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet PC, a laptop computer, a desktop computer, a control system, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. It will be understood that a device of the present disclosure includes broadly any electronic device that provides voice, video or data communication. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
The computer system 700 may include a processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU, or both), a main memory 704 and a static memory 706, which communicate with each other via a bus 708. The computer system 700 may further include a video display unit 710 (e.g., a liquid crystal display (LCD), a flat panel, a solid state display, or a cathode ray tube (CRT)). The computer system 700 may include an input device 712 (e.g., a keyboard), a cursor control device 714 (e.g., a mouse), a disk drive unit 716, a signal generation device 718 (e.g., a speaker or remote control) and a network interface device 720.
The disk drive unit 716 may include a machine-readable medium 722 on which is stored one or more sets of instructions (e.g., software 724) embodying any one or more of the methodologies or functions described herein, including those methods illustrated above. The instructions 724 may also reside, completely or at least partially, within the main memory 704, the static memory 706, and/or within the processor 702 during execution thereof by the computer system 700. The main memory 704 and the processor 702 also may constitute machine-readable media.
Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations.
In accordance with various embodiments of the present disclosure, the methods described herein are intended for operation as software programs running on a computer processor. Furthermore, software implementations can include, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
The present disclosure contemplates a machine readable medium containing instructions 724, or that which receives and executes instructions 724 from a propagated signal so that a device connected to a network environment 726 can send or receive voice, video or data, and to communicate over the network 726 using the instructions 724. The instructions 724 may further be transmitted or received over a network 726 via the network interface device 720.
While the machine-readable medium 722 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure.
The term “machine-readable medium” shall accordingly be taken to include, but not be limited to: solid-state memories such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories; magneto-optical or optical medium such as a disk or tape; and/or a digital file attachment to e-mail or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a machine-readable medium or a distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.
Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Each of the standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same functions are considered equivalents.
The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Figures are also merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.
The Abstract of the Disclosure is provided 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. 14/023,059, filed Sep. 10, 2013, which is a Continuation of and claims priority to U.S. patent application Ser. No. 12/860,824, filed Aug. 20, 2010, issued as U.S. Pat. No. 8,555,332. The contents of each of the foregoing are 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 |
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 |
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 |
20040240668 | Bonan et al. | Dec 2004 | A1 |
20040253923 | Braley | Dec 2004 | A1 |
20050010637 | Dempski et al. | Jan 2005 | A1 |
20050044223 | Meyerson et al. | 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 et al. | Sep 2006 | A1 |
20060220838 | Wakim et al. | Oct 2006 | A1 |
20060262913 | Cook | Nov 2006 | A1 |
20060271968 | Zellner | Nov 2006 | A1 |
20070005506 | Candelore et al. | Jan 2007 | A1 |
20070019670 | Falardeau et al. | Jan 2007 | A1 |
20070022469 | Cooper et al. | Jan 2007 | A1 |
20070055783 | Gourraud | Mar 2007 | A1 |
20070097860 | Rys et al. | May 2007 | A1 |
20070140448 | Lin et al. | Jun 2007 | A1 |
20070142036 | Wikman et al. | Jun 2007 | A1 |
20070157281 | Ellis et al. | 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 et al. | 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 et al. | 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 |
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 |
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. |
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. |
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 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. |
Toorani, et al., “LPKI—A Lightweight Public Key Infrastructure for the Mobile Environnients”, 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, http://wiki.opensource.nokia.com/projects/Mobile—Web—server, Page last modified Sep. 11, 2010. |
Number | Date | Country | |
---|---|---|---|
20140344878 A1 | Nov 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14023059 | Sep 2013 | US |
Child | 14452003 | US | |
Parent | 12860824 | Aug 2010 | US |
Child | 14023059 | US |