Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/14—Direct-mode setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/11—Allocation or use of connection identifiers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/16—Interfaces between hierarchically similar devices
  • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

• Embodiments of the present disclosure generally relate to wireless communication, and more particularly, to methods and apparatuses for identification of wireless devices in Tunneled Direct Link Setup (TDLS) connection.
• TDLS Tunneled Direct Link Setup
• Random and changing MAC RCM
• a wireless station (STA) and an access point (AP) use a fixed unencrypted Media Access Control (MAC) address in frame headers, which causes a security concern by allowing others to track the STA and the AP based on their MAC addresses.
• MAC address randomization became a common technique.
• IEEE 802.11bh and 802.11bi groups focus on identification of STA using Random MAC Address (RMA) without decreasing user privacy.
• IEEE 802.11bh focuses on STA identification through MAC Randomization in pre-association phase, that is, the STA does not change its MAC address after the association with the AP (i.e., post-association) .
• IEEE 802.11bi will address privacy concerns as a part of its work and manage to solve the case where the STA can change its MAC address after the association.
• the STA is assigned with device identification information (e.g. an identifier (ID) or RMA) when the STA associates with the AP (e.g. the first association) , then the STA uses the assigned device identification information (e.g. ID or RMA) in later association (s) (e.g. the second association) .
• ID an identifier
• RMA device identification information
• FIG. 1 illustrates an existing process for identification of STA in an association procedure. As shown in FIG. 1, the STA uses a MAC address (e.g.
• the STA in current association (e.g. the first association) .
• the STA is assigned with device identification information (e.g. ID or RMA, depending on the identification method) .
• device identification information e.g. ID or RMA, depending on the identification method.
• the STA uses the previously assigned (e.g. from the first association) device identification information (e.g. ID or RMA) , and therefore the STA gets identified by the AP.
• the STA might be assigned multiple device identification information (e.g., multiple IDs or multiple RMAs) in one association (e.g., the first association) , and use at least one of them in later association (s) (e.g., the second association) .
• device identification information it covers single device identification information and multiple device identification information.
• Assignment of the device identification information may include: i) the AP assigns ID or RMA to the STA; ii) the STA assigns ID or RMA to itself; or iii) the AP and STA generates ID or RMA at each side through a common procedure (e.g. using ID or RMA generation function) .
• Tunneled direct link setup (TDLS)
• the Tunneled Direct-Link Setup allows two STAs to establish a direct connection.
• the STAs shall be associated to the same AP.
• Direct connection in TDLS means that one STA (e.g. STA1) sends TDLS frames encapsulated in data frames to the AP, and the AP forwards the TDLS frames encapsulated in data frames to the other STA (e.g. STA2) .
• STA1 sends TDLS frames encapsulated in data frames to the AP
• the other STA e.g. STA2
• two STAs send each other TDLS frames through the AP transparently.
• both STAs should support TDLS.
• the initiating STA is called an initiator, and the other STA is called a responder.
• FIG. 2 illustrates a signaling flow of a TDLS procedure.
• both STAs, STA1 and STA2 associates with AP through a normal association setup procedure (including probe, authentication, association, 4-way handshake exchanges) .
• STA1 and STA2 can establish a TDLS link.
• STA1 as the initiator, may discover the capabilities of STA 2 which is the responder, by sending a Discovery Request to STA2. If STA2 supports TDLS, it will respond with a Discovery Response that is sent directly (not through AP) to STA1. Then STA1 sends a Setup Request to establish the TDLS link to STA2.
• STA2 responds with a Setup Response. Afterwards, STA1 sends a Setup Confirm to STA2. Note that the Setup Request/Response/Confirm are all sent through the AP. After the Setup Confirm, data connection can start between STA1 and STA2. If any of the two STAs wants to terminate the TDLS link, they can terminate the link by sending a Teardown message. This Teardown message can both be sent through the AP or directly to the receiving STA. Note that the Teardown message only terminates the TDLS link, not the associations between the STAs and AP. In other words, the STAs may be still associated to the AP after they teardown the TDLS link.
• FIG. 3a illustrates the TDLS frame from the view point of AP.
• the AP In the TDLS procedure, the AP only sees encrypted data in the data frame and just forwards the data frame to the destination STA.
• FIG. 3b illustrates the TDSL frame from the view point of STA.
• the STA can decrypt the data frame and sees the TDLS action frame (for example, TDLS Setup Request, TDLS Setup Response etc. ) .
• the TDLS action frame is encapsulated in Data Frames, and DA is destination address, SA is source address, and FCS is frame check sequence.
• the above discussed RCM solutions aim at the identification of the STA by the AP and.
• the AP does not share the device identification information of a STA (e.g. STA1) with another STA (e.g. STA2)
• the two STAs involved in the TDLS link cannot identify each other.
• a first wireless device comprises 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 at least to obtain, during a Tunneled Direct Link Setup, TDLS, procedure between the first wireless device and a second wireless device, 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.
• TDLS Tunneled Direct Link Setup
• a method performed by a first wireless device comprises obtaining, during a Tunneled Direct Link Setup, TDLS, procedure between the first wireless device and a second wireless device, 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.
• TDLS Tunneled Direct Link Setup
• the first wireless device comprises means for performing steps of any method according to the second aspect.
• a computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform any method according to the second aspect.
• a computer program product comprising program instructions which when executed by at least one processor, cause the at least one processor to perform any method according to the second aspect.
• FIG. 1 is a schematic diagram illustrating identification of STA by AP in an association procedure.
• FIG. 2 is a schematic diagram illustrating a signaling flow of a TDLS procedure
• FIG. 3a is a diagram illustrating TDLS frame from the view point of AP
• FIG. 3b is a diagram illustrating TDLS frame from the view point of STA
• FIG. 4 is a schematic diagram illustrating no identification happens between STAs in a TDLS procedure
• FIG. 5 illustrates an exemplary scenario where two STAs in TDLS connection cannot identify each other
• FIG. 6 is a schematic diagram illustrating a process of identification between two STAs in TDSL connection according to various embodiments of the present disclosure
• FIG. 7 is a flow chart depicting a method performed by a first wireless device according to some embodiments of the present disclosure.
• FIG. 8a-8f illustrate several ways to obtain TDLS identification information of the first wireless device and the second wireless device according to some embodiments of the present disclosure
• FIG. 9 illustrates existing TDLS action frames as defined in 802.11REVme_D1.3;
• FIG. 10 illustrates a format of TDLS identification information element (TIIE) according to some embodiments of the present disclosure
• FIG. 11 illustrates an exemplary scenario in which TDLS connection cannot be established due to STA2 changing MAC address in the second association
• FIG. 12a, FIG. 12b and FIG. 12c illustrates exemplary TDLS frames used in a discovery process according to some embodiments of the present disclosure
• FIG. 13 illustrates an exemplary scenario in which some embodiments of the present disclosure can be implemented
• FIG. 14 illustrates an exemplary scenario in which some embodiments of the present disclosure can be implemented.
• FIG. 15 shows a simplified block diagram of an apparatus according to some embodiments of the present disclosure.
• references in the present disclosure to “one embodiment” , “an embodiment” , “an example embodiment” , and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
• first and 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 could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
• the term “and/or” includes any and all combinations of one or more of the listed terms.
• circuitry may refer to one or more or all of the following:
• circuitry applies to all uses of this term in this application, including in any claims.
• circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
• circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
• wireless network refers to a Wi-Fi network following any suitable communication standards, such as 802.11 standards.
• a wireless device e.g. a wireless station (STA) , or an access point (AP)
• another wireless device e.g. an access point (AP) , or a wireless station (STA)
• Wi-Fi communication protocols e.g. Wi-Fi protocols
• Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
• wireless device refers to any device that can wirelessly communicate with another device over a wireless network.
• the wireless device may refer to a wireless station, or other suitable devices.
• the wireless device may include, but not limited to, a user equipment (UE) (such as mobile phone, smart phone, tablet, wearable device, etc. ) , electric appliances with wireless capability, an Internet of Things (IoT) device, vehicle-mounted wireless device, etc.
• UE user equipment
• IoT Internet of Things
• the term “access device” refers to a device in a wireless network via which a wireless device accesses to the wireless network.
• the access device may refer to an access point (AP) .
• AP access point
• FIG. 4 illustrates no identification happens between STAs in a TDLS procedure.
• STA1 and STA2 start an association setup procedure (including probe, authentication, association, 4-way handshake exchanges) with the AP, and each of STA1 and STA2 is assigned with unique device identification information (ID or RMA) . Both STA1 and STA2 will use the assigned device identification information in later association (s) .
• ID or RMA unique device identification information
• STA1 and STA1 After associating with the AP, STA1 and STA1 establish a TDLS connection and communicate with each other at (2) , where STA1 acts as the initiator, and STA2 acts as the responder. After a while, STA1 and STA2 terminate the TDLS connection at (3) , and then disconnect from the AP at (4) . Later, STA1 and STA2 associate with the AP again at (5) . At this association, STA1 uses its own assigned (from the previous association) device identification information (ID or RMA) , and STA2 uses its own assigned (from previous association) device identification information (ID or RMA) .
• ID or RMA device identification information
• ID or RMA device identification information
• STA1 Since the AP knows STA1’s and STA2’s device identification information, the AP can identify STA1 and STA2 without any problem. Then STA1 establishes a TDLS connection with STA2 again at (6) . In this TDLS procedure, since STA2 does not know STA1’s device identification information, STA2 cannot identify STA1. In other word, STA2 thinks that STA1 is a “new” device, rather than a known device.
• FIG. 5 illustrates an exemplary scenario where the two STAs in the TDLS connection cannot identify each other.
• STA1 is a user equipment (UE)
• STA2 is a TV.
• STA1 and STA2 are connected to the same AP at home, and the UE and the TV are assigned with their device identification information in the current association.
• the UE can establish a TDLS connection with the TV. For instance, a user of the UE plays a movie on the UE and the movie is projected onto the TV. Assume that the user only watches half of the movie and leaves home, and thus the UE terminates the TDLS connection and disconnects from the AP.
• the UE uses its device identification information assigned from the previous association.
• the AP identifies the UE.
• the TV does not know the UE’s device identification information, the TV does not identify the UE. In this case, if the user wants to continue the movie, the movie cannot start from the half, rather, it starts from the beginning, as the UE is regarded as a “new” device by the TV.
• TDLS peer STAs with RMA do not identify each other because the TDLS peer STAs are not assigned with device identification information between each other, nor the AP shares a STA’s device identification information with another STA.
• Embodiments of the present disclosure propose to define a mechanism for identification between two STAs in TDLS connection. Note that the identification between STA and AP is different than the identification between STAs in TDLS connection.
• identification between STA and AP means an identification procedure where device identification information is assigned between STA and AP during the association procedure. The STA uses the assigned device identification information when it enables RMA, and therefore it can be identified by the AP.
• Term “identification between STAs in TDLS connection” means an identification procedure where device identification information is assigned between two STAs in TDLS connection. A TDLS peer STA uses the assigned device identification information when it enables RMA, and therefore it can be identified by the other TDLS peer STA.
• FIG. 6 illustrates an exemplary process of identification between two STAs in TDLS connection according to some embodiments of the present disclosure.
• STA1 and STA2 associate with AP with MAC address (e.g. a public fixed MAC address) .
• STA1 is assigned with unique device identification information used between STA1 and AP
• STA2 is assigned with unique device identification information used between STA2 and AP.
• STA1 initiates a TDLS procedure with STA2, and thus STA1 acts as the initiator and STA2 acts as the responder.
• STA1 is assigned with unique device identification information between STA1 and STA2.
• TDLS identification information is used to refer to the device identification information between STAs for identifying a STA in TDLS connection.
• the TDLS identification information may be carried in TDLS identification information element (TIIE) (which will be described later) of a TDLS action frame, for example.
• TIIE TDLS identification information element
• STA1 disconnects from AP, and associates with same AP again using the previously assigned device identification information between STA1 and AP. Then at step 4, after the successfully association, STA1 starts the TDLS procedure with STA, and uses the previously assigned TDLS identification information. Then STA2 can identify STA1 based on the STA1’s TDLS identification information.
• STA1 Although only one STA (e.g. STA1) is assigned with the TDLS identification information in the above exemplary process, it will be appreciated that the other STA (e.g. STA2) or both STAs can be assigned with its or their TDLS identification information for the identification between STAs in TDLS connection.
• FIG. 7 is a flow chart depicting a method 1000 performed by a first wireless device according to some embodiments of the present disclosure.
• the first wireless device may be a wireless station (STA) in a Wi-Fi network.
• STA wireless station
• the first wireless device obtains 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, at block 710.
• the second wireless device may be another wireless station (STA) in the Wi-Fi network.
• STA wireless station
• the TDLS identification information of a wireless device may be used to uniquely identify the wireless device in the TDLS procedure.
• the TDLS identification information may comprise at least one of the following: an identifier, a random MAC address (RMA) , or information related to generation of the identifier and/or the random MAC address.
• the identifier is a unique ID to identify a TDLS STA. Note that this identifier is different than a MAC Address used in a MAC header. This ID is carried in MAC payload. In other words, when the TDLS STA uses an unidentifiable RMA in its MAC header, it sends this ID to be identified by another TDLS STA.
• this ID may comprise at least one of: public information, or private information.
• the public information may comprise at least one of: a field in 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.
• the private information may comprise at least one of: a private key, a private ID, a private device name, a private MAC address, a private signature, or a random number.
• RMA is a unique random MAC address to identify a TDLS STA. This RMA will be used as MAC address in MAC header. This RMA is identifiable because the TDLS STA determines this RMA beforehand.
• the information related to generation of the ID and/or the RMA may be additional information used to generate the ID and/or RMA to identify a TDLS STA.
• the additional information may comprise at least one of: public information, or private information.
• the public information may comprise at least one of: a field in MAC header, a public key, a public ID, a random number, time information, or a public signature.
• the private information may comprise at least one of: a private key, a private ID, a private signature, or a random number.
• ID and/or RMA mentioned above are exact identification information to be used by the TDLS STA.
• additional information is not explicit identification information, rather, it helps to generate the ID and/or RMA.
• peer TDLS STAs can exchange a private key to generate an ID and/or RMA.
• the additional information can be any information carried in MAC payload or in MAC header.
• the first wireless device may assign the at least one TDLS identification information to itself. Then the first wireless device may inform the second wireless device of the assigned at least one TDLS identification information of the first wireless device, so that when the first wireless device sends its TDLS identification information in later TDLS procedure (s) , the second wireless device can identify the first wireless device.
• the first wireless device may be the initiator or the responder in the TDLS procedure.
• FIGs. 8a and 8b illustrates such the cases.
• the first wireless device is denoted as STA1 which acts as the initiator
• the second wireless device is denoted as STA2 which acts as the responder
• the first wireless device is denoted as STA2 which acts as the responder
• the second wireless device is denoted as STA1 which acts as the initiator.
• the first wireless device may receive the at least one TDLS identification information of the first wireless device from the second wireless device. That is, the second wireless device assigns the at least one TDLS identification information to the first wireless device, and then transmits the assigned at least one TDLS identification information of the first wireless device to the first wireless device.
• the second wireless device can send the assigned TDLS identification information in later TDLS procedure (s) for identification by the first wireless device.
• the first wireless device may be the initiator or the responder in the TDLS procedure.
• FIGs. 8c and 8d illustrates such the cases. In FIG.
• the first wireless device is denoted as STA2 which acts as the responder
• the second wireless device is denoted as STA1 which acts as the initiator
• the first wireless device is denoted as STA1 which acts as the initiator
• the second wireless device is denoted as STA2 which acts as the responder.
• the first wireless device may receive the 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 transmit the at least one TDLS identification information of the first wireless device to the second wireless device.
• the first wireless device may be the initiator or the responder in the TDLS procedure.
• FIGs. 8e and 8f illustrates such the cases.
• the first wireless device is denoted as STA1 which acts as the initiator
• the second wireless device is denoted as STA2 which acts as the responder.
• the first wireless device is denoted as STA2 which acts as the responder
• the second wireless device is denoted as STA1 which acts as the initiator.
• the first wireless device may receive the at least one TDLS identification information of the second wireless device from the second wireless device.
• the first wireless device can identify the second wireless device in later TDLS procedure (s) .
• the first wireless device may be the initiator or the responder in the TDLS procedure.
• the first wireless device is the initiator, such the case may correspond to the case shown in FIG. 8b or 8f.
• the first wireless device is the responder, such the case may correspond to the case shown in FIG. 8a or 8e.
• the TDLS identification information of the wireless device may be same as the device identification information of the wireless device used between the wireless device and the AP.
• the device identification information can be reused by the STA as the TDLS identification information during the TDSL procedure.
• 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 procedure utilizes TDLS action frames.
• Section 9.6.12 defines 11 TDLS action frames
• Section 9.6.7.12 defines 1 TDLS public action frame, as shown in FIG. 9.
• the TDLS action frame that carries the TDLS identification information may change. For example, if an initiator STA assigns the TDLS identification information to itself, it can signal its TDLS identification information to a responder STA in a TDLS setup request.
• the initiator STA assigns the TDLS identification information to the responder STA, it can signal the TDLS identification information to the responder STA in a TDLS setup confirm. If the responder STA assigns the TDLS identification information to itself, it can signal its TDLS identification information to the initiator STA in a TDLS setup response.
• the TDLS identification information may be carried in TDLS identification IE in the TDLS action frame.
• the TDLS identification IE (TIIE) is introduced to carry the TDLS identification information.
• the current 802.11REVme_D1.3 defines several Information Elements, see Table 9-128-Element IDs in 802.11REVme_D1.3.
• FIG. 10 illustrates a format of the TIIE.
• TDLS action frames are encrypted (i.e., encapsulated in data frames) because a TDLS STA is associated with AP and established security keys with the AP for encryption before starting TDLS procedure. Therefore, TDLS Identification Information Element is safe to be carried in any TDLS action frame. In other words, no third party can decrypt TDLS action frames unless it has the key for decryption.
• TIIE TDLS Identification Information Element
• TIIE TDLS identification Information Element
• the current 802.11REVme_D1.3 defines 25 items in TDLS Setup Request frame body (see table 9.497 in 802.11REVme_D1.3) .
• TIIE TDLS identification Information Element
• the current 802.11REVme_D1.3 defines 27 items in TDLS Setup Response frame body (see table 9.497 in 802.11REVme_D1.3) .
• the first wireless device may transmit one of the at least one TDLS identification information of the first wireless device to the second wireless device during a next TDLS procedure. Then the second wireless device can identify the first wireless device based on the TDLS identification information of the first wireless device.
• the first wireless device may receive one of the at least one TDLS identification information of the second wireless device from the second wireless device during a next TDLS procedure. Then the first wireless device may identify the second wireless device based on the received TDLS identification information of the second wireless device.
• FIG. 11 illustrates an exemplary scenario in which the TDLS connection cannot be established due to STA2 changing MAC address in the second association. As shown in FIG.
• STA1 and STA2 associate with AP using their MAC addresses (e.g. STA1_MAC, STA2_MAC) . Then STA1 and STA2 start the TDLS procedure.
• STA1 and STA2 continue the TDLS procedure and terminate the TDLS procedure after a while. Then STA1 and STA2 disconnects from AP.
• STA1 and STA2 associates with AP again using random MAC addresses (e.g. STA1_RMA1, STA2_RMA1) .
• STA1 wants to start the TDLS procedure with STA2.
• STA2_MAC does not exist in the network as STA2 has changed its MAC address to STA2_RMA1, Thus, STA1 will not get a response from STA2, and the TDLS connection will not be established. Therefore, a discovery process is needed for TDLS STAs to discover each other during the TDLS procedure.
• the first wireless device may discover the second wireless device using information related to the second wireless device from the previous TDLS procedure/connection.
• DA broadcast Destination Address
• every STA associated with AP will accept this TDLS Discovery Request.
• the first wireless device may receive TDLS Discovery Response from the second wireless device, thereby obtaining the current device identification information of the second wireless device from Source Address (SA) field in the TDLS Discovery Response.
• SA Source Address
• the information related to the second wireless device from the previous TDLS procedure/connection may be the TDLS identification information (e.g. ID or RMA) of the second wireless device previously assigned in the previous TDLS procedure.
• the TDLS identification information of the second wireless device may be carried in TIIE in TDLS Discovery Request.
• FIG. 12a illustrates an example of the TDLS frame used in the discovery process.
• the information related to the second wireless device from the previous TDLS procedure/connection may be the previous device identification information (e.g. MAC address or ID) of the second wireless device.
• the device identification information of the second wireless device may be carried in TIIE in TDLS Discovery Request.
• TDLS Discovery Request carries STA2’s previous device identification information
• SA STA2_RMA1
• STA1 discovers STA2’s RMA (i.e., STA2_RMA1) and identifies the STA2, hence can construct TDLS Setup request frame and start TDLS procedure.
• TDLS STAs e.g. STA1 and STA2 in FIG. 11
• FIG. 12b illustrates another example of the TDLS frame used in the discovery process.
• the information related to the second wireless device from the previous TDLS procedure/connection may be link identifier IE from the previous TDLS procedure/connection.
• Link identifier IE is already defined in TDLS connection and it contains MAC Addresses of TDLS peer STAs in TDLS action frames.
• DA FF: FF: FF: FF: FF: FF) .
• SA STA2_RMA1
• STA1 discovers STA2’s RMA (i.e., STA2_RMA1) and identifies the STA2, hence can construct TDLS Setup request frame and start TDLS procedure.
• TDLS STAs e.g. STA1 and STA2 in FIG. 11
• STA1 and STA2 in FIG. 11 are required to store the link identifier IE from the previous TDLS connection.
• FIG. 12c illustrates another example of the TDLS frame used in the discovery process.
• FIG. 13 illustrates an exemplary scenario in which some embodiments of the present disclosure can be implemented.
• STA1 is the initiator and STA2 is the responder.
• STA1 and STA2 associate with AP using their MAC addresses (e.g. STA1_MAC, STA2_MAC) . Then STA1 and STA2 start the TDLS procedure.
• This ID i.e., STA1_ID1
• This ID i.e., STA2_ID1
• STA1 and STA2 continue the TDLS procedure and terminate the TDLS procedure after a while. Then STA1 and STA2 disconnects from AP.
• STA1 and STA2 associates with AP using random MAC addresses (e.g. STA1_RMA1, STA2_RMA1) . Then STA1 and STA2 start the TDLS procedure.
• the new TDLS identification information may be used for identification of STA2 in future TDLS procedure.
• STA1 and STA2 continue the TDLS procedure and terminate the TDLS procedure after a while. Then STA1 and STA2 disconnects from AP.
• STA1 and STA2 associates with AP using other random MAC addresses (e.g. STA1_RMA2, STA2_RMA2) . Then STA1 and STA2 start the TDLS procedure.
• the new TDLS identification information may be used for identification of STA2 in future TDLS procedure.
• STA1 and STA2 continue the TDLS procedure and terminate the TDLS procedure after a while. Then STA1 and STA2 disconnects from AP.
• FIG. 14 illustrates an exemplary scenario in which some embodiments of the present disclosure can be implemented.
• STA1 is the initiator and STA2 is the responder, and the TDLS identification information used in the TDLS procedure is same as the device identification information between STA and AP.
• STA1 and STA2 associates with AP using their MAC addresses (e.g. STA1_MAC, STA2_MAC) .
• STA2_RMA1 BB to STA2 as the device identification information between STA2 and AP.
• STA1 and STA2 start the TDLS procedure.
• FIG. 15 illustrating a simplified block diagram of an apparatus 1500 that may be embodied as the first wireless device.
• the apparatus 1500 may comprise 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 apparatus 1500 may further comprise a sending unit and a receiving unit 1503 coupled to the one or more processors 1501.
• the processors 1501 may be of any type suitable to the local technical environment, and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
• general purpose computers special purpose computers
• microprocessors microprocessors
• DSPs digital signal processors
• processors based on multicore processor architecture as non-limiting examples.
• the MEM (s) 1502 may be of any type suitable to the local technical environment and may 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, as non-limiting examples.
• the MEM 1502 stores a program (PROG) 1504.
• the PROG 1504 may include instructions that, when executed on the associated processor 1501, enable the apparatus 1500 to operate in accordance with the embodiments of the present disclosure, for example to perform one of the methods 700 as shown in FIG. 7.
• a combination of the at least one processor 1501 and the at least one MEM 1502 may form processing circuitry or means 1505 adapted to implement various embodiments of the present disclosure.
• Various embodiments of the present disclosure may be implemented by a computer program executable by one or more of the processors 1501, software, firmware, hardware or in a combination thereof.
• the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
• some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto.
• firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto.
• While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
• the exemplary embodiments of the disclosures may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.
• exemplary embodiments of the disclosures may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
• program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular 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, non-transitory computer readable medium, such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc.
• the function of the program modules may be combined or distributed as desired in various embodiments.
• the function may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.
• FPGA field programmable gate arrays

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (1)

Publications (1)

Family

ID=91484214

Family Applications (1)

Country Status (3)

Family Cites Families (6)

• 2022
  • 2022-12-13 WO PCT/CN2022/138588 patent/WO2024124392A1/en not_active Ceased
  • 2022-12-13 CN CN202280102543.7A patent/CN120359807A/zh active Pending
  • 2022-12-13 EP EP22968105.1A patent/EP4635253A1/de active Pending

Also Published As

Similar Documents

Legal Events