State feedback during 4 handshakes

Abstract

Various embodiments provide a method and apparatus for state feedback in a 4 handshake process. In an embodiment, a method performed by a first wireless device includes receiving a first message from a second wireless device, the first message including identification information of the second wireless device; determining state information at least based on the identification information, wherein the state information indicates feedback of the first message; and transmitting the state information to the second wireless device in a four-way handshake message in a four-way handshake process between the first wireless device and the second wireless device.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to wireless communication, and in particular, to methods and apparatuses for status feedback in a four-way handshake process. Background Art

[0002] Management Frame

[0003] Management frames are important components for Wi-Fi networks. As the name implies, management frames manage connections between wireless devices (e.g., wireless stations (STAs) going to / from an access point (AP) or STAs going to / from STAs). Management frames provide certain functions, such as scanning / discovery, authentication, association, roaming, and disconnection, etc. The current 802.11-2020 standard defines 14 different types of management frames, including beacon frames, probe response / request frames, authentication / deauthentication frames, association request / response frames, disassociation frames, reassociation request / response frames, and action frames, etc.

[0004] Status Code and Reason Code

[0005] The management frame body has at least one of two specific fields, namely, the status code field and the reason code field as Figure 1 shown. The status code field is used in response management frames to indicate the success or failure of the requested operation. The reason code field is used to indicate the reasons for unsolicited notification management frames of disassociation, deauthentication, and some other frame types.

[0006] Depending on the operation, status codes and / or reason codes can be inserted into specific management frames. Currently, 802.11REVme_D1.3 defines 129 status codes (see Table 9.78 in 802.11REVme_D1.3) and approximately 70 reason codes (see Table 9.77 in 802.11REVme_D1.3).

[0007] As an example, the Simultaneous Authentication of Equals (SAE) authentication protocol utilizes authentication frames. Since authentication frames are management frames, status codes / reason codes can be used in their frame bodies. During the SAE authentication process, if the operation experiences some problems, these problems can be indicated by the corresponding status codes. Table 1 shows some examples of status codes used in authentication frames for the SAE authentication protocol. Table 1

[0008] As another example, the Pairwise Master Key Identifier (PMKID) is used in the (re)association frame or the Fast Initial Link Setup (FILS) authentication frame. Since the association frame and the authentication frame are management frames, the association frame and the authentication frame can use the status code / reason code field in their frame body. Similarly, if a problem occurs with the PMKID operation, the problem can be stated by the status code / reason code in the association frame. Tables 2 and 3 show some examples of the status code and the reason code being used in the association frame / authentication frame for the PMKID. Table 2 Table 3

[0009] 4-Way Handshake (HS)

[0010] The 4-Way Handshake (HS) is a security association management protocol that was first defined in Amendment 802.11i in 2004 and then adopted into the 802.11 standard. The 4-Way HS protocol uses the IEEE 802.1X EAPOL key frame. The original purpose of the 4-Way HS was to establish the necessary security keys between the STA and the AP. After the security keys are established in the 4-Way HS (i.e., after the successful completion of generating and verifying the security keys), the STA and the AP can start data communication. Figure 2 FIG. shows a signaling flow diagram illustrating the association process between the STA and the AP. The association process may include an attachment process and a 4-Way HS process. Note that the 4-Way Handshake occurs only after a successful attachment process between the STA and the AP (i.e., after a successful authentication and association frame exchange). Generally, the attachment process may include a probe request / response exchange, an authentication request / response exchange, and an association request / response exchange. In addition, the 4-Way HS includes 4 messages (i.e., Msg1, Msg2, Msg3, Msg4) that are sent between the STA and the AP. Each of these messages carries relevant information depending on the purpose. Figure 3 FIG. shows the general frame format for the 4-Way Handshake message, i.e., the EAPOL key frame format.

[0011] In addition, the original intention of the 4-way HS was to generate / validate a security key for encryption. However, in addition to security key generation / validation, the 4-way HS is becoming a more popular choice for including management operations because a part of the frame body of the 4-way HS message can be encrypted, and key information (such as an identifier (ID), a media access control (MAC) address, related parameters, a key) can be securely (i.e., encrypted) carried in the 4-way HS. However, the frame bodies of most management frames cannot be encrypted, and key information is almost always carried unencrypted in probe requests / responses, authentication requests / responses, and association requests / responses.

[0012] More specifically, key information can be encrypted as something called key data encapsulation (KDE) in the key data field of the 4-way HS message, as Figure 3 shown.

[0013] Currently, as Figure 4a shown, 802.11REVme_D1.3 defines 15 KDEs. Note that some of these KDEs are for security keys (such as group temporal key (GTK), integrity GTK (IGTK), beacon IGTK (BIGTK), wake-up radio IGTK (WIGTK)), some of these KDEs are for identifiers (e.g., PMKID, key ID), some of these KDEs are for related parameters and information (e.g., nonce, error, operating channel information (OCI)), one of these KDEs is for the MAC address, and some of these KDEs are reserved for future use. As Figure 4b shown, some working groups (802.11bh and 802.11be) also propose adding more KDEs related to their working directions.

[0014] From the perspective of the 802.11 standard, 4-way handshake messages are considered data frames rather than management frames, even though they can act like "management frames". Therefore, 4-way HS messages do not have a status code / reason code in their frame bodies. The lack of a status code / reason code in the frame body of the 4-way HS message causes some operations not to establish a feedback mechanism. SUMMARY OF THE INVENTION

[0015] The present invention content is provided to introduce a simplified concept of status feedback in the 4-way handshake process. The present invention content is not intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0016] According to a first aspect of the present disclosure, a first wireless device is provided. The first wireless device includes: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the first wireless device to at least: receive a first message from a second wireless device, the first message including identification information of the second wireless device; determine status information at least based on the identification information, the status information indicating feedback on the first message; and transmit the status information to the second wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device.

[0017] According to a second aspect of the present disclosure, a second wireless device is provided. The second wireless device includes: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the network entity to at least: transmit a first message to the first wireless device, the first message including identification information of the second wireless device; receive status information from the first wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device, the status information indicating feedback on the first message; and determine an operation based on the status information.

[0018] According to a third aspect of the present disclosure, a method performed by a first wireless device is provided. The method includes: receiving a first message from a second wireless device, the first message including identification information of the second wireless device; determining status information at least based on the identification information, the status information indicating feedback on the first message; and transmitting the status information to the second wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device.

[0019] According to a fourth aspect of the present disclosure, a method performed by a second wireless device is provided. The method includes: transmitting a first message to the first wireless device, the first message including identification information of the second wireless device; receiving status information from the first wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device, the status information indicating feedback on the first message; and determining an operation based on the status information.

[0020] According to a fifth aspect of the present disclosure, a first wireless device is provided. The first wireless device includes components for performing the steps of any of the methods described in the third aspect.

[0021] According to a sixth aspect of the present disclosure, a second wireless device is provided. The second wireless device includes components for performing the steps of any of the methods described in the fourth aspect.

[0022] According to a seventh aspect of the present disclosure, there is provided a computer-readable medium including program instructions which, when executed by a device, cause the device to execute any of the methods according to the third or fourth aspect.

