HK1153076B - Service differentiation and service level agreements for wireless access clients - Google Patents

Description

Service level agreement and service differentiation for wireless access clients

Technical Field

There is a need for improvements in radio access networks to provide improvements in performance, efficiency, and utility of use.

Background

Unless expressly identified as being publicly or well known, the techniques and concepts used for context, definition, or comparison set forth herein should not be construed as an admission that such techniques and concepts are previously publicly known or are part of the prior art. All references, if any, cited herein, including patents, patent applications, and publications, are hereby incorporated by reference in their entirety for all purposes, whether or not they are specifically incorporated by reference.

Service Level Agreements (SLAs) are a typical way to sell network bandwidth to wireline customers. For example, a customer may have an SLA with (up to) 1.5Mbps bandwidth. The bandwidth may be a total bandwidth (for upstream or downstream) or may be specified as 1Mbps downstream (from the internet/provider to the customer) and 0.5Mbps upstream (from the customer to the internet/provider). Typically, the SLA limits the maximum bandwidth that the customer will receive, but it may additionally specify a guaranteed minimum bandwidth (either full or upstream and downstream) that the customer will receive.

Because the bandwidth on the cable is constant and can be easily controlled, SLAs for bandwidth provisioning and guarantee are more easily supported in wired networks than in wireless networks. On the other hand, wireless bandwidth varies in both time and space due to variations in propagation conditions caused by climate, varying obstacles near the network, interfering devices (e.g., microwaves interfering with Wi-Fi signals), and co-location of multiple wireless networks. Interference and co-location are common, especially when unlicensed frequency bands are used.

Wireless access to network services and the internet is typically provided by a wireless access device of the network, such as a base station (in a cellular network), or an Access Point (AP) in a WLAN, or by a wireless mesh node participating in a mesh network in addition to serving clients. Typically, each wireless access device transmits and receives traffic within a particular geographic area for which coverage is desired. The combination of the areas covered by the radio access devices constitutes the coverage area of the network. Typically, the customer connects to the wireless access network through his laptop, PDA, CPE (customer premises equipment) device, phone, etc. Typically, these devices are referred to as clients with respect to the network. The base stations/APs are interconnected by a network, which may be wireless or wired, and may also interact with a central controller responsible for controlling certain of their activities and configurations. From now on, only the AP will be referred to for simplicity. An example of an existing network of this type is an 802.11 type network.

In the case of a wireless access network serving wireless customers over an unlicensed band (e.g. using the 802.11 family of protocols), it is not possible to provide hard guarantees since some devices (e.g. microwave, cordless phone, baby monitor) are not within the control of the network operator. Because an 802.11 device may not have the latest software, even an 802.11 device may not or cannot comply with SLA policies authorized by a particular network, even though it is using the network service. In addition to clients with the latest software, wireless services networks often have to provide services to such legacy clients.

Reference to the literature

The TCP protocol is described in: postel, J., "Transmission control Protocol-DARPA Internet Program Protocol Specification", RFC793, DARPA, 9 months 1981.

The latest references for the 802.11 standard are: IEEE 802.11, 2007Edition (ISO/IEC 8802-11: 2007) IEEE Standards for Information technology- -Telecommunications and Information Exchange beta systems- -Local and Metropolitan Area networks- -specific requirements- -Part 11: wireless LAN Medium Control (MAC) and physical Layer (PHY) Specification.

All of the foregoing references are incorporated herein by reference for all purposes.

Disclosure of Invention

Summary of the invention

The invention can be implemented in numerous ways, including as a process, an article of manufacture, an apparatus, a system, a composition of matter, and a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links. In this specification, these embodiments, or any other form that the invention may take, may be referred to as techniques. The detailed description provides illustrations of one or more embodiments of the invention that can improve performance, efficiency, and utility of use in the areas identified above. This detailed description includes an introduction to facilitate a faster understanding of the remainder of the detailed description. The introduction includes exemplary embodiments of one or more systems, methods, articles of manufacture, and computer-readable media according to the concepts described herein. As discussed in more detail in the conclusions, the invention encompasses all possible modifications and variations within the scope of the issued claims.

The wireless network 5000 of fig. 5 has a plurality of access nodes (510-1 to 510-5, and as shown in fig. 3 and 4). Each access node has an associated sub-network with associated client devices (e.g., laptop 600-1 associated with access node 510-4, and laptop 600-2 associated with access node 510-5). For the network 5000, devices that are part of the infrastructure of the network 5000 or are provided services by the network are considered internal devices. Devices that are part of the infrastructure of other wireless networks or are not serviced by the network 5000 are considered external devices to the network 5000.

A client device is a non-network infrastructure device to which services are provided by a network infrastructure device. Client devices may include laptops, PDAs, Customer Premises Equipment (CPE), and other types, as appropriate for various use cases. The client devices to which the services are provided over the wireless network 5000 are considered internal client devices. Unless otherwise noted, the internal client devices are associated with a single access node of the wireless network 5000. As will be discussed in more detail, each access node of the wireless network 5000 issues service-related specifications to those internal client devices associated with that access node. Client devices that are incompatible or compatible with respect to the published service-related specification for a particular access node are considered to be incompatible client devices and compatible client devices, respectively, for that particular access node. In addition to legacy devices, the internal client devices associated with a particular access node are compatible client devices for that particular access node. A legacy internal client device that is associated with, but incompatible with, a particular access node is one example of a non-compatible client device for that particular access node. A client device that is not associated with a particular access node, either as an internal device or an external device, is another example of a non-compatible client device for that particular access node.

Each access node subnetwork of figure 5 performs the process of figure 1. In fig. 1, differentiated services are provided by a plurality of techniques commonly performed by each access node and an internal client device associated with the access node. A "target SLA" is determined by the access node (process 100), which specifies an amount of bandwidth that each client device (associated with the access node) is allowed to consume, based on actual SLAs, specified by the network operator/provider for the access node, involving at least some internal client devices. The access node and the internal client device collectively perform rate limiting (process 200) to ensure compliance with the device's target SLA.

