UNINTERRUPTED MULTIPLE BASIC SERVICE SET IDENTIFIERS

Abstract

A procedure that includes the following: Determine, by means of an access point (AP) (170; 302), features of a set of virtual access points (VAPs) associated with the access point; Generating, by the AP, a Multiple Basic Service Set Identifier (MBSSID) VAP based on the features of the set of VAPs, where the MBSSID VAP includes a non-communication-supporting VAP; Generating, by the AP, an MBSSID beacon (400) based on the MBSSID VAP serving as the transmitted VAP (TX-VAP) for the MBSSID beacon, where the MBSSID beacon announces the MBSSID VAP as a hidden Service Set Identifier (SSID); and Transmitted by the AP, the MBSSID beacon.

Description

background

[0001] Today, advances in wireless networking technology are driving technological improvements in other technologies and industries. For example, various industries rely on wireless networking technologies for communication, data storage, and service delivery. In wireless networks, client devices establish a wireless connection to a network via an access point (AP). The AP connects to wired resources and facilitates the use of these resources by client devices wirelessly connected to the AP. The increasing use of wireless networking technologies, among other factors, leads to various technological challenges in the field of wireless networks. The Institute of Electrical and Electronics Engineers (IEEE) has issued several standards, such as 802.The 11 standard was developed to address various challenges in the field of wireless network technologies. Nevertheless, wireless network technologies continue to face technological challenges as their use increases.

[0002] US 2018 / 0302783A1 describes an access point and a procedure for communicating with a wireless device. The access point supports two or more virtual networks. The procedure includes receiving a test request from the wireless device, the test request indicating whether or not the wireless device supports the Multiple Basic Service Set Identifier (M-BSSID) capability; and sending a test response to the wireless device according to the information contained in the test request.

[0003] US 2020 / 0 015 181 A1 describes systems, methods, and devices, including computer programs encoded on computer-readable media, for analyzing management frames for multiple basic service sets (BSSs). In one embodiment of US 2020 / 0 015 181 A1, a wireless node can receive a first management frame from a wireless communication (Wi-Fi) device operating multiple virtual access points (VAPs), each associated with multiple BSSs. The wireless node can determine, based on the arrangement of multiple BSS profiles within one or more management frames, whether the first management frame contains a BSS profile of a BSS associated with the wireless node. Based, at least partially, on the finding that the first management frame contains the BSS profile of the BSS associated with the wireless node, the wireless node can decide to further process the first management frame.

[0004] US 2019 / 0 174 577 A1 describes methods and devices for communication in a wireless network. In one embodiment of US 2019 / 0 174 577 A1, a wireless communication (Wi-Fi) device can operate a first virtual access point (VAP) associated with a first basic service set (BSS), and at least one second VAP associated with a second BSS. The Wi-Fi device can generate a management frame and output it for transmission to a first station (STA) associated with the first BSS. The management frame can contain one or more signaling attributes indicating that the first VAP associated with the first BSS and the second VAP associated with the second BSS are operating on the Wi-Fi device.The first STA can receive the management frame and, based on one or more signaling attributes of the management frame, determine that the first VAP connected to the first BSS and the second VAP connected to the second BSS are operating on the WLAN device. Brief description

[0005] A method according to claims 1 to 8, a system according to claims 9 to 14 and a non-transitory, computer-readable storage medium according to claims 15 to 20 is disclosed. Brief description of the drawings

[0006] The present disclosure is described in detail in accordance with one or more different embodiments with reference to the following figures. The figures serve only for illustration and represent only typical or exemplary embodiments. Fig. shows an example of the use of a wireless network that can be implemented for an organization, e.g., a company, an educational institution, a government agency, a healthcare facility, or another organization. Fig. shows an example of an access point (AP) in which one or more MBSSIDs (Multiple Basic Service Set Identifiers) for virtual access points (VAPs) can be implemented. Fig. shows a block diagram of an example computer component or device associated with providing uninterrupted MBSSIDs. Fig. shows an example of a wireless deployment associated with providing uninterrupted MBSSIDs. Fig. shows an example of an MBSSID beacon and an example of an MBSSID element. Fig. shows an example of MBSSID elements. Fig. is an example of a computer component that can be used to implement various features of the embodiments described in the present disclosure.

[0007] The illustrations are not exhaustive and do not limit the present disclosure to the exact form that is disclosed. Detailed description

[0008] As various technologies increasingly rely on wireless networking technologies, there is a need to expand the capabilities of wireless networks to accommodate a larger number of devices with varying configurations. The use of virtual access points (VAPs) allows a single access point (AP) to present itself as multiple APs. To client devices, a VAP appears as a separate AP. A VAP can be associated with its own set of network properties, such as authentication and encryption, and its set of network properties can be specified by a Basic Service Set Identifier (BSSID). Thus, each VAP can be associated with a BSSID that specifies a set of network properties associated with the VAP. The AP sends these BSSIDs as beacon frames to announce the presence of the VAPs.The beacon frames are sent to client devices, which use the BSSIDs associated with the beacon frames to determine a VAP to connect to. In some installations, a single AP can support multiple wireless networks with multiple VAPs. In these cases, transmitting a separate BSSID as a separate beacon frame for each VAP can be inefficient and negatively impact the wireless network connection quality.

[0009] Several approaches to addressing the inefficiencies and network disruptions associated with transmitting separate BSSIDs as separate beacon frames can involve the use of Multiple Basic Service Set Identifiers (MBSSIDs). When using MBSSIDs, multiple BSSIDs associated with VAPs provided by an AP are generally combined into a single MBSSID that the AP transmits. The information associated with the multiple BSSIDs is combined into a single MBSSID so that client devices can determine the network characteristics for each VAP associated with each BSSID. One approach to combining the information associated with the multiple BSSIDs is inheritance.Information associated with a VAP, which in this approach can be referred to as a transmitted VAP (TX VAP), is included in the MBSSID, and information associated with other VAPs, which in this approach can be referred to as non-transmitted VAPs (non-TX VAPs), is included in the MBSSID through inheritance. Generally, information associated with the non-TX VAPs that differs from that of the TX VAPs (e.g., non-inherited information) is included in the MBSSID. Information belonging to non-TX VAPs that are identical to the TX VAP (e.g., inherited information) is derived from the information belonging to the TX VAP and included in the MBSSID. Transmitting an MBSSID allows the AP to use fewer beacon frames than if it were transmitting separate BSSIDs.While the use of MBSSIDs allows access points (APs) to efficiently transmit information associated with multiple BSSIDs, it also presents several technical challenges. For example, changing the transmitting VAP associated with an MBSSID can cause service interruptions for all VAPs connected to that MBSSID while the change is made and the MBSSID is updated. These interruptions can be exacerbated in deployments with numerous VAPs. Therefore, the use of MBSSIDs represents a technological challenge in wireless networking.

