Address randomization scheme

Abstract

The present disclosure provides an address randomization scheme. Implementations of address change schemes for use in wireless communication systems are disclosed. Some implementations include an access point (AP) that can establish two or more address profiles with a station (STA), establish a schedule for switching from a first address profile to a second address profile, where the first address profile and the second address profile belong to the two or more address profiles, and transmit a first data transmission using the first address profile. Some implementations include switching from the first address profile to the second address profile based on the schedule, and transmitting a second data transmission using the second address profile. The schedule can be based on a random time synchronization function (TSF). The AP can establish a joint algorithm with the STA, and determine the first address profile and the second address profile and a transition time of the schedule using the joint algorithm.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 243,682, filed September 13, 2021, entitled “Address Randomization Schemes,” the disclosure of which is incorporated by reference herein in its entirety. BACKGROUND TECHNICAL FIELD

[0004] Embodiments generally relate to improving privacy of wireless devices communicating with each other in a wireless communication system. SUMMARY

[0005] Some embodiments include apparatuses, methods, and computer program products for address randomization schemes for devices in a wireless communication system, such as a wireless LAN (WLAN) system. Access points (APs) and stations (STAs) can implement address randomization schemes that allow for communication such that a bad actor cannot easily track or detect a device address. Some embodiments include an AP that can establish two or more address profiles with a STA, establish a schedule for switching from a first address profile to a second address profile, and transmit a first data transmission using the first address profile. The AP can switch from the first address profile to the second address profile based on the schedule and transmit a second data transmission using the second address profile. The schedule for switching from the first address profile to the second address profile can be based on a random time synchronization function (TSF) parameter.

[0006] The AP can establish a new address profile with the STA and a first time at which the new address profile is available for use. The AP can also establish a second time at which the AP begins operating on a different channel and, after the first time and the second time, transmit a second data transmission on the different channel using a third address profile of the new address profile. The AP can determine an end time of the new address profile, where the third address profile is randomly selected from the new address profile before the end time.

[0007] In some embodiments, the AP can encrypt an aggregated media access control (MAC) service data unit (A-MSDU) and, after encryption, create an over-the-air (OTA) packet number (PN OTA ) that is different from a packet number (PN OTA ) corresponding to the A-MSDU, where the first data transmission includes the PN Offset , and where the PN OTA = PN + PN OffsetFurthermore, after encryption, the AP can create an OTA sequence number (SN) that is different from the sequence number (SN) corresponding to the A-MSDU. OTA The first data transmission includes SN. OTA The first address profile includes the offset SN (SN Offset ), and among them SN OTA =SN+SN Offset After encryption, the AP can apply the AP identifier from the first address profile, where the first data transmission includes the first AP identifier transmitted via OTA.

[0008] To establish two or more address profiles, the AP can establish a joint algorithm with the STA and use the joint algorithm to determine the first and second address profiles and the scheduled transition times. To establish the joint algorithm, the AP can receive a single address setting algorithm, a MAC address seed, and a proposed average duration for address setting from the STA. In response, the AP can transmit a single address setting start time seed, a single address setting end time seed, a grouped address algorithm, and an AP MAC address seed.

[0009] In some implementations, the AP can receive a notification of a conflicting MAC address from the STA. This notification includes: the conflicting MAC address, the STA's proposed new MAC address, the time the proposed new MAC address is currently in use, or the AP's proposed new MAC address. The AP can then transmit an acknowledgment message to the STA corresponding to the notification.

[0010] In some implementations, the STA can establish two or more address profiles with the AP, establish a schedule for switching from a first address profile to a second address profile, and receive a first data transmission including a first receive address (RA) corresponding to the first address profile. The STA can transmit a block acknowledgment (BA) corresponding to the received first data transmission. The STA can switch from the first address profile to the second address profile based on the schedule and receive a second data transmission including a second RA corresponding to the second address profile, wherein the first RA is different from the second RA. The STA can establish a new address profile with the AP and establish a first time when the new address profile becomes available. The STA can establish a second time when the AP begins operating on different channels, and after the first and second times, transmit the second data transmission on different channels using a third address profile of the new address profile. The STA can determine an end time for the new address profile, wherein a third address profile is randomly selected from the new address profiles before the end time.

[0011] In some implementations, the STA can use the over-the-air (OTA) packet number (PN) of the first data transmission. OTA ) and the offset PN of the first address profileOffset Determine the packet number (PN) and use the sequence number (SN) of the first data transmission over time (OTA). OTA ) and the offset SN of the first address profile Offset The sequence number (SN) is determined, where PN and SN correspond to the encrypted aggregated MAC service data unit (A-MSDU) of the first data transmission. This determination can be based on the following equation: PN = PN OTA -PN Offset And SN = SN OTA -SN Offset The STA can sort the frames of the first data transmission according to the SN and decrypt the encrypted A-MSDU. In some implementations, the STA can establish a joint algorithm with the AP, where the joint algorithm is used to establish the first address profile and the second address profile, as well as the scheduling transition time. Attached Figure Description

[0012] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate the disclosed contents and, together with the specification, further serve to explain the principles of this disclosure and enable those skilled in the art to make and use it.

[0013] Figure 1 An exemplary system of an address randomization scheme according to some embodiments of the present disclosure is shown.

[0014] Figure 2 A block diagram of an exemplary wireless system supporting address randomization schemes according to some embodiments of the present disclosure is shown.

[0015] Figure 3A An example of a hidden access point (AP) system is shown.

[0016] Figure 3B An example of hiding AP operations is shown.

[0017] Figure 4A Examples of systems with random single address settings according to some embodiments of this disclosure are shown.

[0018] Figure 4B An example of scheduling a random single address setting according to some embodiments of this disclosure is shown.

[0019] Figure 5A Examples of systems with randomized grouped address settings according to some embodiments of this disclosure are shown.

[0020] Figure 5B An example of a scheduling method including randomized grouped address settings for channel switching according to some embodiments of this disclosure is shown.

[0021] Figure 6 An exemplary method for receiving a Physical Layer Protocol Data Unit (PPDU) including a random single address setting, according to some embodiments of the present disclosure, is shown.

[0022] Figure 7 Examples of group address setting randomized timing synchronization functions (TSFs) according to some embodiments of this disclosure are shown.

[0023] Figure 8 Examples of signaling for configuring random address settings according to some embodiments of this disclosure are shown.

[0024] Figure 9 Examples of signaling for updating random address settings according to some embodiments of this disclosure are shown.

[0025] Figure 10 Examples of signaling for configuring a joint algorithm for determining random address settings according to some embodiments of this disclosure are shown.

[0026] Figure 11 Examples of signaling for Media Access Control (MAC) address conflict detection and avoidance according to some embodiments of this disclosure are shown.

[0027] Figure 12 Exemplary methods for data transmission using random address settings are shown according to some embodiments of the present disclosure.

[0028] Figure 13A A diagram showing data delivered to Galois / Counter Mode (GCM) encryption is shown.

[0029] Figure 13B An example of an encryption block diagram supporting random address settings is shown according to some embodiments of this disclosure.

[0030] Figure 14A An example of an extended Galois / Counter Mode (GCM) protocol (GCMP) MAC protocol data unit (MPDU) is shown.

[0031] Figure 14B An example of Additional Authentication Data (AAD) for Protocol Version 0 (PV0) MPDU is shown.

[0032] Figure 15 An exemplary privacy-enhanced (PE) multi-link device (MLD) system supporting address randomization schemes according to some embodiments of this disclosure is shown.

[0033] Figure 16An exemplary PEMLD system including address and identifier randomization is shown according to some embodiments of the present disclosure.

[0034] Figure 17 Examples of several MLD address types for address randomization according to some embodiments of this disclosure are shown.

[0035] Figure 18A Examples of data transfer supporting PE MLD random addresses according to some embodiments of this disclosure are shown.

[0036] Figure 18B An exemplary MPDU, comprising a portion of an aggregated MPDU (A-MPDU) subframe including an encrypted MLD address, is shown according to some embodiments of this disclosure.

[0037] Figure 18C The basic A-MAC Service Data Unit (A-MSDU) subframe structure is shown.

[0038] Figure 19 Examples of modifications to the air (OTA) MLD MAC address for PPDUs used in group addressing are shown according to some embodiments of this disclosure.

[0039] Figure 20 Examples of signaling for configuring a joint algorithm according to some embodiments of the present disclosure are shown, which determines the address settings of the MLD and signaling for address conflict notification.

[0040] Figure 21 Exemplary methods for data transfer between PE MLDs according to some embodiments of this disclosure are shown.

[0041] Figure 22A A diagram showing the data delivered to Galois / Counter Mode (GCM) for decryption is shown.

[0042] Figure 22B An example of a decryption block diagram supporting random address settings is shown according to some embodiments of this disclosure.

[0043] Figure 23 It is an exemplary computer system for implementing some implementation schemes or one or more parts of an implementation scheme.

[0044] This disclosure is described with reference to the accompanying drawings. In the drawings, the same reference numerals generally indicate the same or similarly functional elements. Furthermore, the leftmost numeral of the reference numerals generally appears first in the drawings. Detailed Implementation

[0045] Some implementations include address randomization schemes for devices including multi-link devices (MLDs) in wireless communication systems. These schemes prevent malicious actors from tracking, tracing, and / or detecting the Media Access Control (MAC) addresses of access points (APs), stations (STAs), privacy-enhanced (PE) AP MLDs, and PE non-AP MLDs. Because MAC addresses are not easily traced and / or tracked, the security of wireless communication between devices is improved.

[0046] Figure 3A Example 300 of a hidden AP system, which may include an AP in a vehicle or a mobile AP, is shown. Example 300 includes a hidden AP 305, STA1 315, and STA2 325. When the hidden AP 305 begins operation, AP 305 can be randomly configured with parameters that are static for a short operating duration. For example, AP 305 can transmit group transmissions 335a and 335b to STA1 315 and STA2 325, or transmit a single transmission 345 to STA2 325. During the short operating duration, MAC addresses X, Y, and Z are used until the short operating duration ends. When AP 305 begins operation again, different random parameters are used, and different MAC address X, Y, and Z values ​​are used, which remain static for the short operating duration. By using random parameters for the short operating duration, it may be difficult to identify devices using changed MAC addresses.

