Identification of wireless devices in TDLS connections

Abstract

Various embodiments provide methods and apparatus for identification of a wireless device in a Tunnel Direct Link Setup (TDLS) connection. In an embodiment, a method performed by a first wireless device includes obtaining, during a TDLS procedure between the first wireless device and a second wireless device, at least one of: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of the second wireless device.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to wireless communication, and more particularly, to methods and apparatuses for identifying wireless devices in a tunnel direct link setup (TDLS) connection. Background Art

[0002] Randomized and Changed MAC (RCM)

[0003] In traditional IEEE 802.11 standards, wireless stations (STAs) and access points (APs) use fixed unencrypted media access control (MAC) addresses in the frame header, which creates a security issue that allows others to track STAs and APs based on their MAC addresses. To prevent STAs and APs from being tracked and improve the privacy of the 802.11 standard, MAC address randomization has become a common technique. In this regard, the IEEE 802.11bh and 802.11bi groups focus on using randomized MAC addresses (RMAs) to identify STAs without reducing user privacy.

[0004] IEEE 802.11bh focuses on identifying STAs through MAC randomization during the pre-association phase, i.e., the STA does not change its MAC address after associating with the AP (i.e., post-association). On the other hand, IEEE 802.11bi takes solving privacy issues as part of its work and tries to address the situation where the STA can change its MAC address after association.

[0005] To identify STAs with RMAs, there are several proposals in 802.11bh [22 / 187r2, 22 / 925r2, 22 / 895r1, 22 / 888r2, 22 / 158r3], and [22 / 114r3] in 802.11bi. Basically, in the proposed mechanisms, when an STA associates with an AP (such as the first association), the STA is assigned device identification information (such as an identifier (ID) or an RMA), and then the STA uses the assigned device identification information (such as an ID or an RMA) in subsequent (multiple) associations (such as the second association). Figure 1 Shows an existing process for identifying STAs during the association process. As Figure 1 shown, the STA uses a MAC address (such as a common MAC address) in the current association (such as the first association). After the STA associates with the AP using the MAC address, the STA is assigned device identification information (such as an ID or an RMA, depending on the identification method). When the STA disconnects and then associates with the same AP again in a subsequent association, the STA uses the previously assigned (such as the one assigned during the first association) device identification information (such as an ID or an RMA), and thus the STA is identified by the AP.

[0006] Note that a STA may be assigned multiple device identification information (such as multiple IDs or multiple RMAs) during a single association (such as the first association) and use at least one of the device identification information in subsequent associations (such as the second association). As used herein, "device identification information" encompasses both single device identification information and multiple device identification information.

[0007] The assignment of device identification information (ID or RMA) may include: i) the AP assigns the ID or RMA to the STA; ii) the STA assigns the ID or RMA to ; or iii) the AP and the STA generate the ID or RMA on each side through a common process (such as using an ID or RMA generation function).

[0008] Tunneled Direct Link Setup (TDLS)

[0009] Tunneled Direct Link Setup (TDLS) allows two STAs to establish a direct connection. To this end, the STAs should be associated with the same AP. The direct connection in TDLS means that one STA (such as STA1) sends a TDLS frame encapsulated in a data frame to the AP, and the AP forwards the TDLS frame encapsulated in the data frame to another STA (such as STA2). In other words, the two STAs transparently send TDLS frames to each other through the AP. To establish a direct link, both STAs should support TDLS. The initiating STA is called the initiator, and the other STA is called the responder.

[0010] Figure 2 shows the signaling flow of the TDLS process. As Figure 2As shown, first, two STAs, STA1 and STA2, are associated with the AP through a normal association establishment process (including probe, authentication, association, 4-way handshake exchange). After association, STA1 and STA2 can create a TDLS link. Before the TDLS link can be created, STA1, as the initiator, can discover the capabilities of STA2, the responder, by sending a discovery request to STA2. If STA2 supports TDLS, it will respond with a discovery response sent directly (without going through the AP) to STA1. Then, STA1 sends a setup request to create the TDLS link to STA2. STA2 responds with a setup response. After that, STA1 sends a setup confirmation. Note that the setup request / response / confirmation are all sent through the AP. After the setup confirmation, the data connection can start between STA1 and STA2. If either of the two STAs wants to terminate the TDLS link, it can terminate the link by sending a Teardown message. The Teardown message can be sent either through the AP or directly to the receiving STA. Note that the Teardown message only terminates the TDLS link and does not terminate the association between the STA and the AP. In other words, after tearing down the TDLS link, the STA can still be associated with the AP.

[0011] Note that from the perspective of the AP, the AP only sees the data frames from the STA. From the perspective of the STA, it sees the TDLS frames from another STA. Also note that the TDLS frame is an action frame (part of the management frame) (see the TDLS action frame format in Section 9.6 of 802.11REVme_D1.3). Figure 3a The TDLS frame is shown from the perspective of the AP. During the TDLS process, the AP only sees the encrypted data in the data frame and just forwards the data frame to the destination STA. Figure 3b The TDSL frame is shown from the perspective of the STA. The STA can decrypt the data frame and see the TDLS action frame (e.g., TDLS setup request, TDLS setup response, etc.). As shown, the TDLS action frame is encapsulated in the data frame, DA is the destination address, SA is the source address, and FCS is the frame check sequence.

[0012] However, the RCM solution discussed above is designed for the AP to identify the STA. For a TDLS link created between two STAs (such as STA1 and STA2), since the AP does not share the device identification information of one STA (such as STA1) with the other STA (such as STA2), the two STAs participating in the TDLS link cannot identify each other.

[0013] Therefore, it is desired to achieve identification between the two STAs in a TDLS connection. Summary of the Invention

[0014] The present invention aims to introduce a simplified concept of wireless device identification in TDLS connections. The present invention is not intended to identify the key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0015] 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 that, when executed by the at least one processor, cause the first wireless device to at least: obtain at least one of the following during a tunnel direct link setup (TDLS) process between the first wireless device and a second wireless device: at least one TDLS identification information of the first wireless device and at least one TDLS identification information of the second wireless device.