For devices with an actual SLA, the target SLA is nominally equal to the actual SLA. However, for various reasons, the access node may (via process 100) temporarily dynamically adjust the client device's target SLA to a value (including zero) that may substantially deviate from the device's rated target SLA (and actual SLA, if any). Although reference to a "target SLA" generally refers to the current target SLA, the term "adjusted target SLA" is sometimes used to emphasize that the current target SLA value may be substantially different from the nominal target SLA value, regardless of its instantaneous value. For example, as will be explained further below, if a client device is observed to be invalid, although its nominal target SLA value (and actual SLA, if any) remains unchanged, the adjusted target SLA may be reduced to zero until the device is restored to being valid.

The release of the service related specification includes the release of a schedule (process 300). Compatible client devices perform their access according to the schedule published by their associated access node (process 400). In this way, the schedule is used in part to manage contention in internal client devices of multiple classes. These schedules are also referred to as a schedule graph 2000 (as shown in detail in fig. 2), and are also used in part to provide priority access to priority internal client devices.

A compatible client device associated with an access node sends usage and bandwidth availability feedback to the access node (process 500). Feedback reflecting network conditions, including realized bandwidth and experienced contention, enables the access node to increase or decrease the mandatory bandwidth (target SLA) of certain compatible devices to ensure that the actual SLAs of other devices are met. The access node performs these processes by developing a better schedule (schedule map) that acts to better manage contention and redistribute access opportunities.

Glossary

An internal device: are a part of the devices of the wireless network that are the focus of attention. The method can comprise the following steps: an AP, a client device, and an internal legacy client device.

An interfering substance: serving as any transmitting or sending source device that causes communication interference with another device. In addition to external interferers, the first internal device is often also an interference source from the perspective of the second internal device.

External interferents: devices that transmit within the same frequency band, either unintentionally (e.g., via harmonics), or in conjunction with different services (modulation/channel schemes) operating within the same frequency band. Examples of external interference sources include: microwave, cordless phone, and baby monitor.

An external device: are not part of the wireless network of interest. For example, it may be a wireless device that is part of another wireless network in the same vicinity. Likewise, external devices may be "interferers" as well as sources of contention.

A client device: internal or external non-network infrastructure devices. When it is an internal device, it is a device served by a network that is a focus of attention.

Compatible device: directly in response to internal devices controlled by the network operator/provider. Including access nodes and client devices other than internal legacy devices.

Unify the device: devices using a unified protocol such as TCP. Even if a unified internal legacy device may respond indirectly to a control, it is not considered a compatible device.

Legacy devices: unless further defined, an internal legacy device and an external legacy device are included.

Internal legacy devices: incompatible internal client devices that are not willing or able to respond directly to the control of the network operator/provider. Because the client device does not have the latest software, the client device typically falls into the legacy device category.

Drawings

Fig. 1 illustrates selected details of an embodiment of providing differentiated services in a wireless access network;

FIG. 2 illustrates selected details of an embodiment of a scheduling map including time slots designated as dedicated (D) and shared (S);

fig. 3 illustrates selected details of an embodiment of an access node from a hardware architecture perspective;

figure 4 shows selected details of an embodiment of an access node from a software architecture perspective; and

fig. 5 illustrates selected details of an embodiment of a wireless access network including a plurality of access nodes, a client device, and internet access.

List of reference numerals in the drawings

Reference numerals	Element name
		100	SLA processing
200	Rate limiting processing
		300	Scheduling table and contention control handling
400	Access restriction handling
		500	Usage feedback processing
510-1	Access node 1
		510-2	Access node 2
510-3	Access node 3
		510-4	Access node 4
510-5	Access node 5
		520-1	Internet access link 1

520-2	Internet access link 2
		530-1	Client link 1
530-2	Client link 2
		600-1	Client device 1
600-2	Client device 2
		700	Internet network
1000	At WConnection handling for providing differentiated services in AN
		2000	Scheduling map
2000-1	Time slot 1(TS1)
		2000-2	Time slot 2(TS2)
2000-N	Time Slot N (TSN)
		3000	Access node hardware aspects
3001.1	Memory bank 1
		3001.2	Memory bank 2
3002	DRAM memory interface
		3003	Flash memory
3004	EEPROM
		3005	Processor with a memory having a plurality of memory cells
3006	Ethernet interface
		3007	Ethernet port
3008	PCI expansion bus
		3009-A	Wireless interface A
3009-N	Wireless interface N
		4000	Access node software aspects
4001	Network management system manager
		4002	Network interface manager
4003	Fault, configuration, charging, performance, and security manager
		4100	Core interface
4101	Routing and transport protocol layer

4102	Layer 2 abstraction layer
		4103	Flash memory file system module
4104	Ethernet driver
		4105	Radio frequency driver
4106	Flash memory driver
		4200	Collective hardware interface
4201	Ethernet interface
		4202	Wireless interface
4203	Flash memory hardware element
		5000	Wireless access network

Detailed Description

A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate selected details of the invention. The invention is described in connection with the examples. It is well known that it is not necessary, nor practical, or possible to exhaustively describe every embodiment of the invention. Accordingly, the embodiments herein should be understood as merely illustrative, and the present invention is not specifically limited to or by any or all embodiments herein, and encompasses numerous alternatives, modifications, and equivalents. To avoid brevity, various descriptors (including, but not limited to, first, last, certain, multiple, further, other, specific, select, certain, and significant) may be applied to distinguish between the various embodiments; these descriptors used herein do not explicitly imply to convey quality, or any form of preference or bias, but merely to distinguish the various groups as a matter of convenience. The order of certain operations of disclosed processes may be altered within the scope of the invention. Whether the various embodiments are used to illustrate variations in process, method, and/or program instruction features, other implementations are contemplated which perform static and/or dynamic selection of one of a plurality of operating modes, respectively corresponding to the various embodiments, according to predetermined or dynamically determined criteria. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not obscured.

Introduction to the design reside in

This introduction is included merely to facilitate a more rapid understanding of the embodiments; the invention is not limited to the concepts presented in the introduction (including obvious embodiments thereof, if any, constituting limitations), as any section of the introduction is necessarily a brief summary of the entire subject matter and is not meant to be an exhaustive or limiting description. For example, the following introduction provides summary information limited by space and organization only for certain embodiments. Numerous other embodiments are set forth throughout the remainder of the specification, including those in which claims ultimately issue.