[0047] Figure 3B Example 350 of hidden AP operation is shown. Example 350 includes three short-duration operations. At the beginning of the first operation 360, AP1 may randomly set the MAC address and parameters to be used for the duration of the operation ending at 365. At the beginning of the second operation 370, AP2 (which is essentially a different AP) randomly sets the MAC address and parameters and begins operation until the duration ends at 375. At the beginning of the third operation 380, AP3 (yet another different AP) randomly sets the MAC address and parameters and begins operation until the duration ends at 385. While randomized addresses and parameters provide a security metric, the hidden AP method is impractical for operation in wireless communication systems with longer operation durations, including but not limited to Wi-Fi as described in IEEE P802.11REVme_D0.0 (Information Technology Standards Draft—Information Exchange between Telecommunication and System LANs and Metropolitan Area Networks—Specific Requirements Part 11: Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification "IEEE P802.11REVme").

[0048] Figure 1An exemplary system 100 is shown, illustrating an address randomization scheme according to some embodiments of the present disclosure. System 100 includes a privacy-enhanced (PE) AP multi-link device (MLD) 110 providing access to network 150 for PE non-AP MLD 120 and STA 130. System 100 also includes an AP 160 (e.g., a single-link device) providing access to network 150 for STA 180 and STA 170 (e.g., a single-link device). PE AP MLD 110 may include attached PE APs (e.g., PE APs 110a-110c), and PE non-AP MLD 120 may include attached PE non-AP STAs (e.g., PE non-AP STAs 120a-120c) communicating via multiple links: link 1 105, link 2 107, and link 3 109. PE devices other than AP MLD 120, STA 130, STA 180, and STA 170 can be electronic devices including, but not limited to, cellular phones, smartphones, tablets, personal digital assistants (PDAs), or laptops. Network 150 can be, but not limited to, any one or any combination of a local area network (LAN), a metropolitan area network (MAN), a wireless local area network (WLAN), and / or the Internet. STA 130, which is not an AP MLD 120 or is adjacent to AP MLD 110, can be associated with AP MLD 110. STA 180 and STA 170, which are adjacent to AP 160, can be associated with AP 160.

[0049] In some implementations, AP 160 can establish multiple address profiles with STA 180 and multiple different address profiles with STA 170, establish scheduling for switching from one address profile to another, and transmit data using the currently used address profile. In some implementations, the MLD device can include two types of address randomization schemes: one at the MLD address level and the other at a link-specific address level. PE AP MLD 110 and PE non-AP MLD 120 can randomly set the MLD address and MLD level parameters such that the MLD address and MLD level parameters are not transmitted unencrypted over the air. For each link used by PE AP MLD 110 and PE non-AP MLD 120 (e.g., link 1105, link 2 107, and link 3 109), the randomized MLD address and MLD level parameters can be different. Additionally, the associated PE AP (e.g., PE AP 110a) of PE AP MLD110 can establish multiple link-specific address profiles with STA 130, and establish multiple address profiles with the associated PE non-AP STA (e.g., PE non-AP STA 120a) of PE non-AP MLD 120, establish a schedule for switching from one address profile to another, and transmit data using the address profile currently in use.

[0050] Figure 2 A block diagram of an exemplary wireless system supporting address randomization schemes according to some embodiments of this disclosure is shown. Reference may be made for illustrative purposes and not for limiting purposes. Figure 1 To describe the elements Figure 2For example, system 200 can be any electronic device of system 100 (e.g., AP 160, PE AP MLD 110, PE AP 110a-110c, PE non-AP MLD 120, PE non-AP STA 120-120c, STA 130, STA 180, and STA 170). System 200 includes one or more processors 265, transceiver 270, communication interface 275, communication infrastructure 280, memory 285, and antenna 290. Memory 285 may include random access memory (RAM) and / or cache, and may include control logic (e.g., computer instructions) and / or data. One or more processors 265 can execute instructions stored in memory 285 to perform operations that enable wireless system 200 to transmit and receive wireless communications, including functions for implementing the address randomization scheme described herein. In some embodiments, one or more processors 265 may be "hard-coded" to perform these functions described herein. According to some embodiments, transceiver 270 transmits and receives wireless communication signals, including wireless communication supporting address randomization schemes, and may be coupled to one or more antennas 290 (e.g., 290a, 290b). In some embodiments, transceiver 270a (not shown) may be coupled to antenna 290a, and different transceivers 270b (not shown) may be coupled to antenna 290b. Communication interface 275 allows system 200 to communicate with other devices, which may be wired and / or wireless. Communication infrastructure 280 may be a bus. Antenna 290 may include one or more antennas that may be the same or different types.

[0051] To enhance the privacy and security of wireless communications and the traceability of MAC addresses, some implementations include single (also referred to herein as unicast) address settings and group (also referred to herein as multicast) address settings, which include addresses and parameters that change continuously but at different (e.g., random) times. Frequent changes avoid significant one-off changes that can be traced. Single address setting data used to transmit to / from an AP (e.g., AP 160) and associated STAs (e.g., STA 180 or STA 170) should be known only to the AP and associated STAs (e.g., between AP 160 and STA 180, and between AP 160 and STA 170). Single address setting changes and availability are scheduled only between the AP and associated STAs. Group address settings used by the AP (e.g., AP 160) should be known to all associated STAs (e.g., STA 180 and STA 170). The AP (e.g., AP 160) can schedule the group address settings in use for all associated STAs (e.g., STA 180 and STA 170). Individual addresses in a single address setting and group addresses in a group address setting are scheduled and can be changed based on random time synchronization function (TSF) parameter values ​​(e.g., time).

[0052] Referring to the MLD example, a single link-specific address used for transmission on link 1 105 to / from a PE AP (e.g., PE AP 110a) and associated STAs (e.g., STA 130 or PE non-AP STA 120a) should be known only to the AP and associated STAs. Changes to individual addresses and their availability are scheduled only between the AP and associated STAs. In the MLD example, grouped addresses used by the PE AP (e.g., PE AP 110a) should be known to all associated STAs (e.g., STA 130 and PE non-AP STA 120a). The PE AP (e.g., PE AP 110a) can schedule the grouped addresses in use for all associated STAs (e.g., STA 130 and PE non-AP STA 120a). The use of individual and grouped addresses is scheduled and can change based on random MLD level time synchronization function (TSF) parameter values ​​(e.g., time).

[0053] Figure 4A An exemplary system 400 with a random single address setting according to some embodiments of this disclosure is shown. Reference may be made for illustrative purposes and not for limiting purposes. Figure 1 To describe the elements Figure 4A For example, AP 410 can be one of AP160 or PE AP 110a-110c, and the associated STA 420 can be... Figure 1One of STA 130, STA 180, STA170 or PE non-AP STA 120a-120c.

[0054] AP 410 includes a single address configuration profile 418. In system 400, six single address configuration profiles (also referred to herein as single address profiles) are shown as: single address profiles 411-416. The associated STA 420 includes a single address configuration profile 430, which includes six single address profiles 431-436 corresponding to the single address profiles 411-416 of AP 410, respectively.

[0055] Table 1 below shows a brief profile of a single address setting. Single Address Setting.

[0056] Table 1: Individual address settings

[0057]

[0058]

[0059] A single address setting (e.g., one of 411-416) defines the address and identifier used for individual addressing transmissions between AP 410 and associated STA 420. In some embodiments, the address and identifier are known only to AP 410 and associated STA 420 to provide address privacy. In system 400, AP 410 and associated STA 420 establish six single address settings 411-416 for communication. In some embodiments (not shown), AP 410 may be configured with different single address setting profiles (e.g., 411-416) with different associated STAs (e.g., STA 420 may include single address settings 411-414, while different STAs (not shown) may be configured to have single address settings 415-416).

[0060] Some implementation schemes include features and operations for address randomization, as shown in Table 2. Rules are used for APs and STAs employing address randomization.

[0061] Table 2: Rules for AP and STAs using address randomization

[0062]

[0063] These mechanisms are described in Table 3 below. The recommendations for improving privacy help to keep AP 410 and associated STA 420 more private and prevent the tracking of associated STA 420 and AP 410.

[0064] Table 3: Recommendations for improving privacy

[0065]

[0066] In some implementations, the AP / Basic Service Set (BSS) identifier and the corresponding BSSID are used. unicast The color field value is known to all associated STAs, but the remaining information in Table 1, configured for a single address between associated STA 420 and AP 410, is known only to associated STA 420 and AP 410. When the AP / BSS identifier is known to all associated STAs, the associated STAs can detect whether the associated AP is transmitting or receiving collision-preventable data. STAs can utilize space reuse and have more simultaneous transmissions. This implementation can be useful when AP 410 has only a few associated STAs or when AP 410 and STA 420 are far apart.

[0067] In some implementations, a single address used in transmissions to / from AP 410 and associated STA 420 should be known only to AP 410 and associated STA 420. Individual address changes and availability are only scheduled between AP 410 and associated STA 420.

[0068] Figure 4B Example 450 of a scheduling random single address setting according to some embodiments of this disclosure is shown. Reference may be made for illustrative purposes and not for limiting purposes. Figure 4A To describe the elements Figure 4B In Example 450, AP 410 and associated STA 420 can be configured and established on single address settings 411-416 (and corresponding single address settings 431-436) that change randomly over time and are known only to AP 410 and STA 420. Example 450 illustrates the configuration and use of various single address settings on the timeline of Link X, where in the MLD case Link X may correspond to Link 1 105, Link 2 107, or Link 3 109.

[0069] At 460, multiple address settings can be negotiated. For example, associated STA 420 and AP 410 can be configured and three address settings can be established: single address settings 411 (431), 412 (432), and 413 (433) used between time 460 and time 480.

[0070] After configuration and up to time 465, a single address setting 411 (431) can be used to communicate between AP 410 and STA 420 (e.g., uplink and / or downlink communication).

[0071] Between time 465 and time 470, a single address setting 412 (432) can be used to communicate between AP 410 and STA 420.

[0072] Between time 470 and time 480, a single address setting 413 (433) can be used to communicate between AP 410 and STA 420.