[0016] According to a second aspect of the present disclosure, a method performed by a first wireless device is provided. The method includes: obtaining at least one of the following during a tunnel direct link setup (TDLS) process between the first wireless device and a second wireless device: at least one TDLS identification information of the first wireless device and at least one TDLS identification information of the second wireless device.

[0017] According to a third aspect of the present disclosure, a first wireless device is provided. The first wireless device includes components for performing the steps of any method according to the second aspect.

[0018] According to a fourth aspect of the present disclosure, a computer-readable medium including program instructions is provided, which, when executed by a device, cause the device to perform any method according to the second aspect.

[0019] According to a fifth aspect of the present disclosure, a computer program product including program instructions is provided, which, when executed by at least one processor, cause at least one processor to perform any method according to the second aspect.

[0020] It should be understood that the summary of the invention section is not intended to identify the key or essential features of the 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

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

[0022] Figure 1 is a schematic diagram showing an AP identifying a STA during an association process;

[0023] Figure 2is a schematic diagram showing the signaling flow of the TDLS process;

[0024] Figure 3a is a diagram showing a TDLS frame from the perspective of an AP;

[0025] Figure 3b is a diagram showing a TDLS frame from the perspective of a STA;

[0026] Figure 4 is a schematic diagram showing that no identification occurs between STAs during the TDLS process;

[0027] Figure 5 An example scenario is shown in which two STAs cannot recognize each other in a TDLS connection;

[0028] Figure 6 is a schematic diagram showing an identification process between two STAs in a TDSL connection according to various embodiments of the present disclosure;

[0029] Figure 7 is a flow chart depicting a method performed by a first wireless device according to some embodiments of the present disclosure;

[0030] Figures 8a - 8f Several methods for acquiring TDLS identification information of a first wireless device and a second wireless device according to some embodiments of the present disclosure are shown;

[0031] Figure 9 An existing TDLS action frame as defined in 802.11REVme_D1.3 is shown;

[0032] Figure 10 shows the format of a TDLS Identification Information Element (TIIE) according to some embodiments of the present disclosure;

[0033] Figure 11 An example scenario is shown in which a TDLS connection cannot be established because STA2 changes its MAC address in the second association;

[0034] Figure 12a , Figure 12b and Figure 12c shows an exemplary TDLS frame used in the discovery process according to some embodiments of the present disclosure;

[0035] Figure 13 shows exemplary scenarios in which some embodiments of the present disclosure may be implemented;

[0036] Figure 14 illustrates exemplary scenarios in which some embodiments of the present disclosure may be implemented; and

[0037] Figure 15A simplified block diagram of an apparatus according to some embodiments of the present disclosure is shown. Detailed Description

[0038] 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 denote like elements.

[0039] In the following description 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.

[0040] References in this disclosure to "one embodiment", "an embodiment", "example embodiment", etc., mean that the described embodiment may include a particular feature, structure, or characteristic, but not necessarily every embodiment includes that particular feature, structure, or characteristic. Moreover, these phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments (whether or not explicitly described).

[0041] It should be understood that although terms such as "first" and "second" 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, without departing from the scope of example embodiments, a first element may be termed a second element, and similarly, a second element may be termed a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0042] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit example embodiments. As used herein, the singular forms "a", "an" and "the" are also intended to include the plural forms unless the context clearly dictates otherwise. It will also be understood that the terms "comprises", "comprising", "has", "having", "includes", "including" 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.

[0043] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0044] (a) only hardware circuit implementations (such as those in only analog and / or digital circuitry) and

[0045] (b) A combination of hardware circuitry and software, such as (where applicable):

[0046] (i) A combination of one or more analog and / or digital hardware circuits with software / firmware, and

[0047] (ii) Any portion of one or more hardware processors with software (including one or more digital signal processors, software, and one or more memories, which work together to enable a device such as a mobile phone or server to perform various functions) and

[0048] (c) One or more hardware circuits and / or one or more processors (such as one or more microprocessors or a portion of one or more microprocessors) that require software (e.g., firmware) for operation, but the software may be absent when not required for operation.

[0049] This definition of circuitry applies to all uses of the term in this application (including in any claim). As a further 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 and its (or their) attendant software and / or firmware. The term circuitry also encompasses (e.g., and if applicable to a particular claim element) 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 device.

[0050] As used herein, the term "wireless network" refers to a Wi-Fi network that follows any suitable communication standard (e.g., the 802.11 standard). In addition, communication between a wireless device (e.g., a wireless station (STA) or an access point (AP)) and another wireless device (e.g., an access point (AP) or a wireless station (STA)) in a wireless network can be carried out 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 that utilize the present disclosure. The scope of the present disclosure should not be limited to the above systems.

[0051] As used herein, the term "wireless device" refers to any device capable of wireless communication with another device via a wireless network. By way of example and not limitation, a wireless device can refer to a wireless station or other suitable device. A wireless device can include, but is not limited to, a user equipment (UE) (e.g., a mobile phone, a smartphone, a tablet, a wearable device, etc.), an electrical appliance with wireless capabilities, an Internet of Things (IoT) device, a vehicle-mounted wireless device, etc.

[0052] As used herein, the term "access device" refers to a device in a wireless network through which a wireless device accesses the wireless network. The access device may refer to an access point (AP).

