Identification and discovery of devices

Abstract

The embodiment of the invention relates to a device and method for identification and discovery of equipment, the equipment and a computer readable storage medium. The apparatus transmits the MLD MAC address of the non-AP MLD to the first AP in the second apparatus. In response to a second AP MLD in the second device being created based on an association between the MLD MAC address of the non-AP MLD and the private SSID of the second AP MLD, the device receives the private SSID from the second AP MLD. In turn, the device establishes a connection between the device and the second AP MLD using at least the private SSID.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to apparatuses, methods, devices, and computer-readable storage media for identification and discovery of devices. Background Art

[0002] Multi-link operation (MLO) has been identified as an important feature of the Institute of Electrical and Electronics Engineers (IEEE) 802.11be. The goal of MLO is to operate efficiently in all available frequency bands (such as 2.4 GHz, 5 GHz, and 6 GHz) to achieve load balancing, multi-band aggregation, and simultaneous downlink and uplink transmissions.

[0003] In 802.11be, a multi-link device (MLD) is a logical entity. An MLD may have more than one subordinate station (STA) and has a single media access control (MAC) to a logical link control (LLC) with a single MAC data service. The MLD MAC address may be used to identify the MLD entity. The MAC addresses of access points (APs) subordinate to an AP MLD may be different from each other. If each AP subordinate to an AP MLD has a different MAC address, then when a non-AP MLD is associated with an AP MLD, each non-AP STA subordinate to the non-AP MLD has a different MAC address. In 802.11be, MLO enables a non-AP MLD to discover, authenticate, associate, and establish multiple links with an AP MLD. Summary of the invention

[0004] Example embodiments of the present disclosure provide an improved solution for identification and discovery of devices.

[0005] In a first aspect, a device is provided. The device includes at least one processor and at least one memory storing instructions. When the instructions are executed by the at least one processor, the device causes at least: sending an MLD MAC address of a non-AP MLD to a first AP in a second device; in response to a second AP MLD in the second device being created based on an association between the MLD MAC address of the non-AP MLD and a private SSID of the second AP MLD, receiving a private SSID from the second AP MLD; and establishing a connection between the device and the second AP MLD using at least the private SSID.

[0006] In a second aspect, a device is provided. The device includes at least one processor and at least one memory storing instructions. When the instructions are executed by the at least one processor, the device causes at least: receiving an MLD MAC address of a non-AP MLD from a first device at a first AP in the device, the first device being attached to the non-AP MLD; creating a second AP MLD based on a determination that the MLD MAC address of the non-AP MLD is associated with a private SSID of a second AP MLD; and sending the private SSID to the first device for establishment of a connection between the first device and the second AP MLD.

[0007] In a third aspect, a method is provided. The method includes: sending an MLD MAC address of a non-AP MLD from a device to a first AP in a second device, the device being attached to the non-AP MLD; in response to a second AP MLD in the second device being created based on an association between the MLD MAC address of the non-AP MLD and a private SSID of the second AP MLD, receiving a private SSID from the second AP MLD; and establishing a connection between the device and the second AP MLD using at least the private SSID.

[0008] In a fourth aspect, a method is provided. The method includes: receiving, at a first AP in the device, an MLD MAC address of a non-AP MLD from a first device, the first device being attached to the non-AP MLD; creating a second AP MLD based on a determination that the MLD MAC address of the non-AP MLD is associated with a private SSID of a second AP MLD; and sending the private SSID to the first device for establishment of a connection between the first device and the second AP MLD.

[0009] In a fifth aspect, there is provided an apparatus comprising a first device. The first device has: a component for sending an MLD MAC address of a non-AP MLD to a first AP in a second device, the apparatus being attached to the non-AP MLD; a component for receiving a private SSID from a second AP MLD in the second device in response to an association being created between the MLD MAC address of the non-AP MLD and a private SSID of the second AP MLD based on the second AP MLD; and a component for establishing a connection between the apparatus and the second AP MLD using at least the private SSID.

[0010] In a sixth aspect, there is provided an apparatus comprising a second device. The second device has: a component for receiving an MLD MAC address of a non-AP MLD from a first device at a first access point AP in the second device, the first device being attached to the non-AP MLD; a component for creating a second AP MLD based on a determination that the MLD MAC address of the non-AP MLD is associated with a private SSID of a second AP MLD in the second device; and a component for sending the private SSID to the first device for establishment of a connection between the first device and the second APMLD.

[0011] In a seventh aspect, a computer readable medium is provided, wherein the non-transitory computer readable medium comprises program instructions for causing an apparatus to execute the method according to the third aspect.

[0012] In an eighth aspect, a computer readable medium is provided, wherein the non-transitory computer readable medium comprises program instructions for causing an apparatus to execute the method according to the fourth aspect.

[0013] It should be understood that the invention summary is not intended to necessarily 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 easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Some example implementations will now be described with reference to the accompanying drawings, in which:

[0015] Figure 1 illustrates an example communication environment in which embodiments of the present disclosure may be implemented;

[0016] Figure 2 illustrates another example communication environment in which embodiments of the present disclosure may be implemented;

[0017] Figure 3 A signaling diagram is illustrated that illustrates a process for identification and discovery of devices according to some example implementations of the present disclosure;

[0018] Figure 4 A signaling diagram is illustrated that illustrates a process for identification and discovery of devices according to some example implementations of the present disclosure;

[0019] Figure 5 A flowchart illustrating an example method according to some example implementations of the present disclosure;