[0010] Accordingly, systems and methods for providing uninterrupted multiple Basic Service Set Identifiers (MBSSIDs) are disclosed. In various embodiments, a virtual access point (VAP) can be created to enable uninterrupted MBSSIDs. This generated VAP can be referred to, for example, as an MBSSID VAP (or "ghost" VAP). In some embodiments, an access point (AP) can determine characteristics or network properties of VAPs connected to the AP. The AP can create a VAP (e.g., an MBSSID VAP) based on the properties of the VAPs. An MBSSID can be generated using the MBSSID VAP as a transmitted VAP (TXVAP) of the MBSSID. The generated MBSSID VAP can be advertised as a hidden Service Set Identifier (SSID) to prevent client devices from attempting to connect to the MBSSID VAP. Attempts to connect to the MBSSID VAP can be rejected by the AP.In this way, the MBSSID VAP acts as a TX-VAP, which is not subject to changes and does not need to be interrupted to make modifications. Because the MBSSID VAP acts as a TX-VAP that is not subject to changes or interruptions, the MBSSID based on the MBSSID VAP does not need to be interrupted to make changes to other VAPs connected to the MBSSID.

[0011] A wireless network might contain an access point (AP) that provides a number of virtual access points (VAPs). The VAPs provided by the AP can share various common characteristics. For example, the VAPs might use a common operating class, channel, channel access capabilities, and a common radio (or antenna connector of a common radio). An MBSSID VAP can be generated based on these common characteristics. For example, the MBSSID VAP can be generated to have the same characteristics as these common ones. The Basic Service Set Identifier (BSSID) of the MBSSID VAP can contain information associated with these common characteristics. An MBSSID can be generated for the VAPs provided by the AP, where the BSSID of the MBSSID VAP is the transmitting VAP of the MBSSID.The MBSSID VAP is not used to communicate with client devices on the wireless network, and attempts to connect to the MBSSID may be rejected. In this example, changes can be made to the VAPs without interrupting the MBSSID for those VAPs. For example, a change can be made to the properties of one of the VAPs provided by the AP. Because the change is not made to the MBSSID's TX VAP (i.e., the MBSSID VAP), the MBSSID does not need to be interrupted for the change. The AP can continue to advertise the MBSSID with updated information containing the change. As this example demonstrates, by creating an MBSSID VAP that acts as the TX VAP for an MBSSID, changes can be made to VAPs advertised by the MBSSID without interruption.The presented systems and methods are therefore a response to the technological challenges in the field of wireless network technologies by providing uninterrupted MBSSIDs, as further described here.

[0012] Before describing in detail the embodiments of the disclosed systems and methods, it may be useful to describe an example of a network installation that can be used to implement these systems and methods in various applications. Fig. This diagram shows an example of a network configuration 100 that can be implemented for an organization, such as a business, educational institution, government agency, healthcare facility, or other organization. This diagram illustrates an example of a configuration implemented in an organization with multiple users (or at least multiple client devices 110) and potentially multiple physical or geographic locations 102, 132, 142. The network configuration 100 can include a primary location 102 that communicates with a network 120. The network configuration 100 can also include one or more remote locations 132, 142 that connect to the network 120.

[0013]

[0009] The primary location 102 can comprise a primary network, which may be, for example, an office network, a home network, or another network installation. The primary network 102 can be a private network, such as a network that may include security and access controls to restrict access to authorized users of the private network. Authorized users may include, for example, employees of a company at the primary location 102, residents of a house, customers of a company, etc.

[0014] In the example shown, the primary site 102 contains a control unit 104 that communicates with the network 120. The control unit 104 can provide communication with the network 120 for the primary site 102, although it need not be the only point of communication with the network 120 for the primary site 102. A single control unit 104 is shown, although the primary site may include multiple control units and / or multiple communication points with the network 120. In some embodiments, the control unit 104 communicates with the network 120 via a router (not shown). In other embodiments, the control unit 104 provides router functions to the devices at the primary site 102.

[0015] A Controller 104 can configure and manage network devices, for example, at the main site 102, and can also manage network devices at remote sites 132 and 134. The Controller 104 can configure and / or manage switches, routers, access points, and / or client devices connected to a network. The Controller 104 itself can be an access point or provide the functionality of one.

[0016] The control unit 104 can communicate with one or more switches 108 and / or wireless access points (APs) 106ac. The switches 108 and the wireless APs 106a-c provide network connections to various client devices 110a-j. A client device 110a-j can access network resources via a connection to a switch 108 or AP 106a-c, including other devices on the network (primary site 102) and on the network 120.

[0017] Examples of client devices include: desktop computers, laptops, servers, web servers, authentication servers, Authentication Authorisation Accounting (AAA) servers, Domain Name System (DNS) servers, Dynamic Host Configuration Protocol (DHCP) servers, Internet Protocol (IP) servers, Virtual Private Network (VPN) servers, network policy servers, mainframes, tablet computers, e-readers, netbook computers, televisions and similar displays (e.g., smart TVs), content receivers, set-top boxes, personal digital assistants (PDAs), mobile phones, smartphones, smart terminals, silent terminals, virtual terminals, video game consoles, virtual assistants, Internet of Things (IoT) devices, and the like.

[0018] Within primary site 102, a switch 108 is included as an example access point to the network established at primary site 102 for wired client devices 110i-j. The client devices 110i-j can connect to the switch 108 and access other devices within network configuration 100 via the switch 108. The client devices 110i-j can also access network 120 via the switch 108. The client devices 110i-j can communicate with the switch 108 via a wired connection 112. In the example shown, the switch 108 communicates with the control unit 104 via a wired connection 112, although this connection could also be wireless.

[0019] The wireless access points (APs) 106a-c are another example of an access point to the network set up at the main site 102 for client devices 110a-h. Each AP 106a-c can be a combination of hardware, software, and / or firmware configured to provide wireless network connectivity for wireless client devices 110a-h. In the example shown, the APs 106a-c can be managed and configured by the controller 104. The APs 106a-c communicate with the controller 104 and the network via connections 112, which can be either wired or wireless interfaces.