[0053] As described above, currently, in a TDLS connection, STAs cannot identify each other because they do not have the device identification information of the peer STAs. Figure 4 It shows that no identification occurs between STAs during the TDLS process. As Figure 4 shown, at (1), STA1 and STA2 start the association establishment process with the AP (including probing, authentication, association, four-way handshake exchange), and each of STA1 and STA2 is assigned a unique device identification information (ID or RMA). STA1 and STA2 will use the assigned device identification information in subsequent (multiple) associations. After associating with the AP, STA1 and STA1 create a TDLS connection and communicate with each other at (2), where STA1 is the initiator and STA2 is the responder. Later, STA1 and STA2 terminate the TDLS connection at (3), and then disconnect from the AP at (4). Subsequently, STA1 and STA2 associate with the AP again at (5). In this association, STA1 uses its own assigned (from the previous association) device identification information (ID or RMA), and STA2 uses its own assigned (from the previous association) device identification information (ID or RMA). Since the AP knows the device identification information of STA1 and STA2, the AP can identify STA1 and STA2 without any problem. Then, STA1 creates a TDLS connection with STA2 again at (6). During this TDLS process, since STA2 does not know the device identification information of STA1, STA2 cannot identify STA1. In other words, STA2 considers STA1 as a "new" device rather than a known device.

[0054] Figure 5 It shows an example scenario where two STAs cannot identify each other in a TDLS connection. As Figure 5As shown, assume that STA1 is a user equipment (UE) and STA2 is a TV. When the UE (STA1) and the TV (STA2) are connected to the same AP in the home and the UE and the TV are assigned their device identification information in the current association. The UE can establish a TDLS connection with the TV. For example, a user of the UE plays a movie on the UE and the movie is projected onto the TV. Assume that the user leaves home after only watching half of the movie, so the UE terminates the TDLS connection and disconnects from the AP. When the user returns home and reconnects to the AP, the UE uses the device identification information assigned to it from the previous association. At this time, the AP recognizes the UE. However, when the UE creates a TDLS connection with the TV again, since the TV does not know the device identification information of the UE, the TV cannot recognize the UE. In this case, if the user wants to continue watching the movie, the movie cannot be played from where it was left off, but starts from the beginning because the UE is regarded as a "new" device by the TV.

[0055] Therefore, it is desirable to have an identification mechanism between STAs in a TDLS connection so that STAs can identify each other.

[0056] As described above, the current scheme for identifying STAs using RMA mainly focuses on the AP identifying STAs. During the TDLS process, TDLS peer STAs with RMA do not identify each other because device identification information is not assigned between TDLS peer STAs, and the AP does not share the device identification information of a certain STA with another STA. Embodiments of the present disclosure propose to define a mechanism for the identification between two STAs in a TDLS connection. It should be noted that the identification between an STA and an AP is different from the identification between STAs in a TDLS connection.

[0057] Here, the term "identification between an STA and an AP" refers to the identification process in which device identification information is assigned between the STA and the AP during the association process. The STA uses the assigned device identification information when enabling RMA, so the AP can identify the STA. The term "identification between STAs in a TDLS connection" refers to the identification process in which device identification information is assigned between two STAs in a TDLS connection. TDLS peer STAs use the assigned device identification information when enabling RMA, so it can be recognized by another TDLS peer STA.

[0058] Figure 6Illustrates an exemplary process of identification between two STAs in a TDLS connection according to some embodiments of the present disclosure. As shown, in step 1, STA1 and STA2 are associated with the AP using MAC addresses (e.g., a common fixed MAC address). In this association, STA1 is assigned unique device identification information for use between STA1 and the AP, and STA2 is assigned unique device identification information for use between STA2 and the AP. After the association, in step 2, STA1 initiates a TDLS process with STA2, so STA1 acts as the initiator and STA2 acts as the responder. During the TDLS process, STA1 is assigned unique device identification information between STA1 and STA2. Here, to distinguish the device identification information between the STA and the AP and the device identification information between the STAs in the TDLS connection, the term "TDLS identification information" is used to refer to the device identification information between the STAs used to identify the STAs in the TDLS connection. The TDLS identification information can be carried, for example, in a TDLS identification information element (TIIE) of a TDLS action frame (which will be described later). After some time, STA1 and STA2 can terminate the TDLS process.

[0059] In step 3, STA1 disconnects from the AP and reassociates with the same AP using the previously assigned device identification information between STA1 and the AP. Then in step 4, after successful reassociation, STA1 starts a TDLS process with the STA and uses the previously assigned TDLS identification information. Then STA2 can identify STA1 based on the TDLS identification information of STA1.

[0060] Although only one STA (e.g., STA1) is assigned TDLS identification information in the above exemplary process, it can be understood that the other STA (e.g., STA2) or both STAs can be assigned their respective TDLS identification information for identification between the STAs in the TDLS connection.

[0061] will be referred to Figures 7 to 11 to describe more details of exemplary embodiments according to the present disclosure.

[0062] Figure 7 is a flowchart depicting a method 1000 performed by a first wireless device according to some embodiments of the present disclosure. In some embodiments, the first wireless device can be a wireless station (STA) in a Wi-Fi network.

[0063] As Figure 7As shown, during a TDLS process between a first wireless device and a second wireless device, the first wireless device obtains at least one of the following at block 710: at least one TDLS identification information of the first wireless device and at least one TDLS identification information of the second wireless device. In some embodiments, the second wireless device may be another wireless station (STA) in a Wi-Fi network. As described above, the TDLS identification information of a wireless device can be used to uniquely identify the wireless device during the TDLS process.

[0064] When an STA (also referred to as a TDLS STA) in a TDLS connection enables RMA, it will be assigned TDLS identification information so that when the TDLS STA uses the assigned TDLS identification information, the TDLS STA can be identified by another TDLS STA. In some embodiments, the TDLS identification information may include at least one of the following: an identifier, a random MAC address (RMA), or information related to the generation of the identifier and / or the random MAC address.

[0065] In some embodiments, the identifier is a unique ID for identifying the TDLS STA. Note that the identifier is different from the MAC address used in the MAC header. The ID is carried in the MAC payload. In other words, when the TDLS STA uses an unrecognizable RMA in its MAC header, it sends the ID to be identified by another TDLS STA. In some embodiments, the ID may include at least one of the following: public information or private information. In some embodiments, the public information may include at least one of the following: a field in the MAC header, a public key, a public ID, a public device name, a public MAC address, a random number, time information, or a public signature. In some embodiments, the private information may include at least one of the following: a private key, a private ID, a private device name, a private MAC address, a private signature, or a random number.

