U.S. patent application number 13/888346 was filed with the patent office on 2013-09-19 for portable device that operates as a multi-protocol gateway communications gateway to a wireless network.
The applicant listed for this patent is Scott Allen Schlack. Invention is credited to Scott Allen Schlack.
Application Number | 20130242969 13/888346 |
Document ID | / |
Family ID | 43898380 |
Filed Date | 2013-09-19 |
United States Patent
Application |
20130242969 |
Kind Code |
A1 |
Schlack; Scott Allen |
September 19, 2013 |
PORTABLE DEVICE THAT OPERATES AS A MULTI-PROTOCOL GATEWAY
COMMUNICATIONS GATEWAY TO A WIRELESS NETWORK
Abstract
A portable gateway device with a wireless local area network
communications component capable of Wi-Fi or Bluetooth
communications, a cellular wireless communications component
capable of 3GPP LTE or LTE advanced communications, and a WiMAX
communications component capable of WiMAX communications, and an
identification module storing network authentication information
for accessing a telecommunications network. The portable gateway
device is configured such that the WLAN communications component
enables Wi-Fi or Bluetooth communications at the same time the
cellular wireless communications component enables LTE or LTE
Advanced communications. The portable gateway device is also
configured such the WLAN communications component enables Wi-Fi or
Bluetooth communications at the same time the WiMAX communications
component enables WiMAX communications.
Inventors: |
Schlack; Scott Allen;
(Lynnwood, WA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Schlack; Scott Allen |
|
|
US |
|
|
Family ID: |
43898380 |
Appl. No.: |
13/888346 |
Filed: |
May 6, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12910781 |
Oct 22, 2010 |
8488541 |
|
|
13888346 |
|
|
|
|
61253920 |
Oct 22, 2009 |
|
|
|
Current U.S.
Class: |
370/338 |
Current CPC
Class: |
H04W 72/0453 20130101;
H04W 88/16 20130101; H04W 88/04 20130101; H04W 76/15 20180201; H04W
12/0609 20190101 |
Class at
Publication: |
370/338 |
International
Class: |
H04W 88/16 20060101
H04W088/16 |
Claims
1. A portable gateway device comprising: one or more processors; a
memory; an identification module storing network authentication
information; a wireless local area network (WLAN) communications
component; a cellular wireless communications component; and a
WiMAX communications component, wherein the network authentication
information stored in the identification module includes i)
information for accessing a cellular telecommunication network
using the cellular wireless communications component, or ii)
information for accessing a WiMAX network using the WiMAX
communications component.
2. The portable gateway device of claim 1, further comprising a
plurality of indicator lights for identifying a communication
signal strength for communications between the portable gateway
device and a serving base station.
3. The portable gateway device of claim 1, further comprising a
device authentication component for authenticating access to the
portable gateway device by one or more external computing devices
via the WLAN communications component.
4. (canceled)
5. The portable gateway device of claim 1, wherein the WLAN
communications component enables Wi-Fi or Bluetooth
communications.
6. The portable gateway device of claim 5, wherein the cellular
wireless communications component enables 3GPP long term evolution
(LTE) or LTE Advanced communications over a cellular
telecommunication network.
7. The portable gateway device of claim 6, wherein the WiMAX
communications component enables WiMAX communications.
8. The portable gateway device of claim 7, wherein the WLAN
communications component enables Wi-Fi or Bluetooth communications
at the same time that i) the cellular wireless communications
component enables LTE or LTE Advanced communications, or ii) the
WiMAX communications component enables WiMAX communications.
9. The portable gateway device of claim 1, wherein the portable
gateway device is connectable to an external power source that is
portable.
10. The portable gateway device of claim 1, wherein the portable
gateway device is attachable to, and detachable from, a personal
computing device.
11. A wireless communications device comprising: one or more
processors; a memory; a wireless local area network (WLAN)
communications component enabling communications via a WLAN
communications protocol; a first wide area network (WAN)
communications component enabling communications via a first WAN
telecommunications protocol; and a second WAN communications
component enabling communications via a second WAN
telecommunications protocol, wherein the second WAN
telecommunications protocol is different from the first WAN
telecommunications protocol.
12. The wireless communications device of claim 11, further
comprising a network identification module storing authentication
information for accessing a telecommunication network using the i)
the first WAN communications component or ii) the second WAN
communications component.
13. The wireless communications device of claim 11, wherein the
WLAN communications protocol is associated with a Wi-Fi or a
Bluetooth communications protocol.
14. The wireless communications device of claim 12, wherein the
first WAN communications protocol is associated with a 3GPP Long
Term Evolution (LTE) or LTE Advanced telecommunications
protocol.
15. The wireless communications device of claim 12, wherein the
second WAN communications protocol is associated with a WiMAX
telecommunications protocol.
16. The wireless communications device of claim 11, further
comprising a device authentication component for authenticating
access to the portable gateway device by one or more external
computing devices via the WLAN communications component.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] The present application claims priority filing benefit to
co-pending U.S. patent application Ser. No. 12/910,781, filed Oct.
22, 2010, and to U.S. Provisional Patent Application No.
61/253,920, filed Oct. 22, 2009, which are incorporated herein by
reference.
FIELD OF THE INVENTION
[0002] The present invention generally relates to systems and
methods associated with a portable transceiver device that can
facilitate one or more local computing devices accessing a
subscriber-based network.
BACKGROUND OF THE INVENTION
[0003] With the increasing popularity of modern data communications
devices, also referred to herein as personal computing devices
(PCDs), such as cellular phones, personal desktop assistants
(PDAs), tablet computers, netbook computers, laptop computers,
electronic book devices, media player devices, video-gaming units,
digital cameras, video recorders, etc., many consumers are creating
a high demand for new technologies that enhance the mobility and
flexibility of wireless services that facilitate network
communications for their PCDs. Only a minority of consumers today
is able to replace their wireless-capable PCDs (e.g., their cell
phone or tablet computing devices) every time a new or more popular
device model (having improved features and functionality) becomes
available. Most consumers prefer to simply upgrade or enhance their
existing PCDs for a period of time, by updating operating system
firmware, adding new software applications, and/or purchasing
auxiliary compatible aftermarket hardware components, such as:
external or plug-in memory components, wireless modems, media card
readers, GPS units, auxiliary microphone and/or speaker devices,
webcams, etc.
[0004] One relatively new technology that some consumers utilize to
enhance the data communications capability of their existing PCDs
is known in the Art as device "tethering." By way of example, the
Apple.RTM. iPhone.TM. (e.g., 112b of FIG. 1), as well as many
Google.RTM. Android.TM. based phones (e.g., Motorolla.RTM.,
HTC.RTM., or Samsung.RTM. phones running the Android.RTM. operating
system), have been advertised to have tethering software and
functionality that enables these devices to act as a data
communications modem and/or gateway for a separate PCD, such as a
laptop computer (e.g., 112a of FIG. 1). In a scenario where a user
of a PCD is lacking access to the Internet via a wireless network
service (e.g., a cellular or a WiMAX network), a phone (having such
network access) can be tethered or otherwise coupled to the PCD to
allow the PCD to gain access to the cell phone user's subscribed
network service (e.g., a subscribed cellular service provided by
Verizon.RTM., AT&T.RTM., Sprint.RTM., T-Mobile.RTM., etc.).
[0005] As would be understood by those skilled in the art,
tethering generally facilitates a first stand-alone computing
device (e.g., a laptop or mini-computer), not having a desired
network access at a particular time or location, to utilize a
second stand-alone computing device (e.g., a cellular phone or PDA
having a desired network service) as an external modem and/or
gateway to provide the PCD with linked access to the desired
network services (e.g., broadband access to the Internet). In this
scenario, a tethered device (See e.g., cellular phone 112b) acts as
a burdened, slave device for a master tetheree device (See e.g.,
laptop computer 112a). As would be understood by those skilled in
the art, a master-slave model in data communications occurs when a
master, controller device or process has unidirectional control
over one or more slave device components. Generally, a tethered
(slave) device is not designed to function independently of a
tetheree (or master) device, while the two devices are paired in a
routed data communications session. This is due to the fact that a
significant amount of the tethered device's data processing and
communications capability, along with its power and memory
resources, are actively being consumed to facilitate the tetheree
device's communications to a proprietary network service that is
associated with the tethered device. In most scenarios, the
tethered device's user interface is not accessible or practically
available to its user during tethering, nor is its communications
functionality.
[0006] Tethering scenarios that facilitate sharing access to a
subscriber-based proprietary network typically require utilization
of a subscriber identification module (SIM), or some other imbedded
identity module, to authenticate the identity of a network service
subscriber attempting to access the proprietary network. In other
scenarios, tethering may not require use of a subscriber's SIM to
access other types of data communications networks (e.g., some
public Wireless Local Area Networks or WLANs). By way of example,
if a user's PCD is not equipped with a transceiver allowing the PCD
to access a public WiFi.TM. network (e.g., broadband access to the
Internet not requiring secure account authentication), the PCD may
be tethered to a cellular phone or PDA having a WiFi.TM.
transceiver, to allow the PCD to access the public WiFi.TM.
network.
[0007] Several deficiencies exist with modern tethering scenarios
(See e.g., the tethering configuration between the tetheree laptop
112a and the tethered cell phone or PDA 112b of FIG. 1). A few of
these deficiencies include, but are not limited to, the
following:
[0008] 1) a tethered device (the device acting as a modem and/or
gateway for another device 112b) is typically not separately
functional during the period of time when it is being used as an
external modem (when it is in a "tethering mode"); if the device is
functional, it will be significantly burdened by the tethering
functions occurring in the background, and normal application
processing and networking functions may be temporarily burdened to
the point where they become impractical;
[0009] 2) a tethered device 112b, acting as a connected dongle, is
often bulky and awkward to keep connected by wireline coupling to a
tetheree PCD 112a (the device using the tethered device as an
external modem);
[0010] 3) tethering network access authentication sessions
generally require continuous use of the tethered device's 112b
processor in order to facilitate access to internal subscriber
authentication information and routed data communications between a
tetheree device 112a and a network, thereby consuming the tethered
device's 112b resources (e.g., battery power, processing power,
available volatile memory, etc.) and limiting an available data
transfer rate for the tethered device;
[0011] 4) a tethered device 112b, such as cellular phone or a PDA,
often has inadequate battery life to provide sufficient periods of
wireless tethered communications along with the device's primary
functions as a stand-alone computing device; this may require the
device to be charged multiple times during the same day, thereby
reducing or otherwise crippling its extended mobility;
[0012] 5) a tethered device 112b is susceptible to unwanted
computer viruses as well as other malware uploads from afflicted
tetheree PCDs 112a (or vice versa) when the two devices are
connected in networked communications; and
[0013] 6) private and personal information resident on a tethered
device 112b can be accessed or corrupted by or through a tetheree
device 112a or a third party device 104a connected to the tetheree
PCD via a network (e.g., over the Internet) 102 when the devices
are linked during a tethered communications process.
[0014] In a tethering scenario, a tetheree (e.g., a PCD such as a
laptop, tablet computer or an electronic book device) can be
connected to a proprietary network service by using a tethered
device (e.g., a device such as a cellular phone or a PDA) as a
gateway. Generally the tethered device provides the tetheree with
temporary access to its network service account by facilitating
network subscriber authentication while communicating with the
tethered device's service provider. For many service providers in
the United States and abroad, network subscriber authentication is
facilitated when a service provider verifies information contained
on a subscriber resident device's identification module or SIM
card.
[0015] As would be understood by those skilled in the art, SIM
cards are smart cards that may be configured to fit inside a mobile
computing device (e.g., securely under a removable battery
component), such as a cellular phone or a PDA device. In other
devices identity modules or SIM cards may be built into the
hardware memory of the device, such that the identification module
is specifically designed not to be separated from the
communications device as a detachable unit. Identity modules and
SIM cards can provide for the identification of a subscribed user
to a network access provider, allowing the user to access services
and data that may include, but are not limited to, telephony,
email, text messaging, Internet usage, GPS, etc.
[0016] An identity module, or a SIM card, generally includes a
microprocessor unit as well as on-chip memory to process commands
and to store user data, such as contacts and a limited amount of
media content, and to store the SIM card's operating instructions.
As would be understood by those skilled in the Art, identity
modules and SIM cards also provide network specific information
used to identify and authenticate subscribers of a cellular network
service, including, but not limited to, at least the following
information: an Integrated Circuit Card ID (ICC-ID), an
International Mobile Subscriber Identity (IMSI), an Authentication
Key (Ki), and a Local Area Identity (LAI).
[0017] Each identity module or SIM can be internationally
identified by an ICC-ID stored in the module's memory and
optionally engraved or printed on a physical SIM card's exterior.
The ICC-ID is defined by the ITU-T recommendation and is generally
up to 19 or 20 digits long. Identity modules and SIM cards may also
be identified on their individual service provider networks by
holding unique IMSIs. An IMSI is a unique number that is associated
with all GSM, UMTS, LTE, LTE Advanced, etc. network mobile phone
users. An International Mobile Subscriber Identity is up to 15
digits long. The first three digits represent the country code,
followed by the network code. The remaining digits, up to fifteen,
represent the unique subscriber number from within the network's
customer base.
[0018] An identity module's or a SIM's authentication key (Ki) is
generally a 128-bit value used in authenticating the users of a
proprietary network. Each SIM holds a unique Ki assigned to it by a
service provider during a SIM registration process. The Ki is also
stored on a database (e.g., an authentication Center or AuC) within
the service provider's network infrastructure. Generally, an
identity module or SIM card does not allow a particular Ki to be
obtained using the smart-card interface. Instead, the SIM card can
provide a specialized function that allows a PCD to pass data to
the card to be signed with the Ki. This makes usage of the SIM card
mandatory unless the Ki can be extracted from the SIM card, or a
service provider is willing to reveal or duplicate a Ki. In
practice, most service providers prefer to keep only one copy of a
particular Ki per customer account so that duplicate and/or
separate SIM cards would need to be purchased by the customer to
facilitate multi subscriber account access.
[0019] A subscriber authentication process may include a subscriber
PCD (having an identity module or SIM card therein) powering on and
then obtaining the IMSI from SIM card memory. The subscriber PCD
then passes the IMSI to its registered service provider that is
requesting access authentication. The subscriber PCD may further be
required to pass a personal identification number (PIN) to the SIM
card before the SIM card will reveal the IMSI information to the
service provider.
[0020] After receiving the IMSI, the service provider searches its
database for the incoming IMSI's associated Ki. The service
provider then generates a Random Number (RAND, a nonce that is used
only once) and signs it with the Ki associated with the IMSI (and
stored on the SIM card), computing another number known as Signed
Response 1 (SRES1). The service provider then sends the RAND to the
PCD, which passes it to the identity module or SIM card. The
identity module of SIM card signs it with its Ki, producing SRES2,
which it subsequently returns to the PCD, along with encryption key
Kc. The subscriber's PCD passes SRES2 on to the service provider
via the network. The service provider then compares its computed
SRES1 with the received computed SRES2. If the two numbers match,
the SIM is authenticated and the PCD is granted access to the
service provider's network. Subsequently, the Kc may be utilized to
encrypt all further communications between the subscriber PCD and
the service provider network.
[0021] A common scenario may exists where a first stand-alone PCD
with WiFi.TM. communications capability is not in proximity to a
free public WiFi.TM. access point. For example, this may occur when
a user in an automobile, at an airport, staying in a hotel, etc. In
these scenarios, a user may only have access to a proprietary
WiFi.TM. or WiMAX.TM. network that requires them to pay exorbitant
hourly or day-use fees to access the private network. In other
scenarios, access to a wireless local access network, or WLAN, may
simply be unavailable at a PCD's present location.
[0022] To remedy these scenarios some service providers offer
device-specific plug-in cellular transceiver/antenna components
(e.g., USB transceiver 110b or PCI card transceiver 114b of FIG. 1)
that have a service subscriber's identification and account access
data built into the plug-in device, such that a subscriber is
capable of purchasing this additional access device and associated
service to access a proprietary network (e.g., a cellular broadband
network) using the additional service provider device. These
additional plug-in devices can provide an individual network user's
PCD with cellular broadband access in accordance with varying
access provider specific data-rate plans, which may be separate
from an existing customer's cellular phone or PDA data rate plan.
Generally, a customer with a cellular telephone or a PDA pays fees
for both their cellular phone network data access and their
additional PCD modem's network data access as a separate monthly or
annual subscriber fees.
[0023] FIG. 1 depicts one example of a modern distributed computing
system 100 where several subscriber devices 108a-c, 110a, 112a, and
114a can independently access a service provider's network using
various internal (e.g., those associated with cell phones 108a-c)
and external communications transceivers (e.g., any of proprietary
transceiver devices 110b, 112b, and 114b). The modern distributed
computing system 100 may include, but is not limited to: a data
communications network 102 (e.g., including WANs, LANs and backhaul
network components), various distributed server devices 104a-c
(e.g., associated with various control centers/devices, switching
centers, Internet servers, proxy servers, etc.), various cellular
network base stations 106a-b, various stand-alone personal
communications devices 108a-c (e.g., cellular phones or PDAs having
internal subscriber SIMs and subscriber network transceivers), as
well as various tethered personal computing devices 110a, 112a, and
114a (e.g., tablet computers, e-book devices, and laptop or netbook
computers) that are connected to various tethered devices,
including, USB-connected transceivers 110b, cellular phone
(tethering) transceivers 112b, and PCI card or laptop plug-in
transceivers 114b.
[0024] FIG. 2 depicts one example of a modern Multi-Function
Computing Device (MFCD) 200 (e.g., such as a cellular phone or a
PDA device) having at least the following components: a central
processing unit/digital signal processor 202, a transcoder 204, a
system memory 206 including both volatile (RAM) and nonvolatile
(ROM) memory components, a user interface/display 208, a smart
card/smart card reader 210, a universal serial bus (USB) 212, a
flash drive memory component 214, a rechargeable DC power supply
216, a WiFi.TM. transceiver 218, a Bluetooth.TM. transceiver 220, a
GPS transceiver 222, a cellular network transceiver 224, an audio
amplifier 226, a speaker 228, a microphone 230, a MEMS unit 232,
and a system bus 234.
[0025] The MFCD 200 may include one or more different
communications transceivers (e.g., WiFi.TM. 218, Bluetooth.TM. 220,
GPS 222, and Cellular 224 transceivers) for communicating over both
Local Area Networks (e.g., LANs, including WiFi.TM. enabled
networks) and Wide Area Networks (e.g., WANs, including cellular
and satellite communications networks). In order for the MFCD 200
to access a proprietary cellular communications network that can
provide for both digital telephony and Internet data access to the
Internet, the MFCD 200 will typically be required to provide
subscriber identity information to authenticate access with a local
network service provider. This authenticated access (the process of
which is described above) generally requires communication between
a network service provider (e.g., authentication with either
network base station 106a or 106-b of FIG. 1) and the MFCD's 200
internal SIM card 210.
[0026] Even with the advent of modern tethering technologies, most
network subscribers (with a single network service account) have
only one SIM card or identification module within their MFCD 200.
This single SIM card may only provide for subscriber account access
with a single protected SIM authentication key (Ki). As such, these
subscribers are only able to utilize one PCD at a time to access
their network subscriber account. Switching their single SIM card
between devices (only possible when both PCDs have SIM readers,
such as a pair of cellular phones) is often cumbersome and
time-consuming. Further, modern tethered standalone transceiver
devices heavily burden and/or incapacitate a tethered device (the
device acting as a modem) in order to connect a tetheree device to
a proprietary communication network. Therefore it would be
beneficial to have a portable gateway device that was physically
and functionally separate or optionally separable from a user's
PCD. It would also be advantageous if this portable gateway could
facilitate shared access and easy switching amongst multiple
subscriber devices without burdening functionality and/or resources
of any of a user's standalone PCDs. It would also be beneficial if
this device could be adapted to facilitate shared access to a
proprietary WiFi.TM., WiMAX.TM., and/or cellular communications
network.
BRIEF DESCRIPTION OF THE DRAWINGS
[0027] Exemplary and alternative examples of the present invention
are described in detail below with reference to the following
Figure drawings:
[0028] FIG. 1 illustrates a perspective view of a distributed
computing system associated with the Prior Art;
[0029] FIG. 2 illustrates a block diagram of a personal computing
device associated with the Prior Art;
[0030] FIG. 3 illustrates a perspective view of a distributed
computing system with multiple portable gateway devices in
accordance with embodiments of the present invention;
[0031] FIG. 4 illustrates a perspective view of a personal
computing device with a removable portable gateway device and an
attachable power supply component in accordance with an embodiment
of the present invention;
[0032] FIG. 5 illustrates a block diagram of a portable gateway
device with an attachable power supply component (See e.g., FIG. 4)
in accordance with an embodiment of the present invention;
[0033] FIG. 6 illustrates a block diagram of a personal computing
device having a detachable portable gateway device (See e.g., FIG.
4) in accordance with an embodiment of the present invention;
[0034] FIG. 7 illustrates a perspective view of a personal
computing device located in proximity to an autonomous portable
gateway device in accordance with an embodiment of the present
invention;
[0035] FIG. 8 illustrates a block diagram of an autonomous portable
gateway device (See e.g., FIG. 7) in accordance with an embodiment
of the present invention;
[0036] FIG. 9 illustrates a flow diagram of a process that utilizes
a portable gateway device to access proprietary network services
(e.g., those associated with WiFi, WiMAX, and 3G or 4G cellular
networks) in accordance with embodiments of the present
invention;
[0037] FIG. 10 illustrates a communication flow diagram of
processes where multiple personal computing devices simultaneously
access separate networks in accordance with an embodiment of the
present invention;
[0038] FIG. 11 illustrates a communication flow diagram of a
process where a personal computing device accesses a proprietary
WiFi or WiMAX network using a portable gateway device in accordance
with embodiments of the present invention; and
[0039] FIG. 12 illustrates a communication flow diagram of a
process where a personal computing device accesses a proprietary
cellular network using a portable gateway device in accordance with
embodiments of the present invention.
DETAILED DESCRIPTION
[0040] In accordance with exemplary embodiments of the present
invention, FIG. 3 illustrates a distributed computing system 300
including various wireline and wireless computing devices that may
be utilized to implement any of the data communications processes
associated with various embodiments of the present invention (e.g.,
processes associated with any of FIGS. 9-12). The distributed
computing system 300 may include various personal computing devices
(PCDs) 312a-c, 314, 316, and 318 having access to a service
provider network 302 (e.g., including a backhaul) by communicating
wirelessly with various server provider devices, including base
stations 306a-b, and 310, as well as any number or router 308 or
server and controller computing devices 304a-c common in the Art
using various portable gateway devices 320a-c associated with
embodiments of the present invention.
[0041] As would be understood by those skilled in the Art, in most
digital communications networks, the backhaul portion of a data
communications network 302 may include the intermediate, generally
wireline, links between a backbone of the network, and the
sub-networks or network base stations 306a-b, and 310, located at
the periphery of the network. For example, user equipment (also
referred to herein as PCDs) 312a-c, 314, 316, and 318 communicating
with one or more network base stations 306a-b, and 310 may
constitute a local sub-network. Whereas the network connection
between any of the network base stations 306a-b, and 310 and the
rest of the world initiates with a link to the backhaul portion of
an access provider's communications network 302 (e.g., via a point
of presence).
[0042] In an embodiment, any of the portable gateway devices
320a-c, and/or network base stations 306a-b, and 310 may function
collaboratively to implement any of the shared network access
processes associated with various embodiments of the present
invention. Further, any of the shared network access processes may
be carried out via any common communications technology known in
the Art, such as those associated with modern Global Systems for
Mobile (GSM), Universal Mobile Telecommunications System (UMTS),
Long Term Evolution (LTE) network infrastructures, etc. In
accordance with a standard GSM network, any of the service provider
devices 304a-c, 306a-b, 308, 310 may be associated with a base
station controller (BSC), a mobile switching center (MSC), or any
other common service provider device known in the art, such as a
radio resource manager (RRM). In accordance with a standard UMTS
network, any of the service provider devices 304a-c, 306a-b, 308,
310 may be associated with a network resource controller (NRC), a
serving GPRS support node (SGSN), or any other common service
provider controller device known in the art, such as a radio
resource manager (RRM). In accordance with a standard LTE network,
any of the service provider devices 304a-c, 306a-b, 308, 310 may be
associated with an eNodeB base station, a mobility management
entity (MME), or any other common service provider controller
device known in the art, such as a radio resource manager
(RRM).
[0043] In an embodiment, any of the service provider devices
304a-c, 306a-b, 308, 310 as well as any of the PCDs 312a-c, 314,
316, and 318 may be configured to run any well-known operating
system, including, but not limited to: Microsoft.RTM. Windows.RTM.,
Mac OS.RTM., Google.RTM. Chrome.RTM., Linux.RTM., Unix.RTM., or any
well-known mobile operating system, including Symbian.RTM.,
Palm.RTM., Windows Mobile.RTM., Google.RTM. Android.RTM., Mobile
Linux.RTM., etc. In an embodiment, any of the service provider
devices 304a-c, 306a-b, 308, 310 may employ any number of common
server, desktop, laptop, and personal computing devices.
[0044] In an embodiment, any of the PCDs 312a-c, 314, 316, and 318
may be associated with any combination of common mobile computing
devices (e.g., laptop computers, netbook computers, tablet
computers, cellular phones, PDAs, handheld gaming units, electronic
book devices, personal music players, video recorders, etc.),
having wireless communications capabilities employing any common
wireless data communications technology, including, but not limited
to: GSM, UMTS, 3GPP LTE, LTE Advanced, WiFi, WiMAX, etc.
[0045] In an embodiment, the backhaul portion of the data
communications network 302 of FIG. 3 may employ any of the
following common communications technologies: optical fiber,
coaxial cable, twisted pair cable, Ethernet cable, and powerline
cable, along with any other wireless communication technology known
in the art. In an embodiment, any of the service provider devices
304a-c, 306a-b, 308, 310 as well as any of the PCDs 312a-c, 314,
316, and 318 may include any standard computing software and
hardware necessary for processing, storing, and communicating data
amongst each other within the networked computing system 300. The
computing hardware realized by any of the network computing system
300 devices (may include, but is not limited to: one or more
processors, volatile and non-volatile memories, user interfaces,
transcoders, modems, wireline and/or wireless communications
transceivers, rechargeable power supplies, etc.
[0046] Further, any of the portable gateway devices 320a-c, service
provider devices 304a-c, 306a-b, 308, 310, as well as any of the
PCDs 312a-c, 314, 316, and 318 may include one or more
computer-readable media (e.g., any common volatile or non-volatile
memory type) encoded with a set of computer readable instructions,
which when executed, can perform a portion of any of the shared
network access processes associated with various embodiments of the
present invention. In context with various embodiments of the
present invention, it should be understood that wireless
communications coverage associated with various data communication
technologies (e.g., network base stations 106a-b, and 310)
typically vary amongst different service provider networks based on
the type of network and the system infrastructure deployed within a
particular region of a network (e.g., differences amongst GSM,
UMTS, LTE, LTE Advanced, WiFi and WiMAX based networks and the
technologies deployed in each network type).
[0047] FIG. 4 illustrates a perspective view 400 of a personal
computing device 402 (e.g., a cellular phone or a PDA or any of the
other PCDs 312a-c, 314, 316, and 318 of FIG. 3) and a removable
portable gateway device 404a-b that has an optional, attachable
power supply component 412 in accordance with an embodiment of the
present invention. In an embodiment, the portable gateway device
404a-b and the power supply component 412 include all the hardware
components depicted in the block diagram of FIG. 5. In an
embodiment the portable gateway device 404a-b may be removed from
the PCD 402 by pressing or turning the removable device 404a-b,
such that it readily detaches from the PCD 402 without much effort
on the part of a user. Subsequent to being removed from the PCD
402, the portable gateway device 404a-b may be joined with the
power supply component 412 by pressing the two components together,
such that they lock securely and act as a single autonomous device.
In an embodiment, the autonomous portable gateway device 404a-b,
412 may be a snap fit device where peripheral components 410a-c of
the portable gateway device 404a-b lock with peripheral recesses
414a-c of the power supply component 412, when joined. It should be
understood that the portable gateway device 404a-b has an identity
module embodied 406 therein and an optional array of indicator
lights to signal power level and/or communications signal strength
for communications with a neighboring base station (e.g., any of
base stations 306a-b, and 310 of FIG. 3). It should also be
understood that the power supply component 412 has a rechargeable
battery component 416 (e.g., such as a rechargeable lithium ion
battery) stored therein.
[0048] FIG. 5 illustrates a block diagram 500 of a portable gateway
device 502 with an attachable power supply component 526 (See e.g.,
FIG. 4) in accordance with an embodiment of the present invention.
The portable gateway device may be representative of any of the
portable gateway devices 320a-c depicted in FIG. 3. In an
embodiment, the portable gateway device 502 may include, but is not
limited to, the following components: a central processing/digital
signal processing component 502, a transcoders 506, an identity
module 508 (e.g., such as a smart card or SIM card), a serial bus
510, a system memory 512, an array of indicator lights 514, a short
range communications transceiver 516 (i.e., such as a Bluetooth or
a WiFi transceiver) and one or more long range transceiver
components 518, 520 (i.e., such as a Cellular transceiver and/or a
WiMAX transceiver), and a system bus 522 facilitating communication
amongst all components of the portable gateway device 502.
[0049] In an embodiment, the CPU/DSP 504 may include an arithmetic
logic unit (ALU, not shown) that performs arithmetic and logical
operations and one or more control units (CUs, not shown) that
extract instructions and stored content from memory and then
executes and/or processes them, calling on the ALU when necessary
during program execution. The CPU 504 may be responsible for
executing all shared data communications and authentication
software stored on the portable gateway device's 502 volatile (RAM)
and non-volatile (ROM) system memories, 512. In an embodiment, the
identity module 508 (e.g., such as a smart card or SIM card) may
facilitate the portable gateway device's 502 authentication with a
proprietary network service provider. In an embodiment, one or more
users of local PCDs (e.g., any of PCDs 312a-c, 314, 316, and 318)
may communicate with the portable gateway device's 502 short range
communications transceiver 516 (i.e., such as a Bluetooth or a WiFi
transceiver) to request individual and/or simultaneous access to a
proprietary network service. In an embodiment, the portable gateway
device 502 may authenticate one or more shared user access requests
at the portable gateway device 502 and then submit/forward one or
more data transfer requests (along with authentication information
associated with the identity module 508) to a remote service
provider device (e.g., any of base stations 306a-b, and 310 of FIG.
3) using a longer range transceiver component 518, 520 (i.e., such
as a Cellular transceiver and/or a WiMAX transceiver). After
authentication with a remote service provider device, the portable
gateway device 502 may act as a relay/gateway between one or more
PCDs (e.g., any of PCDs 312a-c, 314, 316, and 318) and a service
provider device (e.g., any of base stations 306a-b, and 310)
offering data communications services.
[0050] In an embodiment, the attachable power supply component 526
may include both a rechargeable power supply 528 (e.g., a lithium
ion battery), a power charging unit 530 for allowing the attachable
power supply component 526 to plug into a shore power source (not
shown), and a connector 524 for connecting the attachable power
supply component 526 to the portable gateway device 502.
[0051] FIG. 6 illustrates a block diagram of a personal computing
device 600 having a detachable portable gateway device (See e.g.,
FIG. 5) in accordance with an embodiment of the present invention.
The PCD 600 may be representative of any of the PCDs 312a-c, 314,
316, and 318 depicted in FIG. 3. In an embodiment, the PCD 600 may
include, but is not limited to, the following components: a central
processing/digital signal processing component 602, a transcoder
604, a system memory 606, a detachable PGD plug-in component 608, a
serial bus 610, a flash drive 612, a rechargeable power supply 614,
a user interface/display 616, a short range communications
transceiver 620 (i.e., such as a Bluetooth or a WiFi transceiver)
and one or more longer range transceiver components 618, 622,
(i.e., such as a WiMAX and/or a GPS transceiver), and audio
amplifier 624, a speaker 626, a MEMS unit 630, and a system bus 632
facilitating communication amongst all components of the PCD
632.
[0052] In an embodiment, the CPU/DSP 602 may include an arithmetic
logic unit (ALU, not shown) that performs arithmetic and logical
operations and one or more control units (CUs, not shown) that
extract instructions and stored content from memory and then
executes and/or processes them, calling on the ALU when necessary
during program execution. The CPU/DSP 602 may be responsible for
executing all shared data communications and authentication
software stored on the PCD's 600 volatile (RAM) and non-volatile
(ROM) system memories 606.
[0053] FIG. 7 illustrates a perspective view 700 of a personal
computing device (PCD) 702 located in proximity to an autonomous
portable gateway device (PGD) 704, in accordance with an embodiment
of the present invention. It should be understood that the PCD 702
is substantially or at least partially representative of the PCD
704 depicted in FIG. 2, and that the portable gateway device 704
may be substantially or at least partially representative of the
PGD 800 depicted in FIG. 8. Accordingly, similar device component
descriptions are not being repeated here for brevity, as they are
deemed to be repetitive in nature. In an embodiment, the portable
gateway device 704 has an array of indicator lights 706 that may
depict signal strength between the PCD 702 and the portable gateway
device 704, the signal strength between the portable gateway device
704 and a base station (not shown, e.g., any of base stations
306a-b, and 310 of FIG. 3), and/or a battery power level of the PGD
704.
[0054] FIG. 8 illustrates a block diagram of an autonomous portable
gateway device (PGD) 800 (See e.g., the analogous, detachable PGD
704 of FIG. 7) in accordance with an embodiment of the present
invention. The autonomous PGD 800 may be representative of any of
the portable gateway devices 320a-c depicted in FIG. 3. In an
embodiment, the portable gateway device 800 may include, but is not
limited to, the following components: a central processing/digital
signal processing component 802, a transcoder 804, an identity
module 808 (e.g., such as a smart card or SIM card), a serial bus
810, a system memory 806, an array of indicator lights 822, an
ON/OFF switch 814, a power supply/charging unit 812, a short range
communications transceiver 816 (i.e., such as a Bluetooth or a WiFi
transceiver) and one or more long range transceiver components 818,
820 (i.e., such as a Cellular transceiver and/or a WiMAX
transceiver), and a system bus 824 facilitating communication
amongst all components of the autonomous PGD 800.
[0055] In an embodiment, the CPU/DSP 802 may include an arithmetic
logic unit (ALU, not shown) that performs arithmetic and logical
operations and one or more control units (CUs, not shown) that
extract instructions and stored content from memory and then
executes and/or processes them, calling on the ALU when necessary
during program execution. The CPU 802 may be responsible for
executing all shared data communications and authentication
software stored on the autonomous PGD's 800 volatile (RAM) and
non-volatile (ROM) system memories, 806. In an embodiment, the
identity module 808 (e.g., such as a smart card or SIM card) may
facilitate the autonomous PGD's 800 authentication with a
proprietary network service provider. In an embodiment, one or more
users of local PCDs (e.g., any of PCDs 312a-c, 314, 316, and 318)
may communicate with the autonomous PGD's 800 short range
communications transceiver 816 (i.e., such as a Bluetooth or a WiFi
transceiver), independently or at the same time, to request
individual and/or simultaneous access to a proprietary network
service. In an embodiment, the autonomous PGD 800 may authenticate
one or more shared user access requests at the autonomous PGD 800
and then submit/forward one or more data transfer requests (along
with authentication information associated with the identity module
808) to a remote service provider device (e.g., any of base
stations 306a-b, and 310 of FIG. 3) using a longer range
transceiver component 818, 820 (i.e., such as a Cellular
transceiver and/or a WiMAX transceiver). After authentication with
a remote service provider device, the autonomous PGD 800 may act as
a relay/gateway between one or more PCDs (e.g., any of PCDs 312a-c,
314, 316, and 318) and a service provider device (e.g., any of base
stations 306a-b, and 310) offering data communications
services.
[0056] FIG. 9 illustrates a flow diagram 900 of a process that
utilizes a portable gateway device to access proprietary network
services (e.g., those associated with WiFi, WiMAX, and 3G or 4G
cellular networks) in accordance with embodiments of the present
invention. It should be understood that these processes 900 may be
executed independently or collectively using one or more
computer-executable programs stored on computer-readable media
located on one or more PCDs (e.g., any of PCDs 312a-c, 314, 316,
and 318), a PGD (e.g., any of PGDs 320a-c) and network service
provider devices (e.g., any of network base stations 306a-b, and
310). The process 900 is comprised of flow diagram steps 902, 904,
906, 908, 910, 912, 914, 916, 918, 920, 922, 924, 926, and 928.
Process 900 is depicted/described in sufficient textual and
illustrative detail to facilitate understanding by one of ordinary
skill in the Art reviewing FIG. 9 in combination with FIGS.
3-8.
[0057] FIG. 10 illustrates a communication flow diagram of process
1000 where multiple personal computing devices simultaneously
access separate networks (e.g., WiFi, WiMAX, and/or 3G or 4G
Cellular networks) in accordance with an embodiment of the present
invention. In an embodiment, the system includes a first PCD1 1002
(e.g., optionally, a PGD host, See e.g., FIG. 4), a second PCD2
1004, a PGD 1006, a WiFi or WiMAX network 1010, and a cellular
network 1008. It should be understood that these process 1000 may
be executed independently or collectively using one or more
computer-executable programs stored on computer-readable media
located on one or more PCDs (e.g., any of PCDs 312a-c, 314, 316,
and 318), a PGD (e.g., any of PGDs 320a-c) and network service
provider devices (e.g., any of network base stations 306a-b, and
310). The process 1000 is comprised of flow diagram steps 1012,
1014, 1016, 1018, 1020, 1022, 1024, 1026, 1028, 1030, 1032, and
1034. Process 1000 is depicted/described in sufficient textual and
illustrative detail to facilitate understanding by one of ordinary
skill in the Art reviewing FIG. 10 in combination with FIGS.
3-8.
[0058] FIG. 11 illustrates a communication flow diagram of a
process 1100 where a personal computing device accesses a
proprietary WiFi or WiMAX network using a portable gateway device
in accordance with embodiments of the present invention. In an
embodiment, the system includes a first PCD 1102, a PGD 1104, and a
WiFi or WiMAX network 1106. It should be understood that this
process 1100 may be executed independently or collectively using
one or more computer-executable programs stored on
computer-readable media located on one or more PCDs (e.g., any of
PCDs 312a-c, 314, 316, and 318), a PGD (e.g., any of PGDs 320a-c)
and network service provider devices (e.g., any of network base
stations 306a-b, and 310). The process 1100 is comprised of flow
diagram steps 1108, 1110, 1112, 1114, 1116, and 1118. Process 1100
is depicted/described in sufficient textual and illustrative detail
to facilitate understanding by one of ordinary skill in the Art
reviewing FIG. 11 in combination with FIGS. 3-8.
[0059] FIG. 12 illustrates a communication flow diagram of a
process 1200 where a personal computing device accesses a
proprietary cellular network using a portable gateway device in
accordance with embodiments of the present invention. In an
embodiment, the system includes a first PCD 1202, a PGD 1204, and a
3G or 4G Cellular network 1206. It should be understood that this
process 1200 may be executed independently or collectively using
one or more computer-executable programs stored on
computer-readable media located on one or more PCDs (e.g., any of
PCDs 312a-c, 314, 316, and 318), a PGD (e.g., any of PGDs 320a-c)
and network service provider devices (e.g., any of network base
stations 306a-b, and 310). The process 1200 is comprised of flow
diagram steps 1208, 1210, 1212, 1214, 1216, and 1218. Process 1200
is depicted/described in sufficient textual and illustrative detail
to facilitate understanding by one of ordinary skill in the Art
reviewing FIG. 12 in combination with FIGS. 3-8.
[0060] While several embodiments of the present invention have been
illustrated and described herein, many changes can be made without
departing from the spirit and scope of the invention.
* * * * *