HK1145755A - Ad hoc service provider topology - Google Patents

Description

Ad hoc service provider topology

Claiming priority based on 35 U.S.C. § 119

This patent application claims priority from provisional application No.60/956,658 entitled "METHOD FOR updating the environment WIRELESS AD HOC MOBILE SERVICE PROVIDER" filed on 8/17 of 2007 and provisional application No.60/980,575 entitled "AD HOC SERVICE PROVIDER TOPOLOGY" filed on 10/17 of 2007, both of which are assigned to the assignee of the present application and are hereby expressly incorporated herein by reference.

Technical Field

The present technology relates generally to telecommunications, and more specifically to ad hoc service provider topologies.

Background

Wireless telecommunication systems are widely deployed to provide various services such as voice, data, video, audio, messaging, broadcast, etc. to consumers. Today, wireless networks are providing broadband internet access to mobile users. Such networks are sometimes referred to as Wireless Wide Area Networks (WWANs). WWAN operators typically provide wireless access plans to their subscribers.

Accessing the WWAN from all mobile devices may not be feasible. Some mobile devices may not have a WWAN radio. Other mobile devices with WWAN radios may not have an active subscription plan. Ad hoc networks allow mobile devices to dynamically connect over a wireless interface using a protocol such as WLAN, bluetooth, UWB or other protocols. There is a need in the art for a method to allow a user of a mobile device without WWAN access to dynamically customize wireless access services provided by a user with a WWAN-enabled mobile device using wireless ad hoc network transmissions between mobile devices belonging to both the user and the user with a WWAN-enabled mobile device.

Disclosure of Invention

In one aspect of the present invention, a server includes: a processing system for registering a first ad hoc service provider and registering a second ad hoc service provider. The processing system is further configured to receive information associated with the second ad hoc service provider from the first ad hoc service provider. The information includes service information of the second ad hoc service provider.

In another aspect of the present invention, a server includes: means for registering a first ad hoc service provider; and means for registering the second ad hoc service provider. The server further comprises: means for receiving information from the first ad hoc service provider related to the second ad hoc service provider. The information includes service information of the second ad hoc service provider.

In another aspect of the invention, a method is provided for obtaining or publishing (distribute) information associated with one or more alternative ad hoc service providers. The method comprises the following steps: registering a first ad hoc service provider; and registering the second ad hoc service provider. The method further comprises the following steps: receiving information from the first ad hoc service provider related to the second ad hoc service provider. The information includes service information of the second ad hoc service provider.

In another aspect of the invention, a machine-readable medium includes instructions executable by a processing system in a server. The instructions include code for: registering the first ad hoc service provider and registering the second ad hoc service provider. The instructions also include code for: receiving information from the first ad hoc service provider related to the second ad hoc service provider. The information includes service information of the second ad hoc service provider.

It is to be understood that other configurations of the present technology will become readily apparent to those of ordinary skill in the art from the following detailed description, wherein various configurations of the present technology are shown and described by way of illustration. It is to be understood that the invention is capable of other and different configurations 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.

Drawings

Fig. 1 is a simplified block diagram illustrating an example of a telecommunications system.

Fig. 2 is a simplified block diagram showing an example of the hardware configuration of the server.

Fig. 3 is a simplified block diagram illustrating a functional example of an ad hoc service provider.

Fig. 4 is a simplified block diagram illustrating an example of a hardware configuration of an ad hoc service provider.

Fig. 5 is a simplified block diagram of an example of a telecommunications system with a cluster.

Fig. 6a is a flow diagram illustrating exemplary operations for obtaining ad hoc service provider topology information.

Fig. 6b is a flowchart illustrating exemplary operations for obtaining or publishing ad hoc service provider topology information.

Fig. 7 is a flow diagram illustrating another exemplary operation for obtaining or publishing ad hoc service provider topology information.

FIG. 8 is a simplified block diagram illustrating an example of a system.

Fig. 9 is a simplified block diagram illustrating a functional example of a server.

Fig. 10 is a simplified block diagram illustrating a functional example of a server.

FIG. 11 is a simplified block diagram illustrating a functional example of a server.

Fig. 12 is a simplified block diagram illustrating a functional example of an ad hoc service provider.

Fig. 13 is a simplified block diagram illustrating a functional example of a module for receiving information from a first ad hoc service provider related to a second ad hoc service provider.

Fig. 14 is a simplified block diagram illustrating a functional example of an ad hoc service provider.

Fig. 15 is a simplified block diagram illustrating a functional example of an ad hoc service provider.

Fig. 16 is a simplified block diagram illustrating a functional example of an ad hoc service provider.

Fig. 17 is a simplified block diagram illustrating a functional example of a module for receiving information related to a second ad hoc service provider.

Detailed Description

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. It will be apparent, however, to one 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. The illustrated telecommunications system 100 has multiple WWANs 104 that provide broadband access to a network 102 for mobile users. Network 102 may be a packet-based network, such as the Internet or an intranet. For clarity of presentation, two WWANs 104 are shown with backhaul connections to network 102. However, the number of WWANs providing broadband access to network 102 is not limited to two WWANs. Each WWAN104 may be implemented with a plurality of fixed-site base stations (not shown) dispersed throughout a geographic area. The geographic region may generally be divided into smaller regions (known as cells). Each base station may be used to serve all mobile users in its respective cell. A base station controller (not shown) may be used to manage and coordinate the base stations in the WWAN104 and support the backhaul connection to the network 102.

Each WWAN104 may support radio communication with mobile users using one of many different radio access protocols. For example, one WWAN104 may support evolution data optimized (EV-DO) while another WWAN104 may support Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the third generation partnership project 2(3GPP2) as part of the CDMA2000 family of standards and employ multiple access techniques, such as Code Division Multiple Access (CDMA), to provide broadband internet access to mobile users. Alternatively, one of the WWANs 104 may support Long Term Evolution (LTE), which is an item in 3GPP2 to improve the Universal Mobile Telecommunications System (UMTS) mobile phone standard, which is primarily based on a wideband CDMA (W-CDMA) air interface. One of the WWANs 104 may also support the WiMAX standard developed by the WiMAX forum. The actual wireless access protocol employed by the WWAN for any particular telecommunications system will depend on the particular application and the overall design constraints imposed on the system. The various techniques presented in this specification are equally applicable to any combination of heterogeneous or homogeneous WWANs, regardless of the wireless access protocol used.

Each WWAN104 has multiple mobile subscribers. Each user may have a mobile node that is able to directly access network 102 through WWAN 104. For example, in the telecommunication system shown in FIG. 1, the mobile nodes use EV-DO, UMB, or LTE radio access protocols to access the WWAN 104; however, in actual implementations, these mobile nodes may be configured to support any wireless access protocol.

In the system of fig. 1, one or more of these mobile nodes 106 may be used to create an ad hoc network in its vicinity based on the same or a different wireless access protocol than that used to access the WWAN 104. For example, a mobile node may support a UMB wireless access protocol for a WWAN while providing an IEEE 802.11 access point to other mobile nodes that are not capable of directly accessing the WWAN. IEEE 802.11 specifies a set of Wireless Local Area Network (WLAN) standards developed by the IEEE 802.11 committee for short-range communications (e.g., tens of meters to hundreds of meters). Although IEEE 802.11 is a general WLAN radio access protocol, other suitable protocols may be used.

A mobile node that may be used to provide an access point to another mobile node is referred to herein as an "ad hoc service provider" (provider) and is represented in fig. 1 as ad hoc service provider 106. A mobile node that may use an access point of an ad hoc service provider 106 is referred to herein as a "mobile client" and is represented in fig. 1 as a mobile client 108. The mobile node, whether an ad hoc service provider 106 or a mobile client 108, may be a laptop computer, a mobile phone, a Personal Digital Assistant (PDA), a mobile digital audio player, a mobile gaming console, a digital camera, a digital video camera, a mobile audio device, a mobile video device, a mobile multimedia device, any of the aforementioned components (e.g., printed circuit boards, integrated circuits, and/or circuit components), or any other device capable of supporting at least one wireless access protocol.

Ad hoc service provider 106 may extend its wireless broadband network access services to mobile clients 108 that do not have access to network 102. Server 110 may act as a "switch" to enable mobile client 108 to purchase unused bandwidth from ad hoc service provider 106 to access network 102, e.g., via WWAN 104.

The ad hoc service provider 106, the server 110, and the one or more mobile clients 108 may establish a network as an ad hoc heterogeneous wireless network. For example, the heterogeneous wireless networks may include at least two wireless networks (e.g., WWAN and WLAN). For example, an ad hoc network may be a network whose specific configuration may change over time or from the formation of one network to the formation of the next. The network configuration is not pre-planned before the network is established. Configuration instances of an ad hoc network may include configurations related to which members are in the network (e.g., which ad hoc service provider, which server, and/or which mobile client is to be included in the network), configurations related to the geographic locations of the ad hoc service provider and the mobile client, and configurations related to when and how often the network is to be established.

