Method for changing mac address of wlan affiliated sta of multi-link device

Abstract

A method of changing a MAC address of a WLAN affiliated STA of a multi-link device (MLD), and related systems, devices, and non-transitory machine-readable storage media. A new MAC address is generated for an affiliated non-AP STA of a non-AP MLD. A request to change the MAC address of the affiliated non-AP STA to the new MAC address is sent from the non-AP MLD to an AP MLD. The non-AP MLD receives a response from the AP MLD that the new MAC address of the affiliated non-AP STA of the non-AP MLD has been successfully applied by the AP MLD. In response to the response, the MAC address of the affiliated non-AP STA of the non-AP MLD is changed to the new MAC address.

Description

Technical Field

[0001] This invention relates to communications, and more specifically, to a method for changing the MAC address of a WLAN-affiliated STA in a multi-link device. Background Technology

[0002] The Extremely High Throughput (EHT) task group (TG) recently initiated standardization activities within the IEEE 802.11 WLAN project, known as IEEE 802.11be. IEEE 802.11be introduces a multi-link device (MLD). A multi-link device (MLD) is a logical wireless local area network (WLAN) entity that shares multiple wireless links with another MLD entity. A typical use case is an MLD access point (AP) connecting to a non-AP MLD (e.g., a WLAN terminal or handheld device) using two WLAN wireless links in the 2.4 GHz and 5 GHz WLAN bands. The individual WLAN wireless links are called links, and the radios within the AP MLD are called affiliated APs. The aim is that each affiliated AP can also serve a non-AP station (STA). For example, an AP MLD with a 2.4 GHz wireless link can also function as a traditional AP serving a traditional 802.11ax non-AP STA. In this scenario, the source of the 2.4GHz wireless link is the member AP within the AP MLD. Radios within the non-AP MLD are referred to as member stations (STAs).

[0003] MLD operation differs from the operation of two logical STAs (multi-band clients) within the same physical entity (e.g., two non-AP STAs in the same handheld device). Within an MLD, traffic is coordinated between two links, and a security association is maintained between these two links. This offers several advantages compared to logical (or virtual) STAs. An MLD has more than one affiliated site and a single medium access control (MAC) service access point (SAP) to logical link control (LLC), which includes a MAC data service. MLDs can communicate via parallel transmission over multiple WLAN wireless links between AP MLDs and non-AP MLDs. An AP MLD is an MLD where each STA affiliated with the MLD is also affiliated with an AP. A non-AP MLD is an MLD where each STA affiliated with the MLD is also affiliated with an STA. MLDs allow traffic to flow over any WLAN wireless link with the MLD AP and provide performance gains through the use of multiple channels.

[0004] IEEE 802.11 allows STAs to establish privacy levels for users by periodically changing their MAC addresses (e.g., preventing third-party tracking). However, the MAC address of a member STA should not be changed during the associated lifetime (i.e., when a security association exists between a non-AP MLD and an AP MLD) or during a fast transition (FT), thus limiting user privacy. Summary of the Invention

[0005] This invention provides a method for changing the MAC address of a WLAN-affiliated STA in a multi-link device, as well as related systems, devices, and non-transitory machine-readable storage media.

[0006] When connected to an AP to participate in a LAN, an MLD behaves similarly to a traditional STA. To maintain LAN connectivity, the STA MAC address can only be changed when the IEEE 802.11 STA is not associated; in other words, when there is no security association between the STA and the AP. This invention provides a method for changing the MAC address of a member STA of a non-AP MLD, used by both the member STA and the member AP of the AP MLD associated with the non-AP MLD, without changing the MAC address used by the AP MLD on the LAN to which the AP MLD is joined, and without affecting the LAN connectivity of the AP MLD. This is possible because the MAC address of the member STA is not visible on the LAN. The MAC address of the non-AP MLD is used on the LAN but not for transmitting frames over the air. The MAC address of the member STA is used to transmit frames over the air using a specific link. Therefore, the member STA address of the non-AP MLD can be changed without affecting LAN connectivity. Furthermore, since MLD security is not restricted by the member STA, the MAC address can be changed without affecting any security bindings. This allows the MAC address of the member STA to be changed even when associated with a non-AP MLD. Each member STA of a non-AP MLD can periodically change its MAC address. The non-AP MLD can notify the AP MLD with which it has a security association that the MAC address of its member STA is about to change. The AP MLD can respond with an acknowledgment message, which optionally indicates any error conditions to the non-AP MLD. Therefore, the method of the present invention supports maintaining user privacy for the non-AP MLD without affecting LAN connectivity by periodically changing the MAC address used by each member STA in transit during the associated lifetime and FT period. Without the method of the present invention, the non-AP MLD restricts user privacy by tracking the static MAC addresses of its member STAs after establishing a security association. According to some embodiments of the present invention, the non-AP MLD can request MAC address changes for more than one member non-AP STA. Conversely, in other embodiments of the invention, a member non-AP STA may trigger a MAC address change request for itself and other member non-AP STAs within a public non-AP MLD entity, or a member non-AP STA's MAC address change request may trigger the non-AP MLD entity to trigger other member non-AP STAs to request a change of their MAC address.