[0073] At 480, new individual address settings can be configured (e.g., individual address settings 413 (433), 414 (434), and 415 (435). In some implementations, one or more individual address settings may be used at a time. For example, between 480 and 485, the associated STA 420 and AP 410 may randomly select one of individual address settings 413 (433), 414 (434), and 415 (435) for frame transmission. Having multiple individual address profiles available for communication between AP 410 and associated STA 420 is different. Figure 3B Example 350 of the hidden AP, in which only a single static address setting is available for short-duration operation.

[0074] At 485, new individual address settings can be configured (e.g., individual address settings 415 (435) and 416 (436)). After 485, the associated STA 420 and AP 410 can randomly select one of the individual address settings 415 (435) and 416 (436) for frame transmission.

[0075] Figure 6 An exemplary method 600 for receiving a Physical Layer Protocol Data Unit (PPDU) including a random single address setting, according to some embodiments of the present disclosure, is illustrated. FIG600 may be described with reference to elements of other figures in the present disclosure for illustrative purposes and not for limiting purposes. For example, method 600 may be composed of... Figure 4A AP 410 communication Figure 4AThe associated STA 420 performs this operation. In method 600, the single address configuration profile, including the AP / BSS identifier, is known only to AP 410 and the associated STA 420. In other words, the associated STA 420 is unaware of the AP / BSS identifier (and corresponding address and parameters) in other single address configurations (e.g., configuration 7 of another associated STA, not shown). In some implementations, the color field value can be configured for the AP / BSS identifier, or the color field value can be set to a random value between 0 and 63. In some examples, AP 410 uses a color value to transmit downlink frames to STAs (e.g., STAs 130, 170, 180). In some examples, AP 410 can use the legacy Physical Layer Protocol Data Unit (PPDU) format in transmissions to legacy STAs. As shown below, in method 600, STA 420 receives at least one MAC header from the PPDU.

[0076] At position 605, STA 420 receives the preamble and detects the PPDU duration.

[0077] At position 610, STA 420 receives the MAC header and proceeds to position 615 to apply the receive rules.

[0078] At 615, STA 420 determines whether a payload has been received. If no payload has been received, method 600 proceeds to 620. Otherwise, method 600 proceeds to 625.

[0079] At 620, when no payload is received, STA 420 can set the channel to busy for the duration of the PPDU.

[0080] At 625, STA 420 determines whether the BSSID is within a co-managed BSS or multiple BSSIDs. If the BSSID is not within a co-managed BSS or multiple BSSIDs (e.g., the detected BSSID does not match the BSSID corresponding to a single address setting currently in use), method 600 proceeds to 630. Otherwise, method 600 proceeds to 635.

[0081] At 630, STA 420 sets up the regular network allocation vector (NAV) (e.g., the transmission is not initiated by STA 420).

[0082] At 635, STA 420 determines whether the Receive Address (RA) is equal to the STA 420's MAC address (e.g., the STA link address set by a single address in use). unicast If RA equals the MAC address of STA 420, proceed from method 600 to 645. Otherwise, proceed from method 600 to 640.

[0083] At position 645, STA 420 receives the payload of the detected PPDU.

[0084] Returning to 640, when RA is not equal to the MAC address of STA 420, STA 420 can stop receiving and enter the power saving mode within the PPDU.

[0085] Figure 5A An exemplary system 500 with a randomized grouped address configuration is shown according to some embodiments of this disclosure. Reference may be made for illustrative purposes and not for limiting purposes. Figure 1 To describe the elements Figure 5A For example, AP 510 can be one of AP160 or PE AP 110a-110c, and associated STA 520a, 520b can be... Figure 1 One of STA 130, STA180, STA 170 or PE non-AP STA 120a-120c.

[0086] AP 510 defines group address settings parameters and the number of configured address settings 511-516. All group address settings are configured for all associated STAs 520a and 520b. AP 510 includes a group address setting profile 518. In system 500, six group address settings (also referred to herein as group address profiles) are shown as: group address profiles 511-516. Associated STAs 520a and 520b include group address setting profiles 518a and 518b, which include corresponding group address profiles 511a-516a and 511b-516b, respectively, corresponding to group address profiles 511-516 of AP 510. In some implementations, group address setting profiles 511-516 are substantially identical to group address profiles 511a-516a and 511b-516b.

[0087] The group address configuration profile is shown in Table 4 below. Group Address Configuration.

[0088] Table 4: Grouped address settings

[0089]

[0090] The group address configuration profile is used to send grouped data frames, grouped control frames, and grouped management frames to all associated STAs 520a and 520b. The group address configuration is known to all associated STAs 520a and 520b. Associated STAs 520a and 520b can receive grouped frames and know which BSS-specific parameter values ​​they can expect. The group address configuration configures upcoming BSS parameter changes, including but not limited to TSF offsets and changes in sequence numbers.

[0091] Figure 5B Example 550 illustrates a scheduling method including randomized grouped address settings for channel switching according to some embodiments of this disclosure. Reference may be made for illustrative purposes and not for limiting purposes. Figure 5A To describe the elements Figure 5B In Example 550, AP 510 and associated STAs 520a and 520b can be configured and established with grouped address settings 511-516 (and corresponding individual address settings 531a-536a and 531b-536b) that change at random times. (Even though Example 550 may appear to be periodic, the time between changes can vary, for example, between 565, 570, and 575.) Example 550 illustrates the configuration and use of various individual address settings on the timeline of Link X, where, in the MLD case, Link X could correspond to Link 1 105, Link 2 107, or Link 3 109. In Example 550, one grouped address setting is used at a time.

[0092] At 555, multiple address settings can be negotiated. For example, AP 510, associated STA 520a, and associated STA 520b can be configured and established with three address settings for use at different times between time 555 and time 570: group address settings 511 (511a, 511b), 512 (512a, 512b), and 513 (513a, 513b).

[0093] After configuration and up to time 560, group address settings 511 (511a, 511b) can be used to communicate from AP510 to STA 520a, 520b.

[0094] Between time 560 and time 565, group address settings 512 (512a, 512b) can be used to communicate from AP 510 to STA 520a, 520b.

[0095] Between time 565 and time 570, group address settings 513 (513a, 513b) can be used to communicate from AP 510 to STA 520a, 520b.

[0096] At 570, a new grouped address setting is configured for operation during certain time periods. For example, grouped address setting 513 (513a, 513b) is used between time 570 and time 575, grouped address setting 514 (514a, 514b) is used between time 575 and time 580, and 515 (515a, 515b) is used after time 580.

[0097] In some implementations, AP 510 may also establish with STA 520 the time at which AP 510 begins operation on a different channel marked at 590 (e.g., 575). Therefore, AP 510 begins operation on a different channel except at time 575 when it changes to use group address settings 514 (514a, 514b). Consequently, STAs 520a and 520b essentially tune to this different channel at time 575 to receive group address communication according to the group address settings 514 (514a, 514b) on that different channel. Subsequent reception can remain on this different channel until AP 510 updates the scheduling and / or operation channel.

[0098] Figure 7 Example 700 of a grouped address setting randomized timing synchronization function (TSF) according to some embodiments of the present disclosure is shown. For illustrative purposes and not for limiting purposes, elements of other figures in this disclosure may be referenced for description. Figure 7 For example, Example 700 can be derived from... Figure 5A AP 520 execution.

[0099] In some implementations, when TSF = 0, AP 510 transmits a Delivery Service Indication Message (DTIM) beacon frame at 710a. After AP 510 transmits a buffered group-addressed frame for the DTIM beacon, AP 510 transmits DTIM beacon frames at 710b and 710c. The beacon frames may have a fixed transmission interval (e.g., 100 ms), and the Target Beacon Transmission Time (TBTT) occurs over a TSF time that is a multiple of the beacon interval. See Table 4 above. The group address setting may include random BSS parameters, including a TSF offset. In other words, at 720, the group address setting can be changed and the TSF time can be changed. When the TSF time changes, the beacon frame transmission time can be changed accordingly to 730a. In some implementations, the beacon frame is transmitted when TSF (Mod Beacon Transmission Interval) = 0. Power saving requires the STA to know the AP group address setting and its individual address settings so that the STA can receive the beacon frame.

[0100] In some examples, a DTIM beacon is transmitted every X (X=4) beacon. The DTIM interval can be varied during grouping parameter randomization. Following the grouping address setting and TSF change at time 720, a DTIM beacon occurs at 730b, followed by a TIM beacon at 730c. In some implementations, a new grouping address setting can be transmitted every Y DTIM beacon (e.g., every 3rd DTIM beacon). The STA can obtain the grouping address setting using unicast request / response signaling. Buffered grouped data frames transmitted after the DTIM beacon should use the same grouping address setting.

[0101] Figure 8 Example 800 of signaling for configuring random address settings according to some embodiments of this disclosure is shown. For illustrative purposes and not for limitation, elements of other figures in this disclosure may be referenced for description. Figure 8 For example, AP810 could be Figure 1 One of AP 160 or PE AP 110a-110c, and STA 820 can be Figure 1 One of STA 130, STA 180, STA 170, or PE non-AP STA 120a-120c. Group address settings and individual address settings can operate in different schedules, and they can be configured to be used during association as shown in Example 800. Association can configure the exact parameters of individual and multicast address settings. This mechanism can include updating frames to update new individual and / or group address settings before the old individual and / or group address settings expire. Association signals configure unicast and multicast address settings. The first unicast address setting can be used immediately after association.

[0102] At 830, AP 810 can transmit a beacon frame that signals support for a minimum number of single address settings in address randomization and association. The beacon frame may include a Robust Secure Network (RSN) element (RSNE) that includes indications of: Pre-Association Security Negotiation (PASN) protocol, Fast Basic Services Set (BSS) Transition (FT), Authentication and Key Management (AKM), Robust Secure Network Extension Element (RSNXE), Mobility Domain Element (MDE), and / or support for address randomization.

[0103] At point 840, authentication occurs between STA 820 and AP 810. Authentication may include PASN encryption settings, or PASN encryption may be configured between STA 820 and AP 810 prior to authentication. The authentication request includes the STA 820 associated and authenticated MAC addresses. The authentication response includes the AP 810 associated and authenticated MAC addresses.

[0104] At 850, the STA 820 transmits a PASN-protected association request, which proposes one or more individual address settings and other association parameters. Individual address settings may include: the STA MAC address, an uplink (UL) sequence number (SN) offset (e.g., a separate SN offset for a service identifier (TID)-specific SN), an UL packet number (PN) offset, and the start and end times of the proposed individual address settings. Other association parameters may include the STA's PHY and MAC capabilities.

[0105] The association request frame may also contain the MAC-SAP MAC address of the STA 820, which is used by the STA 820 in frame encryption, and the frame may include the MAC address of the STA 820 used for authentication and association. Similarly, the association response may contain the MAC-SAP MAC address of the AP 810, which is used by the AP 810 in frame encryption, and the frame may include the MAC address of the AP 810 used for authentication and association.

[0106] At 860, AP 810 can transmit a PASN-protected association response, which includes a success (or failure) indication, one or more individual address settings, one or more group address settings, and other association parameters. For example, an individual address setting may include: the corresponding AP MAC address (e.g., BSSID). unicast The associated ID (AID) value, color field value, downlink (DL) SN offset (e.g., SN offset of STA-specific and TID-specific SNs), DL single PN offset, and scheduling of single address settings.

[0107] The AP 810 configures multicast address settings, defining all parameters and scheduling in the association response. For example, the association response may include group address settings, which include: AP MAC address, DL SN offset, DL group PN offset, TSF offset, change sequence counter value, and / or group address setting start and end times. After the multicast address settings are configured, the STA can receive grouped frames.

[0108] Figure 9 Example 900 of signaling for updating random address settings according to some embodiments of this disclosure is shown. For illustrative purposes and not for limitation, elements of other figures in this disclosure may be referenced for description. Figure 9 For example, AP910 could be Figure 1 One of AP 160 or PE AP 110a-110c, and STA 920 can be Figure 1 One of STA 130, STA 180, STA 170 or PE non-AP STA 120a-120c.

[0109] New signaling messages can be used to update individual and / or group address settings. The same signaling can configure multiple individual (e.g., unicast) and group (e.g., multicast) address settings. Address settings should be updated before they expire. AP 910 or STA 920 can initiate address setting updates. AP 910 can send an unsolicited address setting response frame to provide group address setting parameters and AP 910 parameters for individual address settings.

[0110] In some implementations, AP 910 and STA 920 can be configured to restore a single address setting. The restore address setting is used only when all unicast address settings have expired (e.g., STA 920 may be operating in a long-term power-saving mode and not receiving address setting updates). After a transmission with the restore address setting, AP 910 or STA 920 should update its address setting and the restore address setting. In some implementations, simple devices, including IoT devices, may only have the restore address setting that is currently in use (e.g., the restore address setting is used for the next burst of the transmission frame).

[0111] Example 900 illustrates the signaling used to update random address settings.

[0112] At 930, STA 920 is associated with AP 910 and the individual and multicast address settings are updated.

[0113] At 940, the STA 920 can transmit a robust MGMT frame that includes an address setting update request, which comprises one or more individual address settings. The corresponding parameters for the updated individual address settings may include: the STA 920 MAC address, the UL SN offset (e.g., the SN offset of a TID-specific SN), the UL individual PN offset, and / or the proposed start and end times for the individual address setting.

[0114] At 950, the AP 910 can transmit a robust MGMT frame including an address setting update response, which includes one or more individual address settings and / or one or more group address settings. The updated individual address settings may include: the AP 910 MAC address, AID, color field value, DL SN offset (e.g., SN offsets for STA-specific and TID-specific SNs), a single PN offset, and / or the corresponding individual address setting start and end times. The updated group address settings may include: the AP 910 MAC address, DL group SN offset, DL group PN offset, TFS offset, a changed sequence counter value, and / or the group address setting start and end times.

[0115] Figure 10Example 1000 of signaling for configuring a joint algorithm for determining random address settings according to some embodiments of the present disclosure is shown. For illustrative purposes and not for limitation, elements of other figures in this disclosure may be referenced for description. Figure 10 For example, AP 1010 could be... Figure 1 One of AP 160 or PE AP 110a-110c, and STA 1020 can be Figure 1 One of STA 130, STA 180, STA 170 or PE non-AP STA 120a-120c.

[0116] Association can be configured with a joint algorithm to update address setting parameters during association. In association signaling, AP 1010 and STA 1020 can agree on a set of joint algorithms to calculate individual and group address settings. The algorithm can also be configured with address setting transition times and the number of address settings currently in use. An associated AP (e.g., AP 1010) can change the algorithm or parameter values ​​used for address settings. For example, if an STA is not associated with a BSS, a change in the multicast address setting algorithm ensures that only the associated STA (e.g., STA 1020) knows the AP's next address. Alternatively, AP 1010 can maintain an algorithm for group address settings, allowing STAs reassociating with AP 1010 to calculate current AP parameters and discover AP 1010.

[0117] The association request frame may also contain the MAC-SAP MAC address of STA 1020, which STA 1020 uses in frame encryption, and the frame may include the MAC address of STA 1020 for authentication and association. Similarly, the association response may contain the MAC-SAP MAC address of AP 1010, which AP 1010 uses in frame encryption, and the frame may include the MAC address of AP 1010 for authentication and association.

[0118] At 1030, AP 1010 can transmit a beacon frame that signals support for a minimum number of single address settings in address randomization and association. The beacon frame may include RSNE, which includes indications of PASN protocol, FT, AKM, RSNXE, MDE, and / or support for address randomization.

[0119] At 1040, authentication occurs between STA 1020 and AP 1010.

[0120] At 1050, STA 1020 transmits a PASN-protected association request that proposes a single address setup algorithm, including: algorithm parameters, random values, and a MAC address seed. The association request may also include the average duration of the single address setup and other association parameters (e.g., PHY and MAC capabilities).

[0121] At 1060, AP 1010 can transmit a PASN-protected association response, which includes a success (or failure) indication, a single address algorithm, and the single address algorithm including: algorithm parameters, a random value, a first AP MAC address seed, and / or a single address setting start time seed and end time seed. The association response may also include a grouped address algorithm, which includes a random value and / or a second AP MAC address seed, where the first AP MAC address seed is different. In other words, grouped addressing and single addressing can be selected independently. For example, the MAC address used for grouped addressing cannot be calculated by monitoring a single address. The association response may include other association parameters (e.g., PHY and MAC capabilities).

[0122] At 1070, STA 1020 is associated with AP 1010 and has been configured with individual address settings and / or group address settings as described in Table 1. Individual address and / or Table 4. Group address settings. STA 1020 and AP 1010 also have scheduling for changing the individual address settings and group address settings.

[0123] AP 1010 and STA 1020 use the same algorithm and parameters to calculate the same updated parameter values. In other words, the STA has certain parameter values ​​and a corresponding algorithm for individual address settings. One group of address settings can be used at a time. The algorithm can use values ​​stored by other means, including but not limited to: MAC address seed, link ID, authentication MAC address, TSF, AID, etc. The joint algorithm ensures that no signal updates of new random address setting values ​​are needed to AP 1010 and STA 1020. Therefore, power savings for STA 1020 and AP 1010 are improved, and management overhead is reduced. Furthermore, because address changes are more robust, re-authentication or re-association is not required due to AP address loss. In some implementations, the joint algorithm can consume less storage compared to storing new input parameters.

[0124] Figure 11 Example 1100 of signaling for MAC address conflict detection and avoidance according to some embodiments of this disclosure is shown. For illustrative purposes and not for limitation, elements of other figures in this disclosure may be referenced for description. Figure 11 For example, AP 1110 could be... Figure 1One of AP 160 or PE AP 110a-110c, and STA 1120 can be Figure 1 One of STA 130, STA 180, STA 170 or PE non-AP STA 120a-120c.

[0125] During operation, the random MAC address scheme consists of a randomly selected 46-bit address. STA 1120 only experiences a collision if both AP 1110 and STA 1120's individual addresses collide. The receiver verifies the transmitter and receiver addresses, and if the STA is the receiver and the associated AP is the transmitter, the STA will receive frames not targeted at itself. This is a very rare occurrence. AP MAC addresses in a group of addresses can experience collisions (e.g., the associated AP 1110 has the same MAC address as other APs (not shown).

[0126] To avoid MAC address conflicts: STA 1120 can send its MAC address to AP 1110. In some implementations, STA 1120 can propose a new MAC address for itself. In some implementations, if AP 1110's MAC address conflicts with other MAC addresses, STA 1120 can propose that AP 1110 change its MAC address. AP 1110 or a server (not shown) can store currently used MAC addresses and / or MAC addresses to be used in the future, and determine whether a conflict will occur between the currently used MAC address and the MAC address to be used in the future. In some implementations, AP 1110 can request STA 1120 to change its MAC address to avoid using a MAC address that is already in use.

[0127] Example 1100 illustrates signaling used for MAC address conflict detection and avoidance.

[0128] At 1130, STA 1120 is associated with AP 1110 and has been configured with both individual address settings and group address settings.

[0129] At 1140, STA 1120 detects MAC addresses in the channel (e.g., a link) that will conflict with the MAC address of STA 1120 in the address settings to be used in the future. STA 1120 reports the conflict with the associated AP, namely AP 1110. The report may include a proposed new MAC address from STA 1120. (See 1150 below.)

[0130] At 1150, STA 1120 can transmit a robust MGMT frame that includes an address conflict notification, which may include: the conflicting STA 1120 MAC address, the proposed new STA 1120 MAC address, and the time when the proposed new STA 1120 MAC address is in use.

[0131] At 1160, AP 1110 can transmit a robust MGMT frame that includes an address conflict notification, which may include an indication of acceptance (or rejection).

[0132] At 1170, STA 1120 continues operation using the new MAC address. (See 1160 below.)

[0133] Figure 12 An exemplary method 1200 for data transmission using random address settings according to some embodiments of the present disclosure is shown. For illustrative purposes and not for limitation, elements of other figures in this disclosure may be referenced for description. Figure 12 In some implementations, transmitter 1230 may be Figure 1 The AP 160 or PE AP 110a-110c are both valid, and the receiver 1240 can be a STA 170 or... Figure 1 The PE is not one of AP STA 120a-120c. In some implementations, the receiver 1240 may be... Figure 1 One of AP 160 or PE AP 110a-110c, and transmitter 1230 can be Figure 1 One of STA 130, STA 180, STA 170 or PE non-AP STA 120a-120c.

[0134] In method 1200, for convenience rather than limitation, the transmitter 1230 may be... Figure 4A AP 410, and receiver 1240 can be Figure 4A The associated STA 420 (also known as STA 420). AP 410 can receive data corresponding to the Internet / application, encrypt the data, and apply a single address setting as described herein, where the single address setting only modifies the address and parameters of the over-the-air (OTA) transmission. STA 420 can receive data and send a Block Acknowledgment (BA) using the single address setting information. The single address setting is reversed before the MPDU is decrypted. The MPDU is decrypted, and the data is sent to the corresponding Internet / application at 1250. Details of method 1200 are provided below.

[0135] At 1210, data corresponding to the internal / application is generated and sent / delivered to AP410 via the Internet for final transmission to the Internet / application at 1250.

[0136] At position 1232, AP 410 performs aggregated MAC Service Data Unit (A-MSDU) aggregation to form MAC Protocol Data Unit (MPDU). AP 410 assigns a packet number (PN) corresponding to the MPDU and encrypts a portion of the MPDU (e.g., the payload portion of the MPDU).

[0137] At position 1234, set the sequence number (SN) corresponding to the encrypted MPDU.

[0138] At position 1236, AP 410 applies a single address setting as described in Table 1. A single address, such as setting 1411 in Figure 4. Therefore, the address field in the MAC header can be updated so that the transport address (TA) corresponds to the BSSID of AP 410 with single address setting 411. unicast And the receive address (RA) corresponds to the STA link address of STA 420. unicast Additionally, the AP 410 can create over-the-air (OTA) packet numbers (PNs) that are different from the PNs corresponding to the MPDU. OTA ), where PN OTA OTA transmission at 1250. PN OTA =PN+PN Offset , where offset PN (PN Offset ) is a single address setting PN offset of 411. unicast The AP 410 can also create an over-the-air (OTA) serial number (SN) that is different from the SN corresponding to the MPDU. OTA (For example, see 1234 above), where SN OTA OTA transmission at 1250. SN OTA =SN+SN Offset , where offset SN(SN) Offset This is a single address setting with a SN offset (TID) of 411. unicast .

