HK1145764A - Ad hoc service provider's ability to provide service for a wireless network - Google Patents

Description

Ad hoc service provider's ability to provide services for wireless networks

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

This patent application claims priority from provisional application No.60/956,658 entitled "METHOD FOR improving environment WIRELESS AD HOC MOBILE SERVICE PROVIDER" filed on 8, 14/2007 and assigned to the assignee of the present application and expressly incorporated herein by reference.

Technical Field

The present disclosure relates generally to telecommunications, and more particularly to the ability of ad hoc service providers to provide services for wireless networks.

Background

Wireless telecommunication systems are widely deployed to provide various services to consumers such as telephony, data, video, audio, messaging, broadcasting, and so on. These systems continue to evolve as market forces drive wireless communications to new heights. Today, wireless networks provide broadband internet access to mobile users on a regional scale, national scale, or even worldwide. Such networks are sometimes referred to as Wireless Wide Area Networks (WWANs). WWAN operators typically provide their subscribers with a wireless access plan, e.g., a monthly flat-rate subscription plan.

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 a valid subscription plan. Ad hoc networks allow mobile devices to dynamically connect over a wireless interface using protocols such as WLAN, bluetooth, UWB, or other protocols. There is a need in the art for a method that allows a user of a mobile device without WWAN access to dynamically subscribe to wireless access services provided by a user of a WWAN-capable mobile device, wherein the subscription is made using wireless ad hoc networking between the mobile devices belonging to both users.

Disclosure of Invention

In one aspect disclosed herein, an ad hoc service provider for a wireless network is provided. The ad hoc service provider includes a processing system configured to support a first wireless access protocol. The processing system is also configured to support a wireless access point for one or more mobile clients using a second wireless access protocol. Additionally, the processing system is further configured to change an ability of the ad hoc service provider to provide services for the wireless network in response to an event related to the resource.

In another aspect disclosed herein, an ad hoc service provider for a wireless network is provided. The ad hoc service provider includes: means for supporting a first radio access protocol; and means for supporting a wireless access point for one or more mobile clients using a second wireless access protocol. The ad hoc service provider further comprises means for changing an ability of the ad hoc service provider to provide services for the wireless network in response to an event related to the resource.

In another aspect disclosed herein, a method of providing service from a mobile node of a wireless network is disclosed. The method includes sending a request to allow the mobile node to provide a service as an ad hoc service provider. The method also includes detecting a resource-related event of the mobile node of the wireless network and changing a capability of the mobile node to provide service to the wireless network.

In another aspect disclosed herein, a machine-readable medium includes instructions executable by a processing system of a mobile node. The instructions include code for: detecting a resource-related event of the mobile node; and changing the mobile node's ability to provide services as an ad hoc service provider for the wireless network based on the detection.

It is understood that other embodiments of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein various embodiments of the invention are shown and described by way of illustration. As will be realized, the invention is capable of other and different embodiments and its several details are capable of modifications 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 conceptual block diagram illustrating an example of a telecommunications system.

Fig. 2 is a conceptual block diagram illustrating an example of the functionality of an ad hoc service provider.

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

Fig. 4a is a flow chart illustrating an exemplary method for providing service from a mobile node of a wireless network.

Fig. 4b is a flow chart illustrating another exemplary method for providing service from a mobile node of a wireless network.

Fig. 5 is a conceptual block diagram of an exemplary configuration of an ad hoc service provider.

Detailed Description

The various detailed descriptions set forth below in connection with the appended drawings are intended as a description of various configurations of the present invention and are not intended to represent the only configurations in which the present invention may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the present invention. However, it will be apparent to 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 conceptual block diagram illustrating an example of a telecommunications system. The telecommunications system 100 is shown with multiple WWANs 104 for providing broadband access to the network 102 for mobile users. Network 102 may be a packet-based network, such as the Internet, or some other suitable network. For clarity of presentation, two WWANs 104 are shown with backhaul connections to network 102. However, the number of WWANs used to provide broadband access to network 102 is not limited to two WWANs. Each WWAN104 may be implemented with a plurality of fixed-location base stations (not shown) dispersed throughout a geographic area. The geographical area can generally be subdivided into smaller areas called cells. Each base station may be configured 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 wireless access protocols. For example, one of the WWANs 104 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 applying 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 a project within 3GPP2 that improves the Universal Mobile Telecommunications System (UMTS) mobile phone standard 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 throughout this disclosure 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 access the network 102 directly through the WWAN 104. In the telecommunications system depicted in FIG. 1, the mobile nodes use EV-DO, UMB, or LTE wireless access protocols to access the WWAN 104; in actual implementations, however, these mobile nodes may be configured to support any wireless access protocol.

