Multi-link setup in wireless communication system

Abstract

In a wireless local area network (WLAN) system, a STA MLD can include a first STA and a second STA, where the first STA operates on a first link and the second STA operates on a second link. The STA MLD can transmit an association request frame to an access point (AP) MLD. The association request frame can include capability information of a requesting STA among the STAs included in the STA MLD requesting association with the AP MLD and information about a requesting link on which the requesting STA transmits the association request. The STA MLD can receive an association response frame from the AP MLD. The association response frame can include capability information of an AP operating in a link on which the AP MLD accepts association among the requesting link.

Description

Technical Field

[0001] This manual relates to the method of setting up multiple links in a wireless local area network system. Background Technology

[0002] Wireless local area networks (WLANs) have been improved in various ways. For example, the IEEE 802.11ax standard proposed an improved communication environment using orthogonal frequency division multiple access (OFDMA) and downlink multiple user multiple input multiple output (DLMU MIMO) technologies.

[0003] This specification outlines technical features that can be used in new communication standards. For example, a new communication standard could be the currently discussed Extremely High Throughput (EHT) standard. The EHT standard could utilize newly proposed increased bandwidth, enhanced PHY layer Protocol Data Unit (PPDU) structures, enhanced sequences, Hybrid Automatic Repeat Request (HARQ) schemes, etc. The EHT standard could be referred to as the IEEE 802.11be standard. Summary of the Invention

[0004] Technical solution

[0005] In a wireless local area network (WLAN) system according to various embodiments, a station (STA) multilink device (MLD) may include a first STA and a second STA. The first STA may operate in a first link. The second STA may operate in a second link. The STA MLD may send an association request frame to an access point (AP) MLD. The association request frame may include capability information of the requesting STA among the STAs included in the STA MLD, requesting association with the AP MLD, and information related to the requested link requested by the requesting STA. The STA MLD may receive an association response frame from the AP MLD. The association response frame may include capability information of the AP operating in the associated link, which the AP MLD in the requested link accepts.

[0006] Beneficial effects

[0007] According to the examples in this specification, the AP MLD may send only complete information about the AP corresponding to the link that accepts the setup among the requested setup links. Due to the large size of the complete information, sending complete information about all STAs and APs included in the MLD incurs excessive overhead. Therefore, according to the implementation of this specification, overhead can be reduced by sending only information about the requested link and the link that accepts the request in the setup. Attached Figure Description

[0008] Figure 1 Examples of transmitting and / or receiving devices are shown in this specification.

[0009] Figure 2This is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0010] Figure 3 This shows the general link setup process.

[0011] Figure 4 The layout of resource units (RUs) used in the 80MHz frequency band is shown.

[0012] Figure 5 An example of a PPDU used in this specification is shown.

[0013] Figure 6 Examples of modified transmitting and / or receiving devices are shown in this specification.

[0014] Figure 7 An example of a Station-to-Station (STA) Multilink Device (MLD) is shown.

[0015] Figure 8 This illustrates the implementation methods for setting up the relationships between various links.

[0016] Figure 9 This illustrates an implementation of the link set relationship.

[0017] Figure 10 This shows an example of the overall process for multi-link discovery and setup.

[0018] Figure 11 An implementation of a method for providing information about STAs included in an MLD is shown.

[0019] Figure 12 An implementation of method A is shown.

[0020] Figure 13 An implementation of method A-1 is shown.

[0021] Figure 14 An implementation of method A-2 is shown.

[0022] Figure 15 An implementation of method A-3 is shown.

[0023] Figure 16 An implementation of method A-4 is shown.

[0024] Figure 17 An implementation of method B is shown.

[0025] Figure 18 An implementation of method 1-1 is shown.

[0026] Figure 19 Implementation methods 1-2 are shown.

[0027] Figure 20An implementation of method 2-1 is shown.

[0028] Figure 21 An implementation of method 2-1 is shown.

[0029] Figure 22 An implementation of method 2-2 is shown.

[0030] Figure 23 An implementation of method 2-2 is shown.

[0031] Figure 24 An implementation method for operating the STA MLD is shown.

[0032] Figure 25 An implementation of a method for operating an access point (AP) MLD is shown. Detailed Implementation

[0033] In this specification, "A or B" may mean "A only", "B only", or "both A and B". In other words, in this specification, "A or B" may be interpreted as "A and / or B". For example, in this specification, "A, B or C" may mean "A only", "B only", "C only", or "any combination of A, B, and C".

[0034] The forward slash ( / ) or comma used in this specification may indicate "and / or". For example, "A / B" may mean "A and / or B". Therefore, "A / B" may mean "A only", "B only", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0035] In this specification, "at least one of A and B" may mean "A only", "B only" or "both A and B". Additionally, in this specification, the expression "at least one of A or B" or "at least one of A and / or B" may be interpreted as "at least one of A and B".

[0036] Additionally, in this specification, "at least one of A, B, and C" may mean "A only", "B only", "C only" or "any combination of A, B, and C". Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C".

[0037] Additionally, the parentheses used in this specification can indicate "for example". Specifically, when indicated as "control information (EHT-signal)", it can mean that "EHT-signal" is proposed as an example of "control information". In other words, "control information" in this specification is not limited to "EHT-signal", and "EHT-signal" can be proposed as an example of "control information". Furthermore, when indicated as "control information (i.e., EHT signal)", it can also mean that "EHT signal" is proposed as an example of "control information".

[0038] The technical features described individually in one of the accompanying drawings of this specification may be implemented individually or simultaneously.

[0039] The examples in this specification can be applied to various wireless communication systems. For example, the examples in this specification can be applied to wireless local area network (WLAN) systems. For example, this specification can be applied to the IEEE 802.11a / g / n / ac standard or the IEEE 802.11ax standard. Additionally, this specification can be applied to the newly proposed EHT standard or the IEEE 802.11be standard. Furthermore, the examples in this specification can be applied to new WLAN standards enhanced from the EHT standard or the IEEE 802.11be standard. Additionally, the examples in this specification can be applied to mobile communication systems. For example, it can be applied to mobile communication systems based on Long Term Evolution (LTE) standards that rely on the 3rd Generation Partnership Project (3GPP) standards, and mobile communication systems based on LTE evolution. Additionally, the examples in this specification can be applied to communication systems based on the 5G NR standard of the 3GPP standard.

[0040] In the following text, for the purpose of describing the technical features of this specification, technical features that can be applied to this specification will be described.

[0041] Figure 1 Examples of transmitting and / or receiving devices are shown in this specification.

[0042] exist Figure 1 In the examples, the various technical features described below can be performed. Figure 1 This involves at least one station (STA). For example, STA 110 and 120 in this specification may also be referred to by various terms such as mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or simply user. STA 110 and 120 in this specification may also be referred to by various terms such as network, base station, Node B, access point (AP), repeater, router, relay, etc. STA 110 and 120 in this specification may also be referred to by various names such as receiving device, transmitting device, receiving STA, transmitting STA, receiving apparatus, transmitting apparatus, etc.

[0043] For example, STA 110 and 120 can be used as APs or non-APs. That is, STA 110 and 120 in this specification can be used as APs and / or non-APs. In this specification, AP can be indicated as AP STA.

[0044] In addition to the IEEE 802.11 standard, STAs 110 and 120 in this specification can support various communication standards together. For example, they can support communication standards based on 3GPP standards (e.g., LTE, LTE-A, 5G NR standards). Furthermore, the STAs in this specification can be implemented in various devices such as mobile phones, vehicles, and personal computers. Additionally, the STAs in this specification can support various communication services such as voice calls, video calls, data communications, and autonomous driving.

[0045] The STA 110 and 120 of this specification may include a media access control (MAC) compliant with the IEEE 802.11 standard and a physical layer interface for radio media.

[0046] The following will refer to Figure 1 Subgraph (a) describes STA 110 and 120.

[0047] The first STA 110 may include a processor 111, a memory 112, and a transceiver 113. The processor, memory, and transceiver shown may be implemented as separate chips, or at least two blocks / functions may be implemented as a single chip.

[0048] The transceiver 113 of the first STA performs signal transmission / reception operations. Specifically, it can transmit / receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0049] For example, the first STA 110 can perform the operations intended by the AP. For example, the AP's processor 111 can receive signals via transceiver 113, process receive (RX) signals, generate transmit (TX) signals, and provide control over signal transmission. The AP's memory 112 can store signals received via transceiver 113 (e.g., RX signals) and can store signals to be transmitted via transceiver 113 (e.g., TX signals).

