throbber
as) United States
`a2) Patent Application Publication 0) Pub. No.: US 2004/0127208 Al
`(43) Pub. Date: Jul. 1, 2004
`
`Nair et al.
`
`US 20040127208A1
`
`(54) SYSTEMS AND METHODS FOR SEAMLESS
`ROAMING BETWEEN WIRELESS
`NETWORKS
`
`(76)
`
`Inventors: Biju Nair, Buffalo Grove, IL (US);
`Ognjen Redzic, Chicago, IL (US);
`Martin Singer, Northbrook, IL (US);
`Robert Boxall, Elmhurst, IL (US)
`
`Correspondence Address:
`Attn: James E. Eakin
`Pillsbury Winthrop LLP
`Intellectual Property Group
`2475 HanoverStreet
`Palo Alto, CA 94304 (US)
`
`(21) Appl. No.:
`
`10/634,536
`
`(22)
`
`Filed:
`
`Aug. 4, 2003
`
`Related U.S. Application Data
`
`(60) Provisional application No. 60/400,615, filed on Aug.
`2, 2002.
`
`Publication Classification
`
`Ente C07 caccccsssssssssssnssessesnstsnssnstsevee H04Q 7/00
`(SL)
`(52) US. Ch.
`cecessssssssssstsessetsstnstvasnetnstnesvesse 455/420
`
`(57)
`
`ABSTRACT
`
`A method for the seamless switching of a wireless device
`between wireless wide area networks (WWANSs) and wire-
`less local area networks (WLANs) includes automatically
`detecting the available WWANs and WLANs,selecting one
`of the available networks for use by the wireless device, and
`connecting the wireless device to the selected network. The
`method also includes maintaining the network connection by
`monitoring the connection and, upon determining that the
`connection has been lost, selecting a another available
`network for use and connecting the wireless device the other
`network. Additionally, the method communicates informa-
`tion about the availability networks and connectionstatus to
`a user of the wireless device, which allows the user to
`manually switch the wireless device connection from the
`automatically selected available network to another avail-
`able network. Further, a wireless device implements the
`above described method.
`
` ----------- 4
`
`Wireless
`Device
`
`14
`
`16
`
`18
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 1
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 1
`
`

`

`Patent Application Publication
`
`Jul. 1, 2004 Sheet 1 of 6
`
`US 2004/0127208 Al
`
`10
`
`18
`
`Figure1
`
`Wireless
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 2
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 2
`
`

`

`US 2004/0127208 Al
`
`28
`
`
`
`Patent Application Publication
`
`12
`
`Jul. 1, 2004 Sheet 2 of 6
`
`WLANH/W-WWANH/W_-ComboH/W|
` Figure2
`
`ConnectivityApplication
`
`Applications
`
` OperatingSystem
`
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 3
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 3
`
`

`

`Patent Application Publication
`
`Jul. 1, 2004 Sheet 3 of 6
`
`US 2004/0127208 Al
`
`Inter-subcomponent
`
`Communication
`
`3GUISub-
`
`component
`
`UlComponent
`
`2,
`ns—c
`-2
`=¢€
`$8
`=
`
`Figure3
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 4
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 4
`
`

`

`<x
`
`
`
`RulesEngine
`
`c O
`
`o
`oS Cc
`26
`5 oO
`QO 2®
`0 ~/
`2—
`Oo
`
`Patent Application Publication
`
`Jul. 1, 2004 Sheet 4 of 6
`
`US 2004/0127208 Al
`
`Figure4
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 5
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 5
`
`

`

`Patent Application Publication
`
`Jul. 1, 2004 Sheet 5 of 6
`
`US 2004/0127208 Al
`
` Search for
`
`Network
`detected
`
`
`
`oO 100
`network
`?
` 108
`
`Connectto
`
`
`
`network per
`rules engine
`
`recommendation
`
`
`Connection
`maintenance
`
`monitoring and
`
`106
`
`
`
`Search rules
`
` engine
`
`110
`
`Figure 5
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 6
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 6
`
`

`

`Patent Application Publication
`
`Jul. 1, 2004 Sheet 6 of 6
`
`US 2004/0127208 A1
`
`110 ~
`
`112
`
`Monitor Current
`Connection
`
`
`Current
`connection
`loss ?
`
`
`
`User
`intervention
`
`
`
`
`
`2
`
`
`Other
`
`network(s)
`?
`
`Connect to other
`network
`
`Figure 6
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p.7
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 7
`
`