[0020] Network configuration 100 can include one or more remote sites 132. A remote site 132 can be located at a different physical or geographic location than the primary site 102. In some cases, the remote site 132 may be located at the same geographic location or possibly in the same building as the primary site 102, but it does not have a direct connection to the primary site 102's network. Instead, the remote site 132 may use a connection through another network, such as network 120. A remote site 132, as defined in Fig. The location shown could be, for example, a satellite office, another floor, or a suite within a building. The remote location 132 can contain a gateway device 134 for communication with network 120. A gateway device 134 can be a router, a digital-to-analog modem, a cable modem, a DSL modem, or another network device configured to communicate with network 120. The remote location 132 can also contain a switch 138 and / or an access point 136, which communicates with the gateway device 134 either via wired or wireless connections. The switch 138 and the access point 136 provide network connectivity for various client devices 140a-d.

[0021] In various embodiments, the remote site 132 can communicate directly with the primary site 102, allowing client devices 140a-d at the remote site 132 to access the network resources at the primary site 102 as if they were located at the primary site 102. In such embodiments, the remote site 132 is managed by the control unit 104 at the primary site 102, and the control unit 104 provides the necessary connectivity, security, and accessibility that enable communication between the remote site 132 and the primary site 102. Once the remote site 132 is connected to the primary site 102, it can function as part of a private network provided by the primary site 102.

[0022] In various embodiments, the network configuration 100 can include one or more smaller remote sites 142, each comprising only a gateway device 144 for communication with the network 120 and a wireless access point 146 through which various client devices 150a-b access the network 120. Such a remote site 142 could, for example, be the home of a single employee or a temporary remote office. The remote site 142 can also communicate with the main site 102, allowing the client devices 150ab at the remote site 142 to access network resources at the main site 102 as if these client devices 150a-b were located at the main site 102. The remote site 142 can be managed by the controller 104 at the main site 102 to enable this transparency.After connecting to the main site 102, the remote site 142 can function as part of a private network provided by the main site 102.

[0023] Network 120 can be a public or private network, such as the internet or another communications network, that enables connection between the various locations 102, 130 to 142, and access to the servers 160a-b. Network 120 can include third-party telecommunications lines, such as telephone lines, broadcast coaxial cables, fiber optic cables, satellite communications, cellular communications, and the like. Network 120 can contain any number of intermediate network devices, such as switches, routers, gateways, servers, and / or controllers, which are not directly part of Network Configuration 100 but facilitate communication between the various parts of Network Configuration 100 and between Network Configuration 100 and other units connected to the network. Network 120 can contain various content servers 160a-b.Content servers 160a-b can include various providers of downloadable multimedia and / or streaming content, including audio, video, graphics, and / or text content, or any combination thereof. Examples of content servers 160a-b include web servers, streaming radio and video providers, and cable and satellite television providers. Client devices 110a-j, 140a-d, and 150a-b can request and access the multimedia content provided by the content servers 160a-b.

[0024] Although in the example of Fig. While only 10 client devices 110a-j are shown at the primary site 102, a network in different applications can encompass dramatically larger numbers of client devices. For example, different wireless networks can include hundreds, thousands, or even tens of thousands of client devices communicating with their respective access points (APs), possibly even simultaneously. Furthermore, multiple virtual access points (VAPs) can be used within these different wireless networks to provide different services to client devices. For instance, VAPs can be used to segment wireless networks of units sharing a room. The room can use a number of APs to provide wireless connectivity for client devices within the room. Each unit in the room can use its own VAPs, supported by the APs, to segment the client devices connected to each unit.VAPs can be made known to client devices in the room using an MBSSID beacon, which contains information about the APs. In this example, if changes are made to one of the VAPs, such as the transmitted VAP containing the MBSSID beacon, an interruption occurs because the MBSSID beacon is being modified. This interruption can be very disruptive for the devices in the room, as it is generally undesirable for a device to experience service interruptions due to the actions of other devices in a shared space. Therefore, using VAPs and MBSSIDs without mechanisms to facilitate uninterrupted MBSSIDs can lead to undesirable interruptions in wireless networks. As further described here, the disclosed systems and methods improve the use of VAPs and MBSSIDs in wireless networks by generating an MBSSID VAP that enables uninterrupted MBSSIDs.

[0025] Fig. Figure 1 is a schematic representation of an exemplary access point (AP) 170 according to one embodiment. AP 170 can be a network device comprising, for example, a processor 182, a memory / data storage device 174, a radio 176 (and a corresponding antenna 176a), and logic for a virtual access point (VAP) 178.

[0026] Memory 174 can include a fast read / write memory for storing programs and data during AP 180 operation, and a hierarchy of persistent memory such as ROM, EPROM, and flash memory for storing instructions and data required for AP 170 startup and / or operation. Memory 174 can store data to be transmitted by AP 170 or data to be received by AP 170. Memory 174 can store one or more of the various parameters (and their values) described herein. In some embodiments, Memory 174 is a distributed set of data storage components. Although not shown, it should be noted that AP 170 may also include input / output interfaces, including wired network interfaces such as IEEE 802.3 Ethernet interfaces, as well as wireless network interfaces such as IEEE 802.11 Wi-Fi interfaces, although the examples of disclosure are not limited to such interfaces.

[0027] The processor 172 is connected to at least one memory 174. The processor 172 can be any processing device, including but not limited to a MIPS-class processor, a microprocessor, a digital signal processor, an application-specific integrated circuit, a microcontroller, a state machine, or any type of programmable logic array.

[0028] The radio 176 can be a 5 GHz radio, a 2.4 GHz radio, a 6 GHz radio, or any other suitable wireless communication component. The radio 176 can be configured to both send and receive data. The radio 176 can facilitate communication with client devices 180a, 180b, and 180c. For example, the radio 176 can operate in a communication band (e.g., the 5.0 GHz UNII band) and in accordance with a specific wireless specification (e.g., 802.11ax). It is understood that the AP 170 can have multiple radios (physical and / or logical) and can have dedicated or shared channels for each radio or group of radios.

[0029] In some embodiments, the VAP logic 178 may comprise one or more functional units implemented using firmware, hardware, software, or a combination thereof to configure VAPs connected to AP 170 and / or client devices 180a, 180b, 180c for the transmission of data / frames to and from AP 170. Although the VAP logic 178 is depicted as being implemented on the AP 170, one or more physical or functional components of the prioritization logic 178 may be implemented on a separate device, such as an AP controller, for example, the controller 104 of Fig. can act.

[0030] As an illustrative example, VAP logic 178 can implement three VAPs connected to AP 170. Client devices 180a, 180b, and 180c can identify the three VAPs as separate APs with different capabilities. Client devices 180a, 180b, and 180c can connect to the three VAPs based on these different capabilities. In this example, client device 180a can connect to a first VAP, client device 180b to a second VAP, and STA 180c to a third VAP. In some cases, each VAP can be connected to its own Virtual Local Area Network (VLAN). In these cases, client device 180a can be connected to a first VLAN assigned to the first VAP, client device 180b can be connected to a second VLAN assigned to the second VAP, and client device 180c can be connected to a third VLAN assigned to the third VAP.Since client devices 180a, 180b, 180c are connected to different VLANs belonging to different VAPs, client devices 180a, 180b, 180c operate as if they were connected to different APs, even though they communicate with AP 170.

