Network with high-priority enhanced distributed channel access
By broadcasting and negotiating HiP EDCA policies at access points, the access and use of user devices are managed, solving the management challenges of HiP EDCA in Wi-Fi networks and improving network traffic and performance. In particular, it provides improved network performance and guest device experience in automated manufacturing systems.
Patent Information
- Application Number
- CN202580029839.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-22
- Filing Date
- 2025-04-22
- Publication Date
- 2026-11-17
Smart Images

Figure CN123126007A_ABST
Abstract
Description
[0001] Cross-references to related applications This application claims the benefit of co-pending U.S. Provisional Patent Application No. 63 / 637,270, filed April 22, 2024. The aforementioned related patent application is incorporated herein by reference in its entirety. Technical Field
[0002] The embodiments presented in this disclosure generally relate to Wi-Fi networks. More specifically, the embodiments disclosed herein relate to a network using a strategy for High Priority Enhanced Distributed Channel Access (HiP EDCA) (which may also be referred to as Priority Enhanced Distributed Channel Access (P-EDCA)). Background Technology
[0003] Access points in a Wi-Fi network can manage and, in some cases, control access to the wireless transmission medium. User equipment (UEs) and access points can take turns accessing the transmission medium to send and receive messages between each other. HiP EDCA allows certain UEs to obtain higher priority access to the transmission medium (e.g., for certain streams or frames). Attached Figure Description
[0004] To gain a more detailed understanding of the features of this disclosure described above, a more specific description of the disclosure, which has been briefly summarized above, can be obtained by referring to the embodiments, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only typical embodiments and should not be considered limiting; other equivalent embodiments are conceivable.
[0005] Figure 1A An example system is shown.
[0006] Figure 1B It shows Figure 1A Example access points or devices in the system.
[0007] Figure 2A It shows the result of Figure 1A The example operation performed by the system.
[0008] Figure 2B It shows the result of Figure 1A The example operation performed by the system.
[0009] Figure 3 It shows Figure 1A Example HiP EDCA request in the system.
[0010] Figure 4 It shows Figure 1A The example HiP EDCA strategy in the system.
[0011] Figure 5 It shows Figure 1A Example HiP EDCA response in the system.
[0012] Figure 6 It shows the result of Figure 1A The example operation performed by the system.
[0013] Figure 7 It is by Figure 1A A flowchart of an example method executed by an access point in the system.
[0014] Figure 8 It is by Figure 1A A flowchart of an example method executed by a device in the system.
[0015] For ease of understanding, the same reference numerals have been used where possible to refer to the same elements common to all the figures. It is conceivable that elements disclosed in one embodiment may be advantageously used in other embodiments without being specifically described. Detailed Implementation
[0016] Overview This disclosure describes a network using a HiP EDCA policy. According to one embodiment, a wireless access point includes one or more memories and one or more processors communicatively coupled to the one or more memories. The one or more processors perform operations individually or collectively, including: broadcasting a message including a portion of the wireless access point's HiP EDCA policy; and providing access to a transmission medium using HiP EDCA to a user equipment according to the HiP EDCA policy.
[0017] According to another embodiment, a method includes: broadcasting a message comprising a portion of a HiP EDCA policy for a wireless access point; and providing access to a transmission medium using HiP EDCA to a user equipment in accordance with the HiP EDCA policy.
[0018] According to another embodiment, the wireless access point includes one or more memories and one or more processors communicatively coupled to the one or more memories. The one or more processors perform operations individually or jointly, including: receiving a request from a user equipment to use the HiP EDCA access transmission medium; determining that the request conforms to the HiP EDCA policy of the wireless access point; and, in response to determining that the request conforms to the HiP EDCA policy, sending a response to the user equipment granting permission to use the HiP EDCA access transmission medium.
[0019] Example Implementation Some access points and user equipment in a wireless network implement High-Priority Enhanced Distributed Channel Access (HiPEDCA), which can be used to grant some user equipment higher priority access to the wireless transmission medium (e.g., for certain streams or frames). Without proper management, some devices may overuse HiPEDCA or unfairly, leading to congestion, unfairness, and / or failure to achieve one or more of the network's objectives.
[0020] This disclosure describes a network in which an access point manages access to and use of HiP EDCA according to a HiP EDCA policy. Typically, the access point may advertise (e.g., via broadcast or unicast frames) a generic (e.g., device-independent) HiP EDCA policy (e.g., in beacons, in probe / association / reassociation responses). User equipment (UE) may negotiate permission with the access point to use HiP EDCA for UE-specific circumstances. The UE's request may be sent in a (re)association request, and the access point may convey a customized response (instead of the generic response) in the (re)association response. Other frames (e.g., management frames) may be used to negotiate HiP EDCA use after association. During generic announcements and / or negotiations, the access point may instruct the device on parameters and / or restrictions for using HiP EDCA according to the access point's HiP EDCA policy. The access point may convey a concise response including a reason code (e.g., indicating rejection, acceptance, denial, etc., and additional details). If the device agrees to the policies, parameters, and / or restrictions (regardless of how they are expressed), the device can determine that the access point has granted the device access permission to use HiP EDCA. The access point can then monitor the device's use of HiP EDCA and take remedial action if the device violates the HiP EDCA policy.
[0021] In some embodiments, the network offers several technical advantages. For example, the network can control and manage access to and use of HiPEDCA, which can reduce unfairness, congestion, and / or situations where the network fails to achieve its objectives. Therefore, the network can experience improved traffic and performance. For example, if the network supports automated manufacturing, it can provide improved performance for the manufacturing system. As another example, a network providing guest access to devices that want to use HiP EDCA can provide an enhanced experience for those devices.
[0022] Figure 1A An example system 100 is shown, which can be a network deployment providing wireless communication (e.g., Wi-Fi communication). Figure 1AAs shown, system 100 includes one or more access points 102 and multiple devices 104 (which may also be referred to as client devices). Typically, access point 102 maintains and implements HiP EDCA policy, which governs how devices 104 use HiP EDCA to access the transmission medium.
[0023] Access point 102 may be a network device that facilitates wireless communication (e.g., Wi-Fi communication) within system 100. Device 104 is connected to access point 102, and access point 102 can facilitate communication to and from device 104. For example, access point 102 can receive messages from device 104 and direct those messages to their destination. As another example, access point 102 can receive messages destined for device 104 and direct those messages to device 104. Access point 102 can also exchange messages with other access points 102.
[0024] Device 104 can be any suitable device wirelessly connected to access point 102. By way of example and not limitation, device 104 can be a computer, laptop computer, wireless or cellular phone, e-notebook, personal digital assistant, tablet computer, or any other device capable of receiving, processing, storing, or communicating information with other components of system 100. Device 104 can be a wearable device such as a virtual reality or augmented reality headset, smartwatch, or smart glasses. Device 104 may also include a user interaction interface, such as a display, microphone, keyboard, or other suitable terminal device that a user can use. Device 104 may include a hardware processor, memory, or circuitry configured to perform any of the functions or actions of device 104 described herein. For example, a software application designed using software code can be stored in memory and executed by a processor to perform the functions of device 104.
[0025] exist Figure 1AIn the example, system 100 includes devices 104A and 104B. Typically, devices 104A and 104B can access the transmission medium to communicate with access point 102. In some cases, devices 104A and 104B or access point 102 can use HiP EDCA to gain preferential access to the transmission medium. Access point 102 maintains and enforces HiP EDCA policy 108, which governs how and when devices 104A and 104B and / or access point 102 can use HiP EDCA to access the transmission medium. For example, HiP EDCA policy 108 can set restrictions on devices 104A and 104B that are allowed preferential access to the transmission medium, traffic types, flows, transmission opportunities, scheduling information, etc. Access point 102 may apply the same HiP EDCA policy to its use of HiP EDCA, or it may apply a different policy, or a weaker version of the policy to the AP's use of HiP EDCA. When devices 104A and 104B indicate to access point 102 that they can use HiP EDCA, access point 102 may negotiate HiPEDCA use with devices 104A and 104B. For example, device 104A may communicate a request 106A to use HiP EDCA to access the transmission medium (e.g., as a permitted channel access technology). Access point 102 may compare the requested use with HiP EDCA policy 108. If the requested use is permitted under HiP EDCA policy 108, access point 102 may grant device 104A permission to use HiPEDCA. Access point 102 can also communicate response 110A to device 104A to inform device 104A of any restrictions or constraints indicated in HiP EDCA policy 108. If the requested use is not permitted under HiP EDCA policy 108, access point 102 can deny device 104A permission to use HiP EDCA for the requested use and indicate this denial in response 110A. In some cases, access point 102 can also provide an explanation or counterproposal in response 110A that instructs device 104A how to adjust the request so that device 104A is granted permission under HiP EDCA policy 108. For example, access point 102 can indicate adjustments to parameters, traffic types, flows, etc., which will result in permission being granted under HiP EDCA policy 108. Device 104A can adjust the request, and access point 102 can subsequently grant the requested access. Device 104B and access point 102 can similarly use request 106B and response 110B to negotiate HiP EDCA usage.In some cases, a request 106 can be referred to as a HiP EDCA request, and a response 110 can be referred to as a HiP EDCA response.
[0026] In some cases, access point 102 may consider information beyond HiP EDCA policy 108 when negotiating with devices 104A and 104B. For example, when determining whether to allow, deny, or submit a counterproposal and / or determine limitations or constraints on the use of HiP EDCA, access point 102 may consider static and dynamic parameters, including congestion, fairness, and / or the ability to sustainably achieve network objectives (e.g., the objectives of automated manufacturing).
[0027] In some embodiments, access point 102 may pre-announce HiP EDCA policy 108 to devices 104A and 104B. For example, access point 102 may broadcast or convey message 112 received by devices 104A and 104B. Message 112 may instruct access point 102 to allow the use of HiP EDCA according to a portion of HiP EDCA policy 108. Furthermore, message 112 may indicate the aforementioned portion of HiP EDCA policy 108. Devices 104A and 104B may still negotiate HiP EDCA use with access point 102 using request 106 and response 110 as described above. However, in some cases, because message 112 indicates the aforementioned portion of HiP EDCA policy 108, devices 104A and 104B may skip the negotiation using request 106 and response 110 and begin using HiP EDCA with access point 102 if the use conforms to the aforementioned portion of HiP EDCA policy 108. For example, if message 112 indicates that devices 104A and 104B can use HiP EDCA for voice traffic, then devices 104A and 104B can skip the negotiation using request 106 and response 110 for voice traffic. However, devices 104A and 104B can use request 106 and response 110 to negotiate for other types of traffic, such as video traffic.
[0028] In some embodiments, access point 102 may use message 112 to signal whether access point 102 supports HiP EDCA. For example, message 112 may include signaling whether access point 102 supports the Ultra High Rate (UHR) capability element of HiP EDCA. As another example, access point 102 may signal whether access point 102 supports a specific Wi-Fi standard (e.g., 11bn).
[0029] After establishing how HiP EDCA should be used in system 100 with device 104, access point 102 can broadcast a signal (which may be referred to as a delay signal) indicating the start of a time period for using HiP EDCA. This signal can also indicate the duration of the time period. During this time period, device 104, which is permitted to use HiP EDCA, can begin accessing the transmission medium in a preferred access manner. For example, device 104 can back off for a random amount of time before transmitting. Device 104, which is not permitted to use HiP EDCA, can avoid transmitting during the duration. Access point 102 can reuse the HiP EDCA time period any number of times. For example, access point 102 can send another delay signal indicating the duration, and device 104, which is permitted to use HiP EDCA, can again access the transmission medium in a preferred access manner during the duration. Access point 102 and / or device 104 can send acknowledgments to any signals or messages sent by device 104 and / or access point 102.
[0030] If device 104's use of HiP EDCA does not comply with HiP EDCA policy 108, access point 102 may refuse that HiP EDCA use. In some cases, access point 102 may send an unsolicited message to revoke or change HiP EDCA use previously established with device 104. Alternatively or additionally, access point 102 may reduce access to the transmission medium or link, or access point 102 may cause device 104 to deassociate, deauthenticate, or disconnect from access point 102. In this way, access point 102 manages HiP EDCA use according to HiP EDCA policy 108.
[0031] Figure 1B It shows Figure 1A Example access point 102 or device 104 of system 100. For example... Figure 1B As shown, access point 102 and / or device 104 include processor 122, memory 124 and one or more radio devices 126.
[0032] Processor 122 is any electronic circuit, including but not limited to one or a combination of a microprocessor, microcontroller, application-specific integrated circuit (ASIC), application-specific instruction set processor (ASIP), and / or state machine, communicatively coupled to memory 124 and controlling the operation of access point 102 and / or device 104. Processor 122 may be 8-bit, 16-bit, 32-bit, 64-bit, or any other suitable architecture. Processor 122 may include an arithmetic logic unit (ALU) for performing arithmetic and logical operations, processor registers for providing operands to the ALU and storing the results of ALU operations, and a control unit for fetching instructions from memory and executing instructions by directing the coordinated operation of the ALU, registers, and other components. Processor 122 may include other hardware with operating software to control and process information. Processor 122 executes software stored on memory 124 to perform any of the functions described herein. Processor 122 controls the operation and management of access point 102 and / or device 104 by processing information, such as information received from memory 124 and radio device 126. Processor 122 is not limited to a single processing device, but may encompass multiple processing devices contained in the same device or computer or distributed across multiple devices or computers. If multiple processing devices jointly perform a set of functions or actions, processor 122 is considered to have performed that set of functions or actions, even if different processing devices perform different functions or actions within that set.
[0033] Memory 124 may permanently or temporarily store data, operating software, or other information for processor 122. Memory 124 may include any or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example, memory 124 may include random access memory (RAM), read-only memory (ROM), magnetic storage devices, optical storage devices, or any other suitable information storage devices or combinations thereof. Software represents any suitable set of instructions, logic, or code embodied in a computer-readable storage medium. For example, software may be embodied in memory 124, a disk, CD, or flash drive. In certain embodiments, software may include an application executable by processor 122 to perform one or more of the functions described herein. Memory 124 is not limited to a single memory and may encompass multiple memories contained in the same device or computer or distributed across multiple devices or computers. Memory 124 is considered to store a set of data, operating software, or information if multiple memories jointly store a set of data, operating software, or information, even if different memories store different portions of the set of data, operating software, or information.
[0034] Radio device 126 can use different communication technologies to convey messages or information. For example, access point 102 and / or device 104 can use one or more of radio devices 126 to perform Wi-Fi communication. Access point 102 and / or device 104 can use one or more of radio devices 126 to send messages and receive messages. Access point 102 and / or device 104 can include any number of radio devices 126 to communicate using any number of communication technologies.
[0035] Figure 2A It shows the result of Figure 1A The system 100 performs example operation 200. Typically, access point 102 and devices 104A and 104B perform a portion of operation 200. By performing operation 200, access point 102 informs devices 104A and 104B of their access to the transmission medium using HiP EDCA.
[0036] At 202, access point 102 broadcasts a message to user equipment 104A and 104B to pre-announce HiP EDCA policy 108 to devices 104A and 104B. This message may instruct access point 102 to allow the use of HiP EDCA according to a portion of HiP EDCA policy 108. Furthermore, message 112 may indicate the aforementioned portion of HiP EDCA policy 108. In this way, access point 102 informs devices 104A and 104B of the aforementioned portion of HiP EDCA policy 108 without devices 104A and 104B needing to negotiate HiP EDCA usage with access point 102. In some embodiments, message 112 may be a beacon, probe response, (re)association response, Fast Initial Link Establishment (FILS) discovery frame, beacon frame, association response frame, reassociation response frame, etc. At 204 and 206, devices 104A and 104B relay the response back to access point 102. The response can be an acknowledgment of a message broadcast by access point 102. In some cases, in addition to or as a substitute for message 112, access point 102 may broadcast or provide HiP EDCA policy 108 in beacon frames, probe response frames, FILS discovery frames, association response frames, reassociation response frames, or SCS response frames.
[0037] In some embodiments, message 112 includes one or more channel access parameters to be used for accessing the channel using HiP EDCA. For example, message 112 may include the Arbitration Inter-Frame Spacing Number (AIFSN) to be used for HiP EDCA contention. As another example, message 112 may include one or more parameters indicating the minimum contention window (CWmin) and / or maximum contention window (CWmax) to be used for HiP EDCA contention. As yet another example, message 112 may include transmission opportunity constraints to be used for HiP EDCA.
[0038] In some cases, after access point 102 broadcasts message 112, devices 104A and 104B can still... Figure 1A and Figure 2B The HiP EDCA usage is negotiated with access point 102 as discussed (e.g., if message 112 indicates that negotiation is normally or under certain circumstances). However, in some cases, due to the portion of HiP EDCA policy 108 indicated by the message, devices 104A and 104B can skip negotiation and begin using HiP EDCA with access point 102 if the portion conforming to HiP EDCA policy 108 is used. For example, if the message indicates that devices 104A and 104B can use HiPEDCA for voice traffic, devices 104A and 104B can skip negotiation for voice traffic. However, devices 104A and 104B can negotiate for other types of traffic, such as video traffic.
[0039] Figure 2B It shows the result of Figure 1A The system 100 performs example operation 220. Typically, access point 102 and devices 104A and 104B perform a portion of operation 220. By performing operation 220, access point 102 and devices 104A and 104B determine the nature of their access and / or negotiate access to the transmission medium using HiP EDCA.
[0040] At 222, device 104A sends a HiP EDCA request to access point 102. Using this HiP EDCA request, device 104A requests preferential access to the transmission medium. Access point 102 compares the request with HiP EDCA policy 108 and / or resource levels (e.g., available and / or consumed; considering both radio medium resources and internal access point resources) maintained by access point 102 to determine whether the HiP EDCA request complies with HiP EDCA policy 108 and / or resource levels (e.g., whether it is below a resource level threshold or limit). For example, access point 102 may determine whether HiP EDCA policy 108 allows device 104A to use HiP EDCA. As another example, access point 102 may determine whether the HiP EDCA request is for a traffic type or flow for which HiP EDCA policy 108 allows device 104A to use HiP EDCA.
[0041] exist Figure 2B In the example, access point 102 can determine that the HiP EDCA request conforms to HiP EDCA policy 108 and / or resource level. Access point 102 then generates a HiP EDCA response and communicates it to device 104A at 224. The HiP EDCA response can indicate to device 104A that the HiP EDCA request has been granted.
[0042] At 226, device 104B sends a HiP EDCA request to access point 102. Using this HiP EDCA request, device 104B requests preferential access to the transmission medium. Access point 102 compares the request with HiP EDCA policy 108 and / or resource level maintained by access point 102 to determine whether the HiP EDCA request conforms to HiP EDCA policy 108 and / or resource level. For example, access point 102 may determine whether HiP EDCA policy 108 allows device 104B to use HiP EDCA. As another example, access point 102 may determine whether the HiP EDCA request is for a traffic type or flow that HiP EDCA policy 108 allows device 104B to use HiPEDCA.
[0043] exist Figure 2BIn the example, access point 102 can determine that a HiP EDCA request from device 104B does not conform to HiPEDCA policy 108 and / or resource level. Access point 102 then generates a HiP EDCA response and communicates it to device 104B at 228. The HiP EDCA response can indicate to device 104B that the HiP EDCA request has been rejected. In some cases, the HiP EDCA response can indicate the reason or explanation for the rejection. For example, the HiP EDCA response can indicate aspects of the HiP EDCA request that can be modified so that access point 102 grants the HiP EDCA request (which may be referred to as a counterproposal). For example, the HiPEDCA response can indicate that the HiP EDCA request should be restricted to certain traffic types or flows. Device 104B can modify the HiP EDCA request based on the information in the HiPEDCA response, and access point 102 can subsequently grant the HiP EDCA request.
[0044] As described above, access point 102 and devices 104A and 104B can be used without performing... Figure 2A In the case of operation 200 shown, or in combination Figure 2A The operation 200 shown is used to perform operation 220. For example, device 104A and / or device 104B can perform operation 220 to negotiate HiPEDCA usage if access point 102 has not previously advertised HiP EDCA policy 108 to devices 104A and 104B. As another example, device 104A and / or device 104B can perform operation 220 to negotiate HiP EDCA usage (e.g., negotiating HiP EDCA usage not covered by policy 108) after access point 102 has already advertised HiP EDCA policy 108 to devices 104A and 104B.
[0045] In some embodiments, device 104 and / or access point 102 may use HiP EDCA requests and HiP EDCA responses to signal whether device 104 and / or access point 102 supports HiP EDCA. For example, HiP EDCA requests and HiPEDCA responses may include signaling whether device 104 and / or access point 102 supports Ultra High Rate (UHR) capability elements of HiP EDCA. As another example, device 104 and / or access point 102 may signal whether device 104 and / or access point 102 supports a specific Wi-Fi standard (e.g., 11bn). This signaling may be sent in beacons, probes, probe responses, reassociation requests, reassociation responses, etc.
[0046] Figure 3 It shows Figure 1AExample HiP EDCA request 302 in system 100. Typically, a user equipment may communicate HiP EDCA request 302 to an access point to negotiate preferential access to the transmission medium using HiP EDCA.
[0047] like Figure 3 As shown, the HiP EDCA request 302 includes one or more sections that indicate different information regarding preferred access. For example, the HiP EDCA request 302 may include section 304, which includes one or more identifiers (e.g., Access Category (AC) identifiers, one or more Traffic Identifiers (TIDs), etc.). Each identifier may identify a specific traffic type (e.g., voice traffic, video traffic, data traffic, etc.). The identifiers in section 304 may indicate the type of traffic for which the request for preferred access to the transmission medium is directed. In some embodiments, section 304 includes a list of identifiers and / or a bitmap for the identifiers (e.g., each bit corresponds to a traffic type / traffic identifier).
[0048] As another example, HiP EDCA request 302 may include section 306, which identifies one or more traffic flows or characteristics of the flow (Traffic Specification (TSPEC) element, Flow Classification Service Identifier (SCS ID), Quality of Service (QoS) characteristic element, (one or more) Traffic Classification (TCLAS) element, Fully Qualified Domain Name (FQDN), Uniform Resource Identifier (URI), Uniform Resource Locator (URL), Application Identifier, or the like). Each traffic flow may include the traffic source that generates the flow destined for the device. For example, section 306 may identify a streaming media service that generates the traffic flow destined for the device. As another example, section 306 may identify a website that generates the traffic flow destined for the device. Section 306 may indicate the traffic flow for which a request for preferential access to the transport medium is directed. In some embodiments, section 306 may be a TCLAS element in HiP EDCA request 302. The traffic classification element may include one or more parameters that identify an incoming frame with a particular traffic flow, and thus link it to a particular TSPEC.
[0049] As another example, HiP EDCA request 302 may include section 308, which identifies one or more target wake-up time scheduling information. This scheduling information may indicate the time when a device and / or access point wakes up to access the transport medium (e.g., using HiP EDCA) (or the time when either device is unavailable). Therefore, the information in section 308 may indicate the time when a device can (or can not) use HiP EDCA to access the transport medium.
[0050] Figure 4 It shows Figure 1AThe example HiP EDCA policy 108 in system 100. Typically, access points can maintain and use HiP EDCA policy 108 to determine whether preferential access to the transmission medium should be granted or denied. In some cases, access points can use HiP EDCA policy 108 to determine how requests for preferential access should be tailored to conform to HiP EDCA policy 108.
[0051] like Figure 4 As shown, HiP EDCA policy 108 may include information governing how priority access to the transport medium should be provided. For example, HiP EDCA policy 108 may include section 402, which indicates whether HiP EDCA is enabled or disabled. If HiP EDCA is disabled, all HiP EDCA requests for the access point can be rejected. If HiP EDCA is enabled, HiP EDCA requests for the access point can be granted.
[0052] As another example, HiP EDCA policy 108 may include section 404, which identifies one or more devices. The identified devices may be granted preferential access to the transmission medium. If a device not identified in section 404 sends a HiP EDCA request to the access point, the access point may reject the HiP EDCA request. If a device identified in section 404 sends a HiP EDCA request to the access point, the access point may grant the HiP EDCA request.
[0053] As another example, HiP EDCA policy 108 may include section 406, which includes one or more identifiers (e.g., traffic identifiers, access class identifiers, frame types, etc.). The identifiers may identify specific traffic types (e.g., voice traffic, video traffic, data traffic, etc.) or frame types that are given preferential access to the transmission medium. If a device sends a HiP EDCA request that includes an identifier not included in section 406, the access point may reject the HiP EDCA request. If a device sends a HiP EDCA request that includes an identifier included in section 406, the access point may grant the HiP EDCA request.
[0054] As another example, HiP EDCA policy 108 may include section 408, which identifies one or more traffic flows or characteristics of traffic flows (e.g., TSPEC element, SCS ID, QoS characteristic element, (one or more) TCLAS element, FQDN, URI, URL, application identifier, or the like). For example, section 408 may identify one or more sources of the traffic flow. If a device sends a HiP EDCA request identifying a traffic flow not included in section 408, the access point may reject the HiP EDCA request. If a device sends a HiP EDCA request identifying a traffic flow included in section 408, the access point may grant the HiP EDCA request.
[0055] As another example, the HiP EDCA strategy 108 may include a portion 410 indicating a transmission opportunity (TXOP) limit, which may be an upper limit on the number of HiP transmission opportunities, elapsed time, number per time, number of contentions per contention, number of failed contentions per failed contention, number of consecutive failed contentions per failed contention, or elapsed time duty cycle; or conversely, it may be a lower limit, such as the minimum time, contention, failed contention, or consecutive failed contention between HiP EDCA opportunities. Although an access point may grant priority access using HiP EDCA, the transmission opportunity limit may restrict the number of transmission opportunities, elapsed time, number per time, number of contentions per contention, number of failed contentions per failed contention, number of consecutive failed contentions per failed contention, or elapsed time duty cycle that may be allowed priority access to the transmission medium. In some embodiments, the limit may be expressed as a linear value or as a value expressed in mantissa and exponent with various units associated with the parameter being signaled. For example, for time, the unit of the limit may be 1 microsecond, 8 microseconds, and / or 16 microseconds or transmission units. For the duty cycle, the limit can be signaled using an unsigned N field, where power(2, N-1) indicates 100%. For the rate, a scaling value can be used.
[0056] As another example, HiP EDCA policy 108 may include section 412, which indicates one or more SCS, TSPEC, or QoS parameters or characteristics. Section 412 may also include traffic and / or access class identifiers. The information in section 412 can be used to determine whether certain flows or traffic or access class identifiers are eligible for HiP EDCA. If a device sends a HiP EDCA request that includes a traffic or access class identifier that matches the identifier, parameter, or characteristic in section 412, or identifies a flow with an SCS or QoS parameter or characteristic that matches the identifier, parameter, or characteristic in section 412, the access point may grant the HiP EDCA request. If a device sends a HiP EDCA request that includes a traffic or access class identifier that does not match the identifier, parameter, or characteristic in section 412, or identifies a flow with an SCS or QoS parameter or characteristic that does not match the identifier, parameter, or characteristic in section 412, the access point may reject the HiP EDCA request.
[0057] As another example, HiP EDCA policy 108 may include section 414, which includes one or more target wake-up time scheduling information, indicating whether a device may or may not have priority access to the transmission medium. If a device sends a HiP EDCA request that includes a target wake-up time schedule conforming to the target wake-up time schedule in section 414, the access point may grant the HiP EDCA request. If a device sends a HiP EDCA request that includes a target wake-up time schedule that does not conform to the target wake-up time schedule in section 414, the access point may reject the HiP EDCA request. In some cases, the target wake-up time schedule for the device may be dynamically calculated or pre-allocated for the device.
[0058] As another example, HiP EDCA policy 108 may include section 416, which includes a Differentiated Service Code Point (DSCP) policy or QoS mapping. The DSCP policy or QoS mapping may classify or map certain traffic based on application or service type. In some cases, the DSCP policy or QoS mapping can prevent devices from incorrectly identifying traffic as requiring preferential access (e.g., using incorrect traffic identifiers). Therefore, an access point can use the DSCP policy or QoS mapping to check whether certain traffic is allowed preferential access to the transmission medium. This check can occur on the first request or subsequently after the access point has analyzed the actual traffic sent using HiP EDCA.
[0059] As another example, HiP EDCA policy 108 may include section 418. Section 418 identifies one or more external specifications. These external specifications may be required for HiP operation and may identify the corresponding exchange (e.g., the Wi-Fi Alliance Differential Service Code Point Policy). The access point may refer to or use these external specifications when determining whether to grant preferential access to the transport medium. This check may occur on the first request or subsequently after the access point has analyzed the actual traffic sent using HiPEDCA.
[0060] As another example, HiP EDCA policy 108 may include a portion 420 that includes one or more links. HiP EDCA policy 108 may apply to links identified in portion 420, or to all links not identified in portion 420. Access points may use portion 420 to determine whether HiP EDCA policy 108 should apply to a particular link. In some embodiments, portion 420 may be a UHR operation element or a variant of another policy element or multi-link element, which may be sent in a beacon or probe response.
[0061] HiP EDCA policy 108 may include section 422, which indicates additional conditions for using HiP EDCA. Before granting priority access to the transport medium, section 422 may include one or more thresholds (e.g., the number of transmission failure thresholds that should be observed for frames, a resource level threshold, a congestion level threshold, etc.). For example, if too many user equipments are using HiP EDCA for too many flows or traffic types, and the resource level is below a threshold and / or the congestion level exceeds a threshold (e.g., collision rate, distribution of the first HiP time slots used, etc.), the access point may not allow new or additional HiPEDCA usage. The access point may also cancel or renegotiate HiP EDCA usage with some devices. In some cases, section 422 may indicate which frame types (e.g., only data frames or both administrative and data frames) can trigger HiP EDCA. As another example, section 422 may indicate the number of transmission failure thresholds (which may be referred to as a retry count) that a device should experience before receiving priority access to the transport medium.
[0062] HiP EDCA policy 108 may include section 424, which indicates additional information related to the use of HiP EDCA. For example, section 424 may indicate the number of consecutive HiP EDCA attempts or transmissions allowed by the access point. If the number of HiP EDCA attempts or transmissions performed by the device reaches or exceeds this number, the access point may refuse further HiP EDCA attempts or transmissions from the device. As another example, section 424 may indicate whether the device should perform flow-level negotiation with the access point before the access point will allow the use of HiP EDCA (e.g., for a specific flow). As yet another example, section 424 may indicate whether the access point will negotiate and potentially allow the use of HiP EDCA for traffic that otherwise does not conform to HiP EDCA policy 108.
[0063] Figure 5 It shows Figure 1A The example HiP EDCA response 502 in system 100. Typically, an access point can communicate a HiP EDCA response 502 to a device to indicate to that device whether priority access has been granted or denied.
[0064] like Figure 5 As shown, the HiP EDCA response 502 includes a portion 504 indicating whether the HiP EDCA request is accepted, rejected, or counter-proposal is made. If the HiP EDCA request is accepted, the device's preferential access to the transmission medium can be allowed according to the access point's HiP EDCA policy. If the HiP EDCA request is rejected, the device's preferential access to the transmission medium can be disallowed.
[0065] If a HiP EDCA request is counterproposed, the HiP EDCA response 502 may include a portion 506 containing a proposal. This proposal may indicate changes to the HiP EDCA request that, if made, would allow the access point to grant preferential access to the transport medium according to the HiP EDCA policy. For example, the proposal may indicate changes to the traffic identifier, flow, and / or target wake-up time scheduling information indicated in the HiP EDCA request. The proposal may indicate limits on the amount of HiP contention, the number of HiP transmission opportunities, elapsed time, number per time, number of contentions per instance, number of failed contentions per instance, number of consecutive failed contentions per instance, or the elapsed time duty cycle. The device may submit a new HiPEDCA request based on this proposal and send the modified HiP EDCA request to the access point. The access point may then grant the modified HiPEDCA request. In this way, the access point can control how the device obtains preferential access to the transport medium.
[0066] In some embodiments, for some message exchanges, HiP EDCA requests and / or HiP EDCA responses may be part of SCS request and / or report or response frames. An SCS request may request the use of HiP EDCA for the flow and / or traffic identifier for which the SCS flow was created, or it may request the use of HiP EDCA for certain Access Classes (ACs). This can be achieved by requesting HiP EDCA use using bits or fields in a QoS feature element or another field within an SCS descriptor element; and / or by indicating the set of parameters for which the HiP EDCA request is made (e.g., AC, TID, TCLAS, or the SCS ID for the flow). The access point may indicate in the SCS response whether it allows the use of HiP EDCA for the requested SCS flow and / or traffic identifier. In the SCS response, the access point may also indicate that HiP EDCA is allowed for a smaller or alternative set of traffic types. For example, if a device requests the use of HiP EDCA for TID 4 and 5, the access point can allow HiP EDCA only for TID 5 and indicate this in the SCS response. In another example, if a device requests the use of HiP EDCA for access classes AC_BE and AC_VI, the access point can allow HiP EDCA only for AC_VI and indicate this in the SCS response.
[0067] Figure 6 It shows the result of Figure 1A The system 100 performs example operation 600. Typically, access point 102 and device 104 perform operation 600 for HiP access. By performing operation 600, device 104 obtains preferential access to the transmission medium.
[0068] Prior to performing operation 600, access point 102 and / or device 104 may have negotiated preferential access to the transmission medium (i.e., HiP EDCA) (e.g., using...). Figure 2A and / or Figure 2B(See operations 200 and / or 220). When device 104 and / or access point 102 determines that priority access to the transmission medium is required, device 104 and / or access point 102 may broadcast a delay signal at 602. The delay signal may indicate to access point 102 and other nearby devices that device 104 and / or access point 102 has initiated HiP EDCA contention. The delay signal may indicate the duration for which HiP EDCA is used. Conventional (HIP-unaware and HiP-disallowed) devices wait for the duration indicated by the delay signal. Then, HiP-enabled devices, including device 104, may compete for access to the transmission medium during the protected duration. Access point 102 may monitor the use of the delay signal to confirm that the associated device 104 has performed the necessary negotiation with access point 102 and has priority access in accordance with access point 102's HiP EDCA policy 108.
[0069] At point 604, the device that wins the HiP contention (hereinafter referred to as device 104) conveys one or more messages to access point 102. For example, device 104 may gain priority access to the transmission medium to wirelessly send messages to access point 102. Access point 102 may then confirm that the message transmission conforms to HiP EDCA policy 108.
[0070] If access point 102 determines that device 104 does not comply with HiP EDCA policy 108, whether during this single HiP contention or after a behavior pattern during a recent HiP contention, access point 102 may communicate a message to device 104 at 606. This message may instruct access point 102 to take remedial action in response to the violation of HiP EDCA policy 108. For example, the message may instruct access point 102 to revoke or modify a pre-established negotiation with the device regarding HiP EDCA operations. Message 606 may be an unsolicited management frame listing revised negotiations for HiP EDCA operations. As another example, the message may instruct access point 102 to reduce access to one or more links (e.g., using load balancing) in response to a violation of the HiP EDCA policy. As yet another example, the message may instruct access point 102 to deassociate with or deauthenticate device 104 in response to a violation of the HiP EDCA policy.
[0071] Figure 7 It is by Figure 1A The flowchart illustrates an example method 700 executed by an access point (e.g., access point 102) in system 100. By executing method 700, the access point negotiates HiP EDCA usage with the device.
[0072] At 702, the access point receives a HiP EDCA request from the device. The HiP EDCA request may indicate the requested aspect of preferential access to the transport medium. For example, the HiP EDCA request may indicate a request for HiP EDCA for certain traffic identifiers or to identify certain traffic flows. In some embodiments, the access point may advertise a portion of its HiP EDCA policy before 702.
[0073] At 704, the access point can determine whether the HiP EDCA request conforms to the access point's HiP EDCA policy. For example, the access point can compare information in the HiP EDCA request with information in the HiP EDCA policy. If the HiP EDCA request conforms to the HiP EDCA policy (and / or resource level), the access point grants permission at 706. This grant may include limits on HiP usage or rate. If the HiP EDCA request does not conform to the HiP EDCA policy, the access point denies permission at 708. In some embodiments, in addition to denying permission, the access point includes a counterproposal that indicates changes to the HiP EDCA request that would cause the access point to grant permission. The device can modify the HiP EDCA request based on the counterproposal.
[0074] Figure 8 It is by Figure 1A The flowchart illustrates an example method 800 performed by a device (e.g., device 104) in system 100. By performing method 800, the device negotiates HiP EDCA usage with the access point.
[0075] At 802, the device sends a HiP EDCA request to the access point. A HiP EDCA request can indicate the requested aspect of preferential access to the transmission medium. For example, a HiP EDCA request can indicate a request for HiP EDCA for certain traffic identifiers or to identify certain traffic flows.
[0076] At 804, the device receives a HiP EDCA response from the access point. The HiP EDCA response can indicate whether the HiP EDCA request complies with the access point's HiP EDCA policy and / or resource level. If the HiP EDCA request complies with the HiP EDCA policy and / or resource level, the HiP EDCA response can indicate that the HiP EDCA request is granted. This grant may include limits on HiP usage or rate. If the HiP EDCA request does not comply with the HiP EDCA policy, the HiP EDCA response can indicate that the HiPEDCA request is rejected. Furthermore, the HiP EDCA response can indicate possible changes to the HiP EDCA request to allow the access point to grant the HiP EDCA request. The device can modify the HiP EDCA request based on the information in the HiP EDCA response and resubmit the HiPEDCA request to the access point. The access point can then grant permission.
[0077] In summary, the network includes access point 102, which manages access to and use of HiP EDCA through HiP EDCA policy 108. Typically, access point 102 can announce the HiP EDCA policy, and / or user equipment 104 can negotiate permission to use HiP EDCA with access point 102. Before or during negotiation, access point 102 can instruct device 104 on parameters and / or restrictions for using HiP EDCA according to access point 102's HiP EDCA policy 108. If device 104 agrees to the parameters and / or restrictions, access point 102 can grant access permission to use HiP EDCA. Access point 102 can then monitor device 104's use of HiP EDCA and take remedial measures if device 104 violates the HiP EDCA policy.
[0078] Various embodiments have been referenced in this disclosure. However, the scope of this disclosure is not limited to the specific embodiments described. Rather, any combination of the described features and elements (whether or not related to different embodiments) is contemplated for implementing and practicing the contemplated embodiments. Furthermore, when elements of an embodiment are described in the form of “at least one A and B” or “at least one A or B,” it should be understood that embodiments specifically including element A, embodiments specifically including element B, and embodiments including elements A and B are all contemplated. Moreover, while some embodiments disclosed herein may achieve advantages over other possible solutions or over the prior art, whether a particular embodiment achieves a particular advantage does not limit the scope of this disclosure. Therefore, the aspects, features, embodiments, and advantages disclosed herein are merely illustrative and should not be considered elements or limitations of the appended claims(s) unless expressly recited in the claims. Similarly, references to “the invention” should not be construed as a generalization of any inventive subject matter disclosed herein and should not be considered elements or limitations of the appended claims(s) unless expressly recited in the claims.
[0079] As those skilled in the art will understand, the embodiments disclosed herein can be embodied as systems, methods, or computer program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, which can be collectively referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of computer program products embodied in one or more computer-readable media having computer-readable program code embodied thereon. In one example, a computer-readable medium carrying instructions that, when executed by one or more processors, cause any of the methods described herein to be performed.
[0080] Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, or any suitable combination thereof.
[0081] Computer program code used to perform the operations of embodiments of this disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, Smalltalk, C++, etc., and traditional procedural programming languages such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet provided by an Internet service provider).
[0082] This document describes aspects of the present disclosure with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments set forth in this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks in the flowchart illustrations and / or block diagrams.
[0083] These computer program instructions may also be stored in a computer-readable medium that can instruct a computer, other programmable data processing apparatus or other device to operate in a particular manner, such that the instructions stored in the computer-readable medium produce an article of writing including instructions that implement the functions / actions specified in one or more boxes in a flowchart illustration and / or block diagram.
[0084] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus or other equipment to cause a series of operational steps to be performed on the computer, other programmable apparatus or other equipment, thereby producing a computer-implemented process, such that the instructions, which execute on the computer, other programmable data processing apparatus or other equipment, provide a process for implementing the functions / actions specified in one or more boxes in a flowchart diagram and / or block diagram.
[0085] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments. In this regard, each block in a flowchart or block diagram may represent a module, segment, or code portion, comprising one or more executable instructions for implementing one or more specified logical functions. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the functions involved. It will also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware, or a combination of dedicated hardware and computer instructions, that performs the specified functions or actions.
[0086] In view of the foregoing, the scope of this disclosure is defined by the appended claims.
Claims
1. A wireless access point, comprising: One or more memory units; as well as One or more processors, communicatively coupled to the one or more memories, are configured to perform operations individually or jointly, including: The broadcast includes a message that is part of the high-priority enhanced distributed channel access (HiP EDCA) policy of the wireless access point; as well as According to the HiP EDCA strategy, user equipment is provided with access to the transmission medium using HiP EDCA.
2. The wireless access point of claim 1, wherein, The operation also includes: After broadcasting the message, a request to access the transmission medium using HiP EDCA is received from the user equipment; Determine that the request conforms to the HiP EDCA policy of the wireless access point; and In response to determining that the request conforms to the HiP EDCA policy, a response granting permission to access the transmission medium using HiP EDCA is sent to the user equipment.
3. The wireless access point of claim 2, wherein, The operation also includes: Receive a second request from the second user equipment to access the transmission medium using HiP EDCA; It is determined that the second request does not conform to the HiP EDCA policy; and In response to determining that the second request does not conform to the HiP EDCA policy, a second response is sent to the second user equipment, wherein the second response indicates an adjustment to the second request.
4. The wireless access point of claim 2 or claim 3, wherein, The operation further includes: in response to determining that the user equipment is violating the HiP EDCA policy, performing at least one of the following: Revoke the license to use HiP EDCA to access the transmission medium; and / or Disconnect from the user equipment.
5. The wireless access point of any of claims 2 to 4, wherein, The request identifies one or more traffic types or one or more traffic flows, and wherein determining that the request conforms to the HiP EDCA policy includes: determining that the HiP EDCA policy allows access to the transmission medium using HiPEDCA for the one or more traffic types or the one or more traffic flows.
6. The wireless access point of claim 5, wherein, The response grants a license to access the transmission medium using HiP EDCA for a subset of the one or more traffic types or a subset of the one or more traffic flows.
7. The wireless access point of claim 5 or claim 6, wherein, The one or more traffic types include one or more access category identifiers or one or more traffic identifiers.
8. The wireless access point according to any one of claims 2 to 7, wherein, The request requests access to the transmission medium via the first link, and the operation further includes: Receive a second request from the second user equipment to access the transmission medium via the second link using HiP EDCA; and It is determined that the second request conforms to the second HiP EDCA policy for the second link, and the second HiP EDCA policy is different from the HiP EDCA policy.
9. The wireless access point according to any one of claims 2 to 8, wherein, Sending the response to the user equipment is also based on the fact that the request complies with resource level limits.
10. The wireless access point according to any one of claims 2 to 9, wherein, The response includes limitations on the amount or rate of HiP EDCA usage.
11. The wireless access point according to any one of claims 2 to 10, wherein, The request is a Stream Classification Service (SCS) request, and the response is an SCS response.
12. The wireless access point according to any one of the preceding claims, wherein, The HiP EDCA strategy indicates at least one of the following: Is HiP EDCA enabled or disabled? The number of transmission failures that should occur before HiP EDCA should be allowed to be used; The traffic targeted by HiP EDCA should belong to one or more access classes (ACs). The traffic targeted by HiP EDCA should belong to one or more traffic identifiers (TIDs). The number of consecutive HiP EDCA attempts allowed; HiP EDCA is allowed to use the type of frame it targets; Should flow-level negotiation be used to employ HiP EDCA? and / or Does it support negotiating with the wireless access point using HiP EDCA for traffic that does not conform to the HiP EDCA policy? 13. The wireless access point according to any one of the preceding claims, wherein, The message includes one or more of the following: Number of arbitration inter-frame intervals to be used for HiP EDCA contention; Minimum contention window for HiP EDCA contention; The maximum competition window for HiP EDCA competition; and / or Transmission opportunities are limited.
14. The wireless access point according to any one of the preceding claims, wherein, The operation also includes providing the HiP EDCA strategy in one or more of the following: beacon frame, probe response frame, fast initial link establishment discovery frame, association response frame, reassociation response frame, and / or SCS response frame.
15. A method comprising: Broadcasts include messages that are part of the high-priority enhanced distributed channel access (HiP EDCA) policy of the wireless access point; as well as According to the HiP EDCA strategy, user equipment is provided with access to the transmission medium using HiP EDCA.
16. The method of claim 15, further comprising: At the wireless access point, a request to use the HiP EDCA access transmission medium is received from the user equipment. The wireless access point determines that the request conforms to the wireless access point's HiP EDCA policy; as well as In response to determining that the request conforms to the HiP EDCA policy, the wireless access point sends a response to the user equipment granting permission to access the transmission medium using HiP EDCA.
17. The method of claim 16, further comprising: Receive a second request from the second user equipment to access the transmission medium using HiP EDCA; It is determined that the second request does not conform to the HiP EDCA policy; as well as In response to determining that the second request does not conform to the HiP EDCA policy, a second response is sent to the second user equipment, wherein the second response indicates an adjustment to the second request.
18. The method according to claim 16 or claim 17, further comprising: In response to determining that the user equipment is violating the HiP EDCA policy, perform at least one of the following: Revoke the license to use HiP EDCA to access the transmission medium; and / or Disconnect from the user equipment.
19. The method according to any one of claims 16 to 18, wherein, The request identifies a traffic type or traffic flow, and determining that the request conforms to the HiP EDCA policy includes: determining that the HiP EDCA policy allows access to the transmission medium using HiP EDCA for the traffic type or the traffic flow.
20. A wireless access point, comprising: One or more memory units; as well as One or more processors, communicatively coupled to the one or more memories, are configured to perform operations individually or jointly, including: Receive a request from the user equipment to access the transmission medium using High Priority Enhanced Distributed Channel Access (HiP EDCA); Determine that the request conforms to the HiP EDCA policy of the wireless access point; and In response to determining that the request conforms to the HiP EDCA policy, a response granting permission to access the transmission medium using HiP EDCA is sent to the user equipment.
21. A method comprising: Receive a request from the user equipment to access the transmission medium using High Priority Enhanced Distributed Channel Access (HiP EDCA); Determine that the request conforms to the HiP EDCA policy of the wireless access point; as well as In response to determining that the request conforms to the HiP EDCA policy, a response granting permission to access the transmission medium using HiP EDCA is sent to the user equipment.
22. One or more computer-readable media, including instructions that, when executed by one or more processors, cause to perform the method according to any one of claims 15 to 19 and / or 21.