[0066] In some embodiments, the RMA is a unique random MAC address for identifying the TDLS STA. The RMA will be used as the MAC address in the MAC header. The RMA is recognizable because the TDLS STA has determined the RMA in advance.

[0067] In some embodiments, the information related to the generation of the ID and / or the RMA may be additional information for generating the ID and / or the RMA to identify the TDLS STA. In some embodiments, the additional information may include at least one of the following: public information or private information. In some embodiments, the public information may include at least one of the following: a field in the MAC header, a public key, a public ID, a random number, time information, or a public signature. In some embodiments, the private information may include at least one of the following: a private key, a private ID, a private signature, or a random number.

[0068] Note that the above ID and / or RMA are the exact identification information to be used by the TDLS STA. Such additional information is not explicit identification information but helps to generate the ID and / or RMA. For example, peer TDLS STAs can exchange private keys to generate the ID and / or RMA. Note that the additional information can be any information carried in the MAC payload or MAC header.

[0069] In some embodiments, in the obtaining step of block 710, the first wireless device may assign at least one TDLS identification information to itself. Then, the first wireless device may notify the second wireless device of at least one TDLS identification information of the first wireless device that has been assigned, so that in subsequent TDLS processes, when the first wireless device sends its TDLS identification information, the second wireless device can identify the first wireless device. In this case, the first wireless device can be the initiator or responder in the TDLS process. Figure 8a and 8b illustrates such a situation. In Figure 8a , the first wireless device is denoted as STA1, which acts as the initiator, and the second wireless device is denoted as STA2, which acts as the responder. In Figure 8b , the first wireless device is denoted as STA2, which acts as the responder, and the second wireless device is denoted as STA1, which acts as the initiator.

[0070] Alternatively, in some embodiments, in the obtaining step of block 710, the first wireless device may receive at least one TDLS identification information of the first wireless device from the second wireless device. That is, the second wireless device assigns at least one TDLS identification information to the first wireless device and then sends the assigned at least one TDLS identification information of the first wireless device to the first wireless device. The second wireless device may send the assigned TDLS identification information in subsequent TDLS processes for the first wireless device to identify. In this case, the first wireless device can be the initiator or responder in the TDLS process. Figure 8c and 8d illustrates such a situation. In Figure 8c , the first wireless device is denoted as STA2, which acts as the responder, and the second wireless device is denoted as STA1, which acts as the initiator. In Figure 8d , the first wireless device is denoted as STA1, which acts as the initiator, and the second wireless device is denoted as STA2, which acts as the responder.

[0071] Alternatively, in some embodiments, in the obtaining step of block 710, the first wireless device may receive at least one TDLS identification information of the first wireless device from an AP with which both the first wireless device and the second wireless device are associated. Then, the first wireless device may send at least one TDLS identification information of the first wireless device to the second wireless device. In this case, the first wireless device may be an initiator or a responder in the TDLS process. Figure 8e and 8f illustrates this case. In Figure 8e , the first wireless device is denoted as STA1, which acts as the initiator, and the second wireless device is denoted as STA2, which acts as the responder. In Figure 8f , the first wireless device is denoted as STA2, which acts as the responder, and the second wireless device is denoted as STA1, which acts as the initiator.

[0072] Alternatively, in some embodiments, in the obtaining step of block 710, the first wireless device may receive at least one TDLS identification information of the second wireless device from the second wireless device. Thus, the first wireless device may identify the second wireless device in subsequent TDLS process(es). In this case, the first wireless device may be an initiator or a responder in the TDLS process. When the first wireless device is the initiator, this case may correspond to Figure 8b or the case shown in 8f. When the first wireless device is the responder, this case may correspond to Figure 8a or the case shown in 8e.

[0073] In some embodiments, the TDLS identification information of a wireless device may be the same as the device identification information of the wireless device used between the wireless device and an AP. For example, when a STA is assigned device identification information by an AP during the association process, this device identification information may be reused by the STA as TDLS identification information during the TDSL process.

[0074] In some embodiments, the TDLS identification information may be carried in a TDLS action frame for transmission between the first wireless device and the second wireless device. The TDLS process utilizes TDLS action frames. In 802.11REVme_D1.3, Section 9.6.12 defines 11 TDLS action frames, and Section 9.6.7.12 defines 1 TDLS common action frame, as Figure 9As shown. According to the method of obtaining TDLS identification information shown in FIGS. 8A - 8F, the TDLS action frame carrying the TDLS identification information can be changed. For example, if the initiating STA assigns TDLS identification information to itself, it can signal its TDLS identification information to the responding STA in the TDLS establishment request. Similarly, if the initiating STA assigns TDLS identification information to the responding STA, it can signal the TDLS identification information to the responding STA in the TDLS establishment confirmation. If the responding STA assigns TDLS identification information to itself, it can signal its TDLS identification information to the initiating STA in the TDLS establishment response.

[0075] In some embodiments, the TDLS identification information can be carried in the TDLS identification IE in the TDLS action frame. Here, a TDLS identification IE (TIIE) is introduced to carry the TDLS identification information. The current 802.11 REVme_D1.3 defines several information elements, see Table 9 - 128 - the element IDs in 802.11 REVme_D1.3. The TDLS identification information element (TIIE) can be defined as element ID = 255, element ID extension = 94, extensible = no, segmentable = no. Figure 10 The format of the TIIE is shown.

[0076] Note that the TDLS action frame is encrypted (i.e., encapsulated in a data frame) because the TDLS STA is associated with the AP and has created a security key for encryption with the AP before starting the TDLS process. Therefore, the TDLS identification information element can be securely carried in any TDLS action frame. In other words, a third party cannot decrypt the TDLS action frame unless it has the key for decryption. The following describes how the TDLS identification information element (TIIE) is carried in, for example, the TDLS establishment request or the TDLS establishment response.

[0077] TDLS identification information element (TIIE) in the TDLS establishment request