[0050] For example, the second STA 120 can perform operations not expected by the AP STA. For example, the non-AP transceiver 123 performs signal transmission / reception operations. Specifically, it can transmit / receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be packets, etc.).

[0051] For example, a non-AP STA processor 121 can receive signals via transceiver 123, process RX signals, generate TX signals, and provide control over signal transmission. A non-AP STA memory 122 can store signals received via transceiver 123 (e.g., RX signals) and can store signals to be transmitted via transceiver 123 (e.g., TX signals).

[0052] For example, the operation of a device designated as an AP in the description below can be performed in either the first STA 110 or the second STA 120. For instance, if the first STA 110 is an AP, the operation of the device designated as an AP can be controlled by the processor 111 of the first STA 110, and related signals can be transmitted or received via a transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, control information related to the operation of the AP or the AP's TX / RX signals can be stored in the memory 112 of the first STA 110. Similarly, if the second STA 120 is an AP, the operation of the device designated as an AP can be controlled by the processor 121 of the second STA 120, and related signals can be transmitted or received via a transceiver 123 controlled by the processor 121 of the second STA 120. Furthermore, control information related to the operation of the AP or the AP's TX / RX signals can be stored in the memory 122 of the second STA 120.

[0053] For example, in the description below, the operation of a device indicated as a non-AP (or user STA) can be performed in either the first STA 110 or the second STA 120. For instance, if the second STA 120 is a non-AP, the operation of the device indicated as a non-AP can be controlled by the processor 121 of the second STA 120, and related signals can be transmitted or received via a transceiver 123 controlled by the processor 121 of the second STA 120. Additionally, control information related to the operation of a non-AP or non-AP TX / RX signals can be stored in the memory 122 of the second STA 120. Similarly, if the first STA 110 is a non-AP, the operation of the device indicated as a non-AP can be controlled by the processor 111 of the first STA 110, and related signals can be transmitted or received via a transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, control information related to the operation of a non-AP or non-AP TX / RX signals can be stored in the memory 112 of the first STA 110.

[0054] In the following description, the devices referred to as (transmit / receive) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmit / receive) terminal, (transmit / receive) device, (transmit / receive equipment), network, etc., may refer to... Figure 1 STAs 110 and 120. For example, devices designated as (but without specific labels) (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving) equipment, network, etc., may refer to... Figure 1 STAs 110 and 120. For example, in the following example, the operation of various STA transmit / receive signals (e.g., PPDU) can be... Figure 1 This is performed in transceivers 113 and 123. Additionally, in the following examples, various STA operations for generating TX / RX signals or pre-performing data processing and calculations on TX / RX signals can be performed within these transceivers. Figure 1 The operations are executed in processors 111 and 121. Examples of operations for generating TX / RX signals or pre-performing data processing and calculations may include: 1) operations to determine / obtain / configure / calculate / decode / encode bit information of subfields (SIG, STF, LTF, Data) included in the PPDU; 2) operations to determine / configure / obtain time resources or frequency resources (e.g., subcarrier resources) for the subfields (SIG, STF, LTF, Data) included in the PPDU; 3) operations to determine / configure / obtain specific sequences (e.g., pilot sequences, STF / LTF sequences, additional sequences applied to SIG) for the subfields (SIG, STF, LTF, Data) included in the PPDU; 4) power control operations and / or power-saving operations applied to the STA; and 5) operations related to the determination / obtaining / configuration / decoding / encoding of the ACK signal. Additionally, in the following examples, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs to determine / obtain / configure / calculate / decode / decode the TX / RX signal may be stored in... Figure 1 In memory 112 and 122.

[0055] Figure 1 The aforementioned device / STA in subgraph (a) can be as follows Figure 1 The subgraph (b) is modified as shown below. In the following text, the modifications will be based on... Figure 1 The sub-diagram (b) is used to describe STA 110 and STA120 in this specification.

[0056] For example, Figure 1 The transceivers 113 and 123 shown in subgraph (b) can perform the same functions as... Figure 1 The transceiver shown in sub-diagram (a) has the same function as the aforementioned transceiver. For example, Figure 1The processing chips 114 and 124 shown in sub-figure (b) may include processors 111 and 121 and memories 112 and 122. Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (b) can perform operations related to Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (a) have the same functions.

[0057] The mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, user, subscriber STA, network, base station, node B, access point (AP), repeater, router, relay, receiving unit, transmitting unit, receiving STA, transmitting STA, receiving device, transmitting device, receiving equipment and / or transmitting equipment described below may mean Figure 1 The STA 110 and 120 shown in subgraphs (a) / (b) may mean, or Figure 1 The processing chips 114 and 124 are shown in sub-figure (b). That is to say, the technical features of this specification can be found in... Figure 1 It can be performed in STA 110 and 120 as shown in subgraphs (a) / (b), or it can be performed only in... Figure 1 The processing chips 114 and 124 shown in sub-diagram (b) are executed Figure 1 Transceivers 113 and 123 are shown in sub-diagrams (a) and (b). For example, the technical features of transmitting control signals by the STA can be understood as being through... Figure 1 The transceiver 113 shown in sub-diagrams (a) / (b) transmits in Figure 1 The technical features of the control signals generated in processors 111 and 121 are illustrated in sub-figures (a) / (b). Alternatively, the technical features of the STA transmitting control signals can be understood as follows: Figure 1 The technical features of generating control signals to be transmitted to transceivers 113 and 123 in processing chips 114 and 124 are shown in sub-figure (b).

[0058] For example, the technical characteristics of receiving STA control signals can be understood as through... Figure 1 The technical features of transceivers 113 and 123 receiving control signals shown in sub-figure (a) are illustrated. Alternatively, the technical features of receiving STA control signals can be understood as being achieved through... Figure 1 Processors 111 and 121 shown in subgraph (a) obtain Figure 1 The technical features of the control signals received in transceivers 113 and 123 shown in sub-figure (a). Alternatively, the technical features of receiving STA control signals can be understood as being through... Figure 1The processing chips 114 and 124 shown in sub-figure (b) obtain Figure 1 Technical features of the control signals received in transceivers 113 and 123 as shown in sub-figure (b).

[0059] Reference Figure 1 Subgraph (b), software codes 115 and 125 can be included in memories 112 and 122. Software codes 115 and 126 can include instructions for controlling the operation of processors 111 and 121. Software codes 115 and 125 can be included in various programming languages.

[0060] Figure 1 The processors 111 and 121 or processing chips 114 and 124 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, Figure 1 The processors 111 and 121 or processing chips 114 and 124 may include at least one of the following: a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, Figure 1 The processors 111 and 121 or the processing chips 114 and 124 can be made by The SNAPDRAGON™ processor series manufactured by The EXYNOS™ processor series manufactured by The processor series manufactured by The HELIO™ processor series manufactured by The ATOM™ series of processors manufactured or processors enhanced from these processors.

[0061] In this specification, uplink can mean a link used for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc., can be transmitted through the uplink. Similarly, in this specification, downlink can mean a link used for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc., can be transmitted through the downlink.

[0062] Figure 2 This is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0063] Figure 2 The upper part shows the structure of the Infrastructure Basic Services Set (BSS) of the Institute of Electrical and Electronics Engineers (IEEE) 802.11.

[0064] Reference Figure 2The upper part of the wireless LAN system may include one or more infrastructure BSS 200 and 205 (hereinafter referred to as BSS). BSS 200 and 205, as a set of APs and STAs (e.g., access point (AP) 225 and station (STA1) 200-1) that have successfully synchronized to communicate with each other, are not concepts indicating a specific area. BSS 205 may include one or more STAs 205-1 and 205-2 that can join an AP 230.

[0065] A BSS may include at least one STA, an AP that provides distributed services, and a distributed system (DS) 210 that connects multiple APs.

[0066] Distributed system 210 can implement an Extended Service Set (ESS) 240 that is expanded by connecting multiple BSSs 200 and 205. ESS 240 can be used as a term to refer to a network configured by connecting one or more APs 225 or 230 via distributed system 210. APs included in an ESS 240 may have the same Service Set Identifier (SSID).

[0067] Portal 220 can be used as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0068] exist Figure 2 The BSS shown at the top enables networking between APs 225 and 230, as well as between APs 225 and 230 and STAs 200-1, 205-1, and 205-2. However, it also allows for networking between STAs to perform communication even without APs 225 and 230. Networks that enable communication between STAs by configuring networks even without APs 225 and 230 are defined as self-organizing networks or Independent Basic Service Sets (IBSS).