[0023] According to an eighth aspect of the present disclosure, there is provided a computer program product including program instructions which, when executed by at least one processor, cause the at least one processor to execute any of the methods according to the third or fourth aspect.

[0024] It should be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Some example embodiments will now be described with reference to the drawings, in which:

[0026] Figure 1 is a schematic diagram showing a management frame;

[0027] Figure 2 is a schematic diagram showing a signaling flow of a four-way handshake;

[0028] Figure 3 is a diagram showing a frame format for four-way handshake messages;

[0029] Figure 4a shows a KDE as defined in 802.11REVme_D1.3;

[0030] Figure 4b shows a KDE proposed by 802.11bh and 802.11be drafts;

[0031] Figure 5 shows a flow of an association process for network-initiated identification;

[0032] Figure 6 shows a flow of an association process for STA-initiated identification;

[0033] Figure 7 is a schematic diagram showing the basic idea of various embodiments of the present disclosure;

[0034] Figure 8a 、 Figure 8b 、 Figure 8c shows an exemplary frame format for four-way handshake messages according to some embodiments of the present disclosure;

[0035] Figure 9 shows a signal flow between a first wireless device and a second wireless device according to some embodiments of the present disclosure;

[0036] Figure 10 is a flowchart depicting a method performed by a first wireless device according to some embodiments of the present disclosure;

[0037] Figure 11 is a flowchart depicting a method performed by a second wireless device according to some embodiments of the present disclosure;

[0038] Figure 12 illustrates an exemplary process of status feedback in a four - way handshake process for network - initiated identification according to some embodiments of the present disclosure;

[0039] Figure 13 illustrates an exemplary process of status feedback in a four - way handshake process for STA - initiated identification according to some embodiments of the present disclosure;

[0040] Figure 14a 、 Figure 14b 、 Figure 14c illustrates three cases of how to use status information in four - way handshake messages according to some embodiments of the present disclosure;

[0041] Figure 15 illustrates an exemplary scenario in which some embodiments of the present disclosure can be implemented;

[0042] Figure 16 illustrates an exemplary scenario in which some embodiments of the present disclosure can be implemented;

[0043] Figure 17 illustrates an exemplary scenario in which some embodiments of the present disclosure can be implemented; and

[0044] Figure 18 illustrates a simplified block diagram of a device according to some embodiments of the present disclosure. Detailed Description

[0045] Some example embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments are shown. In fact, the example embodiments may take many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals always refer to like elements.

[0046] In the following specification and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0047] References to "an embodiment", "embodiment", "example embodiment", etc. in this disclosure mean that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is considered within the knowledge of those skilled in the art to affect the combination of such feature, structure, or characteristic with other embodiments whether or not explicitly described.

[0048] It should be understood that although the terms "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0049] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the example embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "has", "having", "includes", "including", "contains", "containing", "possesses", and / or "containing" when used herein specify the presence of the stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0050] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) Only hardware circuit implementations (such as implementations only in analog / or digital circuitry) and (b) Combinations of hardware circuits and software, such as (where applicable): (i) Combinations of (one or more) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a (one or more) hardware processor with software (including (one or more) digital signal processors, software, and (one or more) memories that work together to cause a device such as a mobile phone or a server to perform various functions) and (c) (One or more) hardware circuits and / or (one or more) processors, such as (one or more) microprocessors or a part of (one or more) microprocessors, which require software (e.g., firmware) for operation, but the software may not be present when not needed.

[0051] This definition of "circuitry" applies to all uses of the term in this application, including uses in any claims. As another example, as used in this application, the term circuitry also encompasses implementations of only hardware circuits or processors (or multiple processors) or a portion of a hardware circuit or processor along with its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also encompasses a baseband integrated circuit or a processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network devices.

[0052] As used herein, the term "wireless network" refers to a Wi-Fi network that follows any suitable communication standard, such as the 802.11 standard. Additionally, communication between a requester (e.g., a wireless station (STA) or an access point (AP)) and an authenticator (e.g., an access point (AP) or a wireless station (STA)) in a wireless network can be performed according to any suitable Wi-Fi communication protocol. Embodiments of the present disclosure can be applied to various communication systems. Given the rapid development of communication, there will of course also be future types of communication technologies and systems in which the present disclosure can be embodied. The scope of the present disclosure should not be considered limited to the foregoing systems.

[0053] As used herein, the term "wireless device" refers to any device that can wirelessly communicate with another device via a wireless network. By way of example and not limitation, a wireless device can refer to a wireless station, an access point, or other suitable devices. A wireless station can include, but is not limited to, a user equipment (UE), an Internet of Things (IoT) device, a vehicle-mounted wireless device, etc.

[0054] As described above, the 4-way handshake can generate / validate a security key for encryption. Additionally, when the STA is using a Random MAC Address (RMA), the 802.11bh group attempts to find a mechanism to identify the STA. The mechanism proposed in 802.11bh assigns an identifier (ID) or MAC address or parameter related to the generation of the RMA from / to the STA in the 4-way HS. The identification process can be divided into two categories: - Network-initiated identification, which encompasses the following cases: - The network (e.g., an AP) generates an ID and assigns the ID to the STA; - The network (e.g., an AP) generates a MAC address and assigns the MAC address to the STA; or - The network (e.g., an AP) shares relevant parameters with the STA such that both sides can generate the same MAC address or ID; and - STA-initiated identification, which encompasses the following cases: - The STA generates an ID and assigns the ID to itself; - The STA generates a MAC address and assigns the MAC address to the STA; or - The STA shares relevant parameters with the AP so that the same MAC address or ID can be generated on both sides.

[0055] Will be combined with Figure 5 Describe the network-initiated identification. Such as Figure 5 As shown, in the first association, the STA follows the normal attachment process with the AP (this normal attachment process includes probe / authentication / association request / response), and moves into the 4-way HS after the attachment process is successfully completed. During the attachment process, the STA uses a fixed MAC address, for example Figure 5 shown as MAC 1 in. During the 4-way HS, the AP can assign a MAC address or ID or parameters to the STA in the 4-way HS message 1 (Msg1) or the 4-way HS message 3 (Msg3). The parameters can include parameters related to the generation of the ID and MAC address or any relevant information. And the STA and the AP can complete the 4-way HS. Then, the STA and the AP can start a data connection. After a period of time, the STA can disconnect from the AP.

[0056] Later, the STA wants to associate with the AP again, that is, a later association. In this case, the STA can use a random MAC address, for example, in Figure 5 shown as MAC X in. This random MAC address can be an identifiable MAC address, that is, a MAC address assigned to the STA in the previous association or generated by the previously assigned parameter(s); or an unidentifiable MAC address, that is, a MAC address that was not assigned to the STA in the previous association and is a new MAC address. After a successful attachment process, the STA moves into the 4-way HS and sends the previously assigned ID or MAC address or parameter(s) in the 4-way HS message 2 (Msg2) or the 4-way HS message 4 (Msg4). The AP can assign another ID or MAC address or parameter(s) to the STA in the 4-way HS Msg1 or the 4-way HS Msg3. The STA and the AP can complete the 4-way HS and can start a data connection.