[0007] According to a first aspect of the present invention, a method is provided for changing the media access control (MAC) address of a non-AP station (STA) belonging to a wireless local area network (WLAN) of a non-AP multi-link device (MLD), the non-AP MLD including a plurality of belonging non-AP STAs. The non-AP MLD generates a new MAC address for each belonging non-AP STA. The non-AP MLD sends a request to an AP MLD to change the MAC address of the belonging non-AP STA to the new MAC address. The non-AP MLD receives a response from the AP MLD indicating that the new MAC address has been successfully applied by the AP MLD. The non-AP MLD changes the MAC address of the belonging non-AP STA to the new MAC address.

[0008] In some or all examples of the first aspect, the method further includes: the non-AP MLD sending an acknowledgment to the APMLD that the MAC address of the non-AP STA has been successfully modified.

[0009] In some or all of the examples of the first aspect, the confirmation causes the member AP of the AP MLD to use the new MAC address for the member non-AP STA of the non-AP MLD.

[0010] In some or all of the examples of the first aspect, the non-AP MLD generates a new MAC address for the member non-AP STA, including: generating the new MAC address for the member non-AP STA in response to detecting a trigger.

[0011] In some or all of the examples of the first aspect, the trigger is the expiration of a predetermined amount of time since the MAC address of the member non-AP STA was set.

[0012] In some or all of the examples of the first aspect, the triggering is the sending of a predetermined number of frames since the MAC address of the member non-AP STA has been set.

[0013] In some or all of the examples of the first aspect, the predetermined quantity is 1.

[0014] In some or all of the examples of the first aspect, the method further includes: the non-AP MLD monitoring one or more triggers for changing the MAC address of the member non-AP STA.

[0015] In some or all of the examples of the first aspect, the generation, the request, and the change are performed by the non-APMLD.

[0016] In some or all of the examples of the first aspect, the generation, the request, and the change are performed by the non-AP STA belonging to the non-APMLD.

[0017] In some or all of the examples of the first aspect, the monitoring, the generation, and the changes are performed by the non-APMLD.

[0018] In some or all of the examples of the first aspect, the monitoring, the generation, and the changes are performed by the non-AP STA belonging to the non-APMLD.

[0019] In some or all of the examples of the first aspect, the method further includes: the non-AP MLD using the new MAC address to send data between the member non-AP STA and the member AP of the AP MLD.

[0020] In some or all of the examples of the first aspect, the processing of the request by the AP MLD causes the AP MLD to apply the new MAC address change to the mapping of the AP to which the AP MLD belongs.

[0021] According to another aspect of the present invention, a communication device is provided, including a processor, a memory, and a communication subsystem. The memory tangibly stores executable instructions that are executed by the processor. In response to execution by the processor, the executable instructions cause the communication device to perform the methods described above and herein.

[0022] According to another embodiment of the present invention, a non-transitory machine-readable storage medium is provided, which tangibly stores executable instructions for execution by a processor of a computing device. In response to execution by the processor, the executable instructions cause a communication device to perform the methods described above and herein.

[0023] Other aspects and features of the invention will be apparent to those skilled in the art when reading the following description of specific implementations of this application in conjunction with the accompanying drawings. Attached Figure Description

[0024] Figure 1 This is a diagram of a communication system with an MLD architecture provided by the present invention.

[0025] Figure 2 This is a diagram of an MLD with a non-AP MAC address architecture provided by the present invention.

[0026] Figure 3This is a block diagram of an exemplary wireless communication device 100 suitable for providing guidance for practicing the present invention.

[0027] Figure 4 This is a flowchart of a method for changing the MAC address of a STA in a non-AP MLD according to a first embodiment of the present invention.

[0028] Figure 5 This is a message sequence diagram of the message flow between the non-AP MLD and the AP MLD, based on the method of changing the MAC address of the STA belonging to the non-AP MLD in the first embodiment of the present invention.

[0029] Figure 6 This is a diagram of the MAC address change notification frame provided by the present invention.

[0030] Figure 7 This is a diagram of the MLO link subfield format provided by the present invention.

[0031] Figure 8 This is a diagram of the MAC address change response frame provided by the present invention.

[0032] Figure 9 This is a diagram of a MAC address change confirmation frame provided by the present invention.

[0033] Figure 10 This is a flowchart of a method for changing the MAC address of a STA in a non-AP MLD according to a second embodiment of the present invention.

[0034] Figure 11 This is a message sequence diagram of the message flow between the non-AP MLD and the AP MLD, based on the method of changing the MAC address of the STA belonging to the non-AP MLD in the second embodiment of the present invention. Detailed Implementation

[0035] This invention is made with reference to the accompanying drawings, which illustrate embodiments. However, many different embodiments may be used, and therefore the description should not be construed as limiting oneself to the embodiments set forth herein. Rather, these embodiments are provided to make this application thorough and complete. Where possible, the same reference numerals are used in the drawings and the following description to refer to the same elements, and prime number notation is used in alternative embodiments to indicate the same elements, operations, or steps. The separate blocks or separations of functional elements of the illustrated systems and devices do not necessarily require physical separation of these functions, as communication between these elements can occur without any such physical separation via message passing, function calls, shared memory spaces, etc. Therefore, although functions are shown separately herein for ease of explanation, these functions do not need to be implemented in physically or logically separated platforms. Different devices may have different designs such that while some devices implement some functions in fixed-function hardware, others may implement those functions in a programmable processor with code available from a machine-readable storage medium. Finally, elements mentioned in the singular may be plural, and vice versa, unless the context explicitly or inherently indicates otherwise.

