Security for a heterogeneous ad hoc mobile broadband network

Claiming priority under 35 USC 119 This patent application is tentatively entitled "METHOD FOR A HETEROGENEOUS WIRELESS AD HOC MOBILE SERVICE PROVIDER" filed on August 17, 2007, transferred to the assignee of this application and expressly incorporated herein by reference. Claim the priority of application No. 60 / 956,658.

The disclosure relates generally to telecommunications, and more specifically to ad hoc service provider configurations for broadcasting service information.

Wireless telecommunications systems are widely deployed to provide consumers with a variety of services such as telephone, data, video, audio, messaging and broadcasting. These systems continue to evolve as market factors take wireless telecommunications to new heights. Today, wireless networks provide mobile subscribers with broadband Internet access across regions, national and even global territories. Such networks are sometimes referred to as wireless wide area networks (WWANs). WWAN operators generally offer subscribers wireless access plans, such as fixed monthly subscription plans.

Not all mobile devices have access to WWAN. Some mobile devices may not have a WWAN radio. Subscription plans may not be available for other mobile devices with WWAN radios. Ad hoc networking uses protocols such as WLAN, Bluetooth®, UWB or other protocols to allow mobile devices to dynamically connect to each other via a wireless interface. Wireless access provided by users of mobile devices who do not have access to WWAN, by users with WWAN-enabled mobile devices, using wireless ad hoc networking between the mobile devices owned by the two users. There is a need in the art for ways to dynamically subscribe to services.

In one aspect of the disclosure, the ad hoc service provider includes a processing system configured to allow one or more mobile clients to access the first wireless network over the second wireless network. .. The processing system is further configured to assemble service information to be broadcast to one or more mobile clients. The service information includes attributes of access to the first wireless network provided by the ad hoc service provider to one or more mobile clients.

In another aspect of the disclosure, the ad hoc service provider includes means for allowing one or more mobile clients to access the first wireless network over the second wireless network. .. Ad hoc service providers also include means for assembling service information to be broadcast to one or more mobile clients. The service information includes attributes of access to the first wireless network provided by the ad hoc service provider to one or more mobile clients.

A further aspect of the disclosure provides service information from an ad hoc service provider configured to allow one or more mobile clients to access the first wireless network over the second wireless network. The method involves assembling service information to be broadcast to one or more mobile clients. The service information includes attributes of access to the first wireless network provided by the ad hoc service provider to one or more mobile clients.

In yet a further aspect of the disclosure, a machine-readable medium containing instructions that can be executed by a processing system within an ad hoc service provider is such that one or more mobile clients have a first over a second wireless network. Contains code to enable access to wireless networks. The instruction further contains code for assembling the service information to be broadcast to one or more mobile clients. The service information includes attributes of access to the first wireless network provided by the ad hoc service provider to one or more mobile clients.

Those skilled in the art will appreciate that other embodiments of the invention will be readily apparent from the following detailed description illustrated and illustrated by way of example various embodiments of the invention. As will be appreciated, the invention may be in other embodiments and in different embodiments, provided that it does not deviate entirely from the spirit and scope of the invention, some of which may be modified in various other ways. Is. Therefore, the drawings and detailed description should be considered exemplary in nature and not limited.

<figref num="1">A conceptual block diagram showing an example of a telecommunications system.</figref><figref num="2">A conceptual block diagram showing an example of the functionality of an ad hoc service provider.</figref><figref num="3">A conceptual block diagram showing an example of the hardware configuration of an ad hoc service provider.</figref><figref num="4">A flow chart showing an example of a method for providing service information from an ad hoc service provider.</figref><figref num="5">Conceptual block diagram of an exemplary configuration of an ad hoc service provider.</figref>

The detailed description shown below, along with the accompanying drawings, describes various configurations of the invention and does not represent the only configuration in which the invention can be practiced. The detailed description includes specific details to give a complete understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention can be practiced without these specific details. In some examples, well-known structures and components are shown in the form of block diagrams so as not to obscure the concept of the present invention.

FIG. 1 is a conceptual block diagram showing an example of a telecommunications system. Telecommunications 100 is shown with multiple WWAN 104s that provide broadband access to network 102 to mobile subscribers. The network 102 can be a packet-based network such as the Internet or some other suitable network. For clarity, two WWAN 104s are shown with a backhaul connection to network 102. However, the number of WWANs that provide broadband access to network 102 is not limited to two WWANs. Each WWAN 104 can be implemented with multiple fixed location base stations (not shown) distributed over the entire geographic area. Geographical areas can be subdivided into smaller areas, commonly known as cells. Each base station can be configured to serve all mobile subscribers in its own cell. A base station controller (not shown) can be used to manage and coordinate base stations within WWAN 104 to support backhaul connectivity to network 102.

