SYSTEM AND METHOD FOR PROVIDING PRIORITIZED NETWORK ACCESS FOR MULTI-LINK WLAN ENTITIES - Patent application

Abstract

A method for configuring a service in a communication network includes defining a service type by a service provider, and then associating the service type with an Enhanced Distributed Channel Access (EDCA) / Preferred Access parameter set in an Access Point (AP) infrastructure by the service provider of the service type. A WLAN entity is then provisioned with the service type. In some cases, the WLAN entity is a multi-link device (MLD), and the service type is associated with a set of links of the WLAN entity.

Description

[Technical field]

[0001] cross reference This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 310,349, filed February 15, 2022, entitled "SYSTEM AND METHOD FOR PROVIDING PRIORITIZED NETWORK ACCESS FOR A MULTI-LINK WLAN ENTITY," and U.S. Non-Provisional Patent Application No. 18 / 109,227, filed February 13, 2023, also entitled "SYSTEM AND METHOD FOR PROVIDING PRIORITIZED NETWORK ACCESS FOR A MULTI-LINK WLAN ENTITY," the entire contents of which are incorporated herein by reference. The present invention relates to the field of wireless communications, and more particularly to a method and system for facilitating priority access to a wireless network infrastructure for services supporting National Security and Emergency Preparedness (NSEP). [Background technology]

[0002] Wireless communications are used by almost all mobile and many fixed computing devices, including cellular phones, tablets, laptop computers, consumer electronic devices, Internet of Things (IoT) devices, and other consumer electronics products, and the IEEE 802.11 family of standards (also known as WLANs) are commonly used to connect these devices to each other, access the Internet, and otherwise communicate.

[0003] The Extremely High Throughput (EHT) Task Group (TG) "be" of IEEE 802.11 has recently started standardization activities within the IEEE 802.11 WLAN project, and the results of this TG are expected to be included in the upcoming IEEE 802.11be standard. One of the new features of IEEE 802.11be is the creation of Multi-Link Devices (MLDs). MLDs refer to Wireless LAN (WLAN) entities or devices that have multiple radio links for communicating with other MLD entities. A typical use case for Multi-Link Operation (MLO) is an Access Point (AP) using at least two radio links to connect to non-AP Stations (STAs), such as WLAN terminals, computers, or cellular phones, in the WLAN bands, for example, 2.4 GHz and 5 GHz, where traffic is coordinated between the links and one security association is maintained across the two links.

[0004] The IEEE 802.11be standard also includes a new feature called NSEP (National Security and Emergency Preparedness) Priority Access, sometimes also called Emergency Preparedness Communication Service (EPCS). NSEP Priority Access gives wireless devices priority channel access to network communication resources compared to other network devices when traffic related to the priority service is transmitted or received. Currently, NSEP Priority Access is granted to devices on the network by the network operator via the AP infrastructure for all services tagged as having NSEP Priority Access. A set of Enhanced Distributed Channel Access (EDCA) parameters are used to configure NSEP Priority Access. Examples of NSEP Priority Service types include emergency voice services, real-time sensor feeds, video camera feeds, incident response systems, etc. Currently, when priority access is enabled, all of these services are enabled for the device, and all of these priority services are configured using the same parameters.

[0005] This approach has several drawbacks. Currently, NSEP priority access is established regardless of the specific service it is to serve, even if only one service is used. Different NSEP services can benefit from service-specific network traffic characteristics, but it is currently not possible to customize the EDCA parameters for each service. Furthermore, when NSEP priority access is established between an AP MLD and a non-AP MLD, it applies to all setup links of the MLD, even through the service, but may not be suitable for all of these links, but only some of them. NSEP priority access cannot be enabled only on a specific subset of MLD links, nor can NSEP priority access be prohibited on a specific subset of links among all setup links negotiated between an AP MLD and a non-AP MLD when they establish a connection. Summary of the Invention [Means for solving the problem]

[0006] Thus, a need exists to enable service providers to enable and configure NSEP priority access for MLD entities that avoids or mitigates one or more deficiencies of the prior art.

[0007] This background information is provided to identify information believed by the applicant to be of possible relevance to the present invention. No admission is necessarily intended, nor should it be construed, that any of the preceding information constitutes prior art against the present invention.

[0008] An objective of the embodiments of the present invention is to provide a method and system that allows a pair of devices, such as a non-AP STA and an AP, or a non-AP MLD and an MLD, to provide NSEP capability by managing and mapping their multiple radio resources to the requirements of NSEP access. The embodiments allow the pair of devices to map different radio resources to different types of NSEP services simultaneously when necessary. The embodiments allow the system to allow different services to different connected devices.

[0009] The embodiment enumerates different NSEP service types and associates each service type with a specific NSEP service. In the AP infrastructure, each NSEP service type may be associated with a corresponding parameter set, or may be associated with either a preferred link set or a forbidden link set. Furthermore, in the network authentication, authorization, and accounting (AAA) infrastructure, one or more NSEP service types may be assigned to an AAA policy, which may be used to define eligible NSEP preferred access service types for its associated non-AP STAs or non-AP MLDs. The AP MLD may assign and map links to the required NSEP service, and more than one link may be used to map to a single NSEP service. Also, more than one NSEP service may be mapped to a single link.

[0010] The embodiments may also be used for non-MLD (single link device) to configure NSEP services. Each NSEP service type may be associated with a corresponding parameter set used to configure the service between the AP and the non-AP STA.

[0011] The embodiment allows a mechanism to define separate services with their respective parameters and specific link specification. A mechanism is provided to simultaneously modify parameters during the service.

[0012] According to an embodiment of the present invention, there is provided a method for configuring a service in a communication network, comprising: defining a service type by a service provider; associating the service type with an Enhanced Distributed Channel Access (EDCA) / Preferred Access Parameter Set in an Access Point (AP) infrastructure by the service provider of the service type; and then provisioning a Wireless Local Area Network (WLAN) entity with the service type.

[0013] According to various embodiments, the WLAN entity is a multi-link device (MLD) and the service type is associated with a set of links of the WLAN entity.

[0014] According to various embodiments, the set of links includes a subset of the links used for the service type.

[0015] According to various embodiments, the set of links includes a subset of links that are prohibited from use for the service type.

[0016] According to various embodiments, the association of a service type with an EDCA / priority access parameter set is based on the traffic characteristics of the service type.

[0017] According to various embodiments, the provisioning of parameter sets in the AP infrastructure is performed using an authentication, authorization, and accounting (AAA) protocol.

[0018] According to an embodiment of the present invention, there is provided a method for configuring a service in a communication network, the method including: transmitting, by a WLAN entity, an NSEP priority access frame, the frame including a service type of the service.

[0019] According to various embodiments, the frame is either an NSEP priority access request or an NSEP priority access response frame.