[0069] Figure 2 The lower part shows a conceptual diagram illustrating the IBSS.

[0070] Reference Figure 2 Below this, the IBSS operates as a self-organizing BSS. Because the IBSS does not include access points (APs), there is no centralized management entity performing management functions at a central location. That is, in the IBSS, STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed in a distributed manner. In the IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 can be composed of mobile STAs, and access to DS to form a self-contained network is not permitted.

[0071] Figure 3This shows the general link setup process.

[0072] In S310, the STA can perform network discovery operations. Network discovery operations can include scanning operations by the STA. That is, in order to access a network, the STA needs to discover participating networks. The process of identifying compatible networks before joining a wireless network and identifying networks existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0073] Figure 3 This illustrates network discovery operations including active scanning. In active scanning, the STA performing the scan sends a probe request frame and waits for a response to the probe request frame in order to identify which APs are present nearby while moving to a channel. The responder sends a probe response frame to the STA that sent the probe request frame as a response to the probe request frame. Here, the responder can be the STA that sent the last beacon frame in the BSS of the channel being scanned. In the BSS, the AP is the responder because it sends the beacon frame. In the IBSS, the responder is not fixed because the STAs in the IBSS take turns sending beacon frames. For example, when an STA sends a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA can store the BSS-related information included in the received probe response frame, move to the next channel (e.g., channel 2), and perform a scan in the same way (e.g., sending a probe request and receiving a probe response via channel 2).

[0074] although Figure 3 As not shown, scanning can be performed using a passive scanning method. In passive scanning, the STA performing the scan can wait for beacon frames while moving to a channel. Beacon frames are one of the management frames in IEEE 802.11 and are periodically sent to indicate the presence of a wireless network and enable the STA performing the scan to find and join the wireless network. In a BSS, the AP is used to periodically send beacon frames. In an IBSS, STAs in the IBSS take turns sending beacon frames. Upon receiving a beacon frame, the STA performing the scan stores information about the BSS included in the beacon frame and records beacon frame information for each channel while moving to another channel. The STA receiving the beacon frame can store the BSS-related information included in the received beacon frame, can move to the next channel, and can perform scanning on the next channel using the same method.

[0075] After network discovery, the STA can perform authentication processing in S320. This authentication processing can be referred to as the first authentication processing to clearly distinguish it from the subsequent security setup operations in S340. The authentication processing in S320 may include the STA sending an authentication request frame to the AP and the AP sending an authentication response frame to the STA in response. The authentication frame used for the authentication request / response is a management frame.

[0076] The authentication frame may include information about the authentication algorithm number, authentication transaction sequence number, status code, challenge text, robust security network (RSN), and finite cyclic group.

[0077] The STA can send an authentication request frame to the AP. The AP can determine whether to allow the STA's authentication based on the information included in the received authentication request frame. The AP can provide the authentication processing result to the STA via an authentication response frame.

[0078] When a STA is successfully authenticated, it can perform association processing in S330. Association processing includes the STA sending an association request frame to the AP, and the AP responding by sending an association response frame to the STA. For example, the association request frame may include information about various capabilities, beacon listening interval, service set identifier (SSID), supported rates, supported channels, RSN, mobile domain, supported operation classes, service indication map (TIM) broadcast request, and interoperability service capabilities. Similarly, the association response frame may include information about various capabilities, status codes, association ID (AID), supported rates, enhanced distributed channel access (EDCA) parameter set, received channel power indicator (RCPI), received signal-to-noise ratio indicator (RSNI), mobile domain, timeout interval (association recovery time), overlapping BSS scan parameters, TIM broadcast response, and QoS map.

[0079] In the S340, the STA can perform security setup processing. Security setup processing in the S340 may include the process of setting a private key via a four-way handshake (e.g., via an Extensible Authentication Protocol (EAPOL) frame over the LAN).

[0080] Figure 4 The layout of resource units (RUs) used in the 80MHz band is shown.

[0081] RUs of various sizes can be used, such as 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, and 996-RU. Furthermore, seven DC tones can be inserted into the center frequency, 12 tones can be used in the leftmost guard band of the 80MHz band, and 11 tones can be used in the rightmost guard band of the 80MHz band. Additionally, a 26-RU corresponding to 13 tones on each of the left and right sides of the DC band can be used.

[0082] like Figure 7 As shown, when the RU layout is used for a single user, a 996-RU can be used, in which case five DC tones can be inserted.

[0083] The RUs described in this specification can be used for both uplink (UL) and downlink (DL) communication. For example, when performing UL-MU communication requested by a trigger frame, a transmitting STA (e.g., an AP) can assign a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA via the trigger frame. Thereafter, the first STA can send a first trigger-based PPDU based on the first RU, and the second STA can send a second trigger-based PPDU based on the second RU. The first and second trigger-based PPDUs are sent to the AP in the same (or overlapping) time periods.

[0084] For example, when configuring a DL MU PPDU, a transmitting STA (e.g., an AP) can assign a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA. That is, a transmitting STA (e.g., an AP) can transmit HE-STF, HE-LTF, and data fields for a first STA through the first RU in a MU PPDU, and can transmit HE-STF, HE-LTF, and data fields for a second STA through the second RU.

[0085] Information related to the layout of the RU can be communicated via HE-SIG-B signals.

[0086] The following describes the PPDUs sent / received in the STA of this specification.

[0087] Figure 5 An example of a PPDU used in this specification is shown.

[0088] Figure 5 The PPDU may be referred to by various terms such as EHT PPDU, TX PPDU, RX PPDU, Type 1 or Type N PPDU, etc. For example, in this specification, PPDU or EHT PPDU may be referred to by various terms such as TX PPDU, RX PPDU, Type 1 or Type N PPDU, etc. Furthermore, EHT PPDUs may be used in EHT systems and / or new WLAN systems enhanced from EHT systems.

[0089] Figure 5 The PPDU can indicate all or part of the PPDU types used in the EHT system. For example, Figure 5 The example can be used in both single-user (SU) and multi-user (MU) modes. In other words, Figure 5 The PPDU can be used for one or more receiving STAs. When Figure 5 When using trigger-based (TB) mode, the PPDU can be omitted. Figure 5 The EHT-SIG. In other words, the STA that has received the trigger frame for the uplink MU (UL-MU) can send... Figure 5 The PPDU for EHT-SIG is omitted in the example.

[0090] exist Figure 5 In this context, L-STF to EHT-LTF can be referred to as preamble or physical preamble, and can be generated / sent / received / acquired / decoded at the physical layer.

[0091] Figure 5 The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields can be determined to be 312.5 kHz, and the subcarrier spacing of the EHT-STF, EHT-LTF, and data fields can be determined to be 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields can be represented in units of 312.5 kHz, and the tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and data fields can be represented in units of 78.125 kHz.

[0092] exist Figure 5 In the PPDU, L-LTF and L-STF can be the same as those in the traditional fields.

[0093] The transmitting STA can generate an RL-SIG in the same manner as the L-SIG. BPSK modulation can be applied to the RL-SIG. The receiving STA can determine whether the RX PPDU is an HE PPDU or an EHT PPDU based on the presence of the RL-SIG.

[0094] Universal SIG (U-SIG) can be inserted in Figure 5 Following RL-SIG. U-SIG can be referred to by various terms such as First SIG Field, First SIG, First Type SIG, Control Signal, Control Signal Field, First (Type) Control Signal, etc.

[0095] The U-SIG may include N bits of information and may include information for identifying the type of EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two adjacent OFDM symbols). Each symbol of the U-SIG (e.g., an OFDM symbol) may have a duration of 4 μs. Each symbol of the U-SIG may be used to transmit 26 bits of information. For example, each symbol of the U-SIG may be based on 52 data tones and 4 pilot tones for transmission / reception.

[0096] The public fields and user-specific fields of EHT-SIG can be encoded separately. A user block field included in the user-specific fields can include information for two users, but the last user block field included in the user-specific fields can include information for one user. That is, a user block field of EHT-SIG can include at most two user fields. Figure 8 In the example, each user field may be related to MU-MIMO allocation or non-MU-MIMO allocation.

[0097] The common fields of EHT-SIG may include CRC bits and tail bits. The length of the CRC bits can be determined to be 4 bits. The length of the tail bits can be determined to be 6 bits and can be set to "000000".

[0098] The common fields of EHT-SIG may include RU allocation information. RU allocation information may indicate information related to the location of RUs allocated to multiple users (i.e., multiple receiving STAs). RU allocation information can be configured in 8-bit (or N-bit) units.