[0057] Will be combined with Figure 6 Describe the STA-initiated identification. Such as Figure 6 As shown, in the first association, the STA follows the normal attachment process with the AP (which includes probe / authentication / association request / response), and moves into the 4-way HS after the attachment process is successfully completed. During the attachment process, the STA uses a fixed MAC address, for example, in Figure 6Shown as MAC 1 in []. During the 4-way HS, the STA can allocate a MAC address or ID or parameters to the STA and notify the AP in the 4-way HS Msg2 or 4-way HS Msg4. The parameters can include parameters related to the generation of the ID and MAC address or any relevant information. And the STA and AP can complete the 4-way HS. Then, the STA and AP can start a data connection. After some time, the STA can disconnect from the AP.

[0058] Later, the STA wants to associate with the AP again, i.e., a later association. In this case, the STA can use a random MAC address, e.g., shown as MAC X in []. This random MAC address can be an identifiable MAC address, i.e., a MAC address assigned to the STA in a previous association or generated by previously assigned parameters; or an unidentifiable MAC address, i.e., a MAC address that was not assigned to the STA in a previous association and is a new MAC address. After a successful attachment process, the STA moves into the 4-way HS and sends the previously assigned ID or MAC address or parameters in the 4-way HS message 2 (Msg2) or 4-way HS message 4 (Msg4). The STA can also allocate another ID or MAC address or parameters to the STA and notify the AP in the 4-way HS Msg2 or 4-way HS Msg4. The STA and AP can complete the 4-way HS and can start a data connection. Figure 6 However, there is no feedback mechanism in the 4-way handshake because the 4-way handshake is not a management frame. Without such a feedback mechanism, the management operations that occur during the 4-way HS cannot be fully realized.

[0059] For example, if one side (AP or STA) receives an ID, MAC address, or related parameters from the other side (STA or AP) during the 4-way HS and further the received value is unknown / duplicate / invalid, then one side cannot notify the other side. Therefore, the other side will not know whether the 4-way handshake process is proceeding smoothly. For example, if the AP receives an unknown ID from the STA during the 4-way HS and the AP does not notify the STA of the unknown ID, then the STA will not know whether the ID used is correct. Therefore, the STA will not know whether to resend the ID or send another ID or not send an ID at all.

[0060]

[0061] ​In addition, when an unknown ID or MAC address or related parameter is received during four handshakes on one side, that side may decide not to continue the four-way HS and immediately reject the other side. For example, the AP receives an unknown ID from the STA during the four-way HS, and the AP immediately disconnects from the STA. However, the STA may have another ID to use. If no feedback is sent to the other side, the STA cannot send another available ID, and the four-way HS process stops.

[0062] Furthermore, an attack may not be detected by one side. For example, the AP receives a known ID from the STA during the four-way HS, and the STA is actually using or copying the legitimate ID of a legitimate STA. Since the AP does not give feedback to the legitimate STA and accepts the ID from the attacker, the legitimate STA never knows that an attacker is using its ID. If the AP notifies the legitimate STA of the ID, the legitimate STA will understand that an attacker is using the legitimate STA's ID because the legitimate STA has never sent its ID to that AP.

[0063] Therefore, it is desirable to enable status information feedback during the four-way handshake process. As described above, many management operations utilize management frames to implement their operations. An important part of these operations is the status code / reason code field that can be carried in the management frame. The status code / reason code can indicate the success / failure / notification of the requested operation. On the other hand, the four-way handshake becomes more attractive for implementing some management operations because the four-way handshake frame can carry encrypted key information (such as identifiers, MAC addresses, parameters, keys). However, since the four-way handshake message is not a management frame, the four-way handshake message does not have either a status code field or a reason code field in its frame body.

[0064] To fully implement the management operations that occur during the four-way handshake, various embodiments of the present disclosure describe a mechanism for status feedback during the four-way handshake process such that the management operations that occur during the four-way handshake can be fully implemented.

[0065] The basic idea of various embodiments of the present disclosure is to add status information to the frame body of the four-way handshake message to enable management operations during the four-way handshake process. Figure 7 The basic idea of an embodiment of the present disclosure is shown. As Figure 7 shown, the status information can be sent in any of the four-way handshake messages during the four-way handshake process.

[0066] Figure 8a , Figure 8b , Figure 8cShows an exemplary frame format for 4 - way handshake messages according to some embodiments of the present disclosure. As described above, the EAPOL key frame format is used for 4 - way handshake messages. Thus, in embodiments of the present disclosure, status information can be carried in the frame body of the EAPOL key frame that is used as a 4 - way handshake message.

[0067] In some embodiments, as shown in FIG. 8, status information can be carried in the reserved field. In an embodiment, the "status information" field can be defined in the reserved field to carry status information. In some embodiments, as Figure 8b shown, status information can be carried in a new field (i.e., the "status information" field) defined in the EAPOL key frame. In some embodiments, the status information field can be 2 octets. In some embodiments, as shown in FIG. 8, status information can be carried in the key data field as part of the 4 - way handshake key data (KDE). In some embodiments, status information can be represented by a status information code in the 4 - way handshake message. Details of status information and status information codes will be described later.

[0068] Figure 9 Shows the signal flow between a first wireless device and a second wireless device according to some embodiments of the present disclosure. In some embodiments, the first wireless device can be a requester in a wireless network, such as a wireless station (STA) or an access point (AP), and the second wireless device can be an authenticator in the wireless network, such as an AP or an STA. In some embodiments, the first wireless device can be an authenticator in the wireless network, and the second wireless device can be a requester in the wireless network.

[0069] As Figure 9 shown, at step 1, during association, the first wireless device can send a first message including the device identification information of the first wireless device to the second device before or during the 4 - way HS. In some embodiments, the device identification information can be, but is not limited to, at least one of a device identifier (abbreviated as "identifier"), a MAC address, (a plurality of) related parameters for generating a device identifier or a MAC address, a GTK, a PMKID, a random number, an IGTK, a key ID, and an OCI. In some embodiments, the first message can be carried in a management frame during the attachment process or in one of the 4 - way HS messages during the 4 - way HS process.

[0070] At step 2, after receiving the device identification information, the second wireless device can determine the status information based on the received device identification information and the acquired device identification information, where the acquired device identification information is assigned to the first wireless device during the association period or in a previous association. The status information can be used to indicate the reception status of the first message, and / or the actions of subsequent operations. In some embodiments, the status information can be carried in the 4 HS messages as shown in Figure 8a or Figure 8b or Figure 8c . In some embodiments, the status information can be represented by a status information code.

[0071] At step 3, the second wireless device can transmit the status information to the first wireless device through one of the 4 handshake messages, which will be described in detail later. At step 4, the first wireless device can determine at least one of the following operations based on the status information: - For example, if the received device identification information is successfully recognized by the second wireless device, continue the 4-way handshake; - For example, if the device identification information times out, resend the device identification information of the first wireless device; - For example, if the device identification information is unknown to the second wireless device, send another device identification information of the first wireless device; - For example, if the number of transmissions of the device identification information exceeds the maximum number, or the device identification information has been recognized, do not send the device identification information at all; - For example, if the device identification information is unknown to the second wireless device, immediately stop the 4-way handshake.