One or more of the mobile nodes may be configured to create an ad hoc network in its vicinity based on a wireless access protocol that is the same as or different from the wireless access protocol used to access WWAN 104. For example, a mobile node may support a UMB wireless access protocol with a WWAN while providing an IEEE 802.11 access point for other mobile nodes that cannot directly access the WWAN. IEEE 802.11 represents a set of Wireless Local Access Network (WLAN) standards developed by the IEEE 802.11 association for short-range communications (e.g., tens to hundreds of meters). While IEEE 802.11 is a public WLAN wireless access protocol, other suitable protocols may be used.

A mobile node that may be used to provide an access point for another mobile node will be referred to herein as an "ad hoc service 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 will be 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, a mobile phone, a Personal Digital Assistant (PDA), a mobile digital audio player, a mobile gaming device, a digital camera, a digital camcorder, a mobile audio device, a mobile video device, a mobile multimedia device, a component of any of the aforementioned devices (e.g., an integrated circuit included or to be included in any of the aforementioned devices), 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, otherwise mobile clients 108 will not have access to network 102. Server 110 may be used as a "switch" to allow mobile client 108 to purchase unused bandwidth from ad hoc service provider 106 to access network 102, e.g., through WWAN 104.

The ad hoc service provider 106, the server 110, and the one or more mobile clients 108 may establish a network that is an ad hoc heterogeneous wireless network. By way of example, the heterogeneous wireless networks may include at least two types of wireless networks (e.g., WWAN and WLAN). For example, an ad hoc network may be one whose particular configuration may change over time or as one network forms to the next. The network configuration is not planned in advance before the network is established. Examples of the configuration of an ad hoc network may include configurations about which members of the network will be (e.g., which ad hoc service provider, which server, and/or which mobile client will be included in the network), configurations about the geographic locations of the ad hoc service provider and the mobile client, and configurations about when and for how long the network is to be established.

An exemplary scenario of an ad hoc network is described below for purposes of example only. Case 1: when a mobile user is at an airport at 8 am tuesday, he may turn on his mobile node (e.g., laptop or mobile phone), treat it as an ad hoc service provider while waiting for an airplane, and establish an ad hoc network for up to 30 minutes. The 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 can use the same mobile node as an ad hoc service provider to form another ad hoc network for up to 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, different ad hoc service providers may form an ad hoc network at the airport where the first ad hoc service provider was located the day before. Since service providers and clients are mobile, ad hoc networks may be "mobile" networks.

The server 110 may be a centralized server or a distributed server. The centralized server may be a dedicated server or integrated into another entity such as a desktop or laptop computer or a host computer. A distributed server may be distributed among multiple servers and/or one or more other entities such as laptops or desktops or mainframes. In at least one configuration, server 110 may be fully or partially integrated into one or more ad hoc service providers.

In one configuration of the telecommunications system 100, the server 110 charges the mobile client 108 based on usage. This may be an attractive alternative to monthly flat-rate radio access plans for temporary users of mobile internet services. The revenue generated from usage charges may be distributed to various entities in the telecommunications system 100 in a manner that tends to make the switch always efficient. For example, a portion of the revenue may be distributed to ad hoc service providers, thereby providing a incentive for benefits to make mobile users become ad hoc service providers. Another portion of the revenue may be allocated to the WWAN operators to compensate them for bandwidth that would otherwise not be used. Another portion of the revenue may be distributed to the manufacturer of the mobile node. The rest of the revenue may be retained by the server operator providing the switch. The server 110, which may be a centralized server as shown or a distributed server comprising a plurality of servers, may be used to determine how to allocate revenue generated from the mobile clients 108 to various entities in the telecommunications system 110.

The server 110 may be implemented as a trusted server. The server 110 may be authenticated using Public Key Infrastructure (PKI) certificates in a Transport Layer Security (TLS) session 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 be authenticated using a self-issued certificate or by some other means

During enrollment, regardless of the manner used to authenticate the server 110, 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. In one configuration of the telecommunications system 100, the mobile client 108 may register with the server 110 to establish a username and password with payment information. The ad hoc service provider 106 may register with the server 110 to notify that it wishes to provide a wireless access point (e.g., an internet access point) to the network 102 to the mobile client 108.

The server 110 may also be used to provide admission control. The server 110 determines through the admission control whether to allow the ad hoc service provider 106 to provide service within a geographic location. If the server 110 determines that additional ad hoc service providers 106 will adversely affect performance in the WWAN, the server 110 may limit the number of ad hoc service providers 106 at a given location. WWAN operators that do not want its mobile users to provide service within a given geographic location may impose additional constraints based on various network constraints.