[0020] According to various embodiments, the NSEP priority access response frame is transmitted to modify parameters of a previously established NSEP service operation.

[0021] According to various embodiments, the WLAN entity is an access point (AP) and the frame further includes an EDCA or preferred access parameter set used for the service type.

[0022] According to various embodiments, the AP is an AP that belongs to an AP Multi-Link Device (MLD), and the frame further includes a set of links of the service type.

[0023] According to various embodiments, the WLAN entity is a non-AP STA that belongs to a non-AP Multi-Link Device (MLD), and the request frame further includes a set of links of the service type.

[0024] According to various embodiments, the set of links includes a subset of the links used for the service type.

[0025] According to various embodiments, the set of links includes a subset of links that are prohibited from use for the service type.

[0026] According to various embodiments, the link complies with network policies received from the subscription service provider network.

[0027] According to various embodiments, the transmission of the NSEP priority access request frame is sent in response to the MAC layer receiving a request primitive from the SME layer of the WLAN entity.

[0028] According to an embodiment of the present invention, there is provided a method for configuring a priority access service in a communication network, the method including: encoding, by a WLAN entity, a service type of the priority service as an enumeration, inserting, by the WLAN entity, the service type into a frame, and transmitting, by the WLAN entity, the frame.

[0029] According to various embodiments, a priority access service is established between two peer MLDs, and the method further includes encoding, by the WLAN entity, link information of a link associated with the priority service as a number of octets, the number of octets indicating whether the link may be used for the priority service or is prohibited from being used for the priority service, and inserting, by the WLAN entity, the link information into the frame.

[0030] According to various embodiments, the frame is an NSEP priority access request frame or an NSEP priority access response frame.

[0031] According to various embodiments, the frame is transmitted by a STA or an MLD, and the frame further includes a set of EDCA or priority access parameters based on traffic characteristics of the priority service.

[0032] Embodiments provide the technical advantage of enabling devices and networks to apply differentiated parameters associated with priority access that are tailored to each type of service. Multiple services can be enabled simultaneously for NSEP priority access and can be managed by the access network operator independently of each other.

[0033] Embodiments provide the technical advantage of adding type of service, EDCA or preferred access parameter sets, and preferred or forbidden links to NSEP preferred access primitives.

[0034] Embodiments provide the technical advantages of enabling association of an NSEP priority access service type with a user or device, enabling communication of that service type information when the user or device successfully authenticates with the network, and enabling the network AP infrastructure to authorize the user or device for a set of NSEP services. When a user or device requests to establish NSEP priority access for a particular service, the WLAN infrastructure can determine whether the user or device is authorized for that service.

[0035] Embodiments provide the technical advantage of adding type of service and preferred or forbidden links to NSEP preferred access primitives.

[0036] Embodiments provide a technical advantage of adding EDCA or priority access parameter sets and recommended or forbidden links to NSEP priority access request and NSEP priority access response frames for corresponding service types.

[0037] Embodiments provide the technical advantage of enabling the use of a specific EDCA or preferred access parameter set for communication of traffic associated with a negotiated NSEP service type, which in turn enables the use of a specific set of links for communication between an AP MLD and a non-AP MLD for traffic associated with the negotiated NSEP service type.

[0038] Embodiments provide the technical advantage of enabling the use of unsolicited NSEP priority response frames, or equivalent frames, to update parameters associated with a particular NSEP service type during the lifetime of an established service.

[0039] The embodiments are described above in conjunction with the aspects of the invention in which they can be implemented. Those skilled in the art will recognize that the embodiments may be implemented in conjunction with the aspect in which they are described, but may also be implemented with other embodiments of that aspect. When the embodiments are mutually exclusive or otherwise incompatible with each other, it will be apparent to those skilled in the art. Some embodiments may be described in relation to one aspect, but may also be applicable to other aspects, as will be apparent to those skilled in the art.

[0040] Further features and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings. [Brief description of the drawings]

[0041] [Figure 1a] 1 illustrates a multi-link device (MLD) architecture according to one embodiment. [Figure 1b] 1 illustrates an architecture having an AP and associated non-AP STAs, according to one embodiment. [Diagram 2] 1 illustrates a representative network topology for priority access services, according to one embodiment. [Diagram 3] 1 illustrates an association of a preferred service type with a parameter set, a set of links, and an application, according to one embodiment. [Figure 4] 1 illustrates a message flow for non-AP authentication and network policy enforcement, according to one embodiment. [Diagram 5] 1 illustrates primitives and frames that may be used to implement the methods described herein with their respective parameters (depending on the WLAN entity for which the primitive or frame is invoked), according to one embodiment. [Figure 6] 1 illustrates how information related to service type and link can be added to a frame according to one embodiment. [Figure 7]1 illustrates primitives and frames that may be used for prioritized service access and service establishment, according to one embodiment. [Figure 8] 1 illustrates a message flow that may be used to update preferred service parameters corresponding to an existing service type, according to one embodiment. [Figure 9] 1 illustrates an electronic device that can be used to implement the methods described herein, according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0042] It should be noted that throughout the accompanying drawings, like features are identified by like reference numerals.

[0043] The embodiments of the present disclosure relate to methods and systems that enable WLAN entities, such as non-access point (AP) stations (STAs) or APs, to provide National Security and Emergency Preparedness (NSEP) capabilities by managing and mapping their radio resources to requirements for NSEP access. The embodiments enable the WLAN entities to map radio resources to different types of NSEP services simultaneously when necessary. The embodiments enable the system to allow different services to different connected clients.

[0044] The embodiment enumerates different NSEP service types and associates each service type with a particular NSEP service. In the AP infrastructure, each NSEP service type may be associated with a corresponding Enhanced Distributed Channel Access (EDCA) parameter set, or in the case of NSEP preferred access service types established between multi-link device (MLD) entities (AP MLD and non-AP MLD), the service type may be applied to a subset of setup links, either as a preferred link set or a forbidden link set. Furthermore, in the network authentication, authorization, and accounting (AAA) infrastructure, one or more NSEP service types may be assigned to an AAA policy, which may be used to define eligible NSEP preferred access service types for its associated non-AP STAs or non-AP MLDs. The AP MLD or non-AP MLD may assign and map a subset of setup links to the required NSEP service, and more than one link may be used to map to a single NSEP service type. Also, more than one NSEP service may be mapped to a single setup link between an AP MLD and a non-AP MLD.

[0045] The embodiments allow a mechanism to define separate services with respective parameters, such as EDCA or preferred access parameters, and specification of specific links. A mechanism is provided to simultaneously modify parameters during the lifetime of an established service.

[0046] Although embodiments may be described with respect to NSEP priority access service, other priority service types, or different classes or priorities of service types, may be defined, configured, and coordinated using the methods and systems described herein.