Each WWAN104 can support wireless communication with mobile subscribers using one of many different wireless access protocols. As an example, one WWAN104 can support Evolution-Data Optimized (EV-DO) and the other WWAN104 can support Ultra Mobile Broadband (UMB). Can be done. EV-DO and UMB are air interface standards published by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards, utilizing multiple access techniques such as code division multiple access (CDMA). Provides broadband Internet access to mobile subscribers. Alternatively, one of the WWAN 104 is Long Term Evolution (LTE: Long Term). Evolution) can be supported and Long Term Evolution is within 3GPP2 to improve Universal Mobile Telecommunications System (UMTS) mobile phone standards, primarily based on wideband CDMA (W-CDMA) air interfaces. Project. One of the WWAN104s can also support the WiMAX standard developed by the WiMAX Forum. The actual wireless access protocol adopted by WWAN for a particular telecommunications system depends 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 WWAN 104 has several mobile subscribers. Each subscriber can have a mobile node that has direct access to network 102 via WWAN 104. Mobile nodes use EV-DO, UMB, or LTE wireless access protocols to access the WWAN104 shown in the telecommunications system in Figure 1, but in a practical implementation, these mobile nodes can be arbitrary. It can be configured to support wireless access protocols.

One or more mobile nodes can be configured to generate ad hoc networks in their vicinity based on the same or different wireless access protocols used to access WWAN104. As an example, a mobile node can support the UMB wireless access protocol for WWAN, but provides IEEE 802.11 access points for other mobile nodes that do not have direct access to WWAN. IEEE802.11 is a set of wireless local access network (WLAN) standards developed by the IEEE802.11 Commission for short-range communications (eg, tens to hundreds of meters). IEEE 802.11 is a popular WLAN wireless access protocol, but other suitable protocols can be used.

The mobile node used to provide an access point to another mobile node is referred to herein as an "ad hoc service provider" and is represented in FIG. 1 as service provider 106. A mobile node that uses the access point of ad hoc service provider 106 is referred to herein as a "mobile client" and is represented as client 108 in FIG. Mobile nodes, whether ad hoc service providers 106 or clients 108, are laptop computers, mobile phones, personal digital assistants (PDAs), mobile digital audio players, and mobile game consoles. , Digital cameras, digital camcorders, mobile audio devices, mobile video devices, mobile multimedia devices or other devices capable of supporting at least one wireless access protocol. it can.

Ad hoc service provider 106 can extend its wireless broadband network access service to mobile clients 108 that would otherwise not have access to network 102. Server 110 can be used as a "exchange" that allows mobile client 108 to purchase unused bandwidth from ad hoc service provider 106, for example to access network 102 over WWAN 104. it can.

The ad hoc service provider 106, the server 110, and one or more mobile clients 108 can establish a network that is an ad hoc heterogeneous wireless network. As an example, a heterogeneous wireless network can include at least two types of wireless networks (eg WWAN and WLAN). As an example, an ad hoc network can be a network in which a particular configuration changes over time or with each formation of the network. The network configuration is not pre-planned prior to establishing the network. Examples of ad hoc network configurations include configurations depending on the members in the network (for example, which ad hoc service providers, which servers, and / or which mobile clients are included in the network), ad hoc networks. There are configurations according to the geographical location of service providers and mobile clients, and configurations according to when and how long the network will be established.

For illustration purposes only, an exemplary scenario of an ad hoc network is described below. Scenario 1: While a mobile subscriber is at the airport on Tuesday at 8 am, he turns on his mobile node (for example, a laptop computer or cell phone) and ad hoc service while waiting for his flight. You can use a mobile node as a provider and establish an ad hoc network for 30 minutes. An ad hoc network can include one or more mobile clients in the vicinity (eg, other laptop computers or mobile phones). Scenario 2: At 5 pm Wednesday, while the mobile subscriber is at the hotel, he uses the same mobile node as an ad hoc service provider to form another ad hoc network for four hours and deliver that service. It can be delivered to the same mobile client, different mobile clients, or a combination of both. Scenario 3: At 5 pm on Wednesday, different ad hoc service providers can form an ad hoc network at the airport where the first ad hoc service provider was the day before. Since service providers and clients are mobile, ad hoc networks are "mobile" networks.

The server 110 may be a centralized server or a distributed server. The centralized server can be a dedicated server or can be integrated into another entity, such as a desktop or laptop computer, or a mainframe. Distributed servers can be distributed across multiple servers and / or one or more other entities such as laptops or desktop computers, or mainframes. In at least one configuration, the server 110 can be integrated into one or more ad hoc service providers in whole or in part.

