DE102021134386A1 - PRIVATE MEDIA ACCESS CONTROL (MAC) ADDRESS OF A WI-FI DEVICE - Google Patents

Abstract

A circuit configured to: receive a frame from a Wi-Fi device, the frame including an encrypted private identifier; decrypt the encrypted private identifier; and identify the other Wi-Fi devices based on the decrypted private identifier.

Description

CROSS REFERENCE TO RELATED APPLICATION

This patent application claims benefit and priority of the US Provisional App. No. 63/161,160 , filed March 15, 2021.

TECHNICAL AREA

This disclosure relates generally to systems and methods for wireless communications, and more particularly to a Wi-Fi device's private medium access control (MAC) address.

BACKGROUND

Wireless devices are proliferating and increasingly demanding access to wireless channels. The Institute of Electrical and Electronics Engineers (IEEE) is developing one or more standards that use Orthogonal Frequency-Division Multiple Access (OFDMA) in channel allocation.

character list

• 1 1 ist ein Netzwerkdiagramm, das eine beispielhafte Netzwerkumgebung für eine private MAC-Adresse gemäß einem oder mehreren Beispielen der vorliegenden Offenbarung zeigt.
• 2 veranschaulicht Verbindungen zwischen Stationen von Multi-Link-Vorrichtungen.
• 3 veranschaulicht ein 4-Wege-Handshake.
• 4 veranschaulicht ein Flussdiagramm eines illustrativen Prozesses für ein illustratives privates MAC-Adressensystem gemäß einem oder mehreren Beispielen der vorliegenden Offenbarung.
• 5 zeigt ein Funktionsdiagramm einer beispielhaften Kommunikationsstation, die zur Verwendung als Benutzervorrichtung geeignet sein kann, gemäß einem oder mehreren Beispielen der vorliegenden Offenbarung.
• 6 veranschaulicht ein Blockdiagramm einer Beispielmaschine, auf der eine oder mehrere Techniken (z.B. Verfahren) gemäß einem oder mehreren Beispielen der vorliegenden Offenbarung ausgeführt werden können.
• 7 ist ein Blockdiagramm einer Funkarchitektur gemäß einigen Beispielen.
• 8 veranschaulicht eine beispielhafte Front-End-Modul-Schaltung zur Verwendung in der Funkarchitektur von 7, gemäß einem oder mehreren Beispielen der vorliegenden Offenbarung.
• 9 veranschaulicht ein Beispiel für eine Funk-IC-Schaltung zur Verwendung in der Funkarchitektur von 7 gemäß einem oder mehreren Beispielen der vorliegenden Offenbarung.
• 10 zeigt ein Beispiel für eine Basisbandverarbeitungsschaltung zur Verwendung in der Funkarchitektur von 7, gemäß einem oder mehreren Beispielen der vorliegenden Offenbarung.

In the drawings, like reference numbers generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis generally being placed upon illustrating exemplary principles of the disclosure. In the following description, various aspects of the disclosure are described with reference to the following drawings, in which:

• 1 1 is a network diagram depicting an example network environment for a private MAC address, in accordance with one or more examples of the present disclosure.
• 2 illustrates connections between stations of multi-link devices.
• 3 illustrates a 4-way handshake.
• 4 12 illustrates a flow diagram of an illustrative process for an illustrative private MAC address system, in accordance with one or more examples of the present disclosure.
• 5 10 shows a functional diagram of an example communication station that may be suitable for use as a user device, in accordance with one or more examples of the present disclosure.
• 6 11 illustrates a block diagram of an example machine on which one or more techniques (eg, methods) according to one or more examples of the present disclosure may be performed.
• 7 12 is a block diagram of a radio architecture, according to some examples.
• 8th FIG. 12 illustrates an example front-end module circuit for use in the radio architecture of FIG 7 , according to one or more examples of the present disclosure.
• 9 FIG. 12 illustrates an example of a radio IC circuit for use in the radio architecture of FIG 7 according to one or more examples of the present disclosure.
• 10 FIG. 1 shows an example of a baseband processing circuit for use in the radio architecture of FIG 7 , according to one or more examples of the present disclosure.

DETAILED DESCRIPTION

The following description and drawings illustrate examples sufficiently specific to enable those skilled in the art to practice them. Other examples may include structural, logical, electrical, procedural, algorithmic, and other changes. Sections and features of some examples may be included in or superseded by other examples. The examples given in the claims include all available equivalents of these claims.

The following describes a problem related to a connection between a non-AP StA and an AP. However, the same problem also applies to a connection between a non-AP MLD and an AP MLD.

While a Wi-Fi device can randomize the MAC address while connecting to an AP, i.e. use a different MAC address at a different time while connecting to an AP, it has been noted that this may break certain existing mechanisms.

MAC-based Parental Controls:

Almost every home wireless router has the ability to set up a MAC address pass/block list to determine whether to allow/deny a connected wireless device access to the network. The use case is parental control, where parents can restrict Internet access of their children's wireless devices. This mechanism is based on the assumption that a wireless device cannot change its MAC address. If a wireless device can change the MAC address on each connection, a mechanism like the blacklist no longer works.

MAC-based access network:

On certain networks, such as university networks, where the network administrator requires the student to register on the network, a typical approach is to record the MAC address while the registration is being performed. If a wireless device can change the MAC address with each connection, the student who has registered on the network may still not be able to access the network after registration.

DHCP:

After a Wi-Fi device completes the typical authentication, association, and 4-way handshake exchange to establish the security key. DHCP is required to get the IP address. However, a DHCP server typically assigns an IP address from the allocation pool to a MAC address. If a WLAN device randomizes the MAC address much more frequently than the IP address expires, the IP address in the pool can quickly be used up. There are also use cases where specific MAC addresses are included in a specific IP address allocation pool, and randomizing MAC addresses breaks this mechanism.

The possibility that random MAC address assignment could break certain mechanisms has prevented random MAC address assignment from being used consistently. A typical situation is that MAC address randomization is switched off by default (e.g. Windows computers). Another typical situation is that the MAC address feature is turned on by default (e.g. Android or iOs) but when a customer is having problems connecting to the network or having functionality disruption (due to a DHCP issue or a MAC-based access network or a MAC-based parental control), the customer simply switches off the entire function.

There is an option on the wireless device to disable MAC randomization for a specific SSID that identifies a network. So if MAC address randomization is causing problems for a particular network, MAC address randomization can be turned off for that network only, while leaving it on for other networks that don't affect functionality.

Having MAC address randomization turned off does not solve the privacy issue.

A normal person has neither the time nor the energy to analyze and find out whether MAC address randomization needs to be turned on for a particular SSID for every wireless device, although the option is there. A normal person is more likely to turn off the feature and make sure they can access the network to surf the news, shop, and meet other personal needs.

Also note that it is difficult for the wireless device itself to detect whether to use MAC address randomization automatically. Use cases such as parental control, MAC-based access network, and DHCP assignment rules cannot be detected automatically.

For these reasons, there is a constant conflict between achieving privacy and breaking existing mechanisms.

Examples of the present disclosure relate to systems, methods, and apparatus for private medium access control (MAC) addresses of Wi-Fi devices.

In one example, a private MAC address system may allow a Wi-Fi device to have a private MAC address that is securely provided to the attached AP or AP Multilink Device (MLD).

It is proposed that the private MAC address is provided in message 2 of the 4-way handshake and encrypted with the EAPOL-Key Encryption Key (KEK).

After the private address is provided, the attached AP or AP MLD uses the private MAC address to identify the higher-level Wi-Fi device.

A wireless device can have a different private MAC address for different SSIDs to avoid the problem of figuring out whether a particular network identified by a Service Set Identifier (SSID) can be trusted.

A Wi-Fi device can have the same private MAC address for different SSIDs, but then has to solve the problem of figuring out if the AP advertising the SSID can be trusted.

The Wi-Fi device from a higher layer perspective is now identified by the private address, which is not exposed over the air. The private address can now be set for a specific SSID without affecting the functionalities of MAC-based Parental Control, MAC-based Access Network and Dynamic Host Configuration Protocol (DHCP).

The above descriptions are provided for purposes of illustration and are not to be taken as limiting. There are numerous other examples, configurations, processes, algorithms, etc., some of which are described in more detail below. The examples will now be described with reference to the accompanying figures.

