Methods implemented by a communication device in a wireless network and a client device, and associated devices
Patent Information
- Application Number
- EP2023828214
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-12-21
- Filing Date
- 2023-12-19
- Publication Date
- 2025-10-29
AI Technical Summary
In wireless communication networks, managing radio consumption effectively across multiple frequency bands is challenging due to the need for constant power usage and reduced sensitivity when deactivating radios, leading to inefficiencies and potential loss of connectivity with distant terminals.
A method where a communication device transmits information about the state of secondary access points, allowing client devices to request activation of deactivated access points based on specific requirements, and the device monitors and manages the activation and deactivation of access points to optimize radio usage.
This approach reduces unnecessary radio consumption while maintaining connectivity by activating access points only when needed, improving network efficiency and sensitivity.
Smart Images

Figure 1.1
Abstract
Description
[0001] METHODS IMPLEMENTED BY A COMMUNICATION DEVICE IN A WIRELESS NETWORK AND A CLIENT DEVICE, AND ASSOCIATED DEVICES
[0002] Technical field
[0003] A method implemented by a wireless communication device having multiple radios is described, as well as a method implemented by a client device adapted to associate with an access point of one of the radios. Also described are the communication device and the client device. One application is in the activation and deactivation of access points in a wireless network.
[0004] Technical background
[0005] To meet the growing need for data consumption, more and more frequency bands are being used for wireless transmissions. For example, in the 'Wi-Fi' technology defined by the IEEE 802.11 standard, the first products on the market operated in the 2.4 GHz (11 b) band, then 5 GHz (11 a) on 20 MHz wide communication channels. Subsequent generations of 'Wi-Fi' consolidated the use of these bands by increasing the size of the communication channels: 40 MHz with generation 4 (11 n / Wi-Fi 4), 160 MHz with generation 5 (11 ac / Wi-Fi 5). Generation 6 Wi-Fi (11 ax / Wi-Fi 6) also introduced the 6 GHz band with 160 MHz wide communication channels, while Generation 7 (11 be / Wi-Fi 7) expands the channel width in this band to 320 MHz. Now, there is talk of using millimeter wave bands, or 60 GHz, for the future Generation 8 Wi-Fi.
[0006] With each generation of Wi-Fi products, more and more radios must be integrated on the access point side within the same host device (gateway, router, etc.). In addition to the problems of coexistence of these various radios with each other, the consumption of the entire system becomes a critical point.
[0007] By default, all radios are turned on, whether or not there are client or endpoint devices associated with any of them.
[0008] A classic approach to reduce the consumption of a radio is to keep it on but in a degraded mode (i.e., several transmission / reception chains are cut) in order to be able to detect connection requests from terminals on said radio. In case of positive detection, the host device restores the radio to its nominal operating mode. The disadvantage of this approach is that it certainly reduces the consumption of the radio, but it does not completely cut it off. In addition, reducing the number of reception chains can lead to a loss of sensitivity of the radio, i.e. its ability to detect distant terminals.
[0009] Another approach is to keep one radio - called 'primary' - on and one (or more) radio(s) - called secondary(s) - off in a gateway. A switched-off secondary radio will only be switched back on if a terminal compatible with this secondary radio is detected, and which would associate with the primary radio. A radio can host one or more access points. Managing radio consumption then requires efficient management of hosted access points. It is therefore desirable to have an effective solution for managing hosted access points.
[0010] Summary
[0011] A first aspect relates to a method implemented by a communication device comprising a plurality of radios, each radio hosting at least one access point to a wireless network associated with the access point, an access point having one of at least an enabled state and a disabled state, comprising transmitting, by a first enabled access point of the communication device, information relating to a second access point even when this second access point is in the disabled state.
[0012] The dissemination of such information allows a client device to request, if necessary, the activation of an access point which is in a deactivated state, for example on the basis of the information obtained.
[0013] According to one or more embodiments, the information relating to the second access point comprises an identifier of the second access point and the state of the second access point.
[0014] According to one or more embodiments, the information relating to the second access point is transmitted in at least one of: a beacon emitted by the first access point; a response to a request for information from a client device.
[0015] It is thus possible to implement either a passive discovery of the second access point(s) by a client device by simply receiving a beacon, or an active discovery, in which the client device must issue a request to obtain the information.
[0016] In the context of an IEEE 802.11 type network, the identifier can for example be the BSSID.
[0017] According to one or more embodiments, the information relating to the second access point being transmitted in a response to a request for information from a client device adapted to associate with an access point, transmitted to the first access point, a beacon emitted by the first access point not comprising information relating to access points other than the first access point.
[0018] A client device can therefore only obtain information relating to the second access point if it is associated with the host device.
[0019] According to one or more embodiments, the state of the second access point further comprises a state characterizing a malfunction of the second access point.
[0020] A client device may use this information to decide not to send an activation request for an access point in a malfunctioning state. According to one or more embodiments, an activated access point broadcasts on a transmission channel, the information relating to the second access point includes, in the case where the second access point is in a deactivated state, the last transmission channel used by the second access point.
[0021] According to one or more embodiments, the information relating to the second access point comprises a list of transmission channels on which the second access point is capable of operating.
[0022] According to one or more embodiments, said list is included in the information relating to the second access point only in the case where this second access point is in the deactivated state.
[0023] According to one or more embodiments, the information relating to the second access point includes information representative of past statistics of the second access point when activated.
[0024] According to one or more embodiments, the method comprises receiving, from a client device, a request to activate the second access point in the deactivated state, the activation request comprising an identifier of the second access point in the deactivated state.
[0025] According to one or more embodiments, the activation request comprises at least one reason why the activation request is made by the client device.
[0026] According to one or more embodiments, a reason comprises one of: a traffic type to be supported; a current traffic type whose quality is not satisfactory on an activated access point; information representative of the fact that interference due to sources external to the client device is greater than a threshold; information representative of the fact that interference due to sources internal to the client device is greater than one.
[0027] According to one or more embodiments, the method comprises, in the event of acceptance of the request for activation of the second access point by the communication device, the transmission of a response to the client device having transmitted the activation request, the response comprising information indicating the acceptance of the activation request; the activation of the second access point for which activation was requested.
[0028] According to one or more embodiments, the method comprises, if the radio hosting the second access point for which activation has been requested is in a deactivated state, first activating that radio. According to one or more embodiments, the response comprises transmitting a first timeout defining a minimum time to wait before the second access point for which activation has been requested should actually be indicated as activated in the information relating to the second access point.
[0029] A client device receiving the first timeout then waits for the specified time before checking the activation status of the second access point.
[0030] According to one or more embodiments, the response includes a minimum duration during which the second access point will be maintained in an activated state by the communication device.
[0031] A client device receiving the minimum duration must then associate with the second access point before this duration expires. Beyond this time, the second access point may be disabled if necessary.
[0032] According to one or more embodiments, the method comprises, by the communication device:
[0033] - monitoring of the second access point activated on request;
[0034] - determining whether no client device is associated with it, and if so, deactivating the second access point.
[0035] According to one or more embodiments, the method comprises, following a positive determination, by the communication device, implementing the deactivation of the second access point if no client device has associated with the second access point before the elapse of a third timeout.
[0036] According to one or more embodiments, the acceptance of a request for activation, by the communication device, of an access point being subject to one or more conditions, the method comprises: once the second access point is activated, deactivating the second access point if at least one condition is no longer met.
[0037] According to one or more embodiments, the method comprises, prior to deactivation, transmitting, by the communication device, one of a message indicative of the upcoming deactivation to the client devices associated by the second access point or a message comprising a request to transition to an activated access point other than the second access point.
[0038] According to one or more embodiments, the method comprises transmitting a fourth time delay after which the deactivation of the second access point will be carried out. According to one or more embodiments, the method comprises, in the event of rejection of the request for activation of the second access point by the communication device, transmitting a response to the client device having transmitted the activation request, the response comprising information indicating the rejection of the activation request.
[0039] According to one or more embodiments, the response includes a second timeout indicating a minimum time that the client device will wait before repeating its activation request for the second access point.
[0040] If an activation request is rejected, a client device will have to wait the specified time before being able to resubmit a new request.
[0041] According to one or more embodiments, the response includes a reason for the rejection decision. According to one or more embodiments, the response includes information identifying an access point as a replacement for the second access point for which the activation request was rejected. According to one or more embodiments, the method includes transmitting an activated or deactivated state of the radio hosting the second access point.
[0042] A second aspect relates to a communication device comprising: a plurality of radios, each radio hosting at least one access point to a wireless network associated with the access point, an access point having one of an enabled state and a disabled state; and means for performing the steps of one of the above methods.
[0043] A third aspect relates to a method implemented by a client device adapted to associate via an access point of a communication device in a wireless network, an access point having one of at least an activated state and a deactivated state, the method comprising: obtaining from a first activated access point of the communication device, information relating to one or more second access points, even for the second access point(s) whose state is the deactivated state, the information comprising for a given second access point, a respective identifier and the respective state of the given second access point; in the case where at least one second access point is in the deactivated state, determining whether one of the one or more second access points is to be activated, and if so, transmitting, to the first access point, a request to activate the second access point to be activated.
[0044] An activation request may include one or more reasons for the request (e.g., the type of traffic the client device requires, etc.). The reason(s) may allow the host device to decide whether or not to activate the access point, or to propose an alternative access point.
[0045] According to one or more exemplary embodiments, the information relating to a second access point comprising an activation time indication, the indication comprising at least one of: an activation time of the second access point in the deactivated state; and an activation time of a radio hosting the second access point in the deactivated state; determining whether one of the one or more second access points is to be activated is based on the indication.
[0046] According to one or more exemplary embodiments, the information relating to a given second access point identifying a type of traffic supported by that given second access point, wherein determining whether one of the one or more second access points should be activated is a function of the type of traffic supported. According to one or more exemplary embodiments, the information relating to a given second access point identifying a type of traffic supported by that given second access point, wherein determining whether one of the one or more second access points should be activated is a function of the type of traffic supported. According to one or more exemplary embodiments, the information relating to a given second access point comprising at least one descriptive statistic of a past operation of that given second access point, wherein determining whether one of the one or more second access points should be activated is a function of the at least one statistic.
[0047] According to one or more exemplary embodiments, the method comprises, prior to obtaining information relating to one or more second access points, pre-associating with the first access point, transmitting a request for information relating to one or more second access points to the first access point and obtaining this information in response to the request.
[0048] According to one or more exemplary embodiments, obtaining information relating to one or more second access points comprises receiving a beacon from the first access point, the information relating to one or more second access points being contained in the beacon.
[0049] A fourth aspect relates to a client device comprising a communication interface adapted to communicate with an access point in a wireless network; and means for performing the steps of one of the above methods.
[0050] One or more embodiments relate to a computer program product comprising instructions which, when the program is executed by a processor of a device, cause one of the above devices to implement one of the associated methods described.
[0051] One or more embodiments relate to a recording medium readable by a device having a processor, said medium comprising instructions which, when the program is executed by a processor of a device, cause one of the above devices to implement one of the associated methods described.
[0052] Brief description of the figures
[0053] Other characteristics and advantages will appear during the reading of the detailed description which follows for the understanding of which reference will be made to the appended drawings among which: - figure 1 is a functional block diagram of a device according to a particular non-limiting embodiment;
[0054] - figure 2 is a functional block diagram of a radio according to a particular non-limiting embodiment;
[0055] - Figure 3 is a diagram illustrating an example of neighborhood information messages transmitted by activated access points hosted by a device according to a particular non-limiting embodiment;
[0056] - Figure 4 is a message sequence diagram illustrating the passive discovery of one or more neighboring access points;
[0057] - Figure 5 is a message sequence diagram illustrating the active discovery of one or more neighboring access points;
[0058] - figure 6 is a functional block diagram of a client device according to an exemplary embodiment;
[0059] - Figure 7 is a message sequence diagram illustrating the activation of an access point after acceptance of a client device's request by the host device;
[0060] - Figure 8 is a message sequence diagram illustrating a method of activating an access point by a client device in the context of an 'MLO' group according to an exemplary embodiment;
[0061] - Figure 9 is a message sequence diagram illustrating a request to release an access point according to an exemplary embodiment;
[0062] - Figure 10 is a message sequence diagram illustrating a case of a request to activate an access point refused by the radio hosting device for a first reason;
[0063] - figure 11 a message sequence diagram illustrating a case of a request to activate an access point refused by the radio hosting device for a second reason, according to an exemplary embodiment;
[0064] - Figure 12 is a message sequence diagram illustrating a case of a request to activate an access point, but where the radio hosting the access point whose activation is requested cannot be started, according to an exemplary embodiment;
[0065] - Figure 13 is a message sequence diagram illustrating the deactivation of an access point by a host device 200 according to one embodiment;
[0066] - Figure 14 is a message sequence diagram illustrating the deactivation of an access point by a hosting device according to a particular exemplary embodiment;
[0067] - Figure 15 is a message sequence diagram illustrating, according to a particular exemplary embodiment, the case of an activation request accepted, but where the activation of the radio hosting the access point to be activated cannot be carried out.
[0068] Detailed description
[0069] In the following description, identical, similar, or analogous elements will be designated by the same reference numerals. Unless otherwise indicated, the diagrams are not necessarily to scale. The block diagrams, flowcharts, and message sequence diagrams in the figures illustrate the architecture, functionality, and operation of systems, devices, methods, and computer program products according to one or more exemplary embodiments. Each block of a block diagram or each phase of a flowchart may represent a module or a portion of software code comprising instructions for implementing one or more functions. In some implementations, the order of the blocks or phases may be changed, or the corresponding functions may be implemented in parallel.The process blocks or phases may be implemented using circuitry, software, or a combination of circuitry and software, in a centralized manner or in a distributed manner for all or some of the blocks or phases. The systems, devices, processes, and methods described may be modified, added to, and / or deleted within the scope of this disclosure. For example, the components of a device or system may be integrated or separated. Also, the described functions may be implemented using more or fewer components or phases, or with other components or through other phases. Any suitable data processing system may be used for the implementation. For example, a suitable data processing system or device includes a combination of software code and circuitry, such as a processor, controller, or other circuitry suitable for executing the software code.When the software code is executed, the processor or controller causes the system or device to implement all or part of the functionalities of the blocks and / or phases of the processes or methods according to the exemplary embodiments. The software code may be stored in a memory or a readable medium accessible directly or through another module by the processor or controller.
[0070] The examples of implementation are placed, in a non-limiting manner, in the context of networks conforming to the 802.11 family of standards of the Institute of Electrical and Electronics Engineers (IEEE), or so-called 'Wi-Fi' type networks.
[0071] A glossary including the main acronyms used in conjunction with this context is available at the end of the description.
[0072] Figure 1 is a functional block diagram of a radio 100 according to an exemplary embodiment provided for illustrative purposes, while Figure 2 is a block diagram of a host device 200 comprising several radios.
[0073] The radio 100 of Figure 2 is an example implementation of one of the radios of Figure 1. The radio 100 is controlled via the microcontroller or processor 101 of the host device 200. The radio includes a processor 102 and a digital signal processing processor 103 commonly referred to as a 'DSP'. The latter includes a digital-to-analog converter on the transmission path and an analog-to-digital converter on the reception path. The radio's processor 102 is surrounded by a dotted line to indicate that it may be optional as a separate component depending on the implementation - indeed, according to certain embodiments, its functionalities may be integrated with other components, such as the processor 101. The analog signals in transmission, respectively in reception, are modulated, respectively demodulated, by a radio frequency modem 104 comprising a mixer 105.A front-end module 106 amplifies the signal in transmission (power amplifier 107), while the signal in reception is amplified by a low-noise converter block 108. A filter 109 switchable between the transmission path and the reception path is inserted between the output of the power amplifier 107 and the antenna 110 on the one hand and the input of the low-noise converter block 108 and the antenna 110 on the other hand. According to the present example, the filter 109 and the antenna 110 are passive components, while the other components are active components. It should be noted that in other implementations, the filter 109 and / or the antenna 110 may also be non-passive components.
[0074] Figure 1 illustrates the case of a radio with a single transmission / reception chain, however a radio can have several transmission / reception chains. Some components can be common to several chains, for example the processor 102 or the digital signal processing processor 103.
[0075] In some embodiments, disabling a radio involves disabling the non-passive components of the radio, i.e., their power is turned off. In the illustrative example of Figure 1, the non-passive components include at least the signal processing processor 103, the modem 104, the front-end module 105 and, if present and separately deactivatable, the own processor 102. If multiple receive / transmit chains are present, the non-passive components are disabled for all chains. The non-passive components may be different in other implementations.
[0076] According to other exemplary embodiments, only a subset of these components is deactivated. For example, since the power amplifier 107 is a high-consumption component, it is deactivated as a priority. However, the processor 102, the digital signal processing processor 103 and the modem 104 are kept activated, i.e. powered, to allow a rapid restart of the radio. If the low-noise converter block 108 is kept activated and the element 109 switchable to the reception path, then the radio is still equipped with reception capabilities in order to detect, for example, information request frames.
[0077] The device 200 further comprises the aforementioned processor 101, a long-term memory 205 and a working memory 206. The processor 101 controls the functionalities of the device 200 and manages the various radios. The memory 205 comprises software code which, when executed by the processor, leads to the implementation by the device of one or more of the methods described. The memory 206 is used in particular to store data relating to the management of the radios, as well as data relating to the terminals associated or likely to be associated with one of the access points. The respective channels on which the three radios operate are the channels designated by 'a', 'b' and 'c'.According to one or more embodiments, a host device 200 may be a gateway, a router, a radio coverage repeater ('repeater' in English) or a radio coverage extension device ('extender' in English) in a mesh-type wireless network.
[0078] According to one or more embodiments, the device 200 includes at least two radios. Each radio can be independently enabled or disabled. When the host device is in normal operating condition, at least one radio is enabled to provide connectivity.
[0079] A radio hosts at least one access point ('access points' or 'APs') which allows access to the network to client devices ('stations' or 'STAs') which would come to connect.
[0080] A network is typically identified by a name. In the case of a Wi-Fi network, the name is the SSID presented to the user. The AP broadcasting this SSID has a unique BSSID that has the same format as a MAC address (6 bytes).
[0081] The capabilities of a device are determined by the standard with which the entities operating in the wireless network are compatible. In one example, a client device, an entity operating in the wireless network, implements features according to the IEEE 802.11 standard described by amendments 11 b / 11 g / 11 n / 11 ax / 11 be for the 2.4 GHz band, implements features according to the IEEE 802.11 standard described by amendments 11 a / 11 n / 11 ac / 11 ax / 11 be for the 5 GHz band, and implements features according to the IEEE 802.11 standard described by amendments 11 ax / 11 be in the 6 GHz band, also referred to as Wi-Fi 6E / 7. In this example, amendment 11 ax determines the capabilities of the client device and the access point. In another example, an access point has functionality that allows it to operate in accordance with amendments to the IEEE 802.11 standard and in several bands among the 2.4GHz, 5GHz, and 6GHz bands.The capabilities of this access point are determined by these amendments and correspond to the functionalities of said access point. By misuse of language, we can speak of IEEE 802.11 ax standard or IEEE 802.11 ax technology instead of 11 ax amendment for example. Encryption protocols, for example WPA2 or WPA3, can also be implemented in exchanges between network entities.
[0082] In an IEEE 802.11 network, access points hosted by different radios can be grouped together. For example, according to the IEEE 802.11 amendment, also referred to as 'Wi-Fi 7', in this 'MLO' (multi-link operation) mode of operation, all grouped access points have a common identifier. In Wi-Fi 7, this common identifier is the MLD MAC address. All grouped Wi-Fi 7 access points have the same network name (SSID).
[0083] According to one or more exemplary embodiments, all the access points hosted by a radio operate on the same channel, which will be referred to as the radio channel. This channel belongs to a band (e.g., 2.4 GHz, 5 GHz, 6 GHz) which is divided into several channels on which the radio can operate. In an IEEE 802.11 type network, these channels are generally 20 MHz wide and can be aggregated in order to increase the transmission capacity of the so-called operational channel (40
[0084] MHz, 80 MHz, 160 MHz or even 320 MHz depending on the spectrum width available in the band).
[0085] When a radio is activated, an access point it hosts can be activated. An activated access point signals its presence. In an IEEE 802.11 network, an access point signals its presence by periodically transmitting beacons or on demand by sending a probe response frame if a probe request frame has been received. In this state, the radio components required for transmission and reception are powered.
[0086] When a radio is disabled, all access points it hosts are disabled.
[0087] In one embodiment, a radio may be enabled, but an access point hosted by that radio does not signal its presence. To the outside world, that access point is seen as disabled.
[0088] Returning to Figure 2, the hosting device 200 comprises three radios 201, 202 and 203. In the example of Figure 2: an activated radio (Radio 201), hosting: o an activated AP (AP1.1) broadcasting a network “Dom.1” (‘Dorrï for ‘Home’) forming part of the MLO group identified by “MLD.1” o an activated AP (AP1.2) broadcasting a network “Dom.2” a deactivated radio (Radio 202), hosting: o a deactivated AP (AP2.1) which, if activated, would broadcast a network “Dom.1” forming part of the MLO group identified by “MLD.1” a deactivated radio (Radio 203), hosting: o a deactivated AP (AP3.1) which, if activated, would broadcast a network “Dom.1” forming part of the MLO group identified by “MLD.1” o an activated AP (AP3.2) broadcasting a network “Dom.2” (AP3.2) disabled which, if enabled, would broadcast a “Dom.2” network
[0089] An activated access point may signal the presence of other activated neighboring access points. Such information may concern access points of the same radio or of a different radio than the signaling access point, or access points of a different device than the one hosting the radio of the signaling access point. In IEEE 802.11 networks, for example, the dissemination of this neighbor information may be done via a data structure called an "information element" ('IE'). This information element may be included in messages transmitted by an activated access point.Examples of such messages are: beacons emitted periodically and which include a compressed or reduced neighborhood information report or 'RNR' (for "Reduced Neighbor Report" in English); responses to solicitations ("Probe Response" in English) or to requests for neighborhood information reports ("Neighbor Report Response" in English) emitted respectively upon receipt of the solicitations ("Probe Request" in English) or requests for particular neighborhood information reports ("Neighbor Report Request" in English).
[0090] The RNR of an access point reported by another access point generally includes: the identity ('BSSID') of said reported access point, the network name ('SSID') (or its abbreviated version ('Short SSID')) of said reported access point, the frequency band and the width of the operational channels on which said reported access point operates, this information being provided via a data called operating class ('Operating Class' in English); and the (primary) channel in which said access point reports its presence.
[0091] Optionally, the RNR can include the MLO group to which the reported access point belongs if applicable.
[0092] According to one or more embodiments, it is proposed to systematically indicate the state of a neighboring access point in the neighborhood information describing it. More specifically, the data describing a neighboring access point will include information indicating whether said neighboring access point is activated or deactivated.
[0093] According to an optional embodiment, the neighbor information indicates whether the radio hosting a neighboring access point is enabled or disabled.
[0094] If a radio is disabled, then all access points hosted by that radio are disabled. However, it is possible for a radio to be enabled, without all access points hosted by that radio being enabled. A radio can be enabled without any hosted access points being enabled. The power consumption of such a radio is then reduced, but not zero.
[0095] The status information can, for example, take the following three values:
[0096] Access point status = ACTIVE or DISABLED_BUT_RADIO_HOSTING_ACTIVE or RADIO_HOSTING_DISABLED
[0097] (In English: “BSS Status = UP or DOWN_BUT_HOSTING_RADIO_UP or HOSTING_RADIO_DOWN”)
[0098] Depending on the needs of a particular application, this information can be encoded on one bit or more depending on the desired level of detail. For example, if the information relating to the hosting radio does not have to be transmitted, a single bit will be enough to characterize the state of the access point (ACTIVE or DISABLED).
[0099] State information can also represent only states other than the enabled state. If this information is not present, then the enabled state will be considered by default.
[0100] The time associated with switching a radio from a disabled state to an enabled state is generally greater than the time taken to switch an access point from a disabled state to an enabled state if the radio hosting it is enabled. A client device having knowledge of the activation state of both an access point and the radio hosting said access point (for example, an access point disabled but radio enabled) can usefully use this information in a mechanism for selecting an access point to activate based on its needs and their criticality over time.
[0101] Without this being limiting, we subsequently consider only the broadcast of the activated or deactivated state for a neighboring access point respectively activated or deactivated.
[0102] According to one or more embodiments, the neighbor information indicates, when a neighbor access point that is the subject of a neighbor report is currently disabled, the minimum time required to activate it.
[0103] According to one or more embodiments, the neighbor information indicates, when a neighbor access point that is the subject of a neighbor report is currently disabled, the last channel on which that access point was enabled.
[0104] In IEEE 802.11 networks, for example, this indication can be coded by identifying the class of operation and a channel number. The class can be coded on one byte and the (primary) channel also on one byte. The list of classes of operation is given, for IEEE 802.1 1 in Annex E of document IEEE802.11-2020 and its successor amendments (eg IEEE802.11 ax-2021).
[0105] According to an optional embodiment, the information about a neighboring access point includes a list of all channels supported by that access point, in addition to its status. According to another embodiment, this list is included when the status of the neighboring access point is disabled.
[0106] In IEEE 802.11 type networks for example, the above list information may include all the operation classes supported by the radio hosting the neighboring access point mentioned in the neighbor information. For information purposes, this information is encoded by a message including the number of operation classes supported (for example on one byte) and the identifiers of the operation classes concerned (for example one byte per operation class).
[0107] According to one or more embodiments, the neighbor information includes wake-up conditions of a neighboring access point.
[0108] In some implementations, these wake-up conditions are related to the traffic type (defined by the quality of service), for example with the support of a certain type of traffic mainly allowed at the moment on this radio (voice, video, ...).
[0109] In IEEE 802.11 type networks for example, the information relating to the type of traffic associated with the wake-up conditions may include one or more of: one or more authorized traffic identifiers 'TID' (for "Traffic IDentifier" in English); one or more already negotiated flow identifiers (for example a flow classification service such as 'SCS' (for "Stream Classification Service" in English, or a reciprocal flow classification service such as 'MSCS' (for "Mirrored SCS" in English); one or more flow descriptions not yet negotiated (for example a flow descriptor describing the quality of service associated with a flow, such as 'TSPEC' (for "Traffic SPECification" in English) describing traffic types, or 'TCLAS' (for "Traffic CLASsification" in English), describing particular flows.These elements make it possible to characterize more or less precisely the type of traffic authorized to wake up an access point currently deactivated.
[0110] According to an optional embodiment, the neighbor information comprises information representative of past statistics of the neighboring access point for one or more past periods during which this access point was activated. These statistics may include one or more of: information on average latency, average throughput, average channel occupancy rate, average jitter, average consumption at the radio level of this particular neighboring access point, etc. For example, this information is averaged over a fixed duration, for example 10 minutes.
[0111] This information can, for example, be encoded by a message indicating the type of statistic, the length of bytes encoding the statistic and the value of this statistic. This is the use of a classic "Type Length Value" 'TLV' format.
[0112] Table 1 shows the contents of a frame relating to the type of neighbor information for a neighboring access point described in this neighbor information, augmented by the new fields described above. This table is given as a non-limiting example. A neighbor information may include only one of the fields described, or any combination of several of these fields. Fields 1 to 4 of this table are described in the IEEE 802.1 1 standard.
[0113] Table 1
[0114] Figure 3 is a message sequence diagram showing an example of the messages transmitted by active access points of a radio hosting device, in the context of the illustrative example of the radios of the device of Figure 1. The example is in the context of the hosting device 200 of Figure 2. The signaling of the states may result in the activated access points AP1.1 and AP1.2 transmitting information about their neighbors. Access point AP1.1 broadcasts information about all neighbors associated with the Dom.1 and Dom.2 networks (message S301), while access point AP1.2 only broadcasts information about the neighbor associated with the same Dom.2 network as itself, namely access point AP3.2 (message S302).
[0115] A client device associating with one of the two enabled access points then knows that one or more other access points are available for the network to which it has associated, as well as their activation status.
[0116] As mentioned earlier, the device can obtain neighborhood information either passively if the information is broadcast periodically or actively by querying the activated access point directly. Figure 3 shows both possibilities, with messages being sent as a beacon or as a response to an information request.
[0117] Figure 4 is a message sequence diagram illustrating the passive or active discovery of one or more neighboring access points before association of a client device when the activated access point publicly broadcasts neighborhood information. This figure shows the example of a device of the 'Dom. 2' network supporting radio 1 and radio 3 400, also designated as client device 400 receiving and decoding the beacons (message S402, the content of which is similar to that of S302) transmitted by the access point AP1.2 including neighborhood information. Alternatively, the client device 400 can receive a response to an information request ("probe response") including neighborhood information. The client device 400 thus learns that another access point AP3.2 is available but switched off.
[0118] Figure 5 is a message sequence diagram illustrating the active discovery of one or more neighboring access points after association of a client device when the activated access point only broadcasts neighborhood information upon request from authorized client devices. The device of the 'Dom. 2' network supporting radio 1 and radio 3 500, also designated client 500, associates on the Dom.2 network of the access point AP1.2, which is activated on radio 1. The access point AP1.2 broadcasts a beacon S501 (or a response to an information request S501 whose information content is essentially similar to that of the beacon S501), but does not broadcast information on neighboring access points. This is for example the case when it is useful to reduce the size of the beacons. In Figure 5, the messages explicitly linked to the association are voluntarily grouped into an exchange S502 because they are known per se.At the end of this exchange, the client 500 is authorized to use the network. The term "associated" and the term "authorized" will be used equivalently in the following. The client then actively requests the list of neighboring access points from the access point AP1.2 (Neighborhood information request - message S503) which it receives (Response to neighbor information request S504). The client 500 thus learns that another access point AP3.2 is available but deactivated. The advantage of this approach compared to a discovery such as described in Figure 4 is that the discovery of the equipment's capabilities is only known by authorized clients (i.e., having successfully completed the association procedure).
[0119] According to one or more embodiments, a client device associated with an access point of a first radio may want to associate with an access point of a second radio. One possible reason is, for example, that the frequency band of the second radio is more suited to the needs or constraints of the client device than the frequency band of the first radio. In the examples of Figures 4 and 5, a client device supporting the channels of radio 1 and the channels of radio 3 may be interested in radio 3 rather than radio 1 for its traffic - for example, radio 1 operates at 2.4 GHz, while radio 3 operates at 6 GHz.
[0120] According to one or more embodiments, a client device must be associated with an activated access point in order to request activation of a deactivated access point. Thus, once associated with an access point, the client device can send on this link a request for activation of the other access point(s) currently deactivated and which are adapted to operate on bands and channels supported by said client device. The requirement of prior association with an activated access point in order to request activation of a deactivated access point makes it possible to avoid activation requests by unauthorized client devices on the network.
[0121] Depending on the various optional elements additionally present in the neighborhood information, a client device can decide in a more informed manner whether or not to request the activation of another access point and then associate with it.
[0122] In a first example, the client device checks the qualities of service allowed by a given disabled access point considered for activation. If these qualities of service do not allow to cover the current or future traffic of the client device, the client device will not request the activation of the given access point.
[0123] According to a second example, if the past statistics of a given disabled access point considered for activation do not appear to be suitable for the current or future traffic type of the client device, the client device will not request activation of the given access point. According to a particular embodiment, a request to activate a disabled access point includes an identifier of this access point. For an IEEE 802.11 type network, this identifier is for example the BSSID.
[0124] According to an alternative embodiment, an activation request comprises information indicating one or more reasons for requesting this activation.
[0125] Examples of activation reasons are:
[0126] (a) A type of traffic to be supported: type of quality of service, a model or a template ('pattern' in English), required latency, required throughput (for example one or more of a TID, TSPEC, TCLAS for an IEEE 802.11 type network), required duration.
[0127] (b) A quality for a current traffic type on the currently enabled access point that is not satisfactory and a negotiated traffic identifier if existing (e.g., one or more of a TID, TSPEC, TCLAS, or SCSID (if negotiated) for an IEEE 802.11 network).
[0128] (c) An interference level above a threshold. The interference level is measured by the client device on the current access point channel (i.e. with which it is currently associated), it corresponds to a disturbing signal level. The interference level can be external (external interference can for example be due to neighboring networks) or internal (internal interference can be due to other internal radios of the client device).
[0129] Table 2 presents a non-limiting example of the content of an activation request frame. Elements 3 and 4 are optional. For example, the 'Reason' field (Table 2, field 3) can be encoded on one byte. Depending on the value of this 'Reason' field, an additional field (Table 2, field 4) can be added to specify the reason. For example, for an IEEE 802.11 type network, in the case of an activation request by declaration of voice type traffic to be supported, the additional field can indicate the TID associated with the voice and optionally the associated parameters (TCLAS).
[0130] Table 2 The host device 200 receiving the request to activate a currently disabled access point via an enabled access point will analyze this request.
[0131] The host device 200 will then respond via an activated access point to the client device that made the activation request either by rejecting the activation request or by accepting the activation request and then implementing the means to activate the currently deactivated access point. This may, if applicable, include activating the radio hosting the deactivated access point if the latter was switched off.
[0132] According to an alternative embodiment, in the event of acceptance of the activation request for a currently deactivated access point, the activated access point responding to the client device having made said activation request may add a time delay T1 to its positive response. The time delay T1 associated with an access point to be activated indicates to the client device having made the activation request for this access point the minimum duration that this client device must wait before checking whether the access point is activated. As long as the time delay T1 associated with an access point to be activated has not ended, the client device must not send an activation request for this same access point.
[0133] For example, the value of this time delay T1 can range from a few microseconds if the radio hosting the access point to be activated is activated but the access point itself is deactivated, to a few seconds, or even minutes, if the radio must be activated from a deactivated state (this can for example include repowering the hardware part, loading software drivers, etc.) and / or if scans are necessary before operation (scanning of so-called 'DFS' channels at 5 GHz for example).
[0134] Verification by the client device of the activation of the access point that the client device requested to be activated can be performed passively if this information is periodically broadcast by the currently activated AP. Verification can also be performed actively by re-polling the initial activated access point to retrieve its updated neighbor information. This allows the client to identify the channel where the newly activated access point will be located, which may have changed from the one selected before its last deactivation.
[0135] According to an alternative embodiment, in the event of acceptance of the activation request of a currently deactivated access point, the activated access point responding to the client device having made said activation request may add a duration D1 to its positive response. The duration D1 associated with an access point to be activated indicates to the client having made the activation request for this access point the minimum guaranteed activation duration of said access point. Beyond this duration, the hosting device reserves the right to deactivate the access point having been activated. The value of this duration D1 depends on the needs of a particular implementation: it may be a few minutes, or even tens of minutes, in particular if the radio was originally completely deactivated. For example, if thirty seconds are necessary to completely reactivate a radio and the access points it hosts, it would not be reasonable for D1 to be of the order of a few seconds.This mechanism allows the hosting device to control its consumption. Temporary activations of certain access points can thus be tolerated, but not necessarily continuous activations.
[0136] According to a particular embodiment, in the event of rejection of the activation request for a currently deactivated access point, the activated access point responding to the client device having made said activation request may optionally add a time delay T2 to its negative response. The time delay T2 associated with an access point to be activated indicates to the client device having made the activation request for this access point the minimum duration to wait before repeating this request for this access point.
[0137] For example, the value of this timeout can be a few minutes or even a few hours. If longer times are required, it may be worth not including the currently disabled access point in the neighborhood information at all.
[0138] According to a particular embodiment, in the event of rejection of the activation request of a currently deactivated access point, the activated access point responding to the client device having made said activation request may add to its negative response a reason for this rejection. Depending on the nature of the reason and the processing thereof by the client device, repeated requests by the client device may be limited or completely avoided.
[0139] The reason provided depends on the configuration of the hosting device. Examples of possible reasons include, but are not limited to:
[0140] • The host device is not in an acceptable time slot for activation (e.g., the host device is configured in power saving mode, for example by the user, and the current time slot is not off-peak).
[0141] • Activation of the requested access point would result in consumption exceeding a threshold defined in the host device when it is configured in power saving mode. According to an alternative embodiment, the identity of another currently deactivated access point of a less energy-consuming radio can be transmitted by the host device to the client device.
[0142] • The requested traffic can be carried by the current access point or another access point in the same network that is currently activated. This assumes that the traffic information is present in the activation request sent by the client device. The identity of another suitable currently activated AP can be provided indicatively or preferentially by the hosting device to the client device.
[0143] • The requested traffic would result in consumption exceeding a threshold defined in the host device when it is configured in power saving mode (e.g. by the user) due to the activation of the associated radio. This assumes that the traffic information is present in the activation request sent by the client device.
[0144] Table 3 shows an example of an activation response frame.
[0145] Table 3
[0146] The Reason field (table 3, field ...) is for example coded on one byte. Depending on the value of this reason, an additional field can be added to specify the reason, as seen previously in connection with table 2. Fields 4 to 7 are optional.
[0147] According to a particular embodiment, a single activation request transmitted by a client device may relate to several access points. The host device will then respond for each of the access points, for example by concatenating the responses.
[0148] According to a particular embodiment, the host device continuously checks the status of the access points that it has activated on request. If no client device is associated with such an access point, then the host device decides to deactivate this access point. It is possible for the host device to implement a timer T3, which is triggered when the last client device disconnects. When this timer expires, the host device deactivates the access point concerned. T3 is, for example, a few seconds. Timer T3 is reset as soon as a client device associates with the access point.
[0149] According to one embodiment, when a condition required for the activation of an access point activated following a request is no longer met, the hosting device deactivates the access point(s) concerned.
[0150] Non-limiting examples are:
[0151] (a) One or more client devices are associated with an on-demand enabled access point, but there is no traffic or the current traffic can be operated under the same quality of service conditions on another enabled access point.
[0152] (b) The current consumption of the hosting device is greater than a given threshold.
[0153] (c) We enter a so-called full range and an energy saving mode is engaged.
[0154] In such a case of deactivation, the hosting device will signal the termination of the access point concerned by indicating a time delay T4, after which the deactivation will be effective. The time T4 will generally be chosen to be short, the shutdown of the access point being imminent once decided by the hosting device.
[0155] According to a particular embodiment, a client device having made a request to activate an access point may at any time make a request to release this access point. An example concerns the situation in which a client device considers that it no longer needs this access point or that the radio conditions have become less attractive on this access point. For example, the client device has moved away from an access point operating on the 6 GHz band. A reason for the release may optionally be indicated.
[0156] Table 4 shows an example of an activation release frame according to a particular exemplary embodiment.
[0157] Table 4
[0158] Field #3 is optional.
[0159] Figure 6 is a functional block diagram of a client device according to an exemplary embodiment. The client device 600 of Figure 6 is an example of a client device that can be used for the implementation according to one of the described embodiments. The client device 600 comprises a processor 601, a memory 602, a user interface 603, a communication interface 604 configured to communicate for example with the host device 200, a display 606 adapted for displaying data to a user, as well as a working memory 607.
[0160] The various components of the client device 600 are connected through a communication bus 604. The memory 602 comprises software code 605. The memory 607 is used to store and manage the data to be transmitted. When the processor executes the software code 605, it causes the client device 600 to implement a method according to one or more exemplary embodiments described. The client device 600 may be a computer, a mobile phone or any other device capable of acting as a station, terminal or user equipment suitable for interacting with the host device 200.
[0161] Figures 7 to 18 are message sequence diagrams illustrating the implementation of the data present in the neighborhood information according to one or more exemplary embodiments, both from the point of view of the host device and that of one or more client devices. These examples are given for illustrative purposes and placed in the context described in connection with Figure 2. The data described above can of course be used in other contexts as well.
[0162] Figure 7 is a message sequence diagram illustrating a method of activating an access point after acceptance of a client device's request by the hosting device. The client device 700 supports radios 1 and 3 (i.e., it can operate on the respective frequency bands). The client device receives a beacon (S701) from the activated access point AP1.2 of radio 1. This beacon indicates in the neighbor information that an access point AP3.2 exists in radio 3, but that this access point is deactivated. The client device associates on the Dom.2 network of the access point AP1.2 (S702). The client device makes a request to activate the access point AP3.2 (S703) by indicating the desired characteristics of the traffic to be carried out with the access point AP3.2.The request is analyzed by the host device 200 (S704), which in the case of Figure 7 responds positively (S705), indicating a time delay T1 to wait before the client device checks whether the access point AP3.1 is operational. The host device 200 then initiates the activation of radio 3, which was deactivated (S706), following which the state of this radio 3 changes from deactivated to activated. The radio selects a new channel, channel 'd', different from the channel 'c' initially indicated in the beacon S701. The client device waits for T1 before checking the activation status of the access point AP1.3. After T1 it analyzes the content of the beacon (S707) of the activated access point AP1.2 comprising neighbor information indicating that the access point AP3.2 is now activated, and operating on channel 'd'. The host device monitors radio 2 (S708), for example to see if the client device associates or not.In S709, the client device 700 performs an association with the access point AP3.1.
[0163] Figure 8 is a message sequence diagram illustrating a method for activating an access point by a client device 800 in the context of an 'MLO' group, according to an exemplary embodiment. It is recalled that all the networks of an MLO group have the same standard network identifier (SSID). In this context, the association on the various access points of the same MLO group can be done on a single access point. The links between each access point of an MLO group and each station of a client device are called "links". The access point activation requests in an MLO context then relate to links but the principle remains the same as for activation requests previously described.
[0164] Returning to the case of Figure 8, in S801, the client device receives a beacon from the access point AP1.1. The information transmitted in this beacon indicates in particular that the access point AP1.1. is part of an MLO group designated by MLD.1, a group which also contains the access points AP2.1 and AP3.1, both deactivated. A 'group' association procedure S802 is then initiated by the client device 800 with the access point AP1.1 by including the links associated with the activated access point AP1.1 and the deactivated access point AP1.3 supported by the client device.
[0165] According to an alternative embodiment, this 'group' association procedure S802 only contains the link associated with the activated access point AP1.1.
[0166] Once this association is effective, the client device 800 transmits a link activation request to the access point AP1.1 for the link associated with the access point AP3.1 (S803). This request (S804) is analyzed by the host device 200, which in the case of FIG. 8 responds favorably (S805) and activates the radio 3, hosting the access point AP3.1; then subsequently the access point AP3.1. The client device waits for a time delay T1 before checking the activation of the link associated with the access point AP1.3. A beacon S807 informs the client device 800 that the link associated with the AP1.3 is then active. A security parameter reset S808 is then initiated.
[0167] According to an alternative embodiment associated with a 'group' association which would include all the links supported by the client device, even those deactivated, this resetting of the security parameters would only concern the point-to-multipoint ('multicast' in English) encryption key for the newly activated link, the point-to-point ('unicast' in English) key being the same for all the access points of the same MLO group.
[0168] According to a more general embodiment, this resetting of the security parameters is done via a 'group' reassociation frame including the links associated with AP1.1 and AP1.3 supported by the client device.
[0169] Figure 9 is a message sequence diagram illustrating a release request S901 of an access point, for which an activation request has been made previously. The request is acknowledged (at S902) and the monitoring method S903 of the access point carried out by the hosting device will deactivate this access point if the necessary conditions for this are met, as explained previously.
[0170] Figure 10 is a message sequence diagram illustrating the case of a request for activation of an access point by a client device 1000 refused by the radio hosting device 200, in this case because the activation is requested outside of off-peak hours while a power saving mode of the hosting device is engaged. Steps S1001 to S1004 are similar respectively to steps S701 to S704 of Figure 7. In S1005, the hosting device 200 however refuses the request for activation of the access point, indicates the reason (outside of off-peak period) and gives a time delay T2 before a new request for activation of the same access point can be made. A beacon S1006 emitted by the hosting device confirms that the access point is still deactivated. After T2 has elapsed, the client device 1000 makes a new request S1007 to activate the access point AP3.2.
[0171] Figure 11 is a message sequence diagram illustrating the case of a request to activate an access point by a client device 1100 being refused by the radio hosting device 200, in this case because an already active access point can support the traffic described in the activation request. Steps S1101 to S1104 are similar to steps S701 to S704 of Figure 7, respectively, with the client device seeking to activate the access point AP3.2. In S1 105, the host device 200 however refuses the request to activate the access point, indicates the reason (the traffic described can be supported by a currently activated access point, namely the access point AP1.1, this information being optionally passed in the response to the activation request) and gives a time delay T2 before a new request to activate the same access point can be made by the client device 200.A beacon S1106 emitted by the host device confirms that the access point is still deactivated. After T2 has elapsed, the client device 1100 makes a new request S1 107 to activate the access point AP3.2.
[0172] Figure 12 is a message sequence diagram illustrating the case, according to a particular exemplary embodiment, of a request for activation of an access point by a client device 1200, request accepted by a host device 200, but where the radio hosting the access point whose activation is requested cannot be started. Such a case can occur for example following a hardware fault or a software problem. Steps S1201 to S1204 are similar respectively to steps S701 to S704 of Figure 7, the client device seeking to activate the access point AP3.2. In S1205, the host device 200 accepts the activation request and initiates the activation of radio 3 (S1206). However, this radio cannot be activated (S1207).
[0173] According to one embodiment, the host device indicates in the broadcast neighborhood information a malfunction state of the access point whose radio cannot be activated, as illustrated by S1208. This makes it possible to avoid subsequent activation requests. According to another non-exclusive embodiment of the previous one, in the case where a radio cannot be activated, the host device indicates in the broadcast neighborhood information a malfunction state of all the access points of this radio.
[0174] According to an alternative embodiment illustrated by S1209, the hosting device removes, from the broadcast neighborhood information, information concerning the access point whose radio cannot be activated.
[0175] Figure 13 is a message sequence diagram illustrating the deactivation of an access point by a host device 200 according to a particular embodiment. The host device 200 monitors the radios (S1301). The host device decides at some point that the conditions for activating the access point (AP3.2 in the example) are no longer met. An information message (S1302) is broadcast on the network, optionally indicating a reason for the deactivation and optionally the timeout T4 mentioned above. This message can be received by the client device 1300. As a reminder, the timeout T4 indicates the minimum time during which the access point will still remain activated before being deactivated. A beacon S1303 transmitted during the timeout will show the access point still activated. The access point is then deactivated. A beacon S1304 transmitted after the timeout will show the access point deactivated.In the example in Figure 13, Radio 3 is also disabled. In the example in Figure 2, it can also disable Radio 3 because AP3.2 was the only active AP for Radio 3.
[0176] Figure 14 is a message sequence diagram illustrating the deactivation of an access point by a host device 200 according to a particular exemplary embodiment. In this example, the host device 200 performs monitoring of radio 3. The host device transmits a message (S1402) to a client device 1400 associated with an access point (AP 3.2 in the example). This message requests the client device 1400 (and possibly other associated client devices) to disassociate from the access point. The reason is optionally provided, in this case being the termination of the access point. A timer T4 is also optionally provided. Once the disassociation procedure is completed for the last client device (at S1404), the host device 200 deactivates the access point. A beacon S1404 transmitted (for example by the access point AP1.2, always active) during the timeout will show the access point still active. The access point is then deactivated. An S1405 beacon emitted after the timeout will show the access point deactivated. In the example in Figure 13, radio 3 is also deactivated. In the example in Figure 2, it may also deactivate radio 3 because AP3.2 was the only active access point in radio 3. In an IEEE 802.11 network, the 1402 message may be an access point transition management message, or a so-called 'BTM Request' (BSS Transition Management Request).
[0177] Figure 15 is a message sequence diagram illustrating, according to a particular exemplary embodiment, the case of deactivation of an access point activated on demand after disassociation of the last client device. In S1501, the client device 1500 performs a disassociation with the access point AP3.1. It is assumed for the purposes of the example that the client device 1500 is the last client device present on the access point AP3.1. The host device monitors the state of radio 3 and notes that no client device is anymore associated. The host device then waits for a time delay T3 before initiating the deactivation of the access point. A beacon S1503 that would be broadcast (for example by the access point AP1.2) during the time delay T3 would indicate in its neighborhood information the access point still activated. After the time delay T3, the access point is deactivated.A later broadcast S1504 beacon would indicate the disabled access point. The principles discussed above may apply to, among others:.
[0178] - a host device comprising a single radio which itself comprises several access points, this host device being able to optionally extend its neighborhood information also to access points of one or more other host devices;
[0179] - a host device comprising a single radio which itself comprises a single access point, but which covers in its neighborhood information one or more access points of other host devices which may comprise one or more radios.
[0180] One or more embodiments therefore relate to a method implemented by a communication device comprising a single radio hosting at least one access point to a wireless network associated with the access point, an access point having one of at least an enabled state and a disabled state, comprising transmitting, by a first enabled access point of the communication device, information relating to a second access point even when this second access point is in the disabled state.
[0181] Additionally, one or more embodiments relate to a method implemented by a communication device comprising a single radio hosting a threshold access point to a wireless network associated with the access point, the access point having one of at least an enabled state and a disabled state, comprising transmitting, by a first enabled access point of the communication device, information relating to at least one second access point even when that second access point is in the disabled state, the at least second access point being hosted by a radio of another hosting device.
[0182] REFERENCE SIGNS
[0183] 100 - Radio
[0184] 101 - Device Processor
[0185] 102 - Radio processor
[0186] 103 - Digital signal processing processor
[0187] 104 - RF modulator-demodulator
[0188] 105 - Mixer
[0189] 106 - Front module
[0190] 107 - Power amplifier
[0191] 108 - Low noise converter block
[0192] 109 - Filter
[0193] 110 - Antenna
[0194] 200 - Hosting device
[0195] 201 - Radio 1
[0196] 202 - Radio 2
[0197] 203 - Radio 3
[0198] 205 - Long-term memory
[0199] 206 - Working memory
[0200] 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1300, 1400, 1500, 1600, 1700, 1800 - Client Device
[0201] 601 - Processor
[0202] 602 - Memory
[0203] 603 - User Interface
[0204] 604 - Communication bus
[0205] 605 - Software code
[0206] 606 - Display
[0207] 607 - Working memory
[0208] GLOSSARY
[0209]
[0210] Table 5
Claims
CLAIMS 1. A method implemented by a communication device (200) comprising a plurality of radios (201, 202, 203), each radio hosting at least one access point (AP1.1, AP1.2, AP2.1, AP3.1, AP3.2) to a wireless network associated with the access point, an access point having one of at least an enabled state and a disabled state, comprising transmitting, by a first enabled access point of the communication device, information relating to a second access point even when this second access point is in the disabled state.
2. The method of claim 1, the information relating to the second access point comprising an identifier of the second access point and the state of the second access point.
3. Method according to one of claims 1 or 2, the information relating to the second access point being transmitted in at least one of: a beacon (S301) emitted by the first access point; a response (S302) to a request for information from a client device (600).
4. Method according to one of claims 1 or 2, the information relating to the second access point being transmitted in a response (S504) to a request for information from a client device adapted to associate with an access point, transmitted to the first access point, a beacon (S502) emitted by the first access point not comprising information relating to access points other than the first access point.
5. Method according to one of claims 1 to 4, the state of the second access point further comprising a state characterizing a malfunction of the second access point.
6. Method according to one of claims 1 to 5, an activated access point broadcasting on a transmission channel, the information relating to the second access point comprising, in the case where the second access point is in the deactivated state, the last transmission channel used by the second access point.
7. Method according to one of claims 1 to 6, the information relating to the second access point comprising a list of transmission channels on which the second access point is capable of operating.
8. Method according to claim 7, said list being included in the information relating to the second access point only in the case where this second access point is in the deactivated state.
9. Method according to one of claims 1 to 8, the information relating to the second access point comprising information representative of past statistics of the second access point when it is activated.
10. Method according to one of claims 1 to 9, comprising receiving, from a client device, a request to activate the second access point in the deactivated state, the activation request comprising an identifier of the second access point in the deactivated state.
11. The method of claim 10, the activation request comprising at least one reason why the activation request is made by the client device.
12. The method of claim 11, wherein a reason comprises one of: a traffic type to be supported; a current traffic type whose quality is not satisfactory on an activated access point; information representative of the fact that interference due to sources external to the client device is greater than a threshold; information representative of the fact that interference due to sources internal to the client device is greater than one.
13. Method according to one of claims 10 to 12, comprising, in the event of acceptance of the request for activation of the second access point by the communication device, the transmission of a response to the client device having transmitted the activation request, the response comprising information indicating the acceptance of the activation request; the activation of the second access point for which activation has been requested.
14. The method of claim 13, comprising, if the radio hosting the second access point for which activation has been requested is in the deactivated state, first activating that radio.
15. Method according to one of claims 13 or 14, the response comprising the transmission of a first time delay (T1) defining a minimum duration to wait before the second access point for which activation has been requested should actually be indicated as activated in the information relating to the second access point.
16. Method according to one of claims 13 to 15, the response comprising a minimum duration during which the second access point will be maintained in an activated state by the communication device.
17. Method according to one of claims 13 to 16, comprising: monitoring the second access point activated upon request; determining whether no client device is associated with it, and if so, deactivating the second access point.
18. The method of claim 17, comprising, upon a positive determination, deactivation of the second access point being implemented if no client device has associated with the second access point before the elapse of a third time delay (T3).
19. Method according to one of claims 13 to 16, the acceptance of a request to activate an access point being subject to one or more conditions, the method comprising, once the second access point has been activated, the deactivation of the second access point if at least one condition is no longer met.
20. The method of claim 19, comprising, prior to deactivation, transmitting one of a message (S1302) indicative of the upcoming deactivation to the client devices associated with the second access point or a message (S1402) comprising a request to transition to an activated access point other than the second access point.
21. Method according to claim 19, comprising transmitting (S1302, S1402) a fourth time delay (T4) after which the deactivation of the second access point will be carried out.
22. Method according to one of claims 10 to 21, comprising, in the event of rejection of the request for activation of the second access point by the communication device, the transmission of a response (S1105) to the client device having transmitted the activation request, the response comprising information indicating the rejection of the activation request.
23. The method of claim 22, the response comprising a second time delay (T2) indicating a minimum time that the client device will have to wait before repeating its activation request for the second access point.
24. Method according to one of claims 22 or 23, the response comprising a reason for the rejection decision.
25. Method according to one of claims 22 to 24, the response comprising information identifying an access point replacing the second access point for which the activation request was rejected.
26. Method according to one of claims 1 to 25, comprising transmitting an activated or deactivated state of the radio hosting the second access point.
27. A communication device (200) comprising: a plurality of radios (201, 202, 203), each radio hosting at least one access point (AP1.1, AP1.2, AP2.1, AP3.1, AP3.2) to a wireless network associated with the access point, an access point having one of an enabled state and a disabled state; and means for performing the steps of a method according to one of claims 1 to 26.
28. A method implemented by a client device (600) adapted to associate via an access point of a communication device in a wireless network, an access point having one of at least an activated state and a deactivated state, the method comprising: obtaining (S301, S302) from a first activated access point of the communication device, information relating to one or more second access points, even for the second access point(s) whose state is the deactivated state, the information comprising for a given second access point, a respective identifier and the respective state of the given second access point; in the case where at least one second access point is in the deactivated state, determining whether one of the second access point(s) is to be activated, and if so, transmitting, to the first access point, a request to activate the second access point to be activated.
29. The method of claim 28, wherein the information relating to a second access point comprises an indication of activation time, the indication comprising at least one of: an activation time of the second access point in the deactivated state; and an activation time of a radio hosting the second access point in the deactivated state; determining whether one of the one or more second access points is to be activated is based on the indication.
30. Method according to one of claims 28 or 29, the information relating to a given second access point identifying a type of traffic supported by this given second access point, the determination whether one of the second access point(s) must be activated being a function of the type of traffic supported.
31. Method according to one of claims 28 to 30, the information relating to a given second access point identifying a type of traffic supported by this given second access point, the determination whether one of the second access point(s) must be activated being a function of the type of traffic supported.
32. Method according to one of claims 28 to 31, the information relating to a given second access point comprising at least one descriptive statistic of a past operation of this given second access point, the determination whether one of the second access point(s) must be activated being a function of the at least one statistic.
33. Method according to one of claims 28 to 32, comprising, before obtaining information relating to one or more second access points, the prior association (S502) with the first access point, the transmission (S503) of a request for information relating to one or more second access points to the first access point and the obtaining (S504) of this information in response to the request.
34. Method according to one of claims 28 to 33, obtaining information relating to one or more second access points comprising receiving a beacon (S402) from the first access point, the information relating to one or more second access points being contained in the beacon.
35. Client device (600) comprising - a communication interface (604) adapted to communicate with an access point in a wireless network; and - means for carrying out the steps of a method according to one of claims 28 to