In one configuration of telecommunications 100, server 110 charges mobile client 108 based on usage. For users who use mobile Internet services only occasionally, this is an attractive alternative to a fixed monthly wireless access plan. Revenues generated from royalties can be allocated to various entities within the telecommunications system 100 to help perpetuate the vitality of the exchange. As an example, a portion of the revenue can be distributed to ad hoc service providers, thereby incentives for mobile subscribers who become ad hoc service providers. Another portion of the revenue can be distributed to WWAN operators to compensate for otherwise unused bandwidth. Another portion of the revenue can be distributed to the mobile node manufacturer. The rest of the income can be set aside by the server operator that provides the exchange. How to use server 110, which is either a centralized server or a distributed server with multiple servers as shown, to transfer revenue generated from mobile client 108 to various entities within the telecommunications system 100. You can decide whether to allocate to.

Server 110 can be implemented as a trusted server. Therefore, server 110 is a public key infrastructure (PKI), for example, in a transport layer security (TLS) session between server 110 and ad hoc service provider 106, or between server 110 and mobile client 108. You can use the certificate to authenticate. Alternatively, the server 110 can authenticate using a self-signed certificate or by some other suitable means.

Regardless of how the server 110 is authenticated, a secure session channel can be established between the server 110 and the ad hoc service provider 106 or between the server 110 and the mobile client 108 during registration. In one configuration of telecommunications 100, mobile client 108 registers with server 110 to set up a username and password along with payment information. The ad hoc service provider 106 may register with server 110 to notify it that it wants to provide a wireless access point to network 102 (eg, an internet access point) to mobile client 108. it can.

Server 110 can also be used to provide admission control. Admission control is the process by which the server 110 determines whether the ad hoc service provider 106 should be able to provide services within its geographical location. Server 110 may limit the number of ad hoc service providers 106 in a given location if it determines that additional ad hoc service providers 106 will adversely affect performance within the WWAN. Depending on various network constraints, further constraints may be imposed by WWAN operators who may not want mobile subscribers to provide services at a given geographic location.

Server 110 can also be used to manage dynamic sessions established between ad hoc service provider 106 and mobile client 108. In one configuration of telecommunications 100, if the ad hoc service provider 106 is mobile and wants to provide services, the authentication, authorization, for connection with the server 110 initiated by the ad hoc service provider 106, And can use Extensible Authentication Protocol Tunnel Transport Layer Security (EAP-TTLS) for billing (AAA) and secure session establishment. EAP-TTLS can also be used for session start requests by mobile client 108. In the latter case, the mobile client 108 is the supplicant, the ad hoc service provider 106 is the certifier, and the server 110 is the authentication server. Ad hoc service provider 106 sends mobile client credentials to server 110 for EAP-AAA authentication. Then, the EAP-TTLS authentication response from the server 110 is used to generate the master shared key. A link encryption key can then be established between the ad hoc service provider 106 and the mobile client 108.

Additional security can be achieved with a Secure Sockets 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 ad hoc service provider 106 to provide mobile client 108 with improved privacy. Alternatively, the tunnel can be an IPsec tunnel or can be implemented using some other suitable tunneling protocol.

Once the tunnel is established between the server 110 and the mobile client 108, various services can be provided. As an example, server 110 can support audio or video services to mobile client 108. Server 110 can also support advertising services to mobile client 108. Other functions of the server 110 include providing the mobile client 108 with routing of content to and from the network, as well as providing the mobile client 108 with network address translation to and from the network.

Server 110 can also provide support for handoff of mobile client 108 from one ad hoc service provider 106 to another ad hoc service provider based on any number of factors. These factors 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 and link at ad hoc service provider 106. It can include state and energy level (eg, battery life).

Server 110 can also be used to store the quality criteria for each ad hoc service provider 106. The quality criteria reflect the level of service provided by ad hoc service provider 106 during a previous access session with mobile client 108. Server 110 monitors each session between ad hoc service provider 106 and mobile client 108 and updates the quality criteria associated with ad hoc service provider 106 based on one or more factors. Can be done. Factors include, but are not limited to, the duration of the access session and the average bandwidth of access to WWAN 104 provided to mobile client 108. The monitored factor is assigned a value from a range of values for each session. The quality criterion for a session can be the sum or average of these values. As the ad hoc service provider 108 provides more access sessions to the mobile client 108, the goodness criteria associated with the ad hoc service provider continue by averaging the goodness criteria from the preceding access session. Is updated. This average can be a simple average or can be weighted to emphasize more recent access sessions.

FIG. 2 is a conceptual block diagram showing an example of the functions of the ad hoc service provider 106. Ad hoc service provider 106 has the ability to bridge wireless links across homogeneous or heterogeneous wireless access protocols. This is accomplished using WWAN network interface 202, which supports a wireless access protocol to network 102 for WWAN, and WLAN network interface 204, which provides a wireless access point to mobile client 108. Can be done. As an example, WWAN network interface 202 can include transceiver functionality that supports EV-DO for Internet access over WWAN 104, and WLAN network interface 204 can access mobile client 108 with 802.11 access. It can include a transceiver function that provides points. Network interfaces 202, 204, respectively, can be configured to implement the physical layer by demodulating wireless signals and performing other radio frequency (RF) front-end processing. Network interfaces 202, 204, respectively, can also be configured to implement a data link layer by managing data transfer on the physical layer.