1 FIG. 14 is a network diagram depicting an example private MAC address network environment, in accordance with some examples of the present disclosure. The wireless network 100 may include one or more user devices 120 and one or more access points (AP) 102 capable of communicating according to IEEE 802.11 communication standards. The user device(s) 120 may be mobile devices that are non-stationary (eg, do not have fixed locations), or may be stationary devices.

In some examples, user devices 120 and AP 102 may include one or more computing systems that conform to the functional diagram of FIG 5 and/or the example machine/system of 6 resemble

One or more illustrative user device(s) 120 and/or AP(s) 102 may be operated by one or more user(s) 110. Note that any addressable entity can be a station (STA). A STA can have several different characteristics, each of which determines its function. For example, a single addressable entity can simultaneously be a portable STA, a Quality of Service (QoS) station, a slave STA, and a hidden STA. The illustrative device(s) 120 and AP(s) 102 may be STAs. The illustrative device(s) 120 and/or AP(s) 102 may operate as a Basic Personal Service Set (PBSS) Control Point/Access Point (PCP/AP). User equipment(s) 120 (eg, 124, 126, or 128) and/or AP(s) 102 may comprise any suitable processor controlled device, including but not limited to a mobile device or a non-mobile, eg, static device . The user equipment(s) 120 and/or AP(s) 102 may be, for example, a user equipment (UE), a station (STA), an access point (AP), a software-enabled AP (SoftAP), a personal computer (PC), a portable bare wireless device (eg, bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an Ultrabook™ computer, a notebook computer, a tablet computer, a server Computer, a handheld computer, a handheld device, an Internet of Things (IoT) device, a sensor device, a PDA device, a PDA handheld device, an on-board device, an off -Onboard device, a hybrid device (e.g., a hybrid device (e.g., a combination of cellular phone functionality with PDA device functionality), a consumer device, a vehicle device, a non-vehicle device, a mobile or portable device, a non-mobile or non- portable device, a cellular phone, a cellular phone, a PCS device, a PDA device containing a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer , a "Carry Sma ll Live Large" device (CSLL), an ultra-mobile device (UMD), an ultra-mobile PC (UMPC), a mobile internet device (MID), an "origami" device or computing device, a device that performs dynamically composable computing (DCC), contextual device, video device, audio device, A/V device, set-top box (STB), Blu-ray Disc (BD) player, BD recorder, a digital video disc (DVD) player, a high-definition (HD) DVD player, a DVD recorder, a high-definition DVD recorder, a personal video recorder (PVR), a high-definition Broadcast receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, a audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player or the like. Other devices including smart devices such as lights, air conditioners, car components, household components, appliances, etc. can also be included in this list.

As used herein, the term "Internet of Things (IoT) device" refers to any object (e.g., a device, sensor, etc.) that has an addressable interface (e.g., an Internet Protocol (IP) address, a Bluetooth identifier (ID), a Near Field Communication (NFC) ID, etc.) and can transmit information to one or more other devices via a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, radio frequency identification (RFID) tag, NFC tag, or the like, or an active communication interface, such as a modem , a transceiver, a transceiver or the like. An IoT device may have a particular set of attributes (e.g., a device state or status, e.g., whether the IoT device is on or off, open or closed, idle or active, available to perform tasks or busy, etc ., a cooling or heating function, an environmental monitoring or recording function, a light emitting function, a sound emitting function, etc.) embedded in and/or by a central processing unit (CPU), a microprocessor, an ASIC or the like controlled/monitored and set up to connect to an IoT network such as a local ad hoc network or the Internet. For example, IoT devices can include refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, washing machines, tumble dryers, ovens, air conditioners, thermostats, televisions, lighting fixtures, vacuum cleaners, sprinklers, electric meters, gas meters, etc., provided the devices are equipped with are equipped with an addressable communication interface for communication with the IoT network. IoT devices can also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), and so on. Accordingly, the IoT network may include a combination of “traditional” internet-enabled devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that typically do not have internet connectivity (e.g., dishwashers, etc.).

The user equipment(s) 120 and/or AP(s) 102 may also comprise mesh stations, for example in a mesh network according to one or more IEEE 802.11 standards and/or 3GPP standards.

Each of user equipment(s) 120 (eg, user equipments 124, 126, 128) and AP(s) 102 may be configured to communicate with one another via one or more communication networks 130 and/or 135, wirelessly or wired. User device(s) 120 may also communicate peer-to-peer or directly with or without AP(s) 102. Each of communication networks 130 and/or 135 may be, but is not limited to, any Combination of different types of suitable communication networks, such as broadcast networks, cable networks, public networks (eg the Internet), private networks, wireless networks, cellular networks or any other suitable private and / or public networks. Furthermore, each of the communication networks 130 and/or 135 have any suitable communication domain associated with them and include, for example, global networks (eg, the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, each of the communication networks 130 and/or 135 may include any type of medium over which network traffic may be transmitted, including but not limited to coaxial cable, twisted pair wiring, optical fiber, a hybrid fiber coaxial medium (HFC), terrestrial microwave transceivers, Radio Frequency Communications Media, White Space Communications Media, Ultra High Frequency Communications Media, Satellite Communications Media, or any combination thereof.

Each of user equipment(s) 120 (e.g., user equipments 124, 126, 128) and AP(s) 102 may include one or more communication antennas. The one or more communication antennas can be any suitable type of antenna that supports the communication protocols used by UE(s) 120 (e.g., UEs 124, 126, and 128) and AP(s) 102 correspond to. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, IEEE 802.11 family standards compliant antennas, directional antennas, omnidirectional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas , omnidirectional antennas, quasi-omnidirectional antennas or the like. The one or more communication antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communication signals, to and/or from user equipments 120 and/or AP(s) 102.

Each of user equipment(s) 120 (e.g., user equipments 124, 126, 128) and AP(s) 102 may be configured to perform directed transmission and/or directed reception in connection with wireless communications in a wireless network. Each of user equipment(s) 120 (e.g., user equipments 124, 126, 128) and AP(s) 102 may be configured to provide such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like) to carry out. Each of the multiple antenna arrays can be used for transmission and/or reception in a particular respective direction or range of directions. Each of user equipment(s) 120 (e.g., user equipments 124, 126, 128) and AP(s) 102 may be configured to perform any directional transmission toward one or more defined transmit sectors. Each of user equipment(s) 120 (e.g., user equipments 124, 126, 128) and AP(s) 102 may be configured to perform any directional reception from one or more defined reception sectors.

MIMO beamforming in a wireless network can be performed with RF beamforming and/or digital beamforming. In some examples, when performing a particular MIMO transmission, UEs 120 and/or AP(s) 102 may be configured to use all or a subset of their one or more communication antennas to perform MIMO beamforming.

Each of UEs 120 (e.g., UEs 124, 126, 128) and AP(s) 102 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels that conform to the communication protocols used by each of UEs 120 and AP(s) 102 to communicate with each other. The radio components can have hardware and/or software to modulate and/or demodulate communication signals according to predetermined transmission protocols. The radio components may still have hardware and/or software instructions to communicate over one or more Wi-Fi and/or Wi-Fi Direct protocols as defined by the IEEE 802.11 standards (Institute of Electrical and Electronics Engineers ) are standardized. In certain examples, the radio component can be configured in cooperation with the communication antennas to transmit over 2.4 GHz channels (e.g. 802.11b, 802.11g, 802.11n, 802.11ax), 5 GHz channels (e.g. 802.11n, 802.11ac, 802.11ax) or 60 GHz channels (e.g. 802.11ad, 802.11ay). 800MHz channels (e.g. 802.11ah). The communication antennas can operate at 28 GHz and 40 GHz. It is understood that this list of communication channels according to certain 802.11 standards is only a partial list and that other 802.11 standards can also be used (e.g. next generation Wi-Fi or other standards). In some examples, non-Wi-Fi protocols may be used for communication between devices, such as Bluetooth, Dedicated Short-Range Communication (DSRC), Ultra-High Frequency (UHF) (e.g., IEEE 802.1laf, IEEE 802.22), White -Band frequency (e.g. white spaces) or other packetized radio communications. The radio component can have any known receiver and baseband suitable for communication via the communication protocols.

The radio component can also have a low-noise amplifier (LNA), additional signal amplifiers, an analog-to-digital converter (A/D), one or more buffers and a digital baseband.

In an example and with reference to 1 AP 102 may enable private MAC address 142 with one or more user devices 120.

It is understood that the above descriptions are provided for purposes of illustration and are not to be taken as limiting.

The proliferation of wireless devices such as phones, tablets and laptops has made access to information much easier and has made us almost inextricably linked to these wireless devices. Among these wireless devices, Wi-Fi is the popular access mechanism that offers a low-cost, convenient distance measurement network. However, it has been pointed out that the MAC address of the Wi-Fi device can be used for tracking the device, and since wireless devices are intrinsically linked to the person using the device, the MAC address of the Wi -Fi device can then be used to track a specific individual, violating the right to privacy.

To solve the problem of privacy, a common practice is to randomize the MAC address used by the Wi-Fi device. In detail,

A Wi-Fi device can randomize the MAC address during active scanning, e.g. when sending a probe request.

A Wi-Fi device can randomize the MAC address while connecting to an AP, i.e. it can use a different MAC address if it connects to an AP at a different time.

The current 802.11 specification has no mechanism that allows a Wi-Fi device to randomize MAC addressing while connected to an AP, i.e. after authentication and association with the AP.

In the never-ending quest for high throughput, 802.11 be creates a framework that allows multiple links to connect while connected to a network, as shown below.

On each side are two multi-link devices that have multiple STAs that can connect to each other. The detailed definition is shown below.

Multi-Link Device: A logical entity containing one or more STAs. The logical unit has a MAC data service interface and primitives for the Logical Link Control LLC and a single address associated with the interface that can be used for communication on the DSM.

NOTE - A multilink device allows STAs within the multilink logical unit to have the same MAC address.

NOTE - The exact name is subject to change.

For the infrastructure framework, there is a multilink AP device that has APs on one side and a multilink non-AP device that has non-APs on the other side. The detailed definition is shown below.

Multilink AP Device: A multilink device where each STA within the multilink device is an EHT AP.

Multilink Non-AP Device: A multilink device where each STA within the multilink device is a non-AP EHT STA.

Note that this framework is a natural extension of single-link operation between two STAs that are AP and non-AP STA in the framework of the infrastructure.

2 shows different components of an MLD. Each MLD can have a MAC address.

Each MLD has an MLD MAC address. Each STA of an MLD also has a STA MAC address as shown in links 210.

Different STAs of an MLD have different MAC addresses. The MAC address of the MLD can be the same as or different from one of the MAC addresses of the STAs of the MLD.

The MAC address of MLD is introduced to ensure that the traditional mapping of AP and STA from the higher layer perspective under multi-link is preserved, and the mapping is maintained by AP MLD and non-AP MLD independently of the MAC Replaces addresses used by the MLD's STAs, as shown in links 220.

Starting with the connection between a non-AP STA and an AP, then the connection between a non-AP MLD and an AP MLD.

For the connection between a non-AP StA and an AP.

A non-AP STA has a private MAC address that is different from the MAC address of the non-AP STA.

A non-AP STA should use the same private MAC address for a network identified by an SSID.

The MAC address of the non-AP STA is used for the wireless transmission, which includes the exchange of authentication frame, association frame and 4-way handshake.

The MAC address of the non-AP STA is used for the PMK calculation in the SAE method.

The MAC address of the non-AP-StA is used as the address of the SPA in the PTK calculation.

The private MAC address is provided in message 2 of the 4-way handshake.

Key Data Encapsulation (KDE) is used to exhibit the private MAC address.

Existing KDE with data type 3 can be used for this purpose.

A new KDE that has the private MAC address can be used for this purpose.

The KDE containing the private MAC address is included in the key data field of message 2.

An additional element can be used to include the private MAC address.

The element containing the private MAC address is contained in the key data field of message 2.

The key data field of message 2 is wrapped/encrypted using KEK with an appropriate key transcoding algorithm. Also, the Encrypted Key Data field is set to 1.

Alternatively, a private identifier of the STA is provided in message 2 of the 4-way handshake.

The private identifier cannot be a MAC address.

The private identifier can be a MAC address.

A non-AP-STA should use the same private identifier for a network identified by an SSID.

A KDE is used to hold the private identifier.

A new KDE that has the private identifier can be used for this purpose.

The KDE containing the private MAC identifier is included in the key data field of message 2.

An additional element can be used to have the private MAC identifier.

The element containing the private MAC identifier is contained in the key data field of message 2.

The key data field of message 2 is wrapped/encrypted using KEK with an appropriate key-wrap algorithm. Also, the Encrypted Key Data field is set to 1.

3 shows the sequence of the 4-way handshake.

The EAPOL keyframe format is shown in the table below: Protocol version - 1 octet Packet type - 1 octet Packet body length - 2 octets Descriptor Type - 1 octet Key information - 2 octets Key length - 2 octets Key Replay Counter - 8 octets Key nonce - 32 octets EAPOL Key IV - 16 octets Key RSC - 8 octets Reserved - 8 octets Key MIC - variable Key data length - 2 octets Key data - n octets

The format of a key information field containing an encrypted key data field is shown in the table below:

The format of a KDE selector is shown in the table below: OUI data type meaning 00-0F-AC 0 Reserved 00-0F-AC 1 GTK KDE 00-0F-AC 2 Reserved 00-0F-AC 3 MAC address KDE 00-0F-AC 4 PMKID KDE 00-0F-AC 5 Reserved(#59) 00-0F-AC 6 Nonce KDE 00-0F-AC 7 lifetime KDE 00-0F-AC 8th Error KDE 00-0F-AC 9 IGTK KDE 00-0F-AC 10 Key ID KDE 00-0F-AC 11 Multi-Band GTK KDE 00-0F-AC 12 Multi-Band Key ID KDE 00-0F-AC 13(ed) OCI KDE (M58) 00-0F-AC 14 BIGTK KDE (#2116) 00-0F-AC 15-255 Reserved Other OUI or CID Any Manufacturer specific

The key wrapping algorithm table is shown below: AKM integrity algorithm KCK bits Size of MIC Key wrapping(#4723) algorithm KEK_Bits KCK2_Bits KEK2_Bits Outdated HMAC-MD5 128 16 ARC4 128 0 0 00-OF-AC:1 HMAC-SHA-1-128 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:2 HMAC-SHA-1-128 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:3 AES-128-CMAC 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:4 AES-128-CMAC 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:5 AES-128-CMAC 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:6 AES-128-CMAC 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:8 AES-128-CMAC 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:9 AES-128-CMAC 128 16 NIST AES Key Pack 128 0 0 00-OF-AC:11 HMAC-SHA-256 128 16 NIST AES Key Pack 128 0 0 00-0F-AC:12 HMAC-SHA-384 192 24 NIST AES Key Pack 256 0 0 00-0F-AC:13 HMAC-SHA-384 192 24 NIST AES Key Pack 256 0 0 (11ai)00-0F-AC:14 AES-SIV-256 0 0 AES-SIV-256 256 0 0 (11ai)00-0F-AC:15 AES-SIV-512 0 0 AES-SIV-512 512 0 0 (11ai)00-0F-AC:16 AES-SIV-256/ AES-128-CMAC 0 0/16 AES-SIV-256/NIST AES Key Pack 256 128 128 (11ai)00-0F-AC:17 AES-SIV-512/HMAC-SHA-384 0 0/24 AES-SIV-512/NIST AES Key Pack 512 192 256

The KDE format is shown in the table below: Type (0xdd) length OUI data type Data Octets: 1 1 3 1 (Length - 4)

Two examples of a KDE format are provided in the table below:

The private MAC address or identifier can be provided in the frame body of a protected management frame.

Two examples of an element for carrying a private MAC address or private identifier are shown in the table below:

The private MAC address is used in the SA field of the A-MSDU sent from the non-AP STA.

After an AP obtains the private MAC address of the non-AP STA.

The authentication/association/4-way handshake state machine maintained for the non-AP STA MAC address is now the authentication/association/4-way handshake state machine maintained for the private MAC address becomes.

The AP uses the private MAC address as the SA to transmit the data transmitted by the non-AP STA via the DS.

The AP uses the private MAC address to match the DA field of the data transmitted by the DS and transmit the data to the non-AP STA.

Skill Display:

The AP indicates whether it supports the operation of receiving private MAC addresses.

The ad is given in RSNXE.

The AP indicates whether the process of providing a private MAC address is required.

The ad is included with RSNXE.

The non-AP STA indicates whether it supports the process of broadcasting a private MAC address.

The ad is included with RSNXE.

The AP indicates whether it supports the operation of receiving a private identifier.

The ad is included with RSNXE.

The AP indicates whether the process of providing the private identifier is required.

The display is in RSNXE.

The non-AP STA indicates whether it supports the private identifier transmission process.

The ad is included with RSNXE.

For the connection between a non-AP MLD and an AP MLD.

A non-AP MLD has a private MAC address that is different from the MAC address of any connected non-AP STA.

A non-AP MLD should use the same private MAC address for a network identified by an SSID.

The MAC addresses of the associated non-AP STAs are used for the wireless transmission, which includes the exchange of authentication frames, association frames and 4-way handshake.

The MAC address of the non-AP MLD is used for the PMK calculation in the SAE method.

The MAC address of the non-AP MLD is used as the address of the SPA in the PTK calculation.

The private MAC address is transmitted in message 2 of the 4-way handshake.

A KDE is used to exhibit the private MAC address.

Existing KDE with data type 3 can be used for this purpose.

A new KDE containing the private MAC address can be used for this purpose.

The KDE containing the private MAC address is included in the key data field of message 2.

The key data field of message 2 is wrapped/encrypted using KEK with an appropriate key wrapping algorithm. Also, the Encrypted Key Data field is set to 1.

Alternatively, a private identifier of the non-AP MLD is specified in message 2 of the 4-way handshake.

The private identifier cannot be a MAC address.

The private identifier can be a MAC address.

A non-AP MLD should use the same private identifier for a network identified by an SSID.

A KDE is used to have the private identifier.

A new KDE that has the private identifier can be used for this purpose.

The KDE containing the private MAC identifier is included in the key data field of message 2.

An additional element can be used to have the private MAC identifier.

The element containing the private MAC identifier is contained in the key data field of message 2.

The key data field of message 2 is wrapped/encrypted using KEK with an appropriate key wrapping algorithm. Also, the Encrypted Key Data field is set to 1.

The private MAC address or identifier may be specified in the frame body of the protected management frame.

The private MAC address is used in the SA field of the A-MSDU sent by the connected non-AP STAs of the non-AP MLD.

After an AP MLD obtains the private MAC address of the non-AP MLD.

The authentication/association/4-way handshake state machine maintained for the MAC address of the non-AP MLD is now the authentication/association/4-way handshake state machine maintained for the private MAC address becomes.

The AP MLD uses the private MAC address as SA to transmit the data provided by the non-AP MLD via the DS.

The AP MLD uses the private MAC address to match the DA field of the data transmitted by the DS and to transmit the data to the non-AP MLD.

Skill Display:

AP MPD indicates whether it supports receiving private MAC addresses from non-AP MLD.

AP MLD indicates whether the process of providing a private MAC address is required from a non-AP MLD.

The ad is included with RSNXE.

The display is provided in RSNXE by each connected AP.

Each attached AP of an AP MLD declares the same value of capability to support the operation of receiving private MAC addresses.

The indication may be included in another MLD element that indicates the MLD security capability.

Non-AP MLD indicates whether it supports the process of sending a private MAC address.

The ad is included with RSNXE.

The indication may be included in another MLD element that indicates the MLD security capability.

AP MPD indicates whether it supports receiving private identifiers from non-AP MLD.

AP MLD indicates whether the process of providing a private identifier is required from a non-AP MLD.

The ad is given in RSNXE.

The display is provided in RSNXE by each connected AP.

Each associated AP of an AP MLD declares the same value of ability to support the operation of receiving private identifiers.

The indication may be included in another MLD element that indicates the MLD security capability.

Non-AP MLD indicates whether it supports the process of sending a private identifier.

The ad is included with RSNXE.

The indication may be included in another MLD element that indicates the MLD security capability.

It is understood that the above descriptions are provided for purposes of illustration and are not to be taken as limiting.

4 FIG. 4 shows a flowchart of illustrative process 400 for a private MAC address system, in accordance with one or more examples of the present disclosure.

At block 402, a device (e.g., user device(s) 120 and/or AP 102 of 1 ) detect a frame that has a private MAC address associated with an attached Multi-Link Device (MLD).

In block 404, the device may encrypt the private MAC address.

In block 406, the device may cause the frame to be sent to the MLD.

It is understood that the above descriptions are provided for purposes of illustration and are not to be taken as limiting.

5 FIG. 5 shows a functional diagram of an exemplary communication station 500, in accordance with one or more examples of the present disclosure. In an example shows 5 10 is a functional block diagram of a communication station configured for use as AP 102 ( 1 ) or as user device 120 ( 1 ) may be suitable. The communication station 500 can also be used as a handheld device, mobile device, cell phone, smartphone, tablet, netbook, wireless terminal, laptop, portable computing device, femtocell, high data rate (HDR) subscriber station, access point, access terminal, or other PCS device (Personal Communication System) must be suitable.

The communication station 500 may include communication circuitry 502 and a transceiver 510 for transmitting and receiving signals to and from other communication stations using one or more antennas 501 . The communications circuitry 502 may include circuitry that may operate physical layer (PHY) communications and/or medium access control (MAC) communications to control access to the wireless medium and/or any other communications layers to transmit and receive signals . The communication station 500 may also include processing circuitry 506 and memory 508 configured to perform the operations described herein. In some examples, the communication circuitry 502 and the processing circuitry 506 may be configured to perform the operations described in the figures, diagrams, and flows above.

According to some examples, the communication circuitry 502 may be configured to contend for a wireless medium and establish frames or packets for communication over the wireless medium. Communication circuitry 502 may be configured to send and receive signals. The communication circuitry 502 may also include circuitry for modulation/demodulation, up/down conversion, filtering, amplification, and so on. In some examples, the processing circuitry 506 of the communication station 500 may include one or more processors. In other examples, two or more antennas 501 may be coupled to communication circuitry 502, arranged to transmit and receive signals. Memory 508 may store information for configuring processing circuitry 506 to perform operations for setting up and transmitting message frames and for performing the various operations described herein. Memory 508 can be any type of memory, including non-transitory memory, to store information in a form that can be read by a machine (e.g., a computer). For example, memory 508 may include a computer readable storage device, read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and other storage devices and media.

In some examples, communication station 500 may be part of a handheld wireless communication device, such as a personal digital assistant (PDA), a laptop or handheld computer with wireless communication capability, a web tablet, a wireless phone, a smart phone, a wireless headsets, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a portable computing device, or any other device that receives information wirelessly and/or can send.

In some examples, the communication station 500 may include one or more antennas 501 . The antennas 501 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmitting RF signals. In some examples, a single multi-aperture antenna may be used instead of two or more antennas. In these examples, each aperture can be viewed as a separate antenna. In some MIMO (Multiple-Input-Multiple-Output) examples, the antennas can be effectively separated for spatial diversity and the different channel characteristics that can result between each of the antennas and the antennas of a transmitting station.

In some examples, the communication station 500 may include one or more of the following: a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other elements of a mobile device. The display can be an LCD screen that has a touch screen.

Although the communication station 500 includes several separate functional elements, two or more of the functional elements can be combined and implemented through combinations of software configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and combinations of various hardware and logic circuits to perform at least the functions described herein. In some examples, the functional elements of the communication station 500 may refer to one or more processes running on one or more processing elements.

Particular examples may be implemented in one or a combination of hardware, firmware, and software. Other examples may also be implemented as instructions stored on a computer-readable device that are readable and executable by at least one processor to perform the operations described herein. A computer-readable device may include any non-portable storage mechanism for storing information in a form readable by a machine (eg, a computer). A computer-readable storage device may include, for example, read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and other storage devices and media. In some examples, communication station 500 may include one or more processors and may be implemented with instructions stored on a computer readable device.

6 6 shows a block diagram of an example of a machine 600 or system upon which one or more techniques (eg, methods) discussed herein may be implemented. In other examples, machine 600 may operate as a standalone device or may be connected (eg, networked) to other machines. In a networked deployment, machine 600 may operate in the capacity of a server, a client, or both in server-client network environments. In one example, machine 600 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. Machine 600 may be a personal computer (PC), tablet PC, set top box (STB), personal digital assistant (PDA), cellular phone, portable computing device, web appliance, be a network router, switch, or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term "machine" is also intended to include any collection of machines that individually or collectively execute a set (or sets) of instructions to perform one or more of the methods discussed herein, such as Cloud Computing, Software as a Service (SaaS) or other computer cluster configurations.

Examples as described herein may include or operate with logic or a number of components, modules, or mechanisms. Modules are tangible units (e.g. hardware) that are able to carry out certain operations during operation. A module comprises hardware. In one example, the hardware may be specifically configured to perform a particular operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuitry, etc.) and a computer-readable medium bearing instructions, the instructions enabling the execution units to operate in a specific manner. The configuration can be done under the direction of the execution units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is in operation. In this example, the execution units can be members of more than one module. For example, the execution units may be setup during operation by a first set of instructions to implement a first module at a particular time and reconfigured by a second set of instructions to implement a second module at a second time .

The machine (e.g., computer system) 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), main memory 604, and static storage 606 some or all of which may communicate with each other via an interconnect (eg, a bus) 608 . The machine 600 may further include a power management device 632, a graphics display device 610, an alphanumeric input device 612 (eg, a keyboard), and a user interface (UI) navigation device 614 (eg, a mouse). In one example, the graphic display device 610, the alphanumeric input device 612, and the UI navigation device 614 may be a touchscreen display. The machine 600 may additionally include a storage device (ie, drive) 616, a signal generation device 618 (e.g., a speaker), a private MAC address device 619, a network interface device/transceiver 620 connected to one or more antennas 630 and one or more sensors 628, such as a Global Positioning System (GPS) sensor, compass, accelerometer, or other sensor. Device 600 may include an output controller 634, such as a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with one or more peripheral communicate with or control devices (eg, a printer, a card reader, etc.). The acts according to one or more examples herein Disclosures may be performed by a baseband processor. The baseband processor can be set up to generate corresponding baseband signals. The baseband processor may further include physical layer (PHY) and medium access control (MAC) layer circuitry and may further interface with the hardware processor 602 to generate and process the baseband signals and to perform operations of the main memory 604, the storage device 616 and/or or the private MAC address device 619 to control. The baseband processor can reside on a single radio card, chip, or integrated circuit (IC).

Device 616 may include a machine-readable medium 622 storing one or more sets of data structures or instructions 624 (e.g., software) embodying or used by one or more techniques or functions described herein. Instructions 624 may also reside in whole or at least in part in main memory 604, static storage 606, or hardware processor 602 when executed by machine 600. In an example, any one or any combination of hardware processor 602, main memory 604, static storage 606, or device 616 may represent a machine-readable medium.

Private MAC address device 619 may perform or perform any of the acts and processes (e.g., process 400) described and shown above.

It should be understood that the above is only a subset of what private MAC address device 619 may be configured to do, and that other functions implemented in this disclosure are also performed by private MAC address device 619 can become.

While machine-readable medium 622 is depicted as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database and/or associated caches and servers) configured to store one or multiple instructions 624 to store.