[0078] The current 802.11 REVme_D1.3 defines 25 items in the TDLS establishment request frame body (see Table 9.497 in 802.11 REVme_D1.3). As shown in Table 1, the order of the TDLS identification information element (TIIE) is Order = 26. This field carries the device identification information for the TDLS process, i.e., the TDLS identification information.

[0079] Table 1

[0080]

[0081] TDLS Identification Information Element (TIIE) in the TDLS Setup Response

[0082] Currently, 802.11 REVme_D1.3 defines 27 items in the TDLS Setup Response frame body (see Table 9.497 in 802.11 REVme_D1.3). As shown in Table 2, the order of the TDLS Identification Information Element (TIIE) is Order = 28. This field carries device identification information for the TDLS process, i.e., the TDLS identification information.

[0083] Table 2

[0084]

[0085] In addition, in some embodiments, after obtaining at least one TDLS identification information of the first wireless device and / or the second wireless device, the first wireless device may send one TDLS identification information of the at least one TDLS identification information of the first wireless device to the second wireless device during the subsequent TDLS process. Then, the second wireless device may identify the first wireless device based on the TDLS identification information of the first wireless device.

[0086] Alternatively or additionally, in some embodiments, after obtaining at least one TDLS identification information of the first wireless device and / or the second wireless device, the first wireless device may receive one TDLS identification information of the at least one TDLS identification information of the second wireless device from the second wireless device during the subsequent TDLS process. Then, the first wireless device may identify the second wireless device based on the received TDLS identification information of the second wireless device.

[0087] In addition, during the TDLS process, especially in subsequent TDLS processes, a TDLS connection may fail to be created because the initiating TDLS STA does not receive a TDLS Setup Response from the responding TDLS STA. This is because both the initiating TDLS STA and the responding TDLS STA may randomize their MAC addresses when re-associating with the AP, resulting in the TDLS Setup Request not being sent to the responding TDLS STA. Figure 11 An example scenario is shown where a TDLS connection cannot be created because STA2 changes its MAC address in the second association. As Figure 11As shown, in the first association, STA1 and STA2 associate with the AP using their MAC addresses (e.g., STA1_MAC, STA2_MAC). Then, STA1 and STA2 initiate the TDLS process. During the TDLS process, STA1 assigns STA1_ID1 = 10 to itself as TDLS identification information and sends it to STA2 in the TIIE in the TDLS setup request. This ID, i.e., STA1_ID1, will be used in the second association. STA2 assigns STA2_ID1 = 20 to itself as TDLS identification information and sends it to STA1 in the TIIE in the TDLS establishment response. This ID, i.e., STA2_ID1, will be used in the second association. Then, STA1 and STA2 continue the TDLS process and terminate the TDLS process after a period of time. Then, STA1 and STA2 disconnect from the AP. In the second association, STA1 and STA2 associate with the AP again using random MAC addresses (e.g., STA1_RMA1, STA2_RMA1). Then, STA1 wants to start the TDLS process with STA2. During the TDLS process, STA1 sends the previously assigned (from the first association) STA1_ID1 = 10 in the TIIE in the TDLS establishment request. When STA1 constructs the TDLS establishment request, it uses DA = STA2_MAC because STA1_ID1 = 10 has been stored for DA = STA2_MAC. However, since STA2 has changed its MAC address to STA2_RMA1, STA2_MAC does not exist in the network. Therefore, STA1 will not be able to obtain a response from STA2 and the TDLS connection cannot be established. Thus, TDLS STAs need to perform a discovery process during the TDLS process to discover each other.

[0088] In some embodiments, during the TDLS process, before sending the TDLS identification information of the first wireless device to the second wireless device, the first wireless device may use information related to the second wireless device from a previous TDLS process / connection to discover the second wireless device.

[0089] In some embodiments, to discover a second wireless device, the first wireless device may send information related to the second wireless device from a previous TDLS process / connection in a TDLS discovery request with a broadcast destination address (DA) (i.e., DA = FF:FF:FF:FF:FF:FF). Thus, each STA associated with the AP will accept this TDLS discovery request. Since the information related to the second wireless device is carried in the TDLS discovery request, only the second wireless device will respond to the TDLS discovery request. Therefore, the first wireless device can receive a TDLS discovery response from the second wireless device and obtain the current device identification information of the second wireless device from the source address (SA) field in the TDLS discovery response.

[0090] In some embodiments, the information related to the second wireless device from a previous TDLS process / connection may be the TDLS identification information (such as ID or RMA) of the second wireless device previously assigned in the previous TDLS process. In this case, the TDLS identification information of the second wireless device can be carried in the TIIE in the TDLS discovery request. In Figure 11 the above example in, to discover STA2, STA1 sends the TDLS identification information of STA2 (e.g., the previously assigned STA2_ID1 = 20) in the TIIE in a TDLS discovery request with a broadcast DA (i.e., DA = FF:FF:FF:FF:FF:FF). This means that each STA associated with the AP will accept this TDLS discovery request. However, since the TDLS discovery request carries the TDLS identification information of STA2, only STA2 will respond to this TDLS discovery request, i.e., STA2 will send a TDLS discovery response with SA = STA2_RMA1 to STA1. At this time, STA1 discovers the RMA of STA2 (i.e., STA2_RMA1) and identifies STA2, and thus can construct a TDLS establishment request and initiate a TDLS process. FIG. 12A shows an example of a TDLS frame used in the discovery process.