[0020] Figure 6 A flowchart illustrating an example method according to some example implementations of the present disclosure;

[0021] Figure 7 illustrates a simplified block diagram of an apparatus suitable for implementing an example implementation of the present disclosure; and

[0022] Figure 8 A block diagram of an example computer-readable medium according to an example implementation of the present disclosure is illustrated.

[0023] Unless otherwise specified, the same or similar reference numbers refer to the same or similar elements throughout the drawings. DETAILED DESCRIPTION

[0024] The principle of the present disclosure will now be described with reference to some example implementations. It should be understood that these implementations are only for the purpose of illustration to describe and help those skilled in the art to understand and implement the present disclosure, and do not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways except the way described below.

[0025] In the following description and claims, unless defined otherwise, 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 belongs.

[0026] In this disclosure, references to "one embodiment," "an embodiment," and "an example embodiment" indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. In addition, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, those skilled in the art believe that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other implementations, whether or not explicitly described.

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

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

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

[0030] (a) a pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0031] (b) a combination of hardware circuitry and software such as (where applicable):

[0032] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0033] (ii) hardware processor(s) (including digital signal processor(s)) with software, software and any portion of memory(s) that work together to cause a device (such as a mobile phone or server) to perform various functions), and (c) hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), which requires software (e.g., firmware) for operation, but may be absent when not required for operation.

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

[0035] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as, but not limited to, a fifth generation (5G) system, long term evolution (LTE), advanced LTE (LTE-A), wideband code division multiple access (WCDMA), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), Wi-Fi, etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) new radio (NR) communication protocol, and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be communication technologies and systems that can be used to embody future types of the present disclosure. It should not be regarded as limiting the scope of the present disclosure to the above-mentioned systems.

[0036] As used herein, the term "network device" refers to a node in a communication network, via which a terminal device accesses the network and receives services from the network. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, a micro), etc. The RAN split architecture includes a gNB-CU (centralized unit, which hosts RRC, SDAP, and PDCP), which controls multiple gNB-DUs (distributed units, which host RLC, MAC, and PHY). A relay node may correspond to the DU portion of an IAB node.

[0037] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, equipment operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) part of an integrated access and backhaul (IAB) node (also known as a relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0038] Figure 1 An example communication environment 100 is illustrated in which embodiments of the present disclosure may be implemented. Figure 1 As shown, the communication environment 100 includes a non-AP MLD 110 and an AP MLD 120. It should be understood that an MLD is a logical entity. An MLD that acts as an AP may be referred to as an AP MLD, and an MLD that acts as a non-AP may be referred to as a non-AP MLD.

[0039] The non-AP MLD 110 has subordinate non-AP STAs 111, 112, and 113. Hereinafter, for simplicity, the non-AP STAs are also referred to as STAs. The AP MLD 120 has subordinate APs 121, 122, and 123. The AP 121 operates on the 2.4 GHz band, the AP 122 operates on the 5 GHz band, and the AP 123 operates on the 6 GHz band.

[0040] It should be understood that Figure 1As shown, the number of non-AP STAs attached to non-AP MLD 110 and the number of APs attached to AP MLD 120 are for illustration purposes only and do not represent any limitation. Communication environment 100 may include any suitable number of STAs attached to non-AP MLD 110 and any suitable number of APs attached to AP MLD 120 suitable for implementing embodiments of the present disclosure.

[0041] The non-AP MLD 110 may perform MLO to discover, authenticate, associate, and establish multiple links with the AP MLD 120 .

[0042] During the discovery phase, the non-AP MLD 110 may send an (ML) probe request to scan for the AP MLD 120 through one of the STAs 111, 112, and 113 attached to the non-AP MLD 110. Herein, the term (ML) probe request should be understood to refer to a multi-link probe request or a single-link probe request. The same definition also applies to the (ML) probe response. For example, the STA 111 may send an (ML) probe request to scan for the AP MLD 120. Typically, the MAC address of the STA 111 may be carried in the probe request instead of the MLD MAC address of the non-AP MLD 110. In addition, when the STA 111 performs active channel scanning, the service set identifier (SSID) of the APMLD 120 may be present in the probe request.

[0043] For AP MLD discovery, STA 111 may issue an ML probe request to discover APs, wherein the ML probe request may also contain a probe request variant multi-link unit and an extremely high throughput (EHT) capability element. The ML probe request allows STA 111 to request one of APs 121, 122, and 123 to include all or part of the capabilities, parameters, and operational element sets of other APs affiliated with AP MLD 120. In response to the probe request of STA 111, AP MLD 120 may issue an (ML) probe response to STA 111. In addition to the SSID of AP MLD 120, there will be additional information in the probe response, including a basic variant multi-link unit, an EHT capability element, or / and an EHT operational element.

[0044] In case the SSID of the AP MLD 120 carried in the (ML) probe response is the same as the SSID stored at the STA 111, the STA 111 may connect to the AP MLD 120 using the SSID of the AP MLD 120 and the password (PWD) pair information stored at the STA 111 after authentication.

[0045] After authentication, each link implements channel access and frame exchange between the non-AP MLD 110 and the AP MLD 120 based on the supported capabilities exchanged during association. When the non-AP MLD 110 intends to perform multi-link (re)establishment with the AP MLD 120, the non-AP MLD 110 and the AP MLD 120 may exchange (re)association request / response frames. If both frames carry basic multi-link units, the association request / response frame exchange is used for multi-link establishment. Otherwise, the (re)association request / response frame exchange is not applicable to multi-link establishment. Reference will be made to Figure 1 An example of multi-link establishment is described. Herein, the term (re)association should be understood to include both associating and restoring an association after disassociation, as appropriate.

