Abstract:
Apparatus, and an associated method, for requesting, and allocating communication resources at a new fixed-site transceiver of a radio communication system, such as a new access point of a wireless local area network. A resource information container is formed that is structured to include information elements that identify, amongst other things, resource requirements of a mobile unit. The information elements of a resource information container include a root node, one or more leaf nodes, and, selectably, one or more group nodes. The resource information container is communicated prior to commencement of transition procedures to early-reserve or determine availability of resources at a new access point.

Description:
RELATED APPLICATION DATA  
       [0001]     This patent application claims the benefit of provisional U.S. Patent Application Ser. No. 60/609,943, filed Sep. 15, 2004, and provisional U.S. Patent Application Ser. No. 60/609,944, filed Sep. 15, 2004. 
     
    
     FIELD OF THE INVENTION  
       [0002]     The present invention relates to network technologies and, more particularly, to mechanisms for facilitating transition of mobile unit communications between network stations of a radio communication system. Still more particularly, the present invention relates to an apparatus, method, and computer-readable medium for generating, and making use of, a resource information container or data structure that identifies resources that are needed, or desired, to be available to the mobile unit upon transition to a new network station in a radio communication system such as a Wireless Local Area Network (WLAN).  
       BACKGROUND  
       [0003]     Advancements in communication technologies have resulted in the development, and subsequent deployment, of many varied types of communication systems. Communication systems are used to communicate data pursuant to any of many different types of communication services. A communication system is formed by a set of communication stations between which data is communicated. At least one of the communication stations of the set forms a sending station and at least another of the communication stations of the set forms a receiving station. The sending and receiving stations are interconnected by way of a communication channel, and the data communicated by the sending station is delivered to the receiving station by way of the communication channel.  
         [0004]     A radio communication system is a type of communication system in which the communication channel that interconnects the communication stations and upon which data is communicated is formed of a radio channel. A radio channel is defined upon a radio link that comprises a portion of the electromagnetic spectrum. When radio channels are used to communicate data between communication stations, the communication stations need not be interconnected by wireline, i.e., fixed, connections. As the positioning of the communication stations of a radio communication system does not depend upon the availability of wireline connections to interconnect the communication stations, the communication stations are positionable at locations, and in manners, that would not be possible in a wireline communication system. Communications are possible, therefore, through the use of a radio communication system at, and between, locations at which wireline communication stations could not be positioned and used. Additionally, a radio communication system is implementable as a mobile communication system in which one, or more, of the communication stations between which data is communicated is provided with communication mobility.  
         [0005]     A cellular communication system is an exemplary type of mobile radio communication system. In a cellular communication system, a network infrastructure is installed throughout a geographical area throughout which communications are to be permitted. The network infrastructure includes, typically, a plurality of spaced-apart, fixed-site transceivers, each of which defines a cell. The positioning of the fixed-site transceivers is selected, generally, so that the cells partially overlap in manners so that, collectively, the cells encompass the entire geographical area. Radio transceivers, typically both portable and mobile, are used to communicate with the fixed-site transceivers. The portable transceivers generally communicate with the fixed-site transceiver in whose cell that the portable transceiver is positioned. As a portable transceiver travels between cells defined by different fixed-site transceivers, a communication handoff is performed to permit continued communications of, and with, the portable transceiver.  
         [0006]     Other types of radio communication systems have been developed and deployed that exhibit some of the characteristics of cellular communication systems. Wireless local area networks (WLANs), for example, exhibit some of the characteristics of cellular communication systems. A wireless local area network includes a network part, also typically including a plurality of transceivers that each define cells, or coverage areas otherwise-defined. A transceiver, also referred to herein as a mobile station (STA) and mobile unit (MU), operable in a wireless local area network communicates with a network part transceiver in whose coverage area the STA is positioned. Hand-offs of communication between successive network part transceivers permits continued communications as the STA moves between coverage areas defined by different network part transceivers.  
         [0007]     In a communication hand-off, herein also referred to as a communication transition, it is desirable that the hand-off, or transition, between network part transceivers is carried out quickly to minimize communication service interruptions during the communication hand-off. However, various signaling is required pursuant to the transition.  
         [0008]     Additionally, as data communication services that are performed are increasingly data-intensive and involve communication of more than one data type and more than one communication service, radio resource reservation of radio resources at the fixed-site transceiver to which the communications are to be handed off are needed. A reservation request may sometimes comprise a multiple number of requests, both for different types of communication data as well as alternate requests in the event that first requests are for reservations that can not be made. The complexity of the requests, when made during transition of communications, is time-consumptive and is contrary to the goal of minimizing communications service interruption during transition of communications.  
         [0009]     Conventional communication transition mechanisms disadvantageously require a mobile unit to complete a transition prior to determining whether sufficient resources are available at a fixed station to service the mobile unit. A scheme for efficient pre-allocation of communication resources prior to transition of communications is therefore needed.  
       SUMMARY  
       [0010]     Embodiments of the present invention advantageously provide an apparatus, associated method, and computer-readable medium to facilitate quick transition of communications of a mobile unit between network stations of a radio communication system, such as a WLAN operable to a variant of an IEEE 802 operating specification.  
         [0011]     Mechanisms are provided for generating, and making use of, a resource information container or data structure that identifies resources that are needed, or desired, to be available to a mobile unit upon transition of the mobile unit to a new network station.  
         [0012]     The resource information container is formed of a desired number of information elements, formatted in a structured manner. Certain of the information elements identify resources desired, or needed, to be available to the mobile unit pursuant to one or more communication services performed, or anticipated to be performed, by, or with, the mobile unit. The resource information container is sent by the mobile unit prior to transition of communications of the mobile unit to a new network station. Because the resource information container that identifies the requested, or mandated, resources is sent by the mobile unit prior to invocation of transition procedures, the need to identify, during the actual performance of the transition procedures, the same information is obviated. Transition of communications to the new network station is able to be carried out, thereby, more quickly than would otherwise be conventionally permitted. Problems with communication service interruption during transition of communications to a new network station are reduced or alleviated by reducing the time period required to carry out the transition procedures.  
         [0013]     In one aspect of the present invention, the resource information container is sent by the mobile unit to a network station with which the mobile unit is in communication. The network station forwards the resource information container, or at least indications thereof, to one or more potential network stations to which communications may potentially be transitioned.  
         [0014]     Once the resource information container is delivered to a potential transition network station, the potential transition network station detects the contents of the resource information container and the resource requirements or requests set forth therein. The potential transition network station to which the container is routed determines the availability of the requested resources and forms a reply that identifies at least whether the requested resources are available at that network station. In the event that the potential transition network station has the requested resources available (or a portion thereof), the potential transition network station may selectably reserve the requested resources for the mobile unit, and the reservation of the resources may be identifiable in a response generated by the potential transition network station.  
         [0015]     As the resource information container potentially includes a plurality of information elements, each identifying a resource request, the network station to which the container is routed potentially is formed of a plurality of request answers or responses. For instance, the communication service, in one implementation, is effectuated by communication of data at a service quality (QoS) level. The mobile unit requests communication resources to carry out the communication service at an optimal QoS level and, in the alternative, one or more degraded or alternative QoS levels. The network station, in its response, identifies the resources available, or reservable, to comply with the alternative requested levels of service. That is to say, while the optimal QoS level resources may not be available, the network station might have resources to meet an acceptable, degraded service quality level at which to carry out the communication service.  
         [0016]     In another aspect of the present invention, a respective response generated by one or more potential transition network stations, once returned to the mobile unit, indicates to the mobile unit whether the potential transition network station has resources available or reservable for the communication service, or services, that is or are to be carried out. In the event that a potential transition network station does not have the resources desired, or needed, by the mobile unit, the mobile unit is able to elect not to transition to the potential transition network station that does not have the resources available, or reservable, that were requested by the mobile unit.  
         [0017]     Also through the early sending of the resource information container to a potential transition network station, the resources required by the mobile unit pursuant to a particular communication service are quickly identified through the sending of an identifier that is indexable against the earlier-sent resource information container when subsequent transition procedures are carried out. The requested resource is thereby simply and quickly identifiable to the potential transition network station, and the time delays associated with the transition procedure are little affected.  
         [0018]     The resource information container, formed of one or more information elements, may comprise a hierarchical data structure that is associated with resource requirements of communication services performable by, and with, the mobile unit. An information element indicates either a resource requirement or a link to other resource requirements. In an exemplary implementation, the resource information container is formed of descriptors that together define a resource request message and is structured as a tree in which branches of the tree form links and the end points, or leaves, contain resource requests. That is, the resource request message or resource information container, is formed of a number of subcomponents wherein each subcomponent has a substantially common structure. The resource request message is formed of, selectably, one or more subcomponents. In the exemplary implementation, the resource request message is formed of subcomponents that comport with an IEEE 802.11 information element data structure.  
         [0019]     When implemented in a WLAN that operates in conformity with a variant of an IEEE 802 operating specification, the mobile unit, sometimes referred to as a mobile unit (MU), communicates with fixed-site access points (APs). Prior to initiation of transition procedures, the mobile unit forms a resource information container and sends the container, so-formed, to the access point with which the mobile unit is in communication connectivity. The access point with which the mobile unit is in communication, forwards the container, or indications thereof, to a potential transition access point to which communications may potentially be transitioned.  
         [0020]     The potential transition access point detects the contents of the container and determines whether resources are available at the potential transition access point corresponding to the request set forth in the resource information container. The potential transition access point may selectably reserve the requested resources for the mobile unit. The potential transition access point may form a response accepting, or denying, the request and selectably further identifying reservation of the resources if the reservations have been made.  
         [0021]     The mobile unit may subsequently select (or may be instructed to) transition to the potential transition access point. Pursuant to the subsequent transition procedure, the resource requested by the mobile unit, e.g., a single one of the information elements contained in the earlier-sent resource information container, is identified by an indexable value. The transition procedures are little affected as the resource allocation request is identified by minimal indicia and service negotiation is not generally required. Transition procedures are thereby expedited, service interruptions are less likely to occur, and improved communication performance results relative to conventional procedures.  
         [0022]     In these and other aspects, therefore, an apparatus, an associated method, and a computer-readable medium is provided for a mobile unit to facilitate transition of communications thereof pursuant to a communication service to a transition network station. A message generator is embodied at the mobile unit. The message generator is adapted to receive indications of resource requirements required of the mobile unit pursuant to the communication service. The message generator generates a resource information container including a first information element. The first information element is formatted to include a value associated with a first resource requirement associated with the communication service. The resource information container is generated prior to transition of the communications to a transition network station.  
         [0023]     A more complete appreciation of the present invention and the scope thereof can be obtained from the accompanying drawings, the following detailed description of presently-preferred embodiments of the present invention, and the appended claims. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0024]     Aspects of the present disclosure are best understood from the following detailed description when read with the accompanying figures.  
         [0025]      FIG. 1  is a simplified block diagram of an exemplary network system in which embodiments disclosed herein may be implemented for advantage;  
         [0026]      FIG. 2A  illustrates a message sequence diagram representative of an embodiment of signaling generated during operation of the communication system shown in  FIG. 1 ;  
         [0027]      FIG. 2B  illustrates a message sequence diagram representative of another embodiment of signaling generated during operation of the communication system shown in  FIG. 1 ;  
         [0028]      FIG. 3  illustrates an embodiment of a resource information container of a minimal construction;  
         [0029]      FIG. 4  illustrates another exemplary embodiment of a resource information container;  
         [0030]      FIG. 5  illustrates another exemplary embodiment of a resource information container;  
         [0031]      FIG. 6  illustrates another exemplary embodiment of a resource information container that illustrates the ordering of nodes in a multiple-node arrangement;  
         [0032]      FIG. 7  illustrates another embodiment of a resource information container;  
         [0033]      FIG. 8  illustrates another embodiment of a resource information container that provides resource choices or options to a target fast BSS transition enabled access point;  
         [0034]      FIG. 9A  illustrates an embodiment of a resource information container root information element shown in  FIGS. 7 and 8 ;  
         [0035]      FIG. 9B  illustrates an embodiment of a resource information container data information element; and  
         [0036]      FIG. 9C  illustrates an embodiment of a control options field of a resource information container data information element. 
     
    
     DETAILED DESCRIPTION  
       [0037]     It is to be understood that the following disclosure provides many different embodiments, or examples, for implementing different features of various embodiments. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.  
         [0038]      FIG. 1  is a simplified block diagram of an exemplary network system  100  in which embodiments disclosed herein may be implemented for advantage. System  100  is an example of a shared resource network, such as a wireless local area network (WLAN) conforming to an IEEE 802.11 standards variant.  
         [0039]     In the illustrative example, system  100  comprises two basic service sets (BSSs)  10  and  11  although any number of BSSs may be included in system  100 . BSSs  10  and  11  provide respective coverage areas, or cells, in which WLAN stations (STAs), such as mobile STA  20 , may communicate via a wireless medium with one another or with other communication or computational devices in other external networks that interface with system  100 . BSSs  10  and  11  are communicatively interconnected by a distribution system (DS)  30 . DS  30  enables mobile device support by providing requisite logical services for handling address to destination mapping and integration of multiple BSSs. Each of BSSs  10  and  11  include a respective access point (AP)  40  and  41  that provides access to DS  30 . DS  30  provided by BSSs  10  and  11  and APs  40  and  41  facilitate creation of a wireless network of arbitrary size and complexity, and the collection of BSSs  10 - 11  and DS  30  is commonly referred to as an extended service set network. Logical integration between system  100  and non-IEEE 802.11 LANs, e.g., LAN  50 , may be provided by a portal  60 . Various other configurations of network  100  are possible. For example, BSSs  10  and  11  may partially overlap or may be collocated. Each of BSSs  10  and  11  are assigned a respective basic service set identifier (BSSID) that uniquely identifies BSSs  10  and  11  within system  100 .  
         [0040]     System  100  provides for communication transitions of communications by, and with, a STA between access points, such as when a mobile station travels between overlapping coverage areas of different ones of the access points. Communication transitions are sometimes further effectuated for other reasons to facilitate communication operations in a network. Pursuant to communication transitions, various signaling operations are performed and various decisions must be made to perform a transition. The transition process sometimes consumes hundreds of milliseconds of time. During the transition procedure, communication interruptions or data loss may occur, deleteriously effecting communications pursuant to a communication session of the mobile station. The present invention provides mechanisms for a fast transition between APs. APs adapted to carry out fast transitions in accordance with embodiments described herein are referred to as fast BSS transition enabled access points (TAPs), and mobile stations adapted to carry out fast transitions in accordance with embodiments described herein are referred to as transition enabled-enabled stations (TSTAs), or simply stations (STAs).  
         [0041]     For a successful transition to occur from one AP to another AP, it is preferable that the transition access point has sufficient communication resources available to permit continued communications pursuant to the data communication service, or a desired data communication service. A request for allocation of communication resources can be time-consuming, requiring service negotiation for various quality of service (QoS) levels. An embodiment of the present invention advantageously provides a mechanism to facilitate pre-reservation of communication resources at a transition access point or, at the least, provide indications prior to the transition procedures of whether resources are available at a prospective transition access point. In the event that resources are not available at an AP, further decisions can be made as to whether to transition to the access point, to investigate the possibility of transitioning to another access point, or foregoing transition, if possible.  
         [0042]     Pursuant to an embodiment of the present invention, therefore, the mobile station includes a module  36  of an embodiment of the present invention. Module  36  is functionally represented, formed of functional entities comprising software, hardware, or a combination thereof, implementable in any desired manner including, for instance, through implementation by algorithms executable by processing circuitry or ASIC implementation. The module  36  may be communicatively coupled to a transceiver  38  of the mobile station.  
         [0043]     Module  36  includes a resource information message generator that operates to generate a resource request message comprising a resource information container (RIC) or descriptor. A RIC provides a mechanism for the STA to generate resource requests that may include mandatory and optional resources. A RIC that comprises a resource request issued by a STA may comprise a plurality of information elements (IEs), such as a RIC root IE (RRIE) and RIC data IEs (RDIEs). A response to a RIC resource request may comprise a RIC issued by the target TAP and may comprise response IEs. The contents of the RIC that forms the resource request message are created responsive to input indicia. The input indicia may originate, for instance, at transceiver  38 , a data source (not shown), or responsive to user selection. Details of exemplary formats of the RIC are described hereinbelow. Once generated, the RIC is provided to a transmit portion of transceiver  38  for communication upon a radio channel defined upon a radio link  46  for delivery to the network part of system  100 ′ with which the mobile station is in communication connectivity. In one implementation, the receiving access point (also referred to herein as a current access point) with which the mobile station is currently registered forwards the RIC to a prospective, or target, TAP to which communications are prospectively to be transitioned. In this implementation, the RIC may be communicated from the current TAP to the target TAP by way of the DS. In another implementation, the mobile station communicates the resource information container directly to the target TAP by way of an over-the-air interface.  
         [0044]     One or more of APs  40  and  41  may include respective modules  48   a - 48   b  implemented according to an embodiment of the present invention. Modules  48   a - 48   b  are functionally represented, implementable in any desired manner, including software and hardware implementations, or combinations thereof. While each module  48   a - 48   b  in the exemplary implementation is embodied at an access point, in other embodiments, modules  48   a - 48   b  may be located elsewhere, such as at a central control unit (not shown) or distributed in functionality between an access point and other network entities.  
         [0045]     Each of modules  48   a - 48   b  may include a message detector that operates to detect the values of the RIC of the message communicated thereto. Values of the detected RIC are provided to a confirmer routine of the module that determines whether requested resources specified in the RIC, are available and to confirm, if available, what resources are available. The confirmer routine may further, if appropriate, confirm reservation of the requested resources and form a response for return to the mobile station. A response provided to a mobile station from a target TAP may be made by way of the DS or directly to the STA by way of an over-the-air interface. The response may also be structured as a RIC.  
         [0046]     The module  36  of the mobile station may further include a detector routine for detecting a response returned to the mobile station and a committer routine. The committer routine commits the mobile station to use the resources confirmed to be available by a target TAP. The commitment may also be structured as a RIC. Through the generation and communication of the RIC prior to the commencement of transition procedures, delays that are otherwise associated with the request for allocation of resources during the transition procedures are avoided. Accordingly, smaller amounts of transition time delays result and improved communications are possible.  
         [0047]     As referred to herein, a current TAP is an access point with which the mobile station is currently registered and with which the mobile station has communication connectivity. A target TAP, as referred to herein, is an access point to which communications are prospectively to be transitioned. In the illustrative example, AP  40  comprise a current TAP of STA  20 , and AP  41  may comprise a target TAP for STA  20 . Any access point may be capable, with respect to a mobile station at a particular position, to be a current TAP and a target TAP. Additionally, a target TAP to which communications are transitioned can be an access point of the same network in which the current access point is located. In other scenarios, a target TAP may be located in another network. The target TAP alternately could be an access point of another network system. In the exemplary embodiment, when the current TAP and target TAP are both operable in networks using the operating protocols of a variant of an IEEE 802.11 operating specification, the message in which the RIC is formed, as well as the confirmation and commitment message are formed, may comprise layer  2  messages, e.g., MAC (Medium Access Control) layer messages.  
         [0048]     BSS transition mechanisms for a STA described herein provide methods to reserve resources at a target TAP prior to invocation of transition procedures or at a time when the STA invokes re-association procedures. The STA may communicate directly with the target TAP by an over-the-air interface terminated at the STA and the target TAP, the STA may reserve resources through communications with its current TAP by way of the DS. The resource allocation mechanisms described herein may be used to allocate any type of resources, such as a traffic specifier (TSPEC) that specifies a particular bandwidth request in a QoS environment, keying material in a secure environment, or other reservable resources.  
         [0049]     While the descriptions of a shared resource network, devices operating therein, and wireless medium transmissions made within the shared resource network are provided herein according to IEEE 802.11 protocols, functionality, and nomenclature, such examples are illustrative only and implementations of the invention are not limited to any particular network, network-compliant device, or network communication formats or protocols. Furthermore, descriptions of the invention provided herein in relation to implementations in an IEEE 802 conformant network are illustrative only and are provided only to facilitate an understanding of the invention. Embodiments of the present invention may be implemented on other network architectures and devices that utilize shared resources for effecting data communications.  
         [0050]      FIG. 2A  illustrates a message sequence diagram  112   a  representative of an embodiment of signaling generated during operation of the communication system  100  shown in  FIG. 1 . The signaling is representative of messages generated and communicated between mobile station  20  and target TAP  41 . In the illustrative example, signaling exchanged between mobile station  20  and target TAP  41  are made by way of current TAP  40 , that is by way of a DS  30  message exchange mechanism.  
         [0051]     First, at the mobile station, a resource information container specifying a resource request is generated (step  111 ). Then, a resource request message containing the resource information container is sent from mobile station  20  by way of a radio air interface extending to the current TAP  40  (step  114   a ). Current TAP  40  routes the message containing the resource information container to target TAP  41  (step  118   a ). Once delivered to target TAP  41 , the values of the resource information container are detected (step  122 ), and the RIC (or contents thereof) may be stored by target TAP  41  (step  123 ). A determination is made (step  124 ) of whether the resources are available at target TAP  41  to comply with one or more of the requests contained in the resource information container. If the resources are available for allocation, the target TAP may then optionally allocate the resources for a pre-defined interval or duration (step  125 ). A confirmation message or resource response is generated (step  126 ). The confirmation message may specify that none of the requested resources are available, some of the requested resources are available, or all of the requested resources are available. Additionally, the confirmation message may indicate that the available resources have been pre-allocated. In other implementations, the confirmation message may indicate that some or all of the resources are available but are not pre-allocated by the target transition AP. The confirmation message may include a delay interval that specifies an amount of time the requested resources will be reserved for the STA to invoke a reassociation procedure. The confirmation message is then returned (step  128   a ) to the mobile station by way of current TAP  40 . The confirmation message may also be structured as a resource information container. Once delivered to the mobile station, a determination is made (step  132 ) whether to commit to the allocated resources, if any, indicated in the confirmation message. A commitment message is generated and forwarded (step  134   a ) to target TAP  41  by way of current TAP  40  to indicate whether the mobile station is committing to use of the available resources. The commitment message may also comprise a resource information container and may be included in a reassociation request. The commitment message may comprise an index to the RIC transmitted to TAP  41  in steps  114   a  and  118   a  such that TAP  41  is informed of the commitment and is able to identify an association between the request and the commitment. The index to the original request may, for example, comprise a sequence number or other identifier of the RIC or one or more index numbers or identifier of one or more information elements of the RIC included in the resource request transmitted to AP  41  in steps  114   a  and  118   a  in  FIG. 2A  (or step  114   b  in  FIG. 2B ).  
         [0052]      FIG. 2B  illustrates a message sequence diagram  112   b  representative of an embodiment of signaling generated during operation of the communication system  100  shown in  FIG. 1 . The signaling is representative of messages generated and communicated between mobile station  20  and target TAP  41 . In the illustrative example, signaling exchanged between mobile station  20  and target TAP  41  are made by way of an over-the-air interface directly between STA  20  and target TAP  41 .  
         [0053]     First, at the mobile station, a resource information container specifying a resource request is generated (step  111 ). Then, a resource request message containing the resource information container is sent from mobile station  20  by way of a radio air interface extending to the target TAP  40  (step  114   b ). Once delivered to target TAP  41 , the values of the resource information container are detected (step  122 ), and the RIC (or contents thereof) may be stored by target TAP  41  (step  123 ). A determination is made (step  124 ) of whether the resources are available at target TAP  41  to comply with one or more of the requests contained in the resource information container. A confirmation message or resource response is generated (step  126 ). The confirmation message may specify that none of the requested resources are available, some of the requested resources are available, or all of the requested resources are available. Additionally, the confirmation message may indicate that the available resources have been pre-allocated. In other implementations, the confirmation message may indicate that some or all of the resources are available but are not pre-allocated by the target transition AP. The confirmation message may include a delay interval that specifies an amount of time the requested resources will be reserved for the STA to invoke a reassociation procedure. The confirmation message is then and returned (step  128   b ) to the mobile station by way of a radio link between STA  20  and target TAP  41 . The confirmation message may also be structured as a resource information container and may include a delay interval that specifies an amount of time the requested resources will be reserved for the STA to invoke a reassociation procedure. Once delivered to the mobile station, a determination is made (step  132 ) whether to commit to the allocated resources, if any, indicated in the confirmation message. A commitment message is generated and transmitted (step  134   b ) to target TAP  41  to indicate whether the mobile station is committing to use of the available resources. The commitment message transmitted in step  134   b  may be included in a reassociation request message. The commitment message may comprise an index to the RIC transmitted to TAP  41  in step  114   b  such that TAP  41  is informed of the commitment and is able to identify an association between the request and the commitment. The index to the original request may, for example, comprise a sequence number or other identifier of the RIC included in the request.  
         [0054]     In general, therefore, a 3-step, resource pre-establishment procedure is set forth. The first step comprises a notification step in which the target TAP is informed of the mobile station&#39;s resource requirements. Then, a step of confirmation is performed to obtain confirmation of resource availability of the target TAP. A subsequent commitment step is performed at which confirmation is made that the resources shall be used by the mobile station. The notification of the target TAP of the mobile station&#39;s requirements occurs prior to the transition procedure. That is to say, in this phase, the mobile station submits a request message to the target TAP that includes an address referenced to a current access point, e.g., an address contact point, and a list of desired resources. In response, the access point responds with, e.g., either an immediate result, for instance, within a small period of time such as 10 ms, or a defer indication together with a suggested delay period.  
         [0055]     The step of the resource confirmation (step  128   a  and  128   b ) also occurs prior to the transition procedure. This step occurs only subsequent to a preceding notification step for which a defer indication is provided by the access point. During the confirm step, the target TAP indicates whether the target TAP is able to provide the requested resources. The access point indicates the minimum time in time units (TUs) that the access point shall retain the resources and the mobile station indicates whether the mobile station wants the access point to continue to reserve the resources (in the commitment message transmitted to the target TAP). The step of confirming (in the resource response) is repeated, if desired, prior to the commit step to allow the mobile station to have resources reserved therefore to be released. This capability is desirable, for example, if the mobile station decides not to complete the communication transition.  
         [0056]     The step of committing, e.g., in a reassociation request message, occurs during the transition procedure. Success in the commit phase occurs substantially concurrently that the transition with the target TAP is completed. If the commit is not successful, the target TAP terminates the transition procedure with a failure response to enable the mobile station to resume communications with the current AP.  
         [0057]     The steps of notifying, and committing are carried out through the communication of resource information containers (RICs). The resource information container includes a series of information elements, also referred to as resource nodes or subcomponents. Each of the information elements (IEs), as shall also be described below, have similar structures.  
         [0058]     A general resource information container is defined to be part of a TAP and permits a mobile station and an access point to establish resources prior to a transition. The resource information container is formatted in a manner to permit its efficient use when generating small-length resource requests, such as for a single TSPEC, but also flexible so that multiple numbers of resources can also be requested in a single message formed of a resource information container. The ability to combine together multiple requests reduces signaling overhead and assists in the rapid pre-allocation of resources. The subcomponents of a resource information container are the nodes, noted briefly above.  
         [0059]     Each of the resource IEs of the resource information container forms an information element. Or, in other words, each information element contains a single node of the resource information container. In an exemplary implementation, one type of leaf node is defined to carry QoS (Quality of Service) context. Thereby, the resource information container contains a list of required resources determined by the mobile station. In one embodiment, the list of resources formed of the resource information container is validated by the current access point prior to allocation by the target TAP. Appropriate structure is maintained at the current access point to perform such validations. In other implementations, the resource information container is transmitted directly from the mobile station to the target TAP. Accordingly, the target TAP performs the validations in such an implementation.  
         [0060]     The information elements of the resource information container are concatenated in a specific order. In some embodiments, the information elements may comprise IEs of a root E type, a group E type, and a resource E type. In other implementations, information elements may comprises IEs of a root IE type and a data IE type. A resource information container may include only one root node. A resource information container may include any number of group nodes, e.g., no group nodes, one group nodes, or several group nodes, each indicating a connected set of resources and may include any number of data IEs. Additionally, each leaf node may contain a single resource description, such as a TSPEC.  
         [0061]      FIG. 3  illustrates an embodiment of a resource information container  222  of a minimal construction. RIC  222  includes, in a minimal construction, a RIC root E (RRIE)  224  and at least one leaf node comprising a resource E  226 . Each resource IE  226  contains a resource descriptor, such as a TSPEC. RRIE  224  may provide the identity of the access point with which the mobile station is in communication connectivity, that is an identity of the current TAP, and may also indicate the number of leaf nodes or resource IEs present in resource information container  222 .  
         [0062]      FIG. 4  illustrates another exemplary embodiment of a resource information container  228 . Here, the resource information container again includes an RRIE  229 . Multiple leaf nodes comprising resource IEs  226   a - 226   d  are included as parts of resource information container  228 . Each leaf node forms a resource request, and successive leaf nodes are concatenated to RRIE  229 .  
         [0063]      FIG. 5  illustrates another exemplary embodiment of a resource information container  232 . Again, an RRIE  233  is positioned at the head of resource information container  232 . Here, RIC  232  also includes a group IE  234  and a series of leaf nodes each comprising respective resource IEs  236   a - 236   d . Group IE  234  is used to indicate which of the leaf nodes positioned thereafter are related, e.g., thereby to permit treatment of the whole group together for resource allocation purposes. In the illustrative example, group IE  234  in  FIG. 5  links resource IEs  236   a - 236   c . For example, group E  234  may include identifiers associated with respective resource IEs  236   a - 236   c . The fourth resource E  236   d  is not part of the group identified by group E  234 .  
         [0064]      FIG. 6  illustrates another exemplary embodiment of a resource information container  242  that illustrates the ordering of nodes in a multiple-node arrangement. Again, resource information container  242  includes an RRIE  243 . In this example, resource information container  242  includes a plurality of group node information elements  244   a - 244   n  and another plurality of resource IEs  246   a - 246   x . Each of resource IEs  246   a - 246   x  may respectively include a sequential index number or sequence number (SN)  247   a - 247   x , e.g., starting at one and incrementing by one. Groups of the resource IEs, defined by group IEs  244   a - 244   n , may be defined as a contiguous subset defined by the lowest and highest sequence or index number in the group. In one embodiment, group definitions do not overlap.  
         [0065]     When the resource information container is set as part of a resource information container confirmation, the resource information container need have only a partially populated content. This limits returned results of a successful allocation of a group by indicating confirmation or success of the group node without providing an individual confirmation of all subordinate resource IEs in the group. The confirmation message thereby need only be of abbreviated length.  
         [0066]      FIG. 7  illustrates another embodiment of a resource information container  250   a . RIC  250   a  may comprise a RIC root information element (RRIE)  251 , and one or more RIC data IE (RDIE) and resource IE pairs. In the illustrative example, RIC  250   a  includes two RDIE and resource IE pairs, namely RDIE  252   a  and associated resource IE  253   a  and RDIE  252   b  and associated resource IE  253   b . Thus, RIC  250   a  comprises two RDIEs each having a single resource request.  
         [0067]      FIG. 8  illustrates another embodiment of a resource information container  250   b  that provides resource choices or options to the target TAP. RIC  250   b  comprises RRIE  251  followed by a single RDIE  252   c . Multiple resource requests are defined by resource IEs  253   a  and  253   b . In this configuration, a target TAP receiving RIC  250   b  may attempt to allocate the first resource specified in resource IE  253   a . If this allocation fails, the target TAP may then attempt to allocate the resource specified in resource IE  253   b . Any number of resource IEs may be appended to RDIE  252   c . The present example of two resource IEs is illustrative only.  
         [0068]      FIG. 9A  illustrates an embodiment of RIC root IE (RRIE)  251  shown in  FIGS. 7 and 8 . RRIE  251  comprises an element ID field  260 , a length field  261 , an RRIE ID field  262 , a count of RDIEs field  263  and a target BSSID field  264 . Element ID field  260  contains an identifier that specifies information element  251  as a RIC root. Length field  261  may contain a value that specifies the length, e.g., the number of octets, of E  251  that follow length field  261 . RRIE ID field  262  may contain a unique identifier that allows responses to the resource request comprising the RIC to be matched thereto. Count of RDIEs field  263  contains a numerical identifier of the RDIEs contained in the RIC. For example, in the illustrative example, count of RDIEs field  263  would contain a numerical identifier of “2” if RRIE  251  is the RIC root IE of RIC  250   a . Target BSSID includes the BSSID of the target AP to which the RIC is to be sent.  
         [0069]      FIG. 9B  illustrates an embodiment of a RIC data information element  252 , such as RDIE  252   b  shown in  FIG. 7 . RDIE  252  comprises an element ID field  270 , a length field  271 , a sequence number field  272 , and a control options field  273 . Element ID field  270  includes an identifier that specifies information element  252  is a RIC data information element. Length field  271  may contain a value that specifies a length of the information element, e.g., the number of octets that follow length field  271 . Sequence number field  272  includes a unique sequence number or index value within the RIC that is selected by the originating STA. For example, sequence numbers may be incrementally assigned (starting from a particular value, such as “1”) to each RDIE of a RIC.  
         [0070]     Control options field  273  may include various values that facilitate processing of the RDIE by a target TAP.  FIG. 9C  illustrates an embodiment of control options field  273  of an RDIE shown in  FIG. 9B . Control options field  273  may include mandatory field  273   a , confirm field  273   b , reserved field  273   c , and resource IE count field  273   d . Mandatory field  273   a  may comprise a single bit that when set (e.g., to “I”) indicates that one of the associated resources specified in a resource E must be able to be allocated for the resource request to be considered successful. A Mandatory field  273   a  that is not asserted indicates that none of the resources specified in a resource E of the RIC is necessary to be allocated for the resource request to be considered successful. In this instance, the target TAP should keep processing the rest of the request in the RIC even if none of the resources specified in the resource IEs following the RDIE is able to be allocated. Confirm field  273   b  may comprise a bit that is used only in response messages to indicate success or failure of the allocation. If the RIC comprises a resource request, confirm field  273   b  may be set to zero or otherwise left unasserted and ignored in the request message. Reserved field  273   c  may be of a fixed length and ignored by a target TAP. Resource E count field  273   d  indicates the number of resource IEs that follow the RDIE. For example, resource IE count field  273   d  would include an indicator of “1” if control options field  273  is included in RDIE  252   a  of RIC  250   a  shown in  FIG. 7 . As another example, resource IE count field  273   d  would include an indicator of “2” if control options field  273  is included in RDIE  252   c  of RIC  250   b  shown in  FIG. 8 .  
         [0071]     Two general BSS transition methods may be implemented in accordance with embodiments described herein: a required BSS transition and a pre-reservation BSS transition. A required BSS transition may be executed when a STA must transition to a target TAP and therefor does not require resource reservation prior to its transition. A pre-reservation BSS transition may be executed when a STA requires assurances, such as security and QoS resources, be available prior to executing the transition. TAPs may advertise TAP capabilities and policies for supporting the pre-reservation capabilities.  
         [0072]     The required BSS transition mechanism enables STAs to transition to a target TAP in the event that it must transition without expending processing and transition capacity for invoking a reservation or in the event that a network policy, a subscriber policy or a network carrier policy, only enforces the required BSS transition mechanism.  
         [0073]     The pre-reservation BSS Transition mechanism optimizes the number of exchanges required to establish, for example, a PTKSA or QoS resources. Information elements are included to allow for provisioning of a PTKSA and QoS resources.  
         [0074]     As discussed above previously, a resource pre-allocation process is provided. The process is invoked, in one embodiment, by mobile stations that have an existing association to an access point, that is a current access point, in the same administrative domain as a target transition access point. Once the resources have been obtained, pre-allocation operations are subsequently performable at a target TAP. The pre-allocation process, in the exemplary implementation, is not used for the creation of resources over and above a current connection, but in another embodiment, such use is permitted. However, the target TAP is permitted to have a policy whereby the target TAP rejects any requests that are different from the current allocation or rejects any requests that exceed the current allocation while allowing those that are less than current allocations. Communications to confirm allocations are carried out, for instance, by an IETF context transfer protocol (CTP).  
         [0075]     Thereby, through the formation and use of resource information containers, a structured manner is provided by which to request and to reserve resources at a target or candidate TAP prior to the commencement of transition procedures. Improved communication operations are provided as communication interruptions caused by extended delays during transition procedures are avoided.  
         [0076]     The previous descriptions are of preferred examples for implementing the invention, and the scope of the invention should not necessarily be limited by this description. The scope of the present invention is defined by the following claims.