Ad hoc service provider 106 is shown with filtered interconnection and session monitoring module 206. Module 206 filters content from the mobile client 108 so that the interconnection between the ad hoc wireless link and the WWAN network interface 202 is provided only to the mobile client 108 authenticated by the server. I do. Module 206 is also responsible for monitoring the session between the server and the authenticated mobile client 108. Module 206 also maintains tunnel connectivity between the server and the authenticated mobile client 108.

The ad hoc service provider 106 also includes the service provider application 208, which allows the module 206 to (1) provide the ad hoc service to the mobile client 108, and (2) the ad hoc service. Support WWAN or Internet access for mobile subscribers or users of service provider 106. The latter function is supported by user interface 212, which communicates with WWAN network interface 202 via module 206, under the control of service provider application 208. The user interface 212 includes keypads, displays, speakers, microphones, joysticks, and / or other combinations of user interface devices that allow mobile subscribers or users access to WWAN 104 or network 102 (see Figure 1). Can include.

As mentioned above, the service provider application 208 also allows module 206 to provide ad hoc services to mobile client 108. Service provider application 208 maintains a session with server 110 to exchange custom messages with the server. In addition, the service provider application 208 also maintains a separate session with each mobile client 108 for exchanging custom messages between the service provider application 208 and the mobile client 108. Service provider application 208 provides information about authenticated and authorized clients to the filtered interconnect and session monitoring module 206.

Filtered interconnect and session monitoring module 206 allows content flow only to authenticated and authorized mobile clients 108. Filtered interconnect and session monitoring module 206 provides information about content flows related to mobile client 108, such as the amount of content originating from the mobile client and the amount of content arriving at the mobile client, as well as WWAN and WLAN. It also optionally monitors information about network resource utilization and bandwidth available on wireless channels. The filtered interconnect and session monitoring module 206 may optionally provide additional such information to the service provider application 208. The service provider application 208 acts voluntarily based on such information and is appropriate, such as deciding whether to continue to maintain connectivity with the mobile client 108 and the server, or to continue to provide services. Action can be taken. Implementing the functionality described with respect to module 206 and service provider application 208 on a given platform in one or more sets of modules coordinating to provide such functionality in ad hoc service provider 106. Please note that you can.

When the ad hoc service provider 106 decides to provide the ad hoc service, the service provider application 208 sends an approval request to the server 110. Service provider application 208 requires authentication by server 110 and authorization from server 110 to serve one or more mobile clients 108. The server 110 can authenticate the ad hoc service provider 106 and then decide whether to accept the ad hoc service provider's request. As mentioned earlier, the request is rejected if there are too many ad hoc service providers in the same geographic location, or if the WWAN operator imposes some restrictions on ad hoc service providers 106. There are times.

Once the ad hoc service provider 106 is authenticated, the service provider application 208 can advertise the service information to the ad hoc service provider. The service provider application 208 can also prompt changes to the advertised service information as the state changes. The mobile client 108 involved can be associated with a service set identifier (SSID) to access the ad hoc service provider 106. The service provider application 208 can then route an authentication message between the server 110 and the mobile client 108, and once authenticated, the filtered mutual to connect the mobile client 108 to the server. The connection and session monitoring module 206 can be configured. During authentication of mobile client 108, service provider application 208 can use a non-secure wireless link.

The service provider application 208 can manage the mobile client 108 in general and sessions specifically through the user interface 212. Alternatively, the service provider application 208 can support seamless operation modes with processing resources dedicated to servicing the mobile client 108. In this way, the mobile client 108 is managed in a way that is transparent to mobile subscribers. Seamless operating mode may be desirable if the mobile subscriber does not want to manage the mobile client 108, but wants to generate continuous revenue by sharing bandwidth with the mobile client 108.

Although not shown, ad hoc service provider 106 can also include server applications. The server application can be used to enable the ad hoc service provider 106 to act as a server that authenticates the mobile client 108.

FIG. 3 is a conceptual block diagram showing an example of the hardware configuration of an ad hoc service provider. Ad hoc service provider 106 is shown with WLAN transceiver 302, WWAN transceiver 304, and processing system 306. As an example, the WLAN transceiver 302 can be used to implement the analog portion of the physical layer of the WLAN network interface 202 (see Figure 2), and the WWAN transceiver 304 can be used to implement the physical layer of the WWAN network interface 204 (see Figure 2). It can be used to implement the analog part of the layer.