[0046] like Figure 1 As shown, the non-AP MLD 110 initiates a multi-link establishment process, and the non-AP STA 111 attached to the non-AP MLD 110 sends an association request frame to the AP 121 attached to the AP MLD 120. That is, the transmitter address (TA) field of the association request frame is set to the MAC address of the non-AP STA 111, and the receiver address (RA) field of the association request frame is set to the MAC address of the AP 121. The association request frame may include complete information of the attached STAs 111, 112, and 113 to request the establishment of three links. That is, link 1 is to be established between the AP 121 and the non-AP STA 111, link 2 is to be established between the AP 122 and the non-AP STA 2, and link 3 is to be established between the AP 123 and the non-AP STA 113.

[0047] In addition, the association request frame may further include a basic variant multi-link unit indicating the MLD MAC address of the non-AP MLD 110. Then, the AP MLD 120 responds to the requested multi-link establishment, and the AP 121 attached to the AP MLD 120 issues an association response frame to indicate the successful multi-link establishment to the non-AP STA 111 attached to the non-AP MLD 110. For example, the TA field of the association response frame may be set to the MAC address of the AP 121, and the RA field of the association response frame may be set to the MAC address of the non-AP STA 111.

[0048] In addition, the association response frame may include complete information of AP 121, AP 122, and AP 123, and a basic variant multi-link unit indicating the MLD MAC address of AP MLD 120. After successful multi-link establishment between non-AP MLD 110 and AP MLD 120, three links are established. That is, link 1 is established between AP 121 and non-AP STA 111, link 2 is established between AP 122 and non-AP STA 2, and link 3 is established between AP 123 and non-AP STA 113.

[0049] In some implementations, the communication device may provide a distributed system (DS). In other words, the DS may run on the wireless device. The DS may create an AP with a public SSID, the access rights of which are restricted. Therefore, all traditional STAs and non-AP MLDs may discover and access the AP. In the following, an AP with a public SSID is also referred to as a public AP. Similarly, an AP MLD with a public SSID is also referred to as a public AP MLD.

[0050] In addition, in order to deliver a high-quality user experience for certain non-AP MLDs and traditional STAs, the DS can also create an AP MLD with a private unique SSID. Hereinafter, an AP MLD with a private SSID is also referred to as a private AP MLD. In this case, the non-AP MLD can access the private AP MLD using the private SSID and PWD pair information assigned by the DS.

[0051] If a multilink connection is established between a non-AP MLD and a private AP MLD, the DS will obtain the MLD MAC address of the non-AP MLD and the MAC address of the non-AP STA attached to the non-AP MLD based on the (re)association frame exchange. For example, the DS can use the reference Figure 1 The (re)association frame exchange process is used to obtain the MLD MAC address of the non-AP MLD and the MAC address of the non-AP STA attached to the non-AP MLD.

[0052] When the non-AP MLD is disconnected from the private AP MLD (for example, when the non-AP MLD is not at home) and when the private AP MLD needs to be accessed again later (for example, when the non-AP MLD returns home), the non-AP MLD will issue an (ML) probe request frame to scan the channel through a STA attached to the non-AP MLD. Typically, the STA attached to the non-AP MLD should have been associated with the private AP MLD, and the MAC address of the STA is stored at the DS. The private AP MLD will identify the non-AP MLD by the MAC address of the STA, and thereby allow the non-AP MLD to automatically connect to the private AP MLD. To this end, the private AP MLD will send an (ML) probe response to the STA, as well as the private SSID of the private AP MLD. After receiving the (ML) probe response, the STA can access the private AP MLD using the SSID and PWD pair information provided by the DS. In this case, the private AP MLD should be able to identify the non-AP MLD by the MAC address of the STA during the discovery phase, which will be beneficial to home automation, including, for example, arrival detection. A key feature of a home automation system is one that allows it to identify when a resident has arrived and “welcome” them home by turning on lights, music, etc. that are appropriate for the individual.

[0053] However, considering the buffer size of the non-AP MLD list stored at the DS, depending on the implementation of the DS, the DS may store only the MLD MAC address of the non-AP MLD, rather than the MAC address of the STA attached to the non-AP MLD. In addition, if the STA attached to the non-AP MLD has never been associated with the private AP MLD, the MAC address of the STA will not be stored at the DS. If so, the DS will not be able to identify the STA by the MAC address of the STA, and therefore will not issue a probe response to the STA in response to the (ML) probe request from the STA. Therefore, the non-AP MLD will not be able to discover the private AP MLD, which will result in resource waste and delay because an additional process is required to establish a link with the private AP MLD.

[0054] In addition, after the non-AP MLD is disconnected from the private AP MLD, the DS usually destroys the private AP MLD to reclaim resources. In this case, the private AP MLD will not be able to monitor the (ML) detection request from the non-AP MLD, and therefore the non-AP MLD cannot discover the private AP MLD.

[0055] Therefore, the DS may fail to identify the non-AP MLD in the discovery phase and thus does not create a private AP MLD for it, possibly due to, for example, at least one of: unavailability of the MAC address of the STA attached to the non-AP MLD, resource recovery, or release of the private AP MLD.