Although not limited in itself to the current popular definition of an AP, which generally refers to 802.11 APs, the devices that comprise the wireless service network (of fig. 5) and that enforce the wireless SLA are referred to herein as access nodes or Access Points (APs). As the term is used, an AP may be an 802.11AP or any other device that provides connectivity for wireless clients, such as a base station or mesh node. (exemplary hardware and software architectures for access nodes are provided by fig. 3 and 4, respectively.) each device that serves as a client to a wireless access network uses the network through one AP at a time. I.e. the client is associated with the AP. There are two types of SLAs defined for internally compatible client devices: dedicated and shared. The private SLA attempts to reserve a portion of bandwidth at the AP for the internally compatible client devices (associated with the AP) that own the private SLA. On the other hand, a shared SLA means that multiple internally compatible devices (each associated with an AP) can share some portion of the bandwidth and indicate the maximum bandwidth that can be reached by the client device. Although legacy devices and external devices do not have an actual SLA on the wireless network, it is useful for an AP to conceptually impose a pre-configured target SLA on internal legacy devices associated with the AP by attempting to limit the amount of bandwidth that these internal legacy devices can use individually, depending on, for example, device type, or as a group. The SLA may also be dynamically determined based on a customer or device identification that can be used to query stored SLA information.

The 802.11 protocol has two modes of medium access-one is distributed random access (DCF) and the other is AP control mode (PCF). In the latter, all clients that want to send traffic register their intention with the AP, and the AP includes these clients in a polling list. The AP then periodically enters PCF mode, where the AP polls (queries) each client in turn for traffic to send, at which point the client will send some traffic (typically packets) if it has traffic to send. If the client does not have traffic to send at the moment, the slot is wasted. The AP goes through the entire client list, in the same order each time, asking the client if there is traffic to send. The AP may give some clients more slots than others, thus ensuring that some clients have priority access (although only equal access is typically achieved). However, if a device is allocated more time slots without traffic to be transmitted by the device, a longer period of time is wasted. In addition, the PCF cannot implement radio silence (radio silence), so if periodic interference existing around client a always occurs within the time slot allocated to it by the AP, client a may never transmit and the AP will consider that client has no traffic to transmit.

In contrast, the mechanisms presented herein allow devices to have different levels of access to the wireless medium (e.g., certain devices have priority access), while preserving a distributed random access mode of device operation in the network. To this end, some kind of "soft scheduling" is introduced that provides a guide to devices in the network for use rather than absolute broadcast reservation (air reservation). To perform this scheduling, feedback is used to adapt the allocated time to different types of devices with respect to their activity level and channel conditions.

Products available on the market today only implement SLAs as rate limits, i.e. an upper limit on how much traffic a node can transmit (drop its remaining packets) for a certain period of time. Rate limiting is not sufficient because the channel conditions are different, and contention (one node contends with a different number of nodes for broadcast) affects each device to gain access to the medium, so devices that are more important than others may eventually fulfill their SLA less than unimportant devices. To address this issue, several more parts are added to the solution, in addition to rate limiting including scheduling, adaptation based on feedback from the client device.

When discussing priority access, we discuss differentiation between devices rather than traffic types. In the context of 802.11, priority refers to type-based traffic differentiation, e.g., voice packets have a higher priority than video packets, which in turn have a higher priority than best-effort (best-effort) traffic, etc. The contention parameter should be set such that a device seeking to transmit a packet with a higher priority than the packet that another device wants to transmit should be able to access the medium first. Each device may run one or more voice, video, and best effort applications, and thus have multiple traffic streams of each type. These kinds of priorities are independent of the mechanism proposed here. Each device is assigned a priority or class of service relative to the other devices, but in devices seeking to access broadcast/transmit packets, 802.11 type traffic priority will be observed.

SLA defines and expresses: because the quality of the wireless link varies over time, the wireless device may need to use different modulation rates at different times. In particular, higher modulation rates are possible when the link quality is good (low noise level, low loss rate). To maintain control over how much radio resources a device uses, the SLA may be expressed as a function of the modulation rate, so that the amount of broadcast time occupied by the client device is the same regardless of the modulation rate. It prevents devices with poor connectivity from monopolizing network resources and thus depriving devices with good connectivity of airtime (preventing misuse). Example SLA: 0.9Mbps at a modulation rate of 54Mbps, or 0.1Mbps at a modulation rate of 6 Mbps. An internal legacy device can be conceptually viewed as having a default target SLA and being a rate that is restricted not to exceed the preconfigured bandwidth.

And (3) bandwidth allocation: each AP has a certain capacity. Under ideal conditions, this capacity is the rated capacity C. When allocating bandwidth for a dedicated client device, the SLA (upload + download) of the client device is subtracted from the current estimated available bandwidth. Capacity may be allocated on a first come first serve basis, or there may be some minimum allocation for each device type (dedicated, shared, and legacy types), or there may be a fixed allocated bandwidth portion for each device type.

When allocating bandwidth to a shared client device, when such a device can be added by, for example, only allowing the client device to associate with the AP, a restriction may be imposed that the minimum bandwidth available to each shared client device at the AP will still be allowed if a new shared client device is added. For example, if 0.1Mbps is configured to support the minimum bandwidth of a shared client device, and 1Mbps bandwidth is allocated to the shared client device, only 10 such device associations are allowed to be connected. The same rules may be used for legacy devices.

The embodiments discussed elsewhere herein are a class of embodiments in which each client device is associated with a single AP. In an alternative embodiment class, referred to herein as a multi-AP association class, at least some client devices are associated with multiple APs at the same time. In a first embodiment of the multi-AP association class, each client device has a respective actual SLA for each AP with which the client device is associated. In a second embodiment of the multi-AP correlation class, multiple APs associated with a client device collectively enforce a single actual SLA (i.e., at least rate-limit the customer so that it cannot use more than its actual SLA together with all APs).

Exemplary embodiments

Concluding the introduction to the detailed description, a collection of exemplary embodiments follows, including at least the explicit recitation of "EC" (combination of examples), providing additional description of various embodiment types, in accordance with the concepts described herein; these examples are not intended to be exclusive, exhaustive, or limiting; and the invention is not limited to these exemplary embodiments but comprises all possible modifications and variations within the scope of the issued claims.