Various examples may be implemented in software and/or firmware in whole or in part. This software and/or firmware may take the form of instructions embodied in or on a non-transferable computer-readable storage medium. These instructions may then be read and executed by one or more processors to enable the operations described herein to be performed. The instructions may be in any suitable form, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such computer-readable medium may include any tangible, non-transitory medium for storing information in a form readable by one or more computers, such as, but not limited to, read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, etc.

The term “machine-readable medium” may include any medium capable of storing, encoding, or carrying instructions for execution by engine 600 that cause engine 600 to perform one or more of the techniques of the present disclosure, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media can include solid-state memory, optical, and magnetic media. In one example, a machine-readable mass medium comprises a machine-readable medium having a plurality of particles having a rest mass. Specific examples of machine-readable mass media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Instructions 624 may still be transmitted over a communications network 626 using a transmission medium via network interface device/transceiver 620 using any transmission protocol (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.) are sent or received. Communication networks can be, for example, a local area network (LAN), a wide area network (WAN), a packet data network (e.g. the Internet), mobile networks (e.g. cellular networks), simple telephone networks (POTS), wireless data networks (e.g. IEEE 802.11 family of standards, known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards and peer-to-peer (P2P) networks, and others. In one example, network interface device/transceiver 620 may include one or more physical jacks (eg, Ethernet, coaxial, or phone jacks) or one or more antennas to connect to communications network 626 . As an example, the network interface device/transceiver 620 may have a plurality of antennas to communicate wirelessly using at least one of the techniques SIMO (single-input multiple-output), MIMO (multiple-input multiple-output), or MISO (multiple-input single output) is used. The term "transmission medium" is intended to include any intangible medium capable of storing, encoding, or transmitting instructions for execution by the machine 600, and includes digital or analog communication signals or other intangible media to facilitate the communication of such software to facilitate.

The acts and processes described and shown above may be performed in any suitable order as desired in different implementations. Additionally, in certain implementations, at least a portion of the operations may be performed in parallel. Additionally, fewer or more acts than described may be performed in certain implementations.

7 FIG. 7 is a block diagram of a radio architecture 700 installed in one of example APs 102 and/or example user devices 120 of FIG 1 can be implemented. The radio architecture 700 may include radio front end module (FEM) circuitry (704a-b), radio IC circuitry (706a-b), and baseband processing circuitry (708a-b). The radio architecture 700 shown includes both WLAN (Wireless Local Area Network) and Bluetooth (BT) functionality, although the examples are not so limited. In this disclosure, the terms "WLAN" and "Wi-Fi" are used interchangeably.

The FEM circuitry 704a-b may include WLAN or Wi-Fi FEM circuitry 704a and Bluetooth (BT) FEM circuitry 704b. The WiFi FEM circuitry 704a may include a receive signal path that includes circuitry configured to operate on WiFi RF signals received from one or more antennas 701 to amplify the received signals and the amplified versions of the received signals to the WLAN radio IC circuit 706a for further processing. The BT FEM circuitry 704b may include a receive signal path that may include circuitry configured to operate on BT RF signals received from one or more antennas 701 to amplify the received signals and deliver the amplified versions of the received signals to the BT radio IC circuit 706b for further processing. The FEM circuitry 704a may also include a transmit signal path that may include circuitry configured to amplify WLAN signals provided by the wireless IC circuitry 706a for wireless transmission through one or more of the antennas 701 . Additionally, the FEM circuitry 704b may also include a transmit signal path that may include circuitry configured to amplify BT signals transmitted by the radio IC circuitry 706b for wireless transmission through the one or more antennas to be provided. In the example of 7 While FEM 704a and FEM 704b are shown as different from each other, examples are not so limited and are within the scope of using a FEM (not shown) having a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuits, wherein at least some of the FEM circuits share transmit and/or receive signal paths for both WLAN and BT signals.

The radio IC circuit 706a-b shown may include a WLAN radio IC circuit 706a and a BT radio IC circuit 706b. WLAN radio IC circuitry 706a may include a receive signal path that may include circuitry for downconverting WLAN RF signals received from FEM circuitry 704a and providing baseband signals to WLAN baseband processing circuitry 708a. BT radio IC circuitry 706b may in turn include a receive signal path that may include circuitry for downconverting BT RF signals received from FEM circuitry 704b and providing baseband signals to BT baseband processing circuitry 708b. The WiFi radio IC circuitry 706a may also include a transmit signal path that may include circuitry to upconvert WiFi baseband signals provided by the WiFi baseband processing circuitry 708a and output WiFi RF signals to the FEM circuitry 704a for subsequent wireless transmission through the one or more antennas 701. The BT radio IC circuit 706b may also include a transmit signal path that may include circuitry for upconverting BT baseband signals transmitted from the BT baseband processing circuitry 708b, and providing BT RF output signals to the FEM circuitry 704b for subsequent wireless transmission through the one or more antennas 701. In the example of 7 While radio IC circuits 706a and 706b are shown as being separate from one another, examples are not so limited and are within the scope of using one radio IC circuit (not shown) having a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuits, wherein at least some of the radio IC circuits have transmit and/or receive signal paths for both WLAN and BT signals share.

The baseband processing circuitry 708a-b may include a WLAN baseband processing circuitry 708a and a BT baseband processing circuitry 708b. WLAN baseband processing circuitry 708a may include memory, such as a set of RAM arrays in a Fast Fourier Transform or Inverse Fourier Transform block (not shown) of WLAN baseband processing circuitry 708a. Each of the WLAN baseband circuitry 708a and the BT baseband circuitry 708b may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuits 706a-b and also to generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuits 706a-b. Each of the baseband processing circuits 708a and 708b may still include physical layer (PHY) and medium access control (MAC) layer circuitry and may still interface with apparatus for generating and processing the baseband signals and controlling the operations of the radio IC circuits 706a -b have.

According to the example shown in 7 For example, WLAN-BT coexistence circuitry 713 may include logic that provides an interface between WLAN baseband circuitry 708a and BT baseband circuitry 708b to enable use cases requiring WLAN and BT coexistence. In addition, a switch 703 may be provided between the WLAN FEM circuit 704a and the BT FEM circuit 704b to switch between the WLAN and BT radios according to the needs of the application. Additionally, while the antennas 701 are shown connected to the WLAN FEM circuitry 704a and the BT FEM circuitry 704b, respectively, the examples include within their scope the sharing of one or more antennas between the WLAN and BT FEMs or the provision of more than one antenna connected to each of the FEMs 704a or 704b.

In some examples, front-end module circuitry 704a-b, radio IC circuitry 706a-b, and baseband processing circuitry 708a-b may be provided on a single radio card, such as wireless radio card 702. In some other examples, the one or more antennas 701, FEM circuitry 704a-b, and radio IC circuitry 706a-b may reside on a single radio card. In some other examples, radio IC circuitry 706a-b and baseband processing circuitry 708a-b may be provided on a single chip or integrated circuit (IC), such as IC 712.

In some examples, the wireless radio 702 may include a WLAN radio and be configured for Wi-Fi communication, although the examples are not limited in scope in this regard. In some of these examples, the radio architecture 700 may be configured to receive and transmit orthogonal frequency division multiplex (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multi-carrier communication channel. The OFDM or OFDMA signals may have a plurality of orthogonal subcarriers.

In some of these multi-carrier examples, the radio architecture 700 may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station, or a mobile device including a Wi-Fi device. In some of these examples, the radio architecture 700 may be configured to transmit and receive signals according to certain communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards, including 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad,
802.11ay and/or 802.11ax, and/or proposed specifications for WLANs, the examples not being limited in scope in this regard. The radio architecture 700 may also be capable of sending and/or receiving communications according to other techniques and standards.

In some examples, the radio architecture 700 may be configured for high-efficiency Wi-Fi (HEW) communication according to the IEEE 802.11ax standard. In these examples, the radio architecture 700 may be configured to communicate in accordance with an OFDMA technique, although the examples are not limited in scope in this regard.

In some other examples, the radio architecture 700 may be configured to transmit and receive signals transmitted using one or more other modulation techniques, such as spread spectrum modulation (e.g., Direct Sequence Code Division Multiple Access - DS-CDMA) and/or Frequency Hopping Code Division Multiple Access (FH-CDMA)), Time Division Multiplexing (TDM) modulation and/or Frequency Division Multiplexing (FDM) modulation, the scope of the examples being in this regard however, is not restricted.

In some examples, as in 6 As shown, BT baseband circuitry 708b may be compliant with a Bluetooth (BT) connectivity standard, such as Bluetooth, Bluetooth 8.0, or Bluetooth 6.0, or another iteration of the Bluetooth standard.

In some examples, the radio architecture 700 may include other radios, such as a cellular radio configured for cellular (e.g., 5GPP such as LTE, LTE-Advanced, or 7G communications).

In some IEEE 802.11 examples, the radio architecture 700 may be configured to communicate over various channel bandwidths, including bandwidths centered at about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5, 5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160MHz) (with non-contiguous bandwidths). In some examples, a channel bandwidth of 920MHz may be used. However, the scope of the examples is not limited with respect to the center frequencies mentioned above.