[0036] The IEEE 802.11-2020 standard, released in December 2020, describes privacy and MAC address issues and stipulates that MAC addresses cannot be changed during their associated lifetime. The contents of IEEE 802.11-2020 are incorporated herein by reference.

[0037] The IEEE P802.11be D1.0, released in May 2021, describes the latest information on multi-link devices (MLDs) and multi-link operation (MLO). The contents of IEEE P802.11be D1.0 are incorporated herein by reference.

[0038] For convenience, the terms message, frame, and message frame can be used interchangeably in this invention.

[0039] The multi-link device in this invention can be a single-antenna device or a multi-antenna device. A multi-link device has a MAC address for coordinating different radios operating simultaneously. A multi-link device can have multiple radios capable of operating simultaneously on different channels in the same or different frequency bands. This invention is not limited to any number of antennas or radios in the multi-link device. A multi-link device can support the transmission of services of the same access type on different links, and even support the transmission of the same data packets on different links. Alternatively, services of the same access type cannot be transmitted on different links, but services of different access types can be transmitted on different links.

[0040] refer to Figure 1 The following describes a communication system 10 having the multi-link device architecture provided by the present invention. The communication system 10 includes an AP MLD 12 connected to a wired local area network (LAN) 30. The AP MLD 12 generates a wireless local area network (WLAN) 40 through which it communicates with a non-AP MLD 20 (e.g., a handheld device). As described above, the non-AP MLD 20 supports parallel transmission on multiple links, providing higher transmission efficiency and higher throughput compared to communication devices that only support single-link transmission. The AP MLD 12 includes subordinate APs 14 and 16 operating, for example, at 2.4 GHz and 5 GHz, respectively. The non-AP MLD 20 includes subordinate STAs 24 and 26 operating, for example, at 2.4 GHz and 5 GHz, respectively. WLAN wireless links (hereinafter referred to as "links") are formed between the STAs belonging to non-AP MLD 12 and the APs belonging to AP MLD 12 (e.g., a link between STA 24 and AP 14, or a link between STA 26 and AP 16). STAs 24 and 26 are logical sites operating on separate links within an MLD.

[0041] Now for reference Figure 2 This section describes an MLD with the non-AP MAC address architecture provided by this invention. The non-AP MLD 20 comprises three logical entities: the non-AP MLD 20 itself and two subordinate STAs 24 and 26. Subordinate STAs 24 and 26 comprise radios, and the non-AP MLD 20 comprises a MAC layer portion and an upper-level station management entity (SME) within the non-AP MLD 20. All three entities have MAC addresses, represented as MAC... ML MAC A1 and MAC A2 .

[0042] A robust security network association (RSNA) can be established between AP MLD 12 and non-AP MLD 20. Each link between AP MLD 12 and non-AP MLD 20 is formed between the STAs belonging to non-AP MLD 20 and the APs belonging to AP MLD 12. Links including those belonging to STAs 24 and 26 of non-AP MLD 20 are transparent (invisible) to the MLD RSNA. Although the security association (SA) is handled by non-AP MLD 20, only the MAC address is used. ML Used as an identifier for the security association. Accordingly, from the LAN's perspective, LAN 30 only sees the MAC address at non-AP MLD 20. ML MAC address belonging to STA A1 and MAC A2 It is not part of the MLD Security Alliance and will not be seen by LAN 30. When non-AP MLD 20 connects to AP MLD 12 to communicate in a LAN environment, the MAC address of non-AP MLD 20 is... ML This indicates non-AP MLD 20 on LAN 30.

[0043] Figure 3This is a block diagram of an exemplary wireless communication device 100, which is adapted to provide an MLD for practicing the instructions of this invention as an AP MLD 12 or a non-AP MLD 20. The wireless communication device 100 includes a processing system comprising a processor 104 (e.g., a microprocessor or central processing unit (CPU)) that controls the overall operation of the computing device 100. The processing system may include one or more other types of processors coupled to the processor 104, such as a graphics processing unit (GPU), a tensor processing unit (TPU), a neural processing unit (NPU), an application-specific integrated circuit (ASIC), or a field-programmable gate array (FPGA), for offloading certain computational tasks. The processor 104 is coupled to multiple components via a communication bus (not shown), which provides communication paths between the components and the processor 104. The processor 104 is coupled to one or more non-transitory machine-readable storage media (“memory”) 108 and a communication subsystem 110, the one or more non-transitory machine-readable storage media including random access memory (RAM), read-only memory (ROM) and persistent (non-volatile) memory such as flash memory.