Ec1. a method of providing differentiated services to at least some of a plurality of client devices, each client device wirelessly connected to an associated access node of a plurality of access nodes of a wireless access network, the method comprising:

for each access node, enforcing a target service level for each client device associated with the access node, and determining service type slot information for at least some client devices associated with the access node;

each client device of the subset of compatible device classes of client devices transmits according to the service type slot information and respective service type indication determined by its associated access node, performs rate limiting according to its target service level, and provides usage and bandwidth availability feedback to its associated access node; and

wherein the service type slot information is updated at least occasionally based at least in part on the feedback.

The method of ec1, further comprising: at least a particular access node of the access nodes is to provide priority access to client devices associated with the particular access node in at least some of the compatible device classes, at least in part via control of the service type slot information by the particular access node.

The method of ec1, further comprising: at least a particular access node of the access nodes manages allocation of bandwidth capacity of the particular access node at least in part via selectively restricting association with at least some of the client devices.

The method of ec1, further comprising: at least a particular one of the access nodes to manage allocation of bandwidth capacity of the particular access node at least in part via control of the service type slot information.

Ec5. the method of ec1, wherein each service type designation is a mutually exclusive one of a priority service type and a general service type.

The method of ec1, further comprising:

each service type indication includes: a mutually exclusive one of the priority service type and the general service type;

the service type slot information determined by the associated access node of the client device includes: designating each of the plurality of time slots as a mutually exclusive one of a priority service time slot and a general service time slot; and

each generic service type client device of the class of compatible devices transmits only in those of the plurality of time slots designated as generic service time slots.

The method of ec6, further comprising:

each priority service type client device of the class of compatible devices transmits only in those of the plurality of time slots designated as priority service time slots.

The method of ec6, further comprising:

each priority service type client device of the class of compatible devices transmits in any number of time slots.

Ec9.ec6, wherein the client devices of the compatible device class are at least partially under the control of a provider operating the radio access network, and are considered internal devices, each priority service time slot is a dedicated time slot, each general service time slot is a shared time slot, each priority service type client device is a dedicated device of the internal device, and each general service type client device is a shared device of the internal device.

Ec10. the method of ec9, further comprising: a dedicated service level agreement (dedicated SLA) is provided between a particular one of the dedicated devices and a provider operating the radio access network, the dedicated SLA corresponding to a target service level for the particular one of the dedicated devices.

Ec11. the method of ec9, further comprising: a shared service level agreement (shared SLA) is provided between a particular one of the sharing devices and a provider operating the radio access network, the shared SLA corresponding to a target service level for the particular one of the sharing devices.

Ec 12.the method of ec9, further comprising: the relative allocation of available bandwidth between the dedicated devices and the shared devices is controlled, at least in part, by adjusting the relative allocation (relative distribution) of the dedicated slots and the shared slots.

Ec13. the method of ec12, further comprising: the relative allocation of dedicated time slots and shared time slots is adjusted based at least in part on a change in an activity level of at least some of the dedicated devices.

Ec 14.the method of ec13, wherein the fraction of shared slots to total slots is increased at least temporarily during periods when at least some of the dedicated devices are relatively inactive.

The method of ec12, further comprising: the relative allocation of dedicated time slots and shared time slots is adjusted based at least in part on changes in the capacity achieved by at least some of the dedicated devices.

Ec 16.the method of ec15, wherein the fraction of dedicated timeslots to total timeslots is increased at least temporarily during periods when at least some of the dedicated devices experience relatively poor link quality.

The method of ec17.ec9, further comprising: the relative allocation of the dedicated time slots and the shared time slots is adjusted to control the relative allocation of available bandwidth between the dedicated devices and the shared devices in order to fulfill a Service Level Agreement (SLA).

Ec18. the method of ec9, further comprising: the relative allocation of the dedicated time slots and the shared time slots is adjusted to control the relative allocation of available bandwidth between the dedicated devices and the shared devices to fulfill a dedicated service level agreement (dedicated SLA) between a particular one of the dedicated devices and a provider operating the radio access network, the dedicated SLA corresponding to a target service level for the particular one of the dedicated devices.

Ec 19.the method of ec9, wherein the service type slot information is an access schedule for the dedicated device and the shared device.

Ec 20.the method of ec9, further comprising: at least a particular one of the access nodes provides priority access to at least some of the dedicated devices associated with the particular access node at least in part by establishing a reduced contention parameter value for the dedicated devices relative to contention parameter values of other client devices.

The method of ec1, further comprising: a Service Level Agreement (SLA) is provided between a customer associated with a particular one of the client devices and a provider operating the wireless access network, the SLA corresponding to a target level of service for the particular one of the client devices.

The method of ec1, further comprising: the usage feedback includes at least one of: packet size, modulation rate, backoff duration, and number of retransmissions.

Ec23. the method of ec1, wherein the access node is an access point and the wireless access network is a wireless local area network.

Ec 24.the method of ec1, wherein the access node is an access point and the wireless access network is a wireless local area network compatible with at least one version of the 802.11 standard.

Ec25. the method of ec1, wherein the access node is a wireless mesh node and the wireless access network is a wireless mesh network.

Ec26. the method of ec1, wherein the access node is a base station and the radio access network is a cellular network.

The method of ec27.ec1, further comprising: the client device includes at least one of the following device types: wireless-enabled desktop computers, wireless-enabled servers, wireless-enabled laptop computers, wireless-enabled tablets, wireless-enabled PDAs, wireless-enabled Customer Premises Equipment (CPE), and wireless-enabled telephones.

The method of ec28.ec1, further comprising: the service type slot information includes designation of each of the plurality of slots as a mutually exclusive one of a priority service slot and a general service slot.

Ec29. the method of ec28, wherein the priority service slots are dedicated slots and the general service slots are shared slots.

Ec 30.the method of ec1, wherein the service type slot information is a scheduling map.

Ec31. the method of ec1, wherein the service type slot information is a scheduling bitmap.

Ec 32.the method of ec1, wherein the service type slot information is a subset of flow control information periodically broadcast by the access node.

