US20090047964A1 - Handoff in ad-hoc mobile broadband networks - Google Patents
Handoff in ad-hoc mobile broadband networks Download PDFInfo
- Publication number
- US20090047964A1 US20090047964A1 US12/188,985 US18898508A US2009047964A1 US 20090047964 A1 US20090047964 A1 US 20090047964A1 US 18898508 A US18898508 A US 18898508A US 2009047964 A1 US2009047964 A1 US 2009047964A1
- Authority
- US
- United States
- Prior art keywords
- service provider
- mobile
- handoff
- mobile service
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000012545 processing Methods 0.000 claims description 46
- 238000000034 method Methods 0.000 claims description 34
- 230000004044 response Effects 0.000 claims description 11
- 230000005641 tunneling Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 8
- 238000012544 monitoring process Methods 0.000 description 7
- 238000013461 design Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000013475 authorization Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 238000013442 quality metrics Methods 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 230000002411 adverse Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
- H04W12/062—Pre-authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
- H04W36/0038—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of security context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Definitions
- the present disclosure relates generally to telecommunications, and more specifically to handoff in an ad-hoc mobile broadband network.
- Wireless telecommunication systems are widely deployed to provide various services to consumers, such as telephony, data, video, audio, messaging, broadcasts, etc. These systems continue to evolve as market forces drive wireless telecommunications to new heights.
- wireless networks are providing broadband Internet access to mobile subscribers over a regional, a nationwide, or even a global region. Such networks are sometimes referred to as Wireless Wide Area Networks (WWANs).
- WWAN operators generally offer wireless access plans to their subscribers such as subscription plans at a monthly fixed rate.
- WWANs from all mobile devices may not be possible. Some mobile devices may not have a WWAN radio. Other mobile devices with a WWAN radio may not have a subscription plan enabled.
- Ad-hoc networking allows mobile devices to dynamically connect over wireless interfaces using protocols such as WLAN, Bluetooth, UWB or other protocols. There is a need in the art for a methodology to allow a user of a mobile device without WWAN access to dynamically subscribe to wireless access service provided by a user with a WWAN-capable mobile device using wireless ad-hoc networking between the mobile devices belong to the two users.
- a server includes a processing system configured to maintain a session with a mobile client through a first mobile service provider.
- the processing system is further configured to authenticate a second mobile service provider for handoff.
- the processing system is also configured to enable the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- a server in another aspect of the disclosure, includes means for maintaining a session with a mobile client through a first mobile service provider, means for pre-authenticating a second mobile service provider for handoff, and means for enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- a method of providing service from a server includes maintaining a session with a mobile client through a first mobile service provider.
- the method further includes pre-authenticating a second mobile service provider for handoff, and enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- machine-readable medium includes instructions executable by a processing system in a server.
- the instructions include code for maintaining a session with a mobile client through a first mobile service provider.
- the instructions further include code for pre-authenticating a second mobile service provider for handoff, and enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- FIG. 1 is a simplified block diagram illustrating an example of a telecommunications system.
- FIG. 2 is a simplified block diagram illustrating an example of a handoff in a telecommunications system.
- FIG. 3 is a call flow diagram illustrating an example of a pre-authentication process for handoff.
- FIG. 4 is a simplified block diagram illustrating an example of a hardware configuration for a server.
- FIG. 5 is a simplified block diagram illustrating an example of a hardware configuration for a processing system in a server.
- FIG. 6 is a simplified block diagram illustrating an example of the functionality of a mobile service provider.
- FIG. 1 is a simplified block diagram illustrating an example of a telecommunications system.
- the telecommunications system 100 is shown with multiple WWANs that provide broadband access to a network 102 for mobile subscribers.
- the network 102 may be a packet-based network such as the Internet or some other suitable network.
- two WWANs 104 are shown with a backhaul connection to the Internet 102 .
- Each WWAN 104 may be implemented with multiple fixed-site base stations (not shown) dispersed throughout a geographic region. The geographic region may be generally subdivided into smaller regions known as cells.
- Each base station may be configured to serve all mobile subscribers within its respective cell.
- a base station controller (not shown) may be used to manage and coordinate the base stations in the WWAN 104 and support the backhaul connection to the Internet 102 .
- Each WWAN 104 may use one of many different wireless access protocols to support radio communications with mobile subscribers.
- one WWAN 104 may support Evolution-Data Optimized (EV-DO), while the other WWAN 104 may support Ultra Mobile Broadband (UMB).
- EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs multiple access techniques such as Code Division Multiple Access (CDMA) to provide broadband Internet access to mobile subscribers.
- 3GPP2 3rd Generation Partnership Project 2
- CDMA Code Division Multiple Access
- one of WWAN 104 may support Long Term Evolution (LTE), which is a project within the 3GPP2 to improve the Universal Mobile Telecommunications System (UMTS) mobile phone standard based primarily on a Wideband CDMA (W-CDMA) air interface.
- LTE Long Term Evolution
- UMTS Universal Mobile Telecommunications System
- WWAN 104 may also support the WiMAX standard being developed by the WiMAX forum.
- WiMAX WiMAX forum.
- the actual wireless access protocol employed by a WWAN for any particular telecommunications system will depend on the specific application and the overall design constraints imposed on the system.
- the various techniques presented throughout this disclosure are equally applicable to any combination of heterogeneous or homogeneous WWANs regardless of the wireless access protocols utilized.
- Each WWAN 104 has a number of mobile subscribers. Each subscriber may have a mobile node 106 capable of accessing the Internet 102 directly through the WWAN 104 . In the telecommunications system shown in FIG. 1 , these mobile nodes 106 access the WWAN 104 using an EV-DO, UMB or LTE wireless access protocol; however, in actual implementations, these mobile nodes 106 may be configured to support any wireless access protocol.
- a mobile node 106 may be configured to create in its vicinity an ad-hoc network based on the same or different wireless access protocol used to access the WWAN 104 .
- a mobile node 106 may support a UMB wireless access protocol with a WWAN, while providing an IEEE 802.11 access point for mobile nodes 108 that cannot directly access a WWAN.
- IEEE 802.11 denotes a set of Wireless Local Access Network (WLAN) standards developed by the IEEE 802.11 committee for short-range communications (e.g., tens of meters to a few hundred meters).
- IEEE 802.11 is a common WLAN wireless access protocol, other suitable protocols may be used.
- a mobile node 106 that may be used to provide an access point for another mobile node 108 will be referred to herein as a “mobile service provider.”
- a mobile node 108 that may use an access point of a mobile service provider 106 will be referred to herein as a “mobile client.”
- a mobile node, whether a mobile service provider 106 or a mobile client 108 may be a laptop computer, a mobile telephone, a personal digital assistant (PDA), a mobile digital audio player, a mobile game console, a digital camera, a digital camcorder, a mobile audio device, a mobile video device, a mobile multimedia device, or any other device capable of supporting at least one wireless access protocol.
- PDA personal digital assistant
- the mobile service provider 106 may extend its wireless broadband Internet access service to mobile clients 108 that would otherwise not have Internet access.
- a server 110 may be used as an “exchange” to enable mobile clients 108 to purchase unused bandwidth from mobile service providers 106 to access, for example, the Internet 102 across WWANs 104 .
- a mobile service provider 106 , a server 110 , and one or more mobile clients 108 may establish a network that is an ad-hoc heterogeneous wireless network.
- a heterogeneous wireless network may include at least two types of wireless networks (e.g., a WWAN and a WLAN).
- an ad-hoc network may be a network whose specific configuration may change from time to time or from the formation of one network to the next. The network configuration is not pre-planned prior to establishing the network.
- Examples of configurations for an ad-hoc network may include a configuration as to which members are to be in the network (e.g., which mobile service provider, which server, and/or which mobile client(s) are to be included in a network), a configuration as to the geographic locations of a mobile service provider and mobile client(s), and a configuration as to when and how long a network is to be established.
- mobile clients 108 register with the server 110 . Once registered, a mobile client 108 may search for available mobile service providers 106 when Internet access is desired. When the mobile client 108 detects the presence of one or more mobile service providers 106 , it may select a mobile service provider 106 to initiate a session with based on various parameters such as bandwidth, Quality of Service (QoS) and cost. Another parameter that may be used by the mobile client 108 to select a mobile service provider 106 is availability in terms of time. By way of example, a mobile subscriber in an airport may turn on his mobile node (e.g., a laptop computer or a mobile telephone) and use it as a mobile service provider 108 for 30 minutes as he awaits his flight.
- QoS Quality of Service
- a mobile client 108 requiring access to the Internet 102 for 45 minutes may choose not to select this mobile service provider 106 even if the mobile service provider 108 can provide adequate bandwidth with good QoS.
- Another mobile client 108 requiring Internet access for 15 minutes, may select this mobile service provider 106 because of its bandwidth and QoS.
- a session may be established based on the parameters negotiated be the two (e.g., bandwidth, QoS, duration of the session, etc.).
- a link encryption key may be established between the mobile client 108 and the mobile service provider 106 during the establishment of the session.
- a Secured Socket Layer Virtual Private Network (SSL VPN) session may be established between the mobile client 108 and the server 110 .
- the transport layer ports may be kept in the open and not encrypted to provide visibility for the network address translation functionality at the mobile service provider 106 .
- all Internet traffic is routed through the server 110 via a client-server tunnel 112 to provide security.
- a mobile client 108 In some telecommunication systems, once a mobile client 108 has gained access to the Internet 102 , it listens for other mobile service providers 106 and measures the signal strength of the mobile service providers 106 it can hear. The mobile client 108 uses these measurements to create an active list.
- the active list is a list of mobile service providers 106 that can provide service to the mobile client 108 .
- the mobile client 108 will continue to measure the signal strength of other mobile service providers 106 and may add or remove mobile service providers 106 from the active list as the configuration of the ad-hoc network changes.
- One function of the active set is to allow the mobile client 108 to quickly switch between mobile service providers 106 while maintaining the current session with the server 110 .
- the mobile client 108 may consider a handoff to another mobile service provider 106 based on any number of factors. These factors may include, by way of example, the inability of the mobile service provider 106 to provide the bandwidth or QoS negotiated at the beginning of the session. Alternatively, the mobile service provider 106 may not be able to provide Internet access to the mobile client 108 for the entire duration of the session. It would not be uncommon for a mobile subscriber on a mobile service provider 106 that negotiates a 30 minute session with a mobile client 108 to leave the vicinity 15 minutes into the session for whatever reason.
- the mobile client 108 would need to select a new mobile service provider from the active list for handoff.
- the server 110 uses the active list to pre-authenticate other mobile service providers for handoff during the session between the mobile client 108 and the current mobile service provider 106 .
- pre-authenticating the mobile service provider 106 in the active list before the mobile service provider 106 currently serving the mobile client 108 goes down the time required to handoff the mobile client 108 can be reduced.
- pre-authenticating means authenticating a target mobile service 106 provider for handoff prior to receiving a message from the mobile service provider 106 currently serving the mobile client 108 relating to the unavailability of the current mobile service provider 106 .
- the message may provide notification to the server 110 that the current mobile service provider 106 has gone down and a hard handoff must be performed to another mobile service provider 106 if the session between the mobile client 108 and the server 110 is to be maintained.
- the message may provide notification to the server 110 that the current mobile service provider 106 will be going down shortly, or that it can no longer provide the mobile client 108 with the service agreed upon (e.g., QoS, bandwidth, etc.). This provides the server 110 with the option of enabling a soft handoff of the mobile client 108 to another mobile service provider 106 .
- Pre-authentication includes provisioning, prior to handoff, a potential new service provider 106 and a mobile client 108 with encryption/decryption keys that may be needed for communication between the potential new service provider 106 and the mobile client 108 .
- Pre-authentication also includes provisioning, prior to handoff, the current service provider 106 and the new service provider 106 with encryption/decryption keys that may be needed for communication between the current service provider 106 and the new service provider 106 .
- Pre-authentication also includes authorization of communication between the potential new service provider 106 and the current service provider 106 . It also includes authorization of communication between the potential new service provider 106 and the mobile client 108 .
- FIG. 2 is a simplified block diagram illustrating an example of a handoff in a telecommunications system.
- the mobile client 108 is being handed off from a current mobile service provider 106 1 to a target service provider 106 2 .
- a persistent tunnel 112 between the two mobile service providers 106 1 , 106 2 is used to maintain the mobile client's session with the server 110 during handoff.
- Data packets received by the current mobile service provider 106 1 during handoff may be forwarded to the target mobile service provider 106 2 through the tunnel 112 .
- the data packets received by the current service provider 106 1 may be forwarded to the target mobile service provider 106 2 directly over a wireless link 114 between the two as shown in FIG. 2 , or through another mobile service provider (not shown).
- the mobile client 108 may have an IPv4, IPv6, or other suitable address that is used by the server 110 to maintain the session.
- the address may be provided to the mobile client 108 by the server 110 or one of the mobile service providers 106 in the telecommunications network 100 (see FIG. 1 ). Alternatively, the address may be stored on the mobile client 108 . In at least one configuration, the address may be a MobileIP address.
- the tunneling anchor is shown in FIG. 2 as a server. However, the tunneling anchor may be any suitable entity or distributed across multiple entities in the telecommunications system 100 .
- the tunneling anchor may be coupled to the Internet 102 as shown in FIG. 2 or located elsewhere. By way of example, the tunneling anchor may be located anywhere on the Internet 102 or within the network operator's infrastructure. Those skilled in the art will be readily able to determine the optimal implementation of the tunneling anchor for any particular application based on the performance requirements, the overall design constraints imposed on the system, and/or other relevant factors.
- FIG. 3 is a call flow diagram illustrating an example of the authentication process for handoff. For clarity of presentation, various signaling for the mobile service providers 106 and clients 108 to authenticate the server 110 and register with the server 110 will be omitted.
- a connection may be initiated by a mobile service provider 106 1 with the server 110 when the mobile service provider 106 1 is mobile and desires to provide service.
- Extensible Authentication Protocol-Tunneled Transport Layer Security (EAP-TTLS) may be used for Authentication, Authorization and Accounting (AAA) and secure session establishment for this connection.
- EAP-TTLS Extensible Authentication Protocol-Tunneled Transport Layer Security
- AAA Authentication, Authorization and Accounting
- a connection may be initiated by a mobile client 108 with the mobile service provider 106 1 (hereinafter referred to as the “current mobile service provider”) when the mobile client 108 requires Internet access.
- EAP-TTLS may also be used for AAA and secure session establishment.
- the mobile service provider 106 1 sends the mobile client's credentials to the server 110 for EAP-AAA authentication.
- the EAP-TTLS authentication response from the server 110 is then used to generate a master shared key. Subsequently, a link encryption key may be established between the current mobile service provider 106 1 and the mobile client 108 . A SSL VPN session may then be established, in step 306 , between the mobile client 108 and the server 110 .
- information flow may be encrypted using encryption/decryption keys between any pair of nodes (where the nodes comprise the server 110 , the current service provider 106 1 , the target service provider 106 2 , and the mobile client 108 ).
- Such encryption/decryption keys can be set up in the system when nodes in the system connect with the server.
- symmetric key cryptography such as using AES may be used for such encryption or decryption for message-flow between any pair of nodes in the system.
- the mobile client 108 provides the active list to the server 110 .
- the mobile client 108 can send a report identifying mobile service providers that it can hear accompanied by data indicating the signal strength measurements for each.
- the server 110 may use the report to generate the active list at its end.
- the server 110 pre-authenticates one or more of the mobile service providers in the active list. During pre-authentication of a target service provider 106 2 with a client 108 , the server 110 provisions the target-service provider 106 2 with an encryption/decryption key for communication with the client 108 . The server may additionally provision the target service provider 106 2 with an encryption/decryption key for communication with the current service provider 106 1 . The server 110 also provisions the client 108 with the encryption/decryption key to communicate with the target service provider 106 2 . The current service provider 106 1 can be provisioned by the server 110 , either at the time of a handoff or anytime earlier, with the encryption/decryption key to communicate with the target service provider 106 2 .
- the exact number of mobile service providers in the active list that are pre-authenticated may depend on the admission control policies implemented by the server 110 .
- the server 110 may limit the number of mobile service providers at a given location if it determines that additional mobile service providers will adversely affect performance in the WWAN. Additional constraints may be imposed by the WWAN operators that may not want its mobile subscribers to provide service in a given geographic location depending on various network constraints.
- the server 110 pre-authenticates one or more mobile service providers by providing each of them with a key to encrypt the data link between the mobile client 108 and the new mobile service provider 106 following handoff. In FIG.
- the server 110 is shown, in step 310 , providing the key to one mobile service provider 106 2 (hereinafter referred to as the target mobile service provider).
- the server 110 also provides the key to the mobile client 108 through the VPN tunnel.
- step 314 the mobile client 108 sends a message to the current mobile service provider 106 requesting a handoff to an alternate service provider.
- Step 314 is optional and is indicated by a dotted line from the client to the mobile service provider.
- step 316 the current mobile service provider 106 , sends a message to the server 110 requesting a handoff.
- a message is tagged with an identifier that indicates that the handoff was initiated by the mobile client 108 , or that it was initiated by the current mobile service provider 106 1 .
- the message may be created at the current mobile service provider 106 1 as a consequence of the current mobile service provider's unavailability to continue to provide service to the mobile client.
- the message could have been created at the mobile client (step 314 ), which needs to be sent by the current mobile service provider 106 , to the server 110 .
- step 316 is optional.
- step 318 the server 110 responds to step 316 by sending a message back to current mobile service provider 106 1 authorizing handoff.
- step 318 could be a message from the server initiating a handoff, in the absence of a message 316 from the current mobile service provider 106 1 .
- the message sent to the current mobile service provider 106 1 may identify the target mobile service provider 106 2 for handoff, or alternatively, allow the mobile client 108 to make the decision. In the latter case, the user on the mobile client 108 selects a target mobile service provider for handoff in accordance with any admission control policy constraints imposed by the server 110 .
- the server 110 may also provide the mobile client 108 with a quality metric for each mobile service provider available to the mobile client. This quality metric may be used to assist the user on a mobile client 108 to select a new mobile service provider for handoff. In the example shown in FIG. 3 , the mobile client 108 selects the target mobile service provider 106 2 for handoff.
- the server may optionally send a message regarding the handoff to one or more target service providers 106 2 .
- the handoff message received from the server 110 is sent by the current service provider 106 , to the mobile client 108 .
- the mobile client 108 establishes a connection with the target mobile service provider 106 2 by sending a message encrypted with a key. Since the target mobile service provider 106 2 received the same key during the pre-authentication process, it can decrypt the message and establish a session with the mobile client 108 to complete the handoff. The target mobile service provider 106 2 may also send a message back to the server 110 , in step 326 , to signify that the handoff has been successfully completed.
- Packets that have left the mobile client 108 may be in transit to the current mobile service provider 106 1 , or could be at the current mobile service provider 106 1 . These packets need to continue to be supported by the current mobile service provider 106 1 . Other packets that have left the mobile client 108 may be in transit to the server 110 , or may be waiting at server 110 for further processing, or may be in transit to their final destination beyond the tunneling server. Future packets that leave the mobile client 108 are sent to the target mobile service provider 106 2 after handoff. Packets that are destined to the mobile client 108 may be waiting at the server. Such packets are sent to the target mobile service provider 106 2 after handoff.
- Other packets destined for the mobile client 108 may be in transit to the current mobile service provider 106 1 , or may be waiting at the current mobile service provider 106 1 , or may be in transit from the current service provider to the mobile client 108 , and the current mobile service provider 106 1 needs to continue to support such packets to be delivered to the mobile client 108 .
- the delivery of such packets can be done over a wireless link or a multi-hop wireless path between the current mobile service provider 106 1 and the target mobile service provider 106 2 .
- such packets can be delivered by the current mobile service provider 106 1 to the server 110 , which then sends them through the target mobile service provider 106 2 .
- Messages between the current mobile service provider 106 1 and the target mobile service provider 106 2 may be exchanged either through the server 110 , or over a wireless link or multi-hop wireless path between the service providers.
- FIG. 4 illustrates an example of a hardware implementation for a server.
- the server 110 may be a centralized server or a distributed server.
- a centralized server may be a dedicated server or integrated into another network-related entity, such as a desktop or laptop computer, mainframe, or other suitable entity.
- a distributed server may be distributed across multiple servers and/or one or more network-related entities, such as a desktop or laptop computer, mainframe, or some other suitable entity.
- the server may be integrated, either in whole or part, into one or more mobile service providers.
- the server 110 is shown with a network interface 402 , which may support a wired and/or wireless connection to the Internet 102 .
- the network interface 402 may be used to implement the physical layer by providing the means to transmit and receive data in accordance with the physical and electrical specifications required to interface to the transmission medium.
- the network 402 may also be configured to implement the lower portion of the data link layer by managing access to the transmission medium.
- the server 110 is also shown with a processing system 404 that provides various functions, including session management for mobile service providers and clients, pre-authentication of mobile service providers targeted for handoff, handoff of mobile clients from one mobile service providers to another, and data tunneling for mobile clients.
- the processing system 404 is shown separate from the network interface 402 , however, as those skilled in the art will readily appreciate, the network interface 402 , or any portion thereof, may be integrated into the processing system 404 .
- FIG. 5 illustrates an example of a hardware implementation for a processing system in a server.
- the processing system 404 may be implemented with a bus architecture represented generally by bus 502 .
- the bus 502 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 404 and the overall design constraints.
- the bus links together various circuits including a processor 504 and machine-readable media 506 .
- the bus 502 may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further.
- a network adapter 508 provides an interface between the network interface 402 (see FIG. 4 ) and the bus 502 .
- the processor 504 is responsible for managing the bus and general processing, including the execution of software stored on the machine-readable media 506 .
- the processor 504 may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software.
- Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
- Machine-readable media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
- RAM Random Access Memory
- flash memory read Only Memory
- PROM PROM (Programmable Read-Only Memory)
- EPROM Erasable Programmable Read-Only Memory
- EEPROM Electrically Erasable Programmable Read-Only Memory
- registers magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
- the machine-readable media 506 is shown as part of the processing system 404 separate from the processor 504 .
- the machine-readable media 506 may be external to the processing system 404 .
- the machine-readable media 506 may include a transmission line, a carrier wave modulated by data, and/or a computer product separate from the server, all which may be accessed by the processor 504 through the network adapter 508 .
- the machine readable media 506 may be integrated into the processor 504 , such as the case may be with cache and/or general register files.
- the processing system 404 may be configured as a general-purpose processing system with one or more microprocessors providing the processor functionality and external memory providing at least a portion of the machine-readable media 506 , all linked together with other supporting circuitry through an external bus architecture.
- the processing system 404 may be implemented with an ASIC (Application Specific Integrated Circuit) with the processor 504 , the network adapter 508 , supporting circuitry (not shown), and at least a portion of the machine-readable media 506 integrated into a single chip, or with one or more FPGAs (Field Programmable Gate Array), PLDs (Programmable Logic Device), controllers, state machines, gated logic, discrete hardware components, or any other suitable circuitry, or any combination of circuits that can perform the various functionality described throughout this disclosure.
- ASIC Application Specific Integrated Circuit
- the machine-readable media 506 is shown with a number of software modules.
- the software modules include a protocol stack module 509 , a pre-authentication module 510 , a session manager module 512 , a tunneling module 514 , and a handoff module 516 .
- These software modules include instruction sets that when executed by the processor 504 cause the processing system 402 to carry out the process steps as shown and described in FIGS. 1-3 .
- Each software module may reside in a single storage device or distributed across multiple memory devices.
- a software module may be loaded into RAM from a hard drive when a triggering event occurs (e.g., a mobile node decides to become a mobile service provider).
- the processor 504 may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor 504 .
- the functionality of a software module below, it will be understood that such functionality is implemented by the processor 504 when executing instructions from that software module.
- the protocol stack module 509 may be used to implement the protocol architecture, or any portion thereof, for the server. In the implementation described thus far, the protocol stack module 509 is responsible for implementing several protocol layers running on top of the data link layer implemented by the network interface 402 (see FIG. 4 ). By way of example, the protocol stack module 509 may be used to implement the upper portion of the data link layer by providing flow control, acknowledgement, and error recovery. The protocol stack module 509 may also be used to implement the network layer by managing source to destination data packet transfer, as well as the transport layer by providing transparent transfer of data between end users. Although described as part of the processing system, the protocol stack module 509 , or any portion thereof, may be implemented by the network interface 402 .
- the session manager module 512 may be used by the server to maintain sessions with the mobile service providers and clients.
- the pre-authentication module 510 may be used to pre-authenticate mobile service providers for handoff.
- the pre-authentication module 510 may receive from a mobile client a list of mobile service providers in the coverage region for the mobile client and use the list to identify the mobile service provider for pre-authentication.
- the handoff module 516 may be used to enable the handoff of a mobile client between mobile service providers while the session manager module 512 maintains the session with the mobile client.
- the handoff module 516 may enable handoff by authenticating the mobile client for the target service provider prior to handoff and provisioning the target service provider and the mobile client with a key to support an encrypted link between the two following handoff.
- the handoff may be enabled in response to various messages, including by way of example, a message indicating that the mobile client has selected the target service provider, a message indicating the unavailability of the service provider currently serving the mobile client, or a request from the mobile client for a handoff.
- the handoff may be a hard or soft handoff.
- the handoff module 516 may further provide a method for forwarding packets received by the current service provider to the target service provider following handoff through a tunnel between the server and the target service provider, a wireless link, another mobile service provider, or by some other suitable means.
- the tunneling module 514 may be used by the server to maintain tunnels with mobile service providers and clients.
- the tunneling module 514 may also be used to maintain a tunnel with a mobile client during handoff from a current mobile service provider to a target service provider.
- the tunneling is performed by a module in the server.
- the tunneling of data between the Internet and the nodes may be located elsewhere in the network.
- FIG. 6 is a simplified block diagram illustrating an example of the functionality of a mobile service provider.
- the mobile service provider 106 has the ability to bridge wireless links over homogeneous or heterogeneous wireless access protocols. This may be achieved with a WWAN network adapter 602 that supports a wireless access protocol for a WWAN to the Internet 102 , and a WLAN network adapter 604 that provides a wireless access point for mobile clients 108 .
- the WWAN network adapter 602 may include a transceiver function that supports EV-DO for Internet access through a WWAN
- the WLAN network adapter 604 may include a transceiver function that provides an 802.11 access point for mobile clients 108 .
- Each network adapter 602 , 604 may be configured to implement the physical layer by demodulating wireless signals and performing other radio frequency (RF) front end processing.
- Each network adapter 602 , 604 may also be configured to implement the data link layer by managing the transfer of data across the physical layer.
- RF radio frequency
- the mobile service provider 106 is shown with a filtered interconnection and session monitoring module 606 .
- the module 606 provides filtered processing of content from mobile clients 108 so that the interconnection between the ad-hoc wireless links to the WWAN network interface 602 is provided only to mobile clients 108 authenticated and permitted by the server to use the WWAN network.
- the module 606 also maintains tunneled connectivity between the server and the authenticated mobile clients 108 .
- the mobile service provider 106 also includes a service provider application 608 that (1) enables the module 606 to provide ad-hoc services to mobile clients 108 , and (2) supports WWAN or Internet access to a mobile subscriber or user of the mobile service provider 106 .
- the latter function is supported by a user interface 612 that communicates with the WWAN network adapter 602 through the module 606 under control of the service provider application 608 .
- the user interface 612 may include a keypad, display, speaker, microphone, joystick, and/or any other combination user interface devices that enable a mobile subscriber or user to access the WWAN 104 or the Internet 102 (see FIG. 1 ).
- the service provider application 608 also enables the module 606 to provide ad-hoc services to mobile clients 108 .
- the service provider application 608 maintains a session with the server 110 to exchange custom messages with the server.
- the service provider application 608 also maintains a separate session with each mobile client 108 for exchanging custom messages between the service provider application 608 and the mobile client 108 .
- the service provider application 608 provides information on authenticated and permitted clients to the filtered interconnection and session monitoring module 606 .
- the filtered interconnection and session monitoring module 608 allows content flow for only authenticated and permitted mobile clients 108 .
- the filtered interconnection and session monitoring module 606 also optionally monitors information regarding content flow related to mobile clients 108 such as the amount of content outbound from the mobile clients and inbound to the mobile clients, and regarding WWAN and WLAN network resource utilization and available bandwidths on the wireless channels.
- the filtered interconnection and session monitoring module 606 can additionally and optionally provide such information to the service provider application 608 .
- the service provider application 608 can optionally act on such information and take appropriate actions such as determining whether to continue maintaining connectivity with the mobile clients 108 and with the server, or whether to continue to provide service. It should be noted that the functions described in modules 606 and 608 can be implemented in any given platform in one or multiple sets of modules that coordinate to provide such functionality at the mobile service provider 106 .
- the service provider application 608 sends a request to the server 110 for approval.
- the service provider application 608 requests authentication by the server 110 and approval from the server 110 to provide service to one or more mobile clients 108 .
- the server 110 may authenticate the mobile service provider 106 and then determine whether it will grant the mobile service provider's request. As discussed earlier, the request may be denied if the number of mobile service providers in the same geographic location is too great or if the WWAN operator has imposed certain constraints on the mobile service provider 106 .
- the service provider application 608 may advertise an ad-hoc WLAN Service Set Identifier (SSID). Interested mobile clients 108 may associate with the SSID to access the mobile service provider 106 . The service provider application 608 may then authenticate the mobile clients 108 with the server 110 and then configure the filtered interconnection and session monitoring module 606 to connect the mobile clients 108 to the server. During the authentication of a mobile client 108 , the service provider application 608 may use an unsecured wireless link.
- SSID ad-hoc WLAN Service Set Identifier
- the service provider application 608 may optionally choose to move a mobile client 108 to a new SSID with a secure link once the mobile client 108 is authenticated. In such situations, the service provider application 608 may distribute the time it spends in each SSID depending on the load that it has to support for existing sessions with mobile clients 108 .
- the service provider application 608 may also be able to determine whether it can support a mobile client 108 before allowing the mobile client 108 to access a network. Resource intelligence that estimates the drain on the battery power and other processing resources that would occur by accepting a mobile client 108 may assist in determining whether the service provider application 608 should consider supporting a new mobile client 108 or accepting a handoff of that mobile client 108 from another mobile service provider 106 .
- the service provider application 608 may admit mobile clients 108 and provide them with a certain QoS guarantee, such as an expected average bandwidth during a session. Average throughputs provided to each mobile client 108 over a time window may be monitored. The service provider application 608 may monitor the throughputs for all flows going through it to ensure that resource utilization by the mobile clients 108 is below a certain threshold, and that it is meeting the QoS requirement that it has agreed to provide to the mobile clients 108 during the establishment of the session.
- a certain QoS guarantee such as an expected average bandwidth during a session.
- Average throughputs provided to each mobile client 108 over a time window may be monitored.
- the service provider application 608 may monitor the throughputs for all flows going through it to ensure that resource utilization by the mobile clients 108 is below a certain threshold, and that it is meeting the QoS requirement that it has agreed to provide to the mobile clients 108 during the establishment of the session.
- the service provider application 608 may also provide a certain level of security to the wireless access point by routing content through the filtered interconnection and session monitoring module 606 without being able to decipher the content. Similarly, the service provider application 608 may be configured to ensure content routed between the user interface 610 and the WWAN 104 via the module 606 cannot be deciphered by mobile clients 108 . The service provider application 608 may use any suitable encryption technology to implement this functionality.
- the service provider application 608 may also maintain a time period for a mobile client 108 to access a network.
- the time period may be agreed upon between the service provider application 608 and the mobile client 108 during the initiation of the session. If the service provider application 608 determines that it is unable to provide the mobile client 108 with access to the network for the agreed upon time period, then it may notify both the server and the mobile client 108 regarding its unavailability. This may occur due to energy constraints (e.g., a low battery), or other unforeseen events.
- the server may then consider a handoff of the mobile client to another mobile service provider, if there is such a mobile service provider in the vicinity of the mobile client 108 .
- the service provider application 608 may support the handoff of the mobile client 108 .
- the service provider application 608 may also dedicate processing resources to maintain a wireless link or limited session with mobile clients 108 served by other mobile service providers. This may facilitate the handoff of mobile clients 108 to the mobile service provider 106 .
- the service provider application 608 may manage the mobile client 108 generally, and the session specifically, through the user interface 612 .
- the service provider application 608 may support a seamless operation mode with processing resources being dedicated to servicing mobile clients 108 .
- the mobile client 108 is managed in a way that is transparent to the mobile subscriber.
- the seamless operation mode may be desired where the mobile subscriber does not want to be managing mobile clients 108 , but would like to continue generating revenue by sharing bandwidth with mobile clients 108 .
- a TLS session may be used by the mobile client 108 to register with the server 110 .
- the mobile client 108 may search for available mobile service providers 106 .
- the mobile client 108 detects the presence of one or more mobile service providers 106 , it may initiate a session using EAP-TTLS with a mobile service provider 106 based on parameters such as the available bandwidth that the mobile service provider 106 can support, the QoS metric of the mobile service provider 106 , and the cost of the service advertised.
- a link encryption key may be established between the mobile client 108 and the mobile service provider 106 during the establishment of the session.
- An SSL VPN session may be established between the mobile client 108 and the server 110 so that all traffic between the two is encrypted.
- the transport layer ports may be kept in the open and not encrypted to provide visibility for the network address translation functionality at the mobile service provider 106 .
- the handoff of the mobile client 108 may be performed in a variety of ways.
- the mobile client 108 may maintain a limited session with multiple mobile service providers 106 , while using one mobile service provider 106 to access the Internet. As described earlier, this approach may facilitate the handoff process.
- the mobile client 108 may consider a handoff only when necessary.
- the mobile client 108 may maintain an active list of mobile service providers 106 in its vicinity for handoff. The mobile client 108 may select a mobile service provider 106 for handoff from the active list when the current mobile service provider 106 needs to discontinue its service.
- a mobile client 108 may need to reconnect through a different mobile service provider 106 to access the Internet. Persistence of the tunnel between the mobile client and the server can enable a soft handoff of a mobile client from one service provider to another service provider.
- the mobile client 108 may access multiple mobile service providers 106 simultaneously.
- a mobile client 108 with multiple transceivers could potentially access multiple mobile service providers 106 simultaneously using a different transceiver for each mobile service provider 106 .
- different channels may be used. If the mobile client 108 has only one transceiver available, then it may distribute the time that it spends accessing each mobile service provider 106 .
Abstract
A server is configured to maintain a session with a mobile client through a first mobile service provider. The server is further configured to pre-authenticate a second mobile service provider for handoff. The server is also configured to enable the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
Description
- The present application for patent claims priority under 35 U.S.C. §119 to Provisional Application No. 60/956,658 entitled, “Method For A Heterogeneous Wireless Ad Hoc Mobile Service Provider,” filed Aug. 17, 2007 and Provisional Application No. 60/980,557 entitled, “Handoff In Ad-Hoc Mobile Broadband Exchange,” filed Oct. 17, 2007.
- 1. Field
- The present disclosure relates generally to telecommunications, and more specifically to handoff in an ad-hoc mobile broadband network.
- 2. Background
- Wireless telecommunication systems are widely deployed to provide various services to consumers, such as telephony, data, video, audio, messaging, broadcasts, etc. These systems continue to evolve as market forces drive wireless telecommunications to new heights. Today, wireless networks are providing broadband Internet access to mobile subscribers over a regional, a nationwide, or even a global region. Such networks are sometimes referred to as Wireless Wide Area Networks (WWANs). WWAN operators generally offer wireless access plans to their subscribers such as subscription plans at a monthly fixed rate.
- Accessing WWANs from all mobile devices may not be possible. Some mobile devices may not have a WWAN radio. Other mobile devices with a WWAN radio may not have a subscription plan enabled. Ad-hoc networking allows mobile devices to dynamically connect over wireless interfaces using protocols such as WLAN, Bluetooth, UWB or other protocols. There is a need in the art for a methodology to allow a user of a mobile device without WWAN access to dynamically subscribe to wireless access service provided by a user with a WWAN-capable mobile device using wireless ad-hoc networking between the mobile devices belong to the two users.
- In one aspect of the disclosure, a server includes a processing system configured to maintain a session with a mobile client through a first mobile service provider. The processing system is further configured to authenticate a second mobile service provider for handoff. The processing system is also configured to enable the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- In another aspect of the disclosure, a server includes means for maintaining a session with a mobile client through a first mobile service provider, means for pre-authenticating a second mobile service provider for handoff, and means for enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- In a further aspect of the disclosure, a method of providing service from a server includes maintaining a session with a mobile client through a first mobile service provider. The method further includes pre-authenticating a second mobile service provider for handoff, and enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- Inside yet a further aspect of the disclosure, machine-readable medium includes instructions executable by a processing system in a server. The instructions include code for maintaining a session with a mobile client through a first mobile service provider. The instructions further include code for pre-authenticating a second mobile service provider for handoff, and enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
- It is understood that other embodiments of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein various embodiments of the invention are shown and described by way of illustration. As will be realized, the invention is capable of other and different embodiments and its several details are capable of modification in various other respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
-
FIG. 1 is a simplified block diagram illustrating an example of a telecommunications system. -
FIG. 2 is a simplified block diagram illustrating an example of a handoff in a telecommunications system. -
FIG. 3 is a call flow diagram illustrating an example of a pre-authentication process for handoff. -
FIG. 4 is a simplified block diagram illustrating an example of a hardware configuration for a server. -
FIG. 5 is a simplified block diagram illustrating an example of a hardware configuration for a processing system in a server. -
FIG. 6 is a simplified block diagram illustrating an example of the functionality of a mobile service provider. - The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations of the present invention and is not intended to represent the only configurations in which the present invention may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the present invention.
-
FIG. 1 is a simplified block diagram illustrating an example of a telecommunications system. Thetelecommunications system 100 is shown with multiple WWANs that provide broadband access to anetwork 102 for mobile subscribers. Thenetwork 102 may be a packet-based network such as the Internet or some other suitable network. For clarity of presentation, two WWANs 104 are shown with a backhaul connection to the Internet 102. Each WWAN 104 may be implemented with multiple fixed-site base stations (not shown) dispersed throughout a geographic region. The geographic region may be generally subdivided into smaller regions known as cells. Each base station may be configured to serve all mobile subscribers within its respective cell. A base station controller (not shown) may be used to manage and coordinate the base stations in the WWAN 104 and support the backhaul connection to the Internet 102. - Each WWAN 104 may use one of many different wireless access protocols to support radio communications with mobile subscribers. By way of example, one WWAN 104 may support Evolution-Data Optimized (EV-DO), while the other WWAN 104 may support Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs multiple access techniques such as Code Division Multiple Access (CDMA) to provide broadband Internet access to mobile subscribers. Alternatively, one of WWAN 104 may support Long Term Evolution (LTE), which is a project within the 3GPP2 to improve the Universal Mobile Telecommunications System (UMTS) mobile phone standard based primarily on a Wideband CDMA (W-CDMA) air interface. One of WWAN 104 may also support the WiMAX standard being developed by the WiMAX forum. The actual wireless access protocol employed by a WWAN for any particular telecommunications system will depend on the specific application and the overall design constraints imposed on the system. The various techniques presented throughout this disclosure are equally applicable to any combination of heterogeneous or homogeneous WWANs regardless of the wireless access protocols utilized.
- Each WWAN 104 has a number of mobile subscribers. Each subscriber may have a
mobile node 106 capable of accessing the Internet 102 directly through the WWAN 104. In the telecommunications system shown inFIG. 1 , thesemobile nodes 106 access the WWAN 104 using an EV-DO, UMB or LTE wireless access protocol; however, in actual implementations, thesemobile nodes 106 may be configured to support any wireless access protocol. - One or more of these
mobile nodes 106 may be configured to create in its vicinity an ad-hoc network based on the same or different wireless access protocol used to access the WWAN 104. By way of example, amobile node 106 may support a UMB wireless access protocol with a WWAN, while providing an IEEE 802.11 access point formobile nodes 108 that cannot directly access a WWAN. IEEE 802.11 denotes a set of Wireless Local Access Network (WLAN) standards developed by the IEEE 802.11 committee for short-range communications (e.g., tens of meters to a few hundred meters). Although IEEE 802.11 is a common WLAN wireless access protocol, other suitable protocols may be used. - A
mobile node 106 that may be used to provide an access point for anothermobile node 108 will be referred to herein as a “mobile service provider.” Amobile node 108 that may use an access point of amobile service provider 106 will be referred to herein as a “mobile client.” A mobile node, whether amobile service provider 106 or amobile client 108, may be a laptop computer, a mobile telephone, a personal digital assistant (PDA), a mobile digital audio player, a mobile game console, a digital camera, a digital camcorder, a mobile audio device, a mobile video device, a mobile multimedia device, or any other device capable of supporting at least one wireless access protocol. - The
mobile service provider 106 may extend its wireless broadband Internet access service tomobile clients 108 that would otherwise not have Internet access. Aserver 110 may be used as an “exchange” to enablemobile clients 108 to purchase unused bandwidth frommobile service providers 106 to access, for example, theInternet 102 acrossWWANs 104. - A
mobile service provider 106, aserver 110, and one or moremobile clients 108 may establish a network that is an ad-hoc heterogeneous wireless network. By way of example, a heterogeneous wireless network may include at least two types of wireless networks (e.g., a WWAN and a WLAN). By way of example, an ad-hoc network may be a network whose specific configuration may change from time to time or from the formation of one network to the next. The network configuration is not pre-planned prior to establishing the network. Examples of configurations for an ad-hoc network may include a configuration as to which members are to be in the network (e.g., which mobile service provider, which server, and/or which mobile client(s) are to be included in a network), a configuration as to the geographic locations of a mobile service provider and mobile client(s), and a configuration as to when and how long a network is to be established. - In one example of an exchange,
mobile clients 108 register with theserver 110. Once registered, amobile client 108 may search for availablemobile service providers 106 when Internet access is desired. When themobile client 108 detects the presence of one or moremobile service providers 106, it may select amobile service provider 106 to initiate a session with based on various parameters such as bandwidth, Quality of Service (QoS) and cost. Another parameter that may be used by themobile client 108 to select amobile service provider 106 is availability in terms of time. By way of example, a mobile subscriber in an airport may turn on his mobile node (e.g., a laptop computer or a mobile telephone) and use it as amobile service provider 108 for 30 minutes as he awaits his flight. Amobile client 108 requiring access to theInternet 102 for 45 minutes may choose not to select thismobile service provider 106 even if themobile service provider 108 can provide adequate bandwidth with good QoS. Anothermobile client 108, however, requiring Internet access for 15 minutes, may select thismobile service provider 106 because of its bandwidth and QoS. In any event, once amobile client 108 selects amobile service provider 106, a session may be established based on the parameters negotiated be the two (e.g., bandwidth, QoS, duration of the session, etc.). A link encryption key may be established between themobile client 108 and themobile service provider 106 during the establishment of the session. A Secured Socket Layer Virtual Private Network (SSL VPN) session may be established between themobile client 108 and theserver 110. The transport layer ports may be kept in the open and not encrypted to provide visibility for the network address translation functionality at themobile service provider 106. In this example, all Internet traffic is routed through theserver 110 via a client-server tunnel 112 to provide security. - In some telecommunication systems, once a
mobile client 108 has gained access to theInternet 102, it listens for othermobile service providers 106 and measures the signal strength of themobile service providers 106 it can hear. Themobile client 108 uses these measurements to create an active list. The active list is a list ofmobile service providers 106 that can provide service to themobile client 108. Themobile client 108 will continue to measure the signal strength of othermobile service providers 106 and may add or removemobile service providers 106 from the active list as the configuration of the ad-hoc network changes. - One function of the active set is to allow the
mobile client 108 to quickly switch betweenmobile service providers 106 while maintaining the current session with theserver 110. Themobile client 108 may consider a handoff to anothermobile service provider 106 based on any number of factors. These factors may include, by way of example, the inability of themobile service provider 106 to provide the bandwidth or QoS negotiated at the beginning of the session. Alternatively, themobile service provider 106 may not be able to provide Internet access to themobile client 108 for the entire duration of the session. It would not be uncommon for a mobile subscriber on amobile service provider 106 that negotiates a 30 minute session with amobile client 108 to leave the vicinity 15 minutes into the session for whatever reason. In that event, themobile client 108 would need to select a new mobile service provider from the active list for handoff. Theserver 110 uses the active list to pre-authenticate other mobile service providers for handoff during the session between themobile client 108 and the currentmobile service provider 106. By pre-authenticating themobile service provider 106 in the active list before themobile service provider 106 currently serving themobile client 108 goes down, the time required to handoff themobile client 108 can be reduced. - The term “pre-authenticating” as used herein means authenticating a target
mobile service 106 provider for handoff prior to receiving a message from themobile service provider 106 currently serving themobile client 108 relating to the unavailability of the currentmobile service provider 106. The message may provide notification to theserver 110 that the currentmobile service provider 106 has gone down and a hard handoff must be performed to anothermobile service provider 106 if the session between themobile client 108 and theserver 110 is to be maintained. Alternatively, the message may provide notification to theserver 110 that the currentmobile service provider 106 will be going down shortly, or that it can no longer provide themobile client 108 with the service agreed upon (e.g., QoS, bandwidth, etc.). This provides theserver 110 with the option of enabling a soft handoff of themobile client 108 to anothermobile service provider 106. - Pre-authentication includes provisioning, prior to handoff, a potential
new service provider 106 and amobile client 108 with encryption/decryption keys that may be needed for communication between the potentialnew service provider 106 and themobile client 108. - Pre-authentication also includes provisioning, prior to handoff, the
current service provider 106 and thenew service provider 106 with encryption/decryption keys that may be needed for communication between thecurrent service provider 106 and thenew service provider 106. - Pre-authentication also includes authorization of communication between the potential
new service provider 106 and thecurrent service provider 106. It also includes authorization of communication between the potentialnew service provider 106 and themobile client 108. -
FIG. 2 is a simplified block diagram illustrating an example of a handoff in a telecommunications system. In this example, themobile client 108 is being handed off from a currentmobile service provider 106 1 to atarget service provider 106 2. Apersistent tunnel 112 between the twomobile service providers server 110 during handoff. Data packets received by the currentmobile service provider 106 1 during handoff may be forwarded to the targetmobile service provider 106 2 through thetunnel 112. Alternatively, or in addition to, the data packets received by thecurrent service provider 106 1 may be forwarded to the targetmobile service provider 106 2 directly over awireless link 114 between the two as shown inFIG. 2 , or through another mobile service provider (not shown). - The
mobile client 108 may have an IPv4, IPv6, or other suitable address that is used by theserver 110 to maintain the session. The address may be provided to themobile client 108 by theserver 110 or one of themobile service providers 106 in the telecommunications network 100 (seeFIG. 1 ). Alternatively, the address may be stored on themobile client 108. In at least one configuration, the address may be a MobileIP address. - The tunneling anchor is shown in
FIG. 2 as a server. However, the tunneling anchor may be any suitable entity or distributed across multiple entities in thetelecommunications system 100. The tunneling anchor may be coupled to theInternet 102 as shown inFIG. 2 or located elsewhere. By way of example, the tunneling anchor may be located anywhere on theInternet 102 or within the network operator's infrastructure. Those skilled in the art will be readily able to determine the optimal implementation of the tunneling anchor for any particular application based on the performance requirements, the overall design constraints imposed on the system, and/or other relevant factors. -
FIG. 3 is a call flow diagram illustrating an example of the authentication process for handoff. For clarity of presentation, various signaling for themobile service providers 106 andclients 108 to authenticate theserver 110 and register with theserver 110 will be omitted. - In
step 302, a connection may be initiated by amobile service provider 106 1 with theserver 110 when themobile service provider 106 1 is mobile and desires to provide service. Extensible Authentication Protocol-Tunneled Transport Layer Security (EAP-TTLS) may be used for Authentication, Authorization and Accounting (AAA) and secure session establishment for this connection. Instep 304, a connection may be initiated by amobile client 108 with the mobile service provider 106 1 (hereinafter referred to as the “current mobile service provider”) when themobile client 108 requires Internet access. EAP-TTLS may also be used for AAA and secure session establishment. In particular, themobile service provider 106 1 sends the mobile client's credentials to theserver 110 for EAP-AAA authentication. The EAP-TTLS authentication response from theserver 110 is then used to generate a master shared key. Subsequently, a link encryption key may be established between the currentmobile service provider 106 1 and themobile client 108. A SSL VPN session may then be established, instep 306, between themobile client 108 and theserver 110. - It should be noted that information flow may be encrypted using encryption/decryption keys between any pair of nodes (where the nodes comprise the
server 110, thecurrent service provider 106 1, thetarget service provider 106 2, and the mobile client 108). Such encryption/decryption keys can be set up in the system when nodes in the system connect with the server. Typically symmetric key cryptography such as using AES may be used for such encryption or decryption for message-flow between any pair of nodes in the system. - In
step 308, themobile client 108 provides the active list to theserver 110. Alternatively, themobile client 108 can send a report identifying mobile service providers that it can hear accompanied by data indicating the signal strength measurements for each. Theserver 110 may use the report to generate the active list at its end. - The
server 110 pre-authenticates one or more of the mobile service providers in the active list. During pre-authentication of atarget service provider 106 2 with aclient 108, theserver 110 provisions the target-service provider 106 2 with an encryption/decryption key for communication with theclient 108. The server may additionally provision thetarget service provider 106 2 with an encryption/decryption key for communication with thecurrent service provider 106 1. Theserver 110 also provisions theclient 108 with the encryption/decryption key to communicate with thetarget service provider 106 2. Thecurrent service provider 106 1 can be provisioned by theserver 110, either at the time of a handoff or anytime earlier, with the encryption/decryption key to communicate with thetarget service provider 106 2. The exact number of mobile service providers in the active list that are pre-authenticated may depend on the admission control policies implemented by theserver 110. By way of example, theserver 110 may limit the number of mobile service providers at a given location if it determines that additional mobile service providers will adversely affect performance in the WWAN. Additional constraints may be imposed by the WWAN operators that may not want its mobile subscribers to provide service in a given geographic location depending on various network constraints. In any event, theserver 110 pre-authenticates one or more mobile service providers by providing each of them with a key to encrypt the data link between themobile client 108 and the newmobile service provider 106 following handoff. InFIG. 3 , theserver 110 is shown, instep 310, providing the key to one mobile service provider 106 2 (hereinafter referred to as the target mobile service provider). Instep 312, theserver 110 also provides the key to themobile client 108 through the VPN tunnel. - In
step 314, themobile client 108 sends a message to the currentmobile service provider 106 requesting a handoff to an alternate service provider. Step 314 is optional and is indicated by a dotted line from the client to the mobile service provider. - In
step 316, the currentmobile service provider 106, sends a message to theserver 110 requesting a handoff. Such a message is tagged with an identifier that indicates that the handoff was initiated by themobile client 108, or that it was initiated by the currentmobile service provider 106 1. The message may be created at the currentmobile service provider 106 1 as a consequence of the current mobile service provider's unavailability to continue to provide service to the mobile client. Alternatively, the message could have been created at the mobile client (step 314), which needs to be sent by the currentmobile service provider 106, to theserver 110. For a handoff that is initiated directly by the server,step 316 is optional. For a handoff that is initiated by themobile client 108, or by themobile service provider 106 1, instep 318, theserver 110 responds to step 316 by sending a message back to currentmobile service provider 106 1 authorizing handoff. Alternatively, step 318 could be a message from the server initiating a handoff, in the absence of amessage 316 from the currentmobile service provider 106 1. The message sent to the currentmobile service provider 106 1 may identify the targetmobile service provider 106 2 for handoff, or alternatively, allow themobile client 108 to make the decision. In the latter case, the user on themobile client 108 selects a target mobile service provider for handoff in accordance with any admission control policy constraints imposed by theserver 110. Theserver 110 may also provide themobile client 108 with a quality metric for each mobile service provider available to the mobile client. This quality metric may be used to assist the user on amobile client 108 to select a new mobile service provider for handoff. In the example shown inFIG. 3 , themobile client 108 selects the targetmobile service provider 106 2 for handoff. - In
step 320, the server may optionally send a message regarding the handoff to one or moretarget service providers 106 2. Instep 322, the handoff message received from theserver 110 is sent by thecurrent service provider 106, to themobile client 108. - In step 324, the
mobile client 108 establishes a connection with the targetmobile service provider 106 2 by sending a message encrypted with a key. Since the targetmobile service provider 106 2 received the same key during the pre-authentication process, it can decrypt the message and establish a session with themobile client 108 to complete the handoff. The targetmobile service provider 106 2 may also send a message back to theserver 110, in step 326, to signify that the handoff has been successfully completed. - Packets that have left the
mobile client 108 may be in transit to the currentmobile service provider 106 1, or could be at the currentmobile service provider 106 1. These packets need to continue to be supported by the currentmobile service provider 106 1. Other packets that have left themobile client 108 may be in transit to theserver 110, or may be waiting atserver 110 for further processing, or may be in transit to their final destination beyond the tunneling server. Future packets that leave themobile client 108 are sent to the targetmobile service provider 106 2 after handoff. Packets that are destined to themobile client 108 may be waiting at the server. Such packets are sent to the targetmobile service provider 106 2 after handoff. Other packets destined for themobile client 108 may be in transit to the currentmobile service provider 106 1, or may be waiting at the currentmobile service provider 106 1, or may be in transit from the current service provider to themobile client 108, and the currentmobile service provider 106 1 needs to continue to support such packets to be delivered to themobile client 108. The delivery of such packets can be done over a wireless link or a multi-hop wireless path between the currentmobile service provider 106 1 and the targetmobile service provider 106 2. Alternatively, such packets can be delivered by the currentmobile service provider 106 1 to theserver 110, which then sends them through the targetmobile service provider 106 2. Messages between the currentmobile service provider 106 1 and the targetmobile service provider 106 2 may be exchanged either through theserver 110, or over a wireless link or multi-hop wireless path between the service providers. -
FIG. 4 illustrates an example of a hardware implementation for a server. Theserver 110 may be a centralized server or a distributed server. A centralized server may be a dedicated server or integrated into another network-related entity, such as a desktop or laptop computer, mainframe, or other suitable entity. A distributed server may be distributed across multiple servers and/or one or more network-related entities, such as a desktop or laptop computer, mainframe, or some other suitable entity. In at least one configuration, the server may be integrated, either in whole or part, into one or more mobile service providers. - The
server 110 is shown with anetwork interface 402, which may support a wired and/or wireless connection to theInternet 102. Thenetwork interface 402 may be used to implement the physical layer by providing the means to transmit and receive data in accordance with the physical and electrical specifications required to interface to the transmission medium. Thenetwork 402 may also be configured to implement the lower portion of the data link layer by managing access to the transmission medium. - The
server 110 is also shown with aprocessing system 404 that provides various functions, including session management for mobile service providers and clients, pre-authentication of mobile service providers targeted for handoff, handoff of mobile clients from one mobile service providers to another, and data tunneling for mobile clients. Theprocessing system 404 is shown separate from thenetwork interface 402, however, as those skilled in the art will readily appreciate, thenetwork interface 402, or any portion thereof, may be integrated into theprocessing system 404. -
FIG. 5 illustrates an example of a hardware implementation for a processing system in a server. In this example, theprocessing system 404 may be implemented with a bus architecture represented generally bybus 502. Thebus 502 may include any number of interconnecting buses and bridges depending on the specific application of theprocessing system 404 and the overall design constraints. The bus links together various circuits including aprocessor 504 and machine-readable media 506. Thebus 502 may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. Anetwork adapter 508 provides an interface between the network interface 402 (seeFIG. 4 ) and thebus 502. - The
processor 504 is responsible for managing the bus and general processing, including the execution of software stored on the machine-readable media 506. Theprocessor 504 may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Machine-readable media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. - In the hardware implementation illustrated in
FIG. 5 , the machine-readable media 506 is shown as part of theprocessing system 404 separate from theprocessor 504. However, as those skilled in the art will readily appreciate, the machine-readable media 506, or any portion thereof, may be external to theprocessing system 404. By way of example, the machine-readable media 506 may include a transmission line, a carrier wave modulated by data, and/or a computer product separate from the server, all which may be accessed by theprocessor 504 through thenetwork adapter 508. Alternatively, or in addition to, the machinereadable media 506, or any portion thereof, may be integrated into theprocessor 504, such as the case may be with cache and/or general register files. - The
processing system 404 may be configured as a general-purpose processing system with one or more microprocessors providing the processor functionality and external memory providing at least a portion of the machine-readable media 506, all linked together with other supporting circuitry through an external bus architecture. Alternatively, theprocessing system 404 may be implemented with an ASIC (Application Specific Integrated Circuit) with theprocessor 504, thenetwork adapter 508, supporting circuitry (not shown), and at least a portion of the machine-readable media 506 integrated into a single chip, or with one or more FPGAs (Field Programmable Gate Array), PLDs (Programmable Logic Device), controllers, state machines, gated logic, discrete hardware components, or any other suitable circuitry, or any combination of circuits that can perform the various functionality described throughout this disclosure. Those skilled in the art will recognize how best to implement the described functionality for theprocessing system 404 depending on the particular application and the overall design constraints imposed on the overall system. - The machine-
readable media 506 is shown with a number of software modules. The software modules include aprotocol stack module 509, apre-authentication module 510, asession manager module 512, atunneling module 514, and ahandoff module 516. These software modules include instruction sets that when executed by theprocessor 504 cause theprocessing system 402 to carry out the process steps as shown and described inFIGS. 1-3 . Each software module may reside in a single storage device or distributed across multiple memory devices. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs (e.g., a mobile node decides to become a mobile service provider). During execution of the software module, theprocessor 504 may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by theprocessor 504. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by theprocessor 504 when executing instructions from that software module. - The
protocol stack module 509 may be used to implement the protocol architecture, or any portion thereof, for the server. In the implementation described thus far, theprotocol stack module 509 is responsible for implementing several protocol layers running on top of the data link layer implemented by the network interface 402 (seeFIG. 4 ). By way of example, theprotocol stack module 509 may be used to implement the upper portion of the data link layer by providing flow control, acknowledgement, and error recovery. Theprotocol stack module 509 may also be used to implement the network layer by managing source to destination data packet transfer, as well as the transport layer by providing transparent transfer of data between end users. Although described as part of the processing system, theprotocol stack module 509, or any portion thereof, may be implemented by thenetwork interface 402. - The
session manager module 512 may be used by the server to maintain sessions with the mobile service providers and clients. - The
pre-authentication module 510 may be used to pre-authenticate mobile service providers for handoff. Thepre-authentication module 510 may receive from a mobile client a list of mobile service providers in the coverage region for the mobile client and use the list to identify the mobile service provider for pre-authentication. - The
handoff module 516 may be used to enable the handoff of a mobile client between mobile service providers while thesession manager module 512 maintains the session with the mobile client. Thehandoff module 516 may enable handoff by authenticating the mobile client for the target service provider prior to handoff and provisioning the target service provider and the mobile client with a key to support an encrypted link between the two following handoff. The handoff may be enabled in response to various messages, including by way of example, a message indicating that the mobile client has selected the target service provider, a message indicating the unavailability of the service provider currently serving the mobile client, or a request from the mobile client for a handoff. The handoff may be a hard or soft handoff. When the handoff is complete, an indication may be received by thehandoff module 516. Thehandoff module 516 may further provide a method for forwarding packets received by the current service provider to the target service provider following handoff through a tunnel between the server and the target service provider, a wireless link, another mobile service provider, or by some other suitable means. - The
tunneling module 514 may be used by the server to maintain tunnels with mobile service providers and clients. Thetunneling module 514 may also be used to maintain a tunnel with a mobile client during handoff from a current mobile service provider to a target service provider. In the disclosed configuration, the tunneling is performed by a module in the server. However, in other configurations, the tunneling of data between the Internet and the nodes (i.e., mobile service providers and clients) may be located elsewhere in the network. -
FIG. 6 is a simplified block diagram illustrating an example of the functionality of a mobile service provider. Themobile service provider 106 has the ability to bridge wireless links over homogeneous or heterogeneous wireless access protocols. This may be achieved with a WWAN network adapter 602 that supports a wireless access protocol for a WWAN to theInternet 102, and aWLAN network adapter 604 that provides a wireless access point formobile clients 108. By way of example, the WWAN network adapter 602 may include a transceiver function that supports EV-DO for Internet access through a WWAN, and theWLAN network adapter 604 may include a transceiver function that provides an 802.11 access point formobile clients 108. Eachnetwork adapter 602, 604 may be configured to implement the physical layer by demodulating wireless signals and performing other radio frequency (RF) front end processing. Eachnetwork adapter 602, 604 may also be configured to implement the data link layer by managing the transfer of data across the physical layer. - The
mobile service provider 106 is shown with a filtered interconnection andsession monitoring module 606. Themodule 606 provides filtered processing of content frommobile clients 108 so that the interconnection between the ad-hoc wireless links to the WWAN network interface 602 is provided only tomobile clients 108 authenticated and permitted by the server to use the WWAN network. Themodule 606 also maintains tunneled connectivity between the server and the authenticatedmobile clients 108. - The
mobile service provider 106 also includes aservice provider application 608 that (1) enables themodule 606 to provide ad-hoc services tomobile clients 108, and (2) supports WWAN or Internet access to a mobile subscriber or user of themobile service provider 106. The latter function is supported by auser interface 612 that communicates with the WWAN network adapter 602 through themodule 606 under control of theservice provider application 608. Theuser interface 612 may include a keypad, display, speaker, microphone, joystick, and/or any other combination user interface devices that enable a mobile subscriber or user to access theWWAN 104 or the Internet 102 (seeFIG. 1 ). - As discussed above, the
service provider application 608 also enables themodule 606 to provide ad-hoc services tomobile clients 108. Theservice provider application 608 maintains a session with theserver 110 to exchange custom messages with the server. In addition, theservice provider application 608 also maintains a separate session with eachmobile client 108 for exchanging custom messages between theservice provider application 608 and themobile client 108. Theservice provider application 608 provides information on authenticated and permitted clients to the filtered interconnection andsession monitoring module 606. The filtered interconnection andsession monitoring module 608 allows content flow for only authenticated and permittedmobile clients 108. The filtered interconnection andsession monitoring module 606 also optionally monitors information regarding content flow related tomobile clients 108 such as the amount of content outbound from the mobile clients and inbound to the mobile clients, and regarding WWAN and WLAN network resource utilization and available bandwidths on the wireless channels. The filtered interconnection andsession monitoring module 606 can additionally and optionally provide such information to theservice provider application 608. Theservice provider application 608 can optionally act on such information and take appropriate actions such as determining whether to continue maintaining connectivity with themobile clients 108 and with the server, or whether to continue to provide service. It should be noted that the functions described inmodules mobile service provider 106. - When the
mobile service provider 106 decides to provide these services, theservice provider application 608 sends a request to theserver 110 for approval. Theservice provider application 608 requests authentication by theserver 110 and approval from theserver 110 to provide service to one or moremobile clients 108. Theserver 110 may authenticate themobile service provider 106 and then determine whether it will grant the mobile service provider's request. As discussed earlier, the request may be denied if the number of mobile service providers in the same geographic location is too great or if the WWAN operator has imposed certain constraints on themobile service provider 106. - Once the
mobile service provider 106 is authenticated, theservice provider application 608 may advertise an ad-hoc WLAN Service Set Identifier (SSID). Interestedmobile clients 108 may associate with the SSID to access themobile service provider 106. Theservice provider application 608 may then authenticate themobile clients 108 with theserver 110 and then configure the filtered interconnection andsession monitoring module 606 to connect themobile clients 108 to the server. During the authentication of amobile client 108, theservice provider application 608 may use an unsecured wireless link. - The
service provider application 608 may optionally choose to move amobile client 108 to a new SSID with a secure link once themobile client 108 is authenticated. In such situations, theservice provider application 608 may distribute the time it spends in each SSID depending on the load that it has to support for existing sessions withmobile clients 108. - The
service provider application 608 may also be able to determine whether it can support amobile client 108 before allowing themobile client 108 to access a network. Resource intelligence that estimates the drain on the battery power and other processing resources that would occur by accepting amobile client 108 may assist in determining whether theservice provider application 608 should consider supporting a newmobile client 108 or accepting a handoff of thatmobile client 108 from anothermobile service provider 106. - The
service provider application 608 may admitmobile clients 108 and provide them with a certain QoS guarantee, such as an expected average bandwidth during a session. Average throughputs provided to eachmobile client 108 over a time window may be monitored. Theservice provider application 608 may monitor the throughputs for all flows going through it to ensure that resource utilization by themobile clients 108 is below a certain threshold, and that it is meeting the QoS requirement that it has agreed to provide to themobile clients 108 during the establishment of the session. - The
service provider application 608 may also provide a certain level of security to the wireless access point by routing content through the filtered interconnection andsession monitoring module 606 without being able to decipher the content. Similarly, theservice provider application 608 may be configured to ensure content routed between the user interface 610 and theWWAN 104 via themodule 606 cannot be deciphered bymobile clients 108. Theservice provider application 608 may use any suitable encryption technology to implement this functionality. - The
service provider application 608 may also maintain a time period for amobile client 108 to access a network. The time period may be agreed upon between theservice provider application 608 and themobile client 108 during the initiation of the session. If theservice provider application 608 determines that it is unable to provide themobile client 108 with access to the network for the agreed upon time period, then it may notify both the server and themobile client 108 regarding its unavailability. This may occur due to energy constraints (e.g., a low battery), or other unforeseen events. The server may then consider a handoff of the mobile client to another mobile service provider, if there is such a mobile service provider in the vicinity of themobile client 108. Theservice provider application 608 may support the handoff of themobile client 108. - The
service provider application 608 may also dedicate processing resources to maintain a wireless link or limited session withmobile clients 108 served by other mobile service providers. This may facilitate the handoff ofmobile clients 108 to themobile service provider 106. - The
service provider application 608 may manage themobile client 108 generally, and the session specifically, through theuser interface 612. Alternatively, theservice provider application 608 may support a seamless operation mode with processing resources being dedicated to servicingmobile clients 108. In this way, themobile client 108 is managed in a way that is transparent to the mobile subscriber. The seamless operation mode may be desired where the mobile subscriber does not want to be managingmobile clients 108, but would like to continue generating revenue by sharing bandwidth withmobile clients 108. - Turning now to the mobile client, a TLS session may be used by the
mobile client 108 to register with theserver 110. Once registered, themobile client 108 may search for availablemobile service providers 106. When themobile client 108 detects the presence of one or moremobile service providers 106, it may initiate a session using EAP-TTLS with amobile service provider 106 based on parameters such as the available bandwidth that themobile service provider 106 can support, the QoS metric of themobile service provider 106, and the cost of the service advertised. As described earlier, a link encryption key may be established between themobile client 108 and themobile service provider 106 during the establishment of the session. An SSL VPN session may be established between themobile client 108 and theserver 110 so that all traffic between the two is encrypted. The transport layer ports may be kept in the open and not encrypted to provide visibility for the network address translation functionality at themobile service provider 106. - The handoff of the
mobile client 108 may be performed in a variety of ways. In one configuration, themobile client 108 may maintain a limited session with multiplemobile service providers 106, while using onemobile service provider 106 to access the Internet. As described earlier, this approach may facilitate the handoff process. In an alternative configuration, themobile client 108 may consider a handoff only when necessary. In this configuration, themobile client 108 may maintain an active list ofmobile service providers 106 in its vicinity for handoff. Themobile client 108 may select amobile service provider 106 for handoff from the active list when the currentmobile service provider 106 needs to discontinue its service. When handoff is not possible, amobile client 108 may need to reconnect through a differentmobile service provider 106 to access the Internet. Persistence of the tunnel between the mobile client and the server can enable a soft handoff of a mobile client from one service provider to another service provider. - If the bandwidth needs of a
mobile client 108 are greater than the capabilities of the availablemobile service providers 106, then themobile client 108 may access multiplemobile service providers 106 simultaneously. Amobile client 108 with multiple transceivers could potentially access multiplemobile service providers 106 simultaneously using a different transceiver for eachmobile service provider 106. If the same wireless access protocol can be used to access multiplemobile service providers 106, then different channels may be used. If themobile client 108 has only one transceiver available, then it may distribute the time that it spends accessing eachmobile service provider 106. - Those of skill in the art would appreciate that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application.
- It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
- The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. Pronouns in the masculine (e.g., his) include the feminine and neuter gender (e.g., her and its) and vice versa. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.”
Claims (66)
1. A server, comprising:
a processing system configured to maintain a session with a mobile client through a first mobile service provider, the processing system being further configured to pre-authenticate a second mobile service provider for handoff, and wherein the processing system is further configured to enable the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
2. The server of claim 1 wherein the processing system is further configured to authenticate the mobile client for the second service provider prior to the handoff of the mobile client to the second service provider.
3. The server of claim 1 wherein the processing system is further configured to provision the second service provider and the mobile client with a key to support an encrypted link between the mobile client and the second mobile service provider following the handoff.
4. The server of claim 1 wherein the processing system is further configured to receive from the mobile client a list of mobile service providers in the coverage region for the mobile client, the processing system being further configured to use the list to identify the second mobile service provider for pre-authentication.
5. The server of claim 1 wherein the processing system is further configured to enable the handoff in response to a message indicating that the mobile client has selected the second mobile service provider for the handoff.
6. The server of claim 1 wherein the processing system is further configured to enable the handoff in response to a message relating to the unavailability of the first mobile service provider.
7. The server of claim 1 wherein the processing system is further configured to enable the handoff in response to a message relating to a request from the mobile client for a handoff from the first mobile service provider to the second mobile service provider.
8. The server of claim 1 wherein the processing system is further configured to initiate the handoff of the mobile client from the first mobile service provider to the second mobile service provider.
9. The server of claim 1 wherein the processing system is further configured to enable the handoff by providing a request to the first mobile service provider to handoff the mobile client, the processing system being further configured to receive from the second mobile service provider an indication when the handoff is complete.
10. The server of claim 1 wherein the processing system is further configured to support a tunnel with the mobile client.
11. The server of claim 10 wherein the processing system is further to maintain the tunnel with the mobile client during the handoff of the mobile client from the first mobile service provider to the second mobile service provider.
12. The server of claim 10 wherein the processing system is further configured to forward at least some packets received by the first mobile service provider from the mobile client through the tunnel to the second mobile service provider.
13. The server of claim 1 which the processing system is further configured to support forwarding of at least some packets from the first mobile service provider to the second mobile service provider over a wireless link between the first and second service providers.
14. The server of claim 13 wherein the processing system is further configured to support the forwarding of the packets from the first mobile service provider to the second mobile service provider through another mobile service provider.
15. The server of claim 1 wherein the processing system is further configured to provide an IPv4 or IPv6 address to the mobile client.
16. The server of claim 15 wherein the IPv4 or IPv6 address comprises a MobileIP address.
17. The server of claim 1 wherein the handoff comprises a hard handoff.
18. The server of claim 1 wherein the handoff comprises a soft handoff.
19. A server, comprising:
means for maintaining a session with a mobile client through a first mobile service provider;
means for pre-authenticating a second mobile service provider for handoff; and
means for enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
20. The server of claim 19 wherein the means for pre-authenticating the second mobile service provider comprises means for providing the second mobile service provider with a key to support an encrypted link between the mobile client and the second mobile service provider following the handoff.
21. The server of claim 20 further comprising means for providing the key to the mobile client.
22. The server of claim 19 further comprising means for receiving from the mobile client a list of mobile service providers in the coverage region for the mobile client and means for using the list to identify the second mobile service provider for pre-authentication.
23. The server of claim 19 wherein the means for enabling the handoff comprises means for enabling the handoff in response to a message indicating that the mobile client has selected the second mobile service provider for the handoff.
24. The server of claim 19 wherein the means for enabling the handoff comprises means for enabling the handoff in response to a message relating to the unavailability of the first mobile service provider.
25. The server of claim 19 wherein the means for enabling the handoff comprises means for providing a request to the first mobile service provider to handoff the mobile client and means for receiving from the second mobile service provider an indication when the handoff is complete.
26. The server of claim 19 wherein the means for maintaining a session with the mobile client further comprises means for supporting a tunnel with the mobile client.
27. The server of claim 26 wherein the means for supporting the tunnel is configured to maintain the tunnel with the mobile client during the handoff of the mobile client from the first mobile service provider to the second mobile service provider.
28. The server of claim 26 further comprising means for forwarding at least some packets received by the first mobile service provider from the mobile client through the tunnel to the second mobile service provider.
29. The server of claim 19 means for maintaining a session with the mobile client further comprises means for supporting forwarding of at least some packets from the first mobile service provider to the second mobile service provider over a wireless link between the first and second service providers.
30. The server of claim 29 wherein the means for supporting the forwarding of packets is configured to support the forwarding of the packets from the first mobile service provider to the second mobile service provider through another mobile service provider.
31. The server of claim 19 further comprising means for providing an IPv4 or IPv6 address to the mobile client.
32. The server of claim 31 wherein the IPv4 or IPv6 address comprises a MobileIP address.
33. The server of claim 19 wherein the handoff comprises a hard handoff.
34. The server of claim 19 wherein the handoff comprises a soft handoff.
35. A method of providing service from a server, comprising:
maintaining a session with a mobile client through a first mobile service provider;
pre-authenticating second mobile service provider for handoff; and
enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
36. The method of claim 35 wherein the second mobile service provider is pre-authenticated by providing the second mobile service provider with a key to support an encrypted link between the mobile client and the second mobile service provider following the handoff.
37. The method of claim 36 further comprising providing the key to the mobile client.
38. The method of claim 35 further comprising receiving from the mobile client a list of mobile service providers in the coverage region for the mobile client and using the list to identify the second mobile service provider for pre-authentication.
39. The method of claim 35 wherein the handoff is enabled in response to a message indicating that the mobile client has selected the second mobile service provider for the handoff.
40. The method of claim 35 wherein the handoff is enabled in response to a message relating to the unavailability of the first mobile service provider.
41. The method of claim 35 wherein the handoff is enabled by providing a request to the first mobile service provider to handoff the mobile client and receiving from the second mobile service provider an indication when the handoff is complete.
42. The method of claim 35 wherein the session is maintained by supporting a tunnel with the mobile client.
43. The method of claim 42 wherein the tunnel with the mobile client is supported during the handoff of the mobile client from the first mobile service provider to the second mobile service provider.
44. The method of claim 42 further comprising forwarding at least some packets received by the first mobile service provider from the mobile client through the tunnel to the second mobile service provider.
45. The method of claim 35 further comprising supporting forwarding of at least some packets from the first mobile service provider to the second mobile service provider over a wireless link between the first and second service providers.
46. The method of claim 45 wherein the forwarding of packets is supported by forwarding the packets from the first mobile service provider to the second mobile service provider through another mobile service provider.
47. The method of claim 35 further comprising providing an IPv4 or IPv6 address to the mobile client.
48. The method of claim 47 wherein the IPv4 or IPv6 address comprises a MobileIP address.
49. The method of claim 35 wherein the handoff comprises a hard handoff.
50. The method of claim 35 wherein the handoff comprises a soft handoff.
51. A machine-readable medium comprising instructions executable by a processing system in a server, the instructions comprising code for:
maintaining a session with a mobile client through a first mobile service provider;
pre-authenticating a second mobile service provider for handoff; and
enabling the handoff of the mobile client from the first mobile service provider to the second mobile service provider while maintaining the session with the mobile client.
52. The machine-readable medium of claim 51 wherein the code for pre-authenticating the second mobile service provider is configured to provide the second mobile service provider with a key to support an encrypted link between the mobile client and the second mobile service provider following the handoff.
53. The machine-readable medium of claim 52 wherein the instructions further comprise code for providing the key to the mobile client.
54. The machine-readable medium of claim 51 wherein the instructions further comprise code for receiving from the mobile client a list of mobile service providers in the coverage region for the mobile client and using the list to identify the second mobile service provider for pre-authentication.
55. The machine-readable medium of claim 51 wherein the code for enabling the handoff is configured to enable the handoff in response to a message indicating that the mobile client has selected the second mobile service provider for the handoff.
56. The machine-readable medium of claim 51 wherein the code for enabling the handoff is configured to enable the handoff in response to a message relating to the unavailability of the first mobile service provider.
57. The machine-readable medium of claim 51 wherein the code for enabling the handoff is configured to provide a request to the first mobile service provider to handoff the mobile client and receive from the second mobile service provider an indication when the handoff is complete.
58. The machine-readable medium of claim 51 wherein the code for maintaining a session with the mobile client is configured to support a tunnel with the mobile client.
59. The machine-readable medium of claim 58 wherein the code for maintaining a session is further configured to maintain the tunnel with the mobile client during the handoff of the mobile client from the first mobile service provider to the second mobile service provider.
60. The machine-readable medium of claim 58 wherein the instructions further comprise code for forwarding at least some packets received by the first mobile service provider from the mobile client through the tunnel to the second mobile service provider.
61. The machine-readable medium of claim 51 wherein the instructions further comprise code for supporting forwarding of at least some packets from the first mobile service provider to the second mobile service provider over a wireless link between the first and second service providers.
62. The machine-readable medium of claim 61 wherein the code for supporting forwarding of packets is configured to support the forwarding of the packets from the first mobile service provider through the second mobile service provider through another mobile service provider.
63. The machine-readable medium of claim 51 wherein the instructions further comprise code for providing an IPv4 or IPv6 address to the mobile client.
64. The machine-readable medium of claim 63 wherein the IPv4 or IPv6 address comprises a MobileIP address.
65. The machine-readable medium of claim 51 wherein the handoff comprises a hard handoff.
66. The machine-readable medium of claim 51 wherein the handoff comprises a soft handoff.
Priority Applications (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/188,985 US20090047964A1 (en) | 2007-08-17 | 2008-08-08 | Handoff in ad-hoc mobile broadband networks |
EP08827777A EP2179607A2 (en) | 2007-08-17 | 2008-08-13 | Handoff in ad-hoc mobile broadband networks |
CA2694684A CA2694684A1 (en) | 2007-08-17 | 2008-08-13 | Handoff in ad-hoc mobile broadband networks |
JP2010521931A JP2010537567A (en) | 2007-08-17 | 2008-08-13 | Handoff in ad hoc mobile broadband networks |
CN200880102831A CN101785335A (en) | 2007-08-17 | 2008-08-13 | Handoff in AD-HOC mobile broadband networks |
AU2008289251A AU2008289251A1 (en) | 2007-08-17 | 2008-08-13 | Handoff in ad-hoc mobile broadband networks |
KR1020107005901A KR20100054834A (en) | 2007-08-17 | 2008-08-13 | Handoff in ad-hoc mobile broadband networks |
BRPI0814262-9A2A BRPI0814262A2 (en) | 2007-08-17 | 2008-08-13 | RETURN ON AD HOC MOBILE BROADBAND NETWORKS. |
PCT/US2008/073017 WO2009026071A2 (en) | 2007-08-17 | 2008-08-13 | Handoff in ad-hoc mobile broadband networks |
TW097131326A TW200917871A (en) | 2007-08-17 | 2008-08-15 | Handoff in ad-hoc mobile broadband networks |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US95665807P | 2007-08-17 | 2007-08-17 | |
US98055707P | 2007-10-17 | 2007-10-17 | |
US12/188,985 US20090047964A1 (en) | 2007-08-17 | 2008-08-08 | Handoff in ad-hoc mobile broadband networks |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090047964A1 true US20090047964A1 (en) | 2009-02-19 |
Family
ID=40362885
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/188,990 Expired - Fee Related US9392445B2 (en) | 2007-08-17 | 2008-08-08 | Handoff at an ad-hoc mobile service provider |
US12/188,985 Abandoned US20090047964A1 (en) | 2007-08-17 | 2008-08-08 | Handoff in ad-hoc mobile broadband networks |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/188,990 Expired - Fee Related US9392445B2 (en) | 2007-08-17 | 2008-08-08 | Handoff at an ad-hoc mobile service provider |
Country Status (12)
Country | Link |
---|---|
US (2) | US9392445B2 (en) |
EP (2) | EP2179607A2 (en) |
JP (2) | JP2010537567A (en) |
KR (2) | KR20100054834A (en) |
CN (2) | CN101785335A (en) |
AU (2) | AU2008289251A1 (en) |
BR (2) | BRPI0814262A2 (en) |
CA (2) | CA2694684A1 (en) |
MX (2) | MX2010001896A (en) |
RU (2) | RU2010109886A (en) |
TW (2) | TW200915895A (en) |
WO (2) | WO2009026071A2 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090049158A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider topology |
US20090046676A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider configuration for broadcasting service information |
US20090047966A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile internet access service |
US20090046658A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Handoff at an ad-hoc mobile service provider |
US20090046598A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | System and method for acquiring or distributing information related to one or more alternate ad hoc service providers |
US20090073943A1 (en) * | 2007-08-17 | 2009-03-19 | Qualcomm Incorporated | Heterogeneous wireless ad hoc network |
US20100254346A1 (en) * | 2009-04-06 | 2010-10-07 | Robert Bosch Gmbh | Method for performing proactive wireless communication handoffs using a mobile client's route information |
US20110019627A1 (en) * | 2009-05-26 | 2011-01-27 | Qualcomm Incorporated | Maximizing Service Provider Utility in a Heterogeneous Wireless Ad-Hoc Network |
US20110040888A1 (en) * | 2009-08-13 | 2011-02-17 | Qualcomm Incorporated | Method and apparatus for link aggregation in a heterogeneous communication system |
US20110302627A1 (en) * | 2009-02-18 | 2011-12-08 | Telefonaktiebolaget L M Ericsson (Publ) | User authenticaton |
US20130332725A1 (en) * | 2012-06-04 | 2013-12-12 | Sony Corporation | Information processing apparatus, information processing system, information processing method, and program |
US20140325043A1 (en) * | 2013-04-28 | 2014-10-30 | Huawei Technologies Co., Ltd. | Network Switching Method, Version Upgrade Method, and Terminal Device |
US11871316B1 (en) * | 2011-04-02 | 2024-01-09 | Philips North America Llc | System and method for persisting mobile agents within a mobile region of interest |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8208635B2 (en) * | 2007-11-13 | 2012-06-26 | Rosemount Inc. | Wireless mesh network with secure automatic key loads to wireless devices |
JP5279296B2 (en) * | 2008-02-22 | 2013-09-04 | キヤノン株式会社 | COMMUNICATION DEVICE, COMMUNICATION METHOD, PROGRAM, AND STORAGE MEDIUM |
KR20110126123A (en) | 2009-03-16 | 2011-11-22 | 노오텔 네트웍스 리미티드 | Transitioning of packet-switched emergency call between first and second types of wireless access networks |
US20110134883A1 (en) * | 2009-12-09 | 2011-06-09 | Electronics And Telecommunications Research Institute | Network based mobility system and handover method thereof |
KR101819029B1 (en) * | 2011-09-29 | 2018-01-16 | 삼성전자주식회사 | Method and apparatus for providing service |
US9497694B2 (en) * | 2012-03-29 | 2016-11-15 | Nec Corporation | Wireless communication device, wireless communication system and wireless communication method |
US10064095B2 (en) * | 2012-09-29 | 2018-08-28 | Adaptive Spectrum And Signal Alignment, Inc. | Optimized control system for aggregation of multiple broadband connections over radio interfaces |
CN112491623A (en) | 2014-12-04 | 2021-03-12 | 适应性频谱和信号校正股份有限公司 | Method and apparatus for predicting successful DSL line optimization |
US9699817B2 (en) * | 2014-12-16 | 2017-07-04 | Qualcomm Incorporated | Methods to preemptively search and select LTE-direct expressions for uninterrupted device-to-device communication |
RU2622855C1 (en) * | 2016-06-06 | 2017-06-20 | Общество с ограниченной ответственностью "НТЦ Веллинк" | Method and system of selecting of optimal provider for data transmission |
US11373184B2 (en) * | 2017-12-21 | 2022-06-28 | Mastercard International Incorporated | Systems and methods for facilitating network requests |
US10813169B2 (en) | 2018-03-22 | 2020-10-20 | GoTenna, Inc. | Mesh network deployment kit |
CN113924788B (en) * | 2019-07-01 | 2023-12-01 | 住友电气工业株式会社 | Vehicle-mounted device, control method thereof and vehicle |
Citations (98)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5301359A (en) * | 1989-04-27 | 1994-04-05 | Motorola, Inc. | Bulletin board resource for communication system access |
US20010012757A1 (en) * | 2000-02-03 | 2001-08-09 | U.S. Philips Corporation | Ad-hoc radio communication system |
US6295453B1 (en) * | 1998-10-07 | 2001-09-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Multi-full rate channel assignment for a cellular telephone system |
US20010024443A1 (en) * | 1999-12-20 | 2001-09-27 | Fredrik Alriksson | Mobile IP for mobile Ad Hoc networks |
US20020039367A1 (en) * | 2000-09-29 | 2002-04-04 | Jukka Seppala | Selection of serving network element in telecommunications network |
US20020061750A1 (en) * | 1998-05-14 | 2002-05-23 | Behzad Mohebbi | Soft hand-off in cellular mobile communications networks |
US20020080738A1 (en) * | 2000-12-22 | 2002-06-27 | Kim Kyung-Sik | Hard handoff method for packet mobile network |
US20030054796A1 (en) * | 2001-09-17 | 2003-03-20 | Hitachi, Ltd. | Charging method and terminal equipment in the information and communication network system |
US20030095504A1 (en) * | 2000-09-12 | 2003-05-22 | Ogier Richard G. | Reduced-overhead protocol for discovering new neighbor nodes and detecting the loss of existing neighbor nodes in a network |
US20030103521A1 (en) * | 2001-06-18 | 2003-06-05 | Itran Communications Ltd. | Channel access method for powerline carrier based media access control protocol |
US20030157951A1 (en) * | 2002-02-20 | 2003-08-21 | Hasty William V. | System and method for routing 802.11 data traffic across channels to increase ad-hoc network capacity |
US20030198346A1 (en) * | 2002-04-18 | 2003-10-23 | Yoshinobu Meifu | Push delivery service providing method, information providing service system, server system, and user station |
US20030203741A1 (en) * | 2002-04-26 | 2003-10-30 | Kabushiki Kaisha Toshiba | Autonomous distributed wireless network system, method of autonomous distributed wireless network communication and wireless terminal apparatus |
US20030202476A1 (en) * | 2002-04-29 | 2003-10-30 | Harris Corporation | Determining quality of service (QoS) routing for mobile AD HOC networks |
US20040001442A1 (en) * | 2002-06-28 | 2004-01-01 | Rayment Stephen G. | Integrated wireless distribution and mesh backhaul networks |
US20040008663A1 (en) * | 2000-12-29 | 2004-01-15 | Devabhaktuni Srikrishna | Selection of routing paths based upon path quality of a wireless mesh network |
US20040029528A1 (en) * | 2000-11-28 | 2004-02-12 | Chandler Stephen Anthony Gerard | Routing algorithm for distributed telecommunication networks |
US6735417B2 (en) * | 2002-08-15 | 2004-05-11 | Motorola, Inc. | Method and apparatus for relaying information in an AD-HOC network |
US20040174822A1 (en) * | 2003-03-05 | 2004-09-09 | Bui Thomas T. | Systems and methods for providing collaboration between systems |
US20040202120A1 (en) * | 2002-04-17 | 2004-10-14 | Hanson Norman L. | Internet protocol collaborative mobility |
US20050053005A1 (en) * | 2003-09-09 | 2005-03-10 | Harris Corporation | Mobile ad hoc network (MANET) providing connectivity enhancement features and related methods |
US6871071B2 (en) * | 1999-12-28 | 2005-03-22 | Ntt Docomo, Inc. | Handover control method and system |
US6879574B2 (en) * | 2002-06-24 | 2005-04-12 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
US20050088980A1 (en) * | 2001-06-27 | 2005-04-28 | Mikko Olkkonen | Ad hoc network discovery menu |
US20050094588A1 (en) * | 2002-06-12 | 2005-05-05 | Globespan Virata Incorporated | Direct link relay in a wireless network |
US20050136834A1 (en) * | 2003-12-19 | 2005-06-23 | Motorola, Inc. | Communication system with adopted remote identity |
US20050138671A1 (en) * | 2003-12-22 | 2005-06-23 | Love Robert T. | Apparatus and method for adaptive broadcast transmission |
US20050163078A1 (en) * | 2004-01-22 | 2005-07-28 | Toshiba America Research, Inc. | Mobility architecture using pre-authentication, pre-configuration and/or virtual soft-handoff |
US20050197098A1 (en) * | 2004-03-02 | 2005-09-08 | Nokia Corporation | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
US20050228853A1 (en) * | 2004-03-23 | 2005-10-13 | Shinya Yamamura | Method and system for supporting service provision |
US20060005008A1 (en) * | 2004-07-02 | 2006-01-05 | Wen-Hung Kao | Security gateway utilizing ssl protocol protection and related method |
US20060007863A1 (en) * | 2002-09-05 | 2006-01-12 | Siamak Naghian | Signal propagation delay routing |
US7003117B2 (en) * | 2003-02-05 | 2006-02-21 | Voltage Security, Inc. | Identity-based encryption system for secure data distribution |
US20060056368A1 (en) * | 2004-09-10 | 2006-03-16 | Nivis, Llc | System and method for a wireless mesh network of configurable signage |
US20060064589A1 (en) * | 2004-09-17 | 2006-03-23 | Fujitsu Limited | Setting information distribution apparatus, method, program, medium, and setting information reception program |
US20060092939A1 (en) * | 2004-10-29 | 2006-05-04 | Samsung Electronics Co., Ltd. | Apparatus and method for extending mobility in a mobile ad hoc network |
US20060101400A1 (en) * | 2004-10-14 | 2006-05-11 | International Business Machines Corporation | Apparatus and methods for performing computer system maintenance and notification activities in an opportunistic manner |
US20060098598A1 (en) * | 2004-11-10 | 2006-05-11 | Michael Gallagher | Seamless transitions of active calls between enterprise telecommunications networks and licensed public telecommunications networks |
US20060114850A1 (en) * | 2004-01-13 | 2006-06-01 | Joshi Avinash | System and method for achieving continuous connectivity to an access point or gateway in a wireless network following an on-demand routing protocol, and to perform smooth handoff of mobile terminals between fixed terminals in the network |
US20060171403A1 (en) * | 2005-02-01 | 2006-08-03 | Samsung Electronics Co., Ltd. | Gateway for interconnecting ad-hoc network and infrastructure network, and methods for discovering and registering service provider using gateway |
US7089417B2 (en) * | 1998-10-16 | 2006-08-08 | Tecsec, Inc. | Cryptographic information and flow control |
US20060178149A1 (en) * | 2005-02-04 | 2006-08-10 | Kamat Sandip D | Systems and methods for wireless cellular telephone routers |
US20060176852A1 (en) * | 2005-02-04 | 2006-08-10 | Industrial Technology Research Institute | System and method for connection handover in a virtual private network |
US20060215576A1 (en) * | 2005-01-05 | 2006-09-28 | International Business Machines Corporation | Switching between two communicaiton modes in a WLAN |
US20060217062A1 (en) * | 2003-09-23 | 2006-09-28 | Saffre Fabrice T P | Decentralized channel selection in a self-organizing adhoc network |
US20060229080A1 (en) * | 2005-04-08 | 2006-10-12 | The Boeing Company | Net-centric coordination channel (NCC) |
US20060227724A1 (en) * | 2005-04-08 | 2006-10-12 | Pascal Thubert | Arrangement for providing optimized connections between peer routers in a tree-based ad hoc mobile network |
US20060236105A1 (en) * | 2005-03-31 | 2006-10-19 | Jacco Brok | Authenticating a user of a communication device to a wireless network to which the user is not associated with |
US7161914B2 (en) * | 2002-04-11 | 2007-01-09 | Ntt Docomo, Inc. | Context aware application level triggering mechanism for pre-authentication, service adaptation, pre-caching and handover in a heterogeneous network environment |
US20070008902A1 (en) * | 2005-07-11 | 2007-01-11 | Saritha Yaramada | Managing negotiations of quality of service parameters in wireless networks |
US20070016262A1 (en) * | 2005-07-13 | 2007-01-18 | Betastim, Ltd. | Gi and pancreatic device for treating obesity and diabetes |
US7170878B2 (en) * | 2000-03-07 | 2007-01-30 | Sony Corporation | Communication device and communication method |
US20070042769A1 (en) * | 2005-08-17 | 2007-02-22 | Freescale Semiconductor, Inc. | Communications security management |
US20070076875A1 (en) * | 2005-10-05 | 2007-04-05 | Canon Kabushiki Kaisha | Wireless communication system and authentication method and communication control method in wireless communication system |
US20070110009A1 (en) * | 2003-11-12 | 2007-05-17 | Matsushita Electric Industrial Co., Ltd. | Contex transfer in a communication network comprising plural heterogeneous access networks |
US20070111705A1 (en) * | 2004-04-30 | 2007-05-17 | Wenlin Zhang | Method for implementing roaming charging and system thereof |
US20070149139A1 (en) * | 2004-06-10 | 2007-06-28 | Jean-Louis Gauvreau | Wireless Network System with Energy Management |
US7254119B2 (en) * | 2002-05-28 | 2007-08-07 | Zte San Diego, Inc. | Interworking mechanism between CDMA2000 and WLAN |
US7266383B2 (en) * | 2005-02-14 | 2007-09-04 | Scenera Technologies, Llc | Group interaction modes for mobile devices |
US7266374B2 (en) * | 2003-07-22 | 2007-09-04 | Samsung Electronics Co., Ltd. | Communication system and method in wireless infrastructure network environments |
US20070206527A1 (en) * | 2006-03-01 | 2007-09-06 | Yuan-Chang Lo | Virtual access point for configuration of a LAN |
US20070220219A1 (en) * | 2006-03-16 | 2007-09-20 | International Business Machines Corporation | System and method for optimizing data in value-based storage system |
US20070223408A1 (en) * | 2003-10-06 | 2007-09-27 | Broadbeam Corporation | Method and Apparatus for Intelligent Seamless Network Switching |
US20080040481A1 (en) * | 2006-08-11 | 2008-02-14 | Motorola, Inc. | Method and system for compensation in ad hoc networks |
US20080049689A1 (en) * | 2006-08-23 | 2008-02-28 | Motorola, Inc. | Tunneling data to multiple wireless networks from device without connectivity through employment of device with connectivity |
US7340253B2 (en) * | 2002-06-10 | 2008-03-04 | Lucent Technologies Inc. | IP-based distributed wireless access network architecture for CDMA networks |
US7339915B2 (en) * | 2005-10-11 | 2008-03-04 | Cisco Technology, Inc. | Virtual LAN override in a multiple BSSID mode of operation |
US20080069105A1 (en) * | 2004-06-24 | 2008-03-20 | Telecom Italia S.P.A. | Method and System for Controlling Access to Communication Networks, Related Network and Computer Program Therefor |
US20080080387A1 (en) * | 2006-10-02 | 2008-04-03 | Tropos Networks, Inc. | Probe response determination |
US20080089288A1 (en) * | 2006-10-12 | 2008-04-17 | Bellsouth Intellectual Property Corporation | Methods, systems, and computer program products for providing advertising and/or information services over mobile ad hoc cooperative networks using electronic billboards and related devices |
US7363050B2 (en) * | 2005-02-01 | 2008-04-22 | Fujitsu Limited | Mobile station, base station, and wireless communication system |
US7362731B2 (en) * | 2004-03-23 | 2008-04-22 | Nokia Corporation | Selection of network access entity in a communication system |
US20080095134A1 (en) * | 2006-10-23 | 2008-04-24 | Wai Chen | Roadside network unit and method of organizing, managing and maintaining local network using local peer groups as network groups |
US20080112355A1 (en) * | 2006-11-09 | 2008-05-15 | Avaya Technology Llc | Multi-Hop Ad-hoc Wireless Networks That Support Non-Multi-Hop Wireless Terminals |
US20080112362A1 (en) * | 2006-11-10 | 2008-05-15 | Motorola, Inc. | Ip layer-handoff using mobility domains and ip caching |
US20080139239A1 (en) * | 2006-12-11 | 2008-06-12 | O'connor Dennis M | Techniques to share multimedia and enable cellular phone conference calling using ad-hoc wireless networks |
US20080146232A1 (en) * | 2006-12-19 | 2008-06-19 | Douglas Norman Knisely | Neighbor list provision in a communication network |
US7394826B2 (en) * | 2003-09-09 | 2008-07-01 | Harris Corporation | Mobile ad hoc network (MANET) providing quality-of-service (QoS) based unicast and multicast features |
US20080165735A1 (en) * | 2007-01-05 | 2008-07-10 | Jen-Jee Chen | Handoff method of mobile device utilizing dynamic tunnel |
US7408929B2 (en) * | 2001-09-28 | 2008-08-05 | Kabushiki Kaisha Toshiba | Radio communication system, terminal and packet |
US20080192666A1 (en) * | 2007-02-12 | 2008-08-14 | Motorola, Inc. | Method and system for dynamically utilizing a peer network to extend battery life |
US7420952B2 (en) * | 2002-10-28 | 2008-09-02 | Mesh Dynamics, Inc. | High performance wireless networks using distributed control |
US7486651B2 (en) * | 2004-03-02 | 2009-02-03 | Ntt Docomo, Inc. | Mobile node, an ad hoc network routing controlling method and an ad hoc network system |
US20090047966A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile internet access service |
US20090046644A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Service set manager for ad hoc mobile service provider |
US20090046598A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | System and method for acquiring or distributing information related to one or more alternate ad hoc service providers |
US7496363B2 (en) * | 2003-12-17 | 2009-02-24 | Motorola, Inc. | Method of changing access point for a mobile node in a wireless access network |
US7519071B2 (en) * | 2002-09-20 | 2009-04-14 | Cisco Technology, Inc. | Arrangement in a gateway for registering mobile routers of a mobile AD HOC network to respective home agents |
US20090125429A1 (en) * | 1997-08-13 | 2009-05-14 | Matsushita Electric Industrial Co., Ltd. | Mobile electronic commerce system |
US7551576B2 (en) * | 2001-02-06 | 2009-06-23 | Nokia Corporation | Access system for an access network |
US20090172391A1 (en) * | 2004-06-30 | 2009-07-02 | Matsushita Electric Industrial Co., Ltd. | Communication handover method, communication message processing method, and communication control method |
US7573904B2 (en) * | 2002-06-24 | 2009-08-11 | Nokia Corporation | Ad hoc networking of terminals aided by a cellular network |
US7680079B2 (en) * | 2004-11-04 | 2010-03-16 | Samsung Electronics Co., Ltd. | Method of signaling QoS information at hand-over between access networks in an IP-based core network |
US20100202428A1 (en) * | 2000-04-18 | 2010-08-12 | Cisco Technology, Inc. | System and Method for Concurrently Utilizing Multiple System Identifiers |
US7881474B2 (en) * | 2006-07-17 | 2011-02-01 | Nortel Networks Limited | System and method for secure wireless multi-hop network formation |
US20110039566A1 (en) * | 2007-08-27 | 2011-02-17 | Telefonaktiebolaget Lm Ericsson (Publ) | method and a network control node for bandwidth and access control in femto cells of a wireless system |
US20110183685A1 (en) * | 2010-01-20 | 2011-07-28 | Airpatrol Corporation | Multi-band radio frequency detection and location system |
US8717931B2 (en) * | 2004-11-05 | 2014-05-06 | Toshiba America Research, Inc. | Network discovery mechanisms |
Family Cites Families (169)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5263121A (en) | 1991-09-12 | 1993-11-16 | Tellabs, Inc. | Neural network solution for interconnection apparatus |
US5734699A (en) | 1995-05-04 | 1998-03-31 | Interwave Communications International, Ltd. | Cellular private branch exchanges |
US6125185A (en) | 1997-05-27 | 2000-09-26 | Cybercash, Inc. | System and method for encryption key generation |
US6081536A (en) | 1997-06-20 | 2000-06-27 | Tantivy Communications, Inc. | Dynamic bandwidth allocation to transmit a wireless protocol across a code division multiple access (CDMA) radio link |
US6240073B1 (en) | 1997-11-14 | 2001-05-29 | Shiron Satellite Communications (1996) Ltd. | Reverse link for a satellite communication network |
JP3757642B2 (en) | 1998-09-29 | 2006-03-22 | 富士電機機器制御株式会社 | Wireless communication network system |
US6275712B1 (en) | 1999-02-26 | 2001-08-14 | Nokia Mobile Phones Ltd | Mobile station control states based on available power |
SE514264C2 (en) | 1999-05-07 | 2001-01-29 | Ericsson Telefon Ab L M | A communication system |
US7023800B1 (en) | 1999-06-01 | 2006-04-04 | Microsoft Corporation | Congestion avoidance within aggregate channels |
US6377805B1 (en) | 1999-08-04 | 2002-04-23 | International Business Machines Corporation | Maintaining data communication through neighboring mobile units during handoff |
GB9923070D0 (en) | 1999-09-29 | 1999-12-01 | Nokia Telecommunications Oy | Multilayer telecommunications network |
US6954739B1 (en) | 1999-11-16 | 2005-10-11 | Lucent Technologies Inc. | Measurement-based management method for packet communication networks |
US7028186B1 (en) | 2000-02-11 | 2006-04-11 | Nokia, Inc. | Key management methods for wireless LANs |
US6895558B1 (en) | 2000-02-11 | 2005-05-17 | Microsoft Corporation | Multi-access mode electronic personal assistant |
US6650900B1 (en) | 2000-02-29 | 2003-11-18 | Avaya Technology Corp. | Dynamic logical coverage areas for wireless base stations |
EE00315U1 (en) | 2001-02-01 | 2002-07-15 | As Emt | Paid parking method |
WO2001099053A2 (en) | 2000-06-19 | 2001-12-27 | Emt As | Method and system for organizing the payment of parking services |
US6970422B1 (en) | 2000-07-14 | 2005-11-29 | At&T Corp. | Admission control for QoS-Driven Wireless LANs |
US7505451B2 (en) | 2000-10-05 | 2009-03-17 | Sony Corporation | Usage-based charging device and usage-based charging method |
US7072650B2 (en) | 2000-11-13 | 2006-07-04 | Meshnetworks, Inc. | Ad hoc peer-to-peer mobile radio access system interfaced to the PSTN and cellular networks |
DE60039890D1 (en) | 2000-11-17 | 2008-09-25 | Sony Deutschland Gmbh | Information transmission via an ad hoc network |
US8670390B2 (en) | 2000-11-22 | 2014-03-11 | Genghiscomm Holdings, LLC | Cooperative beam-forming in wireless networks |
US7155518B2 (en) | 2001-01-08 | 2006-12-26 | Interactive People Unplugged Ab | Extranet workgroup formation across multiple mobile virtual private networks |
JP4050001B2 (en) | 2001-02-09 | 2008-02-20 | 株式会社 リーテック | Gas-fired hair dryer |
US6882677B2 (en) | 2001-02-28 | 2005-04-19 | Motorola, Inc. | Method and apparatus for facilitating handoff in a wireless local area network |
US20020138635A1 (en) | 2001-03-26 | 2002-09-26 | Nec Usa, Inc. | Multi-ISP controlled access to IP networks, based on third-party operated untrusted access stations |
JP3858746B2 (en) | 2001-05-08 | 2006-12-20 | ソニー株式会社 | Wireless communication system, wireless communication control device, wireless communication control method, and computer program |
US6826154B2 (en) | 2001-05-24 | 2004-11-30 | 3Com Corporation | Method and apparatus for seamless mobility between different access technologies |
US6678517B2 (en) | 2001-06-21 | 2004-01-13 | Spatial Wireless, Inc. | Method and system for providing continuous voice and packet data services to a mobile station |
US20030068975A1 (en) | 2001-08-06 | 2003-04-10 | The Research Foundation Of Suny | Integrated cellular and ad hoc relaying system |
US7295532B2 (en) | 2001-08-17 | 2007-11-13 | Ixi Mobile (R & D), Ltd. | System, device and computer readable medium for providing networking services on a mobile device |
JP4230683B2 (en) | 2001-08-28 | 2009-02-25 | 株式会社エヌ・ティ・ティ・ドコモ | Security judgment method and security judgment device |
EP1289200A1 (en) | 2001-09-04 | 2003-03-05 | Siemens Aktiengesellschaft | Identification procedure for a station with particular functionality in a radio ad-hoc network and network terminal for carrying out such a procedure |
US20040171386A1 (en) | 2001-09-04 | 2004-09-02 | Enric Mitjana | Method for identifying a station with specific functions in a wireless-based ad-hoc network, and a substation for carrying out the method |
US8014305B1 (en) | 2001-09-07 | 2011-09-06 | Qualcomm Atheros, Inc. | Wireless LAN using transmission monitoring |
JP2003101553A (en) | 2001-09-20 | 2003-04-04 | Canon Inc | Device and system for wireless communication, communication connecting method, program and storage medium |
RU2206177C1 (en) | 2001-10-08 | 2003-06-10 | Уральский государственный университет путей сообщения | Carry-on communication network of train |
US7545754B2 (en) | 2001-11-02 | 2009-06-09 | Ntt Docomo, Inc. | Geographically adjacent access router discovery and caching for mobile nodes |
US7684798B2 (en) | 2001-11-09 | 2010-03-23 | Nokia Corporation | Method of pre-authorizing handovers among access routers in communication networks |
AU2002353270A1 (en) | 2001-12-03 | 2003-06-17 | Nokia Corporation | Policy based mechanisms for selecting access routers and mobile context |
RU2192049C1 (en) | 2001-12-26 | 2002-10-27 | Гаврилов Сергей Анатольевич | Method for distributing publicity information messages |
US7206293B2 (en) | 2001-12-28 | 2007-04-17 | Arraycomm Llc | System and related methods for beamforming in a multi-point communications environment |
US6947772B2 (en) | 2002-01-31 | 2005-09-20 | Qualcomm Incorporated | System and method for providing messages on a wireless device connecting to an application server |
JP2003230167A (en) | 2002-02-04 | 2003-08-15 | Ntt Docomo Inc | Mobile communication terminal and connection method possible to connect with ad hoc network |
DE10208689C2 (en) | 2002-02-28 | 2003-11-27 | Deutsch Zentr Luft & Raumfahrt | Method for connecting user terminals serving for communication and belonging to a collectively mobile user network |
EP1484935B1 (en) | 2002-03-13 | 2011-05-11 | Mitsubishi Electric Corporation | Radio area network control system and wide radio area network control system |
US8432893B2 (en) | 2002-03-26 | 2013-04-30 | Interdigital Technology Corporation | RLAN wireless telecommunication system with RAN IP gateway and methods |
US6704584B2 (en) | 2002-04-16 | 2004-03-09 | Thomson Licensing S.A. | Mechanism for a wireless device to relinquish its network master status based on its power reserve |
US6941332B2 (en) | 2002-04-23 | 2005-09-06 | Medtronic, Inc. | Implantable medical device fast median filter |
GB2388276B (en) | 2002-05-04 | 2004-06-30 | Motorola Inc | A wireless communicaton system, a wireless communication device and method of monitoring therefor |
US20030212802A1 (en) | 2002-05-09 | 2003-11-13 | Gateway, Inc. | Proximity network encryption and setup |
US7346167B2 (en) | 2002-05-10 | 2008-03-18 | Harris Corporation | Secure mobile ad-hoc network and related methods |
US7203183B2 (en) | 2002-06-26 | 2007-04-10 | International Business Machines Corporation | Access point initiated forced roaming based upon bandwidth |
US7444152B2 (en) | 2002-06-28 | 2008-10-28 | Nokia Corporation | Signaling and routing protocols for an integrated cellular and relaying system |
US20040203787A1 (en) | 2002-06-28 | 2004-10-14 | Siamak Naghian | System and method for reverse handover in mobile mesh Ad-Hoc networks |
DE60210177T2 (en) | 2002-08-14 | 2006-12-28 | Sony Deutschland Gmbh | Bandwidth-oriented reconfiguration of ad hoc wireless networks |
US7440573B2 (en) | 2002-10-08 | 2008-10-21 | Broadcom Corporation | Enterprise wireless local area network switching system |
US7006481B2 (en) | 2002-10-10 | 2006-02-28 | Interdigital Technology Corporation | System and method for integrating WLAN and 3G |
JP3779673B2 (en) | 2002-10-30 | 2006-05-31 | 株式会社東芝 | Relay device and communication system |
EP1563641A1 (en) | 2002-11-06 | 2005-08-17 | Koninklijke Philips Electronics N.V. | Mobile ad-hoc internet sharing |
CN1711796A (en) | 2002-11-20 | 2005-12-21 | 国际商业机器公司 | Managing network resources for wireless communication |
FI114126B (en) | 2002-12-31 | 2004-08-13 | Vioteq Oy | Wireless LAN Management |
US7797434B2 (en) | 2002-12-31 | 2010-09-14 | International Business Machines Corporation | Method and system for user-determind attribute storage in a federated environment |
US7552234B2 (en) * | 2003-02-11 | 2009-06-23 | Cisco Technology, Inc. | Arrangement for establishing a bidirectional tunnel between a mobile router and a correspondent node |
GB0303471D0 (en) | 2003-02-14 | 2003-03-19 | Toshiba Res Europ Ltd | Improved communication network for indoor environment |
JP3925425B2 (en) | 2003-02-18 | 2007-06-06 | Kddi株式会社 | Wireless multi-hop network configuration method |
JP4098645B2 (en) | 2003-02-28 | 2008-06-11 | 株式会社リコー | Wireless LAN system and wireless LAN communication method |
US7512783B2 (en) | 2003-03-14 | 2009-03-31 | Naghian Siamaek | Provision of security services for an ad-hoc network |
US7349338B2 (en) | 2003-04-15 | 2008-03-25 | Lucent Technologies Inc | Scheduler and method for scheduling transmissions in a communication network |
US7313363B2 (en) | 2003-05-08 | 2007-12-25 | M/A-Com, Inc. | Activation method for wireless communication system |
US20040235452A1 (en) | 2003-05-22 | 2004-11-25 | Fischer Michael Andrew | Network access point for providing multiple levels of security |
US7212514B2 (en) | 2003-05-29 | 2007-05-01 | Matsushita Electric Industrial Co., Ltd. | Mobile communication device containable in ad hoc network |
US7577108B2 (en) | 2003-06-03 | 2009-08-18 | Palo Alto Research Center Incorporated | Learning-based strategies for message-initiated constraint-based routing |
US7406313B2 (en) | 2003-06-25 | 2008-07-29 | International Business Machines Corporation | Systems, methods and computer program products for connecting ad hoc piconets to wide area networks |
KR100547133B1 (en) | 2003-07-11 | 2006-01-26 | 삼성전자주식회사 | Apparatus and method for constructing ad-hoc network of heterogeneous terminals |
JP2005341290A (en) | 2004-05-27 | 2005-12-08 | Keio Gijuku | Communications system, and radio communications device |
EP1665640A1 (en) | 2003-09-09 | 2006-06-07 | Roamad Holdings Limited | Wireless networking system and method |
US6888808B2 (en) | 2003-09-15 | 2005-05-03 | Cisco Technology, Inc. | System and method for providing transparency in delivering private network features |
US20050058109A1 (en) | 2003-09-16 | 2005-03-17 | Jan-Erik Ekberg | Mechanism for improving connection control in peer-to-peer ad-hoc networks |
JP4578917B2 (en) | 2003-10-03 | 2010-11-10 | 富士通株式会社 | Apparatus, method and medium for self-organizing multi-hop radio access network |
JP2005123781A (en) | 2003-10-15 | 2005-05-12 | Sony Corp | Radio communication system, radio communication apparatus and method, radio communication managing apparatus and method, and computer program |
US7212810B2 (en) | 2003-10-17 | 2007-05-01 | Qualcomm Incorporated | System selection for wireless data services |
GB2408173A (en) | 2003-11-13 | 2005-05-18 | Toshiba Res Europ Ltd | Use of communication terminal as a repeater. |
US20050108527A1 (en) | 2003-11-13 | 2005-05-19 | Boris Ginzburg | Method and apparatus to provide secured link |
US7757076B2 (en) | 2003-12-08 | 2010-07-13 | Palo Alto Research Center Incorporated | Method and apparatus for using a secure credential infrastructure to access vehicle components |
JP2005176021A (en) | 2003-12-12 | 2005-06-30 | Toshiba Corp | Information processor and program |
US7340014B2 (en) | 2003-12-31 | 2008-03-04 | Intel Corporation | Apparatus and method of multi-user detection |
JP2005204213A (en) | 2004-01-19 | 2005-07-28 | Toshiba Corp | Call arrival control method for mobile communication terminal, mobile communication terminal, and call arrival control system for same |
TWI249316B (en) * | 2004-02-10 | 2006-02-11 | Ind Tech Res Inst | SIM-based authentication method for supporting inter-AP fast handover |
CA2457909A1 (en) | 2004-02-16 | 2005-08-16 | Christopher Davies | Method and system for self-organizing reliable, multiple path data flow transmission of data on a network |
US20050207416A1 (en) | 2004-03-16 | 2005-09-22 | Samsung Electronics Co. , Ltd. | Apparatus and method for deploying efficient broadcast multicast services in a wireless network |
JP2005295310A (en) | 2004-04-01 | 2005-10-20 | Fuji Electric Holdings Co Ltd | Radio communication method, radio communication system, radio terminal, program and recording medium |
US8139520B2 (en) * | 2004-05-03 | 2012-03-20 | Nokia Corporation | Method of preventing or limiting the number of simultaneous sessions in wireless local area network (WLAN) |
WO2005109693A1 (en) | 2004-05-07 | 2005-11-17 | Samsung Electronics Co., Ltd. | System and method for handover capable of minimizing service delay in broadband wireless access communication system |
KR100612496B1 (en) | 2004-05-11 | 2006-08-14 | 삼성전자주식회사 | Method for service discovery in Mobile Ad-hoc Network |
WO2005116841A1 (en) | 2004-05-26 | 2005-12-08 | Matsushita Electric Industrial Co., Ltd. | Network system and method for providing an ad-hoc access environment |
US7881267B2 (en) | 2004-06-04 | 2011-02-01 | Hewlett-Packard Development Company, L.P. | Portable computing device for wireless communications and method of operation |
JP2006013811A (en) | 2004-06-24 | 2006-01-12 | Matsushita Electric Ind Co Ltd | Information terminal |
JP4645939B2 (en) | 2004-07-22 | 2011-03-09 | 日本電気株式会社 | Mobile base station position determination system, terminal position determination system, mobile base station, radio terminal and base station position determination program |
CN1819536B (en) | 2004-07-28 | 2011-01-26 | 美国博通公司 | Method and apparatus of mobile handoff through multi-network simulcasting |
JP2006050224A (en) | 2004-08-04 | 2006-02-16 | Canon Inc | Wireless communication system |
EP1631000A1 (en) | 2004-08-31 | 2006-03-01 | Matsushita Electric Industrial Co., Ltd. | Deterministic feedback control for multicast or broadcast services |
JP2006074621A (en) | 2004-09-03 | 2006-03-16 | Oki Electric Ind Co Ltd | Communication system, communication terminal for relay, communication method, and communication program |
JP4460399B2 (en) | 2004-09-07 | 2010-05-12 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication system and mobile communication terminal |
US7853204B2 (en) | 2004-10-21 | 2010-12-14 | Panasonic Corporation | Method and system for identifying a relay mobile station in a wireless communication network |
CN101084572A (en) | 2004-10-21 | 2007-12-05 | 卓越自动系统有限公司 | Singulating and de-tapping arrays of semiconductor packages |
CN1225942C (en) | 2004-11-04 | 2005-11-02 | 西安西电捷通无线网络通信有限公司 | Method of improving mobile terminal handover switching performance in radio IP system |
US7933247B2 (en) | 2004-11-18 | 2011-04-26 | Sanjay M. Gidwani | Real-time scalable wireless switching network |
JP2006163793A (en) | 2004-12-07 | 2006-06-22 | Fuji Xerox Co Ltd | Radio communication system |
US7346341B2 (en) | 2004-12-10 | 2008-03-18 | Nokia Corporation | Providing mobile-specific services for mobile devices via ad-hoc networks |
KR100703726B1 (en) | 2004-12-11 | 2007-04-05 | 삼성전자주식회사 | Method for managing neighbor node and determining routing path in mobile ad hoc network, and network apparatus thereof |
US7532907B2 (en) | 2004-12-22 | 2009-05-12 | Sony Ericsson Mobile Communication Ab | Method of providing multiple data paths using a mobile terminal and related devices |
US20060143026A1 (en) | 2004-12-23 | 2006-06-29 | Srinivasan Jagannathan | Network usage analysis system using cost structure and revenue and method |
EP1677462A1 (en) | 2004-12-28 | 2006-07-05 | Eidgenössische Technische Hochschule Zürich | Service discovery in ad hoc networks |
JP4527553B2 (en) | 2005-01-17 | 2010-08-18 | Necインフロンティア株式会社 | Mobile communication terminal and user authentication method |
EP1701486A1 (en) | 2005-03-07 | 2006-09-13 | BRITISH TELECOMMUNICATIONS public limited company | Route selection in multi-hop cellular network |
JP4630706B2 (en) | 2005-03-31 | 2011-02-09 | 富士通株式会社 | Service device, client device connection destination switching control method and program by service device |
US7433324B2 (en) | 2005-04-01 | 2008-10-07 | Microsoft Corporation | User experience for collaborative ad-hoc networks |
US7515909B2 (en) | 2005-04-21 | 2009-04-07 | Qualcomm Incorporated | Wireless handoffs between multiple networks |
JP2006304005A (en) | 2005-04-21 | 2006-11-02 | Mitsubishi Electric Corp | Wireless lan internet telephone |
US20060248337A1 (en) | 2005-04-29 | 2006-11-02 | Nokia Corporation | Establishment of a secure communication |
JP4356647B2 (en) | 2005-05-09 | 2009-11-04 | ソニー株式会社 | Wireless communication system, access point management apparatus, access point management method, wireless communication apparatus, wireless communication method, and computer program |
KR100690762B1 (en) | 2005-05-10 | 2007-03-09 | 엘지전자 주식회사 | A telephone call method and system for using many number in mobile communication station |
WO2006124938A2 (en) | 2005-05-17 | 2006-11-23 | Rajant Corporation | System and method for communication in a wireless mobile ad-hoc network |
DE602005002259T2 (en) | 2005-06-30 | 2008-05-21 | Ntt Docomo Inc. | Apparatus and method for improved handoff in mesh networks |
TWI393414B (en) | 2005-07-06 | 2013-04-11 | Nokia Corp | Secure session keys context |
US8126477B2 (en) | 2005-07-07 | 2012-02-28 | Qualcomm Incorporated | Methods and devices for interworking of wireless wide area networks and wireless local area networks or wireless personal area networks |
JP2007036828A (en) | 2005-07-28 | 2007-02-08 | Oki Electric Ind Co Ltd | Communication control system and communication control method |
US7903628B2 (en) | 2005-08-22 | 2011-03-08 | Qualcomm Incorporated | Configurable pilots in a wireless communication system |
CN1921418A (en) | 2005-08-23 | 2007-02-28 | 华为技术有限公司 | Method and device for checking independency of wireless local area network switch-in |
EP1761082B1 (en) | 2005-09-02 | 2018-06-13 | Nokia Solutions and Networks GmbH & Co. KG | Method and system to connect a second communication network having a connection node to a first communication network having a contact node |
JP2007074177A (en) | 2005-09-06 | 2007-03-22 | Hitachi Ltd | Mobile ad hoc network system |
JP4652934B2 (en) | 2005-09-07 | 2011-03-16 | 株式会社日立製作所 | Access point, communication system, and connection switching method |
CN1953406B (en) | 2005-10-19 | 2011-06-01 | 株式会社Ntt都科摩 | A method to access hybrid network and gateway equipment, wireless terminal and communication system |
GB2433677A (en) | 2005-10-31 | 2007-06-27 | Israel Aircraft Ind Ltd | Medium access control (MAC) method and system for dynamic time slot allocation and QoS priority access in a mobile ad hoc network (MANET) |
AU2006309464B2 (en) * | 2005-10-31 | 2009-10-29 | Lg Electronics Inc. | Method for processing control information in a wireless mobile communication system |
JP4830451B2 (en) | 2005-11-02 | 2011-12-07 | 日本電気株式会社 | Wireless line control system, centralized control apparatus, wireless line control method used therefor, and program thereof |
JP2007143066A (en) | 2005-11-22 | 2007-06-07 | Canon Inc | Imaging apparatus and key managing method |
EP1958345B1 (en) | 2005-11-29 | 2018-05-23 | Telefonaktiebolaget LM Ericsson (publ) | Scheduling in a wireless multi-hop relay network |
US20070174429A1 (en) | 2006-01-24 | 2007-07-26 | Citrix Systems, Inc. | Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment |
US7831027B2 (en) | 2006-01-25 | 2010-11-09 | Accenture Global Services Limited | Configurable charging system for a telecommunications service provider |
US20070201388A1 (en) | 2006-01-31 | 2007-08-30 | Qualcomm Incorporated | Methods and systems for resizing multimedia content based on quality and rate information |
WO2007091699A2 (en) | 2006-02-06 | 2007-08-16 | Matsushita Electric Industrial Co., Ltd. | Method, system and apparatus for indirect access by communication device |
JP4504934B2 (en) | 2006-02-28 | 2010-07-14 | 矢崎総業株式会社 | Vehicle display device |
US7903817B2 (en) * | 2006-03-02 | 2011-03-08 | Cisco Technology, Inc. | System and method for wireless network profile provisioning |
US20070217433A1 (en) | 2006-03-14 | 2007-09-20 | Nokia Corporation | Apparatus, method and computer program product providing relay division multiple access |
WO2007149140A2 (en) | 2006-03-30 | 2007-12-27 | Antlabs | System and method for providing transactional security for an end-user device |
US7817986B2 (en) | 2006-04-28 | 2010-10-19 | Motorola, Inc. | Method and system for providing cellular assisted secure communications of a plurality of ad hoc devices |
US20070254614A1 (en) | 2006-05-01 | 2007-11-01 | Infosys Technologies Ltd. | Secure wireless connections using ssid fields |
US7593378B1 (en) | 2006-06-15 | 2009-09-22 | Redpine Signals, Inc. | SINR-based powerdown apparatus and method for a wireless communications systems |
KR100713626B1 (en) | 2006-06-19 | 2007-05-02 | 삼성전자주식회사 | Motile communication terminal for providing ad-hoc network service and method for managing ad-hoc network using the same |
JP4899696B2 (en) | 2006-07-31 | 2012-03-21 | 富士通株式会社 | Communication device, relay device, communication system, communication method, and communication program |
US8295225B2 (en) | 2006-09-08 | 2012-10-23 | Qualcomm Incorporated | Reverse link feedback for interference control in a wireless communication system |
US7929460B2 (en) | 2006-09-14 | 2011-04-19 | Vanu, Inc. | Communication network topology determination |
US20080081623A1 (en) | 2006-09-29 | 2008-04-03 | Motorola, Inc. | Priority handoff based on battery charge level |
US20080081606A1 (en) | 2006-09-29 | 2008-04-03 | Cole Terry L | Connection manager with branded connection notification |
US20080095114A1 (en) | 2006-10-21 | 2008-04-24 | Toshiba America Research, Inc. | Key Caching, QoS and Multicast Extensions to Media-Independent Pre-Authentication |
US7924793B2 (en) | 2006-11-20 | 2011-04-12 | At&T Intellectual Property I, L.P. | Methods and apparatus to manage bandwidth in a wireless network |
US8204034B2 (en) | 2007-01-10 | 2012-06-19 | Motorola Solutions, Inc. | Method and device for transmitting data packets |
US10419360B2 (en) | 2007-05-31 | 2019-09-17 | International Business Machines Corporation | Market-driven variable price offerings for bandwidth-sharing ad hoc networks |
US20090047930A1 (en) | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile service provider |
US9392445B2 (en) | 2007-08-17 | 2016-07-12 | Qualcomm Incorporated | Handoff at an ad-hoc mobile service provider |
US20090049158A1 (en) | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider topology |
US20090073943A1 (en) | 2007-08-17 | 2009-03-19 | Qualcomm Incorporated | Heterogeneous wireless ad hoc network |
US9398453B2 (en) | 2007-08-17 | 2016-07-19 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
PT2236000E (en) | 2008-01-22 | 2015-12-04 | Savox Comm Oy Ab Ltd | An arrangement and method for connecting an ad-hoc communication network to a permanent communication network via a half-duplex communication link |
WO2010000870A1 (en) | 2008-07-04 | 2010-01-07 | Telespazio S.P.A. | Identification and analysis of persistent scatterers in series of sar images |
US8270975B2 (en) | 2009-01-05 | 2012-09-18 | Intel Corporation | Method of managing network traffic within a wireless network |
US9179367B2 (en) | 2009-05-26 | 2015-11-03 | Qualcomm Incorporated | Maximizing service provider utility in a heterogeneous wireless ad-hoc network |
-
2008
- 2008-08-08 US US12/188,990 patent/US9392445B2/en not_active Expired - Fee Related
- 2008-08-08 US US12/188,985 patent/US20090047964A1/en not_active Abandoned
- 2008-08-13 JP JP2010521931A patent/JP2010537567A/en active Pending
- 2008-08-13 WO PCT/US2008/073017 patent/WO2009026071A2/en active Application Filing
- 2008-08-13 KR KR1020107005901A patent/KR20100054834A/en not_active Application Discontinuation
- 2008-08-13 BR BRPI0814262-9A2A patent/BRPI0814262A2/en not_active IP Right Cessation
- 2008-08-13 CA CA2694684A patent/CA2694684A1/en not_active Abandoned
- 2008-08-13 CN CN200880102831A patent/CN101785335A/en active Pending
- 2008-08-13 EP EP08827777A patent/EP2179607A2/en not_active Withdrawn
- 2008-08-13 RU RU2010109886/08A patent/RU2010109886A/en not_active Application Discontinuation
- 2008-08-13 MX MX2010001896A patent/MX2010001896A/en not_active Application Discontinuation
- 2008-08-13 AU AU2008289251A patent/AU2008289251A1/en not_active Abandoned
- 2008-08-14 CA CA2695328A patent/CA2695328A1/en not_active Abandoned
- 2008-08-14 JP JP2010521942A patent/JP2010537571A/en active Pending
- 2008-08-14 MX MX2010001894A patent/MX2010001894A/en not_active Application Discontinuation
- 2008-08-14 KR KR1020107005911A patent/KR20100054835A/en not_active Application Discontinuation
- 2008-08-14 WO PCT/US2008/073218 patent/WO2009026109A1/en active Application Filing
- 2008-08-14 BR BRPI0815218 patent/BRPI0815218A2/en not_active IP Right Cessation
- 2008-08-14 AU AU2008289212A patent/AU2008289212A1/en not_active Abandoned
- 2008-08-14 CN CN200880102950A patent/CN101779480A/en active Pending
- 2008-08-14 EP EP08827684A patent/EP2179608A1/en not_active Withdrawn
- 2008-08-14 RU RU2010109899/07A patent/RU2010109899A/en not_active Application Discontinuation
- 2008-08-15 TW TW097131375A patent/TW200915895A/en unknown
- 2008-08-15 TW TW097131326A patent/TW200917871A/en unknown
Patent Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5301359A (en) * | 1989-04-27 | 1994-04-05 | Motorola, Inc. | Bulletin board resource for communication system access |
US20090125429A1 (en) * | 1997-08-13 | 2009-05-14 | Matsushita Electric Industrial Co., Ltd. | Mobile electronic commerce system |
US20020061750A1 (en) * | 1998-05-14 | 2002-05-23 | Behzad Mohebbi | Soft hand-off in cellular mobile communications networks |
US6295453B1 (en) * | 1998-10-07 | 2001-09-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Multi-full rate channel assignment for a cellular telephone system |
US7089417B2 (en) * | 1998-10-16 | 2006-08-08 | Tecsec, Inc. | Cryptographic information and flow control |
US20010024443A1 (en) * | 1999-12-20 | 2001-09-27 | Fredrik Alriksson | Mobile IP for mobile Ad Hoc networks |
US6871071B2 (en) * | 1999-12-28 | 2005-03-22 | Ntt Docomo, Inc. | Handover control method and system |
US20010012757A1 (en) * | 2000-02-03 | 2001-08-09 | U.S. Philips Corporation | Ad-hoc radio communication system |
US7170878B2 (en) * | 2000-03-07 | 2007-01-30 | Sony Corporation | Communication device and communication method |
US20100202428A1 (en) * | 2000-04-18 | 2010-08-12 | Cisco Technology, Inc. | System and Method for Concurrently Utilizing Multiple System Identifiers |
US20030095504A1 (en) * | 2000-09-12 | 2003-05-22 | Ogier Richard G. | Reduced-overhead protocol for discovering new neighbor nodes and detecting the loss of existing neighbor nodes in a network |
US20020039367A1 (en) * | 2000-09-29 | 2002-04-04 | Jukka Seppala | Selection of serving network element in telecommunications network |
US20040029528A1 (en) * | 2000-11-28 | 2004-02-12 | Chandler Stephen Anthony Gerard | Routing algorithm for distributed telecommunication networks |
US20020080738A1 (en) * | 2000-12-22 | 2002-06-27 | Kim Kyung-Sik | Hard handoff method for packet mobile network |
US20040008663A1 (en) * | 2000-12-29 | 2004-01-15 | Devabhaktuni Srikrishna | Selection of routing paths based upon path quality of a wireless mesh network |
US7551576B2 (en) * | 2001-02-06 | 2009-06-23 | Nokia Corporation | Access system for an access network |
US20030103521A1 (en) * | 2001-06-18 | 2003-06-05 | Itran Communications Ltd. | Channel access method for powerline carrier based media access control protocol |
US20050088980A1 (en) * | 2001-06-27 | 2005-04-28 | Mikko Olkkonen | Ad hoc network discovery menu |
US20030054796A1 (en) * | 2001-09-17 | 2003-03-20 | Hitachi, Ltd. | Charging method and terminal equipment in the information and communication network system |
US7408929B2 (en) * | 2001-09-28 | 2008-08-05 | Kabushiki Kaisha Toshiba | Radio communication system, terminal and packet |
US20030157951A1 (en) * | 2002-02-20 | 2003-08-21 | Hasty William V. | System and method for routing 802.11 data traffic across channels to increase ad-hoc network capacity |
US7161914B2 (en) * | 2002-04-11 | 2007-01-09 | Ntt Docomo, Inc. | Context aware application level triggering mechanism for pre-authentication, service adaptation, pre-caching and handover in a heterogeneous network environment |
US20040202120A1 (en) * | 2002-04-17 | 2004-10-14 | Hanson Norman L. | Internet protocol collaborative mobility |
US20030198346A1 (en) * | 2002-04-18 | 2003-10-23 | Yoshinobu Meifu | Push delivery service providing method, information providing service system, server system, and user station |
US20030203741A1 (en) * | 2002-04-26 | 2003-10-30 | Kabushiki Kaisha Toshiba | Autonomous distributed wireless network system, method of autonomous distributed wireless network communication and wireless terminal apparatus |
US20030202476A1 (en) * | 2002-04-29 | 2003-10-30 | Harris Corporation | Determining quality of service (QoS) routing for mobile AD HOC networks |
US7254119B2 (en) * | 2002-05-28 | 2007-08-07 | Zte San Diego, Inc. | Interworking mechanism between CDMA2000 and WLAN |
US7340253B2 (en) * | 2002-06-10 | 2008-03-04 | Lucent Technologies Inc. | IP-based distributed wireless access network architecture for CDMA networks |
US20050094588A1 (en) * | 2002-06-12 | 2005-05-05 | Globespan Virata Incorporated | Direct link relay in a wireless network |
US7649872B2 (en) * | 2002-06-24 | 2010-01-19 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
US7573904B2 (en) * | 2002-06-24 | 2009-08-11 | Nokia Corporation | Ad hoc networking of terminals aided by a cellular network |
US6879574B2 (en) * | 2002-06-24 | 2005-04-12 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
US20040001442A1 (en) * | 2002-06-28 | 2004-01-01 | Rayment Stephen G. | Integrated wireless distribution and mesh backhaul networks |
US6735417B2 (en) * | 2002-08-15 | 2004-05-11 | Motorola, Inc. | Method and apparatus for relaying information in an AD-HOC network |
US20060007863A1 (en) * | 2002-09-05 | 2006-01-12 | Siamak Naghian | Signal propagation delay routing |
US7519071B2 (en) * | 2002-09-20 | 2009-04-14 | Cisco Technology, Inc. | Arrangement in a gateway for registering mobile routers of a mobile AD HOC network to respective home agents |
US7420952B2 (en) * | 2002-10-28 | 2008-09-02 | Mesh Dynamics, Inc. | High performance wireless networks using distributed control |
US7003117B2 (en) * | 2003-02-05 | 2006-02-21 | Voltage Security, Inc. | Identity-based encryption system for secure data distribution |
US20040174822A1 (en) * | 2003-03-05 | 2004-09-09 | Bui Thomas T. | Systems and methods for providing collaboration between systems |
US7266374B2 (en) * | 2003-07-22 | 2007-09-04 | Samsung Electronics Co., Ltd. | Communication system and method in wireless infrastructure network environments |
US7394826B2 (en) * | 2003-09-09 | 2008-07-01 | Harris Corporation | Mobile ad hoc network (MANET) providing quality-of-service (QoS) based unicast and multicast features |
US20050053005A1 (en) * | 2003-09-09 | 2005-03-10 | Harris Corporation | Mobile ad hoc network (MANET) providing connectivity enhancement features and related methods |
US20060217062A1 (en) * | 2003-09-23 | 2006-09-28 | Saffre Fabrice T P | Decentralized channel selection in a self-organizing adhoc network |
US20070223408A1 (en) * | 2003-10-06 | 2007-09-27 | Broadbeam Corporation | Method and Apparatus for Intelligent Seamless Network Switching |
US20070110009A1 (en) * | 2003-11-12 | 2007-05-17 | Matsushita Electric Industrial Co., Ltd. | Contex transfer in a communication network comprising plural heterogeneous access networks |
US7496363B2 (en) * | 2003-12-17 | 2009-02-24 | Motorola, Inc. | Method of changing access point for a mobile node in a wireless access network |
US20050136834A1 (en) * | 2003-12-19 | 2005-06-23 | Motorola, Inc. | Communication system with adopted remote identity |
US20050138671A1 (en) * | 2003-12-22 | 2005-06-23 | Love Robert T. | Apparatus and method for adaptive broadcast transmission |
US20060114850A1 (en) * | 2004-01-13 | 2006-06-01 | Joshi Avinash | System and method for achieving continuous connectivity to an access point or gateway in a wireless network following an on-demand routing protocol, and to perform smooth handoff of mobile terminals between fixed terminals in the network |
US20050163078A1 (en) * | 2004-01-22 | 2005-07-28 | Toshiba America Research, Inc. | Mobility architecture using pre-authentication, pre-configuration and/or virtual soft-handoff |
US7486651B2 (en) * | 2004-03-02 | 2009-02-03 | Ntt Docomo, Inc. | Mobile node, an ad hoc network routing controlling method and an ad hoc network system |
US20050197098A1 (en) * | 2004-03-02 | 2005-09-08 | Nokia Corporation | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
US7362731B2 (en) * | 2004-03-23 | 2008-04-22 | Nokia Corporation | Selection of network access entity in a communication system |
US20050228853A1 (en) * | 2004-03-23 | 2005-10-13 | Shinya Yamamura | Method and system for supporting service provision |
US20070111705A1 (en) * | 2004-04-30 | 2007-05-17 | Wenlin Zhang | Method for implementing roaming charging and system thereof |
US20070149139A1 (en) * | 2004-06-10 | 2007-06-28 | Jean-Louis Gauvreau | Wireless Network System with Energy Management |
US20080069105A1 (en) * | 2004-06-24 | 2008-03-20 | Telecom Italia S.P.A. | Method and System for Controlling Access to Communication Networks, Related Network and Computer Program Therefor |
US20090172391A1 (en) * | 2004-06-30 | 2009-07-02 | Matsushita Electric Industrial Co., Ltd. | Communication handover method, communication message processing method, and communication control method |
US20060005008A1 (en) * | 2004-07-02 | 2006-01-05 | Wen-Hung Kao | Security gateway utilizing ssl protocol protection and related method |
US20060056368A1 (en) * | 2004-09-10 | 2006-03-16 | Nivis, Llc | System and method for a wireless mesh network of configurable signage |
US20060064589A1 (en) * | 2004-09-17 | 2006-03-23 | Fujitsu Limited | Setting information distribution apparatus, method, program, medium, and setting information reception program |
US20060101400A1 (en) * | 2004-10-14 | 2006-05-11 | International Business Machines Corporation | Apparatus and methods for performing computer system maintenance and notification activities in an opportunistic manner |
US20060092939A1 (en) * | 2004-10-29 | 2006-05-04 | Samsung Electronics Co., Ltd. | Apparatus and method for extending mobility in a mobile ad hoc network |
US7680079B2 (en) * | 2004-11-04 | 2010-03-16 | Samsung Electronics Co., Ltd. | Method of signaling QoS information at hand-over between access networks in an IP-based core network |
US8717931B2 (en) * | 2004-11-05 | 2014-05-06 | Toshiba America Research, Inc. | Network discovery mechanisms |
US20060098598A1 (en) * | 2004-11-10 | 2006-05-11 | Michael Gallagher | Seamless transitions of active calls between enterprise telecommunications networks and licensed public telecommunications networks |
US20060215576A1 (en) * | 2005-01-05 | 2006-09-28 | International Business Machines Corporation | Switching between two communicaiton modes in a WLAN |
US20060171403A1 (en) * | 2005-02-01 | 2006-08-03 | Samsung Electronics Co., Ltd. | Gateway for interconnecting ad-hoc network and infrastructure network, and methods for discovering and registering service provider using gateway |
US7363050B2 (en) * | 2005-02-01 | 2008-04-22 | Fujitsu Limited | Mobile station, base station, and wireless communication system |
US20060178149A1 (en) * | 2005-02-04 | 2006-08-10 | Kamat Sandip D | Systems and methods for wireless cellular telephone routers |
US20060176852A1 (en) * | 2005-02-04 | 2006-08-10 | Industrial Technology Research Institute | System and method for connection handover in a virtual private network |
US7266383B2 (en) * | 2005-02-14 | 2007-09-04 | Scenera Technologies, Llc | Group interaction modes for mobile devices |
US20060236105A1 (en) * | 2005-03-31 | 2006-10-19 | Jacco Brok | Authenticating a user of a communication device to a wireless network to which the user is not associated with |
US20060229080A1 (en) * | 2005-04-08 | 2006-10-12 | The Boeing Company | Net-centric coordination channel (NCC) |
US20060227724A1 (en) * | 2005-04-08 | 2006-10-12 | Pascal Thubert | Arrangement for providing optimized connections between peer routers in a tree-based ad hoc mobile network |
US20070008902A1 (en) * | 2005-07-11 | 2007-01-11 | Saritha Yaramada | Managing negotiations of quality of service parameters in wireless networks |
US20070016262A1 (en) * | 2005-07-13 | 2007-01-18 | Betastim, Ltd. | Gi and pancreatic device for treating obesity and diabetes |
US20070042769A1 (en) * | 2005-08-17 | 2007-02-22 | Freescale Semiconductor, Inc. | Communications security management |
US20070076875A1 (en) * | 2005-10-05 | 2007-04-05 | Canon Kabushiki Kaisha | Wireless communication system and authentication method and communication control method in wireless communication system |
US7339915B2 (en) * | 2005-10-11 | 2008-03-04 | Cisco Technology, Inc. | Virtual LAN override in a multiple BSSID mode of operation |
US20070206527A1 (en) * | 2006-03-01 | 2007-09-06 | Yuan-Chang Lo | Virtual access point for configuration of a LAN |
US20070220219A1 (en) * | 2006-03-16 | 2007-09-20 | International Business Machines Corporation | System and method for optimizing data in value-based storage system |
US7881474B2 (en) * | 2006-07-17 | 2011-02-01 | Nortel Networks Limited | System and method for secure wireless multi-hop network formation |
US20080040481A1 (en) * | 2006-08-11 | 2008-02-14 | Motorola, Inc. | Method and system for compensation in ad hoc networks |
US20080049689A1 (en) * | 2006-08-23 | 2008-02-28 | Motorola, Inc. | Tunneling data to multiple wireless networks from device without connectivity through employment of device with connectivity |
US20080080387A1 (en) * | 2006-10-02 | 2008-04-03 | Tropos Networks, Inc. | Probe response determination |
US20080089288A1 (en) * | 2006-10-12 | 2008-04-17 | Bellsouth Intellectual Property Corporation | Methods, systems, and computer program products for providing advertising and/or information services over mobile ad hoc cooperative networks using electronic billboards and related devices |
US20080095134A1 (en) * | 2006-10-23 | 2008-04-24 | Wai Chen | Roadside network unit and method of organizing, managing and maintaining local network using local peer groups as network groups |
US20080112355A1 (en) * | 2006-11-09 | 2008-05-15 | Avaya Technology Llc | Multi-Hop Ad-hoc Wireless Networks That Support Non-Multi-Hop Wireless Terminals |
US20080112362A1 (en) * | 2006-11-10 | 2008-05-15 | Motorola, Inc. | Ip layer-handoff using mobility domains and ip caching |
US20080139239A1 (en) * | 2006-12-11 | 2008-06-12 | O'connor Dennis M | Techniques to share multimedia and enable cellular phone conference calling using ad-hoc wireless networks |
US20080146232A1 (en) * | 2006-12-19 | 2008-06-19 | Douglas Norman Knisely | Neighbor list provision in a communication network |
US20080165735A1 (en) * | 2007-01-05 | 2008-07-10 | Jen-Jee Chen | Handoff method of mobile device utilizing dynamic tunnel |
US20080192666A1 (en) * | 2007-02-12 | 2008-08-14 | Motorola, Inc. | Method and system for dynamically utilizing a peer network to extend battery life |
US20090046598A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | System and method for acquiring or distributing information related to one or more alternate ad hoc service providers |
US20090046644A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Service set manager for ad hoc mobile service provider |
US20090047966A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile internet access service |
US20110039566A1 (en) * | 2007-08-27 | 2011-02-17 | Telefonaktiebolaget Lm Ericsson (Publ) | method and a network control node for bandwidth and access control in femto cells of a wireless system |
US20110183685A1 (en) * | 2010-01-20 | 2011-07-28 | Airpatrol Corporation | Multi-band radio frequency detection and location system |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8644206B2 (en) | 2007-08-17 | 2014-02-04 | Qualcomm Incorporated | Ad hoc service provider configuration for broadcasting service information |
US20090046676A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider configuration for broadcasting service information |
US20090047966A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile internet access service |
US20090046658A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Handoff at an ad-hoc mobile service provider |
US20090046598A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | System and method for acquiring or distributing information related to one or more alternate ad hoc service providers |
US20090046591A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
US20090073943A1 (en) * | 2007-08-17 | 2009-03-19 | Qualcomm Incorporated | Heterogeneous wireless ad hoc network |
US9398453B2 (en) | 2007-08-17 | 2016-07-19 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
US9392445B2 (en) | 2007-08-17 | 2016-07-12 | Qualcomm Incorporated | Handoff at an ad-hoc mobile service provider |
US9167426B2 (en) | 2007-08-17 | 2015-10-20 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
US20090049158A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider topology |
US20110302627A1 (en) * | 2009-02-18 | 2011-12-08 | Telefonaktiebolaget L M Ericsson (Publ) | User authenticaton |
US8875232B2 (en) * | 2009-02-18 | 2014-10-28 | Telefonaktiebolaget L M Ericsson (Publ) | User authentication |
US8422460B2 (en) | 2009-04-06 | 2013-04-16 | Robert Bosch Gmbh | Method for performing proactive wireless communication handoffs using a mobile client's route information |
US20100254346A1 (en) * | 2009-04-06 | 2010-10-07 | Robert Bosch Gmbh | Method for performing proactive wireless communication handoffs using a mobile client's route information |
US9179367B2 (en) | 2009-05-26 | 2015-11-03 | Qualcomm Incorporated | Maximizing service provider utility in a heterogeneous wireless ad-hoc network |
US20110019627A1 (en) * | 2009-05-26 | 2011-01-27 | Qualcomm Incorporated | Maximizing Service Provider Utility in a Heterogeneous Wireless Ad-Hoc Network |
US8458353B2 (en) | 2009-08-13 | 2013-06-04 | Qualcomm Incorporated | Method and apparatus for link aggregation in a heterogeneous communication system |
US20110040888A1 (en) * | 2009-08-13 | 2011-02-17 | Qualcomm Incorporated | Method and apparatus for link aggregation in a heterogeneous communication system |
US11871316B1 (en) * | 2011-04-02 | 2024-01-09 | Philips North America Llc | System and method for persisting mobile agents within a mobile region of interest |
US20130332725A1 (en) * | 2012-06-04 | 2013-12-12 | Sony Corporation | Information processing apparatus, information processing system, information processing method, and program |
US20140325043A1 (en) * | 2013-04-28 | 2014-10-30 | Huawei Technologies Co., Ltd. | Network Switching Method, Version Upgrade Method, and Terminal Device |
US9720678B2 (en) * | 2013-04-28 | 2017-08-01 | Huawei Technologies Co., Ltd. | Network switching method, version upgrade method, and terminal device |
Also Published As
Publication number | Publication date |
---|---|
TW200917871A (en) | 2009-04-16 |
JP2010537567A (en) | 2010-12-02 |
WO2009026071A3 (en) | 2009-04-09 |
EP2179607A2 (en) | 2010-04-28 |
CA2694684A1 (en) | 2009-02-26 |
BRPI0814262A2 (en) | 2015-02-03 |
MX2010001894A (en) | 2010-03-15 |
KR20100054835A (en) | 2010-05-25 |
EP2179608A1 (en) | 2010-04-28 |
BRPI0815218A2 (en) | 2015-03-31 |
US9392445B2 (en) | 2016-07-12 |
RU2010109886A (en) | 2011-09-27 |
AU2008289212A1 (en) | 2009-02-26 |
KR20100054834A (en) | 2010-05-25 |
CN101785335A (en) | 2010-07-21 |
US20090046658A1 (en) | 2009-02-19 |
JP2010537571A (en) | 2010-12-02 |
WO2009026071A2 (en) | 2009-02-26 |
CA2695328A1 (en) | 2009-02-26 |
MX2010001896A (en) | 2010-03-15 |
TW200915895A (en) | 2009-04-01 |
AU2008289251A1 (en) | 2009-02-26 |
RU2010109899A (en) | 2011-09-27 |
WO2009026109A1 (en) | 2009-02-26 |
CN101779480A (en) | 2010-07-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9392445B2 (en) | Handoff at an ad-hoc mobile service provider | |
US9398453B2 (en) | Ad hoc service provider's ability to provide service for a wireless network | |
US20090073943A1 (en) | Heterogeneous wireless ad hoc network | |
US20090047966A1 (en) | Method for a heterogeneous wireless ad hoc mobile internet access service | |
EP2026501A2 (en) | Method for a heterogeneous wireless ad hoc mobile service provider | |
EP2031919B1 (en) | Ad hoc service provider's ability to provide service for a wireless network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: QUALCOMM INCORPORATED, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KRISHNASWAMY, DILIP;REEL/FRAME:021627/0687 Effective date: 20080917 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |