Multi-link device and method

By introducing only receiving STAs in a multi-link device and controlling their functions with circuits, the spacious, expensive and power consumption problems of chipsets caused by the increase in the number of STAs in the prior art are solved, and a multi-chain with lower power and complexity is achieved The network equipment improves the efficiency of link switching and data transmission.

CN118947218APending Publication Date: 2024-11-12SONY GROUP CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030132.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-25
Filing Date
2023-03-16
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

Existing multi-link devices have become spacious, expensive and power-consuming due to the need for an attached STA for each link, especially with problems in user non-access point MLD devices.

Method used

A reception-only STA (Rx STA) is introduced, which can only be received but cannot be transmitted. The reception-sTA is controlled by the circuit to assist the MLD to receive control information, and switch channels when necessary to reduce the number and power consumption of the STA.

Benefits of technology

A multi-link device with lower power and complexity is realized, reducing the number of STAs, reducing the cost and power consumption of chipsets, while improving the efficiency of link handover and low latency of data transfer.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947218A_ABST
    Figure CN118947218A_ABST
Patent Text Reader

Abstract

A first multi-link device includes: a first station including a transmitter and a receiver and configured to communicate with a first station of a second multi-link device on a first link; a second station including a receiver but not including a transmitter and configured to receive control information from another first station of a second multi-link device on a second link different from the first link and / or from another communication device; and circuitry configured to control the first station and a second station, where the second station is configured to provide the received control information to the circuitry and / or the first station.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a first multi-link device and a corresponding method. Background Art

[0002] A multi-link device (MLD) combines multiple stations (STAs), each operating on a specific link, to achieve higher throughput and / or lower latency than a single link device. Generally, it is desirable to have as many links as possible. However, since each link requires an affiliated STA within the MLD, the number of STAs increases with the number of links. This makes the chipset more spacious, more expensive, and / or more power-hungry than a single STA chipset, which is particularly problematic for user non-access point (non-AP) MLD devices.

[0003] The "background" description provided herein is for the purpose of generally presenting the context of the present disclosure. The work performed by the presently designated inventors described in this background section, and aspects that may not qualify as prior art at the time of filing, are not admitted, either explicitly or implicitly, to be prior art to the present disclosure. Summary of the invention

[0004] The object of the present invention is to provide a multi-link device that requires less power and has less complexity than conventional multi-link devices, especially in scenarios where control information is exchanged between multi-link devices. Another object is to provide a corresponding method and a corresponding computer program for implementing the method and a non-transitory computer-readable recording medium for implementing the method.

[0005] According to one aspect, there is provided a first multi-link device, comprising:

[0006] - a first station comprising a transmitter and a receiver and configured to communicate with a first station of a second multi-link device on a first link;

[0007] a second station comprising a receiver but not a transmitter and configured to receive control information from another first station of a second multilink device on a second link different from the first link and / or from another communication device; and

[0008] - a circuit configured to control the first station and the second station,

[0009] The second site is configured to provide the received control information to the circuit and / or the first site.

[0010] According to another aspect, there is provided a multi-link method, comprising:

[0011] - communicating with a first station of a second multi-link device on a first link via a first station comprising a transmitter and a receiver;

[0012] - receiving control information from another first station of a second multilink device on a second link different from the first link and / or from another communication device by a second station comprising a receiver but not a transmitter;

[0013] - controlling the first station and the second station by means of a circuit; and

[0014] - providing the received control information to the circuit and / or the first station.

[0015] According to further aspects, a corresponding method is provided, a computer program comprising program means for causing a computer to perform the steps of the method disclosed herein when the computer program is executed on a computer, and a non-transitory computer-readable recording medium having a computer program product stored therein, which, when executed by a processor, causes the method disclosed herein to be performed.

[0016] Implementations are defined in the dependent claims. It should be understood that the disclosed method, the disclosed computer program, and the disclosed computer-readable recording medium have further implementations similar and / or identical to the claimed apparatus and defined in the dependent claims and / or disclosed herein.

[0017] One aspect of the present disclosure is a receiving STA (referred to herein as a "second station" or "Rx STA") included within an MLD (also referred to herein as a "first multi-link device" or "non-AP MLD"), i.e., a STA that can only receive and not transmit. The receiving STA can operate at significantly lower power and have lower complexity than a regular STA. The receiving STA can assist the MLD in receiving control information. Further, a link to the receiving STA can be set up, and regular STAs of the same MLD can be caused to switch their channels in an advantageous manner using the receiving STA.

[0018] In this context, it should be noted that "control information" should be broadly understood as any kind of information useful for control and / or management, i.e., it may include not only any control data, but also management data. For example, information carried in control frames and / or management frames (especially control frames and / or management frames that do not require a response) according to, for example, IEEE802.11, should also be understood as control information.

[0019] The foregoing paragraphs have been provided by way of general introduction and are not intended to limit the scope of the appended claims.The described embodiments, together with other advantages, will be best understood by reference to the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] A more complete appreciation of the present disclosure and its many attendant advantages will be readily obtained as the present disclosure becomes better understood by reference to the following detailed description when considered in conjunction with the accompanying drawings, wherein:

[0021] Figure 1 A schematic diagram illustrating conventional MLD operating on two links is shown.

[0022] Figure 2 A schematic diagram of the control plane of MLD is shown.

[0023] FIG. 3 is a schematic diagram showing an embodiment of an AP MLD and a non-AP MLD according to the present disclosure.

[0024] FIG. 4 illustrates an embodiment of a non-AP MLD according to the present disclosure.

[0025] Figure 5 A flow chart of the setup phase as seen from a non-AP MLD according to the present disclosure is shown.

[0026] Figure 6 A schematic diagram showing an exemplary MLD setting between an AP MLD and a non-AP MLD according to the present disclosure.

[0027] Figure 7 It explains Figure 6 FIG. 1 is a diagram showing frame exchange between an AP MLD and a non-AP MLD.

[0028] Figure 8 A diagram showing acknowledgement timeout under the assumption of non-zero receive state propagation delay is shown.

[0029] Fig. 9 is another diagram illustrating acknowledgement timeout under the assumption of non-zero receive state propagation delay.

[0030] Fig.10 is a diagram illustrating another option for minimizing the time until a response is confirmed.

[0031] Fig.11 is a diagram illustrating a situation where the AP STA waits for the reception state to be delivered.

[0032] Fig.12 is a diagram illustrating a case where the AP STA continues to access the link despite a reception state in which the initial transmission has not been received.

[0033] Fig.13 is a schematic diagram illustrating another exemplary MLD setting between an AP MLD and a non-AP MLD according to the present disclosure.

[0034] Fig.14 is a diagram illustrating how a data receiving Rx STA can facilitate low-latency data transfer.

[0035] Fig.15 A schematic diagram of an exemplary MLD arrangement is shown, wherein the flow of control information is illustrated.

[0036] Fig.16 is a diagram illustrating extraction of parameters from a conventional header of a received PPDU.

[0037] Fig.17 Link state information detection by observing channel energy and / or preamble detection is shown.

[0038] Fig.18 is a diagram illustrating link switching based on Rx STA link state information.