[0139] At 1238, AP 410 transmits the corresponding data from the transmission queue of OTA transmission 1250 to receiver 1240 (STA 420).

[0140] At 1242, STA 420 determines whether a transmission is intended for STA 420 by determining whether RA and TA correspond to a single address setting 411.

[0141] At position 1244, in the receive buffer of STA 420, STA 420 generates and transmits a Block Acknowledgment (BA) using the received value. Subsequently, STA 420 uses a single address setting 411 parameter to recover the MPDU parameters. For example, STA 420 can use the PN of a single address profile 411. Offset PN OTA To determine the PN, and use a single address to set the SN of 411. OTA and SN Offset To determine SN, where PN and SN correspond to MPDU. PN and SN can be determined by the following equation: PN = PN OTA -PN Offset And SN = SN OTA -SN Offset .

[0142] At position 1246, STA 420 can reorder frames based on SN.

[0143] In 1248, STA 420 can decrypt the encrypted part of the MPDU, verify the PN sequence of the MPDU, and verify whether each MPDU receives the source address (SA) and destination address (DA) from the secure A-MSDU.

[0144] At point 1250, the data is sent to the corresponding internet / application.

[0145] Figure 13A Figure 1300 illustrates data delivered to Galois / Counter Mode (GCM) encryption as described in IEEE P802.11 REVme. Figure 1300 includes constructing Additional Authentication Data (AAD) 1320, constructing the GCM Protocol (GCMP) header 1330, and GCM encryption 1310 to form an encrypted MPDU. The GCM header includes the PN of the MPDU. The number of PNs for the transmitter monotonically increases, and the PNs can be used to track the transmitter, as shown in example 1400 of the extended GCMP MPDU. Figure 14A As shown. To protect the identity of the STA (or AP), the number of PNs should be modified for individual address settings or group address settings. In some implementations, individual address settings or group address settings include offset PN values ​​different from the PNs, making it impossible to trace between address settings.