[0099] In the following examples, signals represented as (TX / RX / UL / DL) signals, (TX / RX / UL / DL) frames, (TX / RX / UL / DL) packets, (TX / RX / UL / DL) data units, (TX / RX / UL / DL) data, etc., can be based on... Figure 5 The signals transmitted / received by the PPDU. Figure 5 PPDUs can be used to send / receive various types of frames. For example, Figure 5 PPDUs can be used in control frames. Examples of control frames may include Request to Send (RTS), Clear to Send (CTS), Power Saving Poll (PS-poll), BlockACKReq, BlockAck, Null Data Packet (NDP) announcement, and trigger frames. For example, Figure 5 PPDUs can be used for management frames. Examples of management frames may include beacon frames, (re)association request frames, (re)association response frames, probe request frames, and probe response frames. For example, Figure 5 PPDUs can be used in data frames. For example, Figure 5A PPDU can be used to send at least two or more of control frames, management frames, and data frames simultaneously.

[0100] Figure 6 Examples of modified transmitting and / or receiving devices are shown in this specification.

[0101] Figure 1 Each device / STA in subgraphs (a) / (b) can be as follows Figure 6 The modifications shown are as follows. Figure 6 The transceiver 630 can be used with Figure 1 The transceivers 113 and 123 are the same. Figure 6 The transceiver 630 may include a receiver and a transmitter.

[0102] Figure 6 The processor 610 can be with Figure 1 The processors 111 and 121 are the same. Alternatively, Figure 6 The processor 610 can be with Figure 1 The processing chips 114 and 124 are the same.

[0103] Figure 6 The memory 620 can be with Figure 1 The memories 112 and 122 are the same. Alternatively, Figure 6 The memory 620 can be with Figure 1 The memories 112 and 122 are different separate external memories.

[0104] Reference Figure 6 The power management module 611 manages the power used by the processor 610 and / or transceiver 630. The battery 612 supplies power to the power management module 611. The display 613 outputs the results processed by the processor 610. The keypad 614 receives inputs to be used by the processor 610. The keypad 614 can be displayed on the display 613. The SIM card 615 can be an integrated circuit for securely storing the International Mobile Subscriber Identity (IMSI) and its associated keys, used for identifying and authenticating users on mobile phone devices (e.g., mobile phones and computers).

[0105] Reference Figure 6 The speaker 640 can output results related to the sound processed by the processor 610. The microphone 641 can receive input related to the sound to be used by the processor 610.

[0106] The technical features of the multi-link (ML) technology supported by the STA in this specification will be described below.

[0107] The STA (AP and / or non-AP STA) in this specification may support ML communication. ML communication may refer to support for communication across multiple links. Links associated with ML communication may include at least one channel in the 2.4 GHz band, 5 GHz band, and 6 GHz band (e.g., 20 / 40 / 80 / 160 / 240 / 320 MHz channels).

[0108] Multiple links used for ML communication can be configured in various ways. For example, a single STA supporting multiple links for ML communication may include multiple channels in the 2.4 GHz band, multiple channels in the 5 GHz band, and multiple channels in the 6 GHz band. Alternatively, a single STA supporting multiple links for ML communication may include a combination of at least one channel in the 2.4 GHz band (or the 5 GHz / 6 GHz band) and at least one channel in the 5 GHz band (or the 2.4 GHz / 6 GHz band). Furthermore, at least one of the multiple links supported by a single STA for ML communication may be a channel with preamble puncturing applied.

[0109] The STA can perform ML settings to enable ML communication. ML settings can be performed based on management frames or control frames such as beacons, probe requests / responses, and association requests / responses. For example, information related to ML configuration can be included in element fields included in beacons, probe requests / responses, and association requests / responses.

[0110] Once ML setup is complete, the enabled links for ML communication can be determined. The STA can perform frame switching by using at least one of the multiple links determined to be enabled. For example, the enabled links can be used for at least one of management frames, control frames, and data frames.

[0111] When a STA supports multiple links, the transceivers supporting each link can operate as a single logical STA. For example, an STA supporting two links can be represented as a multi-link device (MLD), which includes a first STA for the first link and a second STA for the second link. Similarly, an AP supporting two links can be represented as an AP MLD, which includes a first AP for the first link and a second AP for the second link. Conversely, a non-AP supporting two links can be represented as a non-AP MLD, which includes a first STA for the first link and a second STA for the second link.

[0112] The following sections describe more specific features related to ML settings.

[0113] MLDs (AP MLDs and / or non-AP MLDs) can send information related to the links supported by the corresponding MLD through ML settings. Link information can be configured in various ways. For example, link information includes at least one of the following: 1) whether the MLD (or STA) supports simultaneous RX / TX operation; 2) the number / upper limit of uplinks / downlinks supported by the MLD (or STA); 3) the location / frequency band / resources of the uplinks / downlinks supported by the MLD (or STA); 4) the type (management, control, data, etc.) of frames available or preferred in at least one uplink / downlink; 5) the ACK policy available or preferred in at least one uplink / downlink; and / or 6) at least one TID (Traffic Identifier) ​​available or preferred in at least one uplink / downlink. TIDs are related to the priority of traffic data and are represented by eight types of values ​​according to traditional WLAN standards. That is, eight TID values ​​can be defined corresponding to the four access categories (AC) (AC_BK (background), AC_BE (best effort), AC_VI (video), and AC_VO (voice)) according to the traditional WLAN standard.

[0114] For example, all TIDs used for uplink / downlink can be pre-configured to be mapped. Specifically, if not negotiated via ML settings, all TIDs are used for ML communication. If the mapping between uplink / downlink and TIDs is negotiated via additional ML settings, the negotiated TIDs are used for ML communication.

[0115] Multiple links that can be used by the sending MLD and receiving MLD related to ML communication can be configured through ML settings, and this can be referred to as "enabling links". "Enabling links" can be called in various different ways. For example, it can be referred to as various expressions such as first link, second link, sending link, and receiving link.

[0116] After the ML setup is complete, the MLD can update the ML settings. For example, when it is necessary to update information about a link, the MLD can send information about a new link. Information related to a new link can be sent based on at least one of management frames, control frames, and data frames.

[0117] Depending on the implementation, an MLD may include a non-AP MLD and an AP-MLD. Non-AP MLDs and AP-MLDs may be classified according to the function of the access point (AP). Non-AP MLDs and AP-MLDs may be physically or logically separated. For example, when an MLD performs an AP function, it may be called an AP MLD; when an MLD performs a STA function, it may be called a non-AP MLD.

[0118] In the following description, an MLD has one or more connected / associated STAs and a MAC service access point (SAP) via the uplink layer (Logical Link Control, LLC). MLD can refer to a physical device or a logical device. In the following text, "device" can refer to an MLD.

[0119] Additionally, the MLD may include at least one STA connected to each link in a multi-link system. For example, the processor of the MLD may control at least one STA. For example, at least one STA may be configured and operated independently. At least one STA may include a processor and a transceiver, respectively. For example, at least one STA may operate independently of the processor of the MLD.

[0120] In the following description, for ease of description, it is described that the MLD (or the processor of the MLD) controls at least one STA, but is not limited thereto. As mentioned above, at least one STA can independently transmit / receive signals, independent of the MLD.

[0121] Depending on the implementation, either an AP MLD or a non-AP MLD can be configured with a structure having multiple links. In other words, a non-AP MLD can support multiple links. A non-AP MLD may include multiple STAs. Each of the multiple STAs may have a link corresponding to that STA.

[0122] The 802.11be standard (hereinafter referred to as the EHT standard) supports multiple links. Here, multiple links can include multiple frequency bands. That is, multiple links can mean links included in multiple frequency bands, or multiple links included in one frequency band.

[0123] The EHT standard enables simultaneous TX / RX (STR) channel access in multi-link environments, depending on link capabilities. Devices supporting multiple links can be defined as non-AP / AP multi-link devices (MLDs). STR capability means the ability to simultaneously transmit / receive data (or signals) on multiple links. That is, while data transmission occurs on another link, an MLD supporting STR capability (hereinafter, STR MLD) can receive data through one link.

[0124] On the other hand, because data collisions can occur due to interference, MLDs that do not support STR capabilities (hereinafter, non-STR MLDs) cannot transmit and receive data (or signals) simultaneously. For example, when a non-STR MLD receives data (or signals) from one link, it does not attempt to transmit to another link to avoid interference. If data (or signals) transmission and reception occur simultaneously on two links, data (or signal) collisions may occur.