[0039] FIG. 19 is a diagram illustrating enhanced single radio operation using Rx STA. DETAILED DESCRIPTION

[0040] Referring now to the drawings, wherein like reference numerals designate identical or corresponding parts throughout the several views, Figure 1 A schematic diagram illustrating two multi-link devices (MLDs) 10, 20 operating on two links (multi-link operation, MLO) is shown. The MLD includes multiple attached STAs (stations), AP STAs (access point STAs) 11, 12 or non-AP STAs 21, 22. Each STA includes a transmitter and a receiver PHY (physical layer) to achieve time division duplex (TDD) and bidirectional data exchange in the lower medium access control (MAC) sublayer. Within the MLD, the upper MAC sublayer 13, 23 converges the data flows of the two links. Typically, as Figure 1 As shown, each STA operates on a different channel, thereby creating a bidirectional link between each AP STA 11, 12 and non-AP STA 21, 22. Depending on the capabilities of the AP MLD 10 and the non-AP MLD 20, communications on the different links may occur simultaneously or at different times. Figure 1 Also shown is a non-MLD non-AP STA 30 that may be connected to the AP MLD 10 over a single link via the AP STA 11. The non-AP STA 31 and the upper MAC layer 33 for the non-MLD 30 are often combined and referred to as a non-AP STA.

[0041] In MLD, each dependent STA generally operates independently in terms of PHY and low-layer MAC processing. However, the upper-layer MAC processing is shared between the two STAs. Figure 2A schematic diagram of the control plane of the MLD is shown. Each STA 11, 12, 21, 22, 31 is characterized by a control unit 14, 15, 24, 25, 36 that controls the STA, the lower layer and the upper MAC sublayer 13, 23, 33. In addition, the MLD is characterized by an SME (Station Management Entity) 16, 26, 36 (or a central control unit) that controls the control unit of each attached STA. The SME performs its control tasks so that the upper MAC sublayer performs appropriate operations. The SME can also perform other tasks that are not related to the PHY and MAC but are higher layers.

[0042] Generally, it is desirable to have as many links as possible to reduce channel access latency (i.e., the first idle link can be used for data exchange), enhance throughput (i.e., the throughput of each link is accumulated) and enhance availability (i.e., with multiple links, the probability of them being idle increases). However, since each link requires an affiliated STA within the MLD, the number of STAs increases with the number of links. This makes the chipset more bulky, more expensive and / or more power-hungry than a single STA chipset, which is particularly problematic for user non-access point (non-AP) MLD devices.

[0043] The reason for these problems is that each STA is a regular STA and supports all features such as transmission and reception of various frames at various rates, bandwidths and streams. These features are always supported regardless of whether they are currently used. These features can be temporarily disabled by power saving techniques; however, they still exist and are deployed, and disabled features have no functionality when in power saving mode.

[0044] In addition, link switching (i.e., STA changes from the first link to the second link) generates overhead and requires STA to observe the wireless medium for a certain time span before being able to access the channel (also referred to as the minimum observation period in this article). In addition, if the STA is an AP STA, it needs to notify its associated STAs about the link switching in advance or disassociate these STAs. Therefore, link switching is not an option to reduce channel access latency. In addition, the link state ("busy" or "idle") of the link to which the STA plans to switch is unclear before the switching operation. Therefore, the STA may switch to a second link with more unfavorable conditions than the first link.

[0045] According to the present disclosure, Rx STA is provided as part of MLD. Rx STA is a receive-only STA, i.e., it cannot transmit but only receive. In order to further save power, the receiving capability can be optionally limited in the sense that the supported PHY configuration and / or MAC frame is very sparse. Rx STA is typically a low-complexity, low-power STA. Therefore, the deployment of Rx STA has less implementation burden than conventional STA. On the contrary, the gain achieved by Rx STA is lower than that of conventional STA, but still significant.

[0046] Figure 3A is a schematic diagram illustrating an embodiment of an AP MLD 40 according to the present disclosure, and Figure 3B 1 is a schematic diagram illustrating an embodiment of a non-AP MLD 50 according to the present disclosure. Each of the MLDs 40 and 50 (also referred to herein as a "first multi-link device" or a "first MLD") includes one or more (regular) STAs 41, 51 (having both transmission and reception functions; also referred to herein as "first STA") and at least one (subordinate) Rx STA 42, 52 (having only reception functions; also referred to herein as "second STA"). Figure 1 and Figure 2 As shown, upper MAC sublayers 43, 53 may also be provided. The Rx STA cannot exist alone, i.e., not as part of the MLD, because the lost transmission function is essential for communication even if only data or other information is received, as will be explained below. The Rx STA may be part of an AP MLD or a non-AP MLD, wherein the Rx STA may be more conducive to the non-AP MLD where power saving and cost are most important. The Rx STA is generally capable of providing control information and / or data to the MLD. Therefore, the connection C1 shown in FIG. 3 showing the data flow may be present or not, and in particular, it only exists when the Rx STA provides data to the MLD.

[0047] FIG4 shows an embodiment of the non-AP MLD 50A, 50B in more detail. Figure 2 As shown, control units 54, 55 and SME 56 are also provided (one or more elements 53-56 are also referred to as "circuitry" in this document). It should be noted that in some embodiments, in particular, the signal processing block "upper MAC layer" marked as 43, 53, 63 in the figure can be regarded as part of the circuit mentioned in this document.

[0048] Figure 4AThe case where the Rx STA 52 provides control information to the MLD via connection C3 is shown. The purpose of connection C3 in the direction to the Rx STA 52 is mainly to configure the receiver of the Rx STA (e.g., to configure the channel (i.e., link) to be observed), and the main purpose of connection C3 in the direction to the control unit 55 is to provide control information to the SME 56 and / or the control unit 54 and / or the upper MAC sublayer 53. Connection C2 may or may not exist, in which case the upper MAC sublayer 53 is controlled via the SME 56 and the control unit 54.

[0049] Figure 4B The case where Rx STA52 provides data to the MLD is shown. Control information exchanged via connection C5 is provided for configuring the Rx STA's receiver (to Rx STA52) and receiving notifications (from Rx STA52). As for connection C2, connection C4 may or may not exist. In general, connection C4 may be required to control the upper MAC sublayer 53 to insert received data into the data stream. As will be explained below, a control link (e.g., via the upper MAC sublayer 53 or SME62) from Rx STA52 to non-AP STA51 and vice versa may be important for operation. Even a direct link (in Figure 4B 1 . One (not necessarily the only) purpose of the control link from Rx STA52 to non-AP STA51 (whether routed via upper MAC sublayer / SME or directly) is to deliver an acknowledgment for received data units by Rx STA52, and / or to relay data or control information to the AP MLD (second MLD), as described in more detail below.

[0050] Hereinafter, a case where the Rx STA provides received data to the MLD as provided according to the first aspect of the present disclosure will be discussed. Figure 5 A flow chart of the setup phase 100 as seen from a non-AP MLD for the case where the Rx STA should receive data is shown. The setup phase 100 may have four sub-phases: a discovery phase 101, an association phase 102, an agreement phase 103, and a communication phase 104. For the case where the Rx STA should only receive control information (discussed later), some cases require the first two sub-phases (discovery and association) of the setup phase 100 to be performed. Sometimes, the agreement 103 may also be used to, for example, agree on encryption parameters or observe links for EMLSR operation.

[0051] During the discovery phase 101, any subordinate non-AP STA of a non-AP MLD may collect information about the configuration of the AP MLD (step 101A). The non-AP MLD may control the subordinate Rx STA so that it can receive data from a link provided by the AP MLD that is not provided by the subordinate non-AP STA of the same non-AP MLD (step 101B).

[0052] In the subsequent association phase 102, the non-AP STA attached to the non-AP MLD announces the presence of the Rx STA and optionally its parameters and / or capabilities, such as channels, bandwidth, supported PHY and MAC configurations. Depending on the implementation of the Rx STA, it may frequently change its observed channel. In this case, the non-AP STA should include a channel schedule according to which the Rx STAs attached to the same non-AP MLD change their observed channels.

[0053] After the association phase 102, the non-AP STA attached to the non-AP MLD may participate in establishing or establishing an agreement with its peer AP MLD in the agreement phase 103. These agreements may specifically include one or more of the following:

[0054] - Block Acknowledgement (BAck) protocol, which configures the use of BAck (e.g., scoreboard size). (When an Rx STA receives in the downlink, the BAck for the Rx STA

[0055] The agreement was initiated by AP MLD).

[0056] - Four-way handshake to exchange encryption parameters to achieve secure communication between non-AP and AP MLD. When Rx STA receives in downlink, the four-way handshake of Rx STA is initiated by AP MLD.

[0057] - TID (Traffic Identifier)-Link Mapping Request / Response which can be initiated by AP MLD or non-AP MLD.

[0058] By default, all agreements hold for the link to the Rx STA as well. Optionally, different parameters may apply to the link towards the Rx STA, in which case a non-AP STA attached to the same non-AP MLD sets up a separate agreement with its peer AP MLD for that link.

[0059] Since the setup phase 100 requires data transmission (eg, for association), the Rx STA cannot exist alone, but requires at least one regular STA, and the two are interconnected within the MLD.

[0060] Figure 6A schematic diagram of an exemplary MLD setup between an AP MLD 60 (also referred to herein as a "second multi-link device" or "second MLD") and a non-AP MLD 50 ("first MLD") is shown. The AP MLD includes two AP STAs 61 and 62 (i.e., first stations with transmission and reception functions) and an upper MAC sublayer 63. Two links are set up: Link 1 between the AP STA 61 and the non-AP STA 51, and Link 2 from the AP STA 62 to the Rx STA 52, and both STAs 51 and 52 are attached to the same non-AP MLD 50.

[0061] Since Rx STA52 includes only a receiver, it cannot transmit Ack or BAck to the transmitter in response to one or more data units. Therefore, the data unit transmitted to Rx STA52 will not request an acknowledgment or cause an acknowledgment (e.g., Back) to be transmitted via another link to AP STA61 of the same MLD60 to which the transmitting AP STA62 is attached. Such an acknowledgment may include not only an acknowledgment of the data unit transmitted to Rx STA52, but also an acknowledgment of the data unit transmitted to one or more non-AP STA51 attached to the same non-AP STA50.

[0062] If a protocol for acknowledgement (e.g., BAck protocol) has been previously set up for the TID and the TID is mapped to a receive-only link and is mapped to at least one link provided by a non-AP STA51 that is affiliated with the same non-AP MLD50 as the Rx STA52, then the AP STA62 transmitting a data unit for a specific TID will only transmit to the Rx STA52. This includes: the sequence number used to identify the data unit from the same TID originates from the same sequence number space for the link to the Rx STA52 and one or more links to the non-AP STA51. Acknowledgements for data units transmitted to the Rx STA52 can only be delivered via the link for which the TID of the data unit is enabled.

[0063] Figure 7 Yes Description Figure 6Schematic diagram of frame exchange between AP MLD60 and non-AP MLD50 shown. In this example, it is assumed that AP STA2 (62) transmits data units #2 and #3 to Rx STA52 and requests Ack for both. After receiving the two data units, the reception status is forwarded to non-AP STA1 (51) to be included in the next BAck transmitted to AP MLD60. In this example, it is assumed that non-AP STA1 (51) transmits the next BAck B1 in response to the reception of data units #4 and #5. Non-AP STA1 (51) can also provide BAck status based on the BAck requested by AP STA1 (61). Thus, BAck B1 includes the reception status of data units #2 to #5. Therefore, it is assumed that data units #2 to #5 originate from the same TID. However, they can also originate from different TIDs, in which case BAck B1 maintains the reception status of multiple TIDs. At AP MLD 60, the reception status of data units #2 and #3 is forwarded to AP STA2 (62) for further consideration, such as retransmission. The last step is optional because APMLD 60 may decide to retransmit data units #2 and #3 via link 1, for example.

[0064] It may take some time for the reception status of Rx STA52 to propagate to the AP STA62 that transmits the data unit. To this end, the following method may be applied: a STA that transmits one or more data units requiring a response to Rx STA52 should assume that the data unit arrives at Rx STA52 no earlier than the first BAck that arrives from the same MLD50 of Rx STA52, which indicates that the data unit has not arrived, or that such information does not exist. The reception status of the data unit to Rx STA52 should be included in the next BAck B1 transmitted to the MLD50 to which the peer STA51 of Rx STA52 is attached.

[0065] In this context, it should be noted that the term "first BAck" or "next BAck" should be interpreted as the first or next acknowledgment (e.g., Back) after the end of the PPDU holding the data unit, and the receive status propagation delay may be included to account for the processing delay. If present, the receive status propagation delay is indicated during the setup phase. Further, it should be noted that Back can be considered as a single acknowledgment including multiple acknowledgments.

[0066] Figure 8 and Fig. 9 is a diagram illustrating BAck timeout under the assumption of non-zero receive state propagation delay. Figure 8In , the first BAck B2 after holding the PPDU of data units #2 and #3 is well after the reception status propagation delay, so the first BAck B2 can contain the reception status of these data units. Fig. 9 In the example, the first BAck B3 after holding the PPDU of the data units #2 and #3 starts transmission before the reception status propagation delay ends. Thus, the reception status of the data units #2 and #3 may be included in the second BAck B4 transmitted by the attached non-AP STA51.

[0067] AP MLD50 may request BAck to solicit BAck response to minimize BAck timeout. Alternatively, non-APSTA60 may actively (ie, without request) transmit BAck. Thus, after Rx STA52 receives the data unit, non-APSTA51 may contend for channel access to transmit BAck.

[0068] Fig.10 is a diagram illustrating another option for minimizing the time until the BAck response requires the reception status propagation delay to be known at AP STA61. In such a case, AP STA61 may include padding ("PAD") after the last data unit or add additional data units (e.g., data units of other TIDs) to the PPDU. By extending the PPDU beyond the reception status propagation delay, the BAck B5 transmitted in response to the extended PPDU may already include the reception status of the data unit received by RxSTA52.

[0069] Any STA operating in the unlicensed band shall perform Listen Before Talk (LBT), which is parameterized by the Contention Window (CW) value. When a STA receives a data unit to be transmitted, it extracts a random backoff counter in the interval [0, CW]. The CW is selected based on the status of the previous transmission: if the previous transmission was successful, i.e., a response to the transmission has been received, then keep CW = CW min , otherwise for example by transmitting a CW in response to each successive non-received new =2·CW old +1, CW increments, i.e., CW is approximately doubled. CW values ​​are typically dedicated to a specific access category (AC) queue to distinguish different priorities of data units (e.g., voice, video, best effort service, and background). CW values ​​are managed (e.g., increased, initialized) on a per-AC basis.

[0070] An AP STA of the AP MLD (transmitting a data unit (e.g., BAck) that requires a response frame and which is transmitted on a link toward the Rx STA) shall not transmit until the AP MLD receives a related response from a non-AP STA of the same non-AP MLD to which the Rx STA is attached via another link, or shall increment its CW for the upcoming transmission, unless the APMLD receives a response from a non-AP STA attached to the same MLD as the Rx STA via another link, in which case CW=CW is maintained. min .

[0071] The exemplary implementation provides that the CW value addressed here is valid only for transmissions towards the Rx STA, and can be further differentiated for each AC. This is advantageous because the response frame may be delayed due to the busy link carrying the BAck. In the case of using a regular CW, traffic to other regular STAs will be unnecessarily penalized.

[0072] Fig.11 1 is a diagram illustrating a situation where the AP STA 62 waits for the reception status delivered via the link 1 before resuming contention after the initial transmission. The random backoff interval is always CW. min Parameterization. Depending on implementation options, the "wait to receive state" phase cannot hold transmissions to regular STAs and / or Rx STAs using different ACs.

[0073] If the AP STA is characterized by a FIFO ordered transmission queue, there are two options for implementing the "wait to receive state" stage: According to the first option, the AP STA checks the destination of the first data unit in its queue. If the destination is an Rx STA, the response is outstanding, and the BAck timeout has not passed, it does not start the backoff process, otherwise it starts the backoff process. According to the second option, the AP STA first starts the backoff, but checks the destination STA of the first data unit in the queue. If the destination is an Rx STA and the response is outstanding, it stops the backoff process and continues the backoff process once a response is received or a BAck timeout occurs.

[0074] Fig.12 1 is a diagram illustrating a situation where AP STA2 (62) continues to access link 2 despite not receiving the initial transmission through link 1. As shown in the figure, using 2CW min +1 parameterizes the random backoff interval for the second transmission, since the reception status of the initial transmission is still unknown to AP STA62. Once the reception status reaches the subordinate AP STA61, which has already started the backoff for the upcoming transmission, it can shorten the backoff, or reinitialize the backoff, or continue to use the previous backoff.

[0075] When BAck is transmitted, the BAck transmitted by non-AP STA51 does not contain the reception status of data units #6 and #7 because these data units have not been received yet. Therefore, the third transmission by AP STA62 is a case of concern because at the initiation time point, the reception status of data units #2 and #3 is clear, while the reception status of data units #6 and #7 is not. In this case, there are three options for initialization of CW values:

[0076] - Initialize with CWmin (eg Fig.12 shown);

[0077] - Initialize with previous CW, i.e. keep CW as it is (this will be 2CW min +1); and

[0078] - Initialize with increased CW (this will be 4CW min +3).

[0079] The last option corresponds to a failed transmission or no reception state is available (although a partial reception state is available). Therefore, the first and second options are more feasible. According to the implementation options, the CW increase may not be maintained for transmissions to regular STAs and / or Rx STAs using different ACs.

[0080] Fig.13 A schematic diagram showing another exemplary MLD arrangement between an AP MLD 60 and a non-AP MLD 50 is shown. Fig.14 is a diagram illustrating how data receiving Rx STA52 can contribute to low-latency data delivery. Link 1 is detected as being busy for a long time. Since Rx STA52 can receive data on Link 2, which is assumed to be idle, AP MLD60 can easily send delay-sensitive data units to non-AP MLD50. Acknowledgements for these data units will arrive at a later point in time via Link 1. However, if received correctly, the data units at non-AP MLD50 can be easily processed by the application layer, although the reception status at AP MLD60 is unknown.

[0081] Hereinafter, a case where the Rx STA provides control information to the non-AP MLD as provided in accordance with the second aspect of the present disclosure will be discussed. In the previous case according to the first aspect, the reception status of the data unit received by the Rx STA can be regarded as control information forwarded from the Rx STA to its non-AP MLD. In contrast, according to the second aspect, control information obtained by the Rx STA through monitoring the medium and not related to the data frame directed to the Rx STA is used. Such control information is often included in a control frame or a management frame (directed or not directed to the Rx STA) or any PPDU directed to other STAs. In this variant, no data frame is directed to the Rx STA as unicast, but the control frame (or management frame) can be directed to the Rx STA. As described above, in this case, it can be executed Figure 5 The first two or even three stages (discovery and association).

[0082] Fig.15 The AP MLD 60 (eg, Figure 6 As shown, with Figure 2 The additional elements 64-66 provided in the AP MLD 10 shown are different from the non-AP MLD 50 (e.g., Figure 4A and Figure 4B ) between non-AP MLD50 and AP MLD60, wherein the flow of control information is shown. There are two sub-variants: In the first sub-variant, the control information retrieved by Rx STA52 is used within the same MLD. The main control flow of this case is shown with a solid thick arrow. In the second sub-variant, the control information retrieved by RxSTA52 is forwarded by MLD to AP MLD60 via non-AP STA51 and AP STA61. The control information can be used in different environments within AP MLD60, for example, channel busy information or OBSS information can trigger AP MLD60 to switch its link to a different channel. The information flow of the second sub-variant includes solid and dotted thick arrows. Although the control information within non-AP MLD50 can be forwarded with a small delay, the forwarding to AP MLD60 may take time due to the channel access delay. Therefore, the average value of the observed parameter is appropriate in the latter case, while the instantaneous value can also be forwarded in the former case.

[0083] The control information that the Rx STA 52 may obtain and that is provided to at least its affiliated non-AP MLD 50 may include:

[0084] a) Link state information or link information about one or more of the length of the currently received PPDU, the bandwidth of the received PPDU, the TXOP duration or NAV, the received power, the BSS identifier (BSS color) of the currently received PPDU, and the restricted channel (puncturing) information of the currently received PPDU. These parameters can be obtained from e.g. Fig.16 The received conventional header of the PPDU shown is either extracted from a received control frame such as RTS or CTS.

[0085] b) Link status information or link information about the current busy / idle state of the observed channel (CCA - Carrier Clearance Assessment). This indication can be obtained by Fig.17 The energy of the observed channel shown and / or the (WLAN) preamble detection may be derived. There may be small deviations between the received power and the CCA.

[0086] c) Channel state information about the impulse response and / or transfer function between the transmitter and the Rx STA determined from the received PPDU (usually a Null Data Packet NDP).

[0087] d) Operational advice information regarding reception of control frames used to configure or reconfigure non-AP MLD operation.

[0088] The information listed above can be used for different purposes. Assume that the non-AP MLD 50 is about to transmit data to the AP MLD 60. The control information of the Rx STA 52 can assist the non-AP STA 51 in this task. In particular, the Rx STA 52 can perform one or more of the following operations:

[0089] i. Control the non-AP STA to turn to an idle link. This turn can be temporary (i.e., used to implement one or more frame exchanges with the peer MLD) or quasi-permanent (i.e., lasting for a longer period of time). Information a) and / or b) can help the non-AP MLD make decisions.

[0090] ii. Perform CW countdown for non-AP STA to transmit after CW countdown. Thus, Rx STA observes CCA (information b), while non-AP STA is switching to Rx

[0091] The link observed by the STA may take some switching delay. In order to correctly obtain CCA

[0092] Information, the bandwidth of Rx STA and non-AP STA must be the same or at least cover the CW

[0093] The primary (e.g., 20 MHz) channel of the link being counted down.

[0094] iii. Enable non-AP STAs to switch their links without or with a reduced medium synchronization delay timer. In multi-link (ML) operation, when a non-AP STA wants to use a different link that was not observed before or cannot be observed, it should consider the timeout before transmitting anything. This is for non-AP STAs to collect information about the link medium (e.g., NAV). In the case where the Rx STA has been continuously observing the medium, the information collection is outdated, and therefore the non-AP STA can transmit immediately (i.e., ignoring the medium synchronization delay) or after a shorter observation period (i.e., shorter medium synchronization delay). Information a) and / or b) can be used for this operation. If the AP MLD initiates link switching via a trigger frame (e.g., a MU-RTS trigger frame), the trigger frame should be configured so that the non-AP MLD should perform carrier sensing before accessing the medium.

[0095] The previous three application examples are Fig.18 It is shown in Fig.18 is a schematic diagram illustrating link switching based on Rx STA link status information. It is assumed here that non-AP MLD50 wants to transmit data, but link 1 is busy. Based on the link status information obtained by Rx STA52, non-AP STA51 of non-AP MLD50 can switch to link 2 to perform frame exchange with AP MLD60. If Rx STA52 can perform CW countdown, the link switching delay of non-AP STA51 may have been used for CW countdown; therefore, frame exchange can start earlier. When non-AP STA51 transmits on link 2, Rx STA52 can observe link 1 to avoid or reduce the medium synchronization delay timer.

[0096] Since the AP MLD60 may start downlink data transmission via link 1 when it expects the non-AP STA51 to receive or respond instead of the Rx STA52, the non-AP MLD51 should immediately notify the APMLD60 of its link switch via a link switch announcement. This may be done before the actual link switch if the original link is accessible and served by the non-AP STA51, or after the actual link switch if the original link is not accessible or observed by the Rx STA52. In the latter case, the non-AP STA51 may include the link switch announcement as the first data unit, or in the first data unit transmitted after the link switch. The link switch announcement may include a time span indicating the length of the link switch, and after this time span the link switch is reversed.

[0097] The control information obtained by the Rx STA 52 may also assist in the transmission of downlink traffic. Thus, assuming that the AP MLD 60 is about to transmit data to the non-AP MLD 50. The Rx STA 52 may perform one or more of the following operations:

[0098] i. Provides the measured impulse response or transfer function of the channel observed by the Rx STA. This channel state information or beamforming information derived therefrom may then be fed back to the peer MLD via the non-APSTA. The peer STA of the Rx STA may then apply beamforming to the link to the Rx STA. This operation may be applied if the Rx STA also receives data units. The above-mentioned information c) and Fig.15 The information forwarding (dashed arrows) shown in can be used for this operation.

[0099] ii. Controlling the resources of an Enhanced Single Radio (EMLSR) non-AP STA. In EMLSR, a control frame received from an AP MLD indicates to which link a non-AP STA should switch or focus its resources to subsequently perform data exchange. For the reception of such a frame, the EMLSR operation foresees segmenting the reception resources of the non-AP STA, which is not necessary when an Rx STA is present. FIG. 19 is a diagram illustrating the EMLSR operation using an Rx STA. Fig.19A shows the initial state before link switching, and Fig.19B and Fig.19C Two options for link switching are shown.

[0100] like Fig.19A As shown, one link is observed by the non-AP STA 51, and the other link is observed by the Rx STA 52. When the Rx STA 52 receives the EMLSR control frame (switching request frame), it causes the non-AP STA 51 to switch its link to the link observed by the Rx STA 52. Then, the Rx STA 52 can switch to the link of the non-AP STA 51 observed before to obtain link status information, thereby avoiding the medium synchronization delay of the non-AP STA when switching back ( Fig.19B ), or the Rx STA52 can disable its radio ( Fig.19C ). The above-mentioned information d) can be used for this operation. Since the link switching is different from the baseline EMLSR, the switching delay of this operation may also be different. In addition, when the switching request frame is transmitted on link 1 in the setting of Figure 19, since the non-APSTA51 has been tuned to link 1, the switching delay is zero. For the same reason, a switching request is actually not required on link 1.

[0101] In order for the AP MLD 60 to know the Rx STA 52 or the EMLSR operation with the Rx STA 52, it should be performed in the previous setup phase. Figure 5 At least the first two stages (discovery and association) shown in .

[0102] In summary, according to the present disclosure, one or more receiving STAs may be included in the MLD, i.e., one or more STAs that can only receive but not transmit. Compared to conventional STAs, receiving STAs can operate at significantly lower power and have lower complexity. The receiving STA can assist the MLD in receiving data and / or control information. Further, the present disclosure describes how a link to a receiving-only STA can be set up, how a response frame such as an acknowledgment can be transmitted, and how a listen-before-talk mechanism can be enhanced. In addition, it is described how to obtain control information through the receiving STA and how to apply the control information in various contexts.

[0103] Therefore, the above discussion only discloses and describes exemplary embodiments of the present disclosure. As will be appreciated by those skilled in the art, the present disclosure may be embodied in other specific forms without departing from the spirit or essential features of the present disclosure. Therefore, the disclosure of the present disclosure is intended to be illustrative, rather than limiting, the scope of the present disclosure and other claims. The present disclosure (including any readily discernible variations of the teachings herein) partially defines the scope of the aforementioned claim terms so that no inventive subject matter is dedicated to the public.

[0104] In the claims, the word "comprising" does not exclude other elements or steps and the indefinite article "a" or "an" does not exclude a plurality. A single element or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

[0105] To the extent that the embodiments of the present disclosure are described as being implemented at least in part by a data processing apparatus controlled by software, it should be understood that non-transitory machine-readable media carrying such software, such as optical disks, magnetic disks, semiconductor memories, etc., are also considered to embody embodiments of the present disclosure. Further, such software may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems.

[0106] The elements of the disclosed devices, apparatuses and systems may be implemented by corresponding hardware and / or software elements (e.g., appropriate circuits or circuits). A circuit is a structural assembly of electronic components including conventional circuit elements, integrated circuits including application specific integrated circuits, standard integrated circuits, application specific standard products, and field programmable gate arrays. In addition, the circuit includes a central processing unit, a graphics processing unit, and a microprocessor that are programmed or configured according to software code. The circuit does not include pure software, although the circuit includes the hardware that executes the software as described above. The circuit or circuit may be implemented by a single device or unit or multiple devices or units, or a chipset or processor.