[0047] As used herein, a station (STA) is a logical entity that is a single addressable instance of a medium access control (MAC) and physical layer (PHY) interface to a wireless medium (WM). An access point (AP) is an entity that contains at least one logical station (STA) and provides access to distribution system services over the wireless medium (WM) for associated STAs. An AP comprises STAs and distribution system access functions. A non-access point (non-AP) station (STA) is a STA that is not included within an access point (AP).

[0048] As used herein, a multilink device (MLD) is an AP device or a non-AP STA device that supports multiple radios operating simultaneously on multiple channels. An AP MLD is a multilink device that has access to a distribution system and includes at least an associated AP that is used as an access to a WM. A non-AP MLD is a multilink device that does not have access to a distribution system and includes at least an associated non-AP STA that is used as an access to a WM. Associated MLD peers establish a connection across multiple wireless peers, called a setup link. In an infrastructure network, frames are exchanged over a single link between a non-AP STA that belongs to a non-AP MLD and an AP that belongs to an AP MLD.

[0049] Referring to Fig. 1a, a typical use case of multi-link operation (MLO) includes a non-AP MLD 106 (such as a WLAN terminal) connecting to an AP MLD 105 using two wireless links in the 2.4GHz and 5GHz WLAN bands. Each wireless link is called a link, and each of the links between the AP MLD 105 and the non-AP MLD 106 is maintained by an AP belonging to the AP MLD and a non-AP STA belonging to the non-AP MLD for each of the different wireless channels on which these links are operating. The non-AP MLD 106 includes a 2.4GHz non-AP STA 110 and a 5GHz non-AP STA 114. The AP MLD 105 includes a 2.4GHz AP 108 and a 5GHz AP 112.

[0050] In the IEEE 802.11 standard, a WLAN entity consists of the following layers: Station Management Entity (SME) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer. The standard includes internal interfaces between these components to describe their interaction and the behavior of the WLAN entity. Communication over these internal interfaces is defined by primitives. Communication between the SME and MAC layers, and between the MAC and PHY layers on the same entity, is internal to the device, while communication between MAC / PHY peers occurs over the wireless medium.

[0051] Each non-AP STA 110 and 114 includes a medium access control (MAC) layer and a physical (PHY) layer. Radio antennas for transmitting and receiving wireless signals are not shown. The 2.4 GHz AP 108 and the 5 GHz AP 112 belong to the AP MLD 105, which exchange frames with their corresponding 2.4 GHz non-AP STA 110 and 5 GHz non-AP STA 114, respectively, that belong to the non-AP MLD 106 via a setup link. The AP MLD interfaces to the LAN 104 for communication with a wired gateway 102 that connects to other networks such as the Internet. The MAC layers of each MLD interact to coordinate the MAC layer operations in their associated STAs. The MAC layers of the associated STAs interact with their respective PHYs.

[0052] In an embodiment, the operation of MLD may be different from that of two logical STAs (e.g., two non-AP STAs in the same handset) in the same physical entity (multi-band clients). In MLD, traffic may be coordinated between two links and one security association may be maintained across them. This provides an advantage over the concept of virtual STA. For example, MLD in this document may be a single antenna device or a multi-antenna device with two or more antennas. The number of antennas included in MLD is not limited in the embodiment. In an embodiment, MLD may allow services of the same access type to be transmitted on different links, or even the same data packet to be transmitted on different or multiple links. Instead, data frames corresponding to the same access category may be transmitted on a specific link. Data frames corresponding to different access categories may also be transmitted on different links. For example, data frames corresponding to video services may use either link 1 and link 2, while data frames corresponding to voice services may always use link 1 depending on the environment and other conditions.

[0053] For MLO proposed as part of IEEE 802.11be, priority access, such as NSEP priority access, may be established between an AP MLD 105 and an associated non-AP MLD 106. The priority access protocol may give a device priority channel access to network communications resources compared to other network devices when frames related to priority services are exchanged.

[0054] In an embodiment, each AP belonging to the AP MLD 105 can also be associated with legacy non-AP STAs. For example, an AP belonging to the AP MLD 105 operating on a 2.4 GHz wireless link can also behave as a legacy AP serving legacy 802.11 non-AP STAs.

[0055] In the IEEE 802.11 standard, a WLAN entity is composed of the following layers: Station Management Entity (SME) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer. The standard includes internal interfaces between these components to describe the interaction of these layers and the behavior of the WLAN entity. Communication over these internal interfaces is defined by primitives. Communication between the SME and MAC layers and between the MAC and PHY layers on the same entity is internal to the device, while communication between MAC / PHY peers occurs over the wireless medium. Layers such as the MAC layer in FIG. 1a may be logically and physically split between entities. For example, the MAC layer of the non-AP MLD 106 is split into an upper MAC for the non-AP MLD itself and a lower MAC for the 2.4 GHz non-AP STAs 110. The upper MAC layer, which operates on all frames exchanged with non-AP MLD (regardless of the link on which they are transmitted or received), is collocated with the SME layer, and the lower MAC, which operates on frames exchanged with peer non-AP STAs on a particular link, is collocated with the PHY layer.

[0056] 1b illustrates an embodiment including a non-MLD WLAN entity with only one link: A non-AP STA 106 is associated with an AP 105 using a single wireless link.

[0057] FIG. 2 shows a diagram of a network topology 200 used to facilitate the priority access described herein. The non-AP MLD 106 is associated with an AP (either 105a, 105b, or 105c) in an access network operated by a WLAN operator. The network access infrastructure 204 is connected to a subscription service provider network (SSPN) 208, which provides access to a service provider 206 that includes or has access to an authentication, authorization, and accounting (AAA) server 218 and a policy server 216. The non-AP STA 106 may be associated with an AP (either 105a, 105b, or 105c) in the access network. The access network communicates with the AAA server 218 by an authentication protocol such as RADIUS, DIAMETER, or other similar protocol during the authentication procedure of the non-AP STA. The AAA server 218 may authenticate the non-AP STA 106 and obtain a policy for the non-AP STA 106 from the policy server 206 by a protocol such as Lightweight Directory Access Protocol (LDAP) or other similar protocol. The result of the authentication may then be returned to the access network along with any policies. When the authentication procedure is successful, the non-AP STA 106 establishes a network connection and the access network applies the network policies to the non-AP STA 106.

[0058] As referred to herein, the WLAN entities 106 may be either non-AP MLDs as shown in Figure 1a or non-AP STAs as shown in Figure 1b. Similarly, the WLAN entities 105 (including 105a, 105b, and 105c) may be either AP MLDs as shown in Figure 1a or APs as shown in Figure 1b.