[0072] By defining a status feedback mechanism in the 4 HS, the management operations occurring in the 4 HS can be fully implemented. With the help of the status information, the STA or AP can know whether the operations in the 4 HS are proceeding smoothly and take actions accordingly, or can decide whether to continue the 4 HS, or can detect an attack from a third party if a third party wants to manipulate the network.

[0073] Reference will be made to Figures 10 to 17 for more details of example embodiments according to the present disclosure.

[0074] Figure 10 is a flowchart depicting method 1000 performed by a first wireless device according to some embodiments of the present disclosure.

[0075] As shown in Figure 10As shown, at block 1010, a first wireless device receives a first message from a second wireless device. The first message may include identification information of the second wireless device. In some embodiments, the identification information may include at least one of the following: an identifier, a media access control (MAC) address, or one or more parameters related to the generation of the identifier or the MAC address.

[0076] In some embodiments, the first message may be one of the following: a management frame during an attachment process between the first wireless device and the second wireless device, or a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device.

[0077] At block 1020, the first wireless device determines status information based at least on the received identification information of the second wireless device. In some embodiments, the status information may indicate feedback on the first message.

[0078] In some embodiments, the first wireless device may compare the received identification information with the obtained identification information of the second wireless device. In some embodiments, the obtained identification information may be the identification information assigned to the second wireless device during the current association process or a previous association process. Then, the first wireless device may determine the status information based on the result of the comparison. For example, if the received identification information matches the obtained identification information of the second wireless device, it means that the first wireless device can recognize the received identification information of the second wireless device, and the first wireless device may determine that the received identification information is the status information known to the first wireless device. On the other hand, if the received identification information does not match the obtained identification information of the second wireless device, it means that the first wireless device cannot recognize the received identification information of the second wireless device, and the first wireless device may determine that the received identification information is the status information unknown to the first wireless device.

[0079] In some embodiments, the first wireless device may determine whether the received identification information has expired, such as a timeout. Then, in response to the received identification information having expired, the first wireless device may determine the corresponding status information.

[0080] In some embodiments, the first wireless device may determine whether the received identification information is repeated, that is, whether the received identification information is used by another wireless device. Then, in response to the received identification information being repeated, the first wireless device may determine the corresponding status information.

[0081] In some embodiments, the status information may indicate at least one of the following: success of an operation related to the first message, failure of an operation related to the first message, the received identification information is known to the first wireless device, the received identification information is unknown to the first wireless device, the received identification information is duplicate, or the identification information of the second wireless device needs to be resent.

[0082] In some embodiments, the status information may be represented by a status information code, as shown in Table 4. Table 4

[0083] At block 1030, the first wireless device transmits the status information to the second wireless device in the four-way handshake message during the four-way handshake process. In some embodiments, the status information may be carried in a reserved field of the four-way handshake message, for example, as Figure 8a shown. Alternatively, in some embodiments, the status information may be carried in a new field of the four-way handshake message, for example, as Figure 8b shown. Alternatively, the status information may be carried in the key data field of the four-way handshake message, for example, as Figure 8c shown.

[0084] In some embodiments, the status information may be transmitted in at least one of the following: four-way handshake message 1 (Msg1), four-way handshake message 2 (Msg2), four-way handshake message 3 (Msg3), and four-way handshake message 4 (Msg4) during the four-way handshake process.

[0085] In some embodiments, the first wireless device may be an authenticator in the wireless network, and the second wireless device may be a supplicant in the wireless network. Thus, in some embodiments, the first message may be any management frame during the attachment process between the first wireless device and the second wireless device. In this case, the status information may be transmitted in the four-way handshake Msg1 during the four-way handshake process.

[0086] Alternatively or additionally, in some embodiments, the first message may be the four-way handshake Msg2 during the four-way handshake process. In this case, the status information may be transmitted in the four-way handshake Msg3.

[0087] In some embodiments, the first wireless device may be a supplicant in the wireless network, and the second wireless device may be an authenticator in the wireless network. Thus, in some embodiments, the first message may be the four-way handshake Msg1 during the four-way handshake process. In this case, the status information may be transmitted in the four-way handshake Msg2.

[0088] Alternatively or additionally, in some embodiments, the first message may be the 4-way handshake Msg3 in a 4-way handshake process. In this case, the status information may be transmitted in the 4-way handshake Msg4.

[0089] In some embodiments, the requester may be a wireless station (STA), and the authenticator may be an access point (AP). Alternatively, the requester may be a first STA, and the authenticator may be a second STA. Alternatively, the requester may be a first AP, and the authenticator may be a second AP.

[0090] Figure 11 is a flowchart depicting a method 1100 performed by a second wireless device according to some embodiments of the present disclosure.

[0091] As Figure 11 shown, at block 1110, the second wireless device transmits a first message to the first wireless device. The first message may include identification information of the second wireless device. As described above, the identification information may include at least one of the following: an identifier, a media access control (MAC) address, or one or more parameters related to the generation of the identifier or MAC address. The first message may be one of the following: a management frame in an attachment process, or a 4-way handshake message in a 4-way handshake process.

[0092] At block 1120, in a 4-way handshake message in a 4-way handshake process, the second wireless device receives status information from the first wireless device. As described above, the status information may indicate feedback on the first message. In some embodiments, the status information may indicate at least one of the following: success of an operation related to the first message, failure of an operation related to the first message, the received identification information is known to the first wireless device, the received identification information is unknown to the first wireless device, the received identification information is duplicate, or the identification information of the second wireless device needs to be resent. The status information may be represented by a status information code defined in Table 4 above.

[0093] In some embodiments, the status information may be received in a reserved field of the 4-way handshake message, for example, as Figure 8a shown. Alternatively, in some embodiments, the status information may be received in a new field of the 4-way handshake message, for example, as Figure 8b shown. Alternatively, the status information may be received in a key data field of the 4-way handshake message, for example, as Figure 8c shown.

[0094] In some embodiments, the status information may be received in at least one of the following: 4-way handshake Msg1, 4-way handshake Msg2, 4-way handshake Msg3, and 4-way handshake Msg4 in a 4-way handshake process.

[0095] In some embodiments, the first wireless device may be an authenticator in a wireless network, and the second wireless device may be a supplicant in the wireless network. Thus, in some embodiments, the first message may be any management frame in the attachment process, and the status information may be received in the 4 - way handshake Msg1 during the 4 - way handshake process. Alternatively or additionally, in some embodiments, the first message may be the 4 - way handshake Msg2 during the 4 - way handshake process, and the status information may be received in the 4 - way handshake Msg3.

