Patent Application
20080137609
This application is related to and claims priority to Chinese Application No. 200610162065.1 filed Dec. 8, 2006 entitled “SYSTEMS AND METHODS FOR INCREASING MOBILITY IN FIXED WIDEBAND WIRELESS APPLICATIONS”, the disclosure of which is hereby incorporated herein by reference.
This invention relates to wireless applications and more specifically to systems and methods for increasing mobility in fixed wideband applications and even more particularly to such systems and methods for use with the 802.16e protocol.
The 802.16f management model for use in some air interface situations requires that a base station have contained therein (perhaps in a lookup table) information (such as the SS identification of the station) pertaining to all mobile stations that can be connected to that base station. Such a requirement does not work well since as mobility increases, the frequency with which a given base station is called upon to connect with stations that are not pre-known also increases. Short of providing every base station with information pertaining to every possible using station, the protocol for 802.16f is not suitable for general air interface communication, such as is desired with 802.16e equipped devices. To put it in other terms, the existing 802.16f model is not universally scalable and is thus used in a fixed situation where the base station always interacts with the same known stations and the stations always interact with the same base station.
Since the protocol assumes a fixed relationship, there is no provision for handing-off between base stations or for “roaming”. Thus, while the protocol functions well for fixed environments, it is inadequate to handle mobility of stations across base stations.
By arranging base stations in a wireless protocol with an ability to handle air interface transmissions on a class of service basis, as opposed to a specific mobile station identification basis, mobility across base stations is achieved. In one embodiment, each station is assigned a class of service and each station can connect to any base station that recognizes that station's class of service. Class of service could, for example, be based on throughput required, fees paid by the station, etc. In this manner, the base station need only know the class of service of a station and then can extend service to that station or not based on factors controlled from each base station. In one embodiment, the class of service information provided with the 802.16f protocol is used to verify the class of service of a mobile station and to update base stations. In one embodiment, the base station can share in fees paid by the station for the privilege of obtaining a certain class of service.
The foregoing has outlined rather broadly the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention. It should be appreciated by those skilled in the art that the conception and specific embodiment disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. It should also be realized by those skilled in the art that such equivalent constructions do not depart from the spirit and scope of the invention as set forth in the appended claims. The novel features which are believed to be characteristic of the invention, both as to its organization and method of operation, together with further objects and advantages will be better understood from the following description when considered in connection with the accompanying figures. It is to be expressly understood, however, that each of the figures is provided for the purpose of illustration and description only and is not intended as a definition of the limits of the present invention.
For a more complete understanding of the present invention, reference is now made to the following descriptions taken in conjunction with the accompanying drawing, in which:
Stations 14 can connect to a base station, as will be discussed, based, at least in part, on the particular station's class of service which then will be authenticated for a particular base station by that base station's authentication and communication control 11-3. Note that one or more of mobile stations 14 could connect to BS 101 again depending upon class of service and signal quality received from BS 101. Any number of base stations can thus be served by the concepts discussed with respect to
Radius server 12 is one example of a server for keeping track of class of services of the mobile stations that are attached to the network. The radius server can be accessed as needed from the base station via the radius client located at the base station. In a preferred embodiment, authentication and control 11-3 receives identity and security information from a calling mobile station and then forwards the information to the authentication server (radius server). The authentication is done by that server remote from the base station and the class of service of the calling mobile station is returned to the base station so that the base station can determine what it will do with respect to the calling mobile station based on rules contained at the base station.
After authentication, the server returns a set of parameters which the base station then uses for facilitating the air interface with the calling mobile station. The parameters include the class of service of the calling station and other common parameters, such as a master key (MSK). Based on the determined class of service of the calling station, bandwidth, for example, could be allocated.
If desired, the calling station can be informed by authentication and communication control 11-3 as to what the calling mobile station's “rights” are so that the station does not try to use features it is not entitled to with respect to this base station. In this manner, if desired, certain stations can have individual (or group) profiles valid with a select set (or one) base station.
Note that while a radius server is shown, any type of authentication can be employed, such EAP-AKA. Thus, in operation, when the subscriber station contacts the base station it identifies itself and, if required, enters a password, etc. The base station passes that information up to the authentication server. The authentication server goes through its data base routine and responds with a reject or accept message based on the parameters received from the calling station. In some systems, the parameters would map to a class of service as discussed herein. In other systems (or for some base stations) this might be a quality of service indication or some other parameter pertaining to a wide grouping of mobile stations (as opposed to an individual mobile station).
Once the base station has determined the class of service, or other parameter pertaining to permission level, the base station then uses a look-up table populated, for example, by EMS server 13. These classes are provisioned by the EMS server and are stored at the base station in a local look-up table, such as the SNMP MIB.
Some base stations may be community towers with high throughput capability and other base stations could be small private systems with limited capabilities. Thus, the actual features and/or bandwidth may be different at different base stations even for stations having the same class of service classification, if the service policy allows.
If the class of service of the calling station is not appropriate for this base station, process 310 so informs the calling mobile station and the air interface is aborted.
However, if transmission capability is available the full data transmission air interface is established (or continued) and the station, if desired, is informed via process 304 as to the services its class of service (or other access parameter) will allow at this base station and bi-directional communication can go forward using the bandwidth and other limitation appropriate to this base station and to this class of service access parameter.
Process 305 determines if a hand-off is required and/or desired by either the base station or the station. If so, process 306 contacts one or more neighbors and facilitates the hand-off, for example by passing along the determined class of service of the connected station, without again requiring a new class of service look-up. At the receiving base station the policies with respect to the station would be in accordance with the target base station's policies for this class of service and would not necessarily be the same as it was with the original base station. Process 307 optionally can upgrade or otherwise change the features given to a “transferee” based, at least in part, on the previous base station.
Note that while not necessary, operational rules can be encrypted for privacy purposes and for security of the system. The security keys and other data can then be transmitted between base stations and can thus reduce set-up time for a given session when stations are moving among different base stations. Also note that on a hand-off situation (or in any other desired situation), a receiving base station could, if it elected to do so, increase its “normal” transmission features (e.g., bandwidth) to accommodate certain stations. This accommodation can be because the receiving base station is being “nice”, or because of a prior arrangement with another base station for certain hand-offs. For example, during a voice call it might be desirable to be able to hand the call from base station to base station on an “accommodation” basis just to preserve the ability to make such voice calls.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
| Number | Date | Country | Kind |
|---|---|---|---|
| 200610162065.1 | Dec 2006 | CN | national |