For purposes of illustration only, an exemplary scenario of an ad hoc network is described below. Case 1: when a mobile user is at an airport at 8 am on tuesday, he may turn on his mobile node (e.g., a laptop or mobile phone) while he is waiting for his flight, use it as an ad hoc service provider, and establish an ad hoc network for 30 minutes. An ad hoc network may include one or more mobile clients (e.g., other laptops or mobile phones) in the vicinity. Case 2: at 5 pm on wednesday, when a mobile user is in a hotel, he may use the same mobile node as an ad hoc service provider to form another ad hoc network for 4 hours, providing his services to the same mobile client, a different mobile client, or a combination of both. Case 3: at 5 pm on wednesday, at an airport the day before the first ad hoc service provider, different ad hoc service providers may form an ad hoc network. Since service providers and clients are mobile, ad hoc networks may be "mobile" networks.

Fig. 2 is a simplified block diagram showing an example of the hardware configuration of the server. The server 110 may be a centralized server or a distributed server. The centralized server may be a dedicated server, or may be integrated into another entity (e.g., a desktop or laptop computer or host). A distributed server may be distributed among multiple servers and/or one or more other entities (e.g., laptop or desktop computers or hosts). In at least one configuration, server 110 may be integrated, in whole or in part, into one or more ad hoc service providers. The server may be a communication device, a system including a communication device, or any of the aforementioned components (e.g., printed circuit boards, integrated circuits, and/or circuit components).

The server 110 is shown with a network interface 202. The network interface 202 may be used to implement the physical layer with respect to the network 102 (shown in fig. 1). In addition, the network interface 202 may also be used to implement the data link layer by managing the transfer of data across the physical layer.

The server 110 is also shown with a processing system 204. The processing system 204 may be implemented in a dedicated server, or integrated into another entity, or distributed among multiple entities using software, hardware, or a combination of both. For example, the processing system 204 may be implemented by one or more processors. A processor may be a general purpose microprocessor, a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity that can perform calculations or other processing of information. The processing system 204 may also include one or more machine-readable media for storing software. Software should be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable code format).

The machine-readable medium may include memory integrated into a processor, such as may be the case with an ASIC. The machine-readable medium may also include memory external to the processor, such as Random Access Memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable PROM (eprom), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device. Further, a machine-readable medium may include a transmission line or a carrier wave that encodes a data signal. Those of ordinary skill in the art will recognize how best to implement the functionality described for the processing system 204. According to an aspect of the invention, a machine-readable medium is a computer-readable medium encoded or stored with instructions, and is a computing element that defines structural and functional associations between instructions and other portions of a system, which allow the instruction functions to be implemented. The instructions may be executed, for example, by a mobile node or server or by a processing system of a mobile node or server. The instructions may be, for example, a computer program comprising code.

The processing system 204 may be used to implement various functions of the server 110. The functionality of the processing system 204 for one configuration of the server 110 will now be presented with reference to FIG. 1. One of ordinary skill in the art will readily appreciate that other configurations of the server 110 may include processing systems having the same or different functionality.

Turning to fig. 1, a processing system in server 110 provides: means for authenticating the ad hoc service provider 106 to provide a mobile client 108 with a wireless access point to a network; means for authenticating the mobile client 108 to use the service provided by the ad hoc service provider 106; and means for establishing a tunnel between the server 110 and each mobile client 108 through the ad hoc service provider 106. A tunnel between a server 110 and one mobile client 108 is shown in fig. 1.

In one configuration of the telecommunications system 100, the server 110 charges the mobile client 108 based on usage. This is an attractive option for temporary users of mobile internet services compared to monthly flat-rate radio access plans. A processing system in server 110 may provide a module for determining a charge for mobile client 108 to access the network through ad hoc service provider 106.

Revenue derived from usage fees may be distributed to various entities in the telecommunications system 100 in a manner that tends to maintain a persistent exchange. For example, a portion of the revenue may be distributed to ad hoc service providers, thereby providing financial incentives to mobile users who become ad hoc providers. Another portion of the revenue may be allocated to the WWAN operators to compensate them for the bandwidth becoming unused. Another portion of the revenue may be distributed to the manufacturer of the mobile node. The remainder of the revenue may be kept by the server operator providing the exchange. The server 110 may provide a module for determining how to allocate revenue generated from the mobile clients 108 to various entities in the telecommunications system 100.

The server 110 may be implemented as a trusted server. Thus, authentication may be performed using Public Key Infrastructure (PKI) certificates in Transport Layer Security (TLS) sessions between the server 110 and the ad hoc service provider 106, or between the server 110 and the mobile client 108. Alternatively, the server 110 may verify using a self-signed certificate or by some other suitable means.

The processing system in server 110 may also provide a module for enrolling ad hoc service providers. A secure session channel may be established between the server 110 and the ad hoc service provider 106, or between the server 110 and the mobile client 108, during enrollment. In one configuration of the telecommunications system 100, the mobile client 108 may register with the server 110 to provide a username and password for payment information. The ad hoc service provider 106 may register with the server 110 to inform the mobile client 108 of its desire to provide a wireless access point, such as an internet access point.

The processing system 204 in the server 110 may also be used to provide admission (admission) control. Admission control is the process by which the processing system determines whether to enable the ad hoc service provider 106 to provide wireless access points in a geographic coverage area. If it is determined that additional ad hoc service providers 106 will adversely affect performance in the WWAN, the processing system may limit the number of ad hoc service providers 106 in any given coverage area. Additional restrictions may be imposed by WWAN operators whose mobile users are not expected to provide service in a given geographic coverage area, subject to various network restrictions.

In one configuration of the processing system, when the ad hoc service provider 106 is mobile and desires to provide services, authentication, authorization, and accounting (AAA) and secure session establishment operations for connections with the server 110 initiated by the ad hoc service provider 106 may be performed using extensible authentication protocol-tunneling layer security (EAP-TTLS). EAP-TTLS may also be used for session initiation requests of the mobile client 108. In the latter case, the mobile client is the requestor, the ad hoc service provider 106 is the authenticator, and the server 110 is the authentication server. The ad hoc service provider 106 sends the mobile client's credentials to the processing system in the server 110 for EAP-AAA authentication. The EAP-TTLS authentication response from the processing system is then used to generate the master shared key. A link encryption key may then be established between the ad hoc service provider 106 and the mobile client 108.

The processing system in the server 110 may also provide a module for establishing a connection with the mobile client 108 for encrypted data that cannot be decrypted by the ad hoc service provider 106. This may be accomplished through a secure socket layer virtual private network (SSL VPN) tunnel between the mobile client 108 and the server 110. The SSL VPN tunnel is used to encrypt traffic routed through the ad hoc service provider 106 to provide enhanced privacy to the mobile client 108. Alternatively, the tunnel may be an IPsec tunnel, or may be implemented using some other suitable tunneling protocol.

Once a tunnel is established between the server 110 and the mobile client 108, various services may be provided. For example, the processing system may support audio or video services for the mobile client 108. The processing system may also support broadcast services for the mobile client 108. Other functions of the processing system include providing routing content to and from the network to the mobile client 108, and providing network address translation to and from the network to the mobile client 108.

The processing system in the server 110 may also provide modules for supporting handoff of the mobile client 108 from one ad hoc service provider 106 to another ad hoc service provider based on any number of factors. These factors may include, for example, the quality of service (QoS) required by each mobile client 108, the length of the session required by each mobile client 108, and the load, link conditions, and energy levels (e.g., battery life) at the ad hoc service provider 106. The handoff may be a soft handoff in which the processing system maintains the tunnel in a persistent state during the handoff.

The server 110 may also be used to store quality metrics for each ad hoc service provider 106. This quality metric may be provided to mobile clients 108 desiring to select from available ad hoc service providers 106. This metric may be continually updated as more information becomes available about a particular ad hoc service provider 106. The quality metrics associated with each ad hoc service provider 106 may be decreased or increased based on the QoS provided.

Briefly, the server 110 is operable to receive the necessary operating parameters of the ad hoc network under its control. The server 110 may configure and make available operational parameters for existing communication entities and other communication entities that have not joined the ad hoc network to cause the latter to join the ad hoc network. The communication entities may be a service provider 106 and a mobile client 108. Wherein the operational parameters may include the number of ad hoc networks under the control of the server 110; the number of clients 108 in each ad hoc network; the relative and absolute locations of the client 108 and the ad hoc network; security and/or encryption parameters required to join the ad hoc network; the identity, performance and load of each ad hoc network; as well as information relating to each service provider 106 such as available bandwidth, processing power, remaining battery life, available usage time, service charges, etc. The operating parameters may be dynamically updated by the server 110 and made available to communication entities, such as the provider 106 and the client 108, immediately as needed.