[0096] In some embodiments, the first wireless device may be a supplicant in a wireless network, and the second wireless device may be an authenticator in the wireless network. Thus, in some embodiments, the first message may be the 4 - way handshake Msg1 during the 4 - way handshake process, and the status information may be received in the 4 - way handshake Msg2. Alternatively or additionally, in some embodiments, the first message may be the 4 - way handshake Msg3 during the 4 - way handshake process, and the status information may be received in the 4 - way handshake Msg4.

[0097] At block 1130, the second wireless device determines an operation based on the status information. In some embodiments, the operation may include at least one of the following: - Continue the 4 - way handshake process; - Resend the identification information of the second wireless device; - Send different identification information of the second wireless device; - Do not send the identification information of the second wireless device; or - Stop the 4 - way handshake process.

[0098] In some embodiments, at least one management operation may be performed during a four-way handshake according to the status information codes listed in Table 4. For example, if the status information code in the four-way HS Msg3 is 2, 3, or 4, it means that the ID or MAC address or (multiple) parameters sent in the four-way HS Msg2 are known, the operation related to the four-way HS Msg2 is successful, and the second wireless device can proceed to the next step (e.g., allowing the transmission of the four-way HS Msg4, or the completion of the four-way HS process). If the status information code in the four-way HS Msg3 is 5, 6, or 7, it means that the ID or MAC address or (multiple) parameters sent in the four-way HS Msg2 are unknown, the operation related to the four-way HS Msg2 fails, and the second wireless device may not proceed to the next step (e.g., allowing the transmission of the four-way HS Msg4, or the completion of the four-way HS process). If the status information code in the four-way HS Msg3 is 8, 9, or 10, it means that the ID or MAC address or (multiple) parameters sent in the four-way HS Msg2 are duplicate (i.e., used by another wireless device), the operation related to the four-way HS Msg2 fails, and the second wireless device may not proceed to the next step (e.g., allowing the transmission of the four-way HS Msg4, or the completion of the four-way HS process). If the status information code in the four-way HS Msg3 is 11, 12, or 13, it means that the ID or MAC address or (multiple) parameters sent in the four-way HS Msg2 are unknown or duplicate, but if the second wireless device has another ID or MAC address or (multiple) parameters (e.g., if the second wireless device has multiple IDs or MAC addresses or parameters assigned during a previous association process), the second wireless device may need to retransmit another ID or MAC address or (multiple) parameters. The status information code may be 1, meaning that the operation related to the first message fails (is rejected) due to an unspecified failure. The status information code may also be 0, meaning that the operation related to the first message is successful without further specific explanation. Similarly, the status information code may be any supplier-specific definition.

[0099] In some embodiments, the requester may be a wireless station (STA), and the authenticator may be an access point (AP). Alternatively, the requester may be a first STA, and the authenticator may be a second STA. Alternatively, the requester may be a first AP, and the authenticator may be a second AP.

[0100] Figure 12 An exemplary process for status feedback during a four-way handshake for network-initiated identification according to some embodiments of the present disclosure is shown. In this example, the first wireless device is the authenticator (e.g., an AP), and the second wireless device is the requester (e.g., an STA).

[0101] As Figure 12 shown, in the first association process, the STA follows the normal attachment process (probe / authentication / association request / response) (at (1)), and moves into the 4-way HS after a successful attachment process (at (2)). During this attachment process, as Figure 12 shown, the STA uses the fixed MAC address MAC 1. During the 4-way HS, the AP can assign a MAC address or ID or (multiple) parameters to the STA in the 4-way HS Msg1 or / and the 4-way HS Msg3. The (multiple) parameters can include one or more parameters used to generate an ID, MAC address, or any related information. Then, the STA and the AP can complete the 4-way HS process at (3). After that, the STA and the AP can start a data connection at (4). After some time, the STA can disconnect from the AP.

[0102] In a later association process, the STA wants to associate with the AP again. At this time, the STA can use the random MAC address MAC X, as Figure 12 shown. At (5), this random MAC address can be an identifiable MAC address (i.e., a MAC address assigned to the STA during the previous association process or generated by the previously assigned (multiple) parameters) or an unidentifiable MAC address (i.e., a MAC address that was not assigned to the STA during the previous association process and is a new MAC address). After a successful attachment process, the STA moves into the 4-way HS. The AP can send relevant status information to the STA in the 4-way HS Msg1 at (6). Based on this status information, the STA can continue or stop the 4-way HS, or resend an ID or MAC address or (multiple) parameters, or send another ID or MAC address or (multiple) parameters, or not send an ID or MAC address or (multiple) parameters. As an example, if the status information indicates "KNOWN_MAC", the STA will continue the 4-way HS process. If the status information indicates "RESEND_ID", the STA will resend the ID. In addition, the AP can assign another ID or MAC address or (multiple) parameters to the STA in the 4-way HS Msg1.

[0103] In addition, the STA can send the previously allocated ID or MAC address or parameter(s) (from the previous association process) in the 4-way HS Msg2 at (7), and the AP can send the relevant status information to the STA in the 4-way HS Msg3 at (8). Based on this status information, the STA can continue or stop the 4-way HS, or resend the ID or MAC address or parameter(s), or send another ID or MAC address or parameter(s), or not send the ID or MAC address or parameter(s). As an example, if the status information indicates "KNOWN_MAC", the STA will continue the 4-way HS process. If the status information indicates "RESEND_ID", the STA will resend the ID. In addition, the AP can allocate another ID or MAC address or parameter(s) to the STA in the 4-way HS Msg3. The STA can send the previously allocated ID or MAC address or parameter(s) in the 4-way HS Msg4 at (9), and the STA and the AP complete the 4-way HS and can start a data connection at (10).

[0104] Figure 13 An exemplary process for status feedback in the 4-way handshake process for STA-initiated identification according to some embodiments of the present disclosure is shown. In this example, the first wireless device is an authenticator (e.g., an AP), and the second wireless device is a supplicant (e.g., an STA).

[0105] As Figure 13 shown, in the first association process, the STA follows the normal attachment process (probe / authentication / association request / response) at (1), and moves into the 4-way HS at (2) after a successful attachment process. During this attachment process, as Figure 13 shown, the STA uses the fixed MAC address MAC 1. During the 4-way HS, the STA can be allocated a MAC address or ID or parameter(s), and notify the AP in the 4-way HS Msg2 or / and the 4-way HS Msg4. The parameter(s) can include one or more parameters for generating an ID, MAC address, or any relevant information. Then, the STA and the AP can complete the 4-way HS process at (3). Thereafter, the STA and the AP can start a data connection at (4). After a period of time, the STA can disconnect from the AP.

[0106] In a later association process, the STA wants to associate with the AP again at (5). At this time, the STA can use the random MAC address MAC X, as Figure 13As shown. The random MAC address can be an identifiable MAC address (i.e., a MAC address assigned to the STA during a previous association process or generated from the previously assigned parameter(s)) or an unidentifiable MAC address (i.e., a MAC address that was not assigned to the STA during the previous association process and is a new MAC address). After a successful attachment process, the STA moves into the 4-way HS. At (6), the AP can send relevant status information to the STA in the 4-way HS Msg1. Based on this status information, the STA can continue or stop the 4-way HS, or resend the ID or MAC address or parameter(s), or send another ID or MAC address or parameter(s), or not send the ID or MAC address or parameter(s). As an example, if the status information indicates "KNOWN_MAC", the STA will continue the 4-way HS process. If the status information indicates "RESEND_ID", the STA will resend the ID.