[0056] Example embodiments of the present disclosure provide a solution for identification and discovery of devices to solve the above-mentioned problems and one or more other potential problems. According to the solution, a device sends an MLD MAC address of a non-AP MLD to a first AP. If the first AP determines that the MLD MAC address of the non-AP MLD is associated with a private SSID of a second AP MLD, the first AP creates a second AP MLD for the non-AP MLD. The second AP MLD then sends a private SSID to the device for connection between the first device and the second AP MLD. In this way, the non-AP MLD can be identified during the discovery phase, which facilitates automatic connection to an AP network or an AP MLD network. In addition, this solution can facilitate resource recovery and release after the non-AP MLD is disconnected from the AP MLD. In the following, reference will be made to Figures 2 to 8 The principles of the present disclosure are described.

[0057] Figure 2 Another example communication environment 200 is illustrated in which embodiments of the present disclosure may be implemented. Figure 2 As shown, the communication environment 200 includes a first device 210 and a second device 220 .

[0058] The first device 210 may be implemented as a communication device. In some implementations, the first device 210 may be implemented as a non-AP STA attached to the non-AP MLD 212. For example, the non-AP MLD 212 may be implemented as Figure 1 The non-AP MLD 110 shown, and the first device 210 can be implemented as Figure 1 One non-AP STA among the non-AP STAs 111, 112, and 113 is shown.

[0059] The second device 220 may be implemented as a communication device. The second device 220 includes a first AP 221 and a second AP MLD 222. In some implementations, the first AP 221 may be implemented as a single-link AP device. Alternatively, the first AP 221 may be implemented as an AP attached to the AP MLD. For example, the first AP 221 may be implemented as Figure 1 AP 121 is shown as being subordinate to AP MLD 120. In such an implementation, similar to AP MLD 120, first AP 221 may have multiple APs subordinate to first AP 221.

[0060] In some embodiments, the second AP MLD 222 may have a plurality of APs subordinate to the second AP MLD 222. For example, the second AP MLD 222 may be APs 222-1 and 222-2 subordinate to the second AP MLD 222. In some embodiments, each of the APs 222-1 and 222-2 may be in the same Figure 1 Any of APs 121, 122, and 124 in the AP 121, 122, and 124 operate in a similar manner.

[0061] For illustration purposes only, and without suggesting any limitation on the scope of the present disclosure, some embodiments will be described in the context of the first device 210 being implemented as a non-AP STA and the first AP 221 in the second device 220 being implemented as an AP MLD.

[0062] It should be understood that in other embodiments, the first device 110 may be implemented as other communication devices other than a non-AP STA, and the first AP 221 in the second device 120 may be implemented as a single-link AP device.

[0063] The communication in the communication environment 200 may conform to any suitable standard for a wireless local area network or a cellular network, including but not limited to Wi-Fi, LTE, LTE evolution, advanced LTE (LTE-A), wideband code division multiple access (WCDMA), code division multiple access (CDMA), and global system for mobile communications (GSM), etc. In addition, the communication may be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include but are not limited to Wi-Fi 7, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), advanced 5G, and sixth generation (6G) communication protocols.

[0064] The first device 210 sends the MLD MAC address of the non-AP MLD 212 to the first AP 221. If the first AP 221 determines that the MLD MAC address of the non-AP MLD 212 is associated with the private SSID of the second AP MLD 222, the first AP 221 creates a second AP MLD 222 for the non-AP MLD 212. Then, the second AP MLD 222 sends the private SSID to the first device 210 for connection between the first device 210 and the second AP MLD 222. In some embodiments, the second AP MLD 222 may instruct its subordinate AP to send the private SSID to the first device 210. For example, the second AP MLD 222 may instruct the subordinate AP 222-1 to send the private SSID to the first device 210. In this way, the non-AP MLD 212 may be identified during the discovery phase, which facilitates automatic connection to the AP (MLD) network. In addition, the solution may facilitate resource recovery and release after the non-AP MLD is disconnected from the AP MLD.

[0065] Figure 3 FIG. 3 illustrates a signaling diagram of a process 300 for identification and discovery of a device according to some example embodiments of the present disclosure. The process 300 may involve: Figure 2 The first device 210 and the second device 220 are shown. Figure 2 The process 300 is described in the communication environment 200 of FIG. 1 , but the process can also be applied to other communication scenarios.

[0066] In the process 300, it is assumed that the DS in the second device 220 can create a first AP MLD 221 with a public SSID. In this case, the legacy STA and the non-AP MLD can discover and access the first AP MLD 221 with a specific access authority managed by the DS. In order to provide a high-quality experience for the non-AP MLD 212, the DS will create a second AP MLD 222 with a private unique SSID for the non-AP MLD 212. After the non-AP MLD 212 disconnects from the second AP MLD 222 and needs to connect to the second AP MLD 222 again using the private SSID and PWD pair information stored at the non-AP MLD 212, the non-AP MLD 212 can initiate the process 300 so that the DS can discover the non-AP MLD 212 and thereby create the second AP MLD 222 for the non-AP MLD 212.

[0067] like Figure 3As shown, the first device 210 sends 310 the MLD MAC address of the non-AP MLD 212 to which the first device 210 is attached to the first AP 221 in the second device 220. Therefore, the first AP 221 receives the MLD MAC address of the non-AP MLD 212.

[0068] In some embodiments, the non-AP MLD 212 may instruct the first device 210 attached to the non-AP MLD 212 to perform channel scanning by sending an ML probe request in order to connect to the second AP MLD 222. In some embodiments, the first device 210 may send an ML probe request in which the MLD MAC address of the non-AP MLD 212 is present in the probe request variant multi-link unit.