Fig. 3 is a simplified block diagram illustrating a functional example of the ad hoc service provider 106. Ad hoc service providers 106 have the ability to bridge wireless links through homogeneous or heterogeneous wireless access protocols. This may be accomplished through a WWAN network interface 302 (which supports a wireless access protocol for WWAN104 to network 102) and a WLAN network interface 304 (which provides a wireless access point for mobile clients 108). For example, the WWAN network interface 302 may include transceiver functionality to support EV-DO for network access (e.g., internet access) through a WWAN, and the WLAN network interface 304 may include transceiver functionality to provide an 802.11 wireless access point to the mobile client 108. Each network interface 302, 304 may be used to implement the physical layer by demodulating wireless signals and performing other Radio Frequency (RF) front-end processing. Each network interface 302, 304 may also be used to implement the data link layer by managing the transfer of data across the physical layer.

The ad hoc service provider 106 is shown with a filtered interconnection and session monitoring module 306. The module 306 provides filtering processing of content from the mobile clients 108 to provide only mobile clients 108 authenticated and licensed by the server with the interconnection between the ad hoc wireless link to WWAN network interface 302 to use the WWAN network. The module 306 also maintains a tunnel connection between the server 110 and the authenticated mobile client 108.

Ad hoc service provider 106 also includes a service provider application unit (application)308 that (1) enables module 306 to provide ad hoc services to mobile client 108; and (2) support WWAN or internet access for mobile users or subscribers of the ad hoc service provider 106. The latter functionality is supported by a service provider user interface 312, which service provider user interface 312 communicates with the WWAN network interface 302 through module 306 under the control of service provider application unit 308. The user interface 312 may include any other combination of a keypad, display, speaker, microphone, joystick, and/or user interface device that enables a mobile user or user to access the WWAN104 or network 102 (shown in fig. 1). The mobile user may also use the user interface 312 to provide input to, or browse output from, a processing system of an ad hoc service provider.

As described above, the service provider application unit 308 also enables the module 306 to provide ad hoc services to the mobile client 108. The service provider application unit 308 maintains a session with the server 110 to exchange customized messages with the server 110. In addition, the service provider application unit 308 also maintains a separate session with each mobile client 108 for exchanging customized messages between the service provider application unit 308 and the mobile client 108. The service provider application unit 308 provides information related to the authenticated and licensed client to the filtered interconnection and session monitoring module 306. The filtered interconnection and session monitoring module 308 only allows content flow for authenticated and licensed mobile clients 108. The filtered interconnection and session monitoring module 306 also optionally monitors information related to content flows involving the mobile client 108, such as the amount of content output from the mobile client 108 and input to the mobile client 108; and information related to WWAN and WLAN network resource utilization and available bandwidth on the wireless channel. The filtered interconnection and session monitoring module 306 may additionally and/or alternatively provide such information to the service provider application unit 308. The service provider application unit 308 may additionally and/or alternatively operate on such information and take appropriate action, such as determining whether to continue to maintain a connection with the mobile client 108 and with the server 110, or whether to continue to provide service. It should be noted that the functionality described in connection with modules 306 and 308 may be implemented in any given platform in one or more sets of modules that coordinate to provide such functionality at the ad hoc service provider 106.

When the ad hoc service provider 106 decides to provide an ad hoc service, the service provider application unit 308 sends a request to the server 110 for approval. The service provider application unit 308 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 ad hoc service provider 106 and then determine whether to grant the ad hoc service provider's request. As previously described, the request may be denied if the number of ad hoc service providers in the same geographic location is too large, or if the WWAN operator has imposed certain restrictions on the ad hoc service providers 106.

Once the ad hoc service provider 106 is authenticated, the service provider application unit 308 may broadcast an ad hoc WLAN Service Set Identifier (SSID). The associated mobile client 108 may be associated with an SSID to access the ad hoc service provider 106. The service provider application unit 308 may then authenticate the mobile client 108 with the server 110 and then configure the filtered interconnection and session monitoring module 306 to connect the mobile client 108 to the server. During authentication of the mobile client 108, the service provider application unit 308 may use an unsecured wireless link.

Once the mobile client 108 is authenticated, the service provider application unit 308 may additionally and/or alternatively choose to move the mobile client 108 to a new SSID over a secure link. In this case, the service provider application unit 308 may allocate the time spent in each SSID according to a load that must not be supported for an existing session with the mobile client 108.

The service provider application unit 308 is also able to determine whether the mobile client 108 is supported before allowing it to access the network. The resource intelligence for estimating the consumption of battery power and other resources required to accept a mobile client 108 may help determine whether the service provider application unit 308 should consider supporting a new mobile client 108 or accepting a handoff of the mobile client 108 from another ad hoc service provider 106.

The service provider application unit 308 may accept the mobile clients 108 and provide them with some QoS guarantee, such as an expected average bandwidth during the session. The average throughput provided to each mobile client 108 over a time window may be monitored. The service provider application unit 308 may monitor the throughput of all flows therethrough to ensure that the resource utilization of the mobile client 108 is below a certain threshold, and to ensure that the agreed QoS requirements are met for provision to the mobile client 108 during establishment of the session.

The service provider application unit 308 may also provide a level of security to the wireless access point by routing the content through the filtered interconnect and the session monitoring module 306 in the event that the content cannot be decrypted. Similarly, the service provider application unit 308 may be used to ensure that content routed between the user interface 312 and the WWAN104 via the module 306 cannot be decrypted by the mobile client 108. The service provider application unit 308 may use any suitable encryption technique to implement this functionality.

The service provider application unit 308 may also maintain a period of time for the mobile client 108 to access the network. The time period may be agreed upon between the service provider application unit 308 and the mobile client 108 during session initiation. If the service provider application unit 308 determines that it cannot provide access to the network to the mobile client 108 during the agreed-upon period of time, it may notify the server 110 and the mobile client 108 of information regarding its unavailability. This may occur due to energy limitations (e.g., low battery) or other unforeseen events. The server 110 may then consider handing off the mobile client 108 to another ad hoc service provider 106 if such an ad hoc service provider exists in the vicinity of the mobile client 108. The service provider application unit 308 may support handoff of the mobile client 108.

The service provider application unit 308 may also dedicate processing resources to maintaining wireless links or restricted sessions with mobile clients 108 served by other ad hoc service providers 106. This may facilitate handoff of the mobile client 108 to the ad hoc service provider 106.

The service provider application unit 308 may generally manage the mobile client 108, and in particular the session, through the user interface 312. Alternatively, the service provider application unit 308 may support a seamless mode of operation through processing resources dedicated to serving the mobile client 108. In this way, the mobile client 108 is managed in a manner that is transparent to the mobile users of the ad hoc service provider. A seamless mode of operation is desirable when the service provider does not desire to manage the mobile client 108, but wants to continually generate revenue by sharing bandwidth with the mobile client 108.

Turning now to the mobile client in fig. 1, the mobile client 108 may register with the server 110 using a TLS session. Once registered, the mobile client 108 searches for available ad hoc service providers 106. When the mobile client 108 detects the presence of one or more ad hoc service providers 106, it may initiate a session with the ad hoc service provider 106 using EAP-TTLS based on attributes and parameters, such as available bandwidth supported by the ad hoc service provider 106, QoS metrics of the ad hoc service provider 106, and broadcasted service costs. As previously described, a link encryption key may be established between the mobile client 108 and the ad hoc service provider 106 during session establishment. An SSL VPN session may be established between the mobile client 108 and the server 110, encrypting all traffic between the two. The transport layer port may remain open and not be encrypted to provide visibility into network address translation functionality at the ad hoc service provider 106.

Due to any number of factors, a handoff of the mobile client 108 from one ad hoc service offering to another may occur. In one configuration, the mobile client 108 may maintain restricted sessions with multiple ad hoc service providers 106 while using one ad hoc service provider 106 to access the internet. As previously described, this approach may facilitate the handover procedure. In an alternative configuration, the mobile client 108 may only consider handover when necessary. In this configuration, the mobile client 108 may maintain a valid list of ad hoc service providers 106 in its vicinity for handoff. The mobile client 108 may select one ad hoc service provider 106 from the active list to handoff when the current ad hoc service provider 106 needs to interrupt its service. When handoff is not possible, the mobile client 108 needs to reconnect through a different ad hoc service provider 106 to access the internet. The persistence of the tunnel between the mobile client and the server (fig. 1) may enable the mobile client to implement a soft handoff from one service provider to another service provider.