[0107] In addition, at (7), the STA can send the previously assigned ID or MAC address or parameter(s) (from the previous association process) in the 4-way HS Msg2. In addition, the STA can assign another ID or MAC address or parameter(s) to the STA and notify the AP in the 4-way HS Msg2. At (8), the AP can send relevant status information to the STA in the 4-way HS Msg3. Based on this status information, the STA can continue or stop the 4-way HS, or resend the ID or MAC address or parameter(s), or send another ID or MAC address or parameter(s), or not send the ID or MAC address or parameter(s). As an example, if the status information indicates "KNOWN_MAC", the STA will continue the 4-way HS process. If the status information indicates "RESEND_ID", the STA will resend the ID. In addition, at (9), the STA can send the previously assigned ID or MAC address or parameter(s) in the 4-way HS Msg4. In addition, the STA can assign another ID or MAC address or parameter(s) to the STA in the 4-way HS Msg4. Then, the STA and the AP complete the 4-way HS and can start a data connection at (10).

[0108] Figure 14a 、 Figure 14b and Figure 14c illustrate three cases of how to use the status information in the 4-way handshake messages according to some embodiments of the present disclosure. In these three cases, the first wireless device is an authenticator (e.g., an AP), and the second wireless device is a supplicant (e.g., a STA). The frame format of the 4-way handshake message used for status feedback has been described in Figure 8a 、 Figure 8b or Figure 8cis shown and described above. Assume the following scenario: - The STA and the AP use network-initiated identification, where the AP generates an ID and assigns the ID to the STA; - The AP assigns ID = 123 to the STA in the 4th HS Msg3 in the first association; - The STA sends the previously assigned ID = 123 in the 4th HS Msg2 in a later association; and - The AP sends status information to the STA in the 4th HS Msg3. As an example, the AP sends "Status Information Code = 2, KNOWN_ID".

[0109] As Figure 14a shown, the status information is carried in a reserved field. In this case, the "Status Information" field is defined in the reserved field and consists of 2 octets. In this scenario, the status information code is 2, meaning the ID is known to the AP.

[0110] As Figure 14b shown, the status information is carried in a new field, such as the "Status Information" field in the 4-way handshake message. The new "Status Information" field can consist of 2 octets. In this scenario, the status information code is 2, meaning the ID is known to the AP.

[0111] As Figure 14c shown, the status information is carried in the key data field, as part of the 4-way HS key data (KDE). The KDE is as Figure 14c shown. In this scenario, the status information code is 2, meaning the ID is known to the AP.

[0112] Figure 15 shows an exemplary scenario in which some embodiments of the present disclosure can be implemented. In this exemplary scenario, the STA as the requester and the AP as the authenticator use network-initiated identification, where the AP generates an ID and assigns the ID to the STA.

[0113] As Figure 15 shown, in the first association, the AP assigns ID = 123 to the STA in the 4th HS Msg3. In the second association, the STA sends the previously assigned (from the first association) ID = 123 to the AP in the 4th HS Msg2. The AP recognizes ID = 123, and thus sends "Status Information Code = 2, KNOWN_ID" to the STA in the 4th HS Msg3. Since the identification of the STA is successful, the AP moves forward and assigns another ID = 456 to the STA in the 4th HS Msg3.

[0114] In the third association, the STA sends ID = 111 in the 4 HS Msg2s. The AP does not recognize ID = 111 and thus sends "Status Information Code = 5, UNKNOWN_ID" to the STA in the 4 HS Msg3s. Since the identification of the STA fails, the 4 HS processes stop.

[0115] Figure 16 An exemplary scenario is shown in which some embodiments of the present disclosure can be implemented. In this exemplary scenario, the STA as the requester and the AP as the authenticator use network-initiated identification, where the AP generates a random MAC (RMA) and assigns the random MAC (RMA) to the STA.

[0116] As Figure 16 shown, in the first association, the AP assigns RMA = AA to the STA in the 4 HS Msg3s. In the second association, the STA sends RMA = AA to the AP in the probe / authentication / association request. The AP recognizes RMA = AA and thus sends "Status Information Code = 3, KNOWN_MAC" to the STA in the 4 HS Msg1s. Since the identification of the STA is successful, the AP moves forward and assigns another RMA = BB to the STA in the 4 HS Msg3s.

[0117] In the third association, the STA sends RMA = CC to the AP in the probe / authentication / association request. The AP does not recognize RMA = CC, so it sends "Status Information Code = 6, UNKNOWN_MAC" to the STA in the 4 HS Msg1s. Since the identification of the STA fails, the 4 HS processes stop.

[0118] Figure 17 An exemplary scenario is shown in which some embodiments of the present disclosure can be implemented. In this exemplary scenario, the STA as the requester and the AP as the authenticator use STA-initiated identification, where the STA generates the RMA, assigns the RMA to itself, and notifies the AP.

[0119] As Figure 17As shown, in the first association, the STA assigns RMA = AA to itself and notifies the AP in the 4 - way HS Msg4. In the second association, the STA sends RMA = CC to the AP in the probe / authentication / association request. The AP does not recognize RMA = CC, but the AP expects another RMA, perhaps RMA = AA. Thus, the AP sends "status information code = 12, RESEND_MAC" to the STA in the 4 - way HS Msg1. Then, the STA sends RMA = AA to the AP in the 4 - way HS Msg2. The AP recognizes RMA = AA and thus sends "status information code = 3, KNOWN_MAC" to the STA in the 4 - way HS Msg3. Since the identification of the STA is successful, the 4 - way HS process is completed.

[0120] Although the exemplary embodiments have been described in the case where the status information is transmitted / received in the 4 - way handshake Msg1 and / or the 4 - way handshake Msg3, those skilled in the art will understand that the status information can be transmitted / received in the 4 - way handshake Msg2 and / or the 4 - way handshake Msg4.

[0121] Now refer to Figure 18 , which shows a simplified block diagram of an apparatus 1800 that can be embodied as a first wireless device or a second wireless device. The apparatus 1800 may include at least one processor 1801 (such as a data processor (DP)) and at least one memory (MEM) 1802 coupled to the at least one processor 1801. The apparatus 1800 may also include a transmitting unit and a receiving unit 1803 coupled to one or more processors 1801.

[0122] As a non - limiting example, the processor 1801 can be of any type suitable for the local technical environment and can include one or more of the following: a general - purpose computer, a special - purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi - core processor architecture.

[0123] As a non - limiting example, the MEM 1802 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor - based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory.

[0124] The MEM 1802 stores a program (PROG) 1804. The PROG 1804 may include instructions that, when executed on the associated processor 1801, enable the apparatus 1800 to operate according to the embodiments of the present disclosure, for example, to perform as Figure 10 and Figure 11One of the methods 1000 and 1100 shown. A combination of at least one processor 1801 and at least one MEM 1802 can form a processing circuitry or component 1805 suitable for implementing various embodiments of the present disclosure.