The server 110 may also be used to manage dynamic sessions established between the ad hoc service provider 106 and the mobile client 108. In one configuration of the telecommunications system 100, when the ad hoc service provider 106 is mobile and wishes to provide services, extended authentication protocol-tunneling layer security (EAP-TTLS) may be used for authentication, authorization and accounting (AAA) and secure session establishment of a connection between the ad hoc service provider 106 and the server 110. EAP-TTLS may also be used for session initiation requests by mobile client 108. In the latter case, the mobile client 108 is a requestor, the ad hoc service provider 106 is an authenticator, and the server 110 is an authentication server. The ad hoc service provider 106 sends the mobile client's credentials to the server 110 for EAP-AAA authentication. The EAP-TTLS authentication response from server 110 is then used to generate the master shared key. Next, a link encryption key may be established between the ad hoc service provider 106 and the mobile client 108.

Additional security may be achieved using a secure socket layer virtual private network (SSL VPN) tunnel between mobile client 108 and server 110. The SSL VPN tunnel is used to encrypt traffic routed through the ad hoc service provider 106 to provide higher privacy for the mobile client 108. Alternatively, the tunnel may be an IPsec tunnel or may be implemented using some other suitable tunneling protocol.

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

The server 110 may also provide support for handoff of the mobile client 108 from one ad hoc service provider 106 to another ad hoc service provider 106 based on any number of factors. These factors may include, for example, the quality of service (QoS) required by each mobile client 108, the duration of the session required by each mobile client 108, and the load, link conditions, and energy level (e.g., battery life) at the ad hoc service provider 106.

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

Fig. 2 is a conceptual block diagram illustrating an example of the functionality of the ad hoc service provider 106. The ad hoc service provider 106 has the ability to bridge wireless links based on homogeneous or heterogeneous wireless access protocols. This may be accomplished using a WWAN network interface 202, a WLAN network interface 204, where the WWAN network interface 202 supports a wireless access protocol for the WWAN104 of the network 102 and the WLAN network interface 204 provides a wireless access point for the mobile client 108. By way of example, the WWAN network interface 202 may include transceiver functionality that supports EV-DO for network access through the WWAN104, and the WLAN network interface 204 may include transceiver functionality that provides an 802.11 access point for the mobile client 108. Each of the network interfaces 202, 204 may be configured to implement the physical layer by demodulating wireless signals and performing other Radio Frequency (RF) front-end processing. Each of the network interfaces 202, 204 may also be configured to implement the data link layer by managing the transfer of data over the physical layer.

The ad hoc service provider 106 is shown with a filtering interconnection and session monitoring module 206. The module 206 provides filtering of content from the mobile clients 108 so that the interconnection between the ad hoc wireless link and the WWAN network interface 202 is provided only to mobile clients 108 that have been authenticated by the server. The module 206 is also responsible for monitoring sessions between the server and the mobile client 108 that have been authenticated. The module 206 also maintains a tunneled connection between the server and the authenticated mobile client 108.

The ad hoc service provider 106 also includes a service provider application 208 that: (1) the permission module 206 provides ad hoc services to the mobile client 108 and (2) supports WWAN or internet access to mobile users or subscribers of the ad hoc service provider 106. The latter functionality is supported through a service provider user interface 212, which 212 communicates with the WWAN network interface 202 under control of a service provider application 208 through module 206. The user interface 212 may include any other combination of keypads, displays, speakers, microphones, joysticks, and/or user interface devices that allow a mobile user or user to access the WWAN104 or network 102 (see fig. 1).

As discussed above, the service provider application 208 also allows the module 206 to provide ad hoc services to the mobile client 108. The service provider application 208 maintains a session with the server 110 to exchange customized messages with the server 110. In addition, the service provider application 208 maintains a separate session with each mobile client 108 for the exchange of custom messages between the service provider application 208 and that mobile client 108. The service provider application 208 provides information about authenticated and licensed clients to the filtered interconnection and session monitoring module 206. The filtering interconnection and session monitoring module 206 only allows content flow for authenticated and allowed mobile clients 108. The filtered interconnection and session monitoring module 206 also optionally monitors information about the content flow associated with the mobile client 108, such as the amount of content sent out from the mobile client 108 and sent to the mobile client 108, as well as information about WWAN and WLAN network resource utilization and available bandwidth on the wireless channel. The filtered interconnection and session monitoring module 206 may additionally and/or alternatively provide this information to the service provider application 208. The service provider application 208 may additionally and/or alternatively process this 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 services. It should be noted that the various functions described in connection with the module 206 and the service provider application 208 may be implemented in one or more sets of modules that cooperate to provide these functions at the ad hoc service provider 106 in any given platform.

When the ad hoc service provider 106 decides to provide ad hoc services, the service provider application 208 sends a request to the server 110 for approval. The service provider application 208 requests authentication by the server 110 and approval from the server 110 to provide services to one or more mobile clients 108. The server 110 may authenticate the ad hoc service provider 106 and then determine whether it approves the ad hoc service provider's 106 request. As previously described, the request may be denied, for example, if the number of ad hoc service providers 106 in the same geographic area is too large or if the WWAN operator imposes certain restrictions on the ad hoc service providers 106.