[0125] In other words, an STR MLD can simultaneously perform signal transmission and reception across multiple links. A non-STR MLD cannot simultaneously transmit and receive signals across multiple links. While transmitting a signal on the first link in a multi-link system, an STA that does not support STR operations cannot receive signals on links other than the first link, but can still transmit signals. Conversely, while receiving a signal on the first link in a multi-link system, an STA that does not support STR operations cannot transmit signals on links other than the first link, but can still receive signals.

[0126] EHT (11be) can consider multi-link technology. In this paper, multi-link can include multiple frequency bands. That is, multi-link can represent links in multiple frequency bands, or multiple multi-links within a single frequency band. Two types of multi-link operation are considered. The ability to simultaneously receive and transmit in multiple links is called simultaneous transmit and receive (STR). It can be said that links with STR capability are STR relationships, and links without STR capability are non-STR relationships.

[0127] Figure 7 An example of STA MLD is shown.

[0128] Reference Figure 7 A STA MLD can have multiple links (e.g., three links). An ML setup is defined in 11be for connections between MLDs via a single link. Therefore, a STA can provide information (e.g., capabilities) about one or more links to a single ML setup. This specification presents methods for processing ML setups and providing this information.

[0129] In this specification, STA (or STA MLD) may mean AP (or AP MLD) or non-AP (or non-AP MLD).

[0130] First, the link configuration types between AP MLDs and non-AP MLDs are defined.

[0131] Supported Link Set: Links supported by STA MLD

[0132] Configure link sets: Links that perform ML settings on AP MLD and non-AP MLD.

[0133] Operational link set: Links that are not part of the AP MLD and those that are actually operated (i.e., exchange frames) by the AP MLD.

[0134] Figure 8 This illustrates the implementation methods for setting up the relationships between various links.

[0135] Reference Figure 8Supported link sets may include configuration link sets, and configuration link sets may include operation link sets. Alternatively, configuration link sets may be the same as operation link sets. That is, all configuration links can be operation links. In other words, configuration links and operation links may not be distinguished.

[0136] Figure 9 This illustrates an implementation of the link set relationship.

[0137] Reference Figure 9 The AP MLD can include AP1 through AP4, while the non-AP MLD can include STA A and STA B. In this example, the supported link set for the AP MLD corresponds to links 1, 2, 3, and 4. However, the STAs of the non-AP MLD do not support 6GHz, so AP4 is not configured. Therefore, the configured link set corresponds to links 1, 2, and 3. Although the configuration is implemented with three links, since the non-AP MLD can use two links, the actual operational link set can correspond to links 1 and 3.

[0138] Alternatively, a STA can perform link setup with only one AP, and the setup link can be the same as the operation link. That is, STA A can operate by setting up with AP1, and STA B can operate by setting up with AP3 (or AP2).

[0139] That is, if AP and STA are only aggregated in pairs to set up a link, i.e., if AP and STA are mapped in a 1:1 manner, then AP2 (link 2) can be excluded in the setup in this example.

[0140] Figure 10 This shows an example of the overall process for multi-link discovery and setup.

[0141] Reference Figure 10 Partial information can refer to partial information, such as information that should at least be known (e.g., reduced Neighbor Report (RNR) elements), such as the channel and the Channel Basic Service Set Identifier (BSSID). Complete information can refer to complete information, such as all capabilities, operating parameters, etc., in a traditional context. Additionally, associated links can refer to the links that perform ML settings.

[0142] In multi-link discovery operations, non-AP MLDs can know (partial or complete) information about each AP in the AP MLD. In other words, if AP1's link 1 is a link performing ML settings (e.g., associated link), then AP1's complete information is known as in the conventional case, and for AP2, AP3, and AP4, partial or complete information is known.

[0143] Based on partial and / or complete information, a non-AP MLD can perform ML setup with an AP MLD. If using a traditional association request / response frame, in the association request, the non-AP MLD requests to set up and operate the link, and the AP MLD responds to this.

[0144] When a non-AP MLD STA requests ML settings, it needs to report information about the other STAs. This may be included if an MLD level exists—that is, information common to all STAs—otherwise, it may not be included. Methods for indicating information about individual STAs may include the following.

[0145] 1) Provide information about all STAs included in the non-AP MLD.

[0146] Regardless of the configuration and operation of the link, information about all STAs can be provided. That is, when the first STA included outside the AP MLD performs configuration, information about all other STAs included outside the AP MLD can be provided. This provides flexibility from the ML configuration perspective when the AP MLD determines STAs suitable for ML configuration. Additionally, since STAs that are not yet configured may be configured at a later time, providing corresponding STA information by the AP MLD can be helpful. However, signaling overhead may increase compared to other methods.

[0147] 2) Provide information about the STA to be configured.

[0148] - Regardless of the operational link, it can provide information about all STAs to be configured. Similar to method 1), this provides flexibility from the perspective of ML settings when APMLD determines STAs suitable for ML settings.

[0149] 3) Provide information about the STA to be actually operated.

[0150] - If information is not provided about STAs that have minimal signaling overhead but are not actually operating, it may be difficult to perform operations such as link switching at a later time.

[0151] Figure 11 An implementation of a method for providing information about the STA included in the MLD is shown.

[0152] Reference Figure 11 STA C is difficult to configure with the AP MLD. However, when using method 1), the non-AP MLD can also provide information about STA C. Therefore, no information about STA C is provided in methods 2) and 3).

[0153] That is, according to method 1), information related to STA A, STA B, and STA C can be provided to the AP MLD, and according to methods 2) and 3), information related to STA A and STA B can be provided to the AP MLD. In this example, since operating the STA is the same as setting the STA, the same information can be provided.

[0154] In addition to providing information about the STA, the non-AP MLD can request certain APs that the corresponding STA expects to set up and certain APs that the corresponding STA expects to actually operate. For example, although in Figure 11 STA B is configured with AP2 and AP3, but operation can actually be performed on link 3 of AP3. Therefore, a method to indicate this is needed. In particular, this request can be considered in conjunction with the above-described method of indication for each STA.

[0155] In the following example, the associated link is link 1, and it is described by focusing on setting up the STA. When STA A requests, information about STA A can be included in the EHT capability element, etc., as in the traditional case, and only information about other STAs besides STAA can be included in the multi-link element.

[0156] A. Provide information about all STAs included in the non-AP MLD and instruct on STA setup and operation links.

[0157] Figure 12 An implementation of method A is shown.

[0158] Reference Figure 12 The information sent by STA A, which is not in the AP MLD, includes the complete information of STA A and STA B, which are also not in the AP MLD, and can instruct STA A and STA B to be configured as STAs. In addition, except for the incapable link 4, STA A can request {link 1, link 2, link 3} as configured links, and for operational links, it can request STA A to operate with link 1 and STA B to operate with link 3.

[0159] Examples of methods that indicate information about method A are shown below, but are not limited to these.

[0160] A-1) The information for each STA indicates whether it is configured and which link it will operate on. Additionally, it indicates the link configuration separately.

[0161] For example, whether to set up a link can be indicated using a 1-bit indicator, and whether to operate a link can be indicated using a bitmap or a link identifier (ID) that can identify the link. Alternatively, an operation link can be indicated by a TID that is mapped together with the link ID. Alternatively, the AP MLD can request information from a non-AP MLD regarding a specific link it will set up / operate. Additionally, setting up a link can also be indicated by enumerating link IDs, or by using a bitmap indicator. When setting up a link is the same as operating a link, setting up only the link can be indicated by enumerating link IDs, or by using a bitmap indicator.

[0162] Link configuration can be indicated individually, but this is not mandatory. That is, link configuration can be indicated in the information of each STA. However, this method may have higher overhead compared to indicating information individually.

[0163] Figure 13 An implementation of method A-1 is shown.

[0164] Reference Figure 13 ,exist Figure 12 The information that STA A of the China-Africa AP MLD needs to send may include, for example: Figure 13 The information shown illustrates the configuration. In the case of a link bitmap, it is assumed that the links from the AP are indicated in the order of links 1, 2, 3, and 4. STA A is a setup STA with Setup=1, and operating the link may include an ID indicating link 1 (and a TID to be mapped) or a bitmap 1000 indicating link 1. Similarly, STA B is a setup STA with Setup=1, and operating the link may include an ID indicating link 3 (and a TID to be mapped) or a bitmap 0010 indicating link 3.

[0165] Bitmap 1110 is used to indicate links 1, 2, and 3 as configuration links. That is, the configuration link field may include bitmap 1110.

[0166] A-2) indicates separately the setup STA or operation link in A-1.