[0069] In such an implementation, the first AP 221 may assist the DS in monitoring the ML probe request from the first device 210 attached to the non-AP MLD 212 to obtain the MLD MAC address of the non-AP MLD 212 .

[0070] After acquiring the MLD MAC address of the non-AP MLD 212 , the DS determines 320 whether the MLD MAC address of the non-AP MLD 212 is associated with the private SSID of the second AP MLD 222 .

[0071] In some embodiments, the DS may maintain a list including mappings between the MLD MAC addresses of non-AP MLDs and the private SSIDs of associated AP MLDs. The DS may search the list for the MLD MAC address of the non-AP MLD 212 or the private SSID of the second AP MLD 222. If the MLD MAC address of the non-AP MLD 212 or the private SSID of the second AP MLD 222 is found in the list, the DS may determine that the MLD MAC address of the non-AP MLD 212 is associated with the private SSID of the second AP MLD 222.

[0072] In turn, the DS creates 330 a second AP MLD 222 having a private SSID other than the AP MLD 212 .

[0073] In some embodiments, the DS may create the second AP MLD 222 based on the locally stored context information of the second AP MLD 222. In some embodiments, the context information of the second AP MLD 222 may include security information of each link profile and associated non-AP MLDs.

[0074] After creating the second AP MLD 222 , the second AP MLD 222 sends 340 the private SSID of the second AP MLD 222 to the first device 210 for establishment of a connection between the first device 210 and the second AP MLD 222 .

[0075] In an embodiment where the first device 210 sends an ML probe request including the MLD MAC address of the non-AP MLD 212 , the second AP MLD 222 may send an ML probe response including the private SSID of the second AP MLD 222 to the first device 210 .

[0076] After receiving the private SSID of the second AP MLD 222 from the second AP MLD 222, the first device 210 establishes 350 a connection between the first device 210 and the second AP MLD 222 using at least the private SSID.

[0077] In some embodiments, the DS may pre-assign a PWD associated with the private SSID of the second AP MLD 222 to the first device 210. In this case, the first device 210 may store the PWD locally. Therefore, the first device 210 may establish a connection between the first device 210 and the second AP MLD 222 using the private SSID and PWD pair information stored locally.

[0078] Through process 300, non-AP MLDs are identified through frames during the discovery phase, which facilitates automatic connection with private AP MLDs even if the STA attached to the non-AP MLD has never been associated with the private AP MLD or the MAC address of the STA is not cached or stored at the private AP MLD.

[0079] In addition, process 300 can facilitate resource recovery or release after the non-AP MLD disconnects from the private AP MLD. For example, the private AP MLD can recover or release resources by refreshing STA information or releasing the private AP MLD.

[0080] In some embodiments, the first device 210 may receive a request for the MLD MAC address of the non-AP MLD 212 from the first AP 221. The first device 210 may then send a response to the request to the first AP 221. The response includes the MLD MAC address of the non-AP MLD 212. This will refer to Figure 4 to describe.

[0081] Figure 4 FIG. 4 is a signaling diagram of a process 400 for identification and discovery of a device according to other example embodiments of the present disclosure. The process 400 may involve the following steps: Figure 2The first device 210 and the second device 220 are shown. Process 400 can be considered as an example implementation of process 300. Figure 2 The process 400 is described in the communication environment 200 of FIG. 1 , but the process can also be applied to other communication scenarios. It should be understood that the reference Figure 3 The same assumptions described apply to process 400 as well.

[0082] like Figure 4 As shown, in order to connect to the second AP MLD 222, the non-AP MLD 212 may instruct the first device 210 attached to the non-AP MLD 212 to perform channel scanning by sending 410 a probe request.

[0083] In some embodiments, the first device 210 may send a probe request with a broadcast destination address. In this case, the private SSID of the second AP MLD 222 stored at the first device 210 will not be carried in the probe request.

[0084] In other embodiments, the first device 210 may send a probe request frame, wherein the private SSID of the second AP MLD 222 stored at the first device 210 will be carried in the probe request.

[0085] The first AP 221 monitors 420 a probe request from the first device 210 attached to the non-AP MLD 212 .

[0086] In some embodiments, the DS may instruct the first AP MLD 221 to send 430 a request for the MLD MAC address of the non-AP MLD 212 to the first device 210 .

[0087] In some embodiments, the probe request may include capability information of the first device 210, the SSID, and the MAC address of the first device 210. In such an embodiment, the first AP MLD 221 may send a request for the MLD MAC address of the non-AP MLD 212 in response to at least one of the following:

[0088] Based on the capability information of the first device 210, determining that the first device 210 is attached to the non-AP MLD 212,

[0089] The SSID in the probe request is associated with the second AP MLD 222, or

[0090] The MAC address of the first device 210 is not stored at the second device 220 .

[0091] In some embodiments, the first AP MLD 221 may optionally send a probe response to the first device 210. For example, if the RA in the probe request is a broadcast address, the first AP MLD 221 may send a probe response to the first device 210.

[0092] In some embodiments, the first AP MLD 221 may transmit a first frame to the first device 210, the first frame including a request for the MLD MAC address of the non-AP MLD 212. For example, the first frame may be a newly defined action frame.

[0093] After receiving the request for the MLD MAC address of the non-AP MLD 212 from the first AP 221, the first device 210 may send 440 a response to the request to the first AP 221. The response includes the MLD MAC address of the non-AP MLD 212.

[0094] In some embodiments, the first device 210 may transmit a second frame including the MLD MAC address of the non-AP MLD to the first AP 221. For example, the second frame may be a newly defined action frame.