The processing system 306 can be used to implement the physical layer as well as the link layer digital processing portion of both the WLAN network adapter 202 and the WWAN network adapter 204 (see Figure 2). The processing system 306 can also be used to implement the filtered interconnect and session monitoring module 206 and the service provider application 208 (see Figure 2).

The processing system 306 can be implemented using software, hardware, or a combination of both. As an example, processing system 306 can be implemented using one or more processors. Processors include general purpose microprocessors, microcontrollers, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, and gates. It can be logic, individual hardware components, or other suitable entity capable of performing information calculations or other operations. The processing system 306 may also include one or more machine-readable media for storing the software. Software should be broadly understood to mean instructions, data, or a combination thereof, regardless of the names such as software, firmware, middleware, microcode, and hardware description language. The instruction can include code (eg, in source code format, binary code format, executable code format, or other suitable code format).

Machine-readable media can include storage devices integrated into the processor, as in the case of ASICs. Machine-readable media are also random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable PROM (EPROM), registers, hard disks, removable disks, CDs. -Can include storage devices external to the processor, such as ROM, DVD, or other suitable storage device. Further, the machine-readable medium can include a transmission line or a carrier wave that encodes a data signal. Those skilled in the art will recognize how best to implement the functionality described for processing system 306.

The functionality of processing system 306 for one configuration of ad hoc service provider 106 is shown below with reference to FIG. Those skilled in the art will readily appreciate that other configurations of the ad hoc service provider 106 can include a processing system 306 with the same or different functionality.

Referring to FIG. 1, the processing system within the ad hoc service provider 106 is a second wireless network in which one or more mobile clients 108 are represented by a WLAN with one or more mobile clients 108. It provides a means to enable access to the first wireless network represented by WWAN104 through an ad hoc service provider that acts as a wireless access point to the network and WLAN. The processing system has filtered interconnects and session monitoring to bridge the wireless links associated with WWAN104 and WLAN with different wireless access protocols (eg EV-DO and 802.11), as shown in Figure 2. This access can be enabled by implementing module 206 and service provider application 208.

The processing system within the ad hoc service provider 106 can function to establish a wireless access point if allowed by server 110. When the processing system decides to establish a wireless access point for one or more mobile clients 108, it sends an approval request to server 110. The processing system requires authentication by server 110 and authorization from server 110 to service one or more mobile clients 108. The server 110 can authenticate the ad hoc service provider 106 and then decide whether to accept the ad hoc service provider's request. As mentioned earlier, the request is rejected if there are too many ad hoc service providers in the same geographic location, or if the WWAN operator imposes some restrictions on ad hoc service providers 106. There are times.

When the ad hoc service provider 106 is authenticated and authorized to serve one or more mobile clients 108, the ad hoc service provider 106 becomes a mobile client 108 within the range of its WLAN transceiver 302. By assembling and broadcasting service information, its availability can be advertised to provide access to WWAN104. The service information shall include parameters for accessing the WLAN established using the ad hoc service provider 106 as a wireless access point, as well as attributes of access to the WWAN 104 provided by the ad hoc service provider 106. Can be done. The parameters of access to the WLAN are related to the ad hoc service set identifier (SSID), supported data rates, data security mechanisms, and ad hoc service providers, and mobile clients to establish wireless links. Other parameters used by 108 can be included. The SSID can be configured to include a character that identifies the ad hoc service provider 106 as a mobile node that provides access to WWAN 104.

The attributes of access to WWAN 104 provided by ad hoc service provider 106 are such that mobile client 108 provides sufficient access to WWAN 104 for ad hoc service provider 106 to meet the needs of mobile client 108. It can contain information that allows the ad hoc service provider 106 to be selected if it is acceptable to the mobile client 108. Access attributes can include the quality criteria described above associated with ad hoc service provider 106, rate of access to WWAN 104, and / or one or more service quality parameters. Service quality parameters include the expected data transfer rate of access to WWAN104, the expected duration of access to WWAN104, the latency of access to WWAN104, the frequency of access to WWAN104, and the amount of data transferred about WWAN104. Not limited to them.

The expected duration of access to WWAN104 reflects the amount of time mobile subscribers expect to make ad hoc service provider 106 available at specific geographic locations such as airport terminals, hotel lobbies, and sports venues. , User-specified time period. The expected duration of access can be communicated to server 110 when ad hoc service provider 106 is authenticated and authorized by server 110 to provide access to WWAN 104.

The expected data transfer rates for access to WWAN104 over the wireless link between ad hoc service providers 106 and WWAN104 are the wireless access protocols used within WWAN104, ad hoc service providers 106 and WWAN104. It can vary depending on the signal strength of the wireless link between and the amount of simultaneous data traffic in the WWAN 104. The ad hoc service provider 106 can be configured to monitor the average data transfer rate of access to the WWAN 104 available to the ad hoc service provider 106. Based on this average data transfer rate, the expected average data transfer rate for access to WWAN 104 available to mobile client 108 via ad hoc service provider 106 is determined.