`

`US 2004/0127208 Al
`
`Jul. 1, 2004
`
`SYSTEMS AND METHODS FOR SEAMLESS
`ROAMING BETWEEN WIRELESS NETWORKS
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] The present application claims the benefit of pri-
`ority under 35 U.S.C. § 119(e) from U'S. Provisional Patent
`Application No. 60/400,615 filed on Aug. 2, 2002 to Nair, et
`al. and entitled “Seamless Roaming Between Wireless Net-
`works”.
`
`BACKGROUND OF THE INVENTION
`
`[0002]
`
`1. Field of the Invention
`
`[0003] The present invention relates generally to the field
`of wireless technology and, more particularly, to seamless
`roaming between wireless networks.
`
`[0004]
`
`2. Description of the Related Art
`
`[0005] Wireless technology allows electronic devices to
`communicate with one another without the use of physical
`lines (e.g., wire or fiber optic cable), and accordingly, has
`become increasingly popular in recent years. There are
`different types of access networksin wireless technology, for
`example, the wireless local area network (WLAN) and the
`wireless wide area network (WWAN). WWANsare used by
`traditional cellular companies to provide high-mobility
`access (e.g., for users moving in cars) over a broad coverage
`area. WLANs can be used in buildings (e.g., homes or
`businesses) for stationary or low mobility access.
`
`[0006] While WLANs provide higher throughput rates
`(e.g., ranging from 11 Mbps to 54 Mbps), such networks
`generally do not provide a broad area of coverage, and thus,
`are not always suitable for high mobility access. On the
`other hand, while WWANSsprovide broad ranging coverage,
`they generally have lower throughputrates.
`
`[0007] Previously developed techniques have provided for
`connections to both a WLAN and a WWAN bya mobile
`device. With these techniques, separate device applications
`were used to independently support and manage different
`kinds of connections. That is, one application would be used
`for WWAN connections, and another application would be
`used for WLAN connections. This was problematic in that
`the two applications were independent, and thus, did not
`provide the ability to coordinate connections for different
`types of wireless networks. Thus, whenever there wasa loss
`of connection as a mobile device was moved out of the
`
`coverage area, of one kind of wireless network into the
`coverage area of another kind of network, the previously
`developed techniques were not able to automatically switch
`connections. Instead, a user had to manually switch from
`one application managing hardware for a connection of the
`first kind of wireless network to a different application
`managing hardware for a connection of the second kind of
`wireless network. In order to make this manual switch, the
`user was required to shut down all applications using the
`external network connection and then, after the switch was
`made,
`to reinitiate network connectivity and restart all
`applications. Accordingly, the previously developed tech-
`niques were disruptive,
`time consuming, and not user
`friendly.
`
`[0008] Therefore, what is needed is a way to automatically
`and seamlessly switch between and among different types of
`wireless networks.
`
`SUMMARYOF THE INVENTION
`
`[0009] According to embodiments of the present inven-
`tion, systems and methods provide uninterrupted and ubiq-
`uitous wireless access, with seamless hand-off between
`different kinds of networks. Thus, applications are not
`affected as a user roams between and among WLANsand
`WWANS. The embodiments of the present invention may
`also facilitate handing off a user to WLANs, whenever
`possible to more cost effectively use the available WWAN
`bandwidth. Important technical advantages of the present
`invention are readily apparent to one skilled in the art from
`the following figures, descriptions, and claims.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0010] For a more complete understanding of the present
`invention, for further features and advantages, applicants
`now make the following description, taken in conjunction
`with the accompanying drawings, in which:
`
`FIG.1 illustrates an environment in which systems
`[0011]
`and methods, according to embodiments of the present
`invention, may operate;
`
`FIG.2 illustrates an exemplary system for seam-
`[0012]
`less roaming between wireless networks according to an
`embodiment of the present invention;
`
`FIG.3 illustrates an exemplary user interface com-
`[0013]
`ponent according to an embodimentof the present invention;
`
`[0014] FIG. 4 illustrates an exemplary core component
`according to an embodimentof the present invention;
`
`[0015] FIG. 5 illustrates a flow chart of an exemplary
`method for seamless roaming between wireless networks
`according to an embodiment of the present invention; and
`
`[0016] FIG. 6 illustrates a flow chart of an exemplary
`method for network connection monitoring and maintenance
`according to an embodiment of the present invention.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`
`Turningfirst to the nomenclature of the specifica-
`[0017]
`tion,
`the detailed description that follows is represented
`largely in terms of processes and symbolic representations
`of operations performed by conventional computer compo-
`nents, such as a local or remote central processing unit
`(CPU), processor, server, or other suitable processing device
`associated with a general purpose or specialized computer
`system, memory storage devices operatively associated with
`the processing device, and connected local or remote display
`devices. These operations may include the manipulation of
`data bits by the processing device and the maintenance of
`these bits within data structures resident in one or more of
`
`the memory storage devices. Such data structures impose a
`physical organization upon the collection of data bits stored
`within computer memory and represent specific electrical or
`magnetic elements. These symbolic representations are the
`means used by those skilled in the art of computer program-
`ming and computer construction to most effectively convey
`teachings and discoveries to others skilled in the art.
`
`[0018] For purposes of this discussion, an application,
`process, method, routine, or sub-routine is generally con-
`sidered to be a sequence of computer-executed steps leading
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 8
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 8
`
`

`

`US 2004/0127208 Al
`
`Jul. 1, 2004
`
`to a desired result. These steps generally require manipula-
`tions of physical quantities. Usually, although not necessar-
`ily always,
`these quantities take the form of electrical,
`magnetic, or optical signals capable of being stored, trans-
`ferred, combined, compared, or otherwise manipulated. It is
`conventional for those skilled in the art to refer to these
`
`signals as bits, values, elements, symbols, characters, text,
`terms, numbers,records,files, or the like. It should be kept
`in mind, however, that these and some other terms should be
`associated with appropriate physical quantities for computer
`operations, and that these terms are merely conventional
`labels applied to physical quantities that exist within and
`during operation of the computer.
`
`should also be understood that automatic
`It
`[0019]
`manipulations within the computer system are often referred
`to in terms such as adding, comparing, moving, searching, or
`the like, which are typically associated with manual opera-
`tions performed by a human operator. It must be understood
`that, in most instances, no involvement of the human opera-
`tor is necessary, or even desirable, in the present invention.
`However, some of the operations described herein are
`machine operations performed in conjunction with the
`humanoperator, or user, that interacts with the computer or
`system. Therefore, unless noted as a manual, user operation,
`all operations are presumed to be automatic.
`
`In addition, it should be understood that the pro-
`[0020]
`grams, processes, methods,and the like, described herein are
`but an exemplary implementation of the present invention
`and are not related, or limited, to any particular computer,
`system, apparatus, or computer language. Rather, various
`types of general purpose computing machines or devices
`may be used with programs constructed in accordance with
`the teachings described herein. Similarly,
`it may prove
`advantageous to construct a specialized apparatus, or hard-
`ware device, to perform one or more of the method steps
`described herein by way of dedicated computer systems with
`hard-wired logic or programsstored in non-volatile memory,
`such as read-only memory (ROM).
`
`[0021] Overview
`
`[0022] According to embodiments of the present inven-
`tion, systems and methods provide automatic and seamless
`roaming between wireless networks, including between dif-
`ferent kinds of wireless networks
`(e.g.. WLAN and
`WWAN). Embodimentsof the presentinvention can provide
`seamless access between two disparate wireless access tech-
`nologies, such as a WLAN and a WWAN.The systems and
`methods of the present invention can provide or support
`automatic detection and connection to WLANs
`and
`WWANs.
`
`[0023] System For Seamless Roaming
`
`[0024] FIG. 1 illustrates an environment 10 in which
`embodiments of the present
`invention may operate. As
`depicted, environment 10 includes a plurality of wireless
`networks through which a wireless device 12 may migrate
`and communicate. These networks can be, for example, a
`wireless wide area network (WWAN) 14,a first wireless
`local area network (WLAN) 16, and a second WLAN 18.
`
`communications, including, but not limited to, analog cel-
`lular system, digital cellular system, Personal Communica-
`tion System (PCS), Cellular Digital Packet Data (CDPD),
`ARDIS, RAM Mobile Data, Metricom Ricochet, paging,
`and Enhanced Specialized Mobile Radio (ESMR). The
`wireless networks 14, 16, 18 may utilize or support various
`protocols. Exemplary protocols for WLANs16, 18 include
`IEEE 802.11, HomeRF, Bluetooth, HiperLAN andthe like.
`Exemplary protocols for WWAN 14include Time Division
`Multiple Access (TDMA, such as IS-136), Code Division
`Multiple Access (CDMA), 1xRTT, General Packet Radio
`Service (GPRS), Enhanced Data rates for GSM Evolution
`(EDGE), Global System for Mobile communications
`(GSM), Universal Mobile Telecommunications System
`(UMTS), and Integrated Digital Enhanced Network (iDEN)
`Packet Data. Each connection of a wireless network may
`have a respective identifier such as, for example, a particular
`Internet Protocol (IP) address. Transmissions over the wire-
`less networks 14, 16, 18 may be analog or digital. The
`wireless networks may include or be supported by a public
`switched telephone network (PSTN) and/or a private system
`(e.g., cellular system)
`implemented with a number of
`switches, wire lines, fiber-optic cable, land-based transmis-
`sion towers, space-basedsatellite transponders, and the like.
`In one embodiment, the wireless networks may include any
`other suitable communication system, such as a specialized
`mobile radio (SMR) system. Each wireless network 14, 16,
`18 may have a respective range of operation. The ranges of
`the various wireless networks can overlap in coverage.
`
`[0026] The wireless networks 14, 16, 18 can be main-
`tained or operated by the sameor different service providers.
`In general, a service provider can be an entity that delivers
`services to one or more users, who, for example, access the
`network with a wireless device. These services may include
`wireless service, and possibly a host of other services,
`including, for example, plain old telephone service (POTS),
`digital telephony service, cellular service, pager service, and
`the like. The user of the wireless device 12 can be a
`subscriber to one or more of the services provided by one or
`moreof the service providers with the wireless networks 14,
`16, 18.
`
`[0027] The wireless device 12 can be an electronic device
`with capability for communicating by wireless technology.
`Thus, wireless device 12 can be, for example, a laptop or
`desktop computer,
`a wireless personal digital assistant
`(PDA), a cellular phone, or any other wireless-capable,
`suitable electronic device. The wireless device 12 can be
`used by a respective user, who can move among and through
`the effective ranges of operation for the various wireless
`networks 14, 16, 18. If the wireless device 12 is within the
`range a particular wireless network, the device 12 will be
`able to communicate through a link of that wireless network.
`The wireless device 12 may run one or more applications
`that exchange data/information through wireless networks
`as the applications are run. Such an application can be, for
`example, a network browser that exchanges information
`with the distributed application known as the “World Wide
`Web.” Another exemplary application can be electronic mail
`or instant messaging services.
`
`[0025] Each wireless networks 14, 16, 18 can be a com-
`munication network that supports wireless communication.
`Each network supports at least one wireless link or device
`connection. As such, the networks may support a variety of
`
`In general, WLANs provide higher throughput
`[0028]
`rates (e.g., from 11 Mbps to 54 Mbpsand higher), butare not
`conducive to use in higher mobility applications (e.g., such
`as when a user is in a car). WWANscan be used in high
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 9
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 9
`
`