8th FIG. 7 illustrates the WLAN FEM circuitry 704a according to some examples. Although the example of 8th described in connection with WLAN FEM circuitry 704a, the example of FIG 8th in connection with the example of the BT FEM circuit 704b ( 7 ) are described, although other configurations of the circuit may be appropriate.

In some examples, the FEM circuitry 704a may include a TX/RX switch 802 to toggle between transmit and receive operations. The FEM circuit 704a may have a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 704a may include a low-noise amplifier (LNA) 806 to amplify the received RF signals 803 and provide the amplified received RF signals 807 as an output signal (e.g., to radio IC circuitry 706a-b ( 7 )). The transmit signal path of circuitry 704a may include a power amplifier (PA) to amplify input RF signals 809 (e.g., provided by radio IC circuitry 706a-b) and one or more filters 812, such as bandpass filters (BPFs), Low-pass filters (LPFs) or other types of filters to filter RF signals 815 for subsequent transmission (e.g., through one or more of antennas 701 ( 7 )) via an example 814 duplexer.

In some dual-mode Wi-Fi communication examples, the FEM circuitry 704a may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these examples, the receive signal path of the FEM circuit 704a may include a receive signal path duplexer 804 to separate the signals from each spectrum and provide a separate LNA 806 for each spectrum (see figure). In these examples, the transmit signal path of the FEM circuit 704a may also include a power amplifier 810 and a filter 812, such as a BPF, an LPF, or other type of filter for each frequency spectrum, and a transmit signal path duplexer 804 to split the signals of one of the different spectrums provide a single transmission path for subsequent transmission through the one or more of the antennas 701 ( 7 ). In some examples, the BT communication can utilize the 2.4 GHz signal paths and use the same FEM circuitry 704a as that for the WLAN communication.