[0059] In an embodiment, priority access may be negotiated between a non-AP STA 106 and an associated AP 105 (either 105a, 105b, or 105c) under certain circumstances, for example, when an event is detected by the non-AP STA 106, the AP 105, or the SSPN 208. The event prompts an exchange of messages between the non-AP STA 106 and the associated AP 105 to establish network access. During the message exchange, the access network transmits a set of wireless medium access parameters that enable the non-AP STA 106 to gain priority access to the wireless medium (i.e., channel). In an embodiment, the parameter set may be an Enhanced Distributed Channel Access (EDCA) parameter set corresponding to an Emergency Preparedness Communication Service (EPCS) service type, or a similar parameter set required to configure and manage communication channels and links for priority access. Examples of priority service types include emergency voice services, real-time sensor feeds, video camera feeds, incident response systems, etc.

[0060] Different types of devices may be authorized for different types of services. For example, a cell phone may be used for emergency voice services but not for temperature sensor services. Thus, a cell phone is authorized for emergency voice and a temperature sensor is authorized for temperature measurement. Different NSEP services may be characterized by different network traffic characteristics. To prioritize the traffic of a particular service, a parameter set may be associated with that service.

[0061] 3, an embodiment includes different service types 302 that may utilize prioritized access. The different prioritized services 302 may be defined and configured in the access network or SSPN network 208. In the access network, each service type 302 is associated with a set of parameters 304 and with a set of links 308 that may include any valid link, preferred link, forbidden link, or any combination of valid links, preferred links, or forbidden links, for connections established between peer MLDs.

[0062] In the SSPN 208, the policy server 216 associates a service type 302 with the device identity. When the device authenticates with the network, the policy server 216, via the AAA server 218, may provide a list of services that the device is authorized to use for priority access, such as NSEP priority access. The list of services is returned to the access network. When NSEP priority access is being established, the service type, the associated (EDCA) parameter set, and a set of recommended or forbidden links for the service established between the peer MLDs are communicated from the AP MLD 105 to the non-AP MLD 106 during establishment of priority access for the specified service type.

[0063] The service provider 206 may define and enumerate different priority service types 302 to be used for NSEP priority access in the access network 214. As an example, the service types 302 may be enumerated to represent emergency voice, sensor communication, real-time video streaming, real-time messaging, and real-time audio communication or announcement. In the access network, each service type 302 that may be defined by the SSPN 208 is associated with a corresponding EDCA or priority access parameter set 304 that may be based on the traffic characteristics of the service. For example, the EDCA or priority access parameter set 304 may give priority access to the wireless medium for voice traffic. In a non-AP STA 106, each service defined by the SSPN 208 may be provisioned and, in a multifunction device, may be associated with an application or applications running on the device. With respect to MLO, in an AP MLD, each service type 302 defined by the SSPN 208 may be mapped to either a set of links used by the AP MLD for that service or a set of forbidden links not used by the AP MLD for that service. Non-AP MLD can also be provisioned with a set of preferred links for a given service type 302. Peer MLD can support multiple services simultaneously and map different service types 302 to different setup links depending on the radio resource requirements of the service.

[0064] The enumeration and provisioning of service types 302 provides the technical advantage of allowing devices and networks to apply differentiated EDCA or priority access parameter sets 304 associated with priority access that may be tailored to the type of service 302. Multiple services may be specified by an operator of the SSPN 208 and enabled for priority access simultaneously, and operators of the access networks 214 may map these service types to their infrastructure networks independently of one another.

[0065] In an embodiment, the policy server 216 may assign one or more service types 302 to an AAA policy. An AAA policy, which may include a set of service types 302, may be associated with a set of devices (or may be associated with one or more users). Once the device successfully authenticates with the network, this policy assignment may be distributed to the AP or AP MLD for use with the device. The policy may be stored in the policy server 216 and communicated to the AP 105 using an AAA protocol such as RADIUS or DIAMETER. A list of allowed service types may be sent from the AAA server 216 to the AP or AP MLD 105 for use with the non-AP STA or non-AP STA 106 using attributes such as RADIUS attributes. After successful authentication, the non-AP STA 106 may be granted priority access for those service types. The policy defines the priority access service types that are allowed for the associated non-AP STA or non-AP MLD 106. The policy allows the access network to enable priority access for the device when the device is triggered and enabled.

[0066] 4 illustrates one embodiment of a message flow for a non-AP STA 106 authenticating and associating with an AP 105 and communicating a service type 302 as part of a network policy for a successfully authenticated non-AP STA 106. In step 402, the non-AP STA 106 selects a network and successfully associates and authenticates with the AP 105 using IEEE 802.11 authentication and association procedures for the network. In step 404, the non-AP STA 106 also performs authentication with the AAA server 218 using a protocol such as the Extensible Authentication Protocol (EAP) or a similar protocol. In step 406, after successful authentication, the AAA server 218 in the SSPN 208 may query the policy server 216 for a network policy associated with the user or device identity of the non-AP STA 106, for example, using an LDAP policy query. In step 410, after receiving the policy information in step 408, the AAA server 218 may communicate the policy information corresponding to the non-AP STA 106 to the AP 105 in a message indicating successful authentication using a protocol such as RADIUS. If the RADIUS protocol is used, this policy information may be communicated in a RADIUS ACCESS ACCEPT message. After successful authentication, the AP 105 and the non-AP STA 106 are permitted to request priority access for that particular service. The priority access service type may be stored locally to verify authorization if the non-AP STA requests priority access later. In steps 412 and 414, an Extensible Authentication Protocol (EAP)-over-LAN (EAPoL) protocol may be used to complete the configuration of communication between the AP 105 and the non-AP STA 106, and data communication may begin between these STA peers in step 416.

[0067] The association of a priority access service type 302 with a user or device, and communication of that service type information when the user or device successfully authenticates with the network, provides the technical advantage of allowing the AP 105 to authorize a set of services for the device. When a user or device requests to establish priority access for a particular service, the AP 105 can determine whether the user or device is authorized for that service.

[0068] 5, an embodiment includes primitives that can be incorporated and used in IEEE 802.11 and other networking protocols to implement the priority access methods described herein. Although the primitives provided in this embodiment refer to the NSEP protocol, it will be understood by those skilled in the art that these concepts and teachings can be adapted for use in other networking protocols. The primitives can be used between the SME layer and the MAC layer within the non-AP STA 106 or the AP 105.

[0069] Embodiments may also modify NSEP priority access frames, including the NSEP priority access request frame 504 and the NSEP priority access response frame 510, to implement the priority access methods described herein.

[0070] In an embodiment, primitives are exchanged between the SME layer and the MAC layer of the WLAN entity: An MLME-NSEP Priority Access Enable.request 502 primitive is sent from the SME layer to the MAC layer; an MLME-NSEP Priority Access Enable.indication 506 primitive is sent from the MAC layer to the SME layer; an MLME-NSEP Priority Access Enable.response 508 primitive is sent from the SME layer to the MAC layer; and an MLME-NSEP Priority Access Enable.confirm 512 primitive is sent from the MAC layer to the SME layer.