[0031] In this illustrative example, the AP 170 can announce the different capabilities (or properties) of the three VAPs using an MBSSID beacon (Multiple Basic Service Set Identifier). Each of the three VAPs can be assigned its own BSSID (Basic Service Set Identifier). The MBSSID beacon combines the BSSIDs through inheritance. The MBSSID beacon contains a transmitted BSSID of a transmitted VAP (TX VAP). The transmitted BSSID contains information elements for the attributes of the transmitted VAP. The MBSSID also contains non-transmitted BSSIDs of non-transmitted VAPs (non-TX VAPs). The non-transmitted BSSIDs contain information elements that indicate which attributes of the transmitted VAP are inherited by the non-transmitted VAPs and which attributes of the transmitted VAP are not inherited by the non-transmitted VAPs. For example, For example, the first of the three VAPs can be used as the sending VAP for the MBSSID beacon.The MBSSID beacon can contain information elements that describe the characteristics of the first VAP. The MBSSID beacon can also contain information elements that describe the characteristics of the second and third VAPs of the three VAPs through inheritance. For characteristics of the second VAP that are not inherited from the first VAP, information elements can be included in the MBSSID beacon specifying these uninherited characteristics. For characteristics of the second VAP that were inherited from the first VAP, no information elements are included in the MBSSID beacon for these inherited characteristics. A client device, such as ClientDevice 180b, can determine these inherited characteristics using the information elements associated with the first VAP, which in this example is the TX-VAP.Similarly, for features of the third VAP that were not inherited from the first VAP, information elements can be included in the MBSSID beacon specifying these uninherited features. For features of the third VAP that were inherited from the first VAP, no information elements are included in the MBSSID beacon for these inherited features. A client device, such as client device 180c, can determine these inherited features using the information elements associated with the first VAP, which in this example is TXVAP.

[0032] Fig. This shows an example of a computer component 200 that can be used to implement uninterrupted multiple basic service set identifiers (MBSSIDs) in accordance with various implementations. The example computer component 200 could be, for example, an access point (AP), a server computer, a controller, or another similar computer component capable of processing data. In the example implementation of Fig. The computer component 200 comprises a hardware processor 202 and a machine-readable storage medium 204.

[0033] The hardware processor 202 may be one or more central processing units (CPUs), semiconductor-based microprocessors, and / or other hardware devices capable of retrieving and executing instructions stored in the machine-readable memory medium 204. The hardware processor 202 can retrieve, decode, and execute instructions, such as instructions 206-212, to control processes or operations for opportunistic spatial reuse. Alternatively or in addition to retrieving and executing instructions, the hardware processor 202 may include one or more electronic circuits comprising electronic components for performing the functionality of one or more instructions, such as a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or other electronic circuits.

[0034] A machine-readable storage medium, such as the machine-readable storage medium 204, can be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. The machine-readable storage medium 204 can be, for example, random access memory (RAM), non-volatile random access memory (NVRAM), electrically erasable programmable solid-state memory (EEPROM), a storage device, an optical disk, or the like. In some embodiments, the machine-readable storage medium 204 can be a non-transitory storage medium, the term "non-transitory" excluding the transitive transmission signals. As detailed below, the machine-readable storage medium 204 can be encoded with executable instructions, such as instructions 206-212.

[0035] The hardware processor 202 can execute instruction 206 to determine the characteristics of a set of virtual access points (VAPs) associated with an access point. In various embodiments, an AP can provide a number of VAPs, and each VAP can be associated with corresponding characteristics (e.g., network properties, capabilities). Among these characteristics, there can be some that are common to all VAPs. For example, characteristics such as operating class, channel, channel access function, antenna connector, radio, MAC (Medium Access Control) capabilities, physical layer capabilities, and the like can be common to the VAPs associated with an AP. In addition, various radio-specific characteristics such as country, spatial reuse capabilities, high efficiency, band capabilities, etc., can be the same for the VAPs associated with the AP. Other characteristics, such as...dot11 protocol capabilities are less likely to be present in the VAPs connected to the AP. An MBSSID beacon can be used to publicize the properties of the VAPs connected to an AP. To enable the MBSSID beacon to efficiently publicize the properties of the VAPs connected to the AP, a VAP with more common properties than other VAPs connected to the AP can be selected as the transmitting VAP (TX VAP). Using a transmitting VAP with more common properties allows the MBSSID to efficiently use inheritance to describe the properties of the other VAPs. To generate an MBSSID VAP and enable uninterrupted MBSSIDs, the MBSSID VAP can be generated based on the common properties of the VAPs connected to an AP.

[0036] For example, a wireless network, such as the one in Fig. The network configuration shown includes an access point (AP) that provides a set of virtual access points (VAPs). The VAPs provided by the AP can be associated with various attributes, some of which are common to all VAPs and some of which are unique to each VAP. Based on the attributes assigned to each VAP, a set of common attributes for the VAPs can be determined. In this example, the VAPs can be associated with the same channel and channel access capabilities. Furthermore, the VAPs can share radio-specific attributes because they are provided by the same AP. In this example, the VAPs can be associated with the same HE capabilities and spatial reuse capabilities. An MBSSID VAP, to facilitate uninterrupted MBSSIDs, can be generated based on these common attributes.

[0037] Hardware processor 202 can execute instruction 208 to generate an MBSSID VAP based on the features of the VAP group. In various embodiments, an MBSSID VAP can be generated based on the common features of a set of VAPs. By generating the MBSSID VAP based on the common features of the set of VAPs, an MBSSID beacon that uses the MBSSID VAP as its TX VAP can efficiently utilize inheritance to reduce the beacon size. Furthermore, the MBSSID VAP can be generated to contain only the common features of the VAP set and no features unique to that set. For example, the MBSSID VAP can be generated to contain only radio-specific features common to all VAPs.Because the MBSSID VAP is generated to enable an uninterrupted MBSSID, rather than to facilitate communication with client devices, it can be generated with a number of features that might be considered incomplete. By generating an MBSSID VAP that only carries the common features of the VAP set, the MBSSID VAP has a smaller impact on the beacon size of the resulting MBSSID beacon used as the transmitting VAP, since the MBSSID VAP does not carry any features not inherited by the other VAPs associated with the MBSSID beacon. Furthermore, because the MBSSID VAP is generated to enable an uninterrupted MBSSID, rather than to facilitate communication with client devices, it can also be generated to discourage connections from client devices. The MBSSID VAP can be generated with a hidden Service Set Identifier (SSID) or with a nameless SSID of zero length.To ensure that client devices do not connect to the MBSSID VAP, an access point (AP) associated with the MBSSID VAP can reject connection attempts from client devices attempting to connect to the MBSSID VAP. Additionally or alternatively, the AP associated with the MBSSID VAP can ignore or prevent responses to unicast and / or broadcast probe requests for the MBSSID VAP. Connection attempts from client devices can be rejected by sending an authentication response with an error status or an association response with an error status.