[0167] - For example, setting up STAs can be indicated using a bitmap corresponding to the number of STAs, and operating links can be based on the order of the STAs indicated by the information (e.g., Figure 14 The link ID can be indicated by STA A->STA B. Alternatively, links can be configured by enumerating link IDs or by using a bitmap.

[0168] Figure 14 An implementation of method A-2 is shown.

[0169] Reference Figure 14 , Figure 14 The middle shows with Figure 12Example of the relevant indication method A-2. In the case of a link bitmap, it is assumed that the links from the AP are indicated by default in the order of links 1, 2, 3, and 4. STA A's operation link indication bitmap 1000 indicates the ID (and TID to be mapped) of link 1 or indicates link 1. That is, the operation link field of STA A may include the ID of link 1, the TID to be mapped, and / or bitmap 1000. Similarly, STA B's operation link indication bitmap 0010 indicates the ID (and TID to be mapped) of link 3 or indicates link 3. That is, STA B's operation link field may include the ID of link 3, the ID to be mapped, and / or bitmap 0010. In this example, bitmap 1110 is used to indicate links 1, 2, and 3 as set links. In addition, the set STA information (i.e., the set STA field) may include 2 bits according to the order of the STAs (e.g., STA A and STA B) that are used as STA indication information to be set (i.e., STAA->STA B). Figure 11 This requests information about the settings of both STA A and STA B.

[0170] A-3) separately indicates both the setup STA and the operation link in A-1.

[0171] For example, the STA field can include a bitmap corresponding to the number of STAs, and the operation link can be based on the order of the STAs in the instruction information (e.g., Figure 14 The STA A->STA B) indicates the link ID. Alternatively, link configuration can be indicated by enumerating link IDs or by using a bitmap.

[0172] Figure 15 An implementation of method A-3 is shown.

[0173] Reference Figure 15 , Figure 15 The middle shows with Figure 12 Example of the relevant indication method A-3). In the case of a link bitmap, it is assumed that the links from the AP are indicated by default in the order of links 1, 2, 3, and 4. In this example, bitmap 1110 is used to indicate links 1, 2, and 3 as the set links. Additionally, the set STA information (i.e., the set STA field) may include 2 bits used according to the order of the STAs as the STAs to be set (i.e., STA A -> STA B). Figure 11 This request requests information from both STA A and STA B. Additionally, for operational links, link IDs are used in the order indicated by the STA information, such that STA A requests link 1 and STA B requests link 3 as the operational link. Information related to the TIDs to be mapped for each link may also be included.

[0174] A-4) In the information of each STA in A-1, the operation link is indicated to indicate operation while setting, and another value (e.g., 0) is set in the STA that will not request setting / operation.

[0175] Figure 16 An implementation of method A-4 is shown.

[0176] Reference Figure 16 Assuming Figure 11 As shown, there is also an STA C. STA A is the STA requesting setup, and the information sent by STA A may include information about STA B and STA C. When the STA and AP performing link setup are mapped 1:1, the operating link can be the same as the setup link. Therefore, the fields related to STA B include the ID of link 1 and the request to operate simultaneously with the setup of link 1, and since STA C is the STA that does not want to be set up, the fields related to STA C are set to 0 as the link ID in the operating link. Any other value other than 0 can be set. For example, the link ID of STA C that does not want to be set up can be set to the link ID of the associated link (e.g., ...). Figure 12 (Link ID of AP 1).

[0177] B. Provide information about the STAs to be configured. Treat these STAs as requesting configuration and instructing the operation of the link (e.g., link ID).

[0178] Except for whether or not the STA is configured, this method is the same as method A (e.g., including methods A-1, A-2, and A-3). In some cases, only in method A, a specific STA may not send a request to the STA to be configured. However, in method B, since only information about the STA that will send the configuration request is included, it is not necessary to indicate information about the STA being configured.

[0179] Figure 17 An implementation of method B is shown.

[0180] Reference Figure 17 Method B is almost identical to Method A. However, since STA C is not a STA requesting setup, it is excluded from the information, and only information about STA A and STA B is included. Furthermore, since STA A and STA B are already setup request STAs, whether or not setup is required is not included.

[0181] ※If all STAs should always be set regardless of their capabilities, then method B can be considered.

[0182] * If all links should always be configured regardless of the capabilities of the STA / AP, then it may not be necessary to instruct the link configuration.

[0183] *Furthermore, since the AP MLD may be unaware of the existence of STA C, when using method B, the non-AP MLD can report information such as "number of STAs" (total number of STAs) to the AP MLD via an association request frame to indicate the existence of STA C. With this information, the AP MLD can request information by considering not setting up an STA for operation (e.g., handover) at a later time.

[0184] The above describes a method for indicating information when a STA (Station) that is not an AP MLD requests ML settings. Next, a method for indicating information when an AP MLD responds to an ML settings request is presented.

[0185] By default, AP MLD can respond to ML setup requests as accept, reject, or by modifying a portion of the request.

[0186] 1. Under the condition of acceptance

[0187] If the AP MLD accepts ML settings requested by a non-AP MLD, it should accept the settings / operation link-related information requested by the non-AP MLD and respond accordingly.

[0188] By default, when responding to ML settings, the AP MLD can provide complete information about each link (e.g., all capabilities, relevant parameter information) and may include instructions on setting up and / or operating the links. Methods used for this may include the following.

[0189] 1-1. When only complete information about the configured access point (AP) is included.

[0190] - The link / AP, including complete information, is ultimately configured as the link (AP). Additionally, since the AP MLD has been accepted, the operational link can also be configured as requested by a non-AP MLD.

[0191] Figure 18 An implementation of method 1-1 is shown.

[0192] Reference Figure 18 The AP MLD can accept the requested links, and the acceptance signal can include complete information about APs 1, 2, and 3 as the setting APs (links). If the APs and STAs are only aggregated in pairs to set up a single link, i.e., if the APs and STAs are mapped in a 1:1 manner, then AP2 can be excluded from the setup in this example. That is, information about AP2 can be excluded. For example, a non-AP MLD can send an association request frame to the AP-MLD requesting the setup of links 1 and 3, and the AP MLD can send an association response frame accepting the setup of links 1 and 3. The association response frame can include complete information about APs 1 and 3 operating in links 1 and 3.

[0193] 1-2. When including complete information about all access points (APs)

[0194] Since the AP MLD has accepted the configuration, setup / operation links not requested by the AP MLD can be configured directly. However, for reliable information, the AP MLD may additionally indicate the setup links in bitmap form.

[0195] Figure 19 Implementation methods 1-2 are shown.

[0196] Reference Figure 19 This can include a bitmap for setting up links. In the case of a link bitmap, it is assumed that the links from the APs are indicated by default in the order of links 1, 2, 3, and 4. Since this is accepted by the AP MLD, settings are performed for links 1, 2, and 3, and the bitmap related to setting up the links can be 1110. Additionally, even if AP4 is not set up, complete information about all APs (i.e., AP1, AP2, AP3, and AP4) can be included in the AP MLD. If APs and STAs are only aggregated in pairs to set up a single link, i.e., if APs and STAs are mapped 1:1, then AP2 can be excluded from the settings in this example. That is, the bits for AP2 can be 0. For example, a non-AP MLD can send an association request frame to the AP-MLD requesting the settings of links 1 and 3, and the AP MLD can send an association response frame accepting the settings of links 1 and 3. The association response frame can include complete information about AP1, AP2, and AP3 operating in links 1, 2, and 3.

[0197] 2. When you need to change the settings of some requests.

[0198] The AP MLD may partially modify the setup and / or operation links (e.g., links mapped to STAs) for ML setup requests not requested by the AP MLD. Reasons for modification may include various issues, such as link quality for proper communication, or the ability to communicate. Partial modification is implemented in the following situations.

[0199] - When only some requests are accepted for the setup link and / or operation link

[0200] - When the setup and / or operation links accept some or all requests, and respond separately to other links (recommended)

[0201] Therefore, AP MLD should respond accordingly. In particular, the response method can be similar to the accepted case.

[0202] By default, when responding to ML settings, the AP MLD will provide complete information about each link and may include instructions on setting up and / or operating the links. Methods used for this may include the following.

[0203] 2-1. When setting up and / or operating a link only for the requested link, the accepted link only includes complete information - the link / AP that includes the information is ultimately the set-up link (AP). However, some requested links may not be included.

[0204] Figure 20 An implementation of method 2-1 is shown.