[0044] The communication subsystem 110 may include a baseband processor or other circuitry for implementing a media access controller, physical layer, transmit amplifier, and RF antenna required for communication over a wireless medium. The communication subsystem 110 typically includes at least two stations (STAs) for exchanging radio frequency signals in parallel with the wireless local area network 40 according to IEEE 802.11be. IEEE 802.11be also supports the inclusion of one STA in the communication subsystem 110. In some embodiments, the communication subsystem 110 may include more than two STAs. STAs include wireless transceivers. The communication subsystem 110 may also include a wired transceiver for wired communication with a wired network (e.g., wired LAN 30). The communication subsystem 110 may also include one or a combination of a Bluetooth transceiver or other short-range wireless transceiver or a wireless wide area network (WWAN) transceiver (e.g., a cellular transceiver for communication with a wireless access network (e.g., a cellular network)). The cellular transceiver may communicate with any of a plurality of fixed transceiver base stations of the cellular network within its geographic coverage area.

[0045] Memory 108 stores various instructions and data that can be executed by a processing system, some of which may take the form of an application program that can be executed by the processing system. Executable instructions and data, which may be in the form of system software, software modules, device-specific applications, or portions thereof, may be temporarily loaded into RAM during execution. Communication signals received by wireless communication device 100 may also be stored in RAM. While specific functions of various types of memory have been described, this is only one embodiment, and different functional allocations to memory types may be used in other embodiments.

[0046] The wireless communication device 100 may include an internal power source, such as a battery (not shown), depending on the type of wireless communication device 100. For example, the wireless communication device 100 may include one or more rechargeable batteries that can be charged, for example, via a charging circuit coupled to a battery interface (e.g., a serial data port). The battery provides power to at least some components of the wireless communication device 100, and the battery interface (not shown) provides mechanical and electrical connections to the battery. Alternatively, the wireless communication device 100 may include an external power source.

[0047] Now for reference Figure 4 and Figure 5 The method 400 for changing the MAC address provided in the first embodiment of the present invention will be described. Figure 4 This is a flowchart of the method 400 provided in the first embodiment of the present invention. Figure 5 This is a message sequence diagram of the message flow provided in the first embodiment of the present invention. Figure 5 The solid line in the middle represents over-the-air (OTA) messages, while Figure 5 The dashed lines in the diagram represent internal messages between MLDs. Frames (messages) sent between MLDs can be transmitted via any link. Method 400 is performed by non-AP MLD 20 and AP MLD 12. At least a portion of method 400 can be performed by software executed by non-AP MLD 20 and AP MLD 12, its processor 104, and / or communication subsystem 110.

[0048] In Operation 402, the non-AP MLD 20 monitors triggers to change the MAC address of one or more of the affiliated STAs 24 and 26 from one or more pre-defined triggers. Triggers can be time-based or event-based. For example, when a trigger is time-based, it can be the expiration of a predetermined amount of time since the affiliated STA's MAC address was set, such as a predetermined periodic interval. The expiration of the predetermined amount of time can be monitored by a timer (e.g., a countdown timer). The predetermined amount of time can be minutes or seconds. The predetermined amount of time can be configured based on the privacy settings of the non-AP MLD 20. In another example, when a trigger is event-based, it can be sending a predetermined number of frames since the affiliated STA's MAC address was set. The predetermined number of frames can be as few as one frame, causing the non-AP MLD 20's MAC address to change every frame. The smaller the time-based or event-based interval between MAC address changes, the greater the privacy provided.

[0049] In Operation 404, non-AP MLD 20 detects a trigger from one or more predetermined triggers.

[0050] In Operation 406, in response to a detected trigger, non-AP MLD 20 generates a new MAC address for one or more of the member STAs 24 and 26. It is possible that not all MAC addresses of all member STAs will change, or that they will change simultaneously.