If the bandwidth requirements of the mobile client 108 are greater than the capabilities of the available ad hoc service providers 106, the mobile client 108 may access multiple ad hoc service providers 106 simultaneously. A mobile client 108 with multiple transceivers may use a different transceiver for each ad hoc service provider 106 to potentially access multiple ad hoc service providers 106 simultaneously. Different channels may be used if the same wireless access protocol may be used to access multiple ad hoc service providers 106. If the mobile client 108 has only one transceiver available, it allocates the time it takes to access each ad hoc service provider 106.

Fig. 4 is a simplified block diagram illustrating an example of a hardware configuration of an ad hoc service provider. The ad hoc service provider 106 is shown having a WLAN transceiver 402, a WWAN transceiver 404, and a processing system 406. For example, the analog portion of the physical layer for the WLAN network interface 304 (shown in fig. 3) may be implemented using the WLAN transceiver 402, and the analog portion of the physical layer for the WWAN network interface 302 (shown in fig. 3) may be implemented using the WWAN transceiver 404.

The processing system 406 may be implemented using software, hardware, or a combination of both. For example, the processing system 406 may be implemented by one or more processors. A processor may be a general purpose microprocessor, a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity that can perform calculations or other processing of information. The processing system 406 may also include one or more machine-readable media for storing software. Software should be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable code format).

The machine-readable medium may include memory integrated into a processor, such as may be the case with an ASIC. The machine-readable medium may also include memory external to the processor, such as Random Access Memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable PROM (eprom), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device. Further, a machine-readable medium may include a transmission line or a carrier wave that encodes a data signal. Those of ordinary skill in the art will recognize how best to implement the functionality described for the processing system 406. According to an aspect of the invention, a machine-readable medium is a computer-readable medium encoded or stored with instructions, and is a computing element that defines structural and functional associations between instructions and other portions of a system, which allow the instruction functions to be implemented. The instructions may be executed, for example, by a mobile node or server or by a processing system of a mobile node or server. The instructions may be, for example, a computer program comprising code.

The processing system 406 may be used to implement the physical layer and link layer digital processing portions for the WLAN and WWAN network interfaces 304 and 302 (shown in fig. 3). The filtered interconnection and session monitoring module 306 and the service provider application unit 308 may also be implemented using a processing system 406.

The functionality of the processing system 406 for one configuration of the ad hoc service provider 106 will be presented in more detail later. One of ordinary skill in the art will readily appreciate that other configurations of the ad hoc service provider 106 may include processing systems having the same or different functionality.

Fig. 5 is a simplified block diagram of an example of a telecommunications system with a cluster (cluster). When ad hoc clusters are formed and at least one mobile node of each cluster has the capability to connect to multiple wireless networks, the mobile node may serve as a routing node for the wireless networks. Exemplary telecommunications system 500 may include: server 110, WWAN104, and one or more ad hoc networks, such as ad hoc clusters 510, 520, and 530. Although 3 clusters are shown for purposes of illustration, the system may include any number of clusters, and each cluster may include at least one ad hoc service provider 106 and any number of mobile clients 108 that the cluster may support. Some mobile nodes may be included in more than one cluster. For example, the ad hoc service provider 106 in each cluster may support multiple wireless networks (e.g., WWAN and WLAN) and may serve as a routing node for one network to another (e.g., WLAN to WWAN).

In one configuration of system 500, processing system 204 of server 110 (shown in FIG. 2) may provide: means for registering the first ad hoc service provider 106; and means for registering the second ad hoc service provider 106. The processing system 204 may also provide: means for receiving information from the first ad hoc service provider 106 related to the second ad hoc service provider 106. The information includes service information of the second ad hoc service provider 106.

The processing systems 406 (shown in FIG. 4) of the ad hoc service provider 106 in the cluster 510, 520, or 530 may provide: means for receiving information related to the second ad hoc service provider 106. The information includes service information of the second ad hoc service provider 106. The processing system 406 of the ad hoc service provider 106 may further include: means for supporting the transfer of information to the server 110; and means for supporting an access point to a network (e.g., WWAN 104) for the mobile client 108.

The processing system 406 of the ad hoc service provider 106 may also provide: means for supporting an access point by bridging a first wireless link with a mobile client 108 to a second wireless link with a network. The first wireless link may use a first wireless access protocol and the second wireless link may use a second wireless access protocol different from the first wireless access protocol. Alternatively, the first radio access protocol may be the same as the second radio access protocol. The processing system 406 may be coupled to a first wireless transceiver (e.g., the WLAN transceiver 402 in fig. 4) to support a first wireless link using a first wireless access protocol; and to a second wireless transceiver (e.g., WWAN transceiver 404 in fig. 4) to support a second wireless link using a second wireless access protocol. The processing system 406 may also be coupled to the user interface 312 shown in fig. 3, and may provide modules for enabling a user to access a network through the user interface 312.

For a system 500 with clusters, it is desirable to have information relating to the characteristics of the clusters (sometimes referred to herein as "cluster information"), including, for example, the formation of the clusters, the lifetime of the clusters (lifetime), the cluster pattern of the ad hoc service provider 106, the number of clusters in the system, the number of mobile clients served in each cluster, the geographic location of the clusters, and the geographic location of the members of the clusters (e.g., ad hoc service provider 106 and mobile client 108), as well as a choice to choose from the organization service providers. The processing system 204 of the server 110 may include any or all of the cluster information. Information with the location of alternative ad hoc service providers near the cluster may provide an opportunity to offload one or more mobile clients 108 to the new ad hoc service provider 106, (i) to obtain the best bandwidth allocated for each mobile client 108 in the system; (ii) to quickly adapt to changing conditions, such as loss of ad hoc service providers in a cluster; or (iii) extend services for a mobile client by utilizing a new ad hoc service provider that joins the network after the mobile client (e.g., if the current ad hoc service provider for the mobile client is unable to provide services to the mobile client for the duration of the mobile client request).

Referring to fig. 3, 4 and 5, each ad hoc service provider 106 may issue beacon information (e.g., beacon frames) including an identifier (e.g., SSID) and service information indicating that the mobile node is an ad hoc service provider for the server 110. Other ad hoc service providers having processing systems suitably configured with software (e.g., appropriate service provider applications 308 and filtered interconnections and session monitoring module 306), hardware, or a combination thereof, may receive and store this beacon information, including service information, and upload it to the processing system 204 of the server 110. The mobile client 108, having a processing system suitably configured with software (e.g., suitable drivers or code), hardware, or a combination thereof, may also receive and store this information, including service information, and upload it to the processing system 204 of the server 110, either directly or through an ad hoc service provider. The processing system 204 may extract information uploaded from the ad hoc service provider 106 and from the mobile client 108 and form an aggregate graph of the cluster information. This may be used to define a cluster of mobile nodes. If any reporting member of the cluster (e.g., the ad hoc service provider 106 or the mobile client 108) has a location determining unit 504, such as a Global Positioning System (GPS) unit, this may be used to specify the geographic location of the cluster.

The beacon information, including the ad hoc service provider's 106 service information, allows the mobile client 108 to distinguish between ad hoc service providers that are registered with the server 110 and other nodes that are not registered with the server but simply provide wireless access points. Nodes that are not registered with the server 110 and therefore do not have the appropriate software to communicate with the server 110 may participate in the service. A mobile node (e.g., any ad hoc service provider or mobile client) that is registered with the server 110 and therefore has appropriate software to communicate with the server may store and upload service information (e.g., valuable location and neighbor information) to the processing system 204 of the server 110.

The processing system 204 of the server 110 may then track the cluster information. Processing system 204 may track, for example, whether the same ad hoc service provider tends to form members of the same cluster and randomness in the system. Information from nearby ad hoc service providers may be published to the mobile client 108 of the system 500. If these mobile clients are not within range of a neighboring ad hoc service provider, but are aware that one of the ad hoc service providers is or has recently been in the vicinity, these mobile clients may be willing to change locations to receive services from the neighboring ad hoc service provider. The information of neighboring ad hoc service providers may also be used to switch to ad hoc service providers when one ad hoc service provider gives notice that it will terminate its service.