After authenticating the ad hoc service provider 106, the service provider application 208 may advertise service information, such as an ad hoc WLAN Service Set Identifier (SSID), a service price, a service duration, availability of the ad hoc service provider, and a quality metric for the ad hoc service provider. The service provider application 208 may also cause changes to the advertised service information as conditions change. Interested mobile clients 108 may associate with the SSID to access the ad hoc service provider 106. The service provider application 208 may then route authentication messages between the mobile client 108 and the server 110 and configure the filtered interconnection and session monitoring module 206 to connect the mobile client 108 to the server after the mobile client 108 is authenticated. During authentication of the mobile client 108, the service provider application 208 may use an unsecured wireless link.

After authenticating the mobile client 108, the service provider application 208 may additionally and/or alternatively choose to move the mobile client 108 to a new SSID with a secure link. In this case, the service provider application 208 may allocate the time spent in each SSID according to the load that needs to be supported for the existing session with the mobile client 108.

The service provider application 208 can also determine whether the mobile client 108 can support the mobile client 108 before allowing it to access the network. Resource intelligence can be used to estimate battery power drain, QoS requirements, bandwidth requirements, latency requirements, processing requirements, required network access time, and/or other processing resources required due to acceptance of a mobile client 108, and can help determine whether a service provider application 208 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 208 may grant the mobile clients 108 and provide them with certain QoS guarantees, such as average bandwidth expected during the session. The average throughput provided to each mobile client 108 over a time window may be monitored. The service provider application 208 may monitor the throughput of all flows that flow through it to ensure that the resource utilization of the mobile client 108 is below a certain threshold and that it meets the QoS requirements that it agrees to provide to the mobile client 108 during the establishment of the session.

The service provider application 208 may also provide a particular level of security to the wireless access point by routing the content through the filtering interconnect and session monitoring module 306 without being able to crack the content. Similarly, the service provider application 208 may be configured to ensure that content routed between the user interface 212 and the WWAN104 via the module 206 is not deciphered by the mobile client 108. The service provider application 208 may use any suitable encryption technique to implement this functionality.

The service provider application 208 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 208 and the mobile client 108 during session initiation. If the service provider application 208 determines that it cannot provide mobile client 108 with access to the network within the agreed-upon period of time, it may notify the server 110 and mobile client 108 of its invalidity. This may occur due to energy constraints (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 as long as such ad hoc service provider exists in the vicinity of the mobile client 108. The service provider application 208 may support this handoff of the mobile client 108.

The service provider application 208 may also contribute processing resources to maintain wireless links or restricted sessions with mobile clients 108 served by other ad hoc service providers 106. These mobile nodes 108 may be pre-authenticated by routing authentication messages to and from the server 110. This may facilitate handoff of the mobile client 108 to the ad hoc service provider 106.

The service provider application 208 may manage the mobile client 108 as a whole and the session in particular, through the user interface 212. Alternatively, the service provider application 208 may support a seamless mode of operation with processing resources that are 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. This seamless mode of operation is desirable when a mobile user does not want to manage the mobile client 108 but wants to continue to generate revenue by contributing bandwidth to the mobile client 108.

Although not shown, the ad hoc service provider 106 may also include a server application. The server application may be used to allow the ad hoc service provider 106 to act as a server to authenticate the mobile client 108.

Fig. 3 is a conceptual block diagram illustrating an example of a hardware configuration of an ad hoc service provider. Ad hoc service provider 106 is shown having a WLAN transceiver 302, a WWAN transceiver 304, and a processing system 306. For example, WLAN transceiver 302 may be used to implement an analog portion of the physical layer for WLAN network interface 204 (see fig. 2), and WWAN transceiver 304 may be used to implement an analog portion of the physical layer for WWAN network interface 202 (see fig. 2).

The processing system 306 may be used to implement the digital processing portions of the physical layer and the link layer for both the WLAN network interface 204 and the WWAN network interface 202 (see fig. 2). The processing system 306 may also be used to implement the filtering interconnection and session monitoring module 206 and the service provider application 208 (see fig. 2).

The processing system 306 may be implemented using hardware, software, or a combination of both. For example, processing system 306 may be implemented using one or more processors. A processor may be a general purpose processor, 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 manipulation of information. The processing system 306 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 the form of source code, binary code, executable code, or any other suitable format).

The machine-readable medium may include memory integrated into a processor, such as may be integrated 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, hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable memory. Additionally, a machine-readable medium may include a transmission line or a carrier wave for encoding a data signal. Those of ordinary skill in the art will recognize how best to implement the described functionality of the processing system 306. According to one aspect disclosed herein, a machine-readable medium is a computer-readable medium encoded or stored with instructions and is a computing element that defines the structural and functional interrelationships between the instructions and the rest of the system that allow the functionality of the instructions 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.