[0038] For example, a wireless network, such as the one in Fig. The network configuration shown includes an access point (AP) that provides a set of virtual access points (VAPs). An MBSSID VAP, which enables uninterrupted MBSSIDs, can be generated based on common characteristics of the VAPs. For example, the VAPs can be assigned to the same operating class, channel, and channel access capabilities. The MBSSID VAP can be generated to have only these common characteristics. Other characteristics that may differ from VAP to VAP, such as the capabilities of the dot11 protocol, are not included in the MBSSID VAP's characteristics. Furthermore, the MBSSID VAP can be generated with a nameless, zero-length SSID to prevent client devices from attempting to connect to it. An MBSSID beacon can be created using the MBSSID VAP as the transmitting VAP.

[0039] Hardware processor 202 can execute instruction 210 to create an MBSSID beacon based on the MBSSID VAP as a transmitted VAP (TX-VAP) for the MBSSID beacon. In various embodiments, an MBSSID VAP can facilitate uninterrupted MBSSIDs by acting as the TX-VAP of an MBSSID beacon. The MBSSID beacon can contain information elements that describe the properties of the TX-VAP. The MBSSID beacon can also contain information elements that describe the properties of non-TX-VAPs. The properties of the non-TX-VAPs are included through inheritance. That is, if the non-TX-VAPs associated with an MBSSID have the same properties as the TX-VAP associated with the MBSSID, these properties are described in the information elements associated with the TX-VAP and not in the information elements associated with the non-TX-VAPs.When the MBSSID beacon is received by a client device or another network device, the characteristics of the non-TXVAPs shared with the TX-VAP are determined based on the information elements associated with the TX-VAP and the absence of information elements describing these characteristics that are associated with the non-TX-VAPs. Conversely, if the non-TX-VAPs associated with an MBSSID have different characteristics than the TX-VAP associated with the MBSSID, these characteristics are described in information elements associated with the non-TX-VAPs. When the MBSSID beacon is received by a client device or another network device, the characteristics of the non-TX-VAPs that differ from the TX-VAP are determined based on the information elements associated with the non-TX-VAPs.The information elements associated with a TX-VAP of an MBSSID beacon can contain various pieces of information, including properties generally common to all VAPs associated with an AP. This information includes, for example, operating class, channel, channel access capabilities, antenna connector, radio, MAC capabilities, PHY capabilities, timestamps and beacon intervals, Traffic Indication Map (TIM), DSSS (Direct Sequence Spread Spectrum) parameters, IBSS (Independent Basic Service Set) parameters, country, channel change announcements, enhanced channel change announcements, wide bandwidth channel changes, transmit power envelope, supported operating classes, HT (High Throughput) capabilities, VHT (Very High Throughput) capabilities, S1G beacon capabilities, short beacon intervals, HE capabilities, BSS color-changing announcements, spatial reuse parameters, and the like.

[0040] For example, a wireless network, such as the one in Fig. The network configuration shown includes an access point (AP) that provides a number of virtual access points (VAPs). An MBSSID VAP, to facilitate uninterrupted MBSSIDs, can be created based on common characteristics of the VAPs. An MBSSID beacon can be created using the MBSSID VAP as the transmitting VAP. The MBSSID beacon can contain information elements describing the common characteristics of the transmitting VAP, in this example, the operating class, channel, and channel access capabilities. The MBSSID beacon can also contain information elements describing the various characteristics of the other VAPs provided by the AP, i.e., the non-transmitting VAPs associated with the MBSSID. For example, the MBSSID beacon can contain information elements associated with the non-transmitting VAPs describing their different dot11 protocol capabilities.The MBSSID beacon, generated by the MBSSID VAP and the VAPs provided by the AP, can be transmitted to publicize the capabilities of the different VAPs.

[0041] Hardware processor 202 can execute instruction 212 to transmit the MBSSID beacon. In various implementations, an access point (AP) sends an MBSSID beacon in one or more beacon frames. The MBSSID beacon can be sent at regular beacon intervals. These intervals can be adjusted and depend on various factors. Generally, a longer beacon interval may require less communication throughput from the AP than a shorter one. A longer beacon interval may also result in slower MBSSID transmission than a shorter interval if the MBSSID spans multiple beacon frames. In cases where an MBSSID spans multiple beacon frames, the MBSSID is available to a given virtual access point (VAP) once every p beacon intervals, where p is the profile periodicity.

[0042] For example, a wireless network, such as the one in Fig. The network configuration shown includes an access point (AP) that provides a number of virtual access points (VAPs). An MBSSID beacon can be generated using an MBSSID VAP based on common characteristics of the VAPs. The MBSSID beacon, generated by the MBSSID VAP and the VAPs provided by the AP, can be broadcast to publicize the capabilities of the different VAPs. For example, the AP can send the MBSSID beacon at regular intervals. In this example, a change can be made to any of the VAPs provided by the AP (other than the MBSSID VAP). Because the change is not made to the MBSSID-providing VAP, the MBSSID is not interrupted to implement the change, and the AP can continue to send the MBSSID beacon at regular intervals. Furthermore, no client devices need to be removed from the MBSSID due to the interruption.As described here, using an MBSSID VAP to facilitate uninterrupted MBSSIDs thus avoids wireless network interruptions due to changes to a VAP provided by an AP.

[0043] Fig. This shows an example wireless deployment 300, which is associated with the continuous provisioning of multiple Basic Service Set Identifiers (MBSSIDs). The example wireless deployment 300 can be associated with one or more functions, such as those provided by the example computer component 200. Fig. to be carried out. It should be understood that there may be additional, fewer, or alternative steps that are carried out in a similar or alternative order or in parallel, based on the various features and embodiments discussed here, unless otherwise specified.

[0044] As in Fig. As shown, the example wireless setup 300 includes an access point (AP) 302. The example wireless setup 300 also includes four client devices 306a-306d. The AP 302 can provide a number of virtual access points (VAPs). For example, the AP 302 can support up to sixteen VAPs in total, and the AP 302 can provide up to fifteen VAPs, reserving one VAP as the MBSSID VAP. As shown in Fig. As shown, AP 302 can have multiple radios. This example shows three radios, 304a and 304c, but a different number of radios is possible. In some cases, an AP can have several radios, some of which support MBSSID, while others do not. For example, radio 304c of AP 302 might support MBSSID, while radios 304a and 304b of AP 302 do not. In this example, an MBSSID VAP that is generated would be included in an MBSSID beacon transmitted by radio 304c.