9 7 shows the radio IC circuit 706a according to some examples. The 706a wireless IC circuit is an example of a circuit designed for use as a WLAN or BT wireless IC circuit 706a/706b ( 7 ) may be suitable, although other configurations of the circuit may be suitable. age natively can the example of 9 will be described in connection with the example of the BT radio IC circuit 706b.

In some examples, the radio IC circuit 706a may have a receive signal path and a transmit signal path. The receive signal path of the radio IC circuit 706a may include at least one mixer circuit 902, such as a down-converter circuit, an amplifier circuit 906 and a filter circuit 908. The transmit signal path of the radio IC circuit 706a may include at least one filter circuit 912 and a mixer circuit 914, such as for example an up-conversion mixer circuit. The radio IC circuit 706a may also include a synthesizer circuit 904 for synthesizing a frequency 905 for use by the mixer circuit 902 and the mixer circuit 914 . The mixer circuitry 902 and/or 914 may be configured to provide direct conversion functionality, according to some examples. The latter type of circuit has a much simpler architecture compared to standard superheterodyne mixer circuits and any flicker caused by it can be mitigated by using OFDM modulation, for example. 9 Figure 12 shows only a simplified version of a radio integrated circuit and, although not shown, may include examples where each of the circuits shown may have more than one component. For example, mixer circuitry 914 may each include one or more mixers, and filter circuitry 908 and/or 912 may each include one or more filters, such as one or more BPFs and/or LPFs, according to the needs of the application. For example, if the mixer circuits are of the direct conversion type, they may each have two or more mixers.