[0095] Actions 320, 330, 340, and 350 in process 400 are the same as those in process 300. Therefore, details of these actions are omitted for the sake of brevity.

[0096] Figure 5 FIG. 5 is a flowchart of an example method 500 implemented at a first device according to some example embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 2 The method 500 is described from the perspective of the first device 210 .

[0097] At block 510, the first device 210 sends the MLD MAC address of the non-AP MLD to the first AP in the second device.

[0098] At block 520 , in response to a second AP MLD in the second device being created based on an association between the MLD MAC address of the non-AP MLD and the private SSID of the second AP MLD, the first device 210 receives the private SSID from the second AP MLD.

[0099] At block 530, the first device 210 establishes a connection between the device and the second AP MLD using at least the private SSID.

[0100] In some embodiments, sending the MLD MAC address of the non-AP MLD includes: in response to receiving a request for the MLD MAC address of the non-AP MLD from the first AP, sending a response to the request to the first AP, the response including the MLD MAC address of the non-AP MLD.

[0101] In some embodiments, receiving a request for an MLD MAC address of a non-AP MLD includes receiving a first frame including the request.

[0102] In some embodiments, sending the MLD MAC address of the non-AP MLD includes sending a second frame including the MLD MAC address of the non-AP MLD.

[0103] In some embodiments, sending the MLD MAC address of the non-AP MLD includes: sending a multi-link probe request to the first AP, the multi-link probe request including a probe request variant multi-link unit, the unit including: the MLD MAC address of the non-AP MLD.

[0104] Figure 6 FIG. 6 is a flowchart of an example method 600 implemented at a second device according to some example embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 2 The method 600 is described from the perspective of the second device 220 .

[0105] At block 610, the second device 220 receives an MLD MAC address of a non-AP MLD from a first device at a first AP in the second device 220. The first device is affiliated with the non-AP MLD.

[0106] At block 620, the second device 220 determines whether the MLD MAC address of the non-AP MLD is associated with the private SSID of the second AP MLD.

[0107] If the MLD MAC address of the non-AP MLD is associated with the private SSID of the second AP MLD, the second device 220 creates the second AP MLD at block 630 .

[0108] At block 640, the second device 220 sends the private SSID to the first device for establishment of a connection between the first device and the second APMLD.

[0109] In some embodiments, method 600 further comprises sending a request for the MLD MAC address of the non-AP MLD to the first device. In such embodiments, receiving the MLD MAC address of the non-AP MLD comprises receiving a response to the request from the first device, the response comprising the MLD MAC address of the non-AP MLD.

[0110] In some embodiments, sending a request for the MLD MAC address of the non-AP MLD includes sending a first frame including the request.

[0111] In some embodiments, the method 600 further includes: receiving a probe request from the first device, the probe request including capability information of the first device, the SSID, and the MAC address of the first device. In such embodiments, sending the request for the MLD MAC address of the non-AP MLD includes: sending the request in response to at least one of: determining that the first device is affiliated with the non-AP MLD based on the capability information of the first device, the SSID in the probe request is associated with the second AP MLD, or the MAC address of the first device is not stored at the second device.

[0112] In some embodiments, receiving a response to the request includes receiving a second frame including the MLD MAC address of the non-AP MLD.

[0113] In some embodiments, receiving the MLD MAC address of the non-AP MLD includes: receiving a multi-link probe request from the first device, the multi-link probe request including a probe request variant multi-link unit, the unit including: the MLD MAC address of the non-AP MLD.

[0114] In some embodiments, creating the second AP MLD includes creating the second AP MLD based on locally stored context information of the second AP MLD.

[0115] Already referenced Figures 1 to 4 The described example embodiments of the present disclosure may also be applied to methods 500 and 600. Therefore, details of the example embodiments are omitted.

[0116] In some example embodiments, a device (e.g., a first device) capable of performing any of the methods in method 500 may include a component for performing the corresponding steps of method 500. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module or a combination thereof.

[0117] In some example embodiments, an apparatus includes a first device having: means for sending an MLD MAC address of a non-AP MLD to a first AP in a second device, the apparatus being attached to the non-AP MLD; means for receiving a private SSID from a second AP MLD in the second device in response to an association being created between the MLD MAC address of the non-AP MLD and a private SSID of the second AP MLD based on the second AP MLD; and means for establishing a connection between the apparatus and the second AP MLD using at least the private SSID.

[0118] In some embodiments, means for sending the MLD MAC address of the non-AP MLD includes means for, in response to receiving a request for the MLD MAC address of the non-AP MLD from the first AP, sending a response to the request to the first AP, the response including the MLD MAC address of the non-AP MLD.

[0119] In some embodiments, means for receiving a request for an MLD MAC address of a non-AP MLD includes means for receiving a first frame including the request.

[0120] In some embodiments, means for transmitting the MLD MAC address of the non-AP MLD includes means for transmitting a second frame including the MLD MAC address of the non-AP MLD.

[0121] In some embodiments, the means for sending the MLD MAC address of the non-AP MLD includes: means for sending a multi-link probe request to the first AP, the multi-link probe request including a probe request variant multi-link unit including: the MLD MAC address of the non-AP MLD.

[0122] In some example embodiments, a device (e.g., a second device) capable of performing any of the methods in method 600 may include a component for performing the corresponding steps of method 600. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module or a combination thereof.