[0045] In a concrete example, the AP 302 can provide four VAPs to client devices 306a-306d. For instance, each client device 306a-306d could be connected to a different entity in a shared space. The four VAPs allow client devices 306a-306d to access the respective resources associated with the different entities via the AP 302. The AP 302 can send an MBSSID beacon to announce the capabilities of the four VAPs. Because the client devices 306a-306d and the VAPs are connected to different entities, the VAPs can be managed by different administrators. If one administrator makes a change to the VAP they manage, this change can cause the other VAPs to be interrupted so that the AP can implement the change and update the MBSSID.To resolve this issue, an MBSSID VAP can be generated to enable uninterrupted MBSSIDs. The MBSSID VAP can be generated to have the characteristics common to the four VAPs. For example, the four VAPs can be assigned to the same operating class, channel, and channel access functions. The MBSSID VAP can then be generated to have only these common characteristics. The MBSSID VAP can be generated with a nameless, zero-length SSID to prevent client devices, such as client devices 306a-306d, from attempting to connect to the MBSSID VAP. Additionally, AP 302 can reject all connection attempts to the MBSSID VAP. The MBSSID beacon broadcast by AP 302 can be based on the MBSSID VAP, with the MBSSID VAP being the transmitted VAP (TX-VAP) of the MBSSID beacon. The MBSSID beacon can contain information about the four VAPs as non-transmitted VAPs (non-TX VAPs).In this way, the MBSSID VAP acts as a TX VAP, which is not subject to changes, and the MBSSID does not need to be interrupted to make changes to the other VAPs. Therefore, if one of the administrators makes a change to the VAP they manage, the other VAPs do not need to be interrupted so that the AP can implement the change and update the MBSSID.

[0046] Fig. Figure 400 shows a block diagram of an example MBSSID (Multiple Basic Service Set Identifier) ​​beacon and a block diagram of an example MBSSID element 420 according to various embodiments. In this example, the MBSSID beacon 400 can contain an MBSSID for virtual access points (VAPs) provided by an access point (AP). The MBSSID combines the BSSIDs of the VAPs by providing elements that describe a transmitted VAP (TX VAP) and elements that describe non-transmitted VAPs (non-TX VAPs) with respect to what is or is not inherited from the TX VAP. In this example, the MBSSID beacon 400 can contain TX VAP elements 402a, 402b, and non-TX VAP elements 404. TX-VAP elements 402a and 402b can contain information elements associated with a TX-VAP in the MBSSID beacon. MAC header 412 can correspond to the MAC header of the TX-VAP.Information elements 414a, 414b, 414c, and 414d can contain various attributes of the TX VAP. Non-TX VAP elements 404 can contain MBSSID elements 416a, 416b, and 416c associated with non-TX VAPs. MBSSID elements 416a, 416b, and 416c can contain various attributes of the non-TX VAPs. MBSSID elements 416a, 416b, and 416c describe the attributes of the non-TX VAPs with respect to what is and is not inherited from the attributes of the transferred VAP, as specified in information elements 414a, 414b, 414c, and 414d.

[0047] As in Fig. As shown, MBSSID element 420 can be implemented as MBSSID elements 416a, 416b, and 416c within MBSSID beacon 400. In this example, MBSSID element 420 can contain element ID 422, length 424, Max-BSSID indicator 426, and sub-elements 428. Element ID 422 specifies the ID of MBSSID element 420. Length 424 specifies the length of MBSSID element 420. Max-BSSID indicator 426 specifies the maximum number of supported BSSIDs. Sub-elements 428 contain the characteristics of the non-TX VAP corresponding to element ID 422. In this example, the element ID is 422, the length is 424, and the Max-BSSID indicator is 426 octets, and the sub-elements 428 have a variable length.

[0048]

[0044] Fig. Figure 430 shows a block diagram of two example MBSSID elements and a block diagram of an example MBSSID configuration element 460 in accordance with various embodiments. In this example, the MBSSID elements 430 comprise two MBSSID elements. The two MBSSID elements can be part of an MBSSID beacon, such as the MBSSID beacon 400 from [reference missing]. Fig. Element IDs 432a and 432b specify the IDs of the two MBSSID elements. Lengths 434a and 434b specify the lengths of the two MBSSID elements. Max BSSID values ​​436a and 436b specify the maximum number of supported BSSIDs. Sub-element 438a provides the attributes of a non-TX VAP corresponding to element ID 432a. Sub-element 438a can contain sub-element ID 440a, length 442a, and data 444a. Sub-element ID 440a specifies the ID of sub-element 438a. Length 442a specifies the length of sub-element 438a. Data 444a provides the attributes of the non-TX VAP corresponding to element ID 432a. In this example, data 444a provides an inherited capability of the non-TX VAP, and the inherited capability is provided by the non-transmitted (non-TX) BSSID capability 446, SSID 448, and Max-BSSID index 450. In this example, sub-element 438b provides the characteristics of a non-TX VAP corresponding to element ID 432b.Subelement 438b can contain subelement ID 440b, length 442b, and data 444b. Subelement ID 440b specifies the ID of subelement 438b. Length 442b specifies the length of subelement 438b. Data 444b provides the characteristics of the non-TX VAP corresponding to element ID 432b. In this example, 444b provides a non-inherited capability of the non-TX VAP, and the non-inherited capability is provided in non-inheritance element 352.

[0049] An MBSSID beacon can also contain MBSSID configuration elements, such as MBSSID configuration element 460. As in Fig. As shown, the MBSSID configuration element 460 can contain the element ID 462, the length 464, the element ID extension 466, the BSSID number 468, and the profile periodicity 470. The element ID 462 identifies an element to be configured by the MBSSID configuration element 460. The length 464 specifies the length of the MBSSID configuration element 460. The element ID extension 466 provides additional elements to be configured, for example, if the element ID 462 is set to 255. The BSSID number 468 specifies the total number of active BSSIDs in an MBSSID beacon. The profile periodicity 470 specifies a minimum number of beacon frames required to detect all non-TX VAPs in an MBSSID beacon. For example, if the profile periodicity is set to four (470), a client device can wait for at least four beacon intervals to fully receive an MBSSID beacon.