[0205] Reference Figure 20 The non-AP MLD can request the configuration of links 1, 2, and 3. AP1 accepts requests for links 1 and 3, but determines that link 2 is not suitable as the configuration link, and therefore responds by selecting APs 1 and 3 as the configuration APs. Therefore, the accept signal sent by the AP MLD can include complete information about APs 1 and 3 as configuration APs.

[0206] exist Figure 20 In this configuration, the number of STAs is set to 2 (i.e., STA A and STA B), and the number of links is set to 3 (link 1, link 2, and link 3). However, the number of STAs set can be equal to the number of links set. For example, a non-AP MLD can request to set STA A with link 1 and STA B with link 3. The AP MLD can accept only the settings for link 1 (which is part of the request for links 1 and 3) and can send only the complete information of AP1 operating on link 1 to the non-AP MLD.

[0207] Figure 21 An implementation of method 2-1 is shown.

[0208] Reference Figure 21 The non-AP MLD can request the configuration of links 1, 2, and 3. AP 1 accepts requests for links 1 and 2, but determines that link 3 is not suitable as the configuration link, and therefore responds by selecting APs 1 and 2 as the configuration APs. Additionally, link 1 determines that STA B, rather than STA A, is suitable for operation, and link 2 determines that STA A, rather than STA B, is suitable for operation. Therefore, the accept signal sent by the AP MLD can include complete information about APs 1 and 3 as configuration APs. Furthermore, the AP MLD can also instruct the non-AP MLD to operate STA A on link 2 and STA B on link 1.

[0209] exist Figure 21In this configuration, the number of STAs is set to 2 (i.e., STA A and STA B), and the number of links is set to 3 (link 1, link 2, and link 3). However, the number of STAs set can be equal to the number of links set. For example, a non-AP MLD can request to set STA A with link 1 and STA B with link 3. The AP MLD can accept only the setting for link 1 (which is part of the request for links 1 and 3) and can determine that it is appropriate for STA B, rather than STA A, to operate on link 1. The AP MLD can send only the complete information of AP1 operating on link 1 to the non-AP MLD.

[0210] 2-2. When including complete information about all access points (APs)

[0211] - The configuration of the links can be indicated in bitmap form by including complete information about all APs (links) regardless of whether configuration is to be performed.

[0212] Figure 22 An implementation of method 2-2 is shown.

[0213] Reference Figure 22 The non-AP MLD can request the configuration of links 1, 2, and 3. AP1 accepts requests for links 1 and 3, but determines that link 2 is not suitable as the configuration link, and therefore responds by selecting AP(link) 1 and 3 as the configuration AP(link). The accept signal sent by the AP MLD may include information about all AP(link) 1 and 3, and may additionally include bitmap information (e.g., 1010) for AP(link) 1 and 3 as the configuration AP(link). In the case of the link bitmap, it is assumed that the links from the APs are indicated by default in the order of links 1, 2, 3, and 4.

[0214] Figure 23 An implementation of method 2-2 is shown.

[0215] Reference Figure 23The non-AP MLD can request the configuration of links 1, 2, and 3. AP 1 accepts requests for links 1 and 2, but determines that link 3 is not suitable as the configuration link, and therefore responds by selecting APs (links) 1 and 2 as the configuration APs (links). Additionally, link 1 determines that STA B is suitable for operation instead of STA A, and link 2 determines that STA A is suitable for operation instead of STA B. Therefore, the accept signal sent by the AP MLD can include information about all APs (links), and may additionally include bitmap information (e.g., 1100) for APs (links) 1 and 2 as configuration APs (links). In the case of the link bitmap, it is assumed that the links from the APs are indicated by default in the order of links 1, 2, 3, and 4. Additionally, the accept signal may also include information indicating that STA operates in link 2 and STA B operates in link 1.

[0216] Figure 24 An implementation method for operating the STA MLD is shown.

[0217] Reference Figure 24 A STA MLD may include a first STA and a second STA. The first STA may operate in a first link, and the second STA may operate in a second link.

[0218] The STA MLD can send an association request frame (S2401). For example, the STA MLD can send an association request frame to the Access Point (AP) MLD. For example, the association request frame may include the capability information of the requesting STA that is associated with the AP MLD and the requesting link associated with the requesting STA, which is included in the STA MLD.

[0219] For example, the capability information requested for the STA may include complete information, which includes all the capabilities requested for the STA.

[0220] For example, a requesting STA to associate with an AP MLD may include a first STA and a second STA. The association response frame may include capability information of the first AP that the AP MLD accepts in the associated first link within the requesting link.

[0221] For example, information related to the requested link may include a link identifier (ID).

[0222] For example, an association request frame may be sent by the first STA via the first link. For example, information about links other than the first link in the request link may be included in the multi-link element.

[0223] STAMLD can receive associated response frames (S2420). For example, STAMLD can receive associated response frames from AP MLD. For example, the associated response frame may include the capability information of AP MLD in the requesting link to accept APs operating in the associated link.

[0224] For example, the capability information of an AP operating in an associated link accepted by the AP MLD may include complete information, which includes all the capabilities of the AP operating in an associated link accepted by the AP MLD.

[0225] For example, a requesting STA to associate with an AP MLD may include a first STA and a second STA. For example, an association response frame may include capability information of the first and second APs that the AP MLD in the requesting link accepts operation in the associated first and second links.

[0226] When the associated response frame includes only complete information about the configured access point (AP)

[0227] The link / AP, including complete information, is ultimately configured (AP). Additionally, since the AP MLD has been accepted, the operational link can also be configured as requested by a non-AP MLD.

[0228] For example, a non-AP MLD can send an association request frame to the AP-MLD requesting the configuration of links 1 and 3, and the AP-MLD can send an association response frame accepting the configuration of links 1 and 3. The association response frame may include complete information about AP1 and AP3 operating in links 1 and 3.

[0229] When the link being set and / or operated only in the link requested by the associated response frame, and the link being accepted only includes complete information.

[0230] The link / AP that includes information is ultimately the link (AP) that is configured. However, some requested links may not be included.

[0231] The number of STAs configured can be equal to the number of links configured. For example, a non-AP MLD can request to configure STA A with link 1 and STA B with link 3. The AP MLD can accept only the configuration for link 1 (which is part of the request for links 1 and 3) and can send only the complete information of AP1 operating on link 1 to the non-AP MLD.

[0232] For example, a non-AP MLD can request to set up STA A with link 1 and STA B with link 3. The AP MLD can accept only the settings for link 1 (as part of the requests for links 1 and 3) and can determine that it is appropriate for STA B, rather than STA A, to operate on link 1. The AP MLD can then send only the complete information about AP1 operating on link 1 to the non-AP MLD.

[0233] Figure 25 An implementation method for operating the AP MLD is shown.

[0234] Reference Figure 25 An AP MLD includes a first AP and a second AP. The first AP can operate in a first link, and the second AP can operate in a second link. A STA MLD includes a first STA and a second STA. The first STA can operate in a first link, and the second STA can operate in a second link.

[0235] The AP MLD can receive association request frames (S2510). For example, the AP MLD can receive association request frames from a station (STA) MLD. For example, the association request frame may include capability information of the requesting STA associated with the AP MLD and information related to the requesting link associated with the requesting STA, which is included in the STA MLD.

[0236] For example, the capability information requested for the STA may include complete information, which includes all the capabilities requested for the STA.

[0237] For example, a requesting STA to associate with an AP MLD may include a first STA and a second STA. The association response frame may include capability information of the first AP that the AP MLD accepts in the associated first link within the requesting link.

[0238] For example, information related to the requested link may include a link identifier (ID).

[0239] For example, an association request frame may be sent by the first STA via the first link. For example, information about links other than the first link in the request link may be included in the multi-link element.

[0240] The AP MLD can send an association response frame (S2520). For example, the AP MLD can send an association response frame to the STA MLD. For example, the association response frame can include the capability information of the AP MLD to accept operation of the associated link in the requested link.

[0241] For example, the capability information of an AP operating in an associated link accepted by the AP MLD may include complete information, which includes all the capabilities of the AP operating in an associated link accepted by the AP MLD.

[0242] For example, a requesting STA to associate with an AP MLD may include a first STA and a second STA. For example, an association response frame may include capability information of the first and second APs that the AP MLD accepts in the associated first and second links within the requesting link.

[0243] Figure 24 and Figure 25 Some of the detailed steps shown in the examples may not be necessary and can be omitted. Besides... Figure 24 and Figure 25 Other steps may be added in addition to those shown, and the order of the steps may vary. Some of the steps described above may have independent technical meaning.