The expected average data transfer rate for access to WWAN104 can be set as a percentage of the total available data transfer rate available to ad hoc service provider 106, or provides access through ad hoc service provider 106. It can be set to the user-specified amount by the mobile subscriber. In the alternative configuration, the server 110 can set the expected average data transfer rate when the ad hoc service provider 106 is authenticated and authorized to provide the service. Server 110 uses the information received from ad hoc service provider 106 when requested for approval and uses the expected average data transfer speed based on an agreement with the mobile subscriber that has reached the level of service provided. Can be set.

The expected duration of access to WWAN104 and the expected data transfer rate of access are dynamic attributes. For example, the expected duration of access to WWAN104 can be set when ad hoc service provider 106 is authenticated and authorized on server 110 to provide service. The expected duration reflects the amount of time that ad hoc service provider 106 has been available to provide access to mobile client 108 since ad hoc service provider 106 was authenticated and approved by server 110. Decreases. Optionally, the mobile subscriber may update the amount of time available for the mobile service subscriber 106 to provide access. After the initially set time period expires, the mobile service subscriber 106 may need to re-authenticate and request approval from the server 110 in order to continue to provide the service.

The expected data transfer rate of access to WWAN104 can also be changed while ad hoc service provider 106 is available to provide access. For example, the overall data transfer rate available to ad hoc service provider 106 can vary due to traffic changes on the WWAN 104. Similarly, the expected data transfer rate of access may be partially utilized by the first mobile client 108 if subsequent mobile client 108 seeks access to WWAN 104. The expected data transfer rate for access to WWAN104 can be changed to take these changes into account.

The latency and frequency of access to WWAN104 is related to the behavioral details of the access provided to the mobile client by the ad hoc service provider. For example, access latency and frequency are related to packet access latency, packet transmission frequency, packet transmission duration, packet length, and so on, which are available to mobile clients during a given session. Changes in these parameters change the priorities associated with the relevant access sessions available to mobile clients. Thus, the mobile client can choose the access provided by the ad hoc service provider that provides access priorities to the WWAN 104 suitable for the application used by the mobile client.

The amount of data transferred refers to the amount of data sent and / or received by a mobile client when accessing WWAN104 during an access session. The amount of data transferred indicates the maximum amount of data that a mobile client is allowed to receive and / or send over WWAN104 in a single access session. The amount of data transferred refers to bytes per session or bytes per specified time period.

The rate of access to WWAN104 is the cost per unit time incurred by mobile client 108 when accessing WWAN104 over a WLAN established by ad hoc service provider 106. The toll rate can include a range of toll rates that cover different time periods. The charge rate can also include a range of charges associated with the different combinations of service quality parameters described above. The rate for accessing the WWAN 104 can be provided by the server 110 to the ad hoc service provider 106 at the time of authentication and authorization to provide access to the WWAN 104. Alternatively, mobile subscribers can set or adjust rate rates independently of server 110.

Processing stem 306 can be used to provide a means for receiving one or more of the above attributes of access to WWAN 104 from server 110. Processing system 306 can execute code to request attributes from server 110 and / or receive attributes from server 110. These attributes can include the quality criteria associated with ad hoc service provider 106 and the rate of access to WWAN 104. The code can be implemented in a stand-alone application or part of a larger application that incorporates other features. For example, the code can run within the processing system when ad hoc service provider 106 is authenticated and authorized by server 110 to provide access to WWAN 104.

A means for using processing stem 306 to dynamically update one or more attributes of access to WWAN 104 provided by ad hoc service provider 106 based on the status of ad hoc service provider 106. Can be provided. Processing system 306 can monitor factors that affect one or more attributes and execute code to adjust the attributes based on the monitored changes in the factors. As mentioned above, such attributes can include the expected duration of access to WWAN104 and the expected data transfer rate of access. The code can be implemented in a stand-alone application or part of a larger application that incorporates other features. For example, the code can run within processing system 306 while ad hoc service provider 106 is enabled to provide access to WWAN 104.

The processing system 306 within the ad hoc service provider 106 can be configured to provide a means for assembling the service information described above, which is broadcast to one or more mobile clients 108. The above parameters and attributes can be stored in processing system 306. The processing system 306 may execute code to extract each of the parameters and attributes and assemble them into a format suitable for broadcasting to one or more mobile clients 108 using the WLAN transceiver 302. it can. For example, the driver for WLAN network interface 204 can be modified to assemble parameters and attributes into beacon frames that are later transmitted using WLAN transceiver 302.