[0125] Various embodiments of the present disclosure can be implemented by a computer program executable by one or more processors 1801, software, firmware, hardware, or a combination thereof.

[0126] Generally, the various exemplary embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software executable by a controller, microprocessor, or other computing device, but the present disclosure is not limited thereto. Although the various aspects of the exemplary embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, as a non-limiting example, the blocks, devices, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general hardware or a controller or other computing device, or some combination thereof.

[0127] Accordingly, it should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of the present disclosure can be implemented in a device embodied as an integrated circuit, wherein the integrated circuit can include circuitry (and possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, a baseband circuit, and a radio frequency circuit that can be configured to operate in accordance with the exemplary embodiments of the present disclosure.

[0128] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be embodied in computer-executable instructions executed by one or more computers or other devices, such as in one or more program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., which perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. The computer-executable instructions can be stored on a computer-readable medium, such as a non-transitory computer-readable medium, such as a hard disk, an optical disk, a removable storage medium, a solid-state memory, RAM, etc. As will be understood by those skilled in the art, the functions of the program modules can be combined or distributed as needed in various embodiments. Additionally, the functionality can be embodied in whole or in part in firmware or hardware equivalents, such as integrated circuits, field-programmable gate arrays (FPGAs), etc.

[0129] Moreover, although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the foregoing discussion, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Specific features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0130] The present disclosure includes any novel feature or combination of features or any generalization thereof explicitly disclosed herein. Various modifications and adaptations of the foregoing exemplary embodiments of the present disclosure may become apparent to those skilled in the relevant arts when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure.

Claims

1. A first wireless device, comprising: At least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the first wireless device to at least: receive a first message from a second wireless device, the first message including identification information of the second wireless device; determine status information at least based on the identification information, the status information indicating feedback on the first message; and transmit the status information to the second wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device.

2. The first wireless device according to claim 1, wherein the identification information comprises at least one of the following: an identifier, a media access control (MAC) address, or one or more parameters related to the generation of the identifier or the MAC address.

3. The first wireless device according to claim 1 or 2, wherein the first message is one of the following: a management frame during an attachment process between the first wireless device and the second wireless device, or a four-way handshake message during the four-way handshake process.

4. The first wireless device according to any one of claims 1 to 3, wherein, in order to determine the status information, the first wireless device is caused to perform at least one of the following: Compare the received identification information with the obtained identification information of the second wireless device; Determine whether the received identification information has expired; or Determine whether the received identification information is repeated.

5. The first wireless device according to any one of claims 1 to 4, wherein the status information indicates at least one of the following: Success of an operation related to the first message; Failure of the operation related to the first message; The received identification information is known to the first wireless device; The received identification information is unknown to the first wireless device; the received identification information is repeated; or the identification information of the second wireless device needs to be resent.

6. The first wireless device according to any one of claims 1 to 5, wherein one of the following applies: The status information is carried in a reserved field of the four-way handshake message; The status information is carried in a new field of the four-way handshake message; or The status information is carried in a key data field of the four-way handshake message.

7. The first wireless device according to any one of claims 1 to 6, wherein the status information is transmitted in at least one of the following: four-way handshake message 1, four-way handshake message 2, four-way handshake message 3, and four-way handshake message 4 in the four-way handshake process.

8. The first wireless device according to any one of claims 1 to 7, wherein the first wireless device is an authenticator in a wireless network, and wherein the second wireless device is a supplicant in the wireless network.

9. The first wireless device according to claim 8, wherein the first message is a management frame in an attachment process between the first wireless device and the second wireless device, and wherein the four-way handshake message in which the status information is transmitted is four-way handshake message 1 in the four-way handshake process.

10. The first wireless device according to claim 8 or 9, wherein the first message is four-way handshake message 2 in the four-way handshake process, and wherein the four-way handshake message in which the status information is transmitted is four-way handshake message 3 in the four-way handshake process.

11. The first wireless device according to any one of claims 1 to 7, wherein the first wireless device is a supplicant in a wireless network, and wherein the second wireless device is an authenticator in the wireless network.

12. The first wireless device according to claim 11, wherein the first message is four-way handshake message 1 in the four-way handshake process, and wherein the four-way handshake message in which the status information is transmitted is four-way handshake message 2 in the four-way handshake process.

13. The first wireless device according to claim 11 or 12, wherein the first message is four-way handshake message 3 in the four-way handshake process, and wherein the four-way handshake message in which the status information is transmitted is four-way handshake message 4 in the four-way handshake process.

14. The first wireless device according to any one of claims 8 to 13, wherein the supplicant is a wireless station, and the authenticator is an access point; or wherein the supplicant is a first access point, and the authenticator is a second access point; or wherein the supplicant is a first wireless station, and the authenticator is a second wireless station.

15. A second wireless device, comprising: At least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the second wireless device to at least: transmit a first message to a first wireless device, the first message including identification information of the second wireless device; receive status information from the first wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device, the status information indicating feedback on the first message; and determine an operation based on the status information.

16. The second wireless device according to claim 15, wherein the identification information includes at least one of the following: an identifier, a media access control (MAC) address, or one or more parameters related to the generation of the identifier or the MAC address.

17. The second wireless device according to claim 15 or 16, wherein the first message is one of the following: a management frame during an attachment process between the first wireless device and the second wireless device, or a four-way handshake message during the four-way handshake process.

18. The second wireless device according to any one of claims 15 to 17, wherein the status information indicates at least one of the following: success of an operation related to the first message; failure of the operation related to the first message; The transmitted identification information is known to the first wireless device; the transmitted identification information is unknown to the first wireless device; the transmitted identification information is repeated; or the identification information of the second wireless device needs to be resent.

19. The second wireless device according to any one of claims 15 to 18, wherein one of the following applies: the status information is carried in a reserved field of the four-way handshake message; the status information is carried in a new field of the four-way handshake message; or the status information is carried in a key data field of the four-way handshake message.

20. The second wireless device according to any one of claims 15 to 19, wherein the operation includes at least one of the following: continue the four-way handshake process; resend the identification information of the second wireless device; send different identification information of the second wireless device; Do not transmit the identification information of the second wireless device; or stop the four-way handshake process.

21. The second wireless device according to any one of claims 15 to 20, wherein the status information is received in at least one of the following: four-way handshake message 1, four-way handshake message 2, four-way handshake message 3, and four-way handshake message 4 during the four-way handshake process.

22. The second wireless device according to any one of claims 15 to 21, wherein the first wireless device is an authenticator in a wireless network, and wherein the second wireless device is a supplicant in the wireless network.

23. The second wireless device according to claim 22, wherein the first message is a management frame in an attachment procedure between the first wireless device and the second wireless device, and wherein the 4-way handshake message in which the status information is received is 4-way handshake message 1 in the 4-way handshake procedure.

24. The second wireless device according to claim 22 or 23, wherein the first message is 4-way handshake message 2 in the 4-way handshake procedure, and wherein the 4-way handshake message in which the status information is received is 4-way handshake message 3 in the 4-way handshake procedure.