Turning now to the mobile client in fig. 1, the mobile client 108 may use a TLS session to register with the server 110. After registration, the mobile client 108 may search 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 that the ad hoc service provider 106 may support, QoS metrics of the ad hoc service provider 106, and prices of advertised services. 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 so that all traffic between the two may be encrypted. The transport layer port may remain open and unencrypted to provide visibility for network address translation functions at the ad hoc service provider 106.

The handoff of the mobile client 108 from one ad hoc service provider to another may be due to any number of factors. The handoff of the mobile client 108 may be performed in various ways. 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 mentioned, 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 an active list of the various ad hoc service providers 106 in its vicinity for handoff. When the current ad hoc service provider 106 needs to stop its service, the mobile client 108 may select one ad hoc service provider 106 from the active list to handoff. When handoff is not feasible, the mobile client 108 may need to reconnect through another different ad hoc service provider 106 to access the internet.

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 potentially access multiple ad hoc service providers 106 simultaneously, using a different transceiver for each ad hoc service provider 106. Different channels may be used if multiple ad hoc service providers 106 may be accessed using the same wireless access protocol. If the mobile client 108 has only one transceiver available, it may allocate the time it takes to access each ad hoc service provider 106.

Referring back to fig. 1 and 3, the resource intelligence on the ad hoc service provider is described in detail below. The ad hoc service provider 106 may include network-known and platform-known resource intelligence for managing the ability of the ad hoc service provider to provide services to a wireless network, which may include the ad hoc service provider 106, a server 110, and one or more mobile clients 108. The server 110 may be a single server or a plurality of servers. The wireless network may be an ad-hoc heterogeneous wireless network including at least two types of wireless networks.

The processing system 306 of the ad hoc service provider 106 may be configured to support a first wireless access protocol (e.g., a wireless access protocol for a WWAN) to communicate with, for example, a WWAN104, network 102, and server 110. It may also be configured to support wireless access points for one or more mobile clients 108 using a second wireless access protocol (e.g., a wireless access protocol for WLAN). Additionally, the processing system 306 may be configured to change the ability of the ad hoc service provider to provide services to the wireless network in response to an event related to the resource.

Ad hoc service provider 106 may include a first wireless transceiver (e.g., WWAN transceiver 304) supporting a first wireless link using a first wireless access protocol and a second wireless transceiver (e.g., WLAN transceiver 302) supporting a second wireless link using a second wireless access protocol. The processing system may also be configured to support the wireless access point by bridging a second wireless link with one or more mobile clients to the first wireless link.

The first wireless access protocol (e.g., EV-DO) may be different from the second wireless access protocol (e.g., IEEE 802.11). In an alternative configuration, the first and second radio access protocols may be the same regardless of whether the network includes two different types of wireless networks, e.g., WWAN and WLAN.

Events related to a resource may include: for example, an indication that an ad hoc service provider's energy level (e.g., ad hoc service provider's battery life) is below an energy threshold and an indication that a load on processing system 306 (e.g., a load due to processing/communication/actions internal or external to the ad hoc service provider) is above a load threshold. The events related to the resource may further include: an indication that an available bandwidth for communications using the first wireless access protocol (e.g., communications with the WWAN104, the network 102, and/or the server 110) is below a first bandwidth threshold or an available bandwidth for communications using a wireless access point (e.g., communications with the mobile client 108) is below a second bandwidth threshold. In one example, an event related to a resource includes all indications described in this paragraph. In another example, an event related to a resource includes only one of the indications described in this paragraph. In another example, the resource-related event includes some of the indications described in this paragraph. In another example, the resource-related event includes a combination of other indications with one or more of the indications.

In response to detecting an event related to a resource, the ad hoc service provider 106 (or the processing system 306) may perform one or more of the following exemplary actions: (a) not allowing any new mobile terminal to enter the wireless network; (b) initiating a handoff of some or all existing mobile clients of the ad hoc service provider to one or more other ad hoc service providers; (c) terminating the services that the ad hoc service provider is providing to some or all of the existing mobile clients (e.g., turning off the ad hoc service provider will terminate the services that are providing to all of the existing mobile clients); (d) changing one or more attributes of the ad hoc service provider's service, such as a data rate of the service or a duration of the service; (e) perform some other action; (f) no action is performed; or (g) notify some or all of the mobile client 108 and the server 110 of the action that the ad hoc service provider 106 is planning to take in response to detecting an event related to a resource, where the action may be one or more of the actions described in (a) - (f) of this paragraph.

The ad hoc service provider 106 (or the processing system 306) may take different actions for each of the existing mobile clients and servers 110 or notify each of the existing mobile clients and servers 110 of the different actions. Alternatively, the ad hoc service provider 106 (or the processing system 306) may take the same action for each or some of the existing mobile clients and servers 110, or notify each or some of the existing mobile clients and servers 110 of the same action. For example, for the actions described in (d), the ad hoc service provider may change the data rate of the services it provides to one or more existing mobile clients. Additionally or alternatively, the ad hoc service provider may change the duration of the service provided to one or more existing mobile clients. Each mobile client (or some mobile clients) may have the same or different data rates, and the ad hoc service provider may change the data rates in the same or different ways for each mobile client (or for some mobile clients). Further, each mobile client (or some mobile clients) may have the same or different service durations, and the ad hoc service provider may change the durations in the same or different ways for each mobile client (or for some mobile clients).