In some examples, mixer circuitry 902 may be configured to combine the FEM circuitry 704a-b ( 7 ) down-converts received RF signals 807 based on the synthesized frequency 905 provided by the synthesizer circuit 904 . The amplifier circuit 906 may be configured to amplify the down-converted signals and the filter circuit 908 may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 907 . The output baseband signals 907 may be sent to baseband processing circuitry 708a-b ( 7 ) for further processing. In some examples, the output baseband signals 907 may be zero-frequency baseband signals, but this is not a requirement. In some examples, the mixer circuit 902 may include passive mixers, although the examples are not limited in scope in this regard.

In some examples, the mixer circuit 914 may be configured to upconvert input baseband signals 911 based on the synthesized frequency 905 provided by the synthesizer circuit 904 to output RF signals 809 for the FEM circuit 704a-b to generate. Baseband signals 911 may be provided by baseband processing circuitry 708a-b and filtered by filter circuitry 912. The filter circuit 912 may comprise an LPF or a BPF, although the examples are not limited in scope in this regard.

In some examples, mixer circuit 902 and mixer circuit 914 may each include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion using synthesizer 904 . In some examples, mixer circuitry 902 and mixer circuitry 914 may each include two or more mixers that are each configured for frame suppression (e.g., Hartley frame suppression). In some examples, mixer circuit 902 and mixer circuit 914 may be configured for direct down-conversion and/or direct up-conversion. In some examples, mixer circuit 902 and mixer circuit 914 may be configured for super-heterodyne operation, although this is not required.