Each ad hoc service provider 106 and each mobile client 108 may monitor beacon information from other ad hoc service providers and notify the processing system 204 of the server 110 of the presence of an ad hoc service provider in the vicinity. The beacon information may include service information of other ad hoc service providers. The service information may include one or more of the following information for the associated ad hoc service provider: channel information (e.g., channel numbers supported by the ad hoc service provider), communication capacity (e.g., dynamic information related to available capacity and used capacity at the ad hoc service provider), duration of service provided by the ad hoc service provider, geographic location of the ad hoc service provider, price of service provided by the ad hoc service provider, quality metrics of the ad hoc service provider, and quality of service provided by the ad hoc service provider. Pricing information may provide dynamic pricing capability based on demand. For example, if there are too many mobile clients compared to the number of ad hoc service providers available, the price may increase. On the other hand, if there are a larger number of available mobile service providers than mobile clients, the price may be reduced.

Referring to fig. 2, 5 and 6a, exemplary operations for obtaining ad hoc service provider topology information are shown from the perspective of a server. At step 602, the processing system 204 of the server 110 may register the first ad hoc service provider 106. The processing system 204 may also register the second ad hoc service provider 106 at step 604. Many other ad hoc service providers 106 may also register with the processing system 204. The mobile client 108 may also register with the processing system 204.

At step 606, the processing system 204 may receive information related to the second ad hoc service provider 106 from the first ad hoc service provider 106. The information may include service information of the second ad hoc service provider 106. The information may be sent out by the second ad hoc service provider 106. The ad hoc service provider 106 may transmit the service information by broadcasting its beacon information including the information. The processing system 204 may also receive information related to other ad hoc service providers from the plurality of ad hoc service providers 106 and/or the mobile client 108. Each such information may also include service information related to its respective ad hoc service provider.

In accordance with an aspect of the present invention, the server 110 may wirelessly receive information from a first ad hoc service provider 106, wherein the first ad hoc service provider 106 may wirelessly receive information from a second ad hoc service provider 106. In another aspect, the server 110 may wirelessly receive information from the first ad hoc service provider 106 after the mobile client 108 of the first ad hoc service provider 106 wirelessly receives information from the second ad hoc service provider 106 and transmits information to the first ad hoc service provider 106. The processing system 204 of the server 110 may support receiving information by, for example, controlling or communicating with a transceiver or receiver of the server 110.

The service information of the second ad hoc service provider 106 may include one or more of the following information related to the second ad hoc service provider 106: channel information of the second ad hoc service provider 106, communication capacity of the second ad hoc service provider 106, duration of service provided by the second ad hoc service provider 106, location of the second ad hoc service provider 106, price of service provided by the second ad hoc service provider 106, quality metric of the second ad hoc service provider 106, and quality of service provided by the second ad hoc service provider 106.

Referring now to fig. 2, 5 and 6b, server 110 may perform additional functions, such as those described below. At step 609, the processing system 204 of the server 110 may generate cluster information relating to the first and second ad hoc service providers and any other ad hoc service providers the processing system receives information from or is involved with. At step 611, processing system 204 may track the cluster information.

The cluster information may include one or more of the following: formation of clusters, age of clusters, pattern of clusters, number of mobile clients in each cluster, information related to alternate ad hoc service providers, geographic location of clusters, and geographic location of members of clusters.

The processing system 204 of the server 110 may then generate second information related to the second ad hoc service provider 106. The second information may be based on information previously received by processing system 204 from the first ad hoc service provider (see, e.g., step 606 in fig. 6 a). The second information may be the same as or different from the original information.

The second information may include one or more of the following information related to the second ad hoc service provider 106: channel information of the second ad hoc service provider 106, communication capacity of the second ad hoc service provider 106, duration of service provided by the second ad hoc service provider 106, location of the second ad hoc service provider 106, price of service provided by the second ad hoc service provider 106, quality metric of the second ad hoc service provider 106, and quality of service provided by the second ad hoc service provider 106.

At step 613, the server 110 may send the second information to the mobile client 108, where the mobile client 108 has accessed the server 110 through a wireless access point provided by the ad hoc service provider 106. The processing system 204 of the server 110 may support the transmission of the second information by, for example, controlling or communicating with a transceiver or transmitter of the server 110. When the second information is sent to the mobile client 108, it enables the mobile client 108 to locate a second ad hoc service provider 106 whose beacon signal cannot be detected by the mobile client 108 but which second ad hoc service provider 106 is physically adjacent to the mobile client 108. The server 110 may send the second information to a plurality of mobile clients in physical proximity to the second ad hoc service provider 106 through one or more ad hoc service providers.

At step 616, the processing system 204 of the server 110 may support a handoff of the mobile client 108 from one ad hoc service provider 106 to a second ad hoc service provider 106 based at least on information associated with the second ad hoc service provider 106.

Referring to fig. 4, 5 and 7, exemplary operations for acquiring and publishing network topology information are shown from the perspective of an ad hoc service provider. The dashed box comprising steps 702, 706, 710 and 712 is an optional step. At step 702, the processing system 406 of the ad hoc service provider 106 may request to register the ad hoc service provider 106 with the server 110. The second ad hoc service provider 106 may be registered with the server 110 and the mobile client 108 may also be registered with the server 110. Many other mobile nodes (e.g., ad hoc service providers and mobile clients) may also be registered with the server 110.

After registering the mobile node with the server 110, the mobile node may obtain software for performing the various functions described herein. Such software may be downloaded from server 110, obtained on a disk such as a CD-ROM or DVD, or obtained in any other suitable manner. The software may be loaded onto a processing system of the ad hoc service provider 106 or the mobile client 108. The software of the ad hoc service provider 106 may be different from the software of the mobile client 108. Hardware or a combination of hardware and software may also be used in place of software. The processing system of the ad hoc service provider 106 and the mobile client 108 may be implemented in hardware or a combination of hardware and software.

At step 704, the processing system 406 of the ad hoc service provider 106 may receive information related to the second ad hoc service provider 106. The ad hoc service provider 106 may be used to support an access point to a network for a mobile client 108. The second ad hoc service provider 106 may also be used to support an access point to the network for the second mobile client 108. The information includes service information of the second ad hoc service provider 106. This information may be sent out by the second ad hoc service provider 106. The information may include beacon information of the second ad hoc service provider 106. The ad hoc service provider 106 may receive information by monitoring beacon information broadcast by a second ad hoc service provider 106. The processing system 406 supports monitoring the beacon information by, for example, controlling or communicating with a transceiver or receiver of the ad hoc service provider 106. The processing system 406 may also receive information related to other ad hoc service providers 106 from the other ad hoc service providers 106, or one or more of its mobile clients 108. Each such information may also include service information associated with its respective ad hoc service provider.

The ad hoc service provider 106 wirelessly receives information from the second ad hoc service provider 106 or after the mobile client 108 wirelessly receives information from the second ad hoc service provider 106, the ad hoc service provider 106 wirelessly receives information from the mobile client 108. The processing system 406 of the ad hoc service provider 106 may support the receiving of information by, for example, controlling or communicating with a transceiver or receiver of the ad hoc service provider 106.

The service information may include service attributes for access to the network provided by the second ad hoc service provider 106. The service information may include one or more of the following: channel information of the second ad hoc service provider 106, communication capacity of the second ad hoc service provider 106, duration of service provided by the second ad hoc service provider 106, location of the second ad hoc service provider 106, price of service provided by the second ad hoc service provider 106, quality metric of the second ad hoc service provider 106, and quality of service provided by the second ad hoc service provider 106.

The processing system 406 of the ad hoc service provider 106 may store the information at step 706. The ad hoc service provider 106 may then send the information to the server 110 at step 708. The processing system 406 may support the transmission of information by, for example, controlling or communicating with a transceiver or transmitter of the ad hoc service provider 106.

At step 710, the processing system 406 of the ad hoc service provider 106 may receive the second information, the third information, or both the second and third information from the server 110. The second information is based on information related to the second ad hoc service provider 106 and the third information comprises information related to the third ad hoc service provider 106. The second information may be the same as or different from the original information. At step 712, the ad hoc service provider 106 may send the second information, the third information, or both the second and third information to the mobile client 108. The processing system 406 supports the transmission by, for example, controlling or communicating with a transceiver or transmitter of the ad hoc service provider 106.

The second information may include an identifier of the second ad hoc service provider 106, and may also include one or more of the following service information: channel information of the second ad hoc service provider 106, communication capacity of the second ad hoc service provider 106, duration of service provided by the second ad hoc service provider 106, location of the second ad hoc service provider 106, price of service provided by the second ad hoc service provider 106, quality metric of the second ad hoc service provider 106, and quality of service provided by the second ad hoc service provider 106. The third information may include similar information for the third ad hoc service provider 106.

The communication capacity of the second ad hoc service provider 106 may include dynamic information related to the available capacity and the used capacity at the second ad hoc service provider 106. The price of the service provided by the second ad hoc service provider 106 may include dynamic pricing based on demand. The communication capacity of the third ad hoc service provider 106 may include dynamic information related to the available capacity and the used capacity at the third ad hoc service provider 106. The price of the service provided by the third ad hoc service provider 106 may include dynamic pricing based on demand.