Beacon frames are a common feature of wireless access protocols for notifying mobile nodes within a specified range of the availability of wireless network access points. Beacon frames can include fields whose content is specified by the wireless access protocol, as well as vendor-specified or user-specified fields that allow custom use. Parameters for access to the WLAN can be automatically included in the fields of the beacon frame specified by the wireless access protocol used within the WLAN. Processing stem 306 can be configured to include one or more of the attributes of access to WWAN104 in user-specified fields.

The processing stem 306 can also be configured to incorporate one or more attributes of access to WWAN104 into the parameters of access to WLAN. For example, a WLAN SSID cannot use all of the available bytes of a beacon frame. The processing stem 306 can be configured to incorporate one or more attributes of access to the WWAN 104 into the SSID of the WLAN. The number of attributes that can be included in the SSID depends on the data size of the SSID and the data size of the attributes.

When the beacon frame configuration is complete, the WLAN transceiver 302 broadcasts the beacon frame to mobile clients 108 within range of the transceiver.

FIG. 4 is a flow chart showing an example of a method for providing service information from the ad hoc service provider 106 that enables access to WWAN 104. In an implementation where the attributes are received from the server 110, in step 400, the processing system 306 of the ad hoc service provider 106 receives such attributes. In an implementation in which attributes are dynamically updated based on the status of ad hoc service provider 106, in step 401, the processing system 306 of ad hoc service provider 106 updates the attributes. At step 402, processing system 306 assembles service information, including both WLAN access parameters and WWAN 104 access attributes, into a format suitable for broadcast to one or more mobile clients 108. .. At step 403, the assembled service information is broadcast to mobile client 108 using the WLAN transceiver 302.

Upon receiving the service information broadcasted by the ad hoc service provider 106, the mobile client 108 displays the service information assembled to identify the various parameters of access to the WLAN and the attributes of access to the WWAN 104. It can be configured to parse. The parameters and attributes can be displayed within the graphical user interface on the mobile client 108 so that mobile users can view the attributes of access to WWAN 104 provided by the ad hoc service provider. Based on the broadcast attributes, the mobile user can determine if the access provided to the WWAN104 is sufficient for the mobile user's desired application. For example, mobile users can be intended to use data-intensive applications that require access for a minimum amount of time or high data transfer rates. In addition, mobile users can obtain information about the reliability of a particular ad hoc service provider 106 based on the relevant quality criteria. In addition, if multiple ad hoc service providers 106 are within the range of mobile client 108, the mobile client can be configured to display the attributes of all available ad hoc service providers 106, thereby mobile. Users can compare different ad hoc service providers and choose the one that best suits their needs.

The mobile client 108 involved in the access provided by the ad hoc service provider 106 can be associated with the broadcast SSID to access the ad hoc service provider 106. The processing system within the ad hoc service provider 106 can then use the server 110 to authenticate the mobile client 108, and then an interconnect bridge from the mobile client 108 to the WWAN link over the WLAN link. Can be set up. During authentication of mobile client 108, the processing system within ad hoc service provider 106 can use a non-secure wireless link.

Once the mobile client 108 is authenticated, the processing system within the ad hoc service provider 106 can optionally choose to move the mobile client 108 to the new SSID of the secure link. In such situations, ad hoc service provider 106 can distribute the time spent on each SSID depending on the load it must support for an existing session with mobile client 108.

The processing system can also determine if the ad hoc service provider 106 can support the mobile client 108 before allowing the mobile client 108 to access the network. Resource intelligence within the processing system that estimates the battery power and other processing resource consumption caused by accepting the mobile client 108 is that the processing system supports the new mobile client 108, or another ad hoc service. It can assist in deciding whether to consider accepting the handoff of its mobile client 108 from provider 106.

The processing system within the ad hoc service provider 106 can allow mobile clients 108 and provide them with certain QoS guarantees, such as expected average bandwidth during a session. You can monitor the average throughput provided to each mobile client 108 over a time window. Ad hoc service provider 106 ensures that resource utilization by mobile client 108 is below a certain threshold and meets the QoS requirements agreed to be provided to mobile client 108 during session establishment. To ensure, throughput can be monitored for all flows that pass through it.

The processing system within the ad hoc service provider 106 also provides a level of security to the wireless access point by making the data unbreakable and routing the data between the mobile client 108 and the server. can do. Similarly, the processing system can be configured so that the data routed between the user interface and the WWAN cannot be decrypted by the mobile client. The processing system can implement this functionality using appropriate encryption techniques.