[0107] It follows a list of further embodiments of the disclosed subject matter:

[0108] 1. A first multi-link device, comprising:

[0109] - a first station comprising a transmitter and a receiver and configured to communicate with a first station of a second multi-link device on a first link;

[0110] a second station comprising a receiver but not a transmitter and configured to receive control information from another first station of a second multilink device on a second link different from the first link and / or from another communication device; and

[0111] - a circuit configured to control the first station and the second station,

[0112] The second site is configured to provide the received control information to the circuit and / or the first site.

[0113] 2. The first multi-link device defined in embodiment 1,

[0114] The first station is configured to transmit the control information received by the second station or the pre-processed control information, and provide the control information to the first station of the second multi-link device and / or another communication device.

[0115] 3. A first multi-link device as defined in any one of the preceding embodiments,

[0116] The control information includes one or more of the following:

[0117] - link information indicating one or more of a length of a received data unit, a bandwidth of a received data unit, a transmission opportunity duration, a network allocation vector (NAV), a received power, a basic service set (BSS) identifier of the received data unit, restricted channel information of the received data unit, and status information indicating a busy or idle state of the second link;

[0118] - channel state information indicating an impulse response and / or a transfer function between the second station and the second multi-link device and / or another communication device; and

[0119] - Operation suggestion information indicating reception of control information for configuring or reconfiguring the operation of the first multi-link device.

[0120] 4. A first multi-link device as defined in any one of the preceding embodiments,

[0121] The second station is configured to use the one or more pieces of control information for one or more of the following:

[0122] -control the first station to switch to an idle link;

[0123] -control the first station to switch to another link;

[0124] - Control itself to turn to other links to receive control information from another communication device; and

[0125] - Performing a Contention Window (CW) countdown for the first station to transmit after the CW countdown.

[0126] 5. A first multi-link device as defined in any one of the preceding embodiments,

[0127] wherein the first station is configured to observe a minimum observation period before transmitting after a link switching operation, and

[0128] The circuit is configured to: if there is control information from the second station that has obtained the control information of the link to which the first station switches, control the first station to reduce or ignore the minimum observation period.

[0129] 6. The first multi-link device as defined in embodiment 4,

[0130] The first station is configured to switch the link used for communication with the second multi-link device and / or another communication device, and transmit a link switch announcement to the second multi-link device and / or another communication device, wherein the link switch announcement includes a link switch timing indicating the time and / or duration of the link switch operation.

[0131] 7. A first multi-link device as defined in any one of the preceding embodiments,

[0132] Therein, the second station is configured to receive an Enhanced Multi-Link Single Radio (EMLSR) control frame from the second multi-link device and is configured to control the link to which the first station switches or focuses its resources for an upcoming frame exchange with the second multi-link device.

[0133] 8. The first multi-link device as defined in embodiment 7,

[0134] Wherein, depending on whether the link indicated by the EMLSR control frame is the first link or the second link, the EMLSR link switching delay is different; and / or

[0135] As part of the setup, the EMLSR delay is signaled by the first multi-link device to the second multi-link device.

[0136] 9. The first multi-link device as defined in any one of the preceding embodiments,

[0137] The first station is configured to collect configuration information from the second multi-link device, and

[0138] The circuit is configured to configure the second station to receive control information from a link provided by the second multi-link device and not used by the first station based on the collected configuration information.

[0139] 10. A first multi-link device as defined in any one of the preceding embodiments,

[0140] The first site is configured as:

[0141] - announcing the existence of the second station and its parameters and capabilities to the second multilink device, and

[0142] - Participating in establishing or establishing an agreement or notification parameter with the second multi-link device for one or more of control information signaling, encryption parameters, and EMLSR switching delay.

[0143] 11. The first multi-link device as defined in embodiment 10,

[0144] wherein the agreement is valid for a second link to a second site of the first multi-link device, and / or

[0145] The protocol may be the same as the protocol on the first link, or may be set separately for the second link.

[0146] 12. A first multi-link device according to any one of the preceding embodiments,

[0147] Therein, the second station obtains control information from a control frame transmitted in a physical layer data unit to which only conventional modulation and coding is applied.

[0148] 13. A first multi-link device according to any one of the preceding embodiments,

[0149] wherein the control information received by the second station is embedded in a physical layer data unit, the physical layer data unit is segmented into a first part to which conventional modulation and coding is applied and a second part to which advanced modulation and coding is applied, and

[0150] The second station is configured to decode and demodulate only the first part of the physical layer data unit to obtain the control information.

[0151] 14. The first multi-link device as defined in embodiment 13,

[0152] Wherein, the second station is configured to suspend reception after a first portion of the physical layer data unit and to continue reception once the physical layer data unit ends.

[0153] 15. The first multi-link device as defined in embodiment 14,

[0154] wherein the point in time at which reception is suspended depends on the format of the detected physical layer data unit, and / or wherein the point in time at which reception is continued depends on a length signaled in the first part of the physical layer data unit.

[0155] 16. A first multi-link device according to any one of the preceding embodiments,

[0156] Therein, the second station is configured to support reception of a physical layer data unit that is modulated and encoded using conventional modulation and coding and / or a modulation and coding scheme of a basic rate set.

[0157] 17. A first multi-link device according to any one of the preceding embodiments,

[0158] The second station is configured to support reception of a physical layer data unit that applies a non-high throughput (non-HT) or non-HT duplicate transmission format.

[0159] 18. The first multi-link device as defined in any one of the preceding embodiments, comprising:

[0160] - one or more first stations, each configured to communicate with one or more first stations of other multi-link devices and / or other communication devices on different links; and

[0161] - one or more second stations, each configured to receive data from one or more first stations of other multi-link devices and / or other communication devices on a link different from the link used by a first station of the first multi-link device.

[0162] 19. A first multi-link device according to any one of the preceding embodiments,

[0163] The first station is configured to communicate with the first station of the second multi-link device and / or with the station of the single link device using the link.

[0164] 20. A first multi-link device according to any one of the preceding embodiments,

[0165] The first multi-link device is configured to operate as a non-access point station (non-AP STA) or as an access point (AP).

[0166] 21. A first multi-link device according to any one of the preceding embodiments,

[0167] The circuit includes a control circuit, a medium access control (MAC) layer and / or a station management entity (SME).

[0168] 22. A first multi-link device according to any one of the preceding embodiments,

[0169] The second site is connected to the first site via the circuit or directly connected to the first site.

[0170] 23. A multi-link method of a first multi-link device, comprising:

[0171] - communicating with a first station of a second multi-link device on a first link via a first station comprising a transmitter and a receiver;

[0172] - receiving control information from another first station of a second multilink device on a second link different from the first link and / or from another communication device by a second station comprising a receiver but not a transmitter;

[0173] - controlling the first station and the second station by means of a circuit; and

[0174] - providing the received control information to the circuit and / or the first station.

[0175] 24. A non-transitory computer-readable recording medium having a computer program product stored therein, which, when executed by a processor, causes execution of the method according to embodiment 23.

[0176] 25. A computer program comprising program code means for causing a computer to execute the steps of the method according to embodiment 23 when the computer program is executed on the computer.