The method of ec1, wherein at least some of the target service classes comprise at least a bandwidth allocation.

The method of ec1, wherein at least some of the target service classes comprise at least a maximum bandwidth limit.

Ec 35.the method of ec1, wherein at least some of the target service classes comprise at least a minimum bandwidth guarantee in at least one direction.

The method of ec36.ec1, wherein at least some of the target service levels comprise at least a total minimum bandwidth guarantee for the composite direction.

Ec37.ec1, wherein at least some of the target service classes comprise at least airtime allocations.

The method of ec1, wherein at least some of the target service classes comprise at least a bandwidth allocation of a particular modulation rate.

Ec 39.the method of ec1, wherein the at least some target service classes comprise at least a first bandwidth allocation of a first modulation rate and a second bandwidth allocation of a second modulation rate.

Ec40. the method of ec1, further comprising: for at least a subset of the non-compatible device classes of client devices associated with the access node, each access node performs rate limiting based on a target level of service for each client device associated with the access node.

The method of ec41.ec1, further comprising: each access node performs rate limiting on at least some client devices associated with the access node that exceed its target service level.

The method of ec42.ec40, further comprising: the access node performs at least some rate limiting by dropping packets.

Ec43. the method of ec40, further comprising: the access node performs at least some rate limiting by delaying packets of unified traffic.

The method of ec40, further comprising: the subset of classes of incompatible devices includes incompatible devices of the client device that operate at least sometimes in opposition to at least one of reserved time slot information and a target class of service respectively corresponding to the incompatible devices.

Ec45. the method of ec40, further comprising: the subset of classes of incompatible devices includes incompatible legacy devices of the client device that are not aware of reserved time slot information and target class of service respectively corresponding to the incompatible legacy devices to operate.

The method of ec40, further comprising: the subset of classes of incompatible devices includes incompatible devices of the client device that are not capable of operating according to the reserved time slot information and the target class of service respectively corresponding to the incompatible devices.

The method of ec40, further comprising: the subset of classes of incompatible devices includes incompatible devices of the client device that are not willing to operate according to reserved time slot information and a target service level respectively corresponding to the incompatible devices.

Ec 48.the method of ec1, wherein the subset of compatible device classes and the subset of non-compatible device classes are mutually exclusive.

The method of ec49, further comprising: the access nodes communicate wirelessly with each other.

Ec50. the method of ec1, further comprising: the access nodes communicate with each other via at least some multi-hop wireless links.

Ec51. the method of ec1, further comprising: at least some of the access nodes communicate with each other via a wireless mesh portion of a wireless access network.

The method of ec1, further comprising: the access nodes communicate with each other via cables.

The method of ec53.ec1, further comprising: the access nodes communicate with each other using a combination of wired and wireless technologies appropriate to the operating environment.

The method of ec1, further comprising: the access node communicates with a central server that is at least partially responsible for the behavior and configuration of the access node.

Ec55. the method of ec1, further comprising: the wireless access network provides access to the internet for at least some client devices.

The method of ec56.ec1, further comprising: the wireless access network provides at least some client devices with access to one or more network services.

Ec57. a system for providing differentiated services to at least some of a plurality of client devices, each of the client devices wirelessly connected to an associated access node of a plurality of access nodes of a wireless access network, the system comprising:

each access node having means for enforcing a target service level for each client device associated with the access node, and means for determining service type slot information for at least some of the client devices associated with the access node;

each client device of the subset of compatible device classes of client devices has means for transmitting according to service type slot information and service type indication each determined by an access node of the client device, means for performing rate limiting according to a target service level of the client device, and means for providing usage and bandwidth availability feedback to an associated access node of the client device; and

wherein the service type slot information is updated at least aperiodically based at least in part on the feedback.

Ec58. the system of ec57, further comprising: at least a particular one of the access nodes has means for providing priority access to at least some of the client devices in the class of compatible devices associated with the particular access node at least in part by the means for controlling the service type slot information that the particular access node has.

Ec59. the system of ec57, further comprising: at least a particular access node of the access nodes has means for managing allocation of bandwidth capacity of the particular access node, at least in part by means for selectively restricting association with at least some of the client devices.

Ec 60.the system of ec57, further comprising: at least a particular one of the access nodes has means for managing bandwidth capacity allocation for the particular access node at least in part by means for controlling service type slot information.

Ec61.ec57, wherein each service type designation is a mutually exclusive one of a priority service type and a general service type.

Ec62. the system of ec57, further wherein:

each service type indication includes: a mutually exclusive one of the priority service type and the general service type;

the service type slot information determined by the associated access node of the client device includes: designating each of the plurality of time slots as a mutually exclusive one of a priority service time slot and a general service time slot; and

each generic service type client device of the class of compatible devices transmits only in those of the plurality of time slots designated as generic service time slots.

Ec63. the system of ec62, further wherein:

each priority service type client device of the class of compatible devices transmits only in those of the plurality of time slots designated as priority service time slots.

Ec64. the system of ec62, further wherein:

each priority service type client device of the class of compatible devices transmits in any number of time slots.

Ec65. the system of ec62, wherein: the client devices of the compatible device class are at least partially under the control of a provider operating the wireless access network and are considered internal devices, each priority service time slot is a dedicated time slot, each general service time slot is a shared time slot, each priority service type client device is a dedicated device of the internal device, and each general service type client device is a shared device of the internal device.

Ec66. the system of ec65, further comprising: an access node arrangement for providing a dedicated service level agreement (dedicated SLA) between a particular one of the dedicated devices and a provider operating a radio access network, the dedicated SLA corresponding to a target service level for the particular one of the dedicated devices.

Ec67. the system of ec65, further comprising: an access node arrangement for providing a shared service level agreement (shared SLA) between a particular one of the sharing devices and a provider operating the radio access network, the shared SLA corresponding to a target service level for the particular one of the sharing devices.

Ec68. the system of ec65, further comprising: an access node apparatus for controlling, at least in part, the relative allocation of available bandwidth between the dedicated devices and the shared devices by adjusting the relative allocation of the dedicated time slots and the shared time slots.

Ec69.ec68, further comprising: an access node apparatus to adjust relative allocation of dedicated time slots and shared time slots based at least in part on changes in activity levels of at least some of the dedicated devices.