[0050] Fig.Figure 500 shows a block diagram of an exemplary computer system 500, in which various embodiments of the design described herein can be implemented. The computer system 500 comprises a bus 502 or other communication mechanism for transmitting information, and one or more hardware processors 504 connected to the bus 502 for processing information. The hardware processor(s) 504 can be, for example, one or more general-purpose microprocessors.

[0051] The Computer System 500 also includes a main memory 506, such as random access memory (RAM), a cache, and / or other dynamic memory devices connected to the bus 502 to store information and instructions to be executed by the processor 504. The main memory 506 can also be used to store temporary variables or other intermediate information during the execution of instructions to be carried out by the processor 504. When such instructions are stored in memory media accessible to the processor 504, the Computer System 500 becomes a specialized machine adapted to perform the operations specified in the instructions.

[0052] The Computer System 500 also includes a read-only memory (ROM) 508 or other static storage device connected to the bus 502 to store static information and instructions for the processor 504. A storage device 510, such as a magnetic disk, an optical disk, or a USB flash drive, etc., is provided and connected to the bus 502 to store information and instructions.

[0053] The computer system 500 can be connected via bus 502 to a display 512, such as a liquid crystal display (LCD) (or a touchscreen), to show information to a computer user. An input device 514, including alphanumeric and other keys, is coupled to bus 502 to transmit information and command selections to the processor 504. Another type of user input device is the cursor control 516, such as a mouse, trackball, or cursor direction keys, for transmitting directional information and command selections to the processor 504 and for controlling cursor movement on the display 512. In some embodiments, the same directional information and command selections as with cursor control can be implemented by receiving touch inputs on a touchscreen without a cursor.

[0054] The Computer System 500 can include a user interface module for implementing a graphical user interface, which can be stored on a mass storage device as executable software code that is executed by the computer device(s). This and other modules can include components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.

[0055] In general, the words "component," "engine," "system," "database," "data store," and the like, as used here, can refer to logic embodied in hardware or firmware, or to a collection of software instructions that may have entry and exit points and are written in a programming language such as Java, C, or C++. A software component may be compiled and linked into an executable program, installed in a dynamic link library, or written in an interpreted programming language such as BASIC, Perl, or Python. It is understood that software components may be invoked by other components or by themselves, and / or may be invoked in response to detected events or interruptions. Software components configured to run on computer devices may be stored on a computer-readable medium, such as...Software code may be provided on a compact disc, digital video disc, flash drive, magnetic disk, or other tangible medium, or as a digital download (and may initially be stored in a compressed or installable format that requires installation, decompression, or decryption before execution). Such software code may be stored partially or entirely in the memory of the executing computer device for execution by the computer device. Software instructions may be embedded in firmware, such as an EPROM. Furthermore, the hardware components may consist of interconnected logic units such as gates and flip-flops, and / or programmable units such as programmable gate arrays or processors.

[0056] The computer system 500 can implement the techniques described herein using custom hard-wired logic, one or more ASICs or FPGAs, firmware, and / or program logic, which, in combination with the computer system, make the computer system 500 a specialized machine or program it. According to one embodiment, the techniques described herein are executed by the computer system 500 in response to the processor(s) 504 executing one or more sequences of instructions contained in the main memory 506. Such instructions may be read into the main memory 506 from another storage medium, such as a storage device 510. The execution of the instruction sequences contained in the main memory 506 causes the processor(s) 504 to perform the process steps described herein.In alternative embodiments, hard-wired circuits can be used instead of, or in combination with, software instructions.

[0057] The term "non-volatile media" and similar terms as used here refer to all media that store data and / or instructions that cause a machine to operate in a particular way. Such non-volatile media can include both non-volatile and volatile media. Examples of non-volatile media include optical or magnetic disks, such as the Storage Device 510. Examples of volatile media include dynamic storage devices, such as the Main Memory 506. Common forms of non-volatile media include floppy disks, flexible disks, hard disks, solid-state drives, magnetic tapes or other magnetic data storage media, CD-ROMs, other optical data storage media, physical media with hole patterns, RAM, PROM and EPROM, FLASH-EPROM, NVRAM, other memory chips or cartridges, and their networked versions.

[0058] Non-transitory media differ from transmission media but can be used in conjunction with them. Transmission media are involved in the transfer of information between non-transitory media. Examples of transmission media include coaxial cable, copper and fiber optic cables, including the wires that make up the 502 bus. Transmission media can also take the form of sound or light waves, such as those generated in radio and infrared data communication.

[0059] The Computer System 500 also includes a Communications Interface 518, which is connected to the Bus 502. The Network Interface 518 provides a two-way data communication connection to one or more network connections that are connected to one or more local area networks (LANs). For example, the Communications Interface 518 could be an ISDN (Integrated Services Digital Network) card, a cable modem, a satellite modem, or a modem to establish a data communication connection to a corresponding type of telephone line. Another example: The Network Interface 518 could be a LAN (Local Area Network) card to establish a data communication connection to a compatible LAN (or a WAN component for communication with a WAN). Wireless connections can also be implemented.In each of these implementations, the network interface 518 sends and receives electrical, electromagnetic, or optical signals that transmit digital data streams representing different types of information.

[0060] A network connection typically enables data communication over one or more networks to other data devices. For example, a network connection might establish a connection over a local area network to a host computer or to data devices operated by an Internet service provider (ISP). The ISP, in turn, provides data communication services over the worldwide packet data communication network, commonly known today as the "Internet." Both the local area network and the Internet use electrical, electromagnetic, or optical signals to transmit digital data streams. The signals in the various networks and the signals on the network link and across the 518 communication interface, which transmit digital data to and from the 500 computer system, are examples of transmission media.

[0061] The Computer System 500 can send messages and receive data, including program code, via the network(s), network connection, and communication interface 518. In the Internet example, a server could transmit requested code for an application program via the Internet, the ISP, the local network, and communication interface 518.

[0062] The received code can be executed by the 504 processor as soon as it is received, and / or stored in the 510 memory device or other non-volatile memory for later execution.

[0063] Each of the processes, methods, and algorithms described in the preceding sections can be embodied in code components and fully or partially automated by them, which are executed by one or more computer systems or computer processors with computer hardware. The one or more computer systems or computer processors can also be operated in such a way as to support the execution of the corresponding operations in a cloud computing environment or as Software as a Service (SaaS). The processes and algorithms can be partially or fully implemented in application-specific circuits. The various features and procedures described above can be used independently or combined in various ways.Various combinations and subcombinations are intended to fall within the scope of this disclosure, and certain procedural or process blocks may be omitted in some implementations. The methods and processes described herein are also not restricted to any particular order, and the associated blocks or states may be executed in other suitable sequences, in parallel, or otherwise. Blocks or states may be added to or removed from the disclosed examples. The execution of certain operations or processes may be distributed across computer systems or computer processors that are not located in a single machine but are distributed across a number of machines.