[0146] Figure 13B Example 1350 illustrates an encryption block diagram supporting random address settings according to some embodiments of this disclosure. Some embodiments improve MAC address privacy and thus improve wireless communication while minimizing the impact on the encryption process. For example, PN for OTA transmission. OTAAdded after A-MSDU encryption. Additionally, additional authentication data (AAD) is constructed using the predefined addresses of the STA and AP. This means that encryption uses the STA and AP addresses of non-OTA transmissions. OTA transmissions belonging to a single address setting or a group address setting first change the addresses to the invariant static addresses of the STA and AP. The MAC address and SN of the OTA transmission packets are changed, and the updated MAC header is pre-applied to the output of the GMC encryption module 1310. The transmitter (e.g., Figure 12 The update operation in transmitter 1230 is shown in example 1350 below: at 1362, by adding PN Offset To calculate PN OTA At position 1364, PN OTA Insert into GCMP header ( Figure 14A (As shown in the diagram). At 1380, the transmitter address (TA) and receiver address (RA) of the SN and MAC headers are modified for OTA transmission.

[0147] Example 1350 illustrates parameters (e.g., PN) in a single address configuration profile and / or a group of address configuration profiles. Offset SN Offset How can this be used to generate over-the-air (OTA) parameters (e.g., PN)? OTA SN OTA Example 1350 shows adding PN at 1362 at 1360. Offset Furthermore, a GCM header is constructed at position 1364, allowing the offset PN to be calculated as follows:

[0148] PN OTA =PN+PN Offset

[0149] AAD is used for encrypting (for transmission) and decrypting (for reception) frames that include A-MSDU. Figure 14BExample 1450 of the AAD for Protocol Version 0 (PV0) MPDU is shown. The AAD includes the MPDU frame control field, the address of the encrypted / decrypted frame, the MPDU sequence control field (bits 0-3 present, other bits masked to 0), and the QoS control field (bits 0-3 and bit 7 if an STA supporting A-MSDU is present, other bits masked to 0). If either the To Distributed System (DS) or From DS subfield in the MPDU's MAC header is set to 1, and the MPDU is a separately addressed data frame between an AP MLD and a non-AP MLD associated with the AP MLD, then A1 is set to the MLD MAC address of the intended receiver MLD of the MPDU, and A2 is set to the MLD MAC address of the transmitting MLD of the MPDU. Otherwise, A1 is set to the MPDU address 1 field, and A2 is set to the MPDU address 2 field. If the MPDU address 3 field is a BSSID and the MPDU is a separately addressed data frame between an AP MLD and a non-AP MLD associated with the AP MLD, then A3 is set to the MLD MAC address of the AP MLD, where the corresponding AP with the BSSID is attached to the AP MLD. Otherwise, A3 is set to the MPDU address 3 field, and A4 (if present) is set to the MPDU address 4 field. At 1380, the OTA SN of the MAC header is generated as the SN. OTA =SN+SN Offset .

[0150] Figure 22A Figure 2200 illustrates the decryption of an encrypted MPDU delivered to a Galois / Counter Mode (GCM) decryption module as described in IEEE P802.11REVme. Figure 2200 shows the parsing of the input encrypted MPDU to construct the AAD and nonce values. At 2220, the AAD is constructed from the MPDU header of the encrypted MPDU. At 2230, the nonce is constructed from the A2 and PN fields. The constructed AAD, data (which is the encrypted frame body of the plaintext MPDU), Message Integrity Check (MIC), and the constructed nonce are input to the GCM decryption module 2210 to generate plaintext data. The received MPDU header and the plaintext MPDU from the GCM decryption function are concatenated to form the plaintext MPDU.

[0151] Figure 22B Example 2270 illustrates a decryption block diagram supporting random address settings according to some embodiments of this disclosure. At 2250, the receiver verifies whether the MAC address of the MPDU matches the receiver's link address. At 2260, the parameters in the MAC header modified at 1380 in example 1350 are restored to their original values. This is achieved by subtracting the offset added at the transmitter (SN = SN...). OTA-SN from address settings Offset And PN = PN OTA -PN from address setting Offset The SN and PN are recovered. Additionally, at 2260, the STA link address can be set to the STA MLD address, and the AP link address can be set to the APMLD address. At 2220 and 2230, the input encrypted MPDU with the updated MAC header is parsed to construct the AAD and nonce values. The constructed AAD, data (which is the encrypted frame body of the plaintext MPDU), Message Integrity Check (MIC), and the constructed nonce are input to the GMC decryption module 2210 to generate plaintext data. The received MPDU header and the plaintext MPDU from the GCM decryption function are concatenated to form the plaintext MPDU.

[0152] In some implementations, when a single address setting or a group of address settings is in use

[0153] The OTA (Over-The-Air) reverts the MAC address of packets received back to the MAC-SAP address of both the AP and STA. In some implementations, the traditional MAC address is divided into three addresses. These addresses are the same as the MLD MAC address. The MAC-SAP address is used for all encryption and decryption operations to avoid changes to the encryption and decryption procedures.

[0154] The receiver verifies the address of received frames before applying AAD parameters. Verification ensures that received frames are addressed according to the currently used address setting rules (see Table 2. Rules for APs and STAs using address randomization). In some implementations, for MLDs (e.g., the 802.11be case), the OTA MLD address is used (see below). Figure 17 (As described in the text), and for 802.11be MLD, the AAD has been changed. Some implementations change the link address to the MLD-SAP address. Using the same MLD-SAP address ensures that encrypted MPDUs can be transmitted over any link by simply changing the address setting to a specific parameter value and without needing to re-encrypt (e.g., decrypt and re-encrypt) the MPDU. The receiver verifies that the MAC address of the MPDU received by the OTA matches the address profile being used, but the AAD used in encryption uses the initial MAC address.

[0155] Some implementation schemes include rules for randomizing the selected parameters, as shown in Table 5 below. Rules for randomizing the selected parameters.

[0156] Table 5: Rules for randomizing selected parameters

[0157]

[0158] In some implementations, the PE MLD implements two levels of MAC address randomization. In the first MAC address randomization level, the BSS / AP link-specific address can be randomized. In other words, the address corresponding to one link of the MLD is randomized, independent of the other links of the MLD. Therefore, each link can have its own individual and grouped address settings. Furthermore, each link can have a separate algorithm or algorithm parameters to randomly select a link-specific MAC address. This is similar to that used for single-link devices. Figure 4A and Figure 5A Examples of system 400 and 500.

[0159] Figure 15 An exemplary privacy-enhanced (PE) multi-link device (MLD) system 1500 supporting address randomization schemes according to some embodiments of this disclosure is illustrated. Reference may be made for illustrative purposes and not for limiting purposes. Figure 1 To describe the elements Figure 15 For example, PE AP MLD 1510 includes three subsidiary PE APs: PE AP1 1511, PE AP2 1513, and PE AP3 1515, which can include... Figure 1 The PE AP MLD 110 includes the associated PE AP 110a-110c. The PE non-AP MLD 1520 includes three associated PE non-AP STAs: PE non-AP STA1 1521, PE non-AP STA2 1523, and PE non-AP STA3 1525, which can be equipped with… Figure 1 The PE non-AP MLD 120 is an auxiliary PE non-AP STA 120a-120c. The PE AP MLD 1510 communicates with the PE non-AP MLD 1520 via corresponding links: Link 1 1530, Link 2 1535 and Link 3 1540.

[0160] For example, PE AP1 1511 operates BSS1 and communicates with PE non-AP STA1 1521 via link 1 1530. PE AP1 1511 can establish multiple individual address settings with PE non-AP STA1 1521, wherein these multiple individual address settings, identified as unicast address settings 1 in system 1500, can be used for communication via link 1 1530. Additionally, multiple group address settings, identified as multicast address settings 1, can be established for communication via link 1 1530. PE AP2 1513 operates BSS2 and communicates with PE non-AP STA2 1523 via link 2 1535. PE AP2 1513 can establish multiple individual address settings with PE non-AP STA2 1523, wherein these multiple individual address settings, identified as unicast address settings 2 in system 1500, can be used for communication via link 2. Multiple group address settings, identified as multicast address setting 2, can be established for communication via link 21533. Furthermore, PE AP3 1515 operates BSS3 and communicates with PE non-AP STA3 1525 via link 3 1540. PE AP3 1515 can establish multiple individual address settings with PE non-AP STA3 1525, wherein these multiple individual address settings, identified as unicast address setting 3 in system 1500, can be used for communication via link 3. Multiple group address settings, identified as multicast address setting 3, can be established for communication via link 3 1540.

[0161] In the second MAC address randomization level, the MLD address, as well as the MLD-level identifier and parameters, are randomized at the MLD level. In other words, there is no common unencrypted MLD address or MLD identifier and parameters transmitted over the air. Randomizing the MLD-level address, identifier, and parameters at the MLD level ensures that PE APs attached to the PE AP MLD can operate independently, and PE non-AP STAs attached to the PE non-AP MLD can operate independently.

[0162] Figure 16 An exemplary PEMLD system 1600, including address and identifier randomization, is shown according to some embodiments of this disclosure. Reference may be made for illustrative purposes and not for limiting purposes. Figure 15 To describe the elements Figure 16 For example, PE APMLD 1610 can be PE AP MLD 1510, and PE non-AP MLD 1620 can be... Figure 15The system 1600 includes a PE AP MLD 1610, which includes three auxiliary PE APs communicating with the PE AP MLD 1620 via corresponding links: link 1 1630, link 2 1635, and link 3 1640: PE AP1 1611, PE AP2 1613, and PE AP3 1615. The PE AP MLD 1620 includes three auxiliary PE AP STAs: PE AP STA1 1621, PE AP STA2 1623, and PE AP STA3 1625.

[0163] The MLD level parameters of PE AP MLD 1610 are randomized and used for three auxiliary PE APs. These MLD level parameters have individual values ​​in each of the auxiliary PE APs 1 1611, PE AP2 1613, and PE AP3 1615, making it possible for an attacker (e.g., a bad actor) to not know which links PE AP MLD 1610 is operating (e.g., link 1 1630, link 2 1635, and link 3 1640). Each of the auxiliary PE APs 1 1611, PE AP2 1613, and PE AP3 1615 can maintain and hide its MLD level parameters, including but not limited to: MLD address, TSF, AID, PN, sequence number space (SNS): per STA and DLTID, grouped frames, MGMT frames, and / or legacy frames. The MLD address of PE AP MLD 1610 is encrypted, making it undetectable to attackers of its affiliated PE APs 1 1611, PE AP2 1613, and PE AP3 1615. SN and PN counters are maintained at the MLD level. Therefore, PE AP MLD 1610 should modify the SN and PN packet values ​​for each link individually. Each link (e.g., link 1 1630, link 2 1635, and link 3 1640) can have a corresponding TSF value. The TSF value should change independently of other link-specific TSF values ​​to make it difficult to trace affiliated PE APs.

[0164] The PE non-AP MLD 1620 MLD level parameters are used for three subordinate PE non-AP STAs. These MLD level parameters have individual values ​​in each of the subordinate PE non-AP STA1 1621, PE non-AP STA2 1623, and PE non-AP STA3 1625, making it possible for an attacker to not know which links the PE non-AP MLD 1620 operates on. Each of the subordinate PE non-AP STA1 1621, PE non-AP STA2 1623, and PE non-AP STA3 1625 can maintain and hide its MLD level parameters, including but not limited to: MLD address, PN, SNS: UL per TID. The PE non-AP MLD 1620 MLD address should be encrypted so that an attacker cannot detect the subordinate PE non-AP STA1 1621, PE non-AP STA2 1623, and PE non-AP STA3 1625 belonging to the PE non-AP MLD 1620.

[0165] Figure 17 Example 1700 of multiple MLD address types for address randomization according to some embodiments of this disclosure is shown. In some embodiments, the packet MLD address for over-the-air (OTA) transmissions can be changed and randomized. Example 1700 includes an MLD address 1710, which may be an IEEE 802.11be MLD address. MLD address 1710 may be one of three different addresses: i) a unique MLD address 1730 that identifies the authenticated and associated MLD (e.g., PE AP MLD or PE MLD). ii) The unique MLD address 1730 is a constant value used for the PE MLD and cannot be changed; ii) the MAC Service Access Point (SAP) address 1740, which can be the MAC address identifying the non-AP MLD facing the Internet (e.g., visible to an AP connected to the Internet via Ethernet). This MAC address can be used for MPDU encryption and decryption. Encryption is performed using the SAP address, and after encryption, the MAC address in the OTA packet is changed to the OTA MAC address. Similarly, in decryption, the OTA address is first verified to match the link-specific address, and then the SAP address is used for decryption. The MAC SAP address 1740 is a constant value and cannot be changed; and iii) the OTA MLD address 1720, which can be transmitted in address 3 of the data frame. (See IEEE P802.11REVme) In some implementations, the PE non-AP MLD can change and encrypt the OTA MLD address value. In some implementations, the OTA MLD address 1720 can be the same as the MAC SAP address 1740. The OTA MLD address 1720 can be the same as the MAC SAP address 1740 when a portion of the MPDU including the MLD address is encrypted.