Ec70.ec69, wherein the fraction of shared slots to total slots is increased at least temporarily during periods when at least some of the dedicated devices are relatively inactive.

Ec71.ec68, further comprising: an access node apparatus for adjusting relative allocation of dedicated time slots and shared time slots based at least in part on changes in capacity achieved by at least some of the dedicated devices.

Ec 72.the system of ec71, wherein the fraction of dedicated timeslots to total timeslots is increased at least temporarily during periods when at least some of the dedicated devices experience relatively poor link quality.

Ec 73.the system of ec65, further comprising: an access node apparatus for adjusting relative allocations of dedicated time slots and shared time slots to control relative allocations of available bandwidth between dedicated devices and shared devices to fulfill a Service Level Agreement (SLA).

Ec 74.the system of ec65, further comprising: access node apparatus for adjusting the relative allocation of dedicated time slots and shared time slots to control the relative allocation of available bandwidth between dedicated devices and shared devices to fulfill a dedicated service level agreement (dedicated SLA) between a particular one of the dedicated devices and a provider operating the radio access network, the dedicated SLA corresponding to a target service level for the particular one of the dedicated devices.

Ec 75.the system of ec65, wherein the service type slot information is an access schedule for the dedicated device and the shared device.

Ec 76.the system of ec65, further comprising: at least a particular one of the access nodes has apparatus for providing priority access to at least some dedicated devices associated with the particular access node at least in part by establishing a reduced contention parameter value for the dedicated devices relative to contention parameter values of other client devices.

Ec77. the system of ec57, further comprising: an access node apparatus for providing a Service Level Agreement (SLA) between a customer associated with a particular one of the client devices and a provider operating a wireless access network, the SLA corresponding to a target service level for the particular one of the client devices.

Ec 78.the system of ec57, further wherein: the usage feedback includes at least one of: packet size, modulation rate, and number of retransmissions.

System and operation

Rate limiting

The download bandwidth and upload bandwidth will be limited to the rate of the SLA (actual SLA or conceptualized target SLA, as appropriate) for each device. As long as a client (associated with an AP) exceeds its SLA, the AP limits the bandwidth usage of the client device in each direction, discards the data packets before transmitting them to the client (in the download direction), and discards the data packets from the client before sending them to the internet. Likewise, to conserve wireless bandwidth, a compatible client device (associated with the AP) will perform rate limiting. Rate limiting may also include traffic shaping in the case of delaying rather than dropping packets. Shaping techniques are particularly useful for rate limiting of unified traffic (e.g., TCP).

Bandwidth usage control

Each AP may periodically broadcast a schedule map that announces which device types are allowed to transmit during each time unit within a period T (e.g., seconds), where a time unit may be defined as a few milliseconds. For example, if a dedicated device associated with an AP has an SLA totaling 5Mbps, while the total capacity of the AP is 20Mbps, then 25% of the slots will be advertised as dedicated slots (indicating that dedicated client devices are allowed to transmit in each such slot) and 75% of the slots will be shared slots (indicating that shared client devices can transmit in each such slot). In some embodiments, a schedule diagram is conceptually illustrated in fig. 2, where each slot is labeled D for dedicated and S for shared. In various embodiments, the scheduling map is implemented as a bitmap, where, for example, dedicated slots are represented by a logical true or value of "1" and shared slots are represented by a logical false or value of "0", or vice versa.

The periodic broadcast of the scheduling map may be combined with other periodic control traffic transmissions, such as piggybacking of beacon packets as is commonly used in wireless access networks today.

In some embodiments, at least some of the dedicated devices are configured to transmit in any time slot in order to provide better service to the selected dedicated devices. The shared device continues to be restricted from transmitting during the shared time slot indicated by the scheduling bitmap. Thus, those devices that are not restricted by the scheduling bitmap can have increased access.

Non-compliant devices for a particular AP, such as internal legacy devices, external legacy devices, and other external devices, will transmit without regard to the scheduling bitmap or may transmit at any time. Since the internal legacy device AP associated with the AP will receive the AP's rate limit, if the internal legacy device uses a unified communication protocol (e.g., TCP), the internal legacy device will gradually adapt its traffic rate to the available/rate-limited bandwidth, and thus its bandwidth usage will be indirectly responsive to the AP's control.

To ensure that high priority packets (e.g., voice packets) do not experience excessive delay, the schedule map needs to ensure that the sequence of consecutive dedicated or shared slots does not exceed a certain length L.

Contention management

By scheduling different types of devices for transmission according to the scheduled time slots, contention in the network is reduced since a smaller number of devices contend for transmission at any given time. Additionally, the dedicated client devices may be given preferential access to the wireless medium relative to the shared client devices and legacy client devices, for example, by reducing contention parameter values (e.g., inter-frame spacing and contention window size) of the dedicated client devices.

In some embodiments, the contention parameter values are modified to further differentiate between dedicated devices and shared devices, but as long as the modification can be done without affecting 802.11 traffic priority: it should not be the case that the modification of the contention window value results in the video traffic of a device gaining access to the medium before the voice traffic of the other device when both devices attempt to access the medium at the same time.

According to an embodiment, to ensure that a client device transmits only within its own slot type, a number of mechanisms are selectively applied:

a) the client device is time synchronized with the AP to ensure that there is a common understanding of when to start advertising the schedule; and

b) one type of packet (e.g., to/from a dedicated device) happens to be queued for transmission at the time the dedicated slot ends and the shared slot begins, it is not transmitted because it will be transmitted in the wrong slot and deprives other types of devices of bandwidth.

Each type of device may have packets with different priorities that may be processed according to their priority, e.g., different contention parameters and queuing may be applied to each priority level (as employed by the current 802.11 standard amendment 802.11 e)

Adjustment of feedback-based estimates

The client device may track its own usage and periodically report the usage to the AP associated with the client device, as well as how much traffic (within the limits of its SLA) the client device wants to send, which is used to indicate whether the device has gained sufficient bandwidth and to track its actual bandwidth requirements. The usage calculation may utilize the following: packet size, modulation rate, number of retransmissions, and backoff duration.