[0091] Alternatively, in some embodiments, the information related to the second wireless device from a previous TDLS process / connection may be the previous device identification information (such as MAC address or ID) of the second wireless device. In this case, the device identification information of the second wireless device can be carried in the TIIE in the TDLS discovery request. In Figure 11In the above example, to discover STA2, STA1 sends the previous device identification information of STA2 (e.g., STA2_MAC used in the first association) in the TIIE of the TDLS discovery request with a broadcast DA (i.e., DA = FF:FF:FF:FF:FF:FF). This means that each STA associated with the AP will accept this TDLS discovery request. However, since the TDLS discovery request carries the previous device identification information of STA2, only STA2 will respond to this TDLS discovery request, i.e., STA2 will send a TDLS discovery response with SA = STA2_RMA1 to STA1. At this time, STA1 discovers the RMA of STA2 (i.e., STA2_RMA1) and identifies STA2, so it can construct a TDLS establishment request frame and start the TDLS process. It should be noted that in this embodiment, the TDLS STA (e.g., Figure 11 STA1 and STA2 in Figure 11 need to store the previous device identification information of the responding TDLS STA (e.g.,

[0092] STA2_MAC in Figure 11 ). Figure 12B shows another example of the TDLS frame used in the discovery process. Figure 11The STA1 and STA2 in it store the link identifier IE from the previous TDLS connection. FIG. 12C shows another example of a TDLS frame used in the discovery process.

[0093] Figure 13 FIG. shows an exemplary scenario in which some embodiments of the present disclosure may be implemented. In this exemplary scenario, STA1 is the initiator and STA2 is the responder.

[0094] As Figure 13 shown, in the first association, STA1 and STA2 associate with the AP using their MAC addresses (e.g., STA1_MAC, STA2_MAC). Then, STA1 and STA2 start the TDLS process. During the TDLS process, STA1 assigns STA1_ID1 = 10 as TDLS identification information to itself and sends it to STA2 in the TIIE in the TDLS establishment request. This ID (i.e., STA1_ID1) will be used in the second association. STA2 assigns STA2_ID1 = 20 as TDLS identification information to itself and sends it to STA1 in the TIIE in the TDLS establishment response. This ID (i.e., STA2_ID1) will be used in the second association. Then, STA1 and STA2 continue the TDLS process and terminate the TDLS process after a period of time. Then, STA1 and STA2 disconnect from the AP.

[0095] In the second association, STA1 and STA2 associate with the AP using random MAC addresses (e.g., STA1_RMA1, STA2_RMA1). Then, STA1 and STA2 start the TDLS process. During the TDLS process, STA1 sends the following items in the TIIE in the TDLS establishment request: the previously assigned (from the first association) STA1_ID1 = 10, and the newly generated STA1_ID2 = 11 as new TDLS identification information. After receiving the TDLS establishment request, STA2 identifies STA1 based on STA1_ID1 = 10. The new TDLS identification information can be used to identify STA1 in future TDLS processes. In addition, STA2 sends the following information in the TIIE in the TDLS establishment response: the previously assigned (from the first association) STA2_ID1 = 20, and the newly generated STA2_ID2 = 21 as new TDLS identification information. After receiving the TDLS establishment response, STA1 identifies STA2 based on STA2_ID1 = 20. The new TDLS identification information can be used to identify STA2 in future TDLS processes. Then, STA1 and STA2 continue the TDLS process and terminate the TDLS process after a period of time. Then, STA1 and STA2 disconnect from the AP.

[0096] In the third association, STA1 and STA2 associate with the AP using other random MAC addresses (e.g., STA1_RMA2, STA2_RMA2). Then, STA1 and STA2 start the TDLS process. During the TDLS process, STA1 sends the following items in the TIIE of the TDLS establishment request: the previously assigned (from the first association) STA1_ID2 = 11, and the newly generated STA1_ID3 = 12 as the new TDLS identification information. After receiving the TDLS establishment request, STA2 identifies STA1 based on STA1_ID2 = 11. The new TDLS identification information can be used to identify STA1 in future TDLS processes. In addition, STA2 sends the following items in the TIIE of the TDLS establishment response: the previously assigned (from the first association) STA2_ID2 = 21, and the newly generated STA2_ID3 = 22 as the new TDLS identification information. After receiving the TDLS establishment response, STA1 identifies STA2 according to STA2_ID2 = 21. The new TDLS identification information can be used to identify STA2 in future TDLS processes. Then, STA1 and STA2 continue the TDLS process and terminate the TDLS process after a period of time. Then, STA1 and STA2 disconnect from the AP.

[0097] Figure 14 An exemplary scenario is shown in which some embodiments of the present disclosure can be implemented. In this exemplary scenario, STA1 is the initiator, STA2 is the responder, and the TDLS identification information used in the TDLS process is the same as the device identification information between the STA and the AP.

[0098] As Figure 14As shown, in the first association, STA1 and STA2 associate with the AP using their MAC addresses (e.g., STA1_MAC, STA2_MAC). During the association, the AP assigns STA1_RMA1 = AA to STA1 as the device identification information between STA1 and the AP, and the AP assigns STA2_RMA1 = BB to STA2 as the device identification information between STA2 and the AP. Then, STA1 and STA2 start the TDLS process. During the TDLS process, STA1 assigns STA1_RMA1 = AA to itself as its TDLS identification information and sends it to STA2 in the TIIE in the TDLS establishment request. This RMA will be used for the second association. STA2 assigns STA2_RMA1 = BB to itself as its TDLS identification information and sends it to STA1 in the TIIE in the TDLS establishment response. This RMA will be used for the second association. Then, STA1 and STA2 continue the TDLS process and terminate the TDLS process after a period of time. Then, STA1 and STA2 disconnect from the AP.

[0099] In the second association, STA1 and STA2 establish an association with the AP using the previously assigned (from the first association) random MAC addresses (i.e., STA1_RMA1 = AA and STA2_RMA1 = BB). Then, STA1 and STA2 start the TDLS process. During the TDLS process, STA1 sends the previously assigned (from the first association) STA1_RMA1 = AA in the MAC header and / or the link identifier IE (which contains the MAC address of the TDLS peer STA in the TDLS action frame) in the TDLS establishment request. After receiving the TDLS establishment request, STA2 identifies STA1 based on STA1_RMA1 = AA. In addition, STA2 sends the previously assigned (from the first association) STA2_RMA1 = BB in the MAC header in the TDLS establishment response. After receiving the TDLS establishment response, STA1 identifies STA2 based on STA2_RMA1 = BB. Then, STA1 and STA2 continue the TDLS process and terminate the TDLS process after a period of time. Then, STA1 and STA2 disconnect from the AP.

[0100] Now refer to Figure 15 , Figure 15 FIG. shows a simplified block diagram of a device 1500 that may be embodied as a first wireless device. The device 1500 may include at least one processor 1501, such as a data processor (DP), and at least one memory (MEM) 1502 coupled to the at least one processor 1501. The device 1500 may also include a transmission unit and a reception unit 1503 coupled to one or more processors 1501.

[0101] The processor 1501 can be of any type suitable for the local technical environment and, by way of non-limiting example, 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.

[0102] (The) MEM 1502 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, by way of non-limiting example.

[0103] MEM 1502 stores a program (PROG) 1504. PROG 1504 can include instructions that, when executed on the associated processor 1501, cause the device 1500 to operate in accordance with an embodiment of the present disclosure, for example, to execute one of the methods 700 as Figure 7 shown. The combination of at least one processor 1501 and at least one MEM 1502 can form a processing circuitry or component 1505 suitable for implementing various embodiments of the present disclosure.

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

[0105] In general, the various exemplary embodiments can be implemented in hardware or a dedicated circuit, 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 that can be executed by a controller, a microprocessor, or other computing devices, but the present invention is not limited thereto. Although aspects of the exemplary embodiments of the present disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that the blocks, devices, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, a dedicated circuit or logic, general hardware or a controller, or other computing devices, or some combination thereof, by way of non-limiting example.

[0106] Therefore, 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. Therefore, it should be understood that the exemplary embodiments of the present disclosure can be implemented in a device embodied as an integrated circuit, where the integrated circuit can include circuitry for embodying at least one or more of the following: a data processor, a digital signal processor, a baseband circuitry, and a radio frequency circuitry, which is configurable to operate in accordance with the exemplary embodiments of the present disclosure.

[0107] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure may be embodied in computer-executable instructions executed by one or more computers or other devices, such as embodied 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 may be stored on a computer-readable medium, for example, a non-transitory computer-readable medium such as a hard disk, an optical disk, a removable storage medium, a solid-state memory, a RAM, etc. As will be understood by those skilled in the art, the functions of the program modules may be combined or distributed as required in various embodiments. In addition, the functions may be embodied in whole or in part in firmware or hardware equivalents, such as integrated circuits, field-programmable gate arrays (FPGAs), etc.

[0108] In addition, although the operations are described 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 details should not be construed as limiting the scope of the present disclosure, but rather as describing features that are specific to particular embodiments. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0109] The present disclosure includes any novel feature or combination of features explicitly or implicitly disclosed herein. Various modifications and adaptations may be made by those skilled in the art to the foregoing exemplary embodiments of the present disclosure when read in conjunction with the accompanying drawings. However, any and all modifications 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: during a tunnel direct link setup (TDLS) procedure between the first wireless device and a second wireless device, obtain at least one of: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of the second wireless device.