[0166] Both PE AP MLDs and PE non-AP MLDs can have link-specific addresses for each link. These link-specific addresses identify the PE APs and PE non-AP STAs within the link. Each PE AP in a PE AP MLD should have a unique link-specific MAC address value. PE non-AP STAs in a PE non-AP MLD can have the same link MAC address across different links. A single address setting limits the link-specific MAC address used for a single frame transmission. Similarly, a grouped address setting limits the link addresses used by a PE AP for transmitting groups of frames.

[0167] Figure 18A Example 1800 of data transmission supporting PE MLD random addresses according to some embodiments of this disclosure is shown. Example 1800 shows data transmission of a PHY Protocol Data Unit (PPDU) including a preamble 1805, and aggregated MPDU (A-MPDU) subframes 1810a-1810c that can be transmitted over OTA.

[0168] Figure 18B An exemplary MPDU 1820 is shown as a portion of an A-MPDU subframe 1810 according to some embodiments of the present disclosure, including an unencrypted A-MPDU subframe header 1822 and a MAC header 1824, an encrypted A-MSDU subframe 1850, and an unencrypted frame check sequence 1826. For illustrative purposes and not for limiting purposes, elements of other figures in this disclosure may be referenced for description. Figure 18B For example, the exemplary MPDU 1820 can be manufactured by... Figure 16 The PE AP MLD 1610 and / or PE non-AP MLD 1620 are used for creation. In some implementations, the MPDU 1820 may be... Figure 18A A portion of the A-MPDU subframe 1810, wherein the A-MPDU 1810 may also include an MPDU delimiter field and variable-length padding.

[0169] Figure 18CAn encrypted basic A-MSDU subframe structure 1850, as shown in A-MPDU subframe 1820, is illustrated. The A-MSDU subframe structure includes an A-MSDU subframe header 1830, a variable-length MSDU, and variable-length padding. In some embodiments, the A-MSDU subframe header 1830 may include an encrypted MLD address, and the unencrypted MAC header 1824 may include a link-specific MAC address. For example, the MLD address may be present in the source address (SA) or destination address (DA) of the A-MSDU subframe header 1830. In some embodiments, the OTA MLD address 1720 may be present in the SA or DA of the A-MSDU subframe header 1830. In some embodiments, the OTA MLD address 1720 present in the SA or DA of the A-MSDU subframe header 1830 may be the same as the MAC SAP address 1740. Therefore, PE AP MLD 1610 and PE non-AP MLD 1620 can encrypt the A-MSDU subframe header 1830 to protect the MLD address, which can be in the SA or DA field. SA and DA can be addresses in Ethernet, Wi-Fi mesh, or MLD addresses, depending on the final destination of the frame. This differs from transmissions that typically transmit without an encrypted A-MSDU subframe header 1830.

[0170] Figure 19 Example 1900 illustrates a modification of the OTA MLDMAC address for a PPDU used for group addressing, according to some embodiments of this disclosure. Reference may be made for illustrative purposes and not for limiting purposes. Figure 15 To describe the elements Figure 19 For example, PEAP MLD 1910 could be PE AP MLD 1510, and PE non-AP MLD 1920 could be... Figure 15 The PE non-AP MLD1520. System 1900 includes PE AP MLD 1910, which includes two auxiliary PE APs: PE AP1 1912 and PE AP2 1914, which communicate with PE non-AP MLD 1920 via corresponding links. PE non-AP MLD 1920 includes two auxiliary PE non-AP STAs: PE non-AP STA1 1922 and PE non-AP STA2 1924.

[0171] A legacy STA 1930 may not be able to receive grouped frames with encrypted A-MSDU aggregation. If a PE AP MLD 1910 has a legacy STA 1930 associated with any affiliated PE APs (e.g., PE AP1 1912), it may be necessary to randomly configure the OTMLD address to protect the privacy of the PE AP MLD 1910. When grouped addressed frames are transmitted by all affiliated PE APs of the PE AP MLD (e.g., PE AP1 1912 and PE AP2 1914), encrypting the MLD address in one affiliated PE AP of the PE AP MLD 1910 (e.g., PE AP1 1912) may not protect the MLD address transmitted in other affiliated PE APs of the PE AP MLD 1910 (e.g., PE AP2 1914).

[0172] In some implementations, the PE non-AP MLD 1920 can change the corresponding OTA MLD address to be part of the unicast address setting. In some implementations, the PE AP MLD 1910 can change the corresponding OTA MLD address to be part of the multicast address setting. For example, OTA MLD address changes can be performed via signaling used to configure and update link-specific address settings, such as... Figure 8 , Figure 9 or Figure 20 As stated in the document. In all cases, the PE AP MLD 1910 should have a corresponding OTA MLD in use, and the PE non-AP MLD 1920 should have a corresponding OTA MLD in use.