The processing system within the ad hoc service provider 106 can also maintain a time period for the mobile client 108 to access the network. The time period is agreed between the ad hoc service provider 106 and the mobile client 108 during the start of the session. If the processing system determines that it cannot provide access to the network to mobile client 108 over the agreed time period, then the processing system is unavailable to both server 110 and mobile client 108. Notify that. This can be caused by energy constraints (eg, low battery) or other contingencies. Server 110 may then consider handing off the mobile client to another ad hoc service provider 106 if there is another ad hoc service provider 106 in the vicinity of mobile client 108. The processing system within the ad hoc service provider 106 can support the handoff of mobile client 108.

Then moving to mobile client 108, the TLS session can be used by mobile client 108 to register with server 110. Once registered, mobile client 108 can 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, the available bandwidth that the ad hoc service providers 106 can support, the ad hoc service provider 106 good criteria. You can use EAP-TTLS to initiate a session with ad hoc service provider 106 based on attributes and parameters, such as, as well as the cost of the advertised service. As mentioned above, a link encryption key can be established between the mobile client 108 and the ad hoc service provider 106 during session establishment. SSL between both mobile client 108 and server 110 so that all traffic is encrypted You can establish a VPN session. The transport layer port is open and unencrypted so that the network address translation feature is visible to the ad hoc service provider 106.

The handoff of mobile client 108 from one ad hoc service provider to another ad hoc service provider can be caused by any of several factors. The mobile client 108 handoff can be performed in a variety of ways. In one configuration, mobile client 108 can maintain a restricted session with multiple ad hoc service providers 106 while using one ad hoc service provider 106 to access the Internet. .. As mentioned above, this approach can facilitate the handoff process. In the alternative configuration, mobile client 108 considers handoffs only when needed. In this configuration, mobile client 108 can maintain an active list of ad hoc service providers 106 in its vicinity for handoffs. If the current ad hoc service provider 106 needs to suspend its service, mobile client 108 can select the ad hoc service provider 106 for handoff from the active list. If handoff is not possible, the mobile client 108 will have to reconnect through a different ad hoc service provider 106 to access the Internet.

If the bandwidth required by the mobile client 108 is greater than the capacity of the available ad hoc service provider 106, the mobile client 108 can access multiple ad hoc service providers 106 at the same time. A mobile client 108 with multiple transceivers can potentially access multiple ad hoc service providers 106 at the same time using different transceivers for each ad hoc service provider 106. Different channels can be used if the same wireless access protocol can be used to access multiple ad hoc service providers 106. If the mobile client 108 has only one transceiver available, the mobile client can distribute the time it spends accessing each ad hoc service provider 106.

FIG. 5 is a conceptual block diagram of an exemplary configuration of an ad hoc service provider. This block diagram shows an example of the functionality of the processing system 306 within the ad hoc service provider 106. Ad hoc service provider 106 is used to allow mobile clients to access the first wireless network, such as WWAN104, through a second wireless network, such as WLAN, which is supported by the ad hoc service provider. .. The ad hoc service provider can include a module 500 to allow access to the first wireless network over the second wireless network. The processing system 306 can also include a module 501 for assembling service information to be broadcast to one or more mobile clients. Processing system 306 sets modules 502 for receiving attributes of access to the first wireless network from the server, and attributes of access to the first wireless network based on the state of ad hoc service provider 106. It can include module 503 for updating.

Those skilled in the art will appreciate that the various exemplary blocks, modules, elements, components, methods, and algorithms described herein can be implemented as electronic hardware, computer software, or a combination of both. Will be done. To illustrate this compatibility of hardware and software, various exemplary blocks, modules, elements, components, methods, and algorithms have generally been described above with respect to their functionality. Whether such functionality is implemented as hardware or software depends on specific application examples and design constraints imposed on the overall system. One of ordinary skill in the art can implement the described functionality in various ways for each particular application.

It will be appreciated that the particular order or hierarchy of steps in the disclosed process is an example of an exemplary approach. It will be appreciated that a particular order or hierarchy of steps in a process can be reordered based on design preferences. The attached method claims present the elements of the various steps in an exemplary order and are not limited to the particular order or hierarchy presented.

The above description is provided to enable those skilled in the art to carry out the various aspects described herein. Various changes to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments. Therefore, the scope of claims is not limited to the aspects presented herein, but should be given the maximum scope consistent with linguistic claims, and references to singular elements should be given. Unless explicitly stated so, it does not mean "only one", but "one or more". Unless otherwise stated, the word "several" stands for "one or more." Male pronouns (eg, he) include feminine and neuter (eg, she and it) and vice versa. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure, known to those of skill in the art, or will become known later, are expressly incorporated herein by reference. It is included in the scope of claims. Moreover, nothing disclosed herein is made publicly available, whether or not such disclosure is explicitly stated in the claims. Any claim element is specified using the phrase "step" unless the element is explicitly stated using the phrase "means" or, in the case of a method claim, the element is expressed using the phrase "step". Unless it is not, it should not be construed under the provisions of 35 USC 112, paragraph 6.