If some dedicated devices are not active for a certain time or they are not fully utilizing their allocations for a certain time, the AP will temporarily set its adjusted target SLA to zero and modify the access schedule to allocate its bandwidth to the shared client device and thus compute the bitmap schedule again. Once the utilization of these dedicated devices increases, their adjusted target SLAs are restored to their nominal target SLAs, and the schedule is adjusted again to accommodate these dedicated devices.

Adjustments due to capacity changes (e.g., when link quality deteriorates) are also performed. If the dedicated client device does not obtain sufficient bandwidth to fulfill its SLA, the access schedule may be modified to allocate more time slots to the dedicated client device.

Node hardware and node software

Figure 3 shows selected details of hardware aspects of an embodiment of an access node. The access node shown comprises: a processor 3005 connected to various types of memory including volatile read/write memory "bank" elements 3001.1 and 3001.2 via a DRAM memory interface 3002, and to non-volatile read/write memory flash 3003 and EEPROM 3004 elements. The processor is also connected to an ethernet interface 3006 providing a plurality of ethernet ports 3007 establishing wired links, and wireless interfaces 3009-a to 3009-N providing radio communication of data packets establishing wireless links. In some embodiments, the wireless interface is compatible with an IEEE 802.11 wireless communication standard or revision (including, but not limited to, any of 802.11-2007, 802.11a, 802.11b, 802.11g, 802.11e, and 802.11 n). The shown partitioning (partioning) is only one example, as other equivalent embodiments of the access node are possible. The access node shown may be used as any one of the nodes shown in fig. 5.

In operation, a processor retrieves instructions from any combination of storage elements (DRAM, flash, and EEPROM) and executes the instructions. Some of the instructions correspond to software related to the various operations discussed above, which operate to: establishing and updating target service levels, rate limiting, creating and updating scheduling graphs, collection and analysis of usage feedback, and other aspects detailed throughout to provide differentiated services to prioritized devices.

Figure 4 illustrates selected details of software aspects of an embodiment of a node. The software shown includes: a Network Management System (NMS) manager 4001 that interfaces to a network interface manager 4002 and a failure, configuration, accounting, performance, and security (FCAPS) manager 4003. In some embodiments, the NMS interfaces between management software running externally to the node and software running internally to the node (e.g., various applications and FCAPS). The network interface manager manages the physical network interfaces (e.g., the wireless interface of the node and the ethernet). The network interface manager assists the NMS in communicating dynamic configuration changes (as requested by the customer) to the FCAPS through the management software. In some embodiments, FCAPS includes functionality to store and retrieve configuration information, and FCAPS functionality serves all applications that require persistent configuration information. FCAPS may also assist in collecting fault information and statistics and performance data from the various operational modules of the node. FCAPS may communicate any portion of the collected information, statistics, and data to the NMS.

Core interface 4100 interfaces the manager to routing and transport protocol layers 4101 and flash file system module 4103. The routing protocol includes the bridge link protocol and software components related to maintaining and referencing bridge tables. Transport protocols include TCP and UDP. The flash file system module interfaces to flash drive 4106, which is conceptually shown as connected to flash hardware elements 4203 representing the flash file system stored in any combination of flash 3003 and EEPROM 3004 of fig. 3. Layer 2 abstraction layer 4102 interfaces routing and transport protocols to ethernet driver 4104 and radio driver 4105, respectively. The ethernet driver is conceptually shown as being connected to an ethernet interface 4201 representing any combination of the ethernet interface 3006 of fig. 3 and other software compatible interfaces. The radio driver is conceptually shown as being connected to a wireless interface 4202 representing any combination of the wireless interface elements 3009-a-3009-N of fig. 3. In some embodiments, the software may also include a serial driver. The software is stored on a computer readable medium (e.g., any combination of DRAM, flash, and EEPROM elements) and executed by a processor. The illustrated partitioning is merely an example, as many other equivalent configurations of layers are possible.

Conclusion

Certain choices have been made in setting forth this disclosure merely for the sake of facilitating text and drawings. These should not be construed as conveying additional information about the structure and operation of the described embodiments in and of itself, unless there is an indication to the contrary. Illustrative examples of such convenient choices include: a specific organization or assignment of designations for reference numbers, and a specific organization or assignment of element identifiers (i.e., labels or numeric designators) for identifying and referring to features and elements of the embodiments.

Although the foregoing embodiments have been described in some detail for purposes of clarity of description and understanding, the invention is not limited to the details provided. There are multiple embodiments of the present invention. The disclosed embodiments are illustrative and not restrictive.

It should be understood that many variations in construction, arrangement, and use are consistent with the present description and are within the scope of the issued patent claims. For example, interconnect and functional unit word widths, clock speeds, and the type of technology used vary according to various embodiments in the various component blocks. The names given to the interconnects and logic are merely illustrative and should not be construed as limiting the concepts described. The order and arrangement of the processes, acts, and functional elements of the flowcharts and flow diagrams may vary according to various embodiments. Additionally, unless expressly stated to the contrary, the value ranges specified, the maximum and minimum values used, or other specific indications are only those of the described embodiments, and it is expected that modifications and variations in the implementation techniques may be tracked and should not be interpreted as limitations.

Functionally equivalent techniques known in the art may be employed in place of those shown to implement the various components, subsystems, functions, operations, procedures, and subroutines. It should also be understood that many functional aspects of the embodiments may be implemented in hardware (i.e., generally as dedicated circuitry) or in software (i.e., by some means of a programmable controller or processor), as a matter of technical trend to implement functions that depend on design constraints, as well as faster processing (which facilitates moving functions previously implemented in hardware to software) and higher integration density (which facilitates moving functions previously implemented in software to hardware). Specific changes in the various embodiments may include, but are not limited to: differences in segmentation; different form factors and configurations; the use of different operating systems and other system software; the use of different interface standards, network protocols, or communication links; and other variations that are contemplated in implementing the concepts described herein based on unique engineering and business constraints of a particular application.

Embodiments are illustrated with details and environmental context well beyond those required for minimal implementation of many aspects of the embodiments described. One of ordinary skill in the art will recognize that certain embodiments omit disclosed elements or features without altering the basic cooperation between the remaining elements. Therefore, it should be understood that many of the specific details disclosed are not required to implement aspects of the described embodiments. To the extent that the remaining elements are distinguishable from the prior art, the omitted components and features are not limited to the concepts described herein.