FIG. 8 is a simplified block diagram illustrating an example of a system. The system 801 may be a server 110 or an ad hoc service provider 106. The system 801 includes a processing system 802, which may be the processing system 204 of the server 110 or the processing system 406 of the ad hoc service provider 106. The processing system 802 can communicate with a receiver 806 and a transmitter 808 via a bus 804 or other structure or device. It should be understood that other means of communication besides a bus may be used in the disclosed configuration. The processing system 802 can generate audio, video, multimedia, and/or other types of data to provide to the transmitter 808 for communication. In addition, audio, video, multimedia, and/or other types of data can be received at receiver 806 and processed by processing system 802.

The processing system 802 may include a general-purpose processor or a special-purpose processor for executing instructions, and may also include volatile or non-volatile memory for storing data and instructions of a software program. Instructions stored in machine-readable media 810 and/or 818 may be executed by processing system 802 to control and manage access to the various networks, as well as to provide other communication and processing functions. The instructions may also include instructions that are executed by the processing system 802 for the various user interface devices, such as the display 812 and keypad 814. The machine-readable media (e.g., 810 and 818) may be in one or more of the various forms previously described in detail in this disclosure, with particular reference to fig. 2 and 4 (e.g., memory, hard disk, CD-ROM, DVD, or any other suitable storage device). The machine-readable medium may be one or more machine-readable media. Interface 816 may be any type of interface and may reside between any of the components shown in fig. 8. The interface 816 may be, for example, the network interface 202 shown in fig. 2. Transceiver frame 807 may represent one or more transceivers, and each transceiver may include a receiver 806 and a transmitter 808. Transceiver frame 807 may represent, for example, WWAN transceiver 404 and WLAN transceiver 402 as shown in fig. 4. The functions implemented in the processing system 802 may be implemented in a portion of the receiver 806, a portion of the transmitter 808, a portion of the machine-readable medium 810, a portion of the display 812, a portion of the keypad 814, or a portion of the interface 816, or vice versa.

Fig. 9 is a simplified block diagram illustrating a functional example of a server. The module 990 of the server 110 is configured with or includes: a module 910 for registering a first ad hoc service provider; module 920 is configured to register a second ad hoc service provider. Module 990 may also be configured with or include: a module 930 for receiving information from a first ad hoc service provider related to a second ad hoc service provider. The information includes service information of the second ad hoc service provider.

It should be noted that module 990 may be, for example, a processing system (e.g., 204 of fig. 2 or 802 of fig. 8), a machine-readable medium (e.g., 810 or 818 of fig. 8), or a combination of both. In one example, each of modules 910, 920, and 930 may represent a portion of a processing system or a machine-readable medium configured with or storing instructions for its respective functions. For example, module 910 in a machine-readable medium may be instructions in the machine-readable medium for registering a first ad hoc service provider. For module 930, it may be, for example, part of a processing system (e.g., 204 of fig. 2 or 802 of fig. 8), network interface 202 of fig. 2, receiver 806 of fig. 8, or some combination thereof.

Fig. 10 is a simplified block diagram illustrating a functional example of a server. The module 990 of the server 110 may be configured with or may include: a module 1010 for registering a first plurality of ad hoc service providers; a module 1020 for registering a second plurality of ad hoc service providers; a module 1030 for receiving a plurality of information from a first plurality of ad hoc service providers relating to a second plurality of ad hoc service providers. The plurality of pieces of information may be issued by a second plurality of ad hoc service providers, and the plurality of pieces of information may include a plurality of pieces of service information of the second plurality of ad hoc service providers.

Module 990 may also be configured with or may also include: module 1040 is configured to generate cluster information relating to a first ad hoc service provider, a second ad hoc service provider, a first plurality of ad hoc service providers, and a second plurality of ad hoc service providers. Each cluster may include at least one ad hoc service provider and at least one mobile client. In one example, each of modules 1010, 1020, 1030, and 1040 may represent a portion of a processing system or a machine-readable medium configured with or storing instructions for their respective functions. For module 1030, it may be, for example, part of a processing system (e.g., 204 of fig. 2 or 802 of fig. 8), part of network interface 202 of fig. 2, part of receiver 806 of fig. 8, or some combination thereof.

FIG. 11 is a simplified block diagram illustrating a functional example of a server. The module 990 of the server 110 may be configured with or may include: a module 1110 for tracking cluster information. The cluster information may include one or more of the following: formation of clusters, age of clusters, pattern of clusters, number of mobile clients in each cluster, information related to alternate ad hoc service providers, geographic location of clusters, and geographic location of members of clusters.

Module 990 may also be configured with or may also include: a module 1120 for supporting transmission of the second information to a mobile client, wherein the mobile client has accessed the server through a wireless access point provided by an ad hoc service provider. The second information is based on information received by the server relating to a second ad hoc service provider. The transmission of the second information to the mobile client may enable the mobile client to locate a second ad hoc service provider whose beacon signal cannot be detected by the mobile client but which is physically adjacent to the mobile client.

Module 990 may also be configured with or may also include: a module 1130 for supporting handoff of the mobile client from one ad hoc service provider to a second ad hoc service provider based at least on the information. In one example, each of modules 1110, 1120, and 1130 may represent a portion of a processing system or a machine-readable medium configured with or storing instructions for its respective functions.

Fig. 12 is a simplified block diagram illustrating a functional example of an ad hoc service provider. The modules 1290 of the first ad hoc service provider 106 may be configured with or may include: a module 1210 for providing a wireless access point to a network for a mobile client; a module 1220 for supporting a wireless access point by bridging a first wireless link with a mobile client to a second wireless link with a network. The first wireless link may use a first wireless access protocol. The second wireless link may use a second wireless access protocol different from the first wireless access protocol. The information may be issued by a second ad hoc service provider.

It is noted that module 1290 can be, for example, a processing system (e.g., 406 of FIG. 4 or 802 of FIG. 8), a machine-readable medium (e.g., 810 or 818 of FIG. 8), or a combination of both. Each of modules 1210 and 1220 may represent a portion of a processing system or a machine-readable medium configured with or storing instructions for its respective functions.

Fig. 13 is a simplified block diagram illustrating a functional example of a module for receiving information from a first ad hoc service provider related to a second ad hoc service provider. In this example, module 930 of fig. 9 may be configured with or may include: a module 1310 for supporting wireless reception of information from a first ad hoc service provider after a mobile client receives the information from a second ad hoc service provider and sends the information to the first ad hoc service provider. Module 1310 may represent a portion of a processing system or a machine-readable medium configured with or storing instructions for its respective functions.

Fig. 14 is a simplified block diagram illustrating a functional example of a processing system in an ad hoc service provider. The modules 1406 of the ad hoc service provider 106 may be configured with or may include: module 1410 for receiving information related to a second ad hoc service provider. The information includes service information of the second ad hoc service provider. The module 1406 may also be configured with or may also include: a module 1420 to support transmission of information to a server; module 1430 for supporting access points to a network for mobile clients.

It should be noted that the module 1406 may be, for example, a processing system (e.g., 406 of fig. 4 or 802 of fig. 8), a machine-readable medium (e.g., 810 or 818 of fig. 8), a transceiver (e.g., 404 or 402 of fig. 4 or 807 of fig. 8), an interface (e.g., 816 of fig. 8), or a combination of some or all of them. In one example, each of modules 1410, 1420, and 1430 may represent a portion of a processing system, a portion of a machine-readable medium, a portion of a transceiver, a portion of an interface, or a combination of some or all of them, which may be configured with or store instructions or hardware for their respective functions. For example, module 1420 in a machine-readable medium may be instructions stored in the machine-readable medium for supporting transmission of information to a server.

Fig. 15 is a simplified block diagram illustrating a functional example of an ad hoc service provider. The modules 1406 of the ad hoc service provider 106 may be configured with or may include: a module 1510 for receiving the second information, the third information, or both the second and third information from the server. The second information may be based on information associated with a second ad hoc service provider and the third information may include information associated with a third ad hoc service provider.

The module 1406 may also be configured with or may also include: module 1520 to support sending the second information, the third information, or both the second and third information to the mobile client. The module 1406 may also be configured with or may also include: module 1530 for requesting registration of an ad hoc service provider with a server. A second ad hoc service provider may be registered with the server, and a mobile client may be registered with the server. The module 1406 may also be configured with or may also include: block 1540 provides for storing information. This information may be sent out by the second ad hoc service provider. In one example, each of modules 1510, 1520, 1530, and 1540 can represent a portion of a processing system, a portion of a machine-readable medium, a portion of a transceiver, a portion of an interface, or a combination of some or all of them, which modules can be configured with or have stored thereon instructions or hardware for their respective functions.