[0177] One or more of the following embodiments may also be combined with one or more of the embodiments disclosed above.

[0178] A1. A first multi-link device, comprising:

[0179] - a first station comprising a transmitter and a receiver and configured to communicate with a first station of a second multi-link device on a first link;

[0180] a second station comprising a receiver but not a transmitter and configured to receive data from another first station of a second multilink device on a second link different from the first link; and

[0181] - a circuit configured to control the first station and the second station,

[0182] The second station is configured to provide the received data to the circuit and / or the first station.

[0183] A2. The first multi-link device defined in embodiment A1,

[0184] The first site or the second site is configured to collect configuration information from the second multi-link device, and

[0185] The circuit is configured to configure the second station to receive data from a link provided by the second multi-link device and not used by the first station based on the collected configuration information.

[0186] A3. A first multi-link device defined in any one of the preceding embodiments,

[0187] The first site is configured as:

[0188] - announcing the existence of the second station and its parameters and capabilities to the second multilink device, and

[0189] - Participating in establishing or establishing an agreement with a second multi-link device for one or more of validation, encryption parameters, and traffic identifier to link mapping.

[0190] A4. A first multi-link device defined according to implementation A3,

[0191] wherein the agreement is valid for a second link to a second site of the first multi-link device, and / or

[0192] The protocol may be the same as the protocol on the first link, or may be set separately for the second link.

[0193] A5. A first multi-link device defined in any one of the preceding embodiments,

[0194] wherein the second station is configured to propagate reception status information to the first station, the reception status information indicating a reception status of one or more second data units received from the second multi-link device on the second link, and

[0195] The first station is configured to transmit a second confirmation of receipt of the one or more second data units to a second multi-link device on the first link when receiving the reception status information.

[0196] A6. The first multi-link device defined in embodiment A5,

[0197] The first station is configured to transmit a second acknowledgment together with a first acknowledgment of receipt of the one or more first data units, or to combine the first acknowledgment and the second acknowledgment into a single acknowledgment, after the first station receives the one or more first data units from the second multi-link device on the first link.

[0198] A7. A first multi-link device defined according to implementation A6,

[0199] The first station is configured to announce a reception status propagation delay to the second multi-link device, where the reception status propagation delay indicates a delay for propagating the reception status information from the second station of the first multi-link device to the first station thereof.

[0200] A8. The first multi-link device defined in any one of the preceding embodiments comprises:

[0201] - one or more first stations, each configured to communicate with one or more first stations of other multi-link devices and / or other communication devices on different links; and

[0202] - one or more second stations, each configured to receive data from one or more first stations of other multi-link devices and / or other communication devices on a link different from the link used by a first station of the first multi-link device.

[0203] A9. A first multi-link device defined in any one of the preceding embodiments,

[0204] The receiver of the second site only supports physical layer data units in traditional modulation and coding formats.

[0205] A10. A first multi-link device defined in any one of the preceding embodiments,

[0206] Therein, the second station is configured to receive an Enhanced Multi-Link Single Radio (EMLSR) control frame from the second multi-link device and is configured to control the link to which the first station switches or focuses its resources for an upcoming frame exchange with the second multi-link device.

[0207] A11. A first multi-link device defined in embodiment A3,

[0208] Wherein the EMLSR link switching delay is different depending on whether the EMLSR control frame indicates a first link or a second link, and / or wherein the EMLSR delay is signaled by the first multi-link device to the second multi-link device as part of the setup.

[0209] A12. A first multi-link device defined in any one of the preceding embodiments,

[0210] wherein the second station is configured to propagate reception status information to the first station, the reception status information indicating a reception status of one or more second data units received from the second multi-link device on the second link, and

[0211] The first station is configured to transmit a second confirmation of receipt of the one or more second data units to a second multi-link device on the first link when receiving the reception status information.

[0212] A13. A first multi-link device defined according to implementation A12,

[0213] wherein the first station is configured to transmit a second acknowledgment together with a first acknowledgment of receipt of one or more first data units, or to combine the first acknowledgment and the second acknowledgment into a single acknowledgment, after the first station has received one or more first data units from the second multi-link device on the first link.

[0214] A14. A first multi-link device defined according to implementation A13,

[0215] The first station is configured to announce a reception status propagation delay to the second multi-link device, where the reception status propagation delay indicates a delay for propagating the reception status information from the second station of the first multi-link device to the first station thereof.

[0216] A15. The first multi-link device defined in any one of the preceding embodiments comprises:

[0217] - one or more first stations, each configured to communicate with one or more first stations of other multi-link devices and / or other communication devices on different links; and

[0218] - one or more second stations, each configured to receive data from one or more first stations of other multi-link devices and / or other communication devices on a link different from the link used by a first station of the first multi-link device.

[0219] A16. A first multi-link device defined in any one of the preceding embodiments,

[0220] The receiver of the second site only supports physical layer data units in traditional modulation and coding formats.

[0221] A17. A first multi-link device defined in any one of the preceding embodiments,

[0222] The first station is configured to communicate with the first station of the second multi-link device and / or with the station of the single link device using the link.

[0223] A18. A first multi-link device defined in any one of the preceding embodiments,

[0224] The first multi-link device is configured to operate as a non-access point station (non-AP STA) or as an access point (AP).

[0225] A19. A first multi-link device defined in any one of the preceding embodiments,

[0226] The circuit includes a control circuit, a medium access control (MAC) layer and / or a station management entity (SME).

[0227] A20. A first multi-link device defined in any one of the preceding embodiments,

[0228] The second site is connected to the first site via the circuit or directly connected to the first site.

[0229] A21. A second multi-link device, comprising:

[0230] - two or more first stations, each comprising a transmitter and a receiver, and each configured to communicate with a first station or a second station of a first multi-link device, wherein one first station communicates with a first station of the first multi-link device on a first link, and another first station transmits to a second station of the first multi-link device on a second link, the second station of the first multi-link device comprising a receiver but not a transmitter; and

[0231] - a circuit configured to control the two or more first sites.

[0232] A22. A second multi-link device defined in embodiment A21,

[0233] wherein the first station is configured to transmit the data unit on the second link to the second station requiring a response from the first multi-link device before transmitting the data unit on the second link to the second station,

[0234] - wait for receipt of a response from the first station on the first link and upon receipt of the response, initialize its contention window value with the minimum contention value, or

[0235] - Initiate another transmission and increment its contention window value.

[0236] A23. A second multi-link device defined in any one of embodiments A21 to A22,

[0237] The first station is configured to transmit low-latency data to a second station of the first multi-link device over the second link, regardless of the state of the first link.

[0238] A24. A second multi-link device defined in any one of embodiments A21 to A23,

[0239] The first station is configured to transmit one or more data units to a second station of the first multi-link device, the one or more data units not requiring a response or requiring an expected response to be received via the first link.

[0240] A25. A second multi-link device defined in any one of embodiments A21 to A24,

[0241] Wherein, the first station is configured to assume that the one or more data units requiring a response are lost if the received response does not include reception status information of at least one of the one or more data units.

[0242] A26. A second multi-link device defined in embodiment A25,