2. The first wireless device according to claim 1, wherein, in order to obtain at least one of: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of a second wireless device, the first wireless device is caused to: allocate the at least one TDLS identification information to the first wireless device; and send the at least one TDLS identification information of the first wireless device to the second wireless device.

3. The first wireless device according to claim 1, wherein, in order to obtain at least one of: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of a second wireless device, the first wireless device is caused to: receive the at least one TDLS identification information of the first wireless device from the second wireless device.

4. The first wireless device according to claim 1, wherein, in order to obtain at least one of: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of a second wireless device, the first wireless device is caused to: receive the at least one TDLS identification information of the first wireless device from an access point, both the first wireless device and the second wireless device being associated with the access point; and send the at least one TDLS identification information of the first wireless device to the second wireless device.

5. The first wireless device according to any one of claims 1 to 4, wherein, in order to obtain at least one of: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of a second wireless device, the first wireless device is caused to: allocate the at least one TDLS identification information to the second wireless device; and send the at least one TDLS identification information of the second wireless device to the second wireless device.

6. The first wireless device according to any one of claims 1 to 4, wherein, in order to obtain at least one of: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of a second wireless device, the first wireless device is caused to: receive the at least one TDLS identification information of the second wireless device from the second wireless device.

7. The first wireless device according to any one of claims 1 to 6, wherein the first wireless device is further caused to: During a subsequent TDLS procedure, send one piece of TDLS identification information among the at least one piece of TDLS identification information of the first wireless device to the second wireless device.

8. The first wireless device according to any one of claims 1 to 7, wherein the first wireless device is further caused to: During a subsequent TDLS procedure, receive one piece of TDLS identification information among the at least one piece of TDLS identification information of the second wireless device from the second wireless device; and Identify the second wireless device based on the received TDLS identification information of the second wireless device.

9. The first wireless device according to any one of claims 1 to 8, wherein the TDLS identification information of the first wireless device or the second wireless device is the same as the device identification information of the first wireless device or the second wireless device used for the association between the first wireless device or the second wireless device and an access point.

10. The first wireless device according to any one of claims 1 to 9, wherein the TDLS identification information includes at least one of the following: an identifier, a random Media Access Control (MAC) address, or information related to the generation of the identifier and / or the random MAC address.

11. The first wireless device according to claim 10, wherein the identifier includes at least one of public information or private information, wherein the public information includes at least one of the following: a field in a MAC header, a public key, a public identifier, a public device name, a public MAC address, a random number, time information, or a public signature, and wherein the private information includes at least one of the following: a private key, a private identifier, a private device name, a private MAC address, a private signature, or a random number.

12. The first wireless device according to claim 10 or 11, wherein the information related to the generation of the identifier and / or the random MAC address includes: At least one of public information or private information, wherein the public information includes at least one of the following: a field in a MAC header, a public key, a public identifier, a random number, time information, or a public signature, and wherein the private information includes at least one of the following: a private key, a private identifier, a private signature, or a random number.