[0064] As used herein, a circuit can be implemented in any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logic components, software routines, or other mechanisms can be implemented to form a circuit. In implementation, the various circuits described herein can be implemented as discrete circuits, or the described functions and features can be partially or completely distributed across one or more circuits.Even if various features or functional elements are individually described or claimed as separate circuits, these features and functions may be shared by one or more common circuits, and such a description is not intended to require or imply that separate circuits are necessary to implement these features or functions. If a circuit is implemented wholly or partially in software, such software may be implemented to operate with a computer or processing system capable of performing the functionality described therein, such as the Computer System 500.

[0065] As used herein, the term "or" can be understood in both an inclusive and an exclusive sense. Furthermore, the singular description of resources, processes, or structures is not to be understood as excluding the plural. Conditional expressions such as "could" or "may," unless expressly stated otherwise or understood differently in context, are generally intended to express that certain embodiments include certain features, elements, and / or steps, while other embodiments do not.

[0066] Unless explicitly stated otherwise, the terms and expressions used in this document, as well as their variations, are not to be understood as restrictive but rather as open-ended. Adjectives such as "conventional," "traditional," "normal," "standard," "known," and terms of similar meaning are not to be understood as limiting the subject matter described to a particular period or to an item available at a particular time, but should be understood as encompassing conventional, traditional, normal, or standard technologies that may be available or known now or at any time in the future. The presence of expansive words and expressions such as "one or more," "at least," "but not limited to," or similar expressions in some cases is not to be understood as implying that the narrower case is intended or required when such expansive expressions are absent.

Claims

[1] A procedure comprising the following: Determine, by means of an access point (AP) (170; 302), features of a set of virtual access points (VAPs) associated with the access point; Generating, by the AP, a Multiple Basic Service Set Identifier (MBSSID) VAP based on the features of the set of VAPs, where the MBSSID VAP includes a non-communication-supporting VAP; Generating, by the AP, an MBSSID beacon (400) based on the MBSSID VAP serving as the transmitted VAP (TX-VAP) for the MBSSID beacon, where the MBSSID beacon announces the MBSSID VAP as a hidden Service Set Identifier (SSID); and Transmitted by the AP, the MBSSID beacon. [2] The method of claim 1, further comprising: Causing the AP to make a change to a VAP in the set of VAPs, whereby an MBSSID associated with the set of VAPs remains active throughout the change. [3] The method according to claim 1, wherein determining features of a set of VAPs associated with the AP comprises: Determining radio-specific characteristics that are assigned to the AP. [4] The method according to claim 1, wherein the MBSSID-VAP is generated based on the radio-specific features that are assigned to the AP and that are common to the set of VAPs. [5] The method according to claim 1, wherein the MBSSID-VAP is created with the hidden SSID or the MBSSID-VAP is created with a nameless SSID of length zero. [6] The method according to claim 1, wherein the MBSSID-VAP is generated such that it has only features common to all VAPs in the set of VAPs. [7] The method according to claim 1, wherein the set of VAPs are non-transmitted VAPs (non-TX VAPs) for the MBSSID beacon. [8] The method according to claim 1, further comprising: Reject, by the AP, connection attempts to the MBSSID VAP; or Respond, through the AP, to connection attempts to the MBSSID-VAP with an authentication response containing an error status. [9] A system that includes the following: a processor; and a memory that is operationally connected to the processor and contains computer code which, when executed, causes the system to: To determine the characteristics of a set of virtual access points (VAPs) associated with an access point (AP) (170; 302); to generate a Multiple Basic Service Set Identifier (MBSSID) VAP based on the features of the set of VAPs, where the MBSSID VAP includes a non-communication-supporting VAP; to generate an MBSSID beacon (400) based on the MBSSID VAP serving as the transmitted VAP (TX-VAP) for the MBSSID beacon; to transmit the MBSSID beacon, where the MBSSID beacon announces the MBSSID VAP as a hidden Service Set Identifier (SSID); and to cause a change to be made to a VAP in the set of VAPs, whereby an MBSSID associated with the set of VAPs is continuously updated during the change. [10] The system according to claim 9, wherein determining features of a set of VAPs associated with the AP comprises: Determining radio-specific characteristics that are assigned to the AP. [11] The system according to claim 9, wherein the MBSSID-VAP is generated based on the radio-specific features that are assigned to the AP and that are common to the set of VAPs. [12] The system according to claim 9, wherein the MBSSID-VAP is created with the hidden SSID or the MBSSID-VAP is created with a nameless SSID of length zero. [13] The system according to claim 9, wherein the computer code further causes the system to: Ignore unicast probe requests and broadcast probe requests associated with the MBSSID VAP. [14] The system according to claim 9, wherein the computer code further causes the system to: Reject attempts to connect to the MBSSID VAP; or Attempts to connect to the MBSSID VAP are met with an authentication response containing an error status. [15] A non-transitory, computer-readable storage medium (506) comprising instructions which, when executed by at least one processor (504) of a computer system (500), cause the computer system to: To determine the characteristics of a set of virtual access points (VAPs) associated with an access point (AP) (170; 302); to generate a Multiple Basic Service Set Identifier (MBSSID) VAP based on the features of the set of VAPs, where the MBSSID VAP includes a non-communication-supporting VAP; to generate an MBSSID beacon (400) based on the MBSSID VAP serving as the transmitted VAP (TX-VAP) for the MBSSID beacon; to transmit the MBSSID beacon, where the MBSSID beacon announces the MBSSID VAP as a hidden Service Set Identifier (SSID); and Attempts to refuse to establish a connection to the MBSSID VAP. [16] The non-transitory, computer-readable storage medium according to claim 15, wherein the instructions further cause the computer system to: to cause a change to be made to a VAP in the set of VAPs, whereby an MBSSID associated with the set of VAPs is continuously updated during the change. [17] The non-transitory, computer-readable storage medium according to claim 15, wherein determining features of a set of VAPs associated with the AP comprises: Determining radio-specific characteristics that are assigned to the AP. [18] The non-transitory, computer-readable storage medium according to claim 15, wherein the MBSSID-VAP is generated based on the radio-specific features that are associated with the AP and are common to the set of VAPs. [19] The non-transitory, computer-readable storage medium according to claim 15, wherein the MBSSID-VAP is created with a hidden Service Set Identifier (SSID) or the MBSSID-VAP is created with a nameless SSID of zero length. [20] The non-transitory, computer-readable storage medium according to claim 15, wherein the MBSSID VAP is generated such that it has only features common to all VAPs in the set of VAPs.

Images