[0051] In operation 408, non-AP MLD 20, for example, notifies AP MLD 12 of the new MAC addresses belonging to STAs 24 and 26 by sending a MAC address change notification frame. The following section combines... Figure 6 and Figure 7 This describes an example of a MAC address change notification frame. The MAC address change notification frame is shown in the message sequence diagram. Figure 5 In this context, it is represented as MAC-ADDR-Change-Notif(MLO link(link ID, newMACAddr)1、……MLO link(link ID, newMACAddr) n For 1...n, where n is the number of non-AP MLD 20 member STAs requesting a change of MAC address, link ID is the identifier of the link of each member STA, and newMACAddr is the proposed new MAC address.

[0052] In operation 410, AP MLD 12 receives a MAC address change notification frame from non-AP MLD 20 and forwards the MAC address change to subordinate APs 14 and 16, thereby instructing these subordinate APs to update their mappings to the MAC addresses of subordinate APs 24 and 26. In some cases, if AP MLD 12 determines that a MAC address change is inappropriate, AP MLD 12 may not forward the MAC address change to the subordinate APs. Forwarding a MAC address change involves sending a MAC address change frame from AP MLD 12 to subordinate APs 14 and 16. The MAC address change frame is described in the message sequence diagram (…). Figure 5 In this context, it is represented as MAC-ADDR-Change(newMACAddr), where newMACAddr is the new MAC address. A MAC address change frame instructs member APs 14 and 16 to update their mapping of MAC addresses with member STAs 24 and 26. Applying a MAC address change also includes, for example, notifying AP MLD12 by sending a MAC address change response frame when the link mapping between member APs 14 and 16 and member STAs 24 and 26 has been successfully changed. For example, when a requested MAC address change from member STAs 24 and 26 has not yet been applied, AP MLD12 may respond to non-AP MLD20 with a success status, or it may respond with an alternative status (e.g., failure) instead of success. A MAC address change may fail for several reasons, such as if the proposed MAC address is unsuitable for AP MLD12 or member APs 14 and 16 for some reason (e.g., already used by another device). An alternative state allows a non-AP MLD 20 to retry the MAC address change; in this case, the operation proceeds to Operation 406. The MAC address change response frame is shown in the message sequence diagram (…). Figure 5 This is represented as MAC-ADDR-Change-ACK (status), where the status is the MAC address change, i.e., success or failure. The decision to update the link mapping of the MAC address belonging to the STA can be made by AP MLD 12, or by one or more of APs 14 and 16.

[0053] In operation 412, AP MLD 12 notifies non-AP MLD 120 that the link mapping of the MAC addresses belonging to STAs 24 and 26 has been successfully changed by APs 14 and 16 belonging to AP MLD 20. For example, by sending a MAC address change acknowledgment frame to non-AP MLD 20, non-AP MLD 120 is notified that the MAC address has been applied and acknowledged by AP MLD 12.

[0054] It should be understood that AP MLD 12 can respond with a status code indicating a halt to MAC address changes or information about how MAC address changes should be performed (e.g., providing information about local address management). For a halt to MAC address status code, the MAC address change response frame can include a status other than success. If the status is not success (e.g., failure), a non-AP MLD 20 can attempt to determine a new address. This can happen if AP MLD 12 detects a duplicate MAC address on LAN 30 or in another subordinate AP. It can also detect invalid MAC addresses, such as broadcast addresses. In some cases, such as in enterprise environments, MAC addresses may have to be within a certain address range, which could be a reason to reject the address. Alternatively, the status code could be a status code about using local address management, such as DENIED_LOCAL_MAC_ADDRESS_POLICY_VIOLATION. In the current standard, APs are able to advertise MAC address policies, and APs can refuse association when a STA uses a MAC address that does not conform to the policy. For information about how MAC address changes should be performed, optional subfields, such as variable-length local management information, can be added to the MAC address change response frame. Figure 8 In this case, the MAC address change response frame (MAC address change response frame) indicates information about local address management. Figure 8 A leading "length" subfield will be required so that the received frame can be parsed correctly.

[0055] In operation 414, non-AP MLD 20, in response to receiving a MAC address change acknowledgment frame, applies a MAC address change to its subordinate STAs 24 and 26. Applying the MAC address change involves sending a MAC address change frame from non-AP MLD 20 to its subordinate STAs 24 and 26. This MAC address change frame instructs subordinate STAs 24 and 26 to update the MAC addresses of their subordinate STAs. Applying the MAC address change also includes subordinate STAs 24 and 26 notifying non-AP MLD 20, for example, by sending a MAC address change acknowledgment frame, when the MAC addresses of their subordinate STAs have been successfully changed. In some cases, the MAC address change may fail, as indicated by a failure (or alternative) status within the MAC address change acknowledgment frame. Non-AP MLD 20 has now completed the link mapping update.

[0056] In operation 416, optionally, non-AP MLD 20 notifies AP MLD 12 that the MAC address of the affiliated STA has been successfully changed, for example, by sending a MAC address change confirmation frame to AP MLD 12. The MAC address change confirmation frame is shown in the message sequence diagram (…). Figure 5 In this context, it's represented as MAC-ADDR-Change-Confirm (status), where the status indicates the MAC address change, i.e., success or failure. A MAC address change confirmation frame can be used to complete the MAC address change and trigger AP MLD 12 and non-AP MLD 20 to use the new MAC address. The existing MAC address can continue to be used by AP MLD 12 and non-AP MLD 20 to allow MLD traffic flow, while... Figure 5 The message sequence is being executed. Once the message sequence is complete, the new MAC address will be used. Therefore, all entities within the MLD can store both the existing and new MAC addresses until a switching signal is sent.

[0057] Figure 6 This is a diagram of a MAC address change notification frame provided by the present invention. The MAC address change notification frame is sent from non-AP MLD 20 to AP MLD 12 to indicate that the MAC address of the affiliated STA has requested a change. The MAC address change notification frame can be an action frame, a protected action frame, or a LAN-based extended authentication protocol (EAP) data frame similar to a tunneled direct link setup (TDLS) frame. Alternatively, the MAC address change can be performed on a TDLS link with the same message passing. Those skilled in the art will understand that TDLS is a direct connection between two non-AP MLD 20s associated with the same AP MLD 12. TDLS communication is transmitted directly between TDLS peers without passing through the AP. TDLS key derivation is bound (i.e., used in key derivation) to the MAC address of the affiliated non-AP STA of the TDLS peer. If the MAC address change is for a member STA operating on a TDLS link, the non-AP MLD 20 will negotiate the MAC address change with the TDLS peer and AP MLD 12. After the MAC address change negotiation is complete, the TDLS peer will negotiate a new TDLS peer key. The key derivation protocol invoked is defined and well-known in the art. The MAC address change message passing will be identical.

[0058] For example, the category field value can be 30 to indicate privacy. If wireless network management (WNM) notifications are used in other examples, the category field value might be 10, as described below. In such other examples, non-AP MLD 20 sends a WNM notification request (category field = 10; action field = 26; type = 3 (MLO address update)), and AP MLD 12 sends a WNM notification response (category = 10; action field = 26; type = 3 (MLO address update)) – other message elements will be the same as a MAC address change notification. The address update action field value options are: value 0 indicates the frame is a notification frame, value 1 indicates the frame is a response frame, and value 2 indicates the frame is an acknowledgment frame. The session token field may have variable values. The session token is unique for a transaction, but may be the same for request / response / acknowledgment frames / messages within the transaction. The link number field value is an integer representing the link number. The MLO link field is described below. Figure 7 This is a diagram of the MLO link subfield format provided by the present invention. The value of the link ID subfield corresponds to the link identifier of the member STA link with the MAC address. The value of the MAC address subfield corresponds to the requested MAC address. A MAC address change notification frame can be used to request a MAC address change for more than one member STA. In this case, the MAC address change notification frame includes data for each member STA with the requested MAC address change.

[0059] Figure 8 This is a diagram of a MAC address change response frame provided by the present invention. For example, the value of the category field can be 30 to indicate privacy. The value of the address update action field is 1, indicating that the frame is a response frame. The session token field is set to the value received in the MAC address change notification frame. The value of the status field corresponds to the status code of the response notification, such as "success" indicating that the MAC address change was successful, and "failure" indicating that the MAC address change was unsuccessful.

[0060] Figure 9 This is a diagram of a MAC address change confirmation frame provided by the present invention. For example, the value of the category field can be 30 to indicate privacy. The value of the address update action field is 2, indicating that the frame is a confirmation frame. The session token field can be set to the value received in the MAC address change response frame. The value of the status field corresponds to the status code of the response notification, such as "success" indicating that the MAC address change was successful, and "failure" indicating that the MAC address change was unsuccessful.

[0061] According to method 400, the establishment of the pairwise transient key security association (PTKSA) between non-AP MLD 20 and AP MLD 12 is performed by the MLD entity. The establishment of the PTKSA is outside the scope of this invention and will not be discussed further here.

[0062] As an alternative to using new action frames or EAPoL data frames, MAC address changes can be performed on TDLS links with the same message passing. If the MAC address change is for a member STA operating on the TDLS link, the non-APMLD 20 will negotiate the MAC address change with the TDLS peer and the AP MLD. After the MAC address change negotiation is complete, the TDLS peer will negotiate a new TDLS peer key.

[0063] As an alternative to defining new action frames with privacy categories, wireless network management (WNM) notification request / response frames (i.e., notification / acknowledgment frames) can be used according to IEEE 802.11v. The payloads of the notification and response frames will remain unchanged.

[0064] Now for reference Figure 10 and Figure 11 The method 450 for changing the MAC address provided in the second embodiment of the present invention will be described below. Figure 10 This is a flowchart of method 500 provided in the second embodiment of the present invention. Figure 11 This is a message sequence diagram of the message flow provided in the second embodiment of the present invention. Figure 11 The solid lines in the middle represent OTA messages, while Figure 11The dashed lines in the diagram represent internal messages between MLDs. Frames (messages) sent between MLDs can be transmitted via any link. Method 450 is performed by non-AP MLD 20 and AP MLD 12. At least a portion of method 400 can be performed by software executed by non-AP MLD 20 and AP MLD 12, the STA belonging to non-AP MLD 20, the AP belonging to AP MLD 12, its processor 104, and / or the communication subsystem 110. The second embodiment is similar to the first embodiment, except that the STA belonging to non-AP MLD 20, 24 or 26, instead of non-AP MLD 20 itself, causes a MAC address change and notifies the corresponding AP belonging to AP MLD 12, 14 or 16, via the corresponding link. Method 450 appears the same or substantially similar in the air, but differs in the internal messages between the elements (e.g., stations) of MLDs 12 and 20. PTKSA is still established between non-AP MLD 20 and AP MLD 12, so the notification frame originates from the subordinate STA 24 or 26, but is sent as a link-specific notification to the corresponding subordinate AP 14 or 16, as described below.

[0065] In operation 452, each subordinate STA 24, 26 of the non-AP MLD 20 monitors triggers to change its MAC address from one or more predetermined triggers. Triggers can be time-based or event-based. For example, when a trigger is time-based, it can be the expiration of a predetermined amount of time, such as a predetermined period interval. The expiration of the predetermined amount of time can be monitored by a timer (e.g., a countdown timer). The predetermined amount of time can be minutes or seconds. The predetermined amount of time can be configured based on the privacy settings of the non-AP MLD 20. In another example, when a trigger is event-based, it can be sending a predetermined number of frames. The predetermined number of frames can be as few as one frame, causing the MAC address of the non-AP MLD 20 to change every frame. The smaller the time-based or event-based interval between MAC address changes, the greater the privacy provided.

[0066] In operation 454, one of the detections of non-AP MLD 20 belonging to STA24, 26 comes from one or more predetermined triggers.

[0067] In operation 456, in response to the detection of a trigger, one of the subordinate STAs 24 and 26 of the non-AP MLD 20 that detected the trigger generates a new MAC address for itself and optionally one or more other subordinate STAs 24 and 26. It will be understood that a subordinate STA can generate a new MAC address for any one or more other subordinate STAs in the non-AP MLD 20, even if a trigger has not yet been detected for those subordinate STAs. A subordinate non-AP STA can trigger a MAC address change request for itself and other subordinate non-AP STAs within the public non-AP MLD entity, or a MAC address change request from a subordinate non-AP STA can trigger the non-AP MLD entity to trigger other subordinate non-AP STAs to request a change of their MAC addresses. In this example, for simplicity, only the MAC address of one subordinate STA is changed. There may be situations where not all MAC addresses of all subordinate STAs are changed, or that they are changed simultaneously.

[0068] In operation 458, the member STA 24 or 26 of non-AP MLD 20 notifies the member AP 14 or 16 of AP MLD 12, corresponding to that member STA, that it is requesting a MAC address change, for example, by sending a MAC address change notification frame. The MAC address change notification frame is shown in the message sequence diagram (…). Figure 11 In this context, it's represented as MAC-ADDR-Change-Notif(AF_AP, AF_STA, newMACAddr), where AF_AP and AF_STA represent the destination (AF_AP), the source (AF_STA), and newMACAddr is the new MAC address. For multi-link operations, the member STA can communicate with the member AP, but not directly. Instead, the member STA sends the frame to the AP MLD 12 via non-AP MLD 20, and then the AP MLD 12 sends the frame to the member AP. The resulting path is: Member STA -> non-AP MLD -> Frame Transmission OTA -> AP MLD -> Member AP.

[0069] In Operation 460, the member AP 14 or 16 receives a MAC address change notification frame and applies the MAC address change to update its link mapping.

[0070] In operation 462, when the link mapping of the MAC address of a member STA 24 or 26 has been successfully changed, the member AP 14 or 16 notifies the member STA 24 or 26 of non-AP MLD 20, for example, by sending a MAC address change acknowledgment frame. For example, if the MAC address change for member STA 24 or 26 has not yet been applied, the member AP 14 or 16 may respond with a success status, or it may respond with an alternative status (e.g., failure) instead of a success status. The MAC address change may fail for several reasons, such as if the proposed MAC address is not suitable for AP MLD 12 or member AP 14 or 16 for some reason (e.g., already used by another device). An alternative status allows member STA 24 or 26 to retry the MAC address change; in this case, the operation proceeds to operation 456. The MAC address change acknowledgment frame is shown in the message sequence diagram (…). Figure 11 In this context, it's represented as MAC-ADDR-Change-ACK (success), where the status indicates the MAC address change, i.e., success or failure. The subordinate AP sends the frame to the non-AP MLD 20 via AP MLD 12, and then the non-AP MLD 20 sends the frame to the subordinate STA. The resulting path is: subordinate AP -> APMLD -> frame transmission OTA -> non-AP MLD -> subordinate STA. As mentioned above, the subordinate AP can also respond with a status code indicating that MAC address changes have been stopped or information about how to perform MAC address changes.

[0071] In operation 464, in response to receiving a MAC address change acknowledgment frame, member STA 24 or 26 applies a MAC address change.

[0072] In operation 466, optionally, the subordinate STA 24 or 26 notifies the subordinate AP 14 or 16 that the MAC address of the non-STA AP has been successfully changed, for example, by sending a MAC address change acknowledgment frame to the subordinate AP 14 or 16. The subordinate STA sends the frame to AP MLD 12 via non-AP MLD 20, and then AP MLD 12 sends the frame to the subordinate AP, resulting in the following path: subordinate STA -> non-AP MLD -> frame transmission OTA -> AP MLD -> subordinate AP. The MAC address change acknowledgment frame is shown in the message sequence diagram (…). Figure 11In this context, it is represented as MAC-ADDR-Change-Confirm(AF-AP, AF-STA, Status), where Status indicates the MAC address change status, i.e., success or failure. MAC address change confirmation frames can be used to complete a MAC address change and trigger affiliated AP 14 or 16 and affiliated STA 24 or 26, as well as AP MLD 12 and non-AP MLD 20 to use the new MAC address.

[0073] While the above embodiments relate to WLAN, it is worth noting that the guidance of this invention can be extended to WWAN, such as cellular networks.

[0074] The steps and / or operations in the flowcharts and accompanying drawings described herein are for illustrative purposes only. These steps and / or operations can be varied in many ways without departing from the guidance of this invention. For example, steps may be performed in a different order, or steps may be added, deleted, or modified as appropriate.

[0075] Overview

[0076] In light of the present invention, the software code used to perform the described methods is within the scope of those skilled in the art. Machine-readable code that can be executed by one or more processors of one or more corresponding devices to perform the described methods can be stored in a machine-readable storage medium such as the memory of a data manager. The terms "software" and "firmware" are interchangeable in this invention and include any computer program stored in memory for execution by a processor, including random access memory (RAM), read-only memory (ROM), EPROM, electrically EPROM (EEPROM), and non-volatile RAM (NVRAM). The above memory types are merely examples and therefore do not limit the types of memory that can be used to store computer programs.

[0077] All values ​​and subranges within the scope of the disclosure are also disclosed. Furthermore, while the systems, devices, and processes disclosed and illustrated herein may include a specific number of elements, these systems, devices, and components may be modified to include more or fewer such elements. Although several exemplary embodiments are described herein, modifications, adaptations, and other implementations are possible. For example, elements shown in the accompanying drawings may be replaced, added, or modified, and the exemplary methods described herein may be modified by replacing, reordering, or adding steps of the disclosed methods.

[0078] Features from one or more of the above embodiments can be selected to create alternative embodiments consisting of sub-combinations of features that may not be explicitly described above. Furthermore, features from one or more of the above embodiments can be selected and combined to create alternative embodiments consisting of combinations of features that may not be explicitly described above. Features suitable for such combinations and sub-combinations will be apparent to those skilled in the art when reviewing the invention as a whole.

[0079] Furthermore, numerous specific details are set forth to provide a thorough understanding of the exemplary embodiments described herein. However, those skilled in the art will understand that the exemplary embodiments described herein can be practiced without these specific details. Moreover, well-known methods, processes, and elements have not been described in detail so as not to obscure the exemplary embodiments described herein. The subject matter described herein and in the cited claims is intended to cover and encompass all appropriate technical changes.

[0080] Although the invention has been described, it will be understood, at least in part, by those skilled in the art, that the invention also relates to various elements for performing at least some aspects and features of the described methods by means of hardware, software, or a combination thereof. Therefore, the technical solutions of the invention can be embodied in non-volatile or non-transitory machine-readable storage media (e.g., optical discs, flash memory, etc.) on which executable instructions tangibly stored thereon are stored, enabling processing devices to perform examples of the methods disclosed herein.

[0081] The term "database" can refer to a data volume, a relational database management system (RDBMS), or both. As used herein, a database can include any collection of data, including hierarchical databases, relational databases, flat file databases, object-relational databases, object-oriented databases, and any other structured records or data collection stored in a computer system. The examples above are merely illustrative and are not intended to limit the definition and / or meaning of the terms "processor" or "database" in any way.

[0082] The invention may be practiced in other specific forms without departing from the subject matter of the claims. The exemplary embodiments described are to be regarded in all respects as illustrative rather than restrictive. The invention is intended to cover and encompass all suitable technical changes. Therefore, the scope of the invention is described by the appended claims rather than by the foregoing description. The scope of the claims should not be limited to the embodiments set forth in the examples, but should be given the broadest interpretation consistent with the entire description.

Claims

1. A method for changing the Media Access Control (MAC) address of a non-AP (Multi-Link Device) wireless local area network (WLAN) belonging to a non-AP (Stationary Access Point) STA, characterized in that, The non-AP MLD includes multiple non-AP STAs, and the method includes: The non-AP MLD generates a new MAC address for the member non-AP STA; The non-AP MLD sends a request to the AP MLD to change the MAC address of the non-AP STA to the new MAC address; The non-AP MLD receives a response from the AP MLD confirming that the new MAC address has been successfully applied by the AP MLD; The non-AP MLD changes the MAC address of the non-AP STA to the new MAC address.

2. The method according to claim 1, characterized in that, The method further includes: The non-AP MLD sends a confirmation to the AP MLD that the MAC address of the non-AP STA has been successfully modified.

3. The method according to claim 1 or 2, characterized in that, The non-AP MLD generates a new MAC address for the member non-APSTA, including: In response to the detection of a trigger, the new MAC address is generated for the member non-AP STA.

4. The method according to claim 3, characterized in that, The trigger is the expiration of a predetermined amount of time since the MAC address of the member non-AP STA was set.

5. The method according to claim 3, characterized in that, The trigger is the sending of a predetermined number of frames since the MAC address of the member non-AP STA has been set.

6. The method according to claim 5, characterized in that, The predetermined quantity is 1.

7. The method according to claim 3, characterized in that, The method further includes: The non-AP MLD monitoring is used to change one or more triggers of the MAC address belonging to the non-AP STA.

8. The method according to claim 1 or 2, characterized in that, The method further includes: The non-AP MLD uses the new MAC address to send data between the non-AP STA and the AP to which the AP MLD belongs.

9. A non-access point (non-AP) multi-link device (MLD), characterized in that, The non-AP MLD includes: processor; A communication subsystem coupled to the processor, wherein the communication subsystem includes multiple affiliated non-AP sites (STAs); Memory coupled to the processor; The processor is used to implement the method as described in any one of claims 1-8.

10. A non-transitory machine-readable storage medium, characterized in that, The non-transitory machine-readable storage medium tangibly stores executable instructions executed by a processor of a non-AP multi-link device (MLD), the non-AP MLD including a processor and a communication subsystem coupled to the processor, the non-AP MLD including a plurality of affiliated non-AP sites (STAs), wherein, in response to execution by the processor, the executable instructions cause the non-AP MLD to implement the method as described in any one of claims 1-8.

Images