Fig. 4a is a flow chart illustrating an exemplary method for providing service from a mobile node of a wireless network. In step 410, a request is sent to allow the mobile node to provide services as an ad hoc service provider. This step may include sending, from the mobile node to a server, a request to allow the mobile node to provide a service as an ad hoc service provider for the wireless network. In step 420, a resource-related event of the mobile node of the wireless network is detected. This step may include detecting, at the mobile node, a resource-related event of the mobile node. At step 430, the mobile node's ability to provide service to the wireless network is changed. The step may include changing, at the mobile node, a capability of the mobile node to provide service to the wireless network in response to the detecting step.

According to one aspect disclosed herein, a mobile node may include a user interface, and this may allow a user to access a wireless network through the user interface. The mobile node may also be configured to support a first radio access protocol and a second radio access protocol, and the first radio access protocol may be different from the second radio access protocol.

Fig. 4b illustrates a flow chart of another exemplary method for providing services from a mobile node of a wireless network (e.g., ad hoc service provider 106 in fig. 1). In step 405, the mobile node requests registration with the server 110 of fig. 1. The request includes the mobile node's desire to provide a wireless access point to one or more mobile clients 108 in fig. 1. One or more mobile clients 108 may also have registered with the server 110. After the mobile node registers with the server, the mobile node sends a request to the server 110 to allow the mobile node to provide services as an ad hoc service provider for the wireless network in step 411. The request may be to service the wireless network within a geographic location. After step 411, the mobile node receives a response from the server 110 regarding granting the mobile node as an ad hoc service provider for the wireless network in step 413.

In step 416, the mobile node admits one or more mobile clients 108 into the wireless network. Which occurs after step 411. The mobile node may seamlessly admit a mobile client without the need for a mobile user at the mobile node to manage one or more mobile clients. After step 411, the mobile node detects a resource-related event of the mobile node of the wireless network in step 421. Step 421 may be performed automatically without intervention from the mobile user of the mobile node. At step 423, the mobile node determines an action in response to detecting the event related to the resource. At step 426, the mobile node communicates the action to the server 110 using the first radio access protocol or to one or more mobile clients 108 using the second radio access protocol. In step 431, the mobile node changes its capabilities to provide services to the wireless network. The mobile node may thus change its availability to some or all of the server 110 and the mobile client 108 in response to resource-related events. Step 431 may be performed automatically without intervention from the mobile user of the mobile node. Processing system 306 in fig. 3 may perform or may initiate the various activities described with reference to fig. 4a and 4 b.

Fig. 5 is a conceptual block diagram of an exemplary configuration of an ad hoc service provider. An example of the functionality of a processing system in an ad hoc service provider is shown. The ad hoc service provider 106 may be used to establish a wireless network that includes the server 110 of fig. 1 and one or more mobile clients 108 of fig. 1. Ad hoc service provider 106 may include a processing system 306, with processing system 306 including a module 510 for supporting a first wireless access protocol (e.g., a wireless access protocol for a WWAN). Processing system 306 may also include a module 520 for supporting wireless access points for one or more mobile clients 108 using a second wireless access protocol (e.g., a wireless access protocol for WLAN). Additionally, processing system 306 can include a module 530 for changing an ad hoc service provider's ability to provide services to a wireless network in response to an event related to a resource.

According to one aspect disclosed herein, the wireless network is a heterogeneous wireless network including a first wireless network and a second wireless network. The ad hoc service provider 106 may include a first wireless transceiver supporting a first wireless link using a first wireless access protocol and a second wireless transceiver supporting a second wireless link using a second wireless access protocol, wherein the processing system is further configured to support a wireless access point by bridging the second wireless link to the first wireless link. The first radio access protocol may be different from the second radio access protocol.

The ad hoc service provider 106 may also include a user interface 212, and the processing system 306 may be further configured to allow a user to access the wireless network through the user interface 212.

According to one aspect disclosed herein, the wireless network includes a server, and the ad hoc service provider 106 further includes: means for communicating with a server using a first radio access protocol; and means for communicating with one or more mobile clients using a second wireless access protocol. The ad hoc service provider may further include: means for interacting with a user; and means for allowing a user to access the wireless network through the means for interacting with the user.