13. The first wireless device according to any one of claims 1 to 12, wherein the TDLS identification information is carried in a TDLS action frame.

14. The first wireless device according to claim 13, wherein the TDLS identification information is carried in any one of the following: a TDLS identification IE in the TDLS action frame, a link identifier IE in the TDLS action frame, or a MAC header of a MAC frame including the TDLS action frame.

15. The first wireless device according to claim 7, wherein the first wireless device is further caused to: Discover the second wireless device using information related to the second wireless device from a previous TDLS procedure.

16. The first wireless device according to claim 15, wherein in order to discover the second wireless device, the first wireless device is further caused to: In a TDLS discovery request with a broadcast destination address, send the information related to the second wireless device from a previous TDLS process; and Receive a TDLS discovery response from the second wireless device.

17. The first wireless device according to claim 15 or 16, wherein the information related to the second wireless device from a previous TDLS process includes one of the following items: the TDLS identification information of the second wireless device allocated in the previous TDLS process, the previous device identification information of the second wireless device, or a link identifier IE from the previous TDLS process.

18. The first wireless device according to claim 17, wherein the TDLS identification information of the second wireless device allocated in the previous TDLS process, and the previous device identification information of the second wireless device are carried in a TDLS identification IE in the TDLS discovery request.

19. The first wireless device according to any one of claims 1 to 18, wherein the first wireless device is one of an initiator and a responder in the TDLS process, and the second wireless device is the other of the initiator and the responder in the TDLS process.

20. A method performed by a first wireless device, the method comprising: During a tunnel direct link setup (TDLS) process between the first wireless device and a second wireless device, obtain at least one of the following: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of the second wireless device.

21. The method according to claim 20, wherein obtaining at least one of the following: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of the second wireless device includes: Allocate the at least one TDLS identification information to the first wireless device; And Send the at least one first TDLS identification information to the second wireless device.

22. The method according to claim 20, wherein obtaining at least one of the following: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of the second wireless device includes: Receive the at least one TDLS identification information of the first wireless device from the second wireless device.

23. The method according to claim 20, wherein obtaining at least one of the following: at least one TDLS identification information of the first wireless device, and at least one TDLS identification information of the second wireless device includes: Receive the at least one TDLS identification information of the first wireless device from an access point, both the first wireless device and the second wireless device being associated with the access point; And Send the at least one first TDLS identification information of the first wireless device to the second wireless device.

24. The method according to any one of claims 20 to 23, wherein obtaining at least one of the following: at least one TDLS identification information of the first wireless device and at least one TDLS identification information of the second wireless device includes: assigning the at least one TDLS identification information to the second wireless device; and sending the at least one TDLS identification information of the second wireless device to the second wireless device.

25. The method according to any one of claims 20 to 23, wherein obtaining at least one of the following: at least one TDLS identification information of the first wireless device and at least one TDLS identification information of the second wireless device includes: receiving the at least one TDLS identification information of the second wireless device from the second wireless device.

26. The method according to any one of claims 20 to 25, further comprising: sending, during a subsequent TDLS procedure, one piece of first TDLS identification information among the at least one piece of first TDLS identification information to the second wireless device.

27. The method according to any one of claims 20 to 26, further comprising: receiving, during a subsequent TDLS procedure, one piece of second TDLS identification information among the at least one piece of second TDLS identification information from the second wireless device; and identifying the second wireless device based on the received second TDLS identification information.

28. The method according to any one of claims 20 to 27, wherein the TDLS identification information is the same as the device identification information of the first wireless device or the second wireless device that is used for the association between the first wireless device or the second wireless device and an access point.

29. The method according to any one of claims 20 to 28, wherein the TDLS identification information includes at least one of the following: an identifier, a random Media Access Control (MAC) address, or information related to the generation of the identifier and / or the random MAC address.

30. The method according to claim 29, wherein the identifier includes at least one of public information or private information, wherein the public information includes at least one of the following: a field in a MAC header, a public key, a public identifier, a public device name, a public MAC address, a random number, time information, or a public signature, and wherein the private information includes at least one of the following: a private key, a private identifier, a private device name, a private MAC address, a private signature, or a random number.

31. The method according to claim 29 or 30, wherein the information related to the generation of the identifier and / or the random MAC address includes at least one of public information or private information, wherein the public information includes at least one of the following: a field in a MAC header, a public key, a public identifier, a random number, time information, or a public signature, and wherein the private information includes at least one of the following: a private key, a private identifier, a private signature, or a random number.

32. The method according to any one of claims 20 to 31, wherein the TDLS identification information is carried in a TDLS action frame.

33. The method according to claim 32, wherein the TDLS identification information is carried in any one of the following: a TDLS identification IE in the TDLS action frame, a link identifier IE in the TDLS action frame, or a MAC header of a MAC frame including the TDLS action frame.

34. The method according to claim 26, further comprising: discovering the second wireless device using information related to the second wireless device from a previous TDLS procedure.

35. The method according to claim 34, wherein discovering the second wireless device comprises: sending, in a TDLS discovery request with a broadcast destination address, the information related to the second wireless device from the previous TDLS procedure; and receiving a TDLS discovery response from the second wireless device.

36. The method according to claim 34 or 35, wherein the information related to the second wireless device from the previous TDLS procedure comprises one of the following items: the TDLS identification information of the second wireless device assigned in the previous TDLS procedure, the previous device identification information of the second wireless device, or a link identifier IE from the previous TDLS procedure.

37. The method according to claim 36, wherein the TDLS identification information of the second wireless device assigned in the previous TDLS procedure and the previous device identification information of the second wireless device are carried in a TDLS identification IE in the TDLS discovery request.

38. The method according to any one of claims 20 to 37, wherein the first wireless device is one of an initiator and a responder in the TDLS procedure, and the second wireless device is the other of the initiator and the responder in the TDLS procedure.

39. A computer-readable medium including program instructions that, when executed by a device, cause the device to perform the method according to any one of claims 20 to 38.

Images