[0243] Wherein, the first station is configured to assume that the one or more data units are lost if the first station of the first multi-link device transmits a response after the end of transmission of the one or more data units with a delay greater than a reception status propagation delay, and the reception status propagation delay indicates the delay of propagating the reception status information from the second station of the first multi-link device to the first station thereof.

[0244] A27. A second multi-link device as defined in any one of embodiments A21 to A26,

[0245] Wherein, the first station communicating with the first station of the first multi-link device is configured to extend its transmission by filling the last data unit transmitted to the first station of the first multi-link device or by transmitting one or more other data units to the first station of the first multi-link device.

[0246] A28. A second multi-link device defined in embodiment A27,

[0247] The first station is configured to determine the length of the extension based on a signaled receive status propagation delay indicating a delay in propagating the receive status information from the second station to the first station of the first multi-link device.

[0248] A29. A first multi-link method of a first multi-link device, comprising:

[0249] - communicating with a first station of a second multi-link device on a first link via a first station comprising a transmitter and a receiver;

[0250] - receiving data at another first station from a second multilink device on a second link different from the first link, by a second station including a receiver but not including a transmitter; and

[0251] - Controlling the first site and the second site.

[0252] A30. A second multi-link method of a second multi-link device, comprising:

[0253] - communicating with a first site or a second site of a first multi-link device via two or more first sites each comprising a transmitter and a receiver, wherein one first site communicates with the first site of the first multi-link device on a first link and another first site transmits to the second site of the first multi-link device on a second link, the second site of the first multi-link device comprising a receiver but not a transmitter; and

[0254] - controlling the two or more first sites.

[0255] A31. A non-transitory computer-readable recording medium having a computer program product stored therein, which, when executed by a processor, causes the method according to implementation A29 or A30 to be performed.

[0256] A32. A computer program comprising program code means for causing the computer to perform the steps of the method according to implementation A29 or A30 when the computer program is executed on the computer.

Claims

1. A first multi-link device, comprising: - a first station comprising a transmitter and a receiver and configured to communicate with a first station of a second multi-link device on a first link; - a second station comprising a receiver but not a transmitter and being configured to receive control information from another first station of the second multilink device on a second link different from the first link and / or from another communication device; as well as - a circuit configured to control the first station and the second station, The second station is configured to provide the received control information to the circuit and / or the first station.

2. The first multi-link device according to claim 1, in, The first station is configured to transmit the control information received by the second station or the pre-processed control information and provide the control information to the first station of the second multi-link device and / or another communication device.

3. The first multi-link device according to claim 1, in, The control information includes one or more of the following: - link information indicating one or more of a length of a received data unit, a bandwidth of a received data unit, a transmission opportunity duration, a network allocation vector (NAV), a received power, a basic service set (BSS) identifier of a received data unit, restricted channel information of a received data unit, and status information indicating a busy or idle state of the second link; - channel state information, the channel state information indicating an impulse response and / or a transfer function between the second station and the second multi-link device and / or another communication device; as well as - Operation suggestion information indicating reception of control information for configuring or reconfiguring the operation of the first multi-link device.

4. The first multi-link device according to claim 1, in, The second station is configured to use one or more of the control information for one or more of the following: -controlling the first station to switch to an idle link; -controlling the first station to switch to another link; - Control itself to other links to receive control information from another communication device; and - Performing a contention window (CW) countdown for the first station to transmit after the CW countdown.

5. The first multi-link device according to claim 1, in, The first station is configured to observe a minimum observation period before transmitting after a link switching operation, and The circuit is configured to: if there is control information from a second station that has obtained control information of a link to which the first station switches, control the first station to reduce or ignore the minimum observation period.

6. The first multi-link device according to claim 4, in, The first station is configured to switch a link for communication with the second multi-link device and / or another communication device, and transmit a link switch announcement to the second multi-link device and / or another communication device, the link switch announcement including a link switch timing indicating a time and / or duration of the link switch operation.

7. The first multi-link device according to claim 1, in, The second station is configured to receive an enhanced multi-link single radio (EMLSR) control frame from the second multi-link device and to control the link to which the first station switches or focuses resources of the second multi-link device for an upcoming frame exchange with the second multi-link device.

8. The first multi-link device according to claim 7, in, Depending on whether the EMLSR control frame indicates that the link is the first link or the second link, the EMLSR link switching delay is different, and / or As part of the setup, the EMLSR delay is signaled by the first multi-link device to the second multi-link device.

9. The first multi-link device according to claim 1, in, The first station is configured to collect configuration information from the second multi-link device, and The circuit is configured to configure the second station to receive control information from a link provided by the second multi-link device and not used by the first station based on the collected configuration information.

10. The first multi-link device according to claim 1, in, The first site is configured as: - announcing the existence of the second station and the parameters and capabilities of the second station to the second multi-link device, and - Participate in establishing or establish an agreement or notification parameter with the second multi-link device for one or more of control information signaling, encryption parameters and EMLSR switching delay.

11. The first multi-link device according to claim 10, in, The agreement is valid for the second link to the second site of the first multi-link device, and / or The protocol may be the same as the protocol on the first link, or may be set separately for the second link.

12. The first multi-link device according to claim 1, in, The second station obtains the control information from a control frame transmitted in a physical layer data unit to which only conventional modulation and coding is applied.

13. The first multi-link device according to claim 1, in, The control information received by the second station is embedded in a physical layer data unit, the physical layer data unit is segmented into a first part to which conventional modulation and coding is applied and a second part to which advanced modulation and coding is applied, and The second station is configured to decode and demodulate only the first part of the physical layer data unit to obtain the control information.

14. The first multi-link device according to claim 13, in, The second station is configured to suspend reception after the first portion of the physical layer data unit and to resume reception once the physical layer data unit ends.

15. The first multi-link device according to claim 14, in, The point in time when reception is suspended depends on the detected format of the physical layer data unit, and / or wherein, The point in time at which reception continues depends on the length signaled in said first part of said physical layer data unit.

16. The first multi-link device according to claim 1, in, The second station is configured to support reception of physical layer data units that apply conventional modulation and coding and / or are modulated and encoded with a modulation and coding scheme of a basic rate set.

17. The first multi-link device according to claim 1, in, The second station is configured to support reception of physical layer data units that apply a non-high throughput (non-HT) or non-HT duplicate transmission format.

18. The first multi-link device according to claim 1, comprising: - one or more first stations, each configured to communicate with one or more first stations of other multi-link devices and / or other communication devices on different links; as well as - one or more second stations, each configured to receive data from one or more first stations of other multi-link devices and / or other communication devices on a link different from the link used by one first station of said first multi-link device.

19. A multi-link method of a first multi-link device, comprising: - communicating with a first station of a second multi-link device on a first link via a first station comprising a transmitter and a receiver; - receiving control information from another first station of said second multilink device on a second link different from said first link and / or from another communication device by a second station comprising a receiver but not comprising a transmitter; - controlling the first station and the second station by means of a circuit; as well as - providing the received control information to said circuit and / or said first station.

20. A non-transitory computer-readable recording medium, wherein: A computer program product is stored which, when executed by a processor, causes the method according to claim 19 to be performed.