`

`US 2004/0127208 Al
`
`Jul. 1, 2004
`
`mobility applications, but do not provide as much through-
`put as WLANs. Thus, to increase throughput rates for the
`user of the wireless device 12, it is desirable to connect to
`a WLAN when one is available and connection to it is
`
`possible, while connecting to a WWAN when a WLAN
`connection is not available or possible.
`
`[0029] To provide uninterrupted and effective wireless
`access for the wireless device 12 in exemplary environment
`10, the present invention provides systems and methods so
`that WLANs and WWANsare able to automatically and
`seamlessly hand-off communications with the wireless
`device 12 as it roams between or among them, without the
`applications executing on the wireless device 12 being
`adversely affected.
`
`[0030] System For Seamless Roaming
`
`[0031] FIG. 2 illustrates an exemplary system for seam-
`less roaming between wireless networks according to an
`embodimentof the present invention. As shown,this system
`can be incorporated into or comprise a wireless device 12.
`The wireless device 12 can be any suitable electronic device
`such as, for example, a portable personal computer (PC),
`wireless PDA or cellular phone, having a data processing
`facility supported by memory (either internal or external)
`and being wireless network capable.
`
`[0032] A numberof networking hardware devices, such as
`WLAN hardware 26, WWAN hardware28, and combination
`hardware 30, support connections between wireless device
`12 and various wireless networks. WLAN hardware 26
`supports connection with a WLAN. WWAN hardware 28
`supports connection with a WWAN. Combination hardware
`30 supports connection with either a WLAN or a WWAN.
`The networking hardware devices could be a wireless
`modem, a wireless network interface card (NIC), or any
`other suitable hardware peripheral device for supporting a
`wireless connection. In other embodiments, such devices
`can be implemented in any combination of hardware and
`software. A driver layer 32, which may be implemented in
`software or hardware or both, functions as a hardware
`controller for the WLAN hardware 26, WWAN hardware 28,
`and combination hardware 30.
`
`[0033] A user interface (I/F) 34 generally functions to
`enable a human userto interact with the wireless device 12,
`for example,
`to run applications (e.g., word processing),
`browse the Internet, check email, and the like. The func-
`tionality of the user interface 34 can be performed by one or
`more suitable input devices (e.g., keypad,
`touch screen,
`input port, pointing device, microphone, and/or other device
`that can accept user input information) and one or more
`suitable output devices (e.g., video display, output port,
`speaker, or other device, for conveying information, includ-
`ing digital data, visual information,or audio information). In
`one embodiment, each user interface 34 may comprise or be
`operable to display at least one graphical user interface
`(GUI) having a number of interactive devices, such as
`buttons, windows, pull-down menus, and the like to facili-
`tate the entry, viewing, and/or retrieval of information.
`
`[0034] The wireless device 12 may operate under the
`control of a suitable operating system (OS) 20, such as, for
`example, MS-DOS, MAC OS, WINDOWSNIT, WIN-
`DOWS 95, WINDOWSCE, OS/2, UNIX, LINUX, LIN-
`DOWS, XENIX, PALM OS, and the like. One or more
`
`software applications 22 may run on the wireless device 12.
`Each application 22 may interact with the operating system
`20. These applications 22 may support numerousservices or
`functions such as, for example, document sharing, account-
`ing, word processing, application sharing,
`file transfer,
`remote control, browser, voice over Internet Protocol (IP),
`user authentication, address book,files and folders, account-
`ing, database management,andthelike. Atleast a portion of
`these applications 22 may require the exchange of informa-
`tion over the wireless network with other electronic devices
`as the applications 22 are executing on the wireless device
`12.
`
`[0035] A connectivity application 24, provided in the
`software layer, acts as a pseudo router of network addresses
`and connectivity. The connectivity application 24 logically
`resides between the operating system 20 and the driver layer
`32 of hardware controllers. The connectivity application 24
`may logically “sit on top” of operating system 20. Connec-
`tivity application 24 may support the detection of wireless
`connections that are available in any given location to the
`wireless device 12. These connections include both WLAN
`and WWAN connections. Furthermore, unlike previously
`developed techniques, the connectivity application 24 main-
`tains information and handles connectivity for different
`kinds of wireless networks. As such, connectivity applica-
`tion 24 is able to coordinate the connection of the wireless
`device 12 with different wireless networks, thereby provid-
`ing seamless transition or handoff between the networks,
`including from a WLAN connection to a WWAN connec-
`tion, and vice versa, as well as between WLAN or WWAN
`connections. Connectivity application 24 may provide the IP
`address of the wireless connection in use to the operating
`system 20, which in turn publishes this IP address to all
`applications 22. As depicted, in one embodiment, connec-
`tivity application 24 includes a user interface (UI) compo-
`nent 36, a core component 38, a WLAN interface component
`40, a WWAN interface component 42, and a combination
`interface component 44.
`
`[0036] WLAN interface component 40, WWAN interface
`component 42, and combination interface component 44
`provide or support an interface with the driver layer 32
`comprising device drivers, which can be supplied by the
`respective hardware manufacturers of the networking hard-
`ware devices (e.g., WLAN hardware 26, WWAN hardware
`28, and combination hardware 30). WLAN interface com-
`ponent 40 may handle all the communications with, for
`example, any WiFi compliant 802.11a card and its driver.
`WLAN interface component 40 can, for example, interface
`with the application program interface (API) of the WLAN
`card. This component 40 implements both the standard
`interfaces as well as specific aspects of communicating with
`the WLAN card, to retrieve common information such as
`Status, Signal Strength, MAC Address, Firmware version,
`and the like. The WLAN interface component 40 also
`handles sending and receiving messages to the card. The
`WWAN interface component 42 and the combo interface
`component 44 have similar functionality to its WLAN
`counterpart, except that it is implemented to communicate
`with the API of the WWAN card.
`
`[0037] The UI component 36 provides support for the
`presentation (e.g., visually, audibly, physically,etc.) of infor-
`mation relating to the wireless connections for the wireless
`device 12. This information may include, for example,
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 10
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 10
`
`

`