Fig. 16 is a simplified block diagram illustrating a functional example of an ad hoc service provider. The modules 1406 of the ad hoc service provider 106 may be configured with or may include: a module 1610 configured to connect with a user; a module 1620 configured to enable a user to access a network via the module 1620; a module 1630 for supporting an access point by bridging a first wireless link with a mobile client to a second wireless link with a network. The first wireless link may use a first wireless access protocol. The second wireless link may use a second wireless access protocol different from the first wireless access protocol. In one example, each of the modules 1610, 1620, and 1630 may represent a portion of a processing system, a portion of a machine-readable medium, a portion of a transceiver, a portion of an interface, or a combination of some or all of them, which may be configured with or store instructions or hardware for their respective functions. The module 1610 may be, for example, a keypad 814 and/or a display 812.

Fig. 17 is a simplified block diagram illustrating a functional example of a module for receiving information related to a second ad hoc service provider. The modules 1410 of the ad hoc service provider 106 may be configured with or may include: a module 1710 to support monitoring for beacon information; a module 1720 for enabling wireless reception of information from a second ad hoc service provider or from a mobile client after the mobile client wirelessly receives information from the second ad hoc service provider. In one example, each of modules 1710 and 1720 may represent a portion of a processing system, a portion of a machine-readable medium, a portion of a transceiver, a portion of an interface, or a combination of some or all of them, which may be configured with or store instructions or hardware for their respective functions.

Those of ordinary skill in the art will appreciate that the various illustrative block diagrams, 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 should be understood that the specific order or hierarchy of steps in the processes disclosed is a representation of exemplary approaches. It should be understood that the specific order or hierarchy of steps in the processes may be rearranged depending on design preferences. Some steps may be performed simultaneously. 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 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. The term "some" means one or more unless specifically stated otherwise. Pronouns expressed in males (e.g., him) include females and neutrals (e.g., her and it), 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. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. Furthermore, no element of any claim should be construed in accordance with clause 6 of U.S. patent Law 112, unless the element is explicitly recited in the language of a "functional module" or in a method claim, the element is recited in the language of a "functional step".

Claims (57)

1. A server, comprising:

a processing system for registering a first ad hoc service provider,

the processing system is further configured to enroll a second ad hoc service provider,

the processing system is further configured to receive information associated with the second ad hoc service provider from the first ad hoc service provider, the information including service information of the second ad hoc service provider.

2. The server of claim 1, wherein the service information comprises one or more of: a duration of service provided by the second ad hoc service provider, a location of the second ad hoc service provider, and a quality of service provided by the second ad hoc service provider.

3. The server of claim 1, wherein the service information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

4. The server according to claim 1, wherein the server is a server,

wherein the processing system is further configured to enroll a first plurality of ad hoc service providers;

wherein the processing system is further configured to enroll a second plurality of ad hoc service providers;

wherein the processing system is further configured to receive, from the first plurality of ad hoc service providers, a plurality of pieces of information relating to the second plurality of ad hoc service providers, the plurality of pieces of information being sourced by the second plurality of ad hoc service providers, the plurality of pieces of information including a plurality of pieces of service information of the second plurality of ad hoc service providers; and

wherein the processing system is further configured to generate cluster information related to the first ad hoc service provider, the second ad hoc service provider, the first plurality of ad hoc service providers, and the second plurality of ad hoc service providers, each cluster including at least one ad hoc service provider and at least one mobile client.

5. The server of claim 4, wherein the processing system is further to track the cluster information,

wherein the cluster information comprises one or more of: formation of clusters, age of clusters, pattern of clusters, number of mobile clients in each cluster, information related to alternate ad hoc service providers, geographic location of clusters, and geographic location of members of clusters.

6. The server of claim 1, wherein the processing system is further configured to support transmission of second information to a mobile client, wherein the mobile client has accessed the server through a wireless access point provided by an ad hoc service provider, the second information based on the information related to the second ad hoc service provider received by the server; and

wherein the transmission of the second information to the mobile client enables the mobile client to locate the second ad hoc service provider whose beacon signal is undetectable by the mobile client but which is physically adjacent to the mobile client.

7. The server of claim 6, wherein the second information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

8. The server of claim 1, wherein the processing system is further to support a handoff of a mobile client from one ad hoc service provider to the second ad hoc service provider based at least on the information.

9. The server according to claim 1, wherein the server is a server,

wherein the first ad hoc service provider is configured to provide a wireless access point to a network to a mobile client;

wherein the first ad hoc service provider is to support the wireless access point by bridging a first wireless link with the mobile client to a second wireless link with the network;

wherein the first wireless link uses a first wireless access protocol and the second wireless link uses a second wireless access protocol different from the first wireless access protocol,

wherein the information is issued by the second ad hoc service provider.

10. The server of claim 1, wherein the server is to wirelessly receive the information from the first ad hoc service provider after a mobile client receives the information from the second ad hoc service provider and sends the information to the first ad hoc service provider.

11. The server of claim 1, further comprising:

a network interface coupled to the processing system.

12. The server of claim 1, wherein the server is provided in one or more integrated circuits or one or more printed circuit boards.

13. A server, comprising:

means for registering a first ad hoc service provider;

means for registering a second ad hoc service provider; and

means for receiving information from the first ad hoc service provider related to the second ad hoc service provider, the information comprising service information of the second ad hoc service provider.

14. The server of claim 13, wherein the service information comprises one or more of: a duration of service provided by the second ad hoc service provider, a location of the second ad hoc service provider, and a quality of service provided by the second ad hoc service provider.

15. The server of claim 13, wherein the service information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

16. The server of claim 13, further comprising:

means for registering a first plurality of ad hoc service providers;

means for registering a second plurality of ad hoc service providers;

means for receiving, from the first plurality of ad hoc service providers, a plurality of pieces of information relating to the second plurality of ad hoc service providers, the plurality of pieces of information issued by the second plurality of ad hoc service providers, the plurality of pieces of information including a plurality of pieces of service information of the second plurality of ad hoc service providers; and

means for generating cluster information related to the first ad hoc service provider, the second ad hoc service provider, the first plurality of ad hoc service providers, and the second plurality of ad hoc service providers, each cluster comprising at least one ad hoc service provider and at least one mobile client.

17. The server of claim 16, further comprising:

means for tracking the cluster information;

wherein the cluster information comprises one or more of: formation of clusters, age of clusters, pattern of clusters, number of mobile clients in each cluster, information related to alternate ad hoc service providers, geographic location of clusters, and geographic location of members of clusters.

18. The server of claim 13, further comprising:

means for supporting transmission of second information to a mobile client, wherein the mobile client has access to the server through a wireless access point provided by an ad hoc service provider, the second information based on the information related to the second ad hoc service provider received by the server;

wherein the transmission of the second information to the mobile client enables the mobile client to locate the second ad hoc service provider whose beacon signal is undetectable by the mobile client but which is physically adjacent to the mobile client.

19. The server of claim 18, wherein the second information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

20. The server of claim 13, further comprising:

means for supporting a handoff of a mobile client from one ad hoc service provider to the second ad hoc service provider based at least on the information.

21. The server according to claim 13, wherein the server is further configured to,

wherein the first ad hoc service provider comprises: means for providing a mobile client with a wireless access point to a network;

wherein the first ad hoc service provider further comprises: means for supporting the wireless access point by bridging a first wireless link with the mobile client to a second wireless link with the network;

wherein the first wireless link uses a first wireless access protocol and the second wireless link uses a second wireless access protocol different from the first wireless access protocol,

wherein the information is issued by the second ad hoc service provider.

22. The server of claim 13, wherein the means for receiving comprises: means for supporting wireless reception of the information from the first ad hoc service provider after a mobile client receives the information from the second ad hoc service provider and sends the information to the first ad hoc service provider.

23. A method for acquiring or publishing information related to one or more alternative ad hoc service providers, comprising the steps of:

registering a first ad hoc service provider;

registering the second ad hoc service provider; and

receiving information from the first ad hoc service provider related to the second ad hoc service provider, the information including service information of the second ad hoc service provider.

24. The method of claim 23, wherein the service information comprises one or more of: a duration of service provided by the second ad hoc service provider, a location of the second ad hoc service provider, and a quality of service provided by the second ad hoc service provider.

25. The method of claim 23, wherein the service information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

26. The method of claim 23, further comprising the steps of:

registering a first plurality of ad hoc service providers;

registering a second plurality of ad hoc service providers;