[0173] Figure 20 Example 2000 of signaling for configuring a joint algorithm according to some embodiments of this disclosure, which determines the address settings of the MLD and signaling for address conflict notification, is shown. Reference may be made for illustrative purposes and not for limiting purposes. Figure 1 To describe the elements Figure 20 For example, PE AP MLD 2010 can be PE AP MLD 110, PE AP12010a and PE AP2 2010b can be PE AP 110a and PE AP 110b, PE non-AP MLD 2020 can be PE non-AP MLD 120, and PE non-AP STA1 2020a and PE non-AP STA2 2020b can be... Figure 1 The accompanying PE non-APSTA 120a and PE non-APSTA 120b.

[0174] The association request may also contain the PE non-AP MLD SAP MAC address used in frame encryption, and it may include the MLD address of the PE non-AP MLD used for authentication and association. Similarly, the association response may contain the PE AP MLD SAP MAC address and the MLD address of the PE AP MLD used for authentication and association.

[0175] In some implementations, individual address settings and grouped address settings are signaled for all links in the setup signaling. Each link can have an independent address change schedule and different random address values. MLD address and MLD level parameters are also set for PE AP MLD2010 and PE non-AP MLD 2020. Address conflict notifications can be transmitted on any link, and it can report conflicts on any link (e.g., link 1 or link 2 in Example 2000).

[0176] During association, a joint algorithm can be deployed to configure and update address setting parameters. In association signaling, the PEAP MLD 2010 and PE non-AP MLD 2020 can agree on a set of joint algorithms to calculate link-specific individual address settings and link-specific group address settings. The joint algorithm can also configure address setting transition times and the number of address settings in use. Furthermore, the joint algorithm can be different for each of the multiple links of the MLD. Communication can occur on one of the multiple links between the affiliated PE AP (e.g., PE AP1 2010a) and the affiliated PE non-AP STA (e.g., PE non-AP STA1 2020a). The PE AP MLD 2010 can change one or more of the joint algorithm or parameter values ​​used for link-specific address settings (e.g., individual address settings or group address settings). For example, if an STA (not shown) is not associated with PE AP1 2010a, a change in the multicast address setting algorithm ensures that only associated STAs (e.g., PE non-AP STA1 2020a) can know the next address of PE AP1 2010a. Alternatively, PE AP1 2010a can maintain an algorithm for group address setting, allowing STAs reassociated with PE AP1 2010a to calculate the current PE AP1 2010a parameters and discover PE AP1 2010a.

[0177] At 2030, PE AP1 2010a can transmit beacon frames that signal support for a minimum number of single address settings in address randomization and association. The beacon frame may include RSNE, which includes indications of PASN protocol, FT, AKM, RSNXE, MDE, and / or support for address randomization.

[0178] At 2035, certification occurs between PE non-AP MLD 2020 and PE AP MLD 2010.

[0179] At point 2040, the PE non-AP STA1 2020a sends a PASN-protected association request that proposes a single address setting algorithm for Link 1 and Link 2 (where the algorithm may differ for each link), including: algorithm parameters, random values, and MAC address seed. The association request may also include the average duration of the proposed single address setting, as well as other association parameters for Link 1 and Link 2 (e.g., the PHY and MAC capabilities of the PE non-AP STA1 2020a).

[0180] At position 2045, PE AP1 2010a can transmit a PASN-protected association response, which includes a success (or failure) indication, a single address algorithm for both Link 1 and Link 2, and this single address algorithm includes: algorithm parameters, a random value, a first AP MAC address seed, and / or a single address setting start time seed and end time seed. The association response may also include a grouped address algorithm for both Link 1 and Link 2, and this grouped address algorithm includes a random value and / or a second AP MAC address seed, wherein the first AP MAC address seed is different. The association response may include other association parameters corresponding to Link 1 and Link 2 (e.g., PHY and MAC capabilities).

[0181] At 2050, the PE non-AP MLD 2020 is associated with the PE AP MLD 2010 and has been configured with individual address settings and / or group address settings for each link, as described in Table 1. Individual address settings and / or Table 4. Group address settings. Each link (e.g., PE non-AP STA1 2020a and PE AP1 2010a) has a schedule for changing the individual address settings and group address settings.

[0182] At address 2065, PE non-AP STA2 2020b detects addresses in the channel that will conflict with the MAC address of PE non-AP STA2 2020b in the address settings to be used in the future. For example, PE non-AP STA2 2020b can notify PE non-AP MLD 2020, causing PE non-AP STA1 2020a to report a conflict with the associated PE AP MLD 2010. The report may include a proposed new MAC address for PE non-AP STA2 2020b.

[0183] At 2070, PE non-AP STA1 2020a can transmit a robust MGMT frame that includes an address conflict notification, which may include the following: the MAC address of the conflicting PE non-AP STA2 2020b, the proposed new MAC address of PE non-AP STA2 2020b, and the time when the proposed new MAC address of PE non-AP STA2 2020b is in use.

[0184] At 2080, the PE non-AP STA1 2020a can transmit a robust MGMT frame that includes an address conflict notification, which may include an indication of acceptance (or rejection).

[0185] Figure 21 Exemplary methods for data transfer between PE MLDs according to some embodiments of the present disclosure are shown. For illustrative purposes and not for limitation, elements of other figures in this disclosure may be referenced for description. Figure 21 In some implementations, transmitter 2130 may be PE AP 110, which includes three auxiliary PE APs: Figure 1 The PE AP 110a-110c, and the receiver 2140 can be a PE non-AP MLD 120, which includes 3 auxiliary PE non-AP STAs: Figure 1 The PE is not APSTA 120a-120c. In some implementations, receiver 2140 may be PE AP 110, which includes three auxiliary PE APs: Figure 1 The PE AP 110a-110c, and the transmitter 2130 can be a PE non-AP MLD 120, which includes 3 auxiliary PE non-APSTAs: Figure 1 PE non-AP STA 120a-120c.

[0186] In method 2100, for convenience rather than limitation, the transmitter 2130 may be... Figure 15 The PE AP MLD 1510 includes three auxiliary PE APs: PE AP1 1511, PE AP2 1513, and PE AP3 1515. The receiver 2140 can be... Figure 15The associated PE non-AP MLD 1520 includes three subsidiary PE non-AP STAs: PE non-AP STA1 1521, PE non-AP STA2 1523, and PE non-AP STA3 1525. The PE AP MLD 1510 can receive data corresponding to the Internet / application, encrypt the data, and apply a single address setting as described herein, where the single address setting only modifies the address and parameters of the over-the-air (OTA) transmission. The PE non-AP MLD 1520 can receive data and send a block acknowledgment (BA) using the single address setting information. The single address setting is reversed before the MPDU is decrypted. The MPDU is decrypted, and at 2150, the data is sent to the corresponding Internet / application. Details of method 2100 are provided below.

[0187] At 2110, data corresponding to the Internet / application is generated and sent to PE AP MLD 1510 for final transmission to the Internet / application at 2150.

[0188] At 2132, the PE AP MLD 1510 performs aggregated MAC Service Data Unit (A-MSDU) aggregation to form a MAC Protocol Data Unit (MPDU). The PE AP MLD 1510 assigns a packet number (PN) corresponding to the MPDU and encrypts the MPDU.

[0189] At position 2134, set the sequence number (SN) corresponding to the encrypted MPDU.

[0190] At 2136a, PE AP MLD 1510 selects PE AP1 1511 to transmit the encrypted MPDU and applies a single address setting as described in Table 1. The single address setting is, for example, setting 1 corresponding to PE AP1 1511 (e.g., 411 in Figure 4). Therefore, the transport address (TA) corresponds to the BSSID of PE AP1 1511 with the single address setting. unicast And the receive address (RA) corresponds to the STA link address of the PE non-AP STA1 1521. unicast Additionally, PE AP1 1511 can create over-the-air (OTA) packet numbers (PNs) that are different from the PNs corresponding to MPDUs. OTA ), where PN OTA OTA transmission at 2150a. PN OTA =PN+PN Offset , where offset PN (PN Offset ) is the PN offset set by a single address. unicastPE AP1 1511 can also create an over-the-air (OTA) sequence number (SN) that is different from the SN corresponding to the encrypted MPDU. OTA ), where SN OTA OTA transmission at 2150a. SN OTA =SN+SN Offset , where offset SN(SN) Offset The SN offset (TID) is set for a single address. unicast When PE AP MLD 1510 selects PE AP2 1513 and PE AP3 1515, a similar process occurs on various links at 2136b and 2136c.

[0191] At 2138a, PE AP1 1511 transmits the corresponding data from the transmission queue of OTA transmission 2150a to receiver 2140 corresponding to PE non-AP STA1. Similar processes occur on various links at 2138b and 2138c when PE AP MLD 1510 selects PE AP2 1513 and PE AP3 1515.

[0192] At 2142a, PE non-AP STA1 determines whether a transmission is intended for PE non-AP STA1 by determining whether RA and TA correspond to a single address setting. A similar process occurs on the various links at 2142b and 2142c when PE AP MLD 1510 selects PE AP2 1513 and PE AP3 1515. For example, a single address setting would identify PE non-AP STA2 1523 and PE non-AP STA3 1525.

[0193] At 2144a, in the receive buffer of PE non-AP STA1, PE non-AP STA1 generates and transmits a block acknowledgment (BA) using the received value. Subsequently, PE non-AP STA1 uses a single address setting parameter to recover the MPDU parameters. For example, PE non-AP STA1 can use the PN of a single address profile. Offset PN OTA To determine the PN, and use the SN set by a single address. OTA and SN Offset To determine SN, where PN and SN correspond to MPDU. PN and SN can be determined by the following equation: PN = PN OTA -PN Offset And SN = SN OTA -SN OffsetWhen PE AP MLD 1510 selects PE AP2 1513 and PE AP3 1515, a similar process occurs on various links at 2144b and 2144c.

[0194] At 2146, PE non-AP MLD 1520 can reorder frames based on SN.

[0195] At 2148, the PE non-AP MLD 1520 can decrypt the encrypted MPDU, verify the PN sequence of the MPDU, and verify whether each MPDU received the source address (SA) and destination address (DA) from the secure A-MSDU.

[0196] At point 2150, the data is sent to the corresponding internet / application.