`US 2004/0127208 Al
`
`Jul. 1, 2004
`
`network information for WWAN 14 and WLANs 16, 18.
`The UI component 36 mayalso allow a user to configure or
`set (e.g., enabling and disabling) the wireless connections
`for the device 12. In one embodiment, for example, UI
`component 36 may enable a user to readily and easily, yet
`manually or automatically, switch from one wireless net-
`work connection (e.g., for WWAN 14) to another wireless
`network connections (e.g., for WLAN 16) with no adverse
`effect on applications running on the wireless device 12.
`
`[0038] The core component 38 is in communication with
`UI component 36, WLAN interface component 40, WWAN
`interface component 42, and combination interface compo-
`nent 44. The core component 38 implements the logic for
`keeping track of, handling, and managing the connectivity to
`the wireless networks and informing the operating system 20
`about any changes. The core component 38 may also be
`responsible for automated switching of the connections
`which,in one embodiment, can be rule-based switching. The
`core component 38 may automatically authenticate and
`connect the wireless device 12 to preferred wireless net-
`works that are detected.
`
`In operation, as the wireless device 12 is moved
`[0039]
`between or among the effective ranges of various wireless
`networks (WLAN or WWAN), connectivity application 24
`functions to change connections from one wireless network
`to another wireless network. In one aspect, the change of
`wireless connection can be automatic suchthat, for example,
`upon loss of connectivity from any one connection,
`the
`connectivity application 24 will automatically initiate a new
`connection and pass the respective IP address to operating
`system 20. Then, as applications 22 are subsequently
`refreshed using an IP connection, the applications 22 will
`automatically pick up the new IP address and start using the
`new address for wireless connectivity (e.g., according to the
`rules of core component 38). This may occur without any
`noticeable loss of connectivity to the user of the wireless
`device 12. In another aspect, the change of wireless con-
`nection can be manually initiated by the user. Connectivity
`application 24 supports the detection of wireless connections
`that may be available for any given location. Information
`about the available wireless connections may be accessed by
`the user from connectivity application 24 via user interface
`34. Then, the user can select which wireless connection to
`use for connectivity (e.g., to the Internet).
`
`[0040] As such, the system according to an embodiment of
`the present invention provides ubiquity of access to wireless
`data and efficiency of spectral usage in cellular bands when
`using wireless data. Thus, for example, Internet-enabled
`applications 22 do not experience a loss of connectivity as
`a result of connection loss by wireless device 12 with either
`a WWAN or a WLAN.Nor dothe applications 22 experi-
`ence loss of connection as result of transition from one
`wireless network to another(e.g., from WWAN to WLAN).
`Furthermore, the system allows cellular service providers to
`offer wireless data services supported by a combination of
`their existing two-and-a-half generation (“2.5G”) networks
`(such as, but not limited to, GPRS, CDMA 1xRTT) and
`TEEE 802.11 WLAN networks (such as, but not limited to,
`802.11a, 802.11b, 802.11 g, etc.), with minimal risk of
`wireless data consuming the entire available capacity of the
`cellular networks.
`
`[0041] User Interface Component
`[0042]
`FIG.3 illustrates an exemplary user interface com-
`ponent 36 according to an embodiment of the present
`invention. As shownin FIG.3, the user interface component
`36 can be completely separated from the core functionality
`(e.g., managing connections) provided by core component
`38 (of FIG. 2) of the connectivity application 24. This
`separability can be done in order to allow users of the
`connectivity application 24 to provide their own user inter-
`faces to the application, each interface having the look and
`feel (along with branding) desired by the particular service
`provider. As shown,user interface component 36 includes a
`third-generation (3G) UI subcomponent 50, a WLAN UI
`subcomponent 52, an inter-subcomponent communication
`module 54, and a core interface (I/F) subcomponent 56.
`[0043] The 3G UI subcomponent 50 may handle the
`connect/disconnect
`functionality for various WWANs,
`which can be the 2.5G or 3G of mobile communications
`technology. Examples of such technologies include, but are
`not limited to GPRS, CDMA 1xRTTand iDEN Packet Data
`services (for 2.5G) and W-CDMAbased services such as
`UMTSand CDMA 3xRTT(for 3G). Relative to first gen-
`eration (e.g., analog cellular) and second generation (e.g.,
`digital PCS), 2.5G and 3G technology provides increased
`bandwidth. For example, 3G technology provides up to 384
`Kbps when a wireless device is stationary or moving at
`pedestrian speed, 128 Kbps in a car, and 2 Mbpsin fixed
`applications. 3G UI subcomponent 50 may present or dis-
`play information for the signal strength of each available
`WWAN (e.g., 2.5G or 3G) connection, as well as type of
`connection (e.g., circuit-switched or packet-switched). This
`subcomponent 50 may also display or present information
`about the availability of WWAN service, or lack thereof.
`[0044] WLAN UI subcomponent 52 can, among other
`things, keep track of and/or present all identified WLANsin
`the particular location of wireless device 12, as well as their
`current connections and encryption status. This WLAN U
`subcomponent 52 mayalso handle selection by a user and
`connection of the wireless device 12 to the various WLANs.
`
`[0045] Taken together, 3G UI subcomponent 50 and
`WLAN UI subcomponent52 provide the user of the wireless
`device 12 with a real-time picture of all available connec-
`tions to the various wireless networks, and may direct the
`user to a location where connectivity is available. A user of
`the wireless device 12 can toggle connections between
`WWAN and WLAN connections by interacting with 3G UI
`subcomponent 50 and WLAN UI subcomponent52.
`[0046] The inter-subcomponent communication module
`54 is responsible for communicating the status of each of the
`subcomponents 50 and 52. The inter-subcomponent com-
`munication module 54 may notify core component 38 of
`connection status change for each of these subcomponents.
`The core I/F subcomponent 56 interacts with core compo-
`nent 38 of connectivity application 24. Core interface 54
`may, among other things, communicate the status of the
`wireless connections and user interactions with UI compo-
`nent 36 to the core component38.
`[0047] Core Component
`[0048]
`FIG.4 illustrates an exemplary core component 38
`according to an embodiment of the present invention. As
`shown,the core component38 generally functions to handle
`and manage the connectivity to the wireless networks and
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 11
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1007, p. 11
`
`

`

`US 2004/0127208 Al
`
`Jul. 1, 2004
`
`inform the operating system 20 about any changes. As
`depicted, the core component 38 includes an active connec-
`tion selection 60 and a rules engine 62.
`[0049] The active connection selection 60 keeps track of
`the various wireless connections which are presently avail-
`able (including both WLAN and WWAN connections) and
`also the particular wireless connection, that is currently in
`use by the wireless device 12. The active connection selec-
`tion 60 publishes the active connection information to the
`operating system 20; thatis, it provides the operating system
`20 with information (e.g., IP address) for the current wireless
`connection. The wireless connection currently in use can be
`changed by modifying (or toggling) current active connec-
`tion 60, either by a direct user intervention or as a result of
`one or more rules in the rules engine 62.
`[0050] The rules engine 62 may implement and execute a
`number of rules for automated switching of the wireless
`connections, and authentication and connection of the wire-
`less device 12 to a preferred wireless network. These rules
`may define, for example, what to do when a GPRS connec-
`tion is lost. Rules engine 62 may also allow the rules
`themselves to be created, modified, or deleted,
`thereby
`defining the characteristic behavior of core component 38.
`[0051] The rules engine 62 is responsible for making the
`decision as to which wireless network (e.g., WWAN 14,
`WLAN 16, or WLAN 18) to connect in the event of lost
`connectivity or the availability of multiple wireless net-
`works. The core component 38 automatically detects any
`available wireless networks in the area of wireless device 12
`
`and uses the rules engine 62 to determine to which network
`to con

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket