1. Technical Field
The embodiments described herein generally relate to wireless communication and more particularly to automatic connection with a wireless Wide Area Network (WAN) through a mobile, wireless Intelligent Mobile HotSpot (IMHS).
2. Related Art
Wireless modems exist that can be inserted, or otherwise interfaced with a computer and that enable data communication over a wireless Wide Area Network (WAN) such as a cellular type network. Early versions of these cards had connectors that complied with the PCMCIA standard and that were inserted into a slot in the side of the computer. Newer versions have USB connectors for interfacing with the computer. Such modems allow access to the Internet, or World Wide Web (WWW), even where no wired network connection exists and are most often interfaced with a laptop or other portable computing device.
In networking, the PPP is a data link protocol commonly used to establish a direct connection between two networking nodes. It can provide connection authentication, transmission encryption privacy, and compression. PPP is used over many types of physical networks including serial cable, phone line, trunk line, cellular telephone, specialized radio links, and fiber optic links such as SONET. For example, most Internet service providers (ISPs) use PPP for customer dial-up access to the Internet. PPP is commonly used as a data link layer protocol for connection over synchronous and asynchronous circuits, where it has largely superseded the older, non-standard Serial Line Internet Protocol (SLIP) and Telephone Company mandated standards, such as Link Access Protocol, Balanced (LAPB) in the X.25 protocol suite. PPP is designed to work with numerous network layer protocols, including Internet Protocol (IP), Novell's Internetwork Packet Exchange (IPX), NBF, and AppleTalk.
One draw back to system 100 of
An Intelligent Mobile HotSpot (IMHS) that can interface multiple computing or wireless LAN client devices with a base station is disclosed herein.
According to one aspect, an IMHS comprises a wide area network radio interface configured to enable communications between a wide area network and the IMHS; a local area network radio interface configured to enable communications between the IMHS and a computing device; a power input configured to cause the IMHS to be powered on; memory configured to store instructions; and a processor coupled with memory, the instructions configured to cause the processor to perform the following in response to an activation of the power input: automatically establish a data connection with a base station associated with the wide area network over the wide area network, automatically establish a data connection with computing device over the local area network, and be in a ready state to route data packets from the computing device to the base station via the local area network data connection and the wide area network connection.
According to another aspect, an IMHS comprises a wide area network radio interface configured to enable communications between a wide area network and the IMHS; a local area network radio interface configured to enable communications between the IMHS and a computing device; a power input configured to cause the IMHS to be powered on; volatile memory; non-volatile memory configured to store modem instructions and a modem function table for controlling the wide area network interface and router instructions and a router function table for controlling the local area network interface, the router instructions comprising an address offset indicating an address in the volatile memory; and a processor coupled with memory, the instructions configured to cause the processor, in response to an activation of the power input, to load the modem instructions into the volatile memory, and to load the router instructions into volatile memory at the address indicated by the offset.
According to still another embodiment, A system for wireless data communication comprises a base station associated with a wide area network; and an IMHS, the IMHS comprising a wide area network radio interface configured to enable communications between the base station and the IMHS; a local area network radio interface configured to enable communications between the IMHS and a computing device; a power input configured to cause the IMHS to be powered on; memory configured to store instructions; and a processor coupled with memory The instructions can be configured to cause the processor to perform the following in response to an activation of the power input automatically establish a data connection with the base station over the wide area network automatically establish a data connection with computing device over the local area network, and be in a ready state to route data packets from the computing device to the base station via the local area network data connection and the wide area network connection.
These and other features, aspects, and embodiments are described below in the section entitled “Detailed Description.”
Features, aspects, and embodiments are described in conjunction with the attached drawings, in which:
In the embodiments below, an IMHS is used to interface a plurality of computing device or LAN client devices with a wireless WAN. For example, the WAN can be configured to implement one of the Third Generation (3G) protocols, such as EDGE, CDMA2000, or the Universal Mobile Telecommunications System (UMTS) protocols, High Speed Packet Access (HSPA) or HSPA+ protocols, Long Term Evolution (LTE) protocols, Evolution Data Optimization (EV-DO) rev. A (DOrA), WiMAX, or other newer 4G protocols. The computing devices interface with the IMHS over a wireless Local Area Network (LAN) such as a WiFi network, wireless USB network, ultrawideband network, or a Zigbee network; however, it will be understood that the descriptions that follow are not intended to limit the embodiments herein to particular standards or architectures, the embodiments being provide by way of example only.
In certain embodiments, IMHS 304 can, e.g., be configured to interface as many as five (5) computing devices 306 with base station 302.
Thus, all that is required to enable multiple computing devices 306 to access the wireless WAN is to power on IMHS 304, and possibly provide a password. IMHS 304 will automatically establish a connection with the WAN and enable the wireless LAN hotspot in response. There is no tethering of IMHS 304 with devices 306.
Referring to
Memory 504 can comprise several forms of memory, such as non-volatile memory 506 and volatile memory 508. Non-volatile memory is used to store data and instructions that should be maintained even when power is removed from IMHS 304. Volatile memory is used to store instructions and data for which it is not important whether it is maintain when power is removed. For example, the code used to run IMHS 304 can be stored in non-volatile memory 506 such that it is maintained even when IMHS 304 is turned off and so that IMHS 304 can access this code when it is turned on again; however, the code can be copied to volatile memory 508 when IMHS 304 is on. This can, for example, allow faster access to instructions and data by processor 502.
Examples of non-volatile memory include Read-Only Memory (ROM), flash memory, and most types of magnetic computer storage devices, e.g., hard disks, floppy disks, and magnetic tape and optical discs, although these later devices are not generally used for IMHS 304. Rather, the former, which can be referred to as electrically addressed non-volatile memories are typically used for IMHS 304. Non-volatile memory is typically used for the task of secondary storage, or long-term persistent storage. Most forms of non-volatile memory have limitations that make them unsuitable for use as primary storage. Typically, non-volatile memory either costs more or performs worse than volatile random access memory. Electrically addressed non-volatile memories can include a Programmable ROM (PROM), Erasable PROMs (EPROM), Electrically erasable PROM (EEPROM), Flash memory, or some combination thereof.
Volatile memory, also known as volatile storage or primary storage device, is computer memory that requires power to maintain the stored information, unlike non-volatile memory which does not require a maintained power supply. The most widely used form of primary storage today is a volatile form of random access memory (RAM), meaning that when the computer is shut down, anything contained in RAM is lost. Most forms of modern RAM are volatile storage, including Dynamic Random Access Memory (DRAM) and static random access memory (SRAM). Thus, IMHS 304 can include DRAM, SRAM, or some combination thereof, although IMHS 304 is more likely to include SRAM than DRAM.
In certain embodiments, some portion or even all of non-volatile memory 506, volatile memory 508, or both can be included with processor 502.
LAN radio 510 can comprises all of the hardware required for the radio front end of the wireless LAN interface. Similarly, WAN radio 512 can comprises all of the hardware required for the radio front end of the wireless WAN interface. Processor 502 or components thereof can serve as the processing backend for both radios 510 and 512. Alternatively, separate processing circuitry can be included for each of the LAN function and the WAN function. In such embodiments, the processing functionality described herein can be included in either the LAN processing circuitry or the WAN processing circuitry.
User interface 514 can comprise just button 312. But in other embodiments, it can also comprise a display, e.g., to display a password.
Instructions stored in memory 504 can be used by processor 502 to control the operation of IMHS 502 including control of radios 510 and 512. Thus, the instructions stored in memory 504 should include instructions for controlling the operation of radios 510 and 512 as well as for bridging communications between basestation 320 and devices 306 and for configuring IMHS 304. In certain embodiments, the instructions for controlling WAN radio 512, and the authentication procedures for connecting to the WAN, can be included in standard code associated with WAN radio 512. These instructions can be referred to as modem instructions. Separate instructions for controlling the remaining functions of IMHS 304 can then also be stored in memory 504, including the procedures and settings for controlling LAN radio 510. These instructions can be referred to as router instructions.
A process for allowing these two sets of instructions to interact must then be implemented in such embodiments.
Alternatively, a single function table with the appropriate functions and pointers can be created and used by both modem and router instructions 602 and 604; however, it will be understood that how the function tables are described is a matter of convenience and that what is important is that there is an association between functions and pointers to functions in the various instructions that is maintained within IMHS 304.
Initialization function 612 can also be configured to create a set of related tasks, e.g., an http server task, a WiFi driver task, a bridge task, etc. For example, once the functional tables are initializes, the router instructions can start to run in step 708. Different tasks can then be called in steps 712, 714, and 716, which can cause initialization functions related with each tasks to run in steps 718, 720, and 722. These initialization functions can then initialize the related tasks such that they can run in steps 724, 726 and 728.
On successful initialization, router instructions 604 can be configured to notify modem instructions 602 through either a return value or a signal.
Modem instructions 602 can start to run in step 708. As the modem instruction and router tasks run, they can communicate with each other using the set of function pointers populated in the function pointer tables. For example, a typical function that a router task can use is “efs_open” or “rex_sleep.” Modem instructions 602 can, for example, call a transmit function in the router WiFi driver or it can call the address translate functions.
A partition table for memory 504 can for example have one additional, e.g., 3 MB partition for router instructions 604. Router instructions 604 can be built into a binary file from, e.g., an elf file.
On boot up, the operating system can verify the checksum, version compatibility, and magic string from the image header before proceeding to the next step, e.g., step 702.
Accordingly, router instructions 604 are not statically linked into modem instructions 602. Rather, they will be compiled and linked into a separate binary with a fixed entry point (offset address) specified in the router image header. This binary can then be loaded at that exact location specified by the offset address at run time. The memory location specified by the offset address should specify a block of memory that is not used by the memory instructions. Once the memory section is created, the router binary except the header can then be loaded at the address where the image was created. After the modem instruction initialization is completed, it will call an initialization function located in the router binary. This location will be known to the modem instructions because where the router binary was loaded in the memory will be known. The router initialization function can then populate the rest of the function pointers in the structure described above for the modem instructions. Form this point on the modem and router instructions can communicate with each other using the set of functions that have been saved in the function pointer table.
Once IMHS 304 is powered up, the connection with base station 302 is establish, the LAN is activated, and IMHS 304 will be ready to route data packets from devices 306 to base station 302. Devices 306 can then access, e.g., the Internet through IMHS 304. All that may be required for devices 306 to access the Internet, or more generally the WAN associated with base station 302 is a password, which can be displayed in IMHS 304. Contrast this with system 100 in which only a single device 106 can access the WAN.
While certain embodiments have been described above, it will be understood that the embodiments described are by way of example only. Accordingly, the systems and methods described herein should not be limited based on the described embodiments. Rather, the systems and methods described herein should only be limited in light of the claims that follow when taken in conjunction with the above description and accompanying drawings.
This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Application Ser. No. 61/178,926, filed May 15, 2009 and entitled “Rule Based Internet Browser Redirect for Wireless WAN Routers,” and which is incorporated herein by reference in its entirety as if set forth in full.
Number | Name | Date | Kind |
---|---|---|---|
6243575 | Ohyama et al. | Jun 2001 | B1 |
6246883 | Lee | Jun 2001 | B1 |
6889032 | Dao et al. | May 2005 | B2 |
7149197 | Garahi et al. | Dec 2006 | B2 |
7167715 | Stanforth | Jan 2007 | B2 |
7206294 | Garahi et al. | Apr 2007 | B2 |
7269668 | Redford et al. | Sep 2007 | B2 |
7317896 | Saxena et al. | Jan 2008 | B1 |
7372843 | Asawa et al. | May 2008 | B1 |
7382771 | Leblanc et al. | Jun 2008 | B2 |
7408896 | Chen et al. | Aug 2008 | B2 |
7499401 | Buddhikot et al. | Mar 2009 | B2 |
7593718 | Gorday et al. | Sep 2009 | B2 |
7672695 | Rainnie et al. | Mar 2010 | B1 |
7801080 | Kim et al. | Sep 2010 | B2 |
7813314 | Fulknier et al. | Oct 2010 | B2 |
8489059 | Rainnie et al. | Jul 2013 | B1 |
20020118663 | Dorenbosch et al. | Aug 2002 | A1 |
20030195010 | Pattabiraman et al. | Oct 2003 | A1 |
20040022222 | Clisham | Feb 2004 | A1 |
20040179512 | Leblanc et al. | Sep 2004 | A1 |
20040219905 | Blumenthal et al. | Nov 2004 | A1 |
20050075093 | Lei et al. | Apr 2005 | A1 |
20050078620 | Balachandran et al. | Apr 2005 | A1 |
20050265323 | Thermond | Dec 2005 | A1 |
20050286476 | Crosswy et al. | Dec 2005 | A1 |
20060013173 | Rinne et al. | Jan 2006 | A1 |
20060089169 | Hsu et al. | Apr 2006 | A1 |
20070066280 | Arai et al. | Mar 2007 | A1 |
20070073854 | Lindquist | Mar 2007 | A1 |
20070088521 | Shmueli et al. | Apr 2007 | A1 |
20070104168 | Polson | May 2007 | A1 |
20070110017 | Fulknier et al. | May 2007 | A1 |
20070115950 | Bennett et al. | May 2007 | A1 |
20070153739 | Zheng | Jul 2007 | A1 |
20070206591 | Doviak et al. | Sep 2007 | A1 |
20070208864 | Flynn et al. | Sep 2007 | A1 |
20070211686 | Belcea et al. | Sep 2007 | A1 |
20070254727 | Sewall et al. | Nov 2007 | A1 |
20070286138 | Kaftan | Dec 2007 | A1 |
20080039102 | Johnson et al. | Feb 2008 | A1 |
20080080455 | Rofougaran | Apr 2008 | A1 |
20080101266 | Dahlstedt et al. | May 2008 | A1 |
20080117860 | Rodriguez | May 2008 | A1 |
20090003269 | Kumazawa et al. | Jan 2009 | A1 |
20090049176 | Weinert et al. | Feb 2009 | A1 |
20090177593 | Kano et al. | Jul 2009 | A1 |
20100226280 | Burns et al. | Sep 2010 | A1 |
20100228936 | Wright et al. | Sep 2010 | A1 |
20100286993 | Lovelace | Nov 2010 | A1 |
20110007705 | Buddhikot et al. | Jan 2011 | A1 |
20110051703 | Fulknier et al. | Mar 2011 | A1 |
20110194411 | Croft et al. | Aug 2011 | A1 |
20120057456 | Bogatin et al. | Mar 2012 | A1 |
20120272310 | Souissi et al. | Oct 2012 | A1 |
Number | Date | Country |
---|---|---|
11621740 | Jan 2010 | CN |
2420954 | Jun 2006 | GB |
2006005824 | Jan 2006 | JP |
2008134763 | Jun 2008 | WO |
2008088923 | Jul 2008 | WO |
2009139562 | Nov 2009 | WO |
2009106791 | Mar 2013 | WO |
Entry |
---|
Combined UK Search and Examination Report for GB0919966.2 dated Nov. 26, 2009. |
International Search Report and Written Opinion issued on Sep. 27, 2010 in related application PCT/US10/25267 (10 pages). |
International Search Report and Written Opinion issued on Dec. 17, 2010 in related application PCT/US2010/034811 (9 pages). |
European Search Report issued in related application EP 10775217.2 dated Sep. 27, 2012 (9 pages). |
Number | Date | Country | |
---|---|---|---|
20100290442 A1 | Nov 2010 | US |
Number | Date | Country | |
---|---|---|---|
61178926 | May 2009 | US |