25. The second wireless device according to any one of claims 15 to 21, wherein the first wireless device is a supplicant in a wireless network, and wherein the second wireless device is an authenticator in the wireless network.

26. The second wireless device according to claim 25, wherein the first message is 4-way handshake message 1 in the 4-way handshake procedure, and wherein the 4-way handshake message in which the status information is received is 4-way handshake message 2 in the 4-way handshake procedure.

27. The second wireless device according to claim 25 or 26, wherein the first message is 4-way handshake message 3 in the 4-way handshake procedure, and wherein the 4-way handshake message in which the status information is received is 4-way handshake message 4 in the 4-way handshake procedure.

28. The second wireless device according to any one of claims 22 to 27, wherein the supplicant is a wireless station and the authenticator is an access point; or wherein the supplicant is a first access point and the authenticator is a second access point; or wherein the supplicant is a first wireless station and the authenticator is a second wireless station.

29. A method performed by a first wireless device, the method comprising: Receive a first message from a second wireless device, the first message including identification information of the second wireless device; Determine status information at least based on the identification information, the status information indicating feedback on the first message; and Transmit the status information to the second wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device.

30. The method according to claim 29, wherein the identification information comprises at least one of the following: an identifier, a media access control (MAC) address, or one or more parameters related to the generation of the identifier or the MAC address.

31. The method according to claim 29 or 30, wherein the first message is one of the following: a management frame during an attachment process between the first wireless device and the second wireless device, or a four-way handshake message during the four-way handshake process.

32. The method according to any one of claims 29 to 31, wherein determining the status information includes at least one of the following: comparing the received identification information with the identification information of the second wireless device previously obtained; determining whether the received identification information has expired; or determining whether the received identification information is repeated.

33. The method according to any one of claims 29 to 32, wherein the status information indicates at least one of the following: success of an operation related to the first message; failure of the operation related to the first message; the received identification information is known to the first wireless device; The received identification information is unknown to the first wireless device; the received identification information is repeated; or the identification information of the second wireless device needs to be resent.

34. The method according to any one of claims 29 to 33, wherein one of the following applies: the status information is carried in a reserved field of the four-way handshake message; the status information is carried in a new field of the four-way handshake message; or the status information is carried in a key data field of the four-way handshake message.

35. The method according to any one of claims 29 to 34, wherein the status information is transmitted in at least one of the following: four-way handshake message 1, four-way handshake message 2, four-way handshake message 3, and four-way handshake message 4 during the four-way handshake process.

36. The method according to any one of claims 29 to 35, wherein the first wireless device is an authenticator in a wireless network, and wherein the second wireless device is a supplicant in the wireless network.

37. The method according to claim 36, wherein the first message is a management frame during an attachment process between the first wireless device and the second wireless device, and wherein the four-way handshake message in which the status information is transmitted is four-way handshake message 1 during the four-way handshake process.

38. The method according to claim 36 or 37, wherein the first message is the four-way handshake message 2 in the four-way handshake process, and wherein the four-way handshake message in which the status information is transmitted is the four-way handshake message 3 in the four-way handshake process.

39. The method according to any one of claims 29 to 35, wherein the first wireless device is a requester in a wireless network, and wherein the second wireless device is an authenticator in the wireless network.

40. The method according to claim 39, wherein the first message is the four-way handshake message 1 in the four-way handshake process, and wherein the four-way handshake message in which the status information is transmitted is the four-way handshake message 2 in the four-way handshake process.

41. The method according to claim 39 or 40, wherein the first message is the four-way handshake message 3 in the four-way handshake process, and wherein the four-way handshake message in which the status information is transmitted is the four-way handshake message 4 in the four-way handshake process.

42. The method according to any one of claims 35 to 41, wherein the requester is a wireless station and the authenticator is an access point; or wherein the requester is a first access point and the authenticator is a second access point; or wherein the requester is a first wireless station and the authenticator is a second wireless station.

43. A method performed by a second wireless device, the method comprising: Transmit a first message to a first wireless device, the first message including identification information of the second wireless device; Receive status information from the first wireless device in a four-way handshake message during a four-way handshake process between the first wireless device and the second wireless device, the status information indicating feedback on the first message; and Determine an operation based on the status information.

44. The method according to claim 43, wherein the identification information comprises at least one of the following: an identifier, a media access control (MAC) address, or one or more parameters related to the generation of the identifier or the MAC address.

45. The method according to claim 43 or 44, wherein the first message is one of the following: a management frame in an attachment process between the first wireless device and the second wireless device, or a four-way handshake message in the four-way handshake process.

46. The method according to any one of claims 43 to 45, wherein the status information indicates at least one of the following: success of an operation related to the first message; failure of the operation related to the first message; The transmitted identification information is known to the first wireless device; the transmitted identification information is unknown to the first wireless device; the transmitted identification information is repeated; or the identification information of the second wireless device needs to be resent.

47. The method according to any one of claims 43 to 46, wherein one of the following applies: The status information is carried in a reserved field of the four-way handshake message; The status information is carried in a new field of the four-way handshake message; or The status information is carried in the key data field of the four-way handshake message.

48. The method according to any one of claims 43 to 47, wherein the operation includes at least one of the following: Continue the four-way handshake process; Resend the identification information of the second wireless device; Send different identification information of the second wireless device; Do not transmit the identification information of the second wireless device; or stop the four-way handshake process.

49. The method according to any one of claims 43 to 48, wherein the status information is received in at least one of the following: four-way handshake message 1, four-way handshake message 2, four-way handshake message 3, and four-way handshake message 4 in the four-way handshake process.

50. The method according to any one of claims 43 to 49, wherein the first wireless device is an authenticator in a wireless network, and wherein the second wireless device is a supplicant in the wireless network.

51. The method according to claim 50, wherein the first message is a management frame in an attachment process between the first wireless device and the second wireless device, and wherein the four-way handshake message in which the status information is received is four-way handshake message 1 in the four-way handshake process.

52. The method according to claim 50 or 51, wherein the first message is four-way handshake message 2 in the four-way handshake process, and wherein the four-way handshake message in which the status information is received is four-way handshake message 3 in the four-way handshake process.

53. The method according to any one of claims 43 to 49, wherein the first wireless device is a supplicant in a wireless network, and wherein the second wireless device is an authenticator in the wireless network.

54. The method according to claim 53, wherein the first message is the four-way handshake message 1 in the four-way handshake process, and wherein the four-way handshake message in which the status information is received is the four-way handshake message 2 in the four-way handshake process.

55. The method according to claim 53 or 54, wherein the first message is the four-way handshake message 3 in the four-way handshake process, and wherein the four-way handshake message in which the status information is received is the four-way handshake message 4 in the four-way handshake process.

56. The method according to any one of claims 50 to 55, wherein the requester is a wireless station and the authenticator is an access point; or wherein the requester is a first access point and the authenticator is a second access point; or wherein the requester is a first wireless station and the authenticator is a second wireless station.

57. A computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform the method according to any one of claims 29 to 56.

Images