[0071] In an embodiment, the primitives and frames specify the service type to which they apply. Primitives and frames invoked by the AP or AP MLD 105 may specify EDCA or preferred access parameter sets. Primitives and frames utilized by or between the AP MLD 105 and non-AP MLD 106 may specify the set of links that are or are not used by the service.

[0072] The SME layer of the STA may include the following parameters in an MLME-NSEP PRI ACCESS ENABLE.request primitive 502, which may initiate the establishment of an NSEP priority access service with a particular peer STA. The primitive 502 includes information such as the service type (one of the enumerated service types defined by the SSPN 208). If called by an AP or AP MLD, the primitive 502 may include an EDCA or priority access parameter set to be used for the service type. If called by an AP MLD or non-AP MLD, the primitive 502 may further include a set of links. The set of links may include a set of recommended links to be used for that service type, or a set of forbidden links for that service type if the initiating SME is in the MLD.

[0073] Upon receiving the MLME-NSEP PRI ACCESS ENABLE.request primitive 502, the MAC layer of the same WLAN entity initiates the transmission of an NSEP priority access request frame 504 to the MAC layer of its associated station. The frame 504 includes information such as the service type (one of the enumerated service types defined by the SSPN 208). If the MAC layer is associated with an AP or AP MLD, the primitive 502 may include an EDCA parameter set used for the service type. If the MAC layer is associated with an AP MLD or a non-AP MLD, the primitive 502 may further include a set of links. The set of links may include a set of recommended links to be used for that service type, or a set of forbidden links for that service type if the initiating SME is in an MLD. In an embodiment, the parameters of the NSEP priority access request frame 504 may be obtained from the MLME-NSEP PRI ACCESS ENABLE.request primitive 502 that triggered the transmission of the NSEP priority access request frame 504.

[0074] For a STA, the service type, associated EDCA parameter set (if included), and list of recommended or forbidden links (if included for MLD) may conform to the network policy communicated by the SSPN 208 .

[0075] In an embodiment, the parameters of the NSEP priority access request frame 504 may be obtained from the MLME-NSEP PRI ACCESS ENABLE.request primitive 502 that triggered the transmission of the NSEP priority access request frame 504 .

[0076] In response to receiving the NSEP priority access request frame 504, an MLME-NSEP PRI ACCESS ENABLE.indication primitive 506 is generated by the receiving MAC layer and sent to its SME layer. If the SME layer is that of an AP or AP MLD, it may verify that the requested NSEP service type and the set of recommended or forbidden links (if included by the MLD) conform to the policy associated with the setup link between the device and the peer MLD, and generate an MLME-NSEP PRI ACCESS ENABLE.response primitive 508. Both primitives 506 and 508 include information such as the service type (one of the enumerated service types defined by the SSPN 208), and primitive 508 may include the EDCA parameter set used for the service type (if invoked by an AP or AP MLD), and the set of links (if the initiating entity is an MLD, such as an AP MLD or a non-AP MLD). The set of links may include the set of recommended links used for that service type, or the set of forbidden links for that service type.

[0077] Upon receiving the MLME-NSEP PRI ACCESS ENABLE.response primitive 508, the MAC layer of the same WLAN entity initiates the transmission of an NSEP priority access response frame 510 to the MAC layer of its associated WLAN entity. The frame 510 includes information such as the service type (one of the enumerated service types defined by the SSPN 208). If the request primitive is invoked by an AP or AP MLD, the primitive 508 may include an EDCA parameter set used for the service type. If the WLAN entity is an AP MLD or a non-AP MLD, the frame 510 may further include a set of links. The set of links may include a set of recommended links to be used for that service type, or a set of forbidden links for that service type if the initiating SME is in the MLD.

[0078] In response to receiving the NSEP priority access response frame 510, an MLME-NSEP PRI ACCESS ENABLE.confirm primitive 512 is generated by the receiving MAC layer for sending to its SME layer. The SME layer may confirm that the requested NSEP service type and the set of recommended or forbidden links (if included by the MLD) conform to the policy associated with the setup link between the device and the peer MLD. The primitive 512 includes information such as the service type (one of the enumerated service types defined by the SSPN 208), the EDCA parameter set used for the service type (if invoked by a non-AP STA or non-AP MLD), and the set of links (if the initiating entity is an MLD such as an AP MLD or non-AP MLD). The set of links may include a set of recommended links used for that service type, or a set of forbidden links for that service type.

[0079] In an embodiment, the MLME-NSEP PRI ACCESS ENABLE.response primitive 508 initiates the MAC layer to send an NSEP priority access response frame 510 to the peer STA. If the SME is of an AP or AP MLD, it configures its MAC layer with EDCA or priority access parameter sets, and if the SME is of an MLD, it configures its MAC layer with link information (i.e., used links or forbidden links if included by the MLD) for NSEP priority access traffic corresponding to its service type.

[0080] Upon receiving the MLME-NSEP PRI ACCESS ENABLE.confirm primitive 512, the SME layer may confirm the NSEP service type that conforms to the requested one and the set of recommended or forbidden links (if included by the AP MLD). The SME layer may configure its MAC layer with the EDCA parameter set and link information (i.e., used links or forbidden links if included by the MLD) for the NSEP priority access traffic that corresponds to that service type.

[0081] In embodiments, the addition of service type and recommended or forbidden links (if included by MLD) to prioritized access primitives such as those used for NSEP provides many technical advantages. In addition to recommended and forbidden links, other types of links, such as required links, or links with different priorities, may also be defined.

[0082] Embodiments may be used to add parameters to the NSEP priority access request frame 504 and the NSEP priority access response frame 510 to establish NSEP priority access service between MLD peers. In particular, parameters related to the service type and a list of either recommended or forbidden links may be included in the NSEP priority access request frame 504 and the NSEP priority access response frame 510.

[0083] The service type field is defined by a one octet field 602 and may indicate an enumerated NSEP service type defined by the SSPN. For example, if the NSEP service types include emergency voice service, real-time sensor feed, video camera feed, and incident response system, emergency voice service may be indicated with service type=0, real-time sensor feed may be indicated with service type=1, video camera feed may be indicated with service type=2, and real-time sensor feed may be indicated with service type=3. The one octet allows up to 256 different service types to be defined. In an embodiment, a single service type is established at a time.

[0084] A set of recommended or forbidden links may be included in an NSEP link element 604, which includes several fields. A link count field 606 may indicate the number of recommended or forbidden links including a flag 608 indicating whether the link is forbidden or recommended. A link ID count field 610 may indicate the number of link ID information fields 610 in the NSEP link element 604. A forbidden link field 608 may be set to 1 to indicate that the link is forbidden for a particular NSEP preferred access service. A forbidden link field 608 may be set to 0 to indicate that the link is recommended for a particular NSEP preferred access service. A link ID information field 612 may include the link ID of the link specified in the NSEP link element 604.