All such variations in design include insubstantial variations in the teachings conveyed by the described embodiments. It should also be understood that the embodiments described herein have broad applicability to other computing and networking applications and are not limited to the particular application or industry of the described embodiments. The invention is therefore to be understood as embracing all possible modifications and variations encompassed within the scope of the claims of the issued patent.

Claims (18)

1. A method of providing differentiated services to at least some of a plurality of client devices, each of the client devices wirelessly connected to an associated access node of a plurality of access nodes of a wireless access network, the method comprising:

for each of the access nodes, implementing a target service level for each of the client devices associated with the access node and determining service type slot information for at least some of the client devices associated with the access node;

each client device of the subset of compatible device classes of client devices transmits according to the service type slot information and respective service type indication determined by the associated access node of the client device, performs rate limiting according to a target service level of the client device, and provides usage and bandwidth availability feedback to the associated access node of the client device, wherein the client device of the compatible device class is at least partially controlled by a provider operating the wireless access network and considered an internal device; and

wherein the service type slot information is updated at least aperiodically based at least in part on the feedback,

each service type indication comprises a mutually exclusive type of a priority service type and a general service type;

the service type slot information determined by the client device's associated access node comprises: each time slot in the plurality of time slots is used as a type of assignment which is mutually exclusive in a priority service time slot and a common service time slot; and

each generic service type client device of the class of compatible devices transmits in only those of the plurality of time slots designated as the generic service time slots.

2. The method of claim 1, further comprising: at least a particular one of the access nodes provides priority access to at least some of the client devices in the class of compatible devices associated with the particular access node at least in part through control of the service type slot information by the particular access node.

3. The method of claim 1, wherein each of the priority service time slots is a dedicated time slot, each of the general service time slots is a shared time slot, each priority service type client device is a dedicated device of the internal device, and each general service type client device is a shared device of the internal device.

4. The method of claim 3, further comprising: providing a shared service level agreement (shared SLA) between a particular one of the sharing devices and a provider operating the radio access network, the shared SLA corresponding to the target service level of the particular one of the sharing devices.

5. The method of claim 3, further comprising: controlling, at least in part, a relative allocation of available bandwidth between the dedicated device and the shared device by adjusting the relative allocation of the dedicated time slots and the shared time slots.

6. The method of claim 5, further comprising: adjusting the relative allocation of the dedicated time slots and the shared time slots based at least in part on a change in an activity level of at least some of the dedicated devices.

7. The method of claim 5, further comprising: adjusting the relative allocation of the dedicated time slots and the shared time slots based at least in part on a change in capacity achieved by at least some of the dedicated devices.

8. The method of claim 7, wherein the fraction of dedicated time slots to total time slots is increased at least temporarily during periods when at least some of the dedicated devices experience relatively poor link quality.

9. The method of claim 3, further comprising: adjusting the relative allocation of the dedicated time slots and the shared time slots to control the relative allocation of available bandwidth between the dedicated devices and the shared devices to fulfill a dedicated service level agreement (dedicated SLA) between a particular one of the dedicated devices and a provider operating the radio access network, the dedicated SLA corresponding to the target service level for the particular one of the dedicated devices.

10. A system for providing differentiated services to at least some of a plurality of client devices, each of the client devices wirelessly connected to an associated access node of a plurality of access nodes of a wireless access network, the system comprising:

each said access node having means for enforcing a target service level for each said client device associated with said access node, and means for determining service type slot information for at least some said client devices associated with said access node;

each client device of the subset of compatible device classes of client devices having means for transmitting in accordance with the service type time slot information and respective service type indications determined by the access node of the client device, means for performing rate limiting in accordance with a target service level for the client device, and means for providing usage and bandwidth availability feedback to an associated access node of the client device, wherein the client devices of the compatible device classes are at least partially under the control of a provider operating the wireless access network and considered as internal devices; and

wherein the service type slot information is updated at least aperiodically based at least in part on the feedback,

each service type indication comprises a mutually exclusive type of a priority service type and a general service type;

the service type slot information determined by the client device's associated access node comprises: each time slot in the plurality of time slots is used as a type of assignment which is mutually exclusive in a priority service time slot and a common service time slot; and

each generic service type client device of the class of compatible devices transmits in only those of the plurality of time slots designated as the generic service time slots.

11. The system of claim 10, further comprising: at least a particular one of the access nodes has means for providing priority access to at least some of the client devices in the class of compatible devices associated with the particular access node at least in part by the means for controlling the service type slot information that the particular access node has.

12. The system of claim 10, wherein each of the priority service time slots is a dedicated time slot, each of the general service time slots is a shared time slot, each priority service type client device is a dedicated device of the internal device, and each general service type client device is a shared device of the internal device.

13. The system of claim 12, further comprising: an access node arrangement for providing a shared service level agreement (shared SLA) between a particular one of the sharing devices and a provider operating the radio access network, the shared SLA corresponding to the target service level for the particular one of the sharing devices.

14. The system of claim 12, further comprising: an access node apparatus for controlling, at least in part, the relative allocation of available bandwidth between the dedicated device and the shared device by adjusting the relative allocation of the dedicated time slots and the shared time slots.

15. The system of claim 14, further comprising: an access node apparatus to adjust relative allocation of the dedicated time slots and the shared time slots based at least in part on changes in activity levels of at least some of the dedicated devices.

16. The system of claim 14, further comprising: an access node apparatus to adjust relative allocation of the dedicated time slots and the shared time slots based at least in part on a change in capacity achieved by at least some of the dedicated devices.

17. The system of claim 16, wherein the fraction of dedicated time slots to total time slots is increased at least temporarily during periods when at least some of the dedicated devices experience relatively poor link quality.

18. The system of claim 12, further comprising: an access node apparatus for adjusting the relative allocation of the dedicated time slots and the shared time slots to control the relative allocation of available bandwidth between the dedicated devices and the shared devices to fulfill a dedicated service level agreement (dedicated SLA) between a particular one of the dedicated devices and a provider operating the radio access network, the dedicated SLA corresponding to the target service level for the particular one of the dedicated devices.