The mixer circuit 902 may include passive quadrature mixers (eg, for the in-phase (I) and quadrature-phase (Q) paths), according to one example. In such an example, the RF input signal 807 may be off 9 downconverted to provide I and Q baseband output signals which are sent to the baseband processor.

Passive quadrature mixers can be driven by LO switching signals varying in time by zero and ninety degrees provided by a quadrature circuit that can be set up to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as the LO frequency 905 of the synthesizer 904 ( 9 ). In some examples, the LO frequency may be the carrier frequency, while in other examples the LO frequency may be a fraction of the carrier frequency (eg, half the carrier frequency, one-third the carrier frequency). In some examples, the time varying zero and ninety degree switching signals are generated by the synthesizer, although the examples are not limited in scope in this regard.

In some examples, the LO signals may differ in duty cycle (the percentage of a period that the LO signal is high) and/or offset (the difference between the starting points of the period). In some examples, the LO signals may have an 85% duty cycle and an 80% offset. In some examples, each leg of the mixer circuit (e.g., the in-phase (I) and quadrature-phase (Q) paths) can operate with an 80% duty cycle, which can result in a significant reduction in power consumption.

The RF input signal 807 ( 8th ) may have a balanced signal, although the examples are not limited in scope in this regard. The I and Q baseband output signals can be fed to a low-noise amplifier, such as the amplifier circuit 906 ( 9 ), or a filter circuit 908 ( 9 ) are supplied.

In some examples, the output baseband signals 907 and the input baseband signals 911 may be analog baseband signals, although the examples are not limited in scope in this regard. In some alternative examples, the output baseband signals 907 and the input baseband signals 911 may be digital baseband signals. In these alternate examples, the radio IC circuit may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC).

In some dual-mode examples, a separate radio IC circuit may be provided for processing signals for each spectrum or for other spectra not mentioned here, although the examples are not limited in scope in this regard.

In some examples, synthesizer circuitry 904 may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the examples is not limited in this regard, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 904 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer having a phase-locked loop with a frequency divider. According to some examples, synthesizer circuitry 904 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuit is that while it can still have some analog components, its footprint is much smaller than the footprint of an analog synthesizer circuit. In some examples, the frequency input to synthesizer circuitry 904 may be provided by a voltage controlled oscillator (VCO), although this is not a requirement. A divider control input can still be obtained from baseband processing circuitry 708a-b ( 7 ) depending on the desired output frequency 905 can be provided. In some examples, a divider control input (eg, N) may be determined from a lookup table (eg, within a Wi-Fi card) based on a channel number and channel center frequency as determined or specified by example application processor 710 . The application processor 710 may include or be otherwise connected to one of the example backup signal converters 721 or the example receive signal converter 723 (eg, depending on which device the example radio architecture is implemented in).

In some examples, the synthesizer circuitry 904 may be configured to generate a carrier frequency as the output frequency 905, while in other examples the output frequency 905 may be a fraction of the carrier frequency (e.g., half the carrier frequency, one-third the carrier frequency). In some examples, the output frequency 905 may be a LO frequency (fLO).

10 7 shows a functional block diagram of baseband processing circuitry 708a, according to some examples. Baseband processing circuitry 708a is an example of circuitry suitable for use as baseband processing circuitry 708a ( 7 ) may be suitable, although other configurations of the circuit may be suitable. Alternatively, the example of 9 may be used to implement the example BT baseband processing circuitry 708b of FIG 7 to implement.

Baseband processing circuitry 708a may include a receive baseband processor (RX BBP) 1002 for processing receive baseband signals 909 received from radio IC circuitry 706a-b ( 7 ) are provided, and a transmit baseband processor (TX BBP) 1004 for generating transmit baseband signals 911 for the radio IC circuit 706a-b. The baseband processing circuitry 708a may also include control logic 1006 for coordinating the operations of the baseband processing circuitry 708a.

In some examples (e.g., when analog baseband signals are exchanged between baseband processing circuitry 708a-b and radio IC circuitry 706a-b), baseband processing circuitry 708a may include an ADC 1010 to convert analog baseband signals 1009 transmitted by radio IC circuitry 706a -b are received to convert to digital baseband signals for processing by the RX BBP 1002. In these examples, baseband processing circuitry 708a may also include a DAC 1012 to convert digital baseband signals from TX BBP 1004 to analog baseband signals 1011 .

In some examples that transmit OFDM signals or OFDMA signals, such as by baseband processor 708a, transmit baseband processor 1004 may be configured to generate OFDM or OFDMA signals suitable for transmission by using an inverse Fast Fourier Transform (IFFT) is performed. The receive baseband processor 1002 may be set up to process received OFDM or OFDMA signals by performing an FFT. In some examples, the receive baseband processor 1002 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing auto-correlation to detect a preamble, e.g. a short preamble, and by performing cross-correlation to detect a long preamble to recognize. The preambles may be part of a predetermined frame structure for Wi-Fi communications.

Back to 7 : In some examples, the antennas 701 ( 7 ) each have one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for the transmission of RF signals. In some MIMO (Multiple-Input-Multiple-Output) examples, the antennas can be effectively separated to take advantage of the spatial diversity and different channel characteristics that can result. The antennas 701 may each comprise a set of phased array antennas, examples are not so limited.

Although the radio architecture 700 includes several separate functional elements, one or more of the functional elements can be combined and implemented through combinations of software configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and combinations of various hardware and logic circuits to perform at least the functions described herein. In some examples, the functional elements may refer to one or more processes running on one or more processing elements.

The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Each example described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other examples. As used herein, the terms "computing device", "user device", "communication station", "station", "handheld device", "mobile device", "wireless device" and "user equipment" (UE) refer to a wireless communication device, such as a cellular phone, smartphone, tablet, netbook, wireless terminal, laptop, femtocell, high data rate (HDR) subscriber station, access point, printer, point of sale, access terminal, or other PCS Device (Personal Communication System). The device can be either mobile or stationary.

As used in this publication, the term "communicate" is intended to include sending or receiving, or both sending and receiving. This can be particularly useful in claims when describing the organization of data sent by one device and received by another, but only requiring the functionality of one of those devices to infringe the claim. Similarly, the bi-directional exchange of data between two devices (both devices send and receive during the exchange) can be described as "communicating" when only the functionality of one of those devices is claimed. The term "communicate," as used herein with respect to a wireless communication signal, includes sending the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless wireless communication unit capable of transmitting a wireless communication signal may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.

As used herein, unless otherwise noted, the use of the ordinal adjectives "first,""second,""third," etc. to describe a common object merely indicates that different instances of like objects are being referred to, and is not intended to imply , that the objects so described must be in a certain sequence, be it temporal, spatial, ranked or otherwise.

As used herein, the term "access point" (AP) may mean a fixed station. An access point may also be referred to as an access node, a base station, an evolved Node B (eNodeB), or other similar terminology known in the art. An access terminal may also be referred to as a mobile station, user equipment (UE), wireless communication device, or other similar terminology known in the art. The examples disclosed herein generally relate to wireless networks. Some examples may relate to wireless networks operating according to any of the IEEE 802.11 standards.

Some examples may be used in connection with various devices and systems, such as a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a PDA (Personal Digital Assistant) device, a PDA handheld device, an onboard device, an offboard device, a hybrid device, an in-vehicle device , a non-vehicle device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wire wireless network, wireless area network, wireless video network (WVAN), local area network (LAN), wireless LAN (WLAN), personal area network (PAN), wireless PAN (WPAN), and the like.

Some examples may be used in connection with one-way and/or two-way radio communication systems, cellular radiotelephone communication systems, a mobile telephone, a cellular telephone, a cordless telephone, a Personal Communication System (PCS) device, a PDA device that uses a wireless communication device, a mobile or handheld Global Positioning System (GPS) device, a device containing a GPS receiver or transceiver or chip, a device containing an RFID element or chip , a MIMO (Multiple Input Multiple Output) transceiver or device, a SIMO (Single Input Multiple Output) transceiver or device, a MISO (Multiple Input Single Output), a device with one or more internal antennas and/or external antennas, DVB devices or systems (Digital Video Broadcast), Multis standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.