[0244] The technical features described above in this specification can be applied to various devices and methods. For example, the technical features described above in this specification can be applied through... Figure 1 and / or Figure 6 The device is used to perform / support this. For example, the technical features described above in this specification may only be applied to... Figure 1 and / or Figure 6 Part of it. For example, the above-described technical features of this specification may be based on Figure 1 This can be achieved using processing chips 114 and 124, or it can be based on... Figure 1 The processors 111 and 121 and the memories 112 and 122 are used to implement this, or it can be based on... Figure 6 The device is implemented using a processor 610 and a memory 620. For example, the device of this specification includes: a memory; and a processor operatively connected to the memory. The processor may be configured to: send an association request frame to the AP MLD, wherein the association request frame includes capability information of the requesting STA among the STAs included in the STA MLD that requests association with the AP MLD and information related to the requesting link requested by the requesting STA; and receive an association response frame from the AP MLD, wherein the association response frame includes capability information of the AP MLD in the requesting link that accepts operation of the AP in the associated link.

[0245] The technical features of this specification can be implemented based on a computer-readable medium (CRM). For example, the CRM proposed in this specification is at least one computer-readable medium having instructions executed by at least one processor of a station (STA) multilink device (MLD) of a wireless local area network (WLAN) system, wherein the STAMLD includes a first STA and a second STA, the first STA operating in a first link and the second STA operating in a second link. The instructions are executable to perform operations including: sending an association request frame to an access point (AP) MLD, wherein the association request frame includes capability information of the requesting STA among the STAs included in the STA MLD requesting association with the AP MLD and information related to the requesting link requested by the requesting STA; and receiving an association response frame from the AP MLD, wherein the association response frame includes capability information of the AP MLD in the requesting link accepting the operation of the AP in the associated link.

[0246] The instructions stored in the CRM of this specification can be executed by at least one processor. The at least one processor associated with the CRM of this specification can be... Figure 1 Processors 111 and 121 or processing chips 114 and 124 or Figure 6 The processor is 610. Furthermore, the CRM in this specification can be... Figure 1 The memory 112 and 122 or Figure 6 The memory 620 or a separate external memory / storage medium / disk, etc.

[0247] The technical features described above in this specification are applicable to various applications or business models. For example, these technical features can be applied to wireless communication in devices that support artificial intelligence (AI).

[0248] Artificial intelligence (AI) refers to the research field concerning artificial intelligence or the methods for creating AI, while machine learning refers to the research field concerning methods for defining and solving various problems within the field of AI. Machine learning is also defined as algorithms that improve operational performance through stable operational experience.

[0249] Artificial neural networks (ANNs) are models used in machine learning, and can refer to an overall problem-solving model comprising artificial neurons (nodes) that form a network by combining synapses. An artificial neural network can be defined by the connection pattern between neurons in different layers, the learning process that updates model parameters, and the activation function that generates output values.

[0250] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses connecting the neurons. In an artificial neural network, each neuron may output a function value of an activation function that takes input signals, weights, and biases as input through the synapse.

[0251] Model parameters refer to the parameters determined through learning, and include the weights of synaptic connections and the biases of neurons. Hyperparameters refer to the parameters set in a machine learning algorithm before learning, and include the learning rate, number of iterations, mini-batch size, and initialization function.

[0252] Learning artificial neural networks aims to determine the model parameters used to minimize the loss function. The loss function can be used as an index to determine the optimal model parameters during the learning process of artificial neural networks.

[0253] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning.

[0254] Supervised learning refers to the method of training an artificial neural network with labeled training data, where the labels indicate the correct answer (or result value) that the artificial neural network should infer when the training data is input. Unsupervised learning refers to the method of training an artificial neural network without labeled training data. Reinforcement learning refers to a training method that defines an agent in the training environment to select actions or action sequences to maximize the cumulative reward in each state.

[0255] Machine learning that utilizes deep neural networks (DNNs) with multiple hidden layers, including artificial neural networks, is called deep learning, and deep learning is a part of machine learning. In the following text, machine learning is interpreted as including deep learning.

[0256] The above-mentioned technical features can be applied to wireless communication of robots.

[0257] A robot can refer to a machine that automatically processes or operates a given task using its own capabilities. Specifically, a robot that has the ability to recognize its environment and autonomously make judgments to perform operations can be called an intelligent robot.

[0258] Robots can be classified according to their purpose or field, such as industrial, medical, household, and military robots. A robot may include actuators or drives, which include motors to perform various physical operations (e.g., moving robot joints). Additionally, mobile robots may include wheels, brakes, propellers, etc., in their drives to move on the ground or fly in the air.

[0259] The aforementioned technical features can be applied to devices that support extended reality.

[0260] Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphics technology that provides real-world objects and backgrounds only in CG images; AR technology is a computer graphics technology that provides virtual CG images on top of real object images; and MR technology is a computer graphics technology that provides virtual objects that are mixed and combined with the real world.

[0261] The similarity between MR and AR technologies lies in the fact that real and virtual objects are displayed together. However, in AR, virtual objects serve as a complement to real objects, while in MR, virtual and real objects are displayed as equal entities.

[0262] XR technology can be applied to head-mounted displays (HMDs), head-up displays (HUDs), mobile phones, tablet PCs, laptops, desktop computers, TVs, digital signage, and more. Devices that utilize XR technology can be referred to as XR devices.

[0263] The claims set forth herein can be combined in various ways. For example, the technical features of the method claims of this specification can be combined to implement an apparatus, and the technical features of the apparatus claims of this specification can be combined to implement it by a method. Furthermore, the technical features of the method claims and the apparatus claims of this specification can be combined to implement an apparatus, and the technical features of the method claims and the apparatus claims of this specification can be combined to implement it by a method.

Claims

1. A method executed in a station-based multi-link device (MLD) of a wireless local area network (WLAN) system, the method comprising the following steps: Send an association request frame to the access point (AP) MLD, wherein the association request frame includes STA capability information requested for configuration with the AP MLD, a link identifier ID for the STA, and a service identifier TID mapped to the link ID, wherein the STA is included in the STA MLD; and The AP MLD receives an associated response frame, wherein the associated response frame includes capability information of the links accepted by the AP MLD.

2. The method according to claim 1, wherein, The capability information of the STA includes complete information, which includes all the capabilities of the STA.

3. The method according to claim 1, wherein, The capability information in the associated response frame includes complete information that includes all capabilities of the AP operating in the link accepted by the AP MLD.

4. A multi-link device (MLD) for a station (STA) in a wireless local area network (WLAN) system, the STA MLD comprising: A transceiver that transmits and receives radio signals; as well as A processor, connected to the transceiver, wherein the processor is configured to: A connection request frame is sent to the access point (AP) MLD. This connection request frame includes the capability information of the STA (Station) requested to be configured with the AP MLD, the link identifier ID for the STA, and the service identifier TID mapped to the link ID. The STA is included in the STMLD. The AP MLD receives an associated response frame, wherein the associated response frame includes capability information of the links accepted by the AP MLD.

5. The STAMLD according to claim 4, wherein, The processor is also configured to perform the steps of the method according to any one of claims 2 to 3.

6. A method executed in an access point (AP) multi-link device (MLD) of a wireless local area network (WLAN) system, the method comprising the following steps: The slave station STAMLD receives an association request frame, wherein the association request frame includes STA capability information requesting configuration with the AP MLD, a link identifier ID for the STA, and a service identifier TID mapped to the link ID, wherein the STA is included in the STAMLD; and Send an association response frame to the STAMLD, wherein the association response frame includes the capability information of the links accepted by the AP MLD.

7. The method according to claim 6, wherein, The capability information of the STA includes complete information, which includes all the capabilities of the STA.

8. The method according to claim 6, wherein, The capability information in the associated response frame includes complete information that includes all capabilities of the AP operating in the link accepted by the AP MLD.

9. An access point (AP) multi-link device (MLD) for use in a wireless local area network (WLAN) system, the AP MLD comprising: A transceiver that transmits and receives radio signals; as well as A processor, connected to the transceiver, wherein the processor is configured to: The slave station STAMLD receives an association request frame, wherein the association request frame includes STA capability information requesting configuration with the AP MLD, a link identifier ID for the STA, and a service identifier TID mapped to the link ID, wherein the STA is included in the STAMLD; and Send an association response frame to the STAMLD, wherein the association response frame includes the capability information of the links accepted by the AP MLD.

10. The AP MLD according to claim 9, wherein, The processor is also configured to perform the steps of the method according to any one of claims 7 to 8.

Images