WO2007134054A2 - Quality of service resource negotiation - Google Patents

Quality of service resource negotiation Download PDF

Info

Publication number
WO2007134054A2
WO2007134054A2 PCT/US2007/068476 US2007068476W WO2007134054A2 WO 2007134054 A2 WO2007134054 A2 WO 2007134054A2 US 2007068476 W US2007068476 W US 2007068476W WO 2007134054 A2 WO2007134054 A2 WO 2007134054A2
Authority
WO
WIPO (PCT)
Prior art keywords
resource
wireless router
qos
request
transmitting
Prior art date
Application number
PCT/US2007/068476
Other languages
French (fr)
Other versions
WO2007134054A3 (en
Inventor
Kapil Sood
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2007134054A2 publication Critical patent/WO2007134054A2/en
Publication of WO2007134054A3 publication Critical patent/WO2007134054A3/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/20Traffic policing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/22Alternate routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/24Multipath
    • H04L45/247Multipath using M:N active or standby paths
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/15Flow control; Congestion control in relation to multipoint traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/76Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/765Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points
    • H04L47/767Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points after changing the attachment point, e.g. after hand-off
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/78Architectures of resource allocation
    • H04L47/783Distributed allocation of resources, e.g. bandwidth brokers
    • H04L47/785Distributed allocation of resources, e.g. bandwidth brokers among multiple network domains, e.g. multilateral agreements
    • H04L47/786Mapping reservation between domains
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/80Actions related to the user profile or the type of traffic
    • H04L47/805QOS or priority aware
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/82Miscellaneous aspects
    • H04L47/824Applicable to portable or mobile terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node

Definitions

  • Embodiments of the present invention relate generally to the field of wireless networks, and more particularly to negotiating for quality of service resources in said wireless networks.
  • a communication session in a wireless network typically involves a local station communicating with a remote station via a communication link.
  • the communication link may include a wireless connection between the local station and a wireless router.
  • the quality of the wireless connection between the wireless router and the local station may deteriorate. This may be due to overloading of the wireless router, mobility of the station, interference, etc.
  • the local station may re- associate the wireless connection portion of the communication link with another wireless router.
  • QoS quality of resource
  • F ⁇ G, 1 illustrates a network providing for fast transition ing in accordance with an embodiment of this invention
  • FIG. 2 illustrates quality of service resource in accordance with an embodiment of this invention
  • FiG. 3 illustrates a fast transition procedure in accordance with an embodiment of this invention
  • FiG. 4 illustrates a 4-message transition procedure in accordance with an embodiment of this invention
  • FIG. 5 illustrates a resource request in accordance with an embodiment of this invention
  • FIG, 6 illustrates a resource response in accordance with an embodiment of this invention
  • FIG. 7 illustrates a resource response in accordance with an embodiment of this invention
  • FIG. 8 illustrates a resource request for two streams in accordance with an embodiment of this invention
  • FIG. 9 illustrates a resource response in accordance with an embodiment of this invention.
  • FIG. 10 illustrates a resource response in accordance with an embodiment of this invention
  • FIG. 11 illustrates a 6-message transition procedure in accordance with an embodiment of this invention.
  • FIG. 12 illustrates a computing device in accordance with an embodiment of this invention.
  • Embodiments of the present invention may provide a method, article of manufacture, apparatus, and system for negotiating quality of service (QoS) resources in wireless networks.
  • QoS quality of service
  • Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternate embodiments may be practiced with only some of the described aspects. For purposes of explanation, specific devices and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative embodiments.
  • phrase "in one embodiment” is used repeatedly. The phrase generally does not refer to the same embodiment; however, it may.
  • the terms “comprising,” “having,” and “including” are synonymous, unless the context dictates otherwise.
  • the phrase “A/B” means “A or B.”
  • the phrase “A and/or B” means “(A) 1 (B) 1 or (A and B).”
  • the phrase “A, B, and/or C” means "(A), (B), (C), (A and B), (A and C), (B and C) or (A, B and C).”
  • a software component may refer to programming logic employed to obtain a desired outcome.
  • the term "software component” may be synonymous with “module” or “agent” and may refer to programming logic that may be embodied in hardware or firmware, or in a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, C++.
  • a software component may be compiled and linked into an executable program, or installed in a dynamic link library, or may be written in an interpretive language such as BASIC. It will be appreciated that software components may be callable from other components or from themselves, and/or may be invoked in response to detected events or interrupts, in some embodiments, the components described herein are implemented as software modules, but nonetheless may be represented in hardware or firmware.
  • hardware components may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. Although only a given number of discrete software/hardware components may be illustrated and/or described, such components may nonetheless be represented by additional components or fewer components without departing from the spirit and scope of embodiments of the invention.
  • FIG. 1 illustrates a network 100 supporting fast transitioning (FT) of mobile wireless devices with QoS resource negotiation in accordance with an embodiment of this invention.
  • a station 104 may be communicating with a remote network entity 108 via an established communication link.
  • the communication session between the station 104 and the remote network entity 108 may include delay and/or jitter sensitive network traffic such as, but not limited to, streaming multimedia, Internet protocol (IP) telephony (e.g., voice-over IP (VoIP)), video teleconferencing, etc.
  • IP Internet protocol
  • VoIP voice-over IP
  • the communication link may include a wireless connection 112 between the station 104 and, at least initiaiiy, a wireless router 116.
  • the station 104 and wireless router 116 may be entities of a wireless network 118 such as, but not limited to, a wireless local area network (WLAN), a wireless metropolitan access network (WMAN), etc.
  • the wireless network 118 may be a subset of network 100.
  • the wireless network 118 may be an infrastructure network and the wireless router 116 (and other wireless routers) may be access points.
  • the wireless network 118 may be an ad hoc network and the wireless router 116 (and other wireless routers) may be stations.
  • the wireless network 118 may comply with one or more of the Institute of Electrical and Electronics Engineers (IEEE) wireless LAN/WLAN standards, e.g., any of the 802.11 standards.
  • IEEE Institute of Electrical and Electronics Engineers
  • the wireless router 116 may be communicatively coupled to other network devices 120 to relay communications between the station 104 and the remote network entity 108.
  • the remote network entity 108 may be communicatively coupled to the other network devices 120 through a wireless connection or a wired connection.
  • the station 104 may experience/anticipate deterioration in a quality of the wireless connection 112 with the wireless router 116.
  • the station 104 may initiate a fast transitioning procedure in order to re-associate the wireless connection 112 with another wireless router, e.g., target wireless router 124.
  • Fast transitioning may also be referred to as "fast roaming.”
  • Network entities capable of performing fast transitioning procedures as described herein, e.g., station 104 and wireless router 124 may be generically referred to as FT platforms.
  • FT platforms may be mobile network client devices such as, but not limited to, a personal computing device, a laptop computing device, a phone, etc. or network infrastructure devices, e.g., a server, an access point, etc.
  • the station 104 and the wireless router 124 may include various hardware and/or software components directed toward fast transitioning operations in accordance with embodiments of this invention. Some of these components will now be briefly introduced and discussed further in embodiments to follow.
  • the station 104 may include a wireless network interface card
  • the WNIC 128 may facilitate wireless communication with other components of the wireless network 118.
  • the WNIC 128 may include firmware to facilitate processing of messages to and/or from components of a host 132,
  • the WNIC 128 may cooperate with an antenna structure 130 to provide access to other entities of the wireless network 118.
  • the antenna structure 130 may include one or more directional antennas, which radiate or receive primarily in one direction (e.g., for 120 degrees), cooperatively coupled to one another to provide substantia ⁇ ly omnidirectionai coverage; or one or more omnidirectionai antennas. which radiate or receive equally well in a!! directions,
  • the host 132 may include a driver, e.g., wireless local area network (WLAN) driver 136, to drive the WN(C 128 for other components of the host 132 such as a transitioning manager 140 and a supplicant 144.
  • the transitioning manager 140 may control QoS operations such as the resource negotiations discussed in embodiments of this invention.
  • the supplicant 144 may act as a security software component, e.g., for performing message integrity calculations.
  • the wireless router 124 may include a WNIC 148 and antenna structure 150 to facilitate wireless communication with a number of stations in the wireless network 118.
  • the wireless router 124 may include a host 152 having a driver 156 to drive the WNIC 148 for other components of the host 152 such as a QoS scheduler 160 and an authenticator 164.
  • the QoS scheduler 160 may process and manage resource requests for a number of different stations of the wireless network 118.
  • the authenticator 164 may act as a security software component, e.g., for performing message integrity calculations.
  • the transitioning manager 140 of the station 104 may generate and transmit, via the WLAN driver 136 and the WNfC 128, a resource request to the target wireless router 124 requesting a resource to maintain a QoS ⁇ evel for transmissions within the session.
  • FIG. 1 the transitioning manager 140 of the station 104 may generate and transmit, via the WLAN driver 136 and the WNfC 128, a resource request to the target wireless router 124 requesting a resource to maintain a QoS ⁇ evel for transmissions within the session.
  • the QoS resource 200 includes a traffic specification information element (TSPEC IE) to describe the traffic pattern for which service is being requested including, e.g., data rate, packet size, delay, and service interval; a traffic classification (TCLAS) IE to specify certain parameters to identify a packet as belonging to the communication session; and a TCLAS processing IE to provide information on processing of packets.
  • TSPEC IE traffic specification information element
  • TCLAS traffic classification
  • TCLAS processing IE to provide information on processing of packets.
  • the QoS scheduler 160 of the wireless router 124 may process the resource request and determine whether it can aifocate one of the requested resources to the station 104. In the event that the wireless router 124 is unable to allocate any of the requested resources, it may communicate this nonallocation to the station 104. in various embodiments of this invention, a nonalfocation of a requested resource may not cause a fast transitioning procedure to fail. That is, the station 104 may still have the option to re-associate the wireless connection 112 with the wireless router 124 even if it wil! be at a level of service less than that which was requested.
  • This flexibility may allow for the transitioning manager 140 to decide to continue transference of the wireless connection 112 or to start a new negotiation, depending on the needs of the station 104 at that time. This elasticity may facilitate preservation of the established communication link, even if it is done so at a decreased level of service.
  • FiG.3 illustrates a fast transitioning procedure in accordance with an embodiment of the present invention.
  • the station 104 may begin the fast transitioning procedure at an event such as, e.g.. detection of signal deterioration in the wireless connection 112 with the wireless router 116, block 304.
  • the station 104 may identify one or more wireless routers that are within range as target wireless routers, e.g., wireless router 124 3 block 308. Identification of target wireless routers may include various identification and/or authentication operations. Some of these operations may occur through the use of active scanning, passive scanning, and/or through the use of wireless neighbor reports.
  • Identification of target wireless routers may include the station 104 receiving policy advertisements broadcast from various wireless routers that indicate the QoS capabilities of the particular wireless routers.
  • the policy advertisement may inform the station 104 that the wireless router 124 has an administrative policy that catis for the station 104 to execute a resource negotiation before the re-association request ⁇ Policy A); or provides the station 104 with an option of executing the QoS resource negotiation contemporaneously with the re-association request or prior to the re-association request (Policy B),
  • These administrative policies may be communicated by, e.g., the setting of a protocol policy bit to 0 or 1. In various embodiments, other policies may be additionally/alternatively implemented.
  • the 6-message procedure may introduce latency into the infrastructure to provide a wireless router additional time to process QoS calculations by having them done prior to the re-association request.
  • the A- message procedure may conserve a station's resources by providing reduced transmissions compared to the 6-message procedure.
  • the station 104 may use the policy advertisement to make a policy determination, block 312. If the station 104 determines that the target wireless router 124 has Policy A set, it may proceed with the 6-message procedure for QoS resource and re-association negotiation, block 316. If, however, the station 104 determines that the target wireless router 124 has Policy B set, it may make a procedure determination, block 320, and decide to use the 4- message procedure, block 324, or the 6-message procedure, block 316.
  • the flexibility provided to the station 104 through Policy B may be useful if, e.g., the station 104 decides that router processing of the TSPECs in 4-message procedure is taking too much time in which case the station 104 may wish to revert to the 6-message procedure. In another example, if the station 104 senses wireless congestion, it may wish to reserve TSPEC resources at multiple wireless routers, using the first 4 messages of the 6-message procedure with multiple wireless routers, and finally send the fast 2 messages to one of those wireless routers, described in further detail below. [0042] If the 4- or 6-message procedure is successful, the station may then transition the wireless connection 112 from the wireless router 116 to the target wireless router 124, block 328.
  • F!G. 4 illustrates a 4-message procedure in accordance with an embodiment of the present invention
  • the station 104 may have the wireless connection 112 with the wireless router 116.
  • the station 104 may transmit an FT Authentication Request 404 to the wireless router 124.
  • the FT Authentication Request 404 may include a station nonce (Snonce), e.g., a randomly (or pseudo-randomly) generated number, to protect against replay attacks.
  • Request 404 may also include a mobility domain identifier (SvIDID) to identify the wireless fast transitioning mobility domain.
  • SvIDID mobility domain identifier
  • a station may execute a fast transitioning procedure to any wireless router within the same mobility domain.
  • the wireless router 124 may use the attributes provided in the FT Authentication Request 404 to derive a secret session key.
  • the wireless router 124 may return an FT Authentication Response 408.
  • the FT Authentication Response 408 may include a wireiess router nonce (ANONCE) 5 an MDID, and a fast transitioning information element (FTJE), which may contain identifiers for the network entities that are eligible to hold secret keys within the mobility domain.
  • the station 104 may use the parameters provided in the FT Authentication Response 408 to derive the secret session key.
  • the FT Authentication Request 404 and
  • Response 408 may be done either over the air (e.g., directly with wireless router 124) or via the wireless connection 112 with wireless router 116; while the messages to follow may be done over the air.
  • the station 104 may construct and transmit a resource request contemporaneously with a Re-Association Request 412. This may be done by including the resource request in the Re-Association Request 412.
  • the Re-Association Request 412 may include management fields such as one or more IEs that carry protocol specific information to assist in fast transitioning, e.g., security information, key lifetimes, MDID 1 FTIE, unique session identifiers, etc.
  • the Re-Association Request 412 may also include a message integrity code (MIC) generated using a key confirmation key (KCK) to authenticate and maintain the integrity of the communications.
  • MIC message integrity code
  • KCK key confirmation key
  • FiG. 5 illustrates a resource request 500 that may be transmitted in the Re-Association Request 412.
  • the resource request 500 may include a stream identification element (stream-(D) followed by a number of QoS resources, e.g., Resource - 1 , Resource - 2, and Resource - 3.
  • Resources 1 - 3 may be QoS resource alternatives, which may be listed in the order of preference. That is, Resource - 1 is the first choice of the station 104, Resource - 2 is the second, and so forth.
  • the wireless router 124 may process the Re-Association Request
  • the wireless router 124 may then generate a Re-Association Response 416 including, for example, management fields, a resource response, and MIC-KCK.
  • the resource response may indicate an allocated resource; no resource allocated but one or more alternative resources suggested; or no resource allocated or suggested.
  • FIG. 6 illustrates a resource response 600 indicating an allocated resource in accordance with an embodiment of this invention.
  • the resource response 600 indicates that the second requested resource, e.g., Resource - 2, was allocated to the station 104.
  • the station 104 may then re-associate the wireless connection 112 with the wireless router 124 with Resource - 2.
  • F!G. 7 illustrates a resource response 700 indicating that no resource was allocated but alternative resources are suggested in accordance with an embodiment of this invention, in particular, the resource response 700 suggests Resource - 4 and Resource - 5 as alternative resources, At this point, neither of these suggested resources may have been allocated.
  • tne station 104 may re-associate the wireless connection 112 with the wireless router 124 and, if desired, request allocation of one of the suggested resources through an add data traffic stream (ADDTS) message 420.
  • ADDTS add data traffic stream
  • the wireless router 124 may allocate one of the requested resources, [0053]
  • An embodiment indicating that no resources were allocated or suggested may simpiy include a stream ID without any resources listed.
  • the Re-Association Request 412 may not fail if none of the requested resources can be allocated. However, the Re-Association Request 412 may fail for other reasons, e.g., a badly formed message, MIC failure, keys not derived properly, etc.
  • the station 104 may perform these other checks prior to transitioning the wireless connection 112.
  • the different streams may indicate a different type of network traffic.
  • stream 1 may include video
  • stream 2 includes voice.
  • the resource request 800 indicates two resource options for the first stream, e.g., Resource - 1 and Resource - 2; and two resource options for the second stream, e.g., Resource - 3 and Resource - 4.
  • the wireless router 124 may transmit a resource response 900 illustrated in FfG. 9, in accordance with an embodiment of this invention.
  • the resource response 900 indicates that Resource ⁇ 2 was allocated for the first stream and no resource was allocated for the second stream.
  • FIG. 10 illustrates an alternative resource response 1000 that may be transmitted by the wireiess router 124 in accordance with an embodiment of this invention.
  • the resource response 1000 indicates that no resources were allocated or suggested for stream 1 ; no resources were allocated for stream 2; and Resource - 5 and Resource - 6 are suggested as alternatives for stream 2.
  • the content of the responses may vary according to resource availability and the capabilities of the QoS scheduler 160 to suggest feasible alternative resources.
  • FIG. 11 illustrates a 6-message procedure in accordance with an embodiment of the present invention
  • the station 104 may initiate fast transitioning procedure through an FT Authentication Request 1104 and FT Authentication Response 1108, similar to like-named messages discussed in relation to the 4-message procedure.
  • the station 104 may then transmit an FT Authentication Confirm 1112 message that includes a resource request. Similar to above embodiment, the FT Authentication Confirm 1112 will not fail if the wireless router 124 is unabie to allocate any of the requested resources; however, it may fail for a badly formed message, MfC failure, keys not properly derived, etc.
  • the wireless router 124 may return an FT Authentication Acknowledge 1116 including a resource response.
  • the station 104 may process the FT Authentication Acknowledge
  • the 1116 may proceed to re-associate the wireless connection 112 with the wireless router 124, go to another wireless router, or restart the 6-message procedure with new resources with the wireless router 124.
  • the station 104 may transmit a Re-Association Request 1120 to the wireless router 124 including management fields and a MlC-KCK.
  • the Re- Association Request 1120 may not include the resource request, as this was already transmitted.
  • the wireless router 124 may process the Re-Association Request 1120 by accessing memory to determine whether any resources were reserved for this station 104. If a resource was allocated, the wireless router 124 may proceed by associating the allocated resource with the station 104.
  • the wireless router 124 may generate and transmit a Re-Association Response 1124 to the station 104 including management fields and an MIC-KCK.
  • the station 104 may process the Re-Association Response 1124 and if it is successful, may proceed to transfer the wirefess connection 112 to the wireless router 124.
  • Association Response 1124 may be done over the air, while the previous messages may be done over the air or through the wireless connection 112 with the wireless router 116. [0064] Sf necessary, the station 104 may use an ADDTS message 1128, after re-associating with wireless router 124, to request allocation of one of the alternative resources suggested in resource response transmitted in FT Authentication Acknowledge 1116.
  • the station 104 may execute the first four messages of the 6-message procedure, e.g., the FT Authentication Request, Response, Confirm, and Acknowledge, with multiple wireless routers. This may allow the station 104 to receive an indication prior to re-association on which wireless routers can accept its resource request.
  • the next two messages of the 6-message procedure e.g., the Re-Association Request and Response, may then be done with a selected wireless router, e.g., wireless router 124, in order to effectuate the re-association.
  • FIG. 12 illustrates a computing device 1200 capable of implementing an FT platform in accordance with various embodiments.
  • computing device 1200 includes processor 1204, memory 1208, and bus 1212, coupied to each other as shown.
  • computing device 1200 includes storage 1216, and communication interfaces 1220, e.g., a WNIC, coupled to each other, and the earlier described elements as shown.
  • communication interfaces 1220 e.g., a WNIC
  • Memory 1208 and storage 1216 may include in particular, temporal and persistent copies of QoS logic 1224, respectively.
  • the QoS logic 1224 may include instructions that when accessed by the processor 1204 result in the computing device 1200 performing operations or executions described in conjunction with the FT platforms in accordance with embodiments of this invention, in particular, the accessing of the QoS fogic 1224 by the processor 1204 may facilitate transition managing and scheduling operations of the FT platforms as described above in connection with various embodiments, [0068] in various embodiments, the memory 1208 may include RAM, dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), dual- data rate RAM (DDRRAM), etc.
  • DRAM dynamic RAM
  • SRAM static RAM
  • SDRAM synchronous DRAM
  • DDRRAM dual- data rate RAM
  • the processor 1204 may include one or more singie-core processors, muitiple-core processors, controllers, application- specific integrated circuits (ASICs), etc.
  • storage 1216 may include integrated and/or peripheral storage devices, such as, but not limited to, disks and associated drives (e.g., magnetic, optical), universal serial bus (USB) storage devices and associated ports, flash memory, read-only memory (ROM), non-volatile semiconductor devices, etc.
  • disks and associated drives e.g., magnetic, optical
  • USB universal serial bus
  • storage 1216 may be a storage resource physically part of the computing device 1200 or it may be accessible by, but not necessarily a part of, the computing device 1200.
  • the storage 1216 may be accessed by the computing device 1200 over a network.
  • computing device 1200 may have more or less elements, and/or different architectures.
  • computing device 1200 may be a station, an access point, or some other wireless communication device.

Abstract

Embodiments of apparatuses, articles, methods, and systems for negotiating quality of service resources in wireless networks are generally described herein. Other embodiments may be described and claimed.

Description

QUALITY QF SERVICE RESOURCE NEGOTSATtON
Related Application
[0001] The present application claims priority to U.S. Provisional Patent
Application No. [not yet known - Express Mail Label No. EV695561614US], filed May 1O1 2006, entitled "A System, Apparatus, Methods and Associated Protocols for Service Resource Negotiation in a Wireless Communications Network," the entire contents of which are hereby incorporated by reference.
Field
[0002] Embodiments of the present invention relate generally to the field of wireless networks, and more particularly to negotiating for quality of service resources in said wireless networks.
Background
[0003] A communication session in a wireless network typically involves a local station communicating with a remote station via a communication link. The communication link may include a wireless connection between the local station and a wireless router. For various reasons, the quality of the wireless connection between the wireless router and the local station may deteriorate. This may be due to overloading of the wireless router, mobility of the station, interference, etc. In order to preserve the established communication link, the local station may re- associate the wireless connection portion of the communication link with another wireless router. When the communication session involves delay intolerant transmissions, e.g., voice or video, various quality of resource (QoS) challenges are presented for a successful and efficient re-association of the wireless connection.
Brief Description of the Drawings
[0004] Embodiments of the invention are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which: [0005] FΪG, 1 illustrates a network providing for fast transition ing in accordance with an embodiment of this invention;
[0006] FIG. 2 illustrates quality of service resource in accordance with an embodiment of this invention; [0007] FiG. 3 illustrates a fast transition procedure in accordance with an embodiment of this invention;
[0008] FiG. 4 illustrates a 4-message transition procedure in accordance with an embodiment of this invention;
[0009] FIG. 5 illustrates a resource request in accordance with an embodiment of this invention;
[0010] FIG, 6 illustrates a resource response in accordance with an embodiment of this invention;
[0011] FIG. 7 illustrates a resource response in accordance with an embodiment of this invention; [0012] FIG. 8 illustrates a resource request for two streams in accordance with an embodiment of this invention;
[0013] FIG. 9 illustrates a resource response in accordance with an embodiment of this invention;
[0014] FIG. 10 illustrates a resource response in accordance with an embodiment of this invention;
[0015] FIG. 11 illustrates a 6-message transition procedure in accordance with an embodiment of this invention; and
[0016] FIG. 12 illustrates a computing device in accordance with an embodiment of this invention.
Detailed Description
[0017] Embodiments of the present invention may provide a method, article of manufacture, apparatus, and system for negotiating quality of service (QoS) resources in wireless networks. [0018] Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternate embodiments may be practiced with only some of the described aspects. For purposes of explanation, specific devices and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative embodiments.
[0019} Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the present invention; however, the order of description should not be construed as to imply that these operations are necessarily order dependent, in particular, these operations need not be performed in the order of presentation.
[0020] The phrase "in one embodiment" is used repeatedly. The phrase generally does not refer to the same embodiment; however, it may. The terms "comprising," "having," and "including" are synonymous, unless the context dictates otherwise. [0021] In providing some clarifying context to language that may be used in connection with various embodiments, the phrase "A/B" means "A or B." The phrase "A and/or B" means "(A)1 (B)1 or (A and B)." The phrase "A, B, and/or C" means "(A), (B), (C), (A and B), (A and C), (B and C) or (A, B and C)."
[0022] A software component, as used herein, may refer to programming logic employed to obtain a desired outcome. The term "software component" may be synonymous with "module" or "agent" and may refer to programming logic that may be embodied in hardware or firmware, or in a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, C++. A software component may be compiled and linked into an executable program, or installed in a dynamic link library, or may be written in an interpretive language such as BASIC. It will be appreciated that software components may be callable from other components or from themselves, and/or may be invoked in response to detected events or interrupts, in some embodiments, the components described herein are implemented as software modules, but nonetheless may be represented in hardware or firmware. [0023] it will be further appreciated that hardware components may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. Although only a given number of discrete software/hardware components may be illustrated and/or described, such components may nonetheless be represented by additional components or fewer components without departing from the spirit and scope of embodiments of the invention.
[0024] FIG. 1 illustrates a network 100 supporting fast transitioning (FT) of mobile wireless devices with QoS resource negotiation in accordance with an embodiment of this invention. In this embodiment, a station 104 may be communicating with a remote network entity 108 via an established communication link. In various embodiments, the communication session between the station 104 and the remote network entity 108 may include delay and/or jitter sensitive network traffic such as, but not limited to, streaming multimedia, Internet protocol (IP) telephony (e.g., voice-over IP (VoIP)), video teleconferencing, etc.
[0025] The communication link may include a wireless connection 112 between the station 104 and, at least initiaiiy, a wireless router 116. The station 104 and wireless router 116 may be entities of a wireless network 118 such as, but not limited to, a wireless local area network (WLAN), a wireless metropolitan access network (WMAN), etc. The wireless network 118 may be a subset of network 100. In an embodiment, the wireless network 118 may be an infrastructure network and the wireless router 116 (and other wireless routers) may be access points. In another embodiment, the wireless network 118 may be an ad hoc network and the wireless router 116 (and other wireless routers) may be stations. [0026] In an embodiment, the wireless network 118 may comply with one or more of the Institute of Electrical and Electronics Engineers (IEEE) wireless LAN/WLAN standards, e.g., any of the 802.11 standards.
[0027] The wireless router 116 may be communicatively coupled to other network devices 120 to relay communications between the station 104 and the remote network entity 108. The remote network entity 108 may be communicatively coupled to the other network devices 120 through a wireless connection or a wired connection.
[0028] in an embodiment, the station 104 may experience/anticipate deterioration in a quality of the wireless connection 112 with the wireless router 116. In this embodiment, the station 104 may initiate a fast transitioning procedure in order to re-associate the wireless connection 112 with another wireless router, e.g., target wireless router 124. "Fast transitioning" may also be referred to as "fast roaming." [0029] Network entities capable of performing fast transitioning procedures as described herein, e.g., station 104 and wireless router 124, may be generically referred to as FT platforms. In some embodiments FT platforms may be mobile network client devices such as, but not limited to, a personal computing device, a laptop computing device, a phone, etc. or network infrastructure devices, e.g., a server, an access point, etc.
[0030] The station 104 and the wireless router 124 may include various hardware and/or software components directed toward fast transitioning operations in accordance with embodiments of this invention. Some of these components will now be briefly introduced and discussed further in embodiments to follow.
[0031] The station 104 may include a wireless network interface card
(WNIC) 128 to facilitate wireless communication with other components of the wireless network 118. The WNIC 128 may include firmware to facilitate processing of messages to and/or from components of a host 132, The WNIC 128 may cooperate with an antenna structure 130 to provide access to other entities of the wireless network 118. [0032] in various embodiments, the antenna structure 130 may include one or more directional antennas, which radiate or receive primarily in one direction (e.g., for 120 degrees), cooperatively coupled to one another to provide substantiaϊly omnidirectionai coverage; or one or more omnidirectionai antennas. which radiate or receive equally well in a!! directions,
[0033] In various embodiments, the host 132 may include a driver, e.g., wireless local area network (WLAN) driver 136, to drive the WN(C 128 for other components of the host 132 such as a transitioning manager 140 and a supplicant 144. The transitioning manager 140 may control QoS operations such as the resource negotiations discussed in embodiments of this invention. The supplicant 144 may act as a security software component, e.g., for performing message integrity calculations.
[0034] The wireless router 124 may include a WNIC 148 and antenna structure 150 to facilitate wireless communication with a number of stations in the wireless network 118. The wireless router 124 may include a host 152 having a driver 156 to drive the WNIC 148 for other components of the host 152 such as a QoS scheduler 160 and an authenticator 164. The QoS scheduler 160 may process and manage resource requests for a number of different stations of the wireless network 118. The authenticator 164 may act as a security software component, e.g., for performing message integrity calculations.
[0035] During a re-association procedure, the transitioning manager 140 of the station 104 may generate and transmit, via the WLAN driver 136 and the WNfC 128, a resource request to the target wireless router 124 requesting a resource to maintain a QoS ϊevel for transmissions within the session. FIG. 2 illustrates an example of a QoS resource 200 in accordance with an embodiment of this invention, in this embodiment, the QoS resource 200 includes a traffic specification information element (TSPEC IE) to describe the traffic pattern for which service is being requested including, e.g., data rate, packet size, delay, and service interval; a traffic classification (TCLAS) IE to specify certain parameters to identify a packet as belonging to the communication session; and a TCLAS processing IE to provide information on processing of packets. These information elements may be similar to like-name elements described in IEEE 802,11(e) (published November 11 , 2005), along with any updates, revisions, and/or amendments to such.
[0036] The QoS scheduler 160 of the wireless router 124 may process the resource request and determine whether it can aifocate one of the requested resources to the station 104. In the event that the wireless router 124 is unable to allocate any of the requested resources, it may communicate this nonallocation to the station 104. in various embodiments of this invention, a nonalfocation of a requested resource may not cause a fast transitioning procedure to fail. That is, the station 104 may still have the option to re-associate the wireless connection 112 with the wireless router 124 even if it wil! be at a level of service less than that which was requested. This flexibility may allow for the transitioning manager 140 to decide to continue transference of the wireless connection 112 or to start a new negotiation, depending on the needs of the station 104 at that time. This elasticity may facilitate preservation of the established communication link, even if it is done so at a decreased level of service.
[0037] In various embodiments, the QoS scheduler 160 may support varying levels of fast transitioning procedures and the transitioning manager 140 may adjust its fast transitioning operations accordingly. FiG.3 illustrates a fast transitioning procedure in accordance with an embodiment of the present invention. In this embodiment, the station 104 may begin the fast transitioning procedure at an event such as, e.g.. detection of signal deterioration in the wireless connection 112 with the wireless router 116, block 304. The station 104 may identify one or more wireless routers that are within range as target wireless routers, e.g., wireless router 1243 block 308. Identification of target wireless routers may include various identification and/or authentication operations. Some of these operations may occur through the use of active scanning, passive scanning, and/or through the use of wireless neighbor reports.
[0038] Identification of target wireless routers may include the station 104 receiving policy advertisements broadcast from various wireless routers that indicate the QoS capabilities of the particular wireless routers. The policy advertisement may inform the station 104 that the wireless router 124 has an administrative policy that catis for the station 104 to execute a resource negotiation before the re-association request {Policy A); or provides the station 104 with an option of executing the QoS resource negotiation contemporaneously with the re-association request or prior to the re-association request (Policy B), These administrative policies may be communicated by, e.g., the setting of a protocol policy bit to 0 or 1. In various embodiments, other policies may be additionally/alternatively implemented.
[0039] Negotiating for QoS resources prior to the re-association request may hereinafter be referred to as a 6-message procedure, while negotiating for QoS resources contemporaneously with re-association negotiation may hereinafter be referred to as a 4-message procedure. !n various embodiments, other number of messages may be used for either of these procedures.
[0040] The 6-message procedure may introduce latency into the infrastructure to provide a wireless router additional time to process QoS calculations by having them done prior to the re-association request. The A- message procedure, on the other hand, may conserve a station's resources by providing reduced transmissions compared to the 6-message procedure.
[0041] In an embodiment, the station 104 may use the policy advertisement to make a policy determination, block 312. If the station 104 determines that the target wireless router 124 has Policy A set, it may proceed with the 6-message procedure for QoS resource and re-association negotiation, block 316. If, however, the station 104 determines that the target wireless router 124 has Policy B set, it may make a procedure determination, block 320, and decide to use the 4- message procedure, block 324, or the 6-message procedure, block 316. The flexibility provided to the station 104 through Policy B may be useful if, e.g., the station 104 decides that router processing of the TSPECs in 4-message procedure is taking too much time in which case the station 104 may wish to revert to the 6-message procedure. In another example, if the station 104 senses wireless congestion, it may wish to reserve TSPEC resources at multiple wireless routers, using the first 4 messages of the 6-message procedure with multiple wireless routers, and finally send the fast 2 messages to one of those wireless routers, described in further detail below. [0042] If the 4- or 6-message procedure is successful, the station may then transition the wireless connection 112 from the wireless router 116 to the target wireless router 124, block 328.
[0043] F!G. 4 illustrates a 4-message procedure in accordance with an embodiment of the present invention, In this embodiment, the station 104 may have the wireless connection 112 with the wireless router 116. At initiation of a fast transitioning procedure, the station 104 may transmit an FT Authentication Request 404 to the wireless router 124. The FT Authentication Request 404 may include a station nonce (Snonce), e.g., a randomly (or pseudo-randomly) generated number, to protect against replay attacks. The FT Authentication
Request 404 may also include a mobility domain identifier (SvIDID) to identify the wireless fast transitioning mobility domain. A station may execute a fast transitioning procedure to any wireless router within the same mobility domain.
[0044] The wireless router 124 may use the attributes provided in the FT Authentication Request 404 to derive a secret session key. The wireless router 124 may return an FT Authentication Response 408. The FT Authentication Response 408 may include a wireiess router nonce (ANONCE)5 an MDID, and a fast transitioning information element (FTJE), which may contain identifiers for the network entities that are eligible to hold secret keys within the mobility domain. The station 104 may use the parameters provided in the FT Authentication Response 408 to derive the secret session key.
[0045] In various embodiments, the FT Authentication Request 404 and
Response 408 may be done either over the air (e.g., directly with wireless router 124) or via the wireless connection 112 with wireless router 116; while the messages to follow may be done over the air.
[0046] After a successful authentication, the station 104 may construct and transmit a resource request contemporaneously with a Re-Association Request 412. This may be done by including the resource request in the Re-Association Request 412. [0047] In addition to the resource request, the Re-Association Request 412 may include management fields such as one or more IEs that carry protocol specific information to assist in fast transitioning, e.g., security information, key lifetimes, MDID1 FTIE, unique session identifiers, etc. The Re-Association Request 412 may also include a message integrity code (MIC) generated using a key confirmation key (KCK) to authenticate and maintain the integrity of the communications.
[0048] FiG. 5 illustrates a resource request 500 that may be transmitted in the Re-Association Request 412. The resource request 500 may include a stream identification element (stream-(D) followed by a number of QoS resources, e.g., Resource - 1 , Resource - 2, and Resource - 3. Resources 1 - 3 may be QoS resource alternatives, which may be listed in the order of preference. That is, Resource - 1 is the first choice of the station 104, Resource - 2 is the second, and so forth.
[0049] The wireless router 124 may process the Re-Association Request
412 and determine whether any of the requested resources may be allocated to the station 104. The wireless router 124 may then generate a Re-Association Response 416 including, for example, management fields, a resource response, and MIC-KCK.
[0050] In various embodiments, the resource response may indicate an allocated resource; no resource allocated but one or more alternative resources suggested; or no resource allocated or suggested. FIG. 6 illustrates a resource response 600 indicating an allocated resource in accordance with an embodiment of this invention. In particular, the resource response 600 indicates that the second requested resource, e.g., Resource - 2, was allocated to the station 104. The station 104 may then re-associate the wireless connection 112 with the wireless router 124 with Resource - 2.
|0051 J As shown above, transmission of the resource requests and responses may be conducted in a secure integrity-protected session so that resources cannot be modified by an attacker. While the above embodiments discuss specific security mechanisms, other embodiments may use other mechanisms [0052] F!G. 7 illustrates a resource response 700 indicating that no resource was allocated but alternative resources are suggested in accordance with an embodiment of this invention, in particular, the resource response 700 suggests Resource - 4 and Resource - 5 as alternative resources, At this point, neither of these suggested resources may have been allocated. At this point, tne station 104 may re-associate the wireless connection 112 with the wireless router 124 and, if desired, request allocation of one of the suggested resources through an add data traffic stream (ADDTS) message 420. At that time, the wireless router 124 may allocate one of the requested resources, [0053] An embodiment indicating that no resources were allocated or suggested may simpiy include a stream ID without any resources listed.
[0054] As discussed above, the Re-Association Request 412 may not fail if none of the requested resources can be allocated. However, the Re-Association Request 412 may fail for other reasons, e.g., a badly formed message, MIC failure, keys not derived properly, etc. The station 104 may perform these other checks prior to transitioning the wireless connection 112.
[0055] While the above resource requests and responses illustrate one data stream, other embodiments may have more than one data stream (hereinafter simply stream). FIG. 8 illustrates a resource request 800 having a first stream with a stream ID = 1 and a second stream with a stream ID = 2. in various embodiments, the different streams may indicate a different type of network traffic. For example, stream 1 may include video, while stream 2 includes voice.
[0056] In this embodiment, the resource request 800 indicates two resource options for the first stream, e.g., Resource - 1 and Resource - 2; and two resource options for the second stream, e.g., Resource - 3 and Resource - 4. In response to this request, the wireless router 124 may transmit a resource response 900 illustrated in FfG. 9, in accordance with an embodiment of this invention. The resource response 900 indicates that Resource ~ 2 was allocated for the first stream and no resource was allocated for the second stream. [0057] FIG. 10 illustrates an alternative resource response 1000 that may be transmitted by the wireiess router 124 in accordance with an embodiment of this invention. The resource response 1000 indicates that no resources were allocated or suggested for stream 1 ; no resources were allocated for stream 2; and Resource - 5 and Resource - 6 are suggested as alternatives for stream 2.
[0058J In various embodiments, the content of the responses may vary according to resource availability and the capabilities of the QoS scheduler 160 to suggest feasible alternative resources.
[0059] FIG. 11 illustrates a 6-message procedure in accordance with an embodiment of the present invention, in this embodiment, the station 104 may initiate fast transitioning procedure through an FT Authentication Request 1104 and FT Authentication Response 1108, similar to like-named messages discussed in relation to the 4-message procedure. The station 104 may then transmit an FT Authentication Confirm 1112 message that includes a resource request. Similar to above embodiment, the FT Authentication Confirm 1112 will not fail if the wireless router 124 is unabie to allocate any of the requested resources; however, it may fail for a badly formed message, MfC failure, keys not properly derived, etc. The wireless router 124 may return an FT Authentication Acknowledge 1116 including a resource response. [0060] The station 104 may process the FT Authentication Acknowledge
1116 and may proceed to re-associate the wireless connection 112 with the wireless router 124, go to another wireless router, or restart the 6-message procedure with new resources with the wireless router 124.
[0061] If the station 104 proceeds to re-associate the wireless connection 112 with the wireless router 124, it may transmit a Re-Association Request 1120 to the wireless router 124 including management fields and a MlC-KCK. The Re- Association Request 1120 may not include the resource request, as this was already transmitted. The wireless router 124 may process the Re-Association Request 1120 by accessing memory to determine whether any resources were reserved for this station 104. If a resource was allocated, the wireless router 124 may proceed by associating the allocated resource with the station 104. The wireless router 124 may generate and transmit a Re-Association Response 1124 to the station 104 including management fields and an MIC-KCK.
[0062] The station 104 may process the Re-Association Response 1124 and if it is successful, may proceed to transfer the wirefess connection 112 to the wireless router 124.
[0063] In an embodiment, the Re-Association Request 1120 and the Re-
Association Response 1124 may be done over the air, while the previous messages may be done over the air or through the wireless connection 112 with the wireless router 116. [0064] Sf necessary, the station 104 may use an ADDTS message 1128, after re-associating with wireless router 124, to request allocation of one of the alternative resources suggested in resource response transmitted in FT Authentication Acknowledge 1116.
[0065] In some embodiments, the station 104 may execute the first four messages of the 6-message procedure, e.g., the FT Authentication Request, Response, Confirm, and Acknowledge, with multiple wireless routers. This may allow the station 104 to receive an indication prior to re-association on which wireless routers can accept its resource request. The next two messages of the 6-message procedure, e.g., the Re-Association Request and Response, may then be done with a selected wireless router, e.g., wireless router 124, in order to effectuate the re-association.
[0066] FIG. 12 illustrates a computing device 1200 capable of implementing an FT platform in accordance with various embodiments. As illustrated, for the embodiments, computing device 1200 includes processor 1204, memory 1208, and bus 1212, coupied to each other as shown. Additionally, computing device 1200 includes storage 1216, and communication interfaces 1220, e.g., a WNIC, coupled to each other, and the earlier described elements as shown.
[0067J Memory 1208 and storage 1216 may include in particular, temporal and persistent copies of QoS logic 1224, respectively. The QoS logic 1224 may include instructions that when accessed by the processor 1204 result in the computing device 1200 performing operations or executions described in conjunction with the FT platforms in accordance with embodiments of this invention, in particular, the accessing of the QoS fogic 1224 by the processor 1204 may facilitate transition managing and scheduling operations of the FT platforms as described above in connection with various embodiments, [0068] in various embodiments, the memory 1208 may include RAM, dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), dual- data rate RAM (DDRRAM), etc.
[0069] !n various embodiments, the processor 1204 may include one or more singie-core processors, muitiple-core processors, controllers, application- specific integrated circuits (ASICs), etc.
[0070] fn various embodiments, storage 1216 may include integrated and/or peripheral storage devices, such as, but not limited to, disks and associated drives (e.g., magnetic, optical), universal serial bus (USB) storage devices and associated ports, flash memory, read-only memory (ROM), non-volatile semiconductor devices, etc.
[0071] in various embodiments, storage 1216 may be a storage resource physically part of the computing device 1200 or it may be accessible by, but not necessarily a part of, the computing device 1200. For example, the storage 1216 may be accessed by the computing device 1200 over a network. [0072J In various embodiments, computing device 1200 may have more or less elements, and/or different architectures. In various embodiments, computing device 1200 may be a station, an access point, or some other wireless communication device.
[0073] Although the present invention has been described in terms of the above-illustrated embodiments, it will be appreciated by those of ordinary skill in the art that a wide variety of alternate and/or equivalent implementations calculated to achieve the same purposes may be substituted for the specific embodiments shown and described without departing from the scope of the present invention. Those with skill in the art will readily appreciate that the present invention may be implemented in a very wide variety of embodiments. This description is intended to be regarded as illustrative instead of restrictive on embodiments of the present invention.

Claims

ClaimsWhat is claimed is:
1. A method comprising: establishing, by a station, a wireless connection with a wireless router; transmitting, by the station, a resource request to another wireless router requesting aiiocation of a quality of service (QoS) resource; receiving, by the station, a resource response from the another wireless router indicating a nonallocation of the QoS resource; and transitioning the wireless connection from the wireless router to the another wireless router notwithstanding said nonallocation of the QoS resource.
2. The method of claim 1 , further comprising: receiving, in the resource response, one or more QoS resources as suggested alternatives to the requested QoS resource.
3. The method of claim 2, further comprising: transmitting, subsequent to said transitioning of the wireless connection, another resource request requesting allocation of another QoS resource selected from the one or more suggested QoS resources.
4. The method of claim 1 , further comprising: detecting a signal deterioration in the wireless connection with the wireless router; and transitioning the wireless connection from the wireless router to the another wireless router based at least in part on said detecting of the signal deterioration.
5. The method of claim 1 , wherein said transitioning of the wireless connection further comprises: transmitting a re-association request to the another wireless router; and receiving a successful re-association response from the another wireless router,
6. The method of claim 5, wherein said transmitting of the re-association request includes said transmitting of the resource request.
7. The method of claim 5, wherein said transmitting of the resource request occurs prior to said transmitting of the re-association request.
8. The method of ciaϊrrt 5, wherein said transmitting of the resource request occurs prior to said transmitting of the re-association request if no policy advertisement is received from the another wireless router.
9. The method of claim 5, further comprising: receiving a policy advertisement from the another wireless router indicating whether the station must transmit the resource request prior to transmitting the re- association request or whether the station has the option to transmit the resource request prior to transmitting the re-association request or contemporaneousiy with the re-association request.
10. The method of claim 5, further comprising: transmitting the resource request to a pluraiity of wireless routers that includes the another wireless router; receiving resource responses from the plurality of wireless routers; selecting the another wireless router from the plurality of wireless routers based at least in part on said receiving of the resource responses; and transmitting the re-association request to the another wireless router based at least in part on said selecting of the another wireless router.
11. The method of claim 1 , wherein said transmitting of the resource request requesting allocation of the QoS resource further comprises: identifying a plurality of QoS resources; and requesting allocation of at least one of the plurality of the QoS resources.
12. The method of claim 1 , wherein said transmitting of the resource request and receiving of the resource response are conducted within an integrity-protected communication session.
13. A system comprising: an omnidirectional antenna coupled to a host and configured to provide access to a wireless network, said access including a wireless connection between the host and a wireless router; and the host including a transitioning manager configured to transmit, via the omnidirectional antenna, a resource request to another wireless router for a quality of service (QoS) resource; to receive, via the omnidirectional antenna, a resource response from the another wireless router indicating a nonatlocatsoπ of the QoS resource; and to transition the wireless connection from the wireless router to the another wireless router notwithstanding said nonallocation of the QoS resource.
14. The system of claim 13, wherein the resource request further indicates one or more suggested QoS resources as alternatives to the requested QoS resource.
15. The system of claim 14, wherein the transitioning manager is further configured to transmit another resource request to the another wireless router for another QoS resource selected from the one or more suggested QoS resources.
16. The system of claim 13, wherein the transitioning manager is further configured to transmit a re-association request to the another wireless router; and to transition the wireless connection from the wireless router to the another wireless router based at ieast in part on a receipt of a successful re-association response from the another wireless router to the re-association request.
17. The system of claim 16, wherein the transitioning manager is further configured to include the resource request in the re-association request.
18. The system of claim 16, wherein the transition manager is further configured to transmit the resource request prior to the re-association request.
19. The system of claim 16, wherein the transition manager is further configured to receive a QoS capability advertisement from the another wireless router indicating whether the another wireless router is capable of receiving the resource request as a part of the re-association request.
20. An apparatus comprising: a wireless network interface card coupled to a host and configured to provide the host access to a wireless network; and the host including a scheduler configured to receive, via the wireless network interface card, a resource request from a station requesting allocation of a quality of service (QoS) resource; transmitting, via the wireless network interface card, a resource response indicating a nonaliocation of the QoS resource; and forming a wireless connection with the station notwithstanding said nonallocation of the QoS resource.
21. The apparatus of claim 20, wherein the scheduler is further configured to broadcast a policy advertisement indicating whether a station must transmit a resource request prior to transmitting a re-association request or whether a station has the option to transmit a resource request prior to transmitting a re-association request or contemporaneously with a re-association request.
22. The apparatus of claim 20, wherein the scheduler is further configured to transmit, in the resource response, one or more QoS resources as suggested alternatives to the requested QoS resource,
23. A machine-accessible medium having associated instructions, which, when executed, results in a station: establishing a wireless connection with a wireiess router; transmitting a resource request to another wireless router requesting allocation of a quality of service (QoS) resource; receiving a resource response from the another wireless router indicating a nonaNocation of the QoS resource; and transitioning the wireiess connection from the wireless router to the another wireless router notwithstanding said nonaNocation of the QoS resource.
24. The machine-accessible medium of claim 23 having associated instructions, which, when executed, further results in the station: receiving, in the resource response, one or more suggested QoS resources as suggested alternatives to the requested QoS resource; and transmitting, subsequent to said transitioning of the wireiess connection, another resource request requesting allocation of another QoS resource selected from the one or more suggested QoS resources.
25. The machine-accessible medium of claim 23 having associated instructions, which, when executed, further results in the station: determining whether to transmit the resource request prior to transmitting a re-association request or contemporaneously with the re-association request.
26. The machine-accessible medium of claim 23 having associated instructions, which, when executed, further results in the station: receiving a poϋcy advertisement from the wireless router and said determining whether to transmit the resource request prior to transmitting a re- association request or contemporaneously with the re-association request is based at least in part on said receiving of the policy advertisement.
PCT/US2007/068476 2006-05-10 2007-05-08 Quality of service resource negotiation WO2007134054A2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US79909206P 2006-05-10 2006-05-10
US60/799,092 2006-05-10
US11/462,657 US7911997B2 (en) 2006-05-10 2006-08-04 Quality of service resource negotiation
US11/462,657 2006-08-04

Publications (2)

Publication Number Publication Date
WO2007134054A2 true WO2007134054A2 (en) 2007-11-22
WO2007134054A3 WO2007134054A3 (en) 2008-01-03

Family

ID=38694642

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/068476 WO2007134054A2 (en) 2006-05-10 2007-05-08 Quality of service resource negotiation

Country Status (3)

Country Link
US (3) US7911997B2 (en)
TW (1) TWI360356B (en)
WO (1) WO2007134054A2 (en)

Families Citing this family (74)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8634399B2 (en) * 2006-04-12 2014-01-21 Qualcomm Incorporated Uplink and bi-directional traffic classification for wireless communication
US7911997B2 (en) 2006-05-10 2011-03-22 Intel Corporation Quality of service resource negotiation
CA2711940C (en) 2008-01-14 2017-06-06 Firetide, Inc. Service differentiation and service level agreements for wireless access clients
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US8340634B2 (en) 2009-01-28 2012-12-25 Headwater Partners I, Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US8635335B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc System and method for wireless network offloading
US8626115B2 (en) 2009-01-28 2014-01-07 Headwater Partners I Llc Wireless network service interfaces
US8275830B2 (en) 2009-01-28 2012-09-25 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8406748B2 (en) 2009-01-28 2013-03-26 Headwater Partners I Llc Adaptive ambient services
US8583781B2 (en) * 2009-01-28 2013-11-12 Headwater Partners I Llc Simplified service network architecture
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8725123B2 (en) * 2008-06-05 2014-05-13 Headwater Partners I Llc Communications device with secure data path processing agents
US8548428B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Device group partitions and settlement platform
US8346225B2 (en) 2009-01-28 2013-01-01 Headwater Partners I, Llc Quality of service for device assisted services
US8589541B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8402111B2 (en) 2009-01-28 2013-03-19 Headwater Partners I, Llc Device assisted services install
US8391834B2 (en) 2009-01-28 2013-03-05 Headwater Partners I Llc Security techniques for device assisted services
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US9270559B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US8893009B2 (en) 2009-01-28 2014-11-18 Headwater Partners I Llc End user device that secures an association of application to service policy with an application certificate check
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US8606911B2 (en) 2009-03-02 2013-12-10 Headwater Partners I Llc Flow tagging for service policy implementation
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US10484858B2 (en) 2009-01-28 2019-11-19 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US8745191B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
KR101543803B1 (en) * 2009-04-14 2015-08-12 엘지전자 주식회사 Method and apparatus of processing multicast frame
US20110145393A1 (en) * 2009-12-13 2011-06-16 Tami Ben-Zvi Method for dynamic reservation of cloud and on premises computing resources for software execution
US9019943B2 (en) * 2010-07-29 2015-04-28 Qualcomm Incorporated Systems and methods of communication using tunneled direct link setup (TDLS)
US20170291065A1 (en) * 2016-04-08 2017-10-12 Slacteq Llc Balance measurement systems and methods thereof
US20180001126A1 (en) * 2010-11-18 2018-01-04 Slacteq Llc Balance measurement systems and methods thereof
US9154826B2 (en) 2011-04-06 2015-10-06 Headwater Partners Ii Llc Distributing content and service launch objects to mobile devices
US9426630B2 (en) * 2011-06-27 2016-08-23 Lg Electronics Inc. Method for transmitting and receiving multicast/broadcast frame in wireless local area network and apparatus for the same
US9077701B2 (en) * 2012-01-06 2015-07-07 Futurewei Technologies, Inc. Systems and methods for authentication
US9059830B2 (en) 2012-08-03 2015-06-16 Intel Corporation Device-to-device on-demand advertisement
US10039071B2 (en) 2012-09-07 2018-07-31 Qualcomm Incorporated Systems, apparatus, and methods for association in multi-hop networks
US9144096B2 (en) 2012-09-07 2015-09-22 Qualcomm Incorporated Systems, apparatus, and methods for association in multi-hop networks
US9426837B2 (en) 2012-09-07 2016-08-23 Qualcomm Incorporated Systems, apparatus and methods for association in multi-hop networks
US9100175B2 (en) 2013-11-19 2015-08-04 M2M And Iot Technologies, Llc Embedded universal integrated circuit card supporting two-factor authentication
US9350550B2 (en) 2013-09-10 2016-05-24 M2M And Iot Technologies, Llc Power management and security for wireless modules in “machine-to-machine” communications
US10498530B2 (en) 2013-09-27 2019-12-03 Network-1 Technologies, Inc. Secure PKI communications for “machine-to-machine” modules, including key derivation by modules and authenticating public keys
US10700856B2 (en) 2013-11-19 2020-06-30 Network-1 Technologies, Inc. Key derivation for a module using an embedded universal integrated circuit card
US10057766B2 (en) * 2014-10-21 2018-08-21 Qualcomm Incorporated Methods and systems for authentication interoperability
US9853977B1 (en) 2015-01-26 2017-12-26 Winklevoss Ip, Llc System, method, and program product for processing secure transactions within a cloud computing system
US11246118B2 (en) * 2019-03-26 2022-02-08 Lg Electronics Inc. Method and apparatus for downlink transmission using preconfigured downlink resource

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6490256B1 (en) * 1998-08-31 2002-12-03 Mororola, Inc. Method, subscriber device, wireless router, and communication system efficiently utilizing the receive/transmit switching time
US6594268B1 (en) * 1999-03-11 2003-07-15 Lucent Technologies Inc. Adaptive routing system and method for QOS packet networks
US7031266B1 (en) * 2000-02-25 2006-04-18 Cisco Technology, Inc. Method and system for configuring wireless routers and networks

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6798762B1 (en) * 1998-07-20 2004-09-28 Agere Systems Inc. Digital wireless communication system for simultaneously conveying full rate speech data and dedicated user data
US6327256B1 (en) * 1999-05-28 2001-12-04 Nokia Mobile Phones Limited Apparatus, and associated method, for communicating packet data in a radio communication system
US6947399B1 (en) * 1999-07-19 2005-09-20 Nortel Networks Limited Handoff mechanisms to support real-time delay-critical services in a next generation network
FR2799082B1 (en) * 1999-09-28 2001-11-02 Thomson Multimedia Sa METHOD FOR ASSOCIATING AN APPARATUS IN A COMMUNICATION NETWORK
US6859444B1 (en) * 1999-10-06 2005-02-22 Utstarcom, Inc. Method and apparatus for handover in TDMA mobile communications system
GB2359220A (en) * 2000-02-03 2001-08-15 Orange Personal Comm Serv Ltd Handover in accordance with a network policy
US6970423B2 (en) * 2001-01-18 2005-11-29 Lucent Technologies Inc. Universal mobile telecommunications system (UMTS) quality of service (QoS) supporting asymmetric traffic classes
FI115021B (en) * 2002-12-20 2005-02-15 Nokia Corp Direct upstream access
KR100580244B1 (en) 2003-01-23 2006-05-16 삼성전자주식회사 A handoff method in wirelessLAN
US6922564B2 (en) * 2003-05-30 2005-07-26 Motorola Inc. Admitting data flows to a multiple access network
KR101100157B1 (en) * 2004-06-08 2011-12-28 엘지전자 주식회사 A Method for Handover between Frequency Allocation in Broadband Wireless Access System
US7397775B2 (en) * 2004-10-18 2008-07-08 Motorola, Inc. Method and apparatus for routing calls
US7911997B2 (en) 2006-05-10 2011-03-22 Intel Corporation Quality of service resource negotiation
US7702333B2 (en) 2006-05-11 2010-04-20 Intel Corporation Wireless local area network and methods for secure resource reservations for fast roaming

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6490256B1 (en) * 1998-08-31 2002-12-03 Mororola, Inc. Method, subscriber device, wireless router, and communication system efficiently utilizing the receive/transmit switching time
US6594268B1 (en) * 1999-03-11 2003-07-15 Lucent Technologies Inc. Adaptive routing system and method for QOS packet networks
US7031266B1 (en) * 2000-02-25 2006-04-18 Cisco Technology, Inc. Method and system for configuring wireless routers and networks

Also Published As

Publication number Publication date
TW200807983A (en) 2008-02-01
US20080031204A1 (en) 2008-02-07
US20120087344A1 (en) 2012-04-12
US20110110222A1 (en) 2011-05-12
WO2007134054A3 (en) 2008-01-03
TWI360356B (en) 2012-03-11
US7911997B2 (en) 2011-03-22
US8094612B2 (en) 2012-01-10
US8331293B2 (en) 2012-12-11

Similar Documents

Publication Publication Date Title
US7911997B2 (en) Quality of service resource negotiation
US7769384B2 (en) Mobile broadband wireless access system for transferring service information during handover
US7961684B2 (en) Fast transitioning resource negotiation
EP2763443B1 (en) On-demand services by wireless base station virtualization
US9031240B2 (en) Method and apparatus for updating a key in an active state
US11533610B2 (en) Key generation method and related apparatus
US8081759B2 (en) Apparatus, and an associated method, for facilitating fast transition in a network system
US20100146272A1 (en) Method of controlling information requests
US20110078442A1 (en) Method, device, system and server for network authentication
TW200830901A (en) Handoff method of mobile device utilizing dynamic tunnel
EP2229018B1 (en) Method and system for authenticating in a communication system
US20100189258A1 (en) Method for distributing an authentication key, corresponding terminal, mobility server and computer programs
US20080144579A1 (en) Fast transitioning advertisement
Park Two-way Handshake protocol for improved security in IEEE 802.11 wireless LANs
Zeng et al. A novel cookie-based DDoS protection scheme and its performance analysis
Jang et al. Secure Roaming Optimization for VoIP in 802.11 MAC Layer
Chakaravarthi et al. Optimal data dissemination over wireless network
Gañán et al. Secure handoffs for V2I communications in 802.11 networks
Qi et al. BSS transition optimizations and analysis for VoIP over WLAN
KR20120069460A (en) System and method for providing a personalalization service in wireless lan

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07783450

Country of ref document: EP

Kind code of ref document: A2