According to one aspect disclosed herein, a machine-readable medium stores instructions executable by a processing system of a mobile node, and the instructions include: the method includes sending a request to allow the mobile node to provide a service as an ad hoc service provider for the wireless network prior to detecting the resource-related event. The code for transmitting may include: code for sending a request to allow a mobile node to provide a service within a geographic location as an ad hoc service provider for a wireless network. The instructions may also include: code for receiving a response granting permission to the mobile node as an ad hoc service provider for the wireless network. The instructions may also include: code for admitting one or more mobile clients into a wireless network. The code for granting may be executed seamlessly without requiring a mobile user at the mobile node to manage the one or more clients. The instructions may also include: code for determining an action in response to detecting an event related to a resource.

According to one aspect disclosed herein, the wireless network includes a mobile node, a server 110, and one or more mobile clients 108, wherein the instructions may further include: code for communicating the action to the server 110 using a first wireless access protocol or communicating the action to the one or more mobile clients 108 using a second wireless access protocol. The mobile node may register with the server 110, one or more mobile clients 108 may register with the server 110, and the instructions may include: code for changing a capability of the mobile node to provide services to some or all of: a server and one or more mobile clients.

According to one aspect disclosed herein, code for detecting a resource-related event of a mobile node is automatically executed without intervention from a mobile user of the mobile node, and code for changing an ability of the mobile node to provide services as an ad hoc service provider of a wireless network is automatically executed without intervention from the mobile user of the mobile node.

According to one aspect disclosed herein, the code for transmitting comprises: code for transmitting, from a mobile node to a server, a request for allowing the mobile node to provide a service as an ad hoc service provider for a wireless network, the code for detecting comprising: code for detecting, at a mobile node, a resource-related event of the mobile node, and the code for changing comprises: code for changing, at a mobile node, a capability of the mobile node to provide service to a wireless network in response to detecting an event related to a resource.

Those of ordinary skill in the art will appreciate that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application.

It is to be understood that the specific order or hierarchy of steps in the processes disclosed is merely an example of exemplary approaches. It should be understood that the specific order or hierarchy of steps in the processes may be rearranged based on design preferences. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the versions shown herein, but are 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" but rather "one or more" unless specifically so stated. The term "some" means one or more unless otherwise specified. Pronouns in the male (e.g., his) include female and neutral (e.g., her or 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 and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. Elements in the claims cannot be construed with the provisions of chapter six of 35 u.s.c. § 112 unless the element is explicitly recited with the phrase "module for … …", or in the case of method claims the element is recited with the phrase "step for … …".

Claims (25)

1. An ad hoc service provider for a wireless network, the ad hoc service provider comprising:

a processing system configured to support a first radio access protocol;

the processing system is further configured to support a wireless access point for one or more mobile clients using a second wireless access protocol;

the processing system is further configured to change an ability of the ad hoc service provider to provide services to the wireless network in response to an event related to a resource.

2. The ad hoc service provider of claim 1, wherein the resource-related event is one or more of: an indication that an energy level of the ad hoc service provider is below an energy threshold, an indication that a load on the processing system is above a load threshold, or an indication that an available bandwidth of communications using the first wireless access protocol is below a first bandwidth threshold or an available bandwidth of communications using the wireless access point is below a second bandwidth threshold.

3. The ad hoc service provider of claim 1, wherein to change the capabilities of the ad hoc service provider, the processing system is configured to not allow any new mobile clients to enter the wireless network in response to the resource-related event.

4. The ad hoc service provider of claim 1, wherein to change the capabilities of the ad hoc service provider, the processing system is configured to support a handoff of some or all of the one or more mobile clients to one or more other ad hoc service providers in the event that the one or more mobile clients are existing mobile clients in response to the resource-related event.

5. The ad hoc service provider of claim 1, wherein to change the capabilities of the ad hoc service provider, the processing system is configured to terminate services the ad hoc service provider is providing to some or all of the one or more mobile clients in response to the resource-related event.

6. The ad hoc service provider of claim 1, wherein the processing system is configured to change one or more attributes of the service in response to the resource-related event.

7. The ad hoc service provider of claim 6, wherein the one or more attributes comprise one or more of: a data rate of a service of the ad hoc service provider or a duration of the service of the ad hoc service provider.

8. The ad hoc service provider of claim 1, wherein the wireless network comprises a server, and wherein to change the ad hoc service provider's capabilities, the processing system is configured to notify some or all of the one or more mobile clients and the server of an action in response to the resource-related event.

9. The ad hoc service provider of claim 8, wherein the action is one or more of: the method may further include not allowing any new mobile clients to access the wireless network, initiating a handoff of some or all of the one or more mobile clients to one or more other ad hoc service providers, terminating services being provided by the ad hoc service provider to some or all of the one or more mobile clients, or changing one or more attributes of the services of the ad hoc service provider.

10. The ad hoc service provider of claim 9, wherein the one or more attributes comprise one or more of: a data rate of a service of the ad hoc service provider or a duration of the service of the ad hoc service provider.

11. The ad hoc service provider of claim 8, wherein the processing system is configured to notify different actions for each or some of the one or more mobile clients and the server.