[0085] In an embodiment, an AP belonging to the initiating AP MLD 105 or a STA belonging to the initiating non-AP MLD 106 may include a service type field 602 in the NSEP priority access request frame 504 or the NSEP priority access response frame 510 that it generates. Any STA belonging to the MLD may include an NSEP link element 604 in the NSEP priority access request frame 504 or the NSEP priority access response frame 510 that it generates. For MLO, the elements of the NSEP link element 604 may indicate either a list of recommended links for communication or a list of forbidden links for communication. In addition, a (non-MLD) AP or an AP belonging to the AP MLD may include an EDCA or priority access parameter set element in the NSEP priority access request frame 504 or the NSEP priority access response frame 510 that it generates. The value included in the EDCA or priority access parameter set element should conform to the service type for which the NSEP priority access is established.

[0086] To establish an NSEP priority access service between MLD peers, a technical advantage is realized by adding a service type, a parameter set corresponding to the service type, and a recommended or forbidden link to the NSEP priority access request frame 504 and the NSEP priority access response frame 510.

[0087] In an embodiment, once NSEP priority access has been negotiated, for example by using the method illustrated in FIG. 4, the NSEP priority access service is applied to the established service type between an associated pair of an AP 105 and a non-AP STA 106, or an associated pair of an AP MLD and a non-AP MLD.

[0088] The channel access rules for NSEP priority access may be defined according to the EDCA or priority access parameter set for the negotiated link set defined by the AP 105 or the AP belonging to the AP MLD 105 during service establishment, instead of other default parameters that may be signaled by the AP 105 or the AP belonging to the AP MLD 105 in the beacon and probe response frames that may be transmitted. The EDCA or priority access parameters used are applicable to the traffic corresponding to the negotiated service type. In case of MLD, the links on which frames are exchanged by both peer MLDs (i.e., AP MLD 105 and non-AP MLD 106) for the established service type follow the links defined in the set of recommended links or exclude the links defined in the forbidden link set, as recommended by the MLME-NSEP PRI ACCESS ENABLE.request 502 primitive and confirmed by the MLME-NSEP PRI ACCESS ENABLE.response 508 primitive. Priority access for multiple different service types may be negotiated independently and can operate simultaneously between a non-AP STA 106 and AP 105 pair.

[0089] 7 illustrates an embodiment including a method for NSEP priority access negotiation and service establishment when initiated by the AP MLD 105. Although FIG. 7 illustrates the case where the method is initiated by the AP or AP MLD side, it should be understood that the method may also be initiated by a non-AP STA or non-AP MLD side, and the primitives and frames used include the parameters described with reference to FIG.

[0090] In step 710, an external event may trigger the SME layer 708 of the APMLD 105 to invoke and send an MLME NSEP PRI ACCESS ENABLE.request primitive 502 to the MAC layer 706 of the AP MLD 105. In step 712, the MAC layer 706 initiates transmission (by the AP 105 to which it belongs) of an NSEP priority access request frame 504 that includes the service type, a set of recommended or forbidden links (included for MLD), and an EDCA or priority access parameter set.

[0091] The NSEP priority access request frame is received by the MAC layer 704 of the non-AP MLD 106 via the STAs attached to the non-AP MLD, and in step 714, the MAC layer 704 may send an MLME NSEP PRI ACCESS ENABLE.indication primitive 506 to the SME layer 702. In step 716, the SME layer 702 may respond with an MLME NSEP PRI ACCESS ENABLE.response primitive 508, which in step 718 may trigger the transmission of an NSEP priority access response frame 510 to the peer STAs operating on the link on which the request frame was sent. The NSEP priority access response frame 510 may include a service type and a set of recommended or forbidden links in the frame 510. After successfully initiating the transmission of the frame 510, the SME layer 708 of the non-AP MLD 106 may then configure a parameter set in the MAC layer 706 of the non-AP MLD 106 with the link information. The AP MLD 105 MAC layer 706 receives the NSEP priority access response frame 510 and sends an MLME NSEP PRI ACCESS ENABLE.confirm primitive 512 to the SME layer 708 in step 720. The AP MLD 105 SME layer 708 may also configure parameter sets in the AP MLD 105 MAC layer 706 with link information. In step 722, traffic associated with that service type may then be transmitted over the negotiated set of links using the negotiated parameter sets.

[0092] In an embodiment, an NSEP priority access request frame 504 transmitted by the MAC layer of a WLAN entity may receive its parameters from an MLME NSEP PRI ACCESS ENABLE.request primitive 502 received from the SME. Also, an MLME NSEP PRI ACCESS ENABLE.indication primitive 506 may be generated by the MAC layer of the WLAN entity using parameters received in an NSEP priority access request frame 510 received by the WLAN entity. Furthermore, an NSEP priority response frame 510 is transmitted by the MAC layer of the WLAN entity using parameters received in an MLME NSEP PRI ACCESS ENABLE.response primitive 508. Values ​​of the parameters in the MLME NSEP PRI ACCESS ENABLE.response primitive 508 are determined by the SME layer based on the parameters received in the MLME NSEP PRI ACCESS ENABLE.indication primitive 506. An MLME NSEP PRI ACCESS ENABLE.confirm primitive 512 is generated by the MAC layer of the WLAN entity using parameters received in the NSEP priority response frame 510 by the WLAN entity.

[0093] The use of a particular EDCA or preferred access parameter set for communications between the AP MLD 105 and the non-AP MLD 106 for traffic associated with the negotiated NSEP service type provides a technical advantage because it enables the use of a particular set of links for communications between the AP MLD 105 and the non-AP MLD 106 for traffic associated with the negotiated NSEP service type.

[0094] In one embodiment, multiple priority services, such as NSEP services, can operate simultaneously. However, to optimize traffic flow when multiple services are operating, or to address any other conditions of the wireless network, the AP or AP MLD 105 can update the priority service configuration to accommodate aggregation, deaggregation, or optimization of the priority services. This can be done by transmitting a spontaneous mode frame, such as the NSEP priority access response frame 510, indicating the service type.

[0095] The spontaneous update can take the form of a link mapping update (by the AP MLD 105 or non-AP MLD 106) or a parameter set update (when invoked by only the AP or AP MLD 105). Figure 8 shows an embodiment of an AP MLD 105 using a spontaneous mode, such as a spontaneous NSEP priority access response frame 510, to update parameters for a particular priority access service type. Although Figure 8 shows the case where the method is initiated by the AP or AP MLD side, it should be understood that the method can also be initiated by a non-AP STA or non-AP MLD side, and the primitives and frames used include the parameters described with reference to Figure 5.