receiving, from the first plurality of ad hoc service providers, a plurality of pieces of information relating to the second plurality of ad hoc service providers, the plurality of pieces of information issued by the second plurality of ad hoc service providers, the plurality of pieces of information including a plurality of pieces of service information of the second plurality of ad hoc service providers; and

generating cluster information relating to the first ad hoc service provider, the second ad hoc service provider, the first plurality of ad hoc service providers, and the second plurality of ad hoc service providers, each cluster including at least one ad hoc service provider and at least one mobile client.

27. The method of claim 26, further comprising the steps of:

the cluster information is tracked and the cluster information is tracked,

wherein the cluster information comprises one or more of: formation of clusters, age of clusters, pattern of clusters, number of mobile clients in each cluster, information related to alternate ad hoc service providers, geographic location of clusters, and geographic location of members of clusters.

28. The method of claim 23, further comprising the steps of:

transmitting second information to a mobile client, wherein the mobile client has accessed the server through a wireless access point provided by an ad hoc service provider, the second information being based on information related to the second ad hoc service provider received by the server,

wherein sending the second information to the mobile client enables the mobile client to locate the second ad hoc service provider whose beacon signal is undetectable by the mobile client but which is physically adjacent to the mobile client.

29. The method of claim 28, wherein the second information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

30. The method of claim 23, further comprising the steps of:

supporting a handoff of a mobile client from one ad hoc service provider to the second ad hoc service provider based at least on the information.

31. The method of claim 23, wherein the step of,

wherein the first ad hoc service provider is configured to provide a wireless access point to a network to a mobile client;

wherein the first ad hoc service provider is to support the wireless access point by bridging a first wireless link with the mobile client to a second wireless link with the network;

wherein the first wireless link uses a first wireless access protocol and the second wireless link uses a second wireless access protocol different from the first wireless access protocol,

wherein the information is issued by the second ad hoc service provider.

32. The method of claim 23, wherein the receiving step comprises:

wirelessly receiving the information from the first ad hoc service provider after a mobile client receives the information from the second ad hoc service provider and sends the information to the first ad hoc service provider.

33. A machine-readable medium comprising instructions executable by a processing system in a server, the instructions comprising code to:

registering a first ad hoc service provider;

registering the second ad hoc service provider; and

receiving information from the first ad hoc service provider related to the second ad hoc service provider, the information including service information of the second ad hoc service provider.

34. The machine-readable medium of claim 33, wherein the service information comprises one or more of: a duration of service provided by the second ad hoc service provider, a location of the second ad hoc service provider, and a quality of service provided by the second ad hoc service provider.

35. The machine-readable medium of claim 33, wherein the service information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

36. The machine-readable medium of claim 33, wherein the instructions further comprise code to:

registering a first plurality of ad hoc service providers;

registering a second plurality of ad hoc service providers;

receiving, from the first plurality of ad hoc service providers, a plurality of pieces of information relating to the second plurality of ad hoc service providers, the plurality of pieces of information issued by the second plurality of ad hoc service providers, the plurality of pieces of information including a plurality of pieces of service information of the second plurality of ad hoc service providers; and

generating cluster information relating to the first ad hoc service provider, the second ad hoc service provider, the first plurality of ad hoc service providers, and the second plurality of ad hoc service providers, each cluster including at least one ad hoc service provider and at least one mobile client.

37. The machine-readable medium of claim 36, wherein the instructions further comprise code for:

the cluster information is tracked and the cluster information is tracked,

wherein the cluster information comprises one or more of: formation of clusters, age of clusters, pattern of clusters, number of mobile clients in each cluster, information related to alternate ad hoc service providers, geographic location of clusters, and geographic location of members of clusters.

38. The machine-readable medium of claim 33, wherein the instructions further comprise code to:

supporting transmission of second information to a mobile client, wherein the mobile client has accessed the server through a wireless access point provided by an ad hoc service provider, the second information being based on information related to the second ad hoc service provider received by the server;

wherein the transmission of the second information to the mobile client enables the mobile client to locate the second ad hoc service provider whose beacon signal is undetectable by the mobile client but which is physically adjacent to the mobile client.

39. The machine-readable medium of claim 38, wherein the second information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

40. The machine-readable medium of claim 33, wherein the instructions further comprise code to:

supporting a handoff of a mobile client from one ad hoc service provider to the second ad hoc service provider based at least on the information.

41. The machine-readable medium of claim 33,

wherein the first ad hoc service provider is configured to provide a wireless access point to a network to a mobile client;

wherein the first ad hoc service provider is to support the wireless access point by bridging a first wireless link with the mobile client to a second wireless link with the network;

wherein the first wireless link uses a first wireless access protocol and the second wireless link uses a second wireless access protocol different from the first wireless access protocol,

wherein the information is issued by the second ad hoc service provider.

42. The machine-readable medium of claim 33, wherein the code for receiving comprises code for:

enabling wireless reception of the information from the first ad hoc service provider after a mobile client receives the information from the second ad hoc service provider and sends the information to the first ad hoc service provider.

43. A processing system for performing a method of obtaining or publishing information associated with one or more alternate ad hoc service providers, the method comprising the steps of:

registering a first ad hoc service provider;

registering the second ad hoc service provider; and

receiving information from the first ad hoc service provider related to the second ad hoc service provider, the information including service information of the second ad hoc service provider.

44. The processing system of claim 43, wherein the service information comprises one or more of: a duration of service provided by the second ad hoc service provider, a location of the second ad hoc service provider, and a quality of service provided by the second ad hoc service provider.

45. The processing system of claim 43, wherein the service information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

46. The processing system of claim 43, wherein the method further comprises the steps of:

registering a first plurality of ad hoc service providers;

registering a second plurality of ad hoc service providers;

receiving, from the first plurality of ad hoc service providers, a plurality of pieces of information relating to the second plurality of ad hoc service providers, the plurality of pieces of information issued by the second plurality of ad hoc service providers, the plurality of pieces of information including a plurality of pieces of service information of the second plurality of ad hoc service providers; and

generating cluster information relating to the first ad hoc service provider, the second ad hoc service provider, the first plurality of ad hoc service providers, and the second plurality of ad hoc service providers, each cluster including at least one ad hoc service provider and at least one mobile client.

47. The processing system of claim 46, wherein the method further comprises the steps of:

the cluster information is tracked and the cluster information is tracked,

wherein the cluster information comprises one or more of: formation of clusters, age of clusters, pattern of clusters, number of mobile clients in each cluster, information related to alternate ad hoc service providers, geographic location of clusters, and geographic location of members of clusters.

48. The processing system of claim 43, wherein the method further comprises the steps of:

transmitting second information to a mobile client, wherein the mobile client has accessed the server through a wireless access point provided by an ad hoc service provider, the second information being based on information related to the second ad hoc service provider received by the server,

wherein sending the second information to the mobile client enables the mobile client to locate the second ad hoc service provider whose beacon signal is undetectable by the mobile client but which is physically adjacent to the mobile client.

49. The processing system of claim 48, wherein the second information comprises one or more of: channel information of the second ad hoc service provider, communication capacity of the second ad hoc service provider, duration of service provided by the second ad hoc service provider, location of the second ad hoc service provider, price of service provided by the second ad hoc service provider, quality metric of the second ad hoc service provider, and quality of service provided by the second ad hoc service provider.

50. The processing system of claim 43, wherein the method further comprises the steps of:

supporting a handoff of a mobile client from one ad hoc service provider to the second ad hoc service provider based at least on the information.

51. The processing system according to claim 43, wherein,

wherein the first ad hoc service provider is configured to provide a wireless access point to a network to a mobile client;

wherein the first ad hoc service provider is to support the wireless access point by bridging a first wireless link with the mobile client to a second wireless link with the network;

wherein the first wireless link uses a first wireless access protocol and the second wireless link uses a second wireless access protocol different from the first wireless access protocol,

wherein the information is issued by the second ad hoc service provider.

52. The processing system of claim 43, wherein the receiving step comprises:

wirelessly receiving the information from the first ad hoc service provider after a mobile client receives the information from the second ad hoc service provider and sends the information to the first ad hoc service provider.

53. An apparatus in a communication system, comprising:

a processing system for receiving operating parameters of existing communication entities of an ad hoc network and setting the operating parameters for access by the communication entities and for access by other communication entities determined to join the ad hoc network.

54. The apparatus of claim 53, wherein the communication entity comprises an ad hoc service provider.

55. The apparatus of claim 54, wherein the communication entity comprises a mobile client.

56. The apparatus of claim 53, wherein the operational parameters comprise parameters related to capabilities of the ad hoc network.

57. The apparatus of claim 53, wherein the operating parameters further comprise: a parameter relating to an ability of an ad hoc service provider to join the ad hoc network.