12. The ad hoc service provider of claim 1, wherein the first radio access protocol is different from the second radio access protocol.

13. An ad hoc service provider for a wireless network, comprising:

means for supporting a first radio access protocol;

means for supporting a wireless access point for one or more mobile clients using a second wireless access protocol; and

means for changing an ability of the ad hoc service provider to provide services to a wireless network in response to an event related to a resource.

14. The ad hoc service provider of claim 13, wherein the resource-related event is one or more of: an indication that an energy level of the ad hoc service provider is below an energy threshold, an indication that a load on a processing system of the ad hoc service provider is above a load threshold, or an indication that an available bandwidth of communications using the first wireless access protocol is below a first bandwidth threshold or an available bandwidth of communications using the wireless access point is below a second bandwidth threshold.

15. The ad hoc service provider of claim 13, wherein the wireless network comprises a server, and wherein the means for changing is configured to perform one or more of:

in response to the resource-related event, not allowing any new mobile clients to enter the wireless network;

in response to the resource-related event, supporting some or all of the one or more mobile clients to handoff to one or more other ad hoc service providers if the one or more mobile clients are existing mobile clients;

terminating the services that the ad hoc service provider is providing to some or all of the one or more mobile clients in response to the resource-related event;

changing one or more attributes of a service of the ad hoc service provider in response to the resource-related event; or

Notifying some or all of the one or more mobile clients and the server of an action in response to the resource-related event.

16. A method of providing service from a mobile node of a wireless network, the method comprising:

sending a request to allow the mobile node to provide a service as an ad hoc service provider;

detecting a resource-related event of the mobile node of a wireless network; and is

Changing the capability of the mobile node to provide service to the wireless network.

17. The method of claim 16, wherein the mobile node is configured to support a first radio access protocol, and wherein the wireless node is further configured to support a wireless access point for one or more mobile clients using a second radio access protocol.

18. The method of claim 16, wherein the transmitting a request comprises: a request is sent to allow the mobile node to provide service as an ad hoc service provider for a wireless network within a geographic location.

19. The method of claim 16, further comprising:

requesting registration of the mobile node with a server, the request including a desire of the mobile node to provide a wireless access point to one or more mobile clients,

wherein one or more mobile clients have registered with the server, and wherein the step of changing comprises: changing the ability of the mobile node to provide service to some or all of the one or more mobile clients and the server.

20. The method of claim 16, wherein the wireless network comprises the mobile node, a server, and one or more mobile clients, and wherein the step of changing comprises one or more of:

in response to detecting the resource-related event, not allowing any new mobile clients to enter the wireless network;

in response to detecting the resource-related event, initiating a handover of some or all of the one or more mobile clients of the mobile node to one or more other mobile nodes;

terminating the service being provided by the mobile node to some or all of the one or more mobile clients in response to the resource-related event;

changing one or more attributes of service of the mobile node in response to the resource-related event; or

Notifying some or all of the one or more mobile clients and the server of an action in response to the resource-related event.

21. The method of claim 16, wherein the resource-related event is one or more of: an indication that an energy level of the mobile node is below an energy threshold, an indication that a load on a processing system of the mobile node is above a load threshold, or an indication that an available bandwidth for communications using a first wireless access protocol is below a first bandwidth threshold or an available bandwidth for communications using a wireless access point is below a second bandwidth threshold.

22. A machine-readable medium comprising instructions executable by a processing system of a mobile node, the instructions comprising code for:

detecting a resource-related event of the mobile node; and is

Changing the mobile node's ability to provide services as an ad hoc service provider for the wireless network based on the detecting.

23. The machine-readable medium of claim 22, wherein the instructions further comprise: code for transmitting a request to allow the mobile node to provide service as an ad hoc service provider for the wireless network prior to detecting the resource-related event.

24. The machine-readable medium of claim 22, wherein the resource-related event is one or more of: an indication that an energy level of the mobile node is below an energy threshold, an indication that a load on a processing system of the mobile node is above a load threshold, or an indication that an available bandwidth for communications using a first wireless access protocol is below a first bandwidth threshold or an available bandwidth for communications using a wireless access point for one or more mobile clients is below a second bandwidth threshold.

25. The machine-readable medium of claim 22, wherein the wireless network comprises the mobile node, a server, and one or more mobile clients, and wherein the code for changing comprises one or more of:

code for, in response to detecting the resource-related event, disallowing any new mobile clients into the wireless network;

code for initiating a handover of some or all of the one or more mobile clients of the mobile node to one or more other mobile nodes in response to detecting the resource-related event;

code for terminating the service being provided by the mobile node to some or all of the one or more mobile clients in response to the resource-related event;

code for changing one or more attributes of a service of the mobile node in response to the resource-related event; or

Code for notifying some or all of the one or more mobile clients and the server of an action in response to the resource-related event.