Some examples may be used in connection with one or more types of wireless communication signals and/or systems that follow one or more wireless communication protocols, e.g. radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM ), Time Division Multiple Access (TDM), Time Division Multiple Access (TDMA), Enhanced TDMA (E-TDMA), General Packet Radio Service (GPRS), Extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000 , Single-Carrier CDMA, Multi-Carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth, Global Positioning System (GPS), Wi-Fi, WiMax, ZigBee, Ultra Wideband (UWB), Global System for Mobile Communications (GSM), 2G, 2. 5G, 3G, 3.5G, 4G, Fifth Generation Cellular Networks (5G), 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data Rates for GSM Evolution (EDGE ) or similar. Other examples may be used in various other devices, systems, and/or networks.

The following examples relate to further examples.

Example 1 may include an apparatus including processing circuitry coupled to memory, the processing circuitry configured to: determine a frame having a private MAC address associated with a connected multi-link device (MLD); encrypt the private MAC address; and cause the frame to be sent to the MLD.

Example 2 may include the device of example 1 and/or another example herein, wherein the private MAC address may be provided during a second message of a 4-way handshake.

Example 3 may include the device of Example 1 and/or any other example herein wherein the private MAC address may be set for a particular Service Set Identifier (SSID).

Example 4 may include the device of Example 1 and/or another example herein that still includes a transceiver configured to transmit and receive wireless signals.

Example 5 may include the apparatus of Example 4 and/or another example herein that still includes an antenna coupled to the transceiver to cause the frame to be transmitted.

Example 6 may include a non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors, result in the performance of operations, including: determining a frame having a private MAC address, associated with a connected Multi-Link Device (MLD); encrypting the private MAC address; and causing the frame to be sent to the MLD.

Example 7 may include the non-transitory computer-readable medium of example 6 and/or another example herein, where the private MAC address may be provided during a second message of a 4-way handshake.

Example 8 may include the non-transmittable, computer-readable medium of example 6 and/or any other example herein where the private MAC address may be set for a particular Service Set Identifier (SSID).

Example 9 may include a method comprising: determining, by one or more processors, a frame having a private MAC address associated with a connected multi-link device (MLD); encrypting the private MAC address; and causing the frame to be sent to the MLD.

Example 10 may include the method of example 9 and/or another example herein, wherein the private MAC address may be provided during a second message of a 4-way handshake.

Example 11 may include the method of Example 9 and/or any other example included herein, where the private MAC address may be set for a particular Service Set Identifier (SSID).

Example 12 may include an apparatus having means for: determining a frame having a private MAC address associated with a connected multi-link device (MLD); encrypting the private MAC address; and causing the frame to be sent to the MLD.

Example 13 may include the apparatus of example 12 and/or another example herein wherein the private MAC address may be provided during a second message of a 4-way handshake.

Example 14 may include the device of Example 12 and/or another example included herein, where the private MAC address may be set for a particular Service Set Identifier (SSID).

Example 15 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 1 -14 or refers to any of these examples, or any other method or process described herein.

Example 16 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of Examples 1-14, or any other method or process described herein .

Example 17 may include a method, technique, or process as described in or associated with any of Examples 1-14, or portions or portions thereof.

Example 18 may include an apparatus, comprising: one or more processors, and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform the method to perform the technique or process as described in or associated with any of Examples 1-14, or portions thereof.

Example 19 may include a method of communicating in a wireless network as shown and described herein.

Example 20 may include a system for providing wireless communications as shown and described herein.

Example 21 may include an apparatus for providing wireless communication as shown and described herein.

Examples according to the disclosure are disclosed in particular in the appended claims relating to a method, a storage medium, an apparatus and a computer program product, wherein each feature recited in one claim category, e.g. method, is also claimed in another claim category, e.g. system can. The dependencies or back-references in the appended claims are only chosen for formal reasons. However, any subject-matter resulting from intentional reference to earlier claims (especially multiple dependencies) may also be claimed, so that any combination of claims and their features are disclosed and can be claimed independently of the dependencies chosen in the appended claims. The claimable subject-matter has not only the combinations of features set out in the appended claims, but also any other combination of features in the claims, it being possible for any feature recited in the claims to be combined with any other feature or combination of features in the claims. Furthermore, any of the examples and features described or illustrated herein may be claimed in a separate claim and/or in any combination with any example or feature described or illustrated herein or with any of the features of the appended claims.

The foregoing description of one or more implementations has been presented for purposes of illustration and description, but is not intended to be exhaustive or to limit the scope of examples to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various examples.

Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, devices, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flowcharts, and combinations of blocks in the block diagrams and flowcharts, respectively, can be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flowcharts need not be performed in the order presented, or may not be performed at all, according to some implementations.

These computer-executable program instructions may be loaded onto a special purpose computer or other specified machine, processor or other programmable computing device to create a specified machine such that the instructions executed on the computer, processor or other programmable computing device provide means for implementing one or more functions specified in the flowchart block or blocks. These computer program instructions may also be stored on a computer-readable storage medium or memory that can instruct a computer or other programmable computing device to operate in a particular manner such that the instructions stored on the computer-readable storage medium produce an article of manufacture that contains instruction means that implement one or more functions specified in the flowchart block or blocks. As an example, certain implementations may provide a computer program product, comprising a computer-readable storage medium, in which computer-readable program code or program instructions are implemented, the computer-readable program code being adapted to be executed to implement one or more functions contained in the or the flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operational elements or steps to be executed on the computer or other programmable device to produce a computer-implemented process such that the instructions, executing on the computer or other programmable device, provide elements or steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, the blocks of the block diagrams and flowcharts support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It is also understood that each block of the block diagrams and flowcharts, and combinations of blocks in the block diagrams and flowcharts, can be implemented by specific hardware-based computer systems that perform the specified functions, elements, or steps, or combinations of specific hardware and computer instructions.

Conditional expressions, such as "may", "could", "could", or "may", unless expressly stated otherwise or understood otherwise in the context used, are generally intended to convey that certain implementations have certain characteristics, elements and/or operations, while other implementations do not. Therefore, such conditional language is generally not intended to imply that features, elements, and/or operations are in any way required by one or more implementations, or that one or more implementations necessarily have logic to decide with or without user input or prompting whether those features, elements, and/or operations are included or intended to be performed in a particular implementation.

Many modifications and other implementations of the disclosure set forth herein will become apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• US63/161160 [0001]

Claims (10)

A circuit set up: receive a frame from a Wi-Fi device, the frame including an encrypted private identifier; decrypt the encrypted private identifier; and identify the other Wi-Fi device based on the decrypted private identifier. The circuit after Claim 1 , wherein the Wi-Fi device is a multi-link device or station (STA). The circuit after one of patent claims 1 and 2 , wherein the private identifier is a private MAC address of the Wi-Fi device; and the private MAC address is different from a public MAC address of the Wi-Fi device, the public MAC address being provided over the air. The circuit after one of patent claims 1 until 3 further configured to identify the Wi-Fi device to higher layers of a Wi-Fi protocol based on the private identifier; and/or wherein the frame is part of a second message of a four-way handshake between the Wi-Fi device and an encrypted management frame. The circuit after one of patent claims 1 until 4 further configured to indicate to the Wi-Fi device that the private identifier is required or supported; and/or wherein the indication that a private identifier is required or supported is provided as a robust safety net extension element. The circuit after one of patent claims 1 until 5 wherein the Wi-Fi device propagates the same private identifier to an IEEE 802.11 communications terminal device associated with a Service Set Identifier (SSID). An IEEE 802.11 communications terminal apparatus, the apparatus comprising: a radio frequency (RF) interface; and the circuit according to one of the patent claims 1 until 6 , the circuit being coupled to the RF interface. A circuit set up: generate a private identifier; generate a frame configured for a receiving Wi-Fi device; have the private identifier in the frame; and to encrypt the frame. The circuit after patent claim 8 , where the private identifier is a MAC address; and/or wherein the private identifier is present in a key data encapsulation (KDE) in an EAPOL-KeyData field of an EAPOL-Key frame; and/or wherein the circuitry is further configured to identify the receiving Wi-Fi device based on a service set identifier of the receiving Wi-Fi device, wherein the private identifier used to communicate with the receiving Wi-Fi device is based on the SSID of the receiving Wi-Fi device based; and/or wherein the circuitry is further arranged to indicate support for the private identifier. A device of an IEEE 802.11 communication terminal, the device comprising a radio frequency (RF) interface; and the circuit after one of the patent claims 8 or 9 , the circuit being coupled to the RF interface.

Images