[0096] In step 802, the NSEP service is operational and has been previously configured and enabled using the methods described herein. An event may trigger a change to the parameters associated with an existing priority access service of a particular service type, and in step 804, the SME layer 708 of the AP MLD 105 may send an MLME NSEP PRI ACCESS ENABLE.response primitive 508 to the MAC layer 706 of the AP MLD 105. In step 806, the MAC layer 706 of the AP belonging to the AP MLD 105 sends an unsolicited response frame, such as an NSEP priority access enable response frame 510, to the MAC layer 704 of the non-AP STA of 106 belonging to the non-AP MLD 106. In step 808, the MAC layer sends an MLME NSEP PRI ACCESS ENABLE.confirm 512 to the SME layer 702 of the non-AP MLD 106. Both devices update their parameters associated with that service type and continue to exchange frames related to that NSEP priority access service in step 810.

[0097] In an embodiment, a dedicated frame can be defined for signaling changes to the NSEP priority service access configuration. The new frame can be called a (NSEP) priority access update frame, which has the same or similar format as the NSEP priority access response frame 510 when used in the spontaneous mode.

[0098] In an embodiment, an unsolicited NSEP priority access response frame 510 is transmitted by the MAC layer of the WLAN entity using the parameters included in the reception of the MLME NSEP PRI ACCESS ENABLE.response primitive 508. An MLME NSEP PRI ACCESS ENABLE.confirm primitive 512 is generated by the MAC layer of the WLAN entity using the parameters received in the unsolicited NSEP priority access response frame 510.

[0099] The use of unsolicited NSEP priority access response frames or equivalent frames provides the technical advantage of updating parameters associated with a particular priority service type during the lifetime of an established service.

[0100] 9 is a schematic diagram of an electronic device 900 that may perform any or all of the operations of the above methods and features explicitly or implicitly described herein according to different embodiments of the present invention. For example, such an electronic device with network capabilities may be configured as an AP 105, a non-AP STA 106, an AP MLD 105, or a non-AP MLD 106, or any other networking equipment or server described herein.

[0101] As shown, the device includes a processor 910, such as a central processing unit (CPU) or a dedicated processor such as a graphics processing unit (GPU) or other such processor unit, memory 920, non-transitory mass storage 930, I / O interface 940, network interface 950, video adapter 970, and one or more transceivers 960, all of which are communicatively coupled via a bidirectional bus 925. The video adapter 970 may be connected to one or more of the displays 975, and the I / O interface 940 may be connected to one or more of the I / O devices 945 that may be used to implement a user interface. According to a particular embodiment, any or all of the illustrated elements, or only a subset of the elements, may be utilized. Furthermore, the device 900 may include multiple instances of a particular element, such as multiple processors, memories, or transceivers. Also, elements of a hardware device may be directly coupled to other elements without a bidirectional bus. In addition to or instead of the processor and memory, other electronic devices, such as integrated circuits, may be used to perform the necessary logical operations.

[0102] The memory 920 may include any type of non-transitory memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read only memory (ROM), or any combination thereof. The mass storage element 930 may include any type of non-transitory storage device, such as a solid state drive, a hard disk drive, a magnetic disk drive, an optical disk drive, a USB drive, or any computer program product configured to store data and machine-executable program code. According to certain embodiments, the memory 920 or mass storage 930 may record statements and instructions executable by the processor 910 to perform any of the foregoing method operations described above.

[0103] Although specific embodiments of the present technology are described herein for illustrative purposes, it will be recognized that various modifications may be made without departing from the scope of the present technology. Therefore, the specification and drawings should be considered as merely illustrative of the present invention as defined by the appended claims, and are intended to encompass any and all modifications, variations, combinations, or equivalents that are within the scope of the present technology. In particular, it is within the scope of the present technology to provide a computer program product or program element, or a program storage or memory device, such as a magnetic or optical wire, tape, or disk, for storing a machine-readable signal, for controlling the operation of a computer in accordance with the method of the present technology, and / or for structuring some or all of its components in accordance with the system of the present technology.

[0104] The operations associated with the methods described herein may be implemented at least in part as coded instructions in a computer program product. In other words, the computer program product is a computer-readable medium having recorded thereon software code for performing the methods when the computer program product is loaded into a memory and executed on a microprocessor of a wireless communication device.

[0105] Throughout the description of the preceding embodiments, the present invention may be implemented using only hardware, or using software and a required general-purpose hardware platform. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product. The software product may be stored in a non-volatile or non-transitory storage medium, which may be a compact disc read-only memory (CD-ROM), a USB flash disk, or a removable hard disk. The software product includes a number of instructions that enable a computer device (personal computer, server, or network device) to execute the method provided in the embodiments of the present invention. For example, such execution may correspond to the simulation of the logic operations described herein. The software product may additionally or alternatively include a number of instructions that enable a computer device to execute operations for configuring or programming a digital logic device according to the embodiments of the present invention.

[0106] According to one aspect, a method for configuring a service in a communication network is provided, the method including: defining a service type by a service provider; associating the service type with an Enhanced Distributed Channel Access (EDCA) / Preferred Access Parameter Set in an Access Point (AP) infrastructure by the service provider of the service type; and then associating the service type with a WLAN entity.

[0107] In one aspect, the WLAN entity is a multi-link device (MLD) and the service type is associated with a set of links of the WLAN entity.

[0108] In one aspect, the set of links includes a subset of links used for a service type.

[0109] In one aspect, the set of links includes a subset of links that are prohibited from use for the service type.

[0110] In one aspect, the definition of the service type includes enumerating a plurality of service types that include the service type.

[0111] In one aspect, the association of a service type with an EDCA / priority access parameter set is based on the traffic characteristics of the service type.

[0112] In one aspect, the service type is associated with an application of a non-AP STA.

[0113] According to one aspect, a method for configuring a service in a communication network is provided, the method including assigning, by an authentication server, a service type to an authorization policy, associating the authorization policy with a non-AP station (STA) or a non-AP MLD wireless local area network (WLAN) entity, and transmitting the service type network policy to an AP infrastructure in response to the WLAN entity authenticating to the communication network.

[0114] In one aspect, transmitting the network policy to the AP infrastructure is performed using an authentication, authorization, and accounting (AAA) protocol.

[0115] According to one aspect, a method for configuring a service in a communication network is provided, the method including transmitting, by a WLAN entity, an NSEP priority access frame, the frame including a service type of the service.

[0116] In one aspect, the frame is a NSEP priority access request frame.

[0117] In one aspect, the frame is an NSEP priority access response frame.

[0118] In one aspect, the NSEP priority access response frame is transmitted in response to the WLAN entity receiving the NSEP priority access request frame.

[0119] In one aspect, the NSEP priority access response frame is transmitted to modify parameters of a previously established NSEP service operation.

[0120] In one aspect, the WLAN entity is an access point (AP) and the frame further includes an EDCA or preferred access parameter set used for the service type.