[0123] In some example embodiments, an apparatus includes a second device having: means for receiving, at a first AP in the second device, an MLD MAC address of a non-AP MLD from the first device, the first device being attached to the non-AP MLD; means for creating a second AP MLD based on a determination that the MLD MAC address of the non-AP MLD is associated with a private SSID of a second AP MLD in the second device; and means for sending the private SSID to the first device for establishment of a connection between the first device and the second AP MLD.

[0124] In some embodiments, the apparatus further comprises: means for sending a request for the MLD MAC address of the non-AP MLD to the first apparatus. In such an embodiment, means for receiving the MLD MAC address of the non-AP MLD comprises: means for receiving a response to the request from the first apparatus, the response comprising the MLD MAC address of the non-AP MLD.

[0125] In some embodiments, means for sending a request for an MLD MAC address of a non-AP MLD includes means for sending a first frame including the request.

[0126] In some embodiments, the apparatus further comprises: means for receiving a probe request from the first apparatus, the probe request comprising capability information of the first apparatus, the SSID, and the MAC address of the first apparatus. In such an embodiment, the means for sending a request for the MLD MAC address of the non-AP MLD comprises: means for sending the request in response to at least one of: determining based on the capability information of the first apparatus that the first apparatus is affiliated with the non-AP MLD, the SSID in the probe request is associated with the second AP MLD, or the MAC address of the first apparatus is not stored at the second apparatus.

[0127] In some embodiments, means for receiving a response to the request includes means for receiving a second frame including the MLD MAC address of the non-AP MLD.

[0128] In some embodiments, the means for receiving the MLD MAC address of the non-AP MLD includes: means for receiving a multi-link probe request from the first device, the multi-link probe request including a probe request variant multi-link unit including: the MLD MAC address of the non-AP MLD.

[0129] In some embodiments, the means for creating the second AP MLD includes means for creating the second AP MLD based on locally stored context information of the second AP MLD.

[0130] Figure 7 700 is a simplified block diagram of a device 700 suitable for implementing an embodiment of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1 The first device 110 or the second device 120 shown, or Figure 2 The first device 210 or the second device 220 is shown. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0131] The communication module 740 is configured for bidirectional communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface may represent any interface required for communication with other network elements.

[0132] Processor 710 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of 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. Device 700 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0133] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power outages.

[0134] Computer program 730 includes computer executable instructions executed by associated processor 710. Program 730 may be stored in memory 720, such as ROM 724. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 722.

[0135] The embodiments of the present disclosure may be implemented by a program 730, so that the device 700 may execute the reference Figures 1 to 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0136] In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium, which may be included in the device 700 (such as in the memory 720) or in other storage devices accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 in the form of a CD or DVD is shown. The computer readable medium has a program 730 stored thereon.

[0137] Generally, various embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0138] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the above referenced method for the device. Figure 5 and Figure 6 The methods 500 and 600 described herein. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules can be combined or split between program modules as needed. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0139] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code is implemented when executed by the processor or controller in the flow chart and / or the block diagram. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0140] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0141] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer readable storage media will include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0142] In addition, although the operations are described in a specific order, this should not be understood as requiring such operations to be performed in the specific order shown or in order or performing all the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0143] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Instead, the specific features or acts described above are disclosed as example forms of implementing the claims.

[0144] List of Abbreviations and Acronyms AP: Access Point Non-AP MLD: Non-Access Point Multi-Link Device DS: Distributed System

[0145] LCC: Logical Link Control

[0146] MAC: Media Access Control

[0147] ML: Multi-Link

[0148] MLD: Multi-Link Device

[0149] MLO: Multi-Link Operation

[0150] PWD: Password

[0151] QoS: Quality of Service

[0152] RCPI: Receive Channel Power Indicator

[0153] RSSI: Reference signal strength

[0154] SAP: Service Access Point

[0155] SINR: Signal to Interference and Noise Ratio

[0156] SSID: Service Set Identifier

[0157] STA: Station

Claims

1. A device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Attached to non-access point multi-link devices (non-AP MLD); Sending the multi-link device media access control MLD MAC address of the non-AP MLD to the first access point AP in the second device; In response to a second access point multi-link device AP MLD in the second apparatus being created based on an association between the MLDMAC address of the non-AP MLD and a private service set identifier SSID of the second APMLD, receiving the private SSID from the second AP MLD; as well as A connection is established between the device and the second AP MLD using at least the private SSID.

2. The apparatus according to claim 1, configured to: In response to receiving a request for the MLD MAC address of the non-AP MLD from the first AP, sending a response to the request to the first AP, the response comprising: The MLD MAC address of the non-AP MLD.

3. The apparatus of claim 2, configured to receive the request for the MLD MAC address of the non-AP MLD by: A first frame including the request is received.

4. The apparatus according to claim 2, configured to send: A second frame including the MLD MAC address of the non-AP MLD.

5. The apparatus according to claim 1, configured to send a multi-link probe request to the first AP, the multi-link probe request comprising a probe request variant multi-link unit, the unit comprising: The MLD MAC address of the non-AP MLD.

6. A device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: At a first access point AP in the device, receiving a multi-link device media access control MLDMAC address of a non-access point multi-link device (non-AP MLD) from a first device, the first device being attached to the non-AP MLD; creating the second AP MLD based on a determination that the MLD MAC address of the non-AP MLD is associated with a private service set identifier SSID of a second AP MLD in the device; as well as The private SSID is sent to the first device for establishing a connection between the first device and the second AP MLD.