[0197] Various implementation schemes can be implemented, for example, using one or more well-known computer systems such as the computer system 2200 shown in Figure 22. The computer system 2200 can be any well-known computer capable of performing the functions described herein. For example, but not limited to, Figure 1 PE AP MLD 110, PE AP 110a-110c, PE non-AP MLD 120, PE non-AP STA 120a-120c, STA 130, STA 170, STA 180 and AP 160; Figure 2 System 200; Figure 4A and Figure 4B System 400 and Example 450; Figure 5A and Figure 5B System 500 and Example 550; Figure 6 to Figure 12 , Figure 13B , Figure 15 to Figure 17 , Figure 18A , Figure 18B as well as Figure 19 to Figure 21 Examples 600, 700, 800, 900, 1000, 1100, 1200, 1350, 1500, 1600, 1700, 1800, 1810a, 1900, 2000 and 2100 (and / or other devices and / or components shown in the figures) may be implemented using computer system 2300 or a portion thereof.

[0198] Computer system 2300 includes one or more processors (also referred to as central processing units or CPUs), such as processor 2304. Processor 2304 is connected to a communication infrastructure 2306, which may be a bus. The one or more processors 2304 may each be a graphics processing unit (GPU). In embodiments, a GPU is a processor designed for processing dedicated electronic circuitry for mathematically intensive applications. The GPU may have an efficient parallel architecture for parallel processing of large blocks of data, such as general mathematically intensive data in computer graphics applications, images, videos, etc.

[0199] Computer system 2300 also includes user input / output devices 2303, such as monitors, keyboards, pointing devices, etc., that communicate with communication infrastructure 2306 via user input / output interface 2302. Computer system 2300 also includes main memory or primary memory 2308, such as random access memory (RAM). Main memory 2308 may include one or more levels of cache. Control logic components (e.g., computer software) and / or data are stored in main memory 2308.

[0200] The computer system 2300 may also include one or more auxiliary storage devices or memories 2310. The auxiliary storage 2310 may include, for example, a hard disk drive 2312 and / or a removable storage device or drive 2314. The removable storage drive 2314 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a magnetic tape backup device, and / or any other storage device / drive.

[0201] The removable storage drive 2314 can interact with the removable storage unit 2318. The removable storage unit 2318 includes a computer-usable or readable storage device on which computer software (control logic components) and / or data are stored. The removable storage unit 2318 can be a floppy disk, magnetic tape, optical disc, DVD, optical storage disk, and / or any other computer data storage device. The removable storage drive 2314 reads from and / or writes to the removable storage unit 2318 in a well-known manner.

[0202] According to some embodiments, auxiliary storage 2310 may include other means, tools, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 2300. Such means, tools, or other methods may include, for example, removable storage unit 2322 and interface 2320. Examples of removable storage unit 2322 and interface 2320 may include program boxes and box interfaces (such as those found in video game devices), removable memory chips (such as EPROM or PROM) and associated sockets, memory sticks and USB ports, memory cards and associated memory card slots, and / or any other removable storage unit and associated interface.

[0203] Computer system 2300 may also include a communication or network interface 2324. Communication interface 2324 enables computer system 2300 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (indicated individually and collectively by reference numeral 2328). For example, communication interface 2324 may allow computer system 2300 to communicate with remote device 2328 via communication path 2326, which may be wired and / or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic components and / or data may be transmitted to and from computer system 2300 via communication path 2326.

[0204] The operations described in the foregoing embodiments can be implemented with a wide variety of configurations and architectures. Therefore, some or all of the operations described in the foregoing embodiments can be performed in hardware, software, or both. In some embodiments, tangible, non-transitory devices or articles of art include tangible, non-transitory computer-usable or readable media on which control logic components (software) are stored, also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 2300, main memory 2308, secondary memory 2310, and removable storage units 2318 and 2322, and tangible articles of art embodying any combination thereof. When executed by one or more data processing devices (such as computer system 2300), such control logic components cause such data processing devices to operate as described herein.

[0205] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the art how to use [other methods]. Figure 23 The embodiments of this disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown herein. Specifically, the embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.

[0206] It should be understood that the Detailed Description section, rather than the Summary and Abstract section, is intended to interpret the claims. The Summary and Abstract section may set forth one or more, but not all, exemplary embodiments of this disclosure as contemplated by the inventors, and therefore is not intended to limit this disclosure or the appended claims in any way.

[0207] Although this disclosure has been described herein with reference to exemplary embodiments in exemplary fields and applications, it should be understood that this disclosure is not limited thereto. Other embodiments and modifications are possible and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. Furthermore, embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond those described herein.

[0208] The specific implementation has been described here using functional building blocks that illustrate the implementation of specific functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are performed appropriately. Furthermore, alternative implementations may use sequences of functional blocks, steps, operations, methods, etc., that differ from those described herein.

[0209] References to “an implementation,” “implementation,” “exemplary implementation,” or similar phrases herein indicate that the described implementation may include specific feature structures, structures, or characteristics, but each implementation need not necessarily include such feature structures, structures, or characteristics. Furthermore, such terminology need not refer to the same implementation. Additionally, when a specific feature structure, structure, or characteristic is described in connection with an implementation, whether or not it is explicitly mentioned or described herein, such feature structure, structure, or characteristic must be within the knowledge of a person skilled in the art to incorporate it into other implementations.

[0210] The breadth and scope of this disclosure should not be limited by any of the exemplary embodiments described above, but should be defined solely by the appended claims and their equivalents.

[0211] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should only occur upon receiving informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Transfer and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

Claims

1. An access point (AP), comprising: a transceiver; and a processor coupled to the transceiver, the processor configured to: establish two or more address profiles with a station (STA); establish a schedule for switching from a first address profile to a second address profile, wherein the first address profile and the second address profile belong to the two or more address profiles; encrypt an aggregated MAC service data unit (A-MSDU) including a packet number (PN) for transmission to the STA; After said encryption, creating an over-the-air, OTA, packet number, PN, different from said packet number, PN, corresponding to said A-MSDU OTA ; and transmitting a first data transmission via the transceiver using the first address profile, wherein the first data transmission includes the PN OTA .

2. The AP of claim 1, wherein the processor is further configured to: switch from the first address profile to the second address profile based on the schedule; and transmit a second data transmission via the transceiver using the second address profile.

3. The AP of claim 1, wherein the schedule for switching from the first address profile to the second address profile is based on a random time synchronization function (TSF) parameter.

4. The AP of claim 1, wherein the processor is further configured to: establish a new address profile with the STA; establish a first time at which the new address profile can be used; establish a second time at which the AP begins to operate on a different channel; and transmit a second data transmission via the transceiver on the different channel using a third address profile of the new address profile after the first time and the second time.

5. The AP of claim 4, wherein the processor is further configured to: determine an end time of the new address profile, wherein the third address profile is randomly selected from the new address profile before the end time.

6. The AP of claim 1, wherein the first address profile comprises an offset PN PN Offset , and wherein the PN OTA = PN + PN Offset .

7. The AP of claim 1, wherein the processor is further configured to: After said encryption, creating an over-the-air, OTA, sequence number, SN, different from a sequence number, SN, corresponding to said A-MSDU OTA wherein said first data transmission comprises said SN OTA wherein said first address profile comprises an offset SN SN Offset and wherein said SN OTA = SN + SN Offset .

8. The AP of claim 1, wherein the processor is further configured to: apply an AP identifier of the first address profile after the encrypting, wherein the first data transmission includes the AP identifier.

9. The AP of claim 1, wherein to establish the two or more address profiles, the processor is configured to: establish a joint algorithm with the STA; and determine the first address profile and the second address profile and a transition time for the schedule using the joint algorithm.

10. The AP of claim 9, wherein to establish the joint algorithm, the processor is further configured to: receive a single address set algorithm, a MAC address seed, and a proposed address set average duration via the transceiver; and transmit a single address set start time seed, a single address set end time seed, a group address algorithm, and an AP MAC address seed via the transceiver in response to the receiving.

11. The AP of claim 1, wherein the processor is further configured to: receiving, via the transceiver, a notification of a conflicting MAC address from the STA, wherein the notification includes: the conflicting MAC address, a proposed new MAC address for the STA, a time when the proposed new MAC address for the STA is in use, or a proposed new MAC address for the AP; and transmit, via the transceiver, an acknowledgement message corresponding to the notification to the STA.

12. A station (STA) comprising: a transceiver; and a processor coupled to the transceiver, the processor configured to: establish two or more address profiles with an access point (AP); establish a schedule for switching from a first address profile to a second address profile, wherein the first address profile and the second address profile belong to the two or more address profiles; and receive, via the transceiver, a first data transmission comprising a first receive address (RA) corresponding to the first address profile; and using an over-the-air, OTA, packet number, PN, of the first data transmission OTA and an offset, PNPN, from the first address profile Offset to determine a packet number, PN, wherein the PN corresponds to an encrypted aggregated, MAC, service data unit, A-MSDU, of the first data transmission.

13. The STA of claim 12, wherein the processor is further configured to: transmit, via the transceiver, a block acknowledgement (BA) corresponding to the first data transmission.

14. The STA of claim 12, wherein the processor is further configured to: switch from the first address profile to the second address profile based on the schedule; and receive, via the transceiver, a second data transmission comprising a second RA corresponding to the second address profile, wherein the first RA is different from the second RA.

15. The STA of claim 12, wherein the processor is further configured to: establish a new address profile with the AP; establish a first time at which the new address profile is available for use; establish a second time at which the AP begins to operate on a different channel; and transmit, via the transceiver, a second data transmission on the different channel using a third address profile of the new address profile after the first time and the second time.

16. The STA of claim 15, wherein the processor is further configured to: determine an end time of the new address profile, wherein the third address profile is randomly selected from the new address profile before the end time.

17. The STA of claim 12, wherein the processor is further configured to: using an over-the-air, OTA, sequence number, SN, of the first data transmission OTA and an offset SN of the first address profile Offset to determine a sequence number, SN, wherein the SN corresponds to the encrypted A-MSDU of the first data transmission.

18. The STA of claim 17, wherein the PN = PN OTA -PN Offset , and wherein the SN = SN OTA -SN Offset .

19. The STA of claim 17, wherein the processor is further configured to: order frames of the first data transmission according to the SN; and decrypt the encrypted A-MSDU.

20. The STA of claim 12, wherein the processor is further configured to establish a joint algorithm with the AP, wherein the joint algorithm is used to establish the first address profile and the second address profile and a transition time for the schedule.

Images