[0121] In one aspect, the AP is an AP that belongs to an AP Multi-Link Device (MLD), and the frame further includes a set of links of the service type.

[0122] In one aspect, the WLAN entity is a non-access point (AP) station (STA).

[0123] In one aspect, the non-AP STA belongs to a non-AP multi-link device (MLD), and the request frame further includes a set of links of the service type.

[0124] In one aspect, the set of links includes a subset of links used for a service type.

[0125] In one aspect, the set of links includes a subset of links that are prohibited from use for the service type.

[0126] In one aspect, the link complies with a network policy received from the subscription service provider network.

[0127] In one aspect, the transmission of the NSEP priority access request frame is sent in response to the MAC layer receiving a request primitive from the SME layer of the WLAN entity.

[0128] According to one aspect, a method for configuring a priority access service in a communication network is provided, the method including: encoding, by a WLAN entity, a service type of the priority service as an enumeration, inserting, by the WLAN entity, the service type into a frame, and transmitting, by the WLAN entity, the frame.

[0129] In a further aspect, a priority access service is established between two peer MLDs, and the method further includes encoding, by the WLAN entity, link information of a link associated with the priority service as a plurality of octets, the plurality of octets indicating whether the link may be used for the priority service or is prohibited from being used for the priority service, and inserting, by the WLAN entity, the link information into a frame.

[0130] In one aspect, the frame is an NSEP priority access request frame or an NSEP priority access response frame.

[0131] In one aspect, the frame is transmitted by an access point (AP) or an AP multilink device (MLD), and the frame further includes a set of EDCA or prioritized access parameters based on traffic characteristics of the prioritized service.

[0132] In one aspect, the frame is an NSEP priority access response frame and is transmitted in response to receiving an NSEP priority access request frame.

[0133] In one aspect, the frame is an NSEP priority access response frame and is sent to modify a previously established NSEP service operation.

[0134] While the invention has been described with reference to particular features and embodiments thereof, it is apparent that various modifications and combinations can be made thereto without departing from the invention. Accordingly, the specification and drawings should be considered merely as illustrative of the invention as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations, or equivalents that are within the scope of the invention. [Explanation of symbols]

[0135] 102 Wired Gateway 104 LAN 105 AP, AP MLD, WLAN entities 105a AP 105b AP 105c AP 106 Non-AP MLD, WLAN entity 108 AP 110 Non-AP STA 112 AP 114 Non-AP STA 200 Network Topology 204 Network Access Infrastructure 206 Service Provider 208 SSPN 214 Access Network 216 Policy Server 218 AAA Server 302 Service type, priority service 304 Priority Access Parameter Set 308 Link Set 502 Primitive 504 NSEP Priority Access Request Frame 506 Primitive 508 Primitive 510 NSEP Priority Access Response Frame 512 Primitive 602 Service Type Field 604 NSEP Link Element 606 Link Count Field 608 Forbidden Link Field, Flag 610 Link ID number field, Link ID information field 612 Link ID Information Field 702 SMEs 704 MAC layer 706 MAC layer 708 SMEs 900 Electronic Devices 910 Processor 920 Memory 925 Bidirectional Bus 930 Non-transient bulk storage, bulk storage elements 940 I / O Interface 945 I / O Devices 950 Network Interface 960 Transceiver 970 Video Adapter 975 Display

Claims

1. 1. A method for configuring services in a communications network, comprising: defining, by a service provider, a service type; associating the service type with an Enhanced Distributed Channel Access (EDCA) / priority access parameter set in an access point (AP) infrastructure by the service provider of the service type; provisioning a wireless local area network (WLAN) entity with said service type; A method comprising:

2. The method of claim 1 , wherein the WLAN entity is a multi-link device (MLD) and the service type is associated with a set of links of the WLAN entity.

3. The method of claim 2 , wherein the set of links comprises a subset of links used for the type of service.

4. The method of claim 2 or 3, wherein the set of links comprises a subset of links that are prohibited from use for the service type.

5. 5. The method of claim 1, wherein the step of associating the service type with an EDCA / priority access parameter set is based on traffic characteristics of the service type.

6. The method of claim 1 , wherein provisioning the EDCA / priority access parameter set in the AP infrastructure is performed using an Authentication, Authorization, and Accounting (AAA) protocol.

7. 1. A method for configuring services in a communications network, comprising: transmitting, by a wireless local area network (WLAN) entity, a National Security and Emergency Preparedness (NSEP) priority access frame, said frame including a service type of said service; A method comprising:

8. 8. The method of claim 7, wherein the frame is either an NSEP priority access request frame or an NSEP priority access response frame.

9. The method of claim 8 , wherein the NSEP priority access response frame is transmitted to modify parameters of a previously established NSEP service operation.

10. 10. The method of claim 7, wherein the WLAN entity is an access point (AP), and the frame further includes a set of Enhanced Distributed Channel Access (EDCA) parameters or prioritized access parameters used for the service type.

11. The method of claim 10 , wherein the AP is an AP belonging to an AP Multi-Link Device (MLD), and the frame further includes a set of links of the service type.

12. The method according to claim 7, wherein the WLAN entity is a non-Access Point (AP) Station (STA) belonging to a non-AP Multi-Link Device (MLD), and the request frame further includes a set of links of the service type.

13. The method of claim 12 , wherein the set of links comprises a subset of links used for the service type.

14. The method of claim 12 or 13, wherein the set of links comprises a subset of links that are prohibited from use for the service type.

15. The method of claim 12 , wherein the set of links conforms to a network policy received from a subscription service provider network.

16. 16. The method according to claim 7, wherein the step of transmitting an NSEP priority access request frame is transmitted in response to a medium access control (MAC) layer receiving a request primitive from a station management entity (SME) layer of the WLAN entity.

17. 1. A method for configuring a priority access service in a communications network, comprising the steps of: encoding, by a wireless local area network (WLAN) entity, a service type of the preferred service as an enumeration; inserting, by the WLAN entity, the service type into a frame; transmitting, by the WLAN entity, the frame; A method comprising:

18. The priority access service is established between two peer multi-link devices (MLDs), and the method includes: encoding, by the WLAN entity, link information of a link associated with the priority service as a number of octets, the number of octets indicating whether the link may be used for the priority service or is prohibited from being used for the priority service; inserting, by the WLAN entity, the link information into the frame; 20. The method of claim 17, further comprising:

19. 19. The method of claim 17 or 18, wherein the frame is a National Security and Emergency Preparedness (NSEP) priority access request frame or a NSEP priority access response frame.

20. 20. The method of claim 17, wherein the frame is transmitted by a station (STA) or a multilink device (MLD), and the frame further includes an enhanced distributed channel access (EDCA) parameter or a set of priority access parameters based on traffic characteristics of the priority service.

Images