7. The apparatus of claim 6, configured to send a request for the MLD MAC address of the non-AP MLD to the first apparatus; and receiving a response to the request from the first device, the response comprising: The MLD MAC address of the non-AP MLD.

8. The apparatus of claim 7, configured to send the request for the MLD MAC address of the non-AP MLD by: A first frame including the request is sent.

9. The apparatus according to claim 7, configured to: A probe request is received from the first device, the probe request comprising: capability information of the first device, the SSID, and the MAC address of the first device; as well as sending the request for the MLD MAC address of the non-AP MLD in response to at least one of: determining, based on the capability information of the first device, that the first device is affiliated with the non-AP MLD, The SSID in the probe request is associated with the second AP MLD, or The MAC address of the first device is not stored at the second device.

10. The apparatus according to claim 7, configured to receive the response to the request by: A second frame including the MLD MAC address of the non-AP MLD is received.

11. The apparatus of claim 6, configured to receive the MLD MAC address of the non-AP MLD by: A multi-link probe request is received from the first device, the multi-link probe request comprising a probe request variant multi-link unit, the unit comprising: The MLD MAC address of the non-AP MLD.

12. The apparatus of claim 6, configured to create the second AP MLD based on locally stored context information of the second AP MLD.

13. A method comprising: Sending, from the device to a first access point AP in a second device, a multi-link device media access control MLD MAC address of a non-access point multi-link device (non-AP MLD), to which the device is attached; In response to a second access point multi-link device AP MLD in the second apparatus being created based on an association between the MLDMAC address of the non-AP MLD and a private service set identifier SSID of the second AP MLD, receiving the private SSID from the second AP MLD; as well as A connection is established between the device and the second AP MLD using at least the private SSID.

14. The method of claim 13, wherein sending the MLD MAC address of the non-AP MLD comprises: In response to receiving a request for the MLD MAC address of the non-AP MLD from the first AP, sending a response to the request to the first AP, the response including: the MLD MAC address of the non-AP MLD.

15. The method of claim 14, wherein receiving the request for the MLD MAC address of the non-AP MLD comprises: A first frame including the request is received.

16. The method of claim 14, wherein sending the MLD MAC address of the non-AP MLD comprises: A second frame including the MLD MAC address of the non-AP MLD is sent.

17. The method of claim 13, wherein sending the MLD MAC address of the non-AP MLD comprises: A multi-link detection request is sent to the first AP, wherein the multi-link detection request includes a detection request variant multi-link unit, wherein the unit includes: the MLD MAC address of the non-AP MLD.

18. A method comprising: At a first access point AP in the device, receiving a multi-link device media access control MLD MAC address of a non-access point multi-link device (non-AP MLD) from a first device, the first device being attached to the non-AP MLD; creating the second AP MLD based on a determination that the MLD MAC address of the non-AP MLD is associated with a private service set identifier SSID of a second access point multi-link device AP MLD; as well as The private SSID is sent to the first device for establishing a connection between the first device and the second AP MLD.

19. The method according to claim 18, further comprising: sending a request for the MLD MAC address of the non-AP MLD to the first device; as well as The receiving the MLD MAC address of the non-AP MLD includes: receiving a response to the request from the first device, the response comprising: The MLD MAC address of the non-AP MLD.

20. The method of claim 19, wherein sending the request for the MLD MAC address of the non-AP MLD comprises: A first frame including the request is sent.

21. The method of claim 19, further comprising: receiving a probe request from the first device, the probe request including: capability information of the first device, an SSID, and a MAC address of the first device; and The sending of the request for the MLD MAC address of the non-AP MLD includes: The request is sent in response to at least one of: determining, based on the capability information of the first device, that the first device is affiliated with the non-AP MLD, The SSID in the probe request is associated with the second AP MLD, or The MAC address of the first device is not stored at the second device.

22. The method of claim 19, wherein receiving the response to the request comprises: A second frame including the MLD MAC address of the non-AP MLD is received.

23. The method of claim 18, wherein receiving the MLD MAC address of the non-AP MLD comprises: A multi-link probe request is received from the first device, the multi-link probe request comprising a probe request variant multi-link unit, the unit comprising: the MLD MAC address of the non-AP MLD.

24. The method of claim 18, wherein creating the second AP MLD comprises: The second AP MLD is created based on the locally stored context information of the second AP MLD.

25. An apparatus comprising: A first device having: means for attaching the apparatus to a non-access point multi-link device (non-AP MLD); A component for sending the multi-link device media access control MLDMAC address of the non-AP MLD to the first access point AP in the second device, means for receiving the private SSID from the second AP MLD in response to a second access point multi-link device APMLD in the second device being created based on an association between the MLD MAC address of the non-AP MLD and a private service set identifier SSID of the second AP MLD; as well as Means for establishing a connection between the device and the second APMLD using at least the private SSID.

26. An apparatus comprising: A second device having: means for receiving, at a first access point AP in the second device, a multi-link device media access control MLD MAC address of a non-access point multi-link device (non-APMLD) from a first device, the first device being attached to the non-APMLD; means for creating a second access point multi-link device AP MLD in the second device based on a determination that the MLD MAC address of the non-AP MLD is associated with a private service set identifier SSID of the second AP MLD; as well as means for sending the private SSID to the first device for establishment of a connection between the first device and the second AP MLD.

27. A computer readable medium comprising program instructions for causing an apparatus to perform the method according to any one of claims 13 to 17.

28. A computer readable medium comprising program instructions for causing an apparatus to perform the method according to any one of claims 18 to 24.

Images