Communication apparatus and communication method for uplink multi-layer transmission

Abstract

A communication apparatus and method for uplink multi-layer transmission are provided. One exemplary embodiment provides a first communication device comprising: circuitry to generate a signal for one or more second communication devices, the signal indicating whether to request or enable an uplink signal comprising two or more transport layers; and a transmitter that transmits the signal to one or more second communication devices.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to communication methods and apparatuses, and more particularly to methods and apparatuses for uplink multi-layer transmission. BACKGROUND

[0002] In the standardization of next generation WLAN, a new radio access technology that must have backward compatibility with Institute of Electrical and Electronics Engineers (IEEE) 802.11 a / b / g / n / ac / ax / be technologies has been discussed in the Ultra High Reliability Study Group (UHR SG).

[0003] Multi-layer transmission is an effective method to improve the throughput and reliability of a physical (PHY) layer. IEEE 802.11 ax / be does not define a multi-layer transmission mode. IEEE 802.11 n defines Unequal Modulation (UEQM) which applies different modulation mapping for symbols of different spatial streams. However, UEQM only supports single data stream transmission to a single user.

[0004] Broad ideas on multi-layer transmission have been discussed in UHR, however, there is no discussion on implementation of uplink multi-layer transmission.

[0005] Therefore, there is a need for communication apparatuses and methods that can solve the above problems. Furthermore, other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background of the disclosure. SUMMARY

[0006] The non-limiting and exemplary embodiments help to provide communication apparatuses and communication methods for uplink multi-layer transmission.

[0007] According to an aspect of the present disclosure, a first communication apparatus is provided, comprising: a circuitry that generates a signal for one or more second communication apparatuses, the signal indicating whether to request or enable an uplink signal including two or more transmission layers; and a transmitter that transmits the signal to the one or more second communication apparatuses.

[0008] According to another aspect of the present disclosure, a second communication apparatus is provided, comprising: a receiver that receives a signal from a first communication apparatus, the signal indicating whether to request or enable an uplink signal including two or more transmission layers; and a circuitry that demodulates and decodes the signal to obtain two or more sets of transmission parameters for the uplink signal.

[0009] According to another aspect of the disclosure, a communication method is provided, comprising: generating a signal for one or more communication devices, the signal indicating an uplink signal comprising whether two or more transmission layers are requested or enabled; and transmitting the signal to the one or more communication devices.

[0010] According to another aspect of the disclosure, a communication method is provided, comprising: receiving a signal, the signal indicating whether an uplink signal comprising two or more transmission layers is requested or enabled; and demodulating and decoding the signal to obtain two or more sets of transmission parameters for the uplink signal.

[0011] It should be noted that general or specific embodiments can be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof. Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages can be had from one or more of the embodiments and features without providing all of the benefits and / or advantages. BRIEF DESCRIPTION OF DRAWINGS

[0012] In the drawings, like reference numerals refer to same or functionally similar elements throughout the separate views, and the drawings are used to illustrate various embodiments and to explain various principles and advantages according to the present embodiments, which together with the detailed description below are incorporated into this specification and form a part hereof.

[0013] Figure 1 A trigger-based uplink multi-user (TB UL MU) transmission procedure in IEEE 802.11be specification according to an example is depicted.

[0014] Figure 2 A trigger frame format with Extra High Throughput (EHT) variant user info field according to an example is depicted.

[0015] Figure 3 An EHT TB physical protocol data unit (PPDU) according to an example is depicted.

[0016] Figure 4 A buffer status report procedure according to various embodiments of the disclosure is depicted.

[0017] Figure 5 A trigger frame format for requesting buffer status report according to various embodiments of the disclosure is depicted.

[0018] Figure 6 An example trigger-based uplink multi-user (TB UL MU) multi-layer transmission procedure in ultra-high reliability (UHR) is depicted.

[0019] Figure 7 A ultra-high reliability (UHR) trigger frame format in accordance with various embodiments of the disclosure is depicted.

[0020] Figure 8 A trigger frame format including multiple user information fields in accordance with various embodiments of the disclosure is depicted.

[0021] Figure 9 Multiple user information fields in accordance with various embodiments of the disclosure are depicted.

[0022] Figure 10 A user information field with an end marker subfield in accordance with various embodiments of the disclosure is depicted.

[0023] Figure 11 A flowchart of non-AP STA behavior in processing a trigger frame in accordance with various embodiments of the disclosure is depicted.

[0024] Figure 12 A flowchart of non-AP STA behavior in processing multiple user information fields in a non-adaptive manner in accordance with various embodiments of the disclosure is depicted.

[0025] Figure 13 A flowchart of non-AP STA behavior in processing multiple user information fields in an adaptive manner in accordance with various embodiments of the disclosure is depicted.

[0026] Figure 14 A trigger frame including multi-layer user information fields in accordance with various embodiments of the disclosure is depicted.

[0027] Figure 15 A common information field in a trigger frame including an indication for uplink multi-layer transmission in accordance with various embodiments of the disclosure is depicted.

[0028] Figure 16 A multi-layer user information field in a trigger frame including an indication for uplink multi-layer transmission in accordance with various embodiments of the disclosure is depicted.

[0029] Figure 17 A multi-layer user information field in a trigger frame including an indication of the size of the multi-layer user information field in accordance with various embodiments of the disclosure is depicted.

[0030] Figure 18 A flowchart of non-AP STA behavior in processing a multi-layer user information field in a non-adaptive manner in accordance with various embodiments of the disclosure is depicted. Figures 14-17a flowchart of non-AP STA behavior at the time of a trigger frame of any one of

[0031] Figure 19 depicts a trigger frame format that includes both a user info field and a multi-layer user info field of different sizes, in accordance with various embodiments of the present disclosure. Figures 14-17 a flowchart of non-AP STA behavior at the time of a trigger frame of any one of

[0032] Figure 20 depicts a trigger frame format that includes both a user info field and a multi-layer user info field of different sizes, in accordance with various embodiments of the present disclosure.

[0033] Figure 21 depicts an exemplary encoding of a UL UHR Modulation Coding Scheme (UHR-MCS) subfield, in accordance with various embodiments of the present disclosure.

[0034] Figure 22 depicts a trigger frame format that includes both a user info field and a multi-layer user info field of different sizes, in accordance with various embodiments of the present disclosure.

[0035] Figure 23 a flowchart of non-AP STA behavior at the time of a trigger frame of any one of Figure 22 a flowchart of non-AP STA behavior at the time of a trigger frame of any one of

[0036] Figure 24 a flowchart of non-AP STA behavior at the time of a trigger frame of any one of Figure 22 a flowchart of non-AP STA behavior at the time of a trigger frame of any one of

[0037] Figure 25 depicts a preamble of a UL transmission that includes a U-SIG field, in accordance with various embodiments of the present disclosure.

[0038] Figure 26 depicts a UL multi-layer transmission flag subfield included in a U-SIG field, in accordance with various embodiments of the present disclosure.

[0039] Figure 27 depicts a UHR TBP PDU that includes a UL multi-layer transmission parameter subfield, in accordance with various embodiments of the present disclosure.

[0040] Figure 28 depicts a UHR TBP PDU that includes a new UHR-SIG field, in accordance with various embodiments of the present disclosure.

[0041] Figure 29A flowchart illustrating a method for transmitting a signal for uplink multi-layer transmission according to various embodiments of the disclosure is shown.

[0042] Figure 30 A flowchart illustrating a method for receiving a signal for uplink multi-layer transmission according to various embodiments of the disclosure is shown.

[0043] Figure 31 A schematic partial cross-sectional view of a communication apparatus that can be implemented for uplink multi-layer transmission according to various embodiments of the disclosure is shown.

[0044] Those skilled in the art will understand that the elements in the figures are shown for the purpose of simplicity and clarity and are not necessarily drawn to scale. DETAILED DESCRIPTION

[0045] The following detailed description is merely exemplary in nature and is not intended to limit the embodiments or the application and uses of the embodiments. There is no intention that the application be bound by any theory of operation or by any theory presented in the preceding background or the following detailed description. Furthermore, there is no intention that any aspect of the application be bound by the foregoing Summary or by any theory presented in the Background or Detailed Description.

[0046] Some embodiments of the disclosure will be described by reference to the drawings, which are intended to be merely illustrative. In the drawings, like numerals and characters designate like elements or equivalents throughout.

[0047] In the following paragraphs, specific exemplary embodiments are explained with reference to an Access Point (AP) and a Station (STA) for service discovery in a local area network.

[0048] In the context of IEEE 802.11 (Wi-Fi) technology, a station (interchangeably referred to as a STA) is a communication apparatus with the capability to use IEEE 802.11 protocols. Based on the IEEE 802.11-2020 definition, a STA can be any device that contains an IEEE 802.11 conformant Media Access Control (MAC) and a physical layer (PHY) interface to the Wireless Medium (WM).

[0049] For example, a station can be a laptop computer, a desktop Personal Computer (PC), a Personal Digital Assistant (PDA), an access point or non-access point (e.g., an AP STA or a non-AP STA), or a Wi-Fi phone in a Wireless Local Area Network (WLAN) environment. The station can be fixed or mobile. In a WLAN environment, the terms "STA," "non-AP STA," "client," "wireless client," "user," "user device," and "mobile terminal" are often used interchangeably.

[0050] Likewise, an AP (which can be interchangeably referred to as a Wireless Access Point (WAP) in the context of IEEE 802.11 (Wi-Fi) technology) is a communication device that allows STAs in a WLAN to connect to a wired network. The AP is typically connected to a router (via a wired network) as a standalone device, but it can also be integrated with or used in a router.

[0051] As mentioned above, a STA in a WLAN can function as an AP at different times, and vice versa. This is because a communication device in the context of IEEE 802.11 (Wi-Fi) technology can include both STA hardware components and AP hardware components. In this way, the communication device can switch between STA mode and AP mode based on actual WLAN conditions and / or requirements.

[0052] In Figure 1An example of a trigger-based uplink multi-user (TB UL MU) transmission procedure in the IEEE 802.11 be specification is shown in diagram 100. For example, the AP 102 can transmit an Extremely High Throughput (EHT) trigger frame 108 after a back off time 114, which has transmission parameters for requesting EHT TB Physical Protocol Data Units (PPDUs) from non-AP STAs 104 and 106 (e.g., EHT TB PPDUs 110 and 112 from non-AP STAs 104 and 106, respectively). Each EHT TB PPDU 110 and 112 can be transmitted from non-AP STAs 104 and 106 on allocated Resource Units (RUs) and Spatial Stream(s) (SSs) following the transmission parameters indicated in the EHT trigger frame 108. A single Physical Layer Service Data Unit (PSDU) can be transmitted by each of non-AP STAs 104 and 106. Those skilled in the art will appreciate that there can be a Short Interframe Space (SIFS) time interval, for example, as shown in Figure 1 and other figures. Figure 2 An example of an EHT trigger frame 108 is shown in diagram 200, where the trigger frame format 200 includes an EHT variant of the User Info field 202. In addition, Figure 3 An example EHT TB PPDU format 300 is shown that can be used for EHT TB PPDUs 110 and 112 as shown in Figure 1

[0053] A TB UL MU multi-layer transmission can be requested by a trigger frame containing information to indicate and request UL multi-layer transmission from one or more non-AP STAs. A non-AP STA can transmit UL multi-layer transmission in a TB PPDU. In the UL multi-layer transmission, a single non-AP STA transmits one or more data streams (PSDUs) carried by different transmission layers protected by different transmission parameters in a TB PPDU.

[0054] ​In this disclosure, several triggering options and variants for TB UL MU multi-layer transmission are proposed. In one option, the trigger can be performed in a non-adaptive way, such that whether to apply multi-layer transmission and all transmission parameters are decided by the AP transmitting the trigger frame and indicated in the trigger frame. The AP can advantageously decode and demodulate the UL multi-layer transmission without any additional signaling and the TB PPDU does not need to change. In another option, the trigger can be performed in an adaptive way, where whether to apply multi-layer transmission is decided by the non-AP STA receiving the trigger frame. All or part of the transmission parameters are decided by the AP transmitting the trigger frame and indicated in the trigger frame. The non-AP STA can also decide part of the transmission parameters by itself. The advantage of this option is that UL multi-layer transmission can be sent only when necessary.

[0055] In addition, the AP and non-AP STAs can indicate the capability of supporting UL multi-layer transmission before the UL multi-layer transmission. The capability can be indicated in an element (e.g., Multi-Layer element, UHR capability element) carried in the beacon or probe request / response frame. The capability can also be indicated in the buffer status report carried in the TB feedback Null Data Packet / Buffer Status Report (NDP / BSR). The AP can request TB UL MU multi-layer transmission from a non-AP STA that indicates the capability of supporting UL multi-layer transmission. The AP should not request TB UL MU multi-layer transmission from a non-AP STA that does not indicate the capability of supporting UL multi-layer transmission.

[0056] In one embodiment, before the TB UL MU multi-layer transmission, the AP can request multi-layer buffer status report from non-AP STAs to know the demand of UL multi-layer transmission from non-AP STAs. For example, referring to Figure 4In the illustration 400, the AP 402 can transmit a Null Data PPDU Feedback Report Poll (NFRP) or Buffer Status Report Poll (BSRP) trigger frame 408 to request multi-tier buffer status reports from non-AP STAs (e.g., in TB Feedback NDPs or BSRs 410 and 412 from non-AP STAs 404 and 406, respectively). The multi-tier buffer status reports can be included in TB Feedback NDPs requested by the NFRP trigger frame or in Buffer Status Reports (BSRs) included in TB PPDUs requested by the BSRP trigger frame. In the case where TB PPDUs containing the requested BSRs are transmitted from the STAs 404 and 406 to the AP 402 (e.g., in response to the BSRP trigger frame transmitted from the AP 402), a Multi-STA Block Ack frame 414 can be transmitted from the AP 402 to acknowledge the received TB PPDUs.

[0057] In the NFRP trigger frame or the BSRP trigger frame, an indication of the special type of buffer status report requested (e.g., multi-tier, low latency, etc.) can be included. For example, referring to the trigger frame 500 of Figure 5 The special type trigger indication subfield 504 can be included in the common information field 502 of the trigger frame 500. The value of the special type trigger indication subfield can be 0, 1, or 3-4, where a value of '0' can indicate a multi-tier BSR, a value of '1' can indicate a low latency BSR, and a value of '3' or '4' can indicate a reservation. It will be understood that these values can change depending on the application to indicate different BSR types. Further, the trigger type subfield 506 of the common information field can indicate whether the trigger type is a BSRP or an NFRP. If no special type of buffer status report is requested, the non-AP STAs can simply feedback buffer status reports in the same manner as in the IEEE 802.11 be specification.

[0058] Alternatively, the non-AP STAs can also indicate multi-tier buffer status in unsolicited BSRs, such as the Quality of Service (QoS) control field in QoS Null and QoS Data frames and the BSR control subfield (if present) in QoS Null, QoS Data, and Management frames. In the multi-tier buffer status reports, information such as the uplink data buffer expected to be transmitted, the priority level(s) of the uplink data, the recommended transmission parameters for each priority level of the uplink data, and other similar information can be included.

[0059] An example of a TB UL MU multi-layer transmission procedure is shown in the illustration 600 of Figure 6 For example, the AP 602 can transmit a UHR trigger frame 608 with transmission parameters for requesting UHR TB PPDUs from the non-AP STAs 604 and 606 (e.g., UHR TB PPDUs 610 and 612 from the non-AP STAs 604 and 606, respectively). Each UHR TB PPDU 610 and 612 from the non-AP STAs 604 and 606 can include an UL multi-layer transmission following the transmission parameters indicated in the UHR trigger frame 608. One or more PSDUs can be transmitted by each of the non-AP STAs 604 and 606.

[0060] In a trigger frame requesting a TB UL MU transmission, it can be explicitly or implicitly indicated whether UL multi-layer transmission (e.g., UL multi-layer transmission can be referred to as an uplink signal including two or more transmission layers) from non-AP STA(s) is requested or enabled. In explicit indication, a subfield can indicate the information. In one embodiment, to indicate the information in a non-adaptive manner, a UL multi-layer Tx subfield can be utilized to indicate whether multi-layer transmission from non-AP STA(s) is requested (e.g., the UL multi-layer Tx subfield can be referred to as a first field, which indicates whether an uplink signal including two or more transmission layers is requested). The UL multi-layer Tx subfield can be included in a user information field, or in a common information field. If the UL multi-layer Tx subfield is included in the user information field, when the UL multi-layer Tx subfield is set to 1, UL multi-layer transmission from the non-AP STA addressed by the user information field can be requested. If the UL multi-layer Tx subfield is included in the common information field, when the UL multi-layer Tx subfield is set to 1, UL multi-layer transmission from one or more non-AP STAs can be requested. When the UL multi-layer Tx subfield is set to 0, normal UL transmission can be requested. The normal UL transmission can be the same as UL transmission in IEEE 802.11 be specification.

[0061] In IEEE 802.11be, there is no signaling for an AP to transmit a trigger frame to indicate UL multi-layer transmission, and there is no processing rule for a non-AP STA to receive the trigger frame to understand that UL multi-layer transmission is being requested. With explicit or implicit indication, UL multi-layer transmission can be advantageously requested or enabled. Explicit indication requires small changes on the AP side (e.g., adding new signaling in the trigger frame), while the trigger frame implementation on the non-AP side is almost the same process (e.g., as in IEEE 802.11be). Implicit indication requires changes on both the AP and non-AP STA sides, but has less impact on devices of previous revisions of IEEE 802.11 specifications, thus enabling backward compatibility.

[0062] In one embodiment, to indicate the information in an adaptive manner, a UL multi-layer enable subfield can be utilized to indicate whether multi-layer transmission from non-AP STA(s) is enabled (e.g., the UL multi-layer enable subfield can be referred to as a first field, which indicates whether uplink signals including two or more transmission layers are enabled). The UL multi-layer enable subfield can be included in the user info field, or in the common info field. If the UL multi-layer enable subfield is included in the user info field, when the UL multi-layer Tx subfield is set to 1, UL multi-layer transmission from non-AP STAs addressed by the user info field can be enabled. If the UL multi-layer enable subfield is included in the common info field, when the UL multi-layer enable subfield is set to 1, UL multi-layer transmission from one or more non-AP STAs can be enabled. This embodiment can not be applicable to UL MU-MIMO transmission. Non-AP STAs indicated that UL multi-layer transmission is enabled can decide whether to send UL multi-layer transmission based on link and buffer status. In addition, when the UL multi-layer enable subfield is set to 0, UL multi-layer transmission can be disabled. Non-AP STAs indicated that UL multi-layer transmission is disabled should not send multi-layer transmission in the TB PPDU. Figure 7 A UHR trigger frame format 700 is depicted, which includes a UL multi-layer Tx / enable subfield 702 or 708 as described above, for showing indication of whether UL multi-layer transmission from non-AP STA(s) is requested or enabled. As explained above, the subfield 702 can be included in the common info field 706; the subfield 708 can be included in the user info field 704.

[0063] In addition, for implicit indication of whether UL multi-layer transmission from non-AP STA(s) is requested or enabled, a specific subfield can not be needed to indicate the information. Instead, the information is indicated by the presence of a specific user info field or the total number of sets of transmission parameters assigned to non-AP STAs.

[0064] In one embodiment, in the trigger frame requesting TB UL MU transmission, when UL multi-layer transmission is requested or enabled (e.g., in a non-adaptive manner or in an adaptive manner), the transmission parameters can be further indicated in the trigger frame. In a first option, the transmission parameters can be indicated in multiple user info fields (e.g., the multiple user info fields can be referred to as two or more second fields, which indicate two or more sets of transmission parameters corresponding to two or more transmission layers of the uplink signal, respectively). For example, the transmission parameters for multi-layer transmission can be indicated by multiple user info fields specified with the same Association Identifier (AID) (e.g., the multiple user info fields can be referred to as two or more second fields addressed by the same identifier, and the two or more second fields can include two or more third fields, which indicate two or more sets of transmission parameters for two or more transmission layers of the uplink signal, respectively). The RUs allocated for each transmission layer, along with the location of each user info field corresponding to the transmission layer, are indicated in the RU allocation subfield. For example, each of the two or more second fields can include a fourth field (RU allocation subfield), which indicates resource unit (RU) allocation information for the two or more sets of transmission layers of the uplink signal. The AP can allocate each RU based on the transmission parameters or other parameters (such as the size or rate of the content in the layer) for each transmission layer. With this option, there is advantageously no impact on legacy non-AP STAs decoding the trigger frame, although a long trigger frame can be needed. In a second option, the transmission parameters can be indicated in a multi-layer user info field. The transmission parameters for multi-layer transmission can be indicated by the multi-layer user info field with the corresponding AID. For example, the multi-layer user info field can be referred to as a second field, which indicates two or more sets of transmission parameters corresponding to two or more transmission layers of the uplink signal. The two or more sets of transmission parameters can be indicated in two or more third fields in the second field, and the RU allocation information can be indicated in a fourth field in the second field. With this option, legacy non-AP STAs can be impacted, but a shorter trigger frame can be used (compared to the first option).

[0065] The transmission parameters can be indicated in multiple user info fields. Whether UL multi-layer transmission by a non-AP STA is requested or enabled can be implicitly indicated based on whether more than one user info field (and thus more than one set of transmission parameters) is assigned to a single non-AP STA (e.g., the indication of whether uplink signals are requested or enabled can be based on the presence of two or more second fields, or based on the total number of sets of transmission parameters). For example, if multiple user info fields are assigned to a single non-AP STA, UL multi-layer transmission from the non-AP STA can be requested or enabled. If only one user info field is assigned to a single non-AP STA, normal UL transmission from the non-AP STA can be requested. When more than one user info field is assigned to a single non-AP STA in a non-adaptive manner, each single user info field assigned to the same non-AP STA can carry a single set of transmission parameters for each of the transmission layers in the UL multi-layer transmission by the non-AP STA. In an adaptive manner, if the non-AP STA determines not to transmit UL multi-layer transmission, one of the multiple user info fields assigned to the non-AP STA can carry a set of transmission parameters for normal UL transmission (e.g., the same UL transmission as in IEEE 802.11 be), while if the non-AP STA determines to transmit UL multi-layer transmission, each of the remaining user info fields can carry a single set of transmission parameters for each of the transmission layers.

[0066] Figure 8 FIG. 1 depicts a wireless communication system including multiple user info fields (e.g., a first user info field and a second user info field) according to various embodiments of the present disclosure, Figure 8The value indicated in AID 12 subfield 806 in user info field 802 of trigger frame 800 and the value indicated in AID 12 subfield 808 in another user info field 804 can be the same, e.g., to indicate that the transmission parameters for the UL multi-layer transmission are provided in user info field 802 (e.g., transmission parameters 810) and user info field 804 (e.g., transmission parameters 812). Thus, the two or more second fields (e.g., user info fields 802 and 804) can include two or more third fields (e.g., fields indicating transmission parameters 810 in user info field 802 and transmission parameters 812 in user info field 804) indicating two or more sets of transmission parameters for two or more transmission layers of the uplink signal, respectively. In one implementation, in a non-adaptive manner, transmission parameters 810 included in user info field 802 can be assigned to a first transmission layer of the requested UL multi-layer transmission to the non-AP STA, while transmission parameters 812 included in user info field 804 can be assigned to a second transmission layer of the requested UL multi-layer transmission to the non-AP STA. In another implementation, in an adaptive manner, trigger frame 800 can further include a user info field 814 including an AID 12 subfield 816 having the same value as AID 12 subfields 806 and 808. In this example, if the non-AP STA determines not to transmit the UL multi-layer transmission, transmission parameters 810 included in user info field 802 can be assigned to a normal UL transmission (e.g., the same UL transmission as in IEEE 802.11 BE, rather than an UL multi-layer transmission). If the non-AP STA determines to transmit the UL multi-layer transmission, transmission parameters included in user info field 804 can be assigned to a first transmission layer to the non-AP STA, while transmission parameters 818 included in user info field 814 can be assigned to a second transmission layer to the non-AP STA.

[0067] Since there can be multiple user info fields assigned to a single non-AP STA, the end of multiple user info fields can be indicated. In one implementation, multiple user info fields for the same non-AP STA should be arranged consecutively in the trigger frame, and the end of the multiple user info fields can be implicitly indicated based on a different user info field (e.g., having a different AID value than the previous user info field) after the last user info field of the multiple user info fields. Once the non-AP STA finds the first user info field addressed with a different AID after encountering multiple consecutive user info fields assigned to it, it can stop checking further user info fields. For example, referring to FIG. 8, if the non-AP STA determines to transmit the UL multi-layer transmission, it can stop checking further user info fields after finding the first user info field 814 addressed with a different AID than the previous user info field 804. Figure 9The illustrated multiple user info fields 900, each user info 1 field 902 is intended for the first non-AP STA and includes an AID 12 subfield set to the same AID value assigned to the first non-AP STA, and each user info 2 field 904 is intended for the second non-AP STA and includes an AID 12 subfield set to the same AID value assigned to the second non-AP STA. In an example, the AID value indicated in the user info 1 fields is different from the AID value indicated in the user info 2 fields. The difference in AID values of the last user info 1 field 902 and the first user info 2 field 904 indicates the end of the user info fields associated with user info 1, where user info 1 includes the AID value indicating the intended non-AP STA, and user info 2 includes a different AID value. In another implementation, the end of the multiple user info fields can be explicitly indicated by a subfield included in the last user info field of the multiple user info fields assigned to a single non-AP STA (e.g., the end flag subfield 1002 in the user info field 1000 of FIG. 10). The explicit indication of the end of the multiple user info fields (e.g., the end flag subfield) can also be used when the UL multi-layer transmission is explicitly indicated by the UL multi-layer Tx / UL multi-layer enabled subfield. When the UL multi-layer Tx / UL multi-layer enabled subfield is included in the user info field, the UL multi-layer Tx / UL multi-layer enabled subfield can be used instead of the end flag subfield to indicate that the values are set to 1 in other user info fields of the multiple user info fields by setting its value to 0 in the last user info field. Once the non-AP STA finds the indication of the end of the multiple user info fields included in the allocated user info field (e.g., the end flag subfield set to 1), the non-AP STA can stop checking the other user info fields. Figure 10

[0068] ​In one implementation, when a non-AP STA receives a trigger frame including multiple user info fields, it can continue to process the multiple user info fields based on the following processing steps if the non-AP STA satisfies any one of the following conditions: (1) the non-AP STA is addressed by a user info field that includes UL multi-layer Tx / UL multi-layer enabled subfield set to 1; (2) the non-AP STA supports UL multi-layer transmission and the common info field of the trigger frame includes UL multi-layer Tx / UL multi-layer enabled subfield set to 1, and the non-AP STA is addressed by the multiple user info fields; and (3) the non-AP STA is addressed by the multiple user info fields. The processing steps for processing the multiple user info fields can be as follows: (1) the non-AP STA examines the trigger frame to find all user info fields specified with corresponding AIDs; (2) in a non-adaptive manner, the non-AP STA prepares the UL multi-layer transmission according to multiple sets of transmission parameters indicated in the multiple user info fields, and in an adaptive manner, the non-AP STA determines whether to transmit the UL multi-layer transmission; (3) if the non-AP STA determines not to transmit the UL multi-layer transmission, then the non-AP STA prepares the UL transmission according to the user info field carrying the transmission parameters for normal UL transmission. Otherwise, the non-AP STA prepares the UL multi-layer transmission according to multiple sets of transmission parameters indicated in the multiple user info fields.

[0069] Figure 11 A flowchart 1100 depicting non-AP STA behavior in processing a trigger frame in accordance with various embodiments of the present disclosure is depicted. At step 1102, the non-AP STA receives a trigger frame. At step 1104, the non-AP STA examines a user info field of the trigger frame. Next, at step 1106, the non-AP STA determines whether an AID value of the user info field (e.g., indicated in the AID 12 field of the user info field) matches an AID value associated with the non-AP STA. If the AID is determined not to match, the flow proceeds to step 1108. At step 1108, the non-AP STA determines whether there are still user info fields that have not been examined. If it is determined that there are user info fields that have not been examined, the flow returns from step 1108 to step 1104 to examine a user info field, e.g., the first user info field that was determined at step 1108 to not have been examined. If the non-AP STA determines at step 1108 that there are no remaining user info fields to be examined (or in other words, that all user info fields have been examined), the flow can end at step 1110.

[0070] On the other hand, if it is determined at step 1106 that the AID matches (e.g., the AID value of the user info field is the same as the AID value associated with the non-AP STA), the flow proceeds to step 1112, where it is determined whether a condition is satisfied. The condition can be any one of the following: (1) the non-AP STA is addressed by the user info field that includes the UL multi-layer Tx / UL multi-layer enable subfield set to 1; (2) the non-AP STA supports UL multi-layer transmission and the common info field of the received trigger frame includes the UL multi-layer Tx / UL multi-layer enable subfield set to 1, and the non-AP STA is addressed by multiple user info fields; (3) the non-AP STA is addressed by multiple user info fields.

[0071] If it is determined that any one of these conditions is satisfied, the flow proceeds to step 1114, where the multiple user info fields with matching AID values are processed by the non-AP STA as follows: (1) the non-AP STA examines the trigger frame to find all user info fields specified with the corresponding AID; (2) in a non-adaptive manner, the non-AP STA prepares UL multi-layer transmission according to multiple sets of transmission parameters indicated in the multiple user info fields, and in an adaptive manner, the non-AP STA determines whether to transmit the UL multi-layer transmission; and (3) if the non-AP STA determines not to transmit the UL multi-layer transmission, the non-AP STA then prepares UL transmission according to the user info field carrying the transmission parameters for normal UL transmission. Otherwise, the non-AP STA prepares UL multi-layer transmission according to multiple sets of transmission parameters indicated in the multiple user info fields. After step 1114, the flow can end at step 1110.

[0072] If it is determined at step 1112 that none of the conditions is satisfied, the flow proceeds to step 1116, where the non-AP STA obtains the transmission parameters of the examined user info field and prepares UL transmission according to the IEEE 802.11 be specification. After step 1116, the flow can end at step 1110.

[0073] Figure 12 A flowchart 1200 depicting the non-AP STA behavior when processing multiple user info fields in a non-adaptive manner (e.g., in step 1114 of flowchart 1100) is depicted in accordance with various embodiments of the present disclosure. At step 1202, the non-AP STA can prepare UL multi-layer transmission according to the transmission parameters obtained from the multiple user info fields, and the flow ends at step 1204.

[0074] Further, Figure 13A flowchart 1300 of non-AP STA behavior in processing multiple user info fields in an adaptive manner (e.g., in step 1114 of flowchart 1100) is depicted in accordance with various embodiments of the present disclosure. At step 1302, the non-AP STA determines whether to transmit UL multi-layer transmission. If it is determined that UL multi-layer transmission is to be transmitted, the flow proceeds to step 1304, where the non-AP STA prepares UL multi-layer transmission according to the transmission parameters obtained from the multiple user info fields, or prepares UL multi-layer transmission according to part of the transmission parameters obtained from the multiple user info fields and then determines other transmission parameters by itself. Then, the flow ends at step 1306. If it is determined at step 1302 that the non-AP STA will not transmit UL multi-layer transmission, the flow proceeds to step 1308, where the non-AP STA obtains the transmission parameters of the user info fields and prepares UL transmission according to IEEE 802.11 be specification, and the flow can end at step 1306.

[0075] The transmission parameters for UL multi-layer transmission can be indicated in the multi-layer user info field. Whether UL multi-layer transmission from the non-AP STA is requested or enabled can be implicitly indicated by whether the multi-layer user info field (e.g., indicating two or more sets of transmission parameters instead of just one set) is assigned to the non-AP STA (e.g., the indication of whether uplink signal is requested or enabled can be based on the presence of the multi-layer user info field, or based on the total number of sets of transmission parameters). If the multi-layer user info field is assigned to the non-AP STA, UL multi-layer transmission from the non-AP STA is requested or enabled. If the user info field is assigned to the non-AP STA, normal UL transmission from the non-AP STA is implied to be requested. In one implementation, only the multi-layer user info field, padding field and frame check sequence (FCS) field are included after the common info field in the trigger frame. For simplicity, the trigger frame refers to the trigger frame including only the multi-layer user info field below. The trigger frame including only the multi-layer user info field can be specified by a subfield of the common info field in the trigger frame, or a subfield of each multi-layer user info field. This advantageously makes the processing of the trigger frame less complex, and has no impact on legacy non-AP STAs. In another implementation, the multi-layer user info field, user info field, padding field and frame check sequence (FCS) field can be included after the common info field in the trigger frame. The multi-layer user info field can be distinguished from the user info field by a subfield included in the multi-layer user info field. The multi-layer user info field can have the same size as the user info field or a different size. This implementation advantageously enables higher flexibility as the trigger frame can request both UL multi-layer and normal transmission at the same time.

[0076] Figure 14 A trigger frame 1400 including only multi-layer user info fields 1402 is depicted in accordance with various embodiments of the present disclosure. Since all user info fields 1402 in the trigger frame 1400 are multi-layer user info fields, these fields as a whole can be referred to as “only multi-layer user info fields” 1402. The multi-layer user info fields 1404 can include an AID 12 subfield 1406, an UL target receive power subfield 1408, a PS 160 subfield 1412, and a plurality of UL Tx parameter subfields 1410. For example, a second field (e.g., the multi-layer user info fields 1404) can include two or more third fields (e.g., the UL Tx parameter subfields 1410) that respectively indicate two or more sets of transmission parameters for two or more transmission layers of an uplink signal. The multi-layer user info fields 1404 are addressed to the associated non-AP STA whose AID is equal to the value in the AID 12 subfield 1406. In a non-adaptive manner of processing the trigger frame 1400, in each UL Tx parameter subfield 1410, a set of transmission parameters for a single transmission layer can be indicated, such that different UL Tx parameter subfields can carry different sets of transmission parameters. In an adaptive manner of processing the trigger frame 1400, in one of the UL Tx parameter subfields 1410, a set of transmission parameters for normal transmission can be indicated if the non-AP STA determines not to transmit an UL multi-layer transmission, while in the other UL Tx parameter subfields, a set of transmission parameters for each single transmission layer can be indicated.

[0077] Figure 15 A common info field 1502 in a trigger frame 1500 is depicted in accordance with various embodiments of the present disclosure. The common info field 1502 can include an indication for uplink multi-layer transmission. For example, “include only multi-layer user info fields in the trigger frame” can be indicated by a trigger type subfield 1504 and / or an UL multi-layer Tx / UL multi-layer enable subfield 1506 of the common info field 1502. Further reference is made to the trigger frame 1600 of Figure 16 include only multi-layer user info fields in the trigger frame, and can also be indicated by the UL multi-layer Tx / UL multi-layer enable subfield 1604 in each of the plurality of multi-layer user info fields 1602 in the trigger frame 1600, such that the value of the UL multi-layer Tx / UL multi-layer enable subfield in each of the plurality of multi-layer user info fields 1602 can be the same.

[0078] The size of each multi-layer user info field can be flexible, and the size of the multi-layer user info field can be indicated in a subfield of the multi-layer user info field. Figure 17A multi-layer user info field 1702 in a trigger frame 1700 according to various embodiments of the disclosure is depicted. The multi-layer user info field 1702 can indicate its size. The size of the multi-layer user info field 1702 can be indicated by N (e.g., the value of the number of UL Tx parameter subfields 1704, where N is an integer and ≥ 2), which is the number of UL Tx parameter subfields 1706 included in the corresponding multi-layer user info field 1702. The number of UL Tx parameter subfields can be referred to herein as a sixth field, which is used to indicate the size of a second field (e.g., the multi-layer user info field).

[0079] When a non-AP STA receives a trigger frame containing one or more multi-layer user info fields and no any user info field, the non-AP STA can take the following steps: if the non-AP STA does not support UL multi-layer transmission, it stops decoding the trigger frame, or if the non-AP STA supports UL multi-layer transmission, it proceeds to the next step; in the next step, the non-AP STA checks the multi-user info fields of the trigger frame until it identifies a multi-layer user info field designated with an AID corresponding to an AID associated with the non-AP STA association. In a non-adaptive way of handling the multi-layer user info field with the corresponding AID, the non-AP STA prepares UL multi-layer transmission according to the multiple sets of transmission parameters indicated in the multi-layer user info field. In an adaptive way of handling the multi-layer user info field with the corresponding AID, the non-AP STA determines whether to transmit UL multi-layer transmission. If the non-AP STA determines not to transmit UL multi-layer transmission, it prepares UL transmission according to the multi-layer user info field. Otherwise, the non-AP STA prepares UL multi-layer transmission according to the multiple sets of transmission parameters indicated in the multi-layer user info field.

[0080] Figure 18 A flowchart 1800 of non-AP STA behavior when handling a trigger frame in a non-adaptive way according to various embodiments of the disclosure is depicted. The trigger frame can be as described above with respect to FIG. 17. Figures 14 to 17Any of the ones shown. At step 1802, the non-AP STA receives the trigger frame. At step 1804, it is checked whether the trigger frame includes any multi-layer user info field(s). If the trigger frame does not include any multi-layer user info field, the flow proceeds to step 1806. At step 1806, the non-AP STA checks the user info field included in the trigger frame, obtains the transmission parameters and prepares the UL transmission in the same way as specified in IEEE 802.11 be specification. After step 1806, the flow can end at step 1818. On the other hand, if it is determined at step 1804 that there is one or more multi-layer user info fields, the flow proceeds to step 1808. At step 1808, the non-AP STA checks one of the multi-layer user info field(s) and then proceeds to step 1810. At step 1810, the non-AP STA determines whether the AID indicated in the multi-layer user info field matches the AID associated with the non-AP STA. If the AID does not match the AID associated with the non-AP STA, the flow can proceed to step 1812. At step 1812, the non-AP STA determines whether there are any unexamined multi-layer user info fields in the trigger frame. If there are unexamined multi-layer user info fields in the trigger frame (left), the flow returns from step 1812 to step 1808 to examine the first unexamined multi-layer user info field determined in step 1812. If it is determined at step 1812 that there are no unexamined multi-layer user info fields in the trigger frame (left) (or in other words, all the multi-layer user info fields in the trigger frame have been examined), the flow can proceed to step 1818 and end at step 1818.

[0081] On the other hand, if it is determined at step 1810 that the AID value matches, the flow can proceed to step 1814 where the transmission parameters of the multi-layer user info field are obtained. Next, at step 1816, the non-AP STA prepares the UL multi-layer transmission according to the transmission parameters obtained from the multi-layer user info field at step 1814, and then the flow ends at step 1818.

[0082] Figure 19 A flowchart 1900 of non-AP STA behavior when handling trigger frames in an adaptive manner is depicted in accordance with various embodiments of the present disclosure. The trigger frame can be as described in any of the ones shown. At step 1902, the non-AP STA receives the trigger frame. At step 1904, it is checked whether the trigger frame includes any multi-layer user info field(s). If the trigger frame does not include any multi-layer user info field, the flow proceeds to step 1906. At step 1906, the non-AP STA checks the user info field included in the trigger frame, obtains the transmission parameters and prepares the UL transmission in the same way as specified in IEEE 802.11 be specification. After step 1906, the flow can end at step 1918. On the other hand, if it is determined at step 1904 that there is one or more multi-layer user info fields, the flow proceeds to step 1908. At step 1908, the non-AP STA checks one of the multi-layer user info field(s) and then proceeds to step 1910. At step 1910, the non-AP STA determines whether the AID indicated in the multi-layer user info field matches the AID associated with the non-AP STA. If the AID does not match the AID associated with the non-AP STA, the flow can proceed to step 1912. At step 1912, the non-AP STA determines whether there are any unexamined multi-layer user info fields in the trigger frame. If there are unexamined multi-layer user info fields in the trigger frame (left), the flow returns from step 1912 to step 1908 to examine the first unexamined multi-layer user info field determined in step 1912. If it is determined at step 1912 that there are no unexamined multi-layer user info fields in the trigger frame (left) (or in other words, all the multi-layer user info fields in the trigger frame have been examined), the flow can proceed to step 1918 and end at step 1918. Figures 14 to 17Any of the illustrated. At step 1902, the non-AP STA receives the trigger frame. At step 1904, it is checked whether the trigger frame includes any multi-layer user info field(s). If the trigger frame does not include any multi-layer user info field, the flow proceeds to step 1906, where the non-AP STA checks the user info field included in the trigger frame, obtains the transmission parameters and prepares the UL transmission in the same way as specified in IEEE 802.11 be specification. Then, the flow ends at step 1922. On the other hand, if it is determined at step 1904 that there is one or more multi-layer user info field, the flow proceeds to step 1908, where the non-AP STA checks one of the multi-layer user info field(s). At step 1910, it is determined whether the AID indicated in the multi-layer user info field matches the AID associated with the non-AP STA. If it is determined that the AID does not match, the flow proceeds to step 1912, where it is determined whether there is any multi-layer user info field left unchecked in the trigger frame. If yes, the flow returns to step 1908 to check the next multi-layer user info field. Otherwise, the flow ends at step 1922. On the other hand, if it is determined at step 1910 that the AID value matches, the flow proceeds to step 1914, where the transmission parameters of the multi-layer user info field are obtained. At step 1916, the non-AP STA determines whether an UL multi-layer transmission should be sent (e.g., an adaptive procedure). If it is determined that an UL multi-layer transmission should not be sent, the non-AP STA obtains the transmission parameters and prepares the UL transmission in the same way as specified in IEEE 802.11 be specification, and the flow ends at step 1922. Otherwise, the flow proceeds from step 1916 to step 1918, where the non-AP STA prepares the UL multi-layer transmission according to the transmission parameters obtained from the multi-layer user info field, or prepares the UL multi-layer transmission according to the partial transmission parameters obtained from the multi-layer user info field and other transmission parameters determined by itself, and the flow ends at step 1922.

[0083] The multi-layer user info field can be included in the trigger frame together with the user info field. In one embodiment, the multi-layer user info field can have the same size as the user info field. Figure 20A trigger frame 2000 including both a user info field of the same size (e.g., user info field 2004) and a multi-layer user info field (e.g., multi-layer user info field 2002) according to various embodiments of the present disclosure is depicted. The multi-layer user info field 2002 can include the same subfields as in the user info field 2004. A single set of transmission parameters indicated by the UL FEC coding type subfield 2008, SS allocation subfield 2014, UL target receive power subfield 2016, and PS 160 subfield 2018 applies across all transmission layers. Two sets of transmission parameters can be indicated by the RU allocation subfield 2006 (herein referred to as the fourth field) and the UL UHR-MCS subfield 2010 (herein referred to as the fifth field) for the two transmission layers. The multi-layer user info field can be specified by the UL multi-layer Tx / UL multi-layer enabled subfield (e.g., UL multi-layer Tx / UL multi-layer enabled subfield 2012 in the multi-layer user info field 2002). In this case, the multi-layer user info field 2002 can be considered as a special case of the user info field. RU allocation for the two transmission layers can be indicated implicitly by the RU allocation subfield 2006 using MRU allocation. Each RU in the MRU can be assigned to each layer according to a predetermined order. For example, when RU allocation RU A and RU B are indicated by the RU allocation subfield 2006 and the UL multi-layer Tx / UL multi-layer enabled subfield 2012 is set to 1, RU A is the RU for the first transmission layer and RU B is the RU for the second transmission layer (e.g., A and B are RU index numbers between 1 and 148). Alternatively, each RU can be assigned to each layer based on parameters (such as MCS) for each layer. MCS for the two transmission layers can be indicated by the UL UHR-MCS subfield 2010. When the UL multi-layer Tx subfield 2012 is set to 1, the UL UHR-MCS subfield 2010 (4 bits) can indicate two different MCSs for the two transmission layers. Limitations such as a range of the difference between the two MCS indices can be applied to reduce the number of bits. For example, it can be limited that the two MCSs indicated in the UL UHR-MCS subfield 2010 should not exceed MCS 9, and the difference between the two MCS indices should not exceed 3. Should be satisfied ; the difference between the options for the MCS index for a single transmission layer Should be satisfied In this case, example encodings for the UL UHR-MCS subfield 2010 are shown in Table 2100 of Figure 21 Thus, a non-AP STA addressed by the multi-layer user info field 2002 prepares for UL multi-layer transmission according to the multiple sets of transmission parameters indicated in the user info field 2004.

[0084] In one implementation, the multi-layer user information field, together with the user information field, can be included in the trigger frame, thereby allowing the multi-layer user information field to have a different size than the user information field. Figure 22 Trigger frames 2200, according to various embodiments of the present disclosure, are depicted including both user information fields of different sizes (e.g., user information field 2204) and multi-level user information fields (e.g., multi-level user information field 2202). The multi-level user information field 2202 may include an AID12 subfield 2206, an actual AID12 subfield 2208, and multiple UL Tx parameter subfields 2210. The multi-level user information field 2202 is addressed to an associated non-AP STA, whose AID is equal to the value in the actual AID12 subfield 2208. The multi-level user information field 2202 may be specified by a special AID12 value 2208 (or any value reserved for the AID12 subfield according to the IEEE 802.11 be specification). The format and rules of the UL Tx parameter subfield 2210 may be the same as those of the UL Tx parameter subfields 1410 and 1706 (e.g., the same as when only the multi-level user information field is included in the trigger frame). The size of each multi-level user information field (such as multi-level user information field 2202) can be flexible, and the size of the multi-level user information field (such as user information field 2204) can be indicated. For example, a multi-level user information field may include a subfield of "number of ULTx parameters" (such as...). Figure 17 The number of UL Tx parameter subfields (1704) in the trigger frame indicates their size, similar to the case where only the multi-level user information field is included in the trigger frame. Advantageously, the multi-level user information field 2202 can contain more information compared to the multi-level user information field 2002 (e.g., compared to the case where the multi-level user information field has the same size as the user information field).

[0085] When a non-AP STA receives a trigger frame, if the non-AP STA is addressed by the multi-level user information field in the trigger frame, the non-AP STA should take the following steps: In a non-adaptive manner of processing the trigger frame, the non-AP STA prepares for UL multi-level transmission based on the multiple sets of transmission parameters indicated in the multi-level user information field; in an adaptive manner of processing the trigger frame, the non-AP STA determines whether to transmit the UL multi-level transmission. If the non-AP STA determines not to transmit the UL multi-level transmission, it prepares for the UL transmission based on the multi-level user information field. Otherwise, the non-AP STA prepares for the UL multi-level transmission based on the multiple sets of transmission parameters indicated in the multi-level user information field.

[0086] Figure 23 The present disclosure describes various embodiments of the trigger frame being processed in a non-adaptive manner (e.g., Figure 22a flowchart 2300 of non-AP STA behavior when a trigger frame 2200 is received. At step 2302, the non-AP STA receives the trigger frame. At step 2304, the non-AP STA checks the user info field of the trigger frame. At step 2306, it is determined whether the AID 12 of the user info field (e.g., the value indicated in the AID 12 field of the user info field) matches the AID associated with the non-AP STA. If it is determined that there is a match, the flow proceeds to step 2308, where the non-AP STA obtains the transmission parameters of the checked user info field, and prepares for UL transmission according to the IEEE 802.11 be specification. The flow then ends at step 2320. On the other hand, if it is determined that the AID 12 does not match, the flow proceeds from step 2306 to step 2310, where it is determined whether the AID 12 is equal to 2008. If it is determined that the AID 12 is not equal to 2008, the flow proceeds to step 2312, where it is determined whether there are any unexamined user info fields left in the trigger frame. If it is determined that this is the case, the flow returns to step 2304 to examine another user info field, otherwise the flow ends at step 2320.

[0087] On the other hand, if it is determined at step 2310 that the AID 12 is equal to 2008, the flow proceeds to step 2314, where it is determined whether the actual AID 12 (e.g., the value indicated in the actual AID 12 subfield of the examined multi-layer user info field) matches the AID associated with the non-AP STA. If it is determined that the actual AID 12 does not match, the flow proceeds to step 2312 as described above. If it is determined that the actual AID 12 matches the AID associated with the non-AP STA, the flow proceeds to step 2316, where the non-AP STA obtains the transmission parameters of the examined multi-layer user info field. At step 2318, the non-AP STA prepares for UL multi-layer transmission according to the transmission parameters obtained from the multi-layer user info field, and the flow then ends at step 2320.

[0088] Figure 24 depictions of non-AP STA behavior when a trigger frame (e.g., trigger frame 2200) is received in an adaptive manner, in accordance with various embodiments of the present disclosure. Figure 22FIG. 24 is a flowchart 2400 of non-AP STA behavior when triggered by a trigger frame 2200. At step 2402, the non-AP STA receives the trigger frame. At step 2404, the non-AP STA checks the user info field of the trigger frame. At step 2406, it is determined whether the AID 12 of the user info field (e.g., the value indicated in the AID 12 field of the user info field) matches the AID associated with the non-AP STA. If it is determined that there is a match, the flow proceeds to step 2408, where the non-AP STA obtains the transmission parameters of the checked user info field, and prepares the UL transmission according to the IEEE 802.11 be specification. The flow then ends at step 2424. On the other hand, if it is determined that the AID does not match, the flow proceeds from step 2406 to step 2410, where it is determined whether the AID 12 is equal to 2008. If it is determined that the AID 12 is not equal to 2008, the flow proceeds to step 2412, where it is determined whether there are any unexamined user info fields left in the trigger frame. If it is determined that there is such a case, the flow returns to step 2404 to examine another user info field, otherwise the flow ends at step 2424.

[0089] On the other hand, if it is determined at step 2410 that the AID 12 is equal to 2008, the flow proceeds to step 2414, where it is determined whether the actual AID 12 (e.g., the value indicated in the actual AID 12 subfield of the examined multi-layer user info field) matches the AID associated with the non-AP STA. If it is determined that the actual AID 12 does not match, the flow returns to step 2412, where it is again determined whether there are any unexamined user info fields left in the trigger frame. On the other hand, if it is determined at step 2414 that the actual AID 12 matches the AID associated with the non-AP STA, the flow proceeds to step 2416, where the non-AP STA determines whether an UL multi-layer transmission should be sent (e.g., an adaptive procedure). If it is determined that an UL multi-layer transmission should not be sent, the flow proceeds to step 2418, where the non-AP STA obtains the transmission parameters of the multi-layer user info field, and prepares the UL transmission in the same way as in the IEEE 802.11 be specification, and the flow ends at step 2424. Otherwise, the flow proceeds from step 2416 to step 2420, where the non-AP STA obtains the transmission parameters of the multi-layer user info field, and proceeds to step 2422, where the non-AP STA prepares the UL multi-layer transmission according to the transmission parameters obtained from the multi-layer user info field, and the flow ends at step 2424.

[0090] In one embodiment, when a non-AP STA transmits UL multi-layer transmission in a UHR TB PPDU, the non-AP STA can prepare the UHR TB PPDU in a non-adaptive or adaptive manner. In a non-adaptive manner, the non-AP STA can construct the UHR TB PPDU according to the transmission parameters obtained from the trigger frame. No additional signaling is needed. In an adaptive manner, in a first option, the non-AP STA can construct the UHR TB PPDU according to the transmission parameters obtained from the trigger frame (e.g., all transmission parameters are indicated in the trigger frame). In a first case of the first option, the non-AP STA can indicate the UL multi-layer transmission through signaling in the UHR TB PPDU. In a second case of the first option, the non-AP STA can indicate the UL multi-layer transmission without signaling in the UHR TB PPDU. In a second option of handling the trigger frame in an adaptive manner, the non-AP STA can construct the UHR TB PPDU according to partial transmission parameters obtained from the trigger frame, and decide the parameters by itself. (e.g., partial transmission parameters are indicated in the trigger frame). In a first case of the second option, the transmission parameters for the UL multi-layer transmission can be indicated through signaling in the UHR TB PPDU. In a second case of the second option, the transmission parameters for the UL multi-layer transmission can be indicated without signaling in the UHR TB PPDU.

[0091] According to the first case of the first option as described above, whether the UL transmission is an UL multi-layer transmission can be indicated in the preamble of the UL transmission. Referring to the UL transmission preamble 2500 of Figure 25 , the UL multi-layer transmission flag subfield can be included in the U-SIG field 2502 of the preamble 2500. This is further illustrated in the table 2600 of Figure 26 , where the UL multi-layer transmission flag subfield 2602 can be indicated in bit B20 of U-SIG-1 of the U-SIG field (e.g., the U-SIG field 2502 of the preamble 2500). The AP can decode and demodulate the UHR TB PPDU based on the indication of the UL multi-layer transmission flag subfield. For example, when the UL multi-layer transmission flag subfield is set to 1, it indicates that the UL transmission is an UL multi-layer transmission transmitted by the non-AP STA. When the UL multi-layer transmission flag subfield is set to 0, it is a normal UL transmission transmitted by the non-AP STA. The total RU / MRU size allocated to the non-AP STA can be an integer multiple of 242 tones (20 MHz), so the signaling can be added to the U-SIG field without affecting the transmissions from other non-AP STAs.

[0092] According to a second case of the first option as described above, the AP can identify whether the UL transmission is an UL multi-layer transmission based on the blind decoding result. In this case, no additional signaling is needed in the UHR TB PPDU. The transmission parameters indicated in the trigger frame can be limited (e.g., two different types of transmission parameters indicated when it is used for adaptive processing approach, the first type is the transmission parameters for normal UL transmission if the non-AP STA determines not to transmit UL multi-layer transmission, and the second type is the transmission parameters for UL multi-layer transmission) in order to reduce the decoding complexity of the AP. For example, the total RU / MRU size indicated in the first type of transmission parameters for normal UL transmission and the second type of transmission parameters for UL multi-layer transmission can be different. The AP can identify the UL multi-layer transmission by blind decoding the occupied RU / MRU.

[0093] According to a first case of the second option as described above, the transmission parameters for UL multi-layer transmission can be indicated through signaling in the UHR TB PPDU. For example, referring to the UHT TB PPDU 2700 of Figure 27 , the UL multi-layer transmission parameters subfield can be included in the UHR TB PPDU, as shown by the UL multi-layer transmission parameters subfield 2704 in the U-SIG field 2702 of the UHR TB PPDU 2700. In this case, the total RU / MRU size allocated to the non-AP STA can be an integer multiple of 242 tones (20MHz), so the signaling can be added to the U-SIG field 2702 without affecting the transmissions from other non-AP STAs. Further referring to the UHR TB PPDU 2800 of Figure 28 , the UL multi-layer transmission parameters subfield 2804 can alternatively be included in the new SIG field (e.g., the UHR-SIG field 2802) in the UHR TB PPDU 2800. The advantage of such an implementation is that more signaling bits can be used, thereby enabling more information to be indicated.

[0094] Further, according to the second case of the second option as described above, the transmission parameters for UL multi-layer transmission can be identified by the AP based on the blind decoding results. No additional signaling is needed in the UHR TB PPDU. The transmission parameters indicated in the trigger frame can be limited (e.g., two different types of transmission parameters are indicated when it is used for adaptive processing approach, the first type is the transmission parameters for normal UL transmission if the non-AP STA determines not to transmit UL multi-layer transmission, and the second type is the transmission parameters for UL multi-layer transmission) in order to reduce the decoding complexity of the AP. For example, the total RU / MRU size indicated in the first type of transmission parameters for normal UL transmission and the second type of transmission parameters for UL multi-layer transmission can be different. The AP can identify the UL multi-layer transmission by blind decoding the occupied RUs / MRUs. Further, the transmission parameters decided by the non-AP STA can be limited in order to reduce the decoding complexity of the AP. For example, if the MCS is decided by the non-AP STA, the range of MCSs that can be selected can be limited to "only one MCS index can be selected for the same modulation mapping". Once the constellation point for MCS is detected, the AP can identify the MCS.

[0095] Figure 29 A flowchart 2900 illustrating a method of communication in accordance with various embodiments is shown. At step 2902, a signal is generated for one or more second communication devices, the signal indicating whether uplink signals including two or more transmission layers are requested or enabled. At step 2904, the signal is transmitted to the one or more second communication devices.

[0096] Figure 30 A flowchart 3000 illustrating a method of communication in accordance with various embodiments is shown. At step 3002, a signal is received, the signal indicating whether uplink signals including two or more transmission layers are requested or enabled. At step 3004, the signal is demodulated and decoded to obtain two or more sets of transmission parameters for the uplink signals.

[0097] Figure 31 A schematic, partially sectioned view of a communication device 3100 that can be implemented for service discovery of a local area network in accordance with various embodiments is shown. According to various embodiments, the communication device 3100 can be implemented as a mobile terminal, an application host, a router, a server, a STA, or an AP.

[0098] Various functions and operations of the communication device 3100 are arranged into layers according to a layered model. In this model, lower layers report to and receive instructions from higher layers according to IEEE specifications. Details of the layered model are not discussed in this disclosure for the sake of simplicity.

[0099] As Figure 31As shown, the communication apparatus 3100 can include circuitry 3114, at least one radio transmitter 3102, at least one radio receiver 3104, and a plurality of antennas 3112 (only one antenna is depicted in Figure 31 the interest of simplicity, for the purpose of illustration). The circuitry can include at least one controller 3106 for software and hardware aided performance of tasks it is designed to perform, including control of communications with one or more other devices in a wireless network. The at least one controller 3106 can control at least one transmit signal generator 3108 for generating frames to be transmitted to one or more other STAs or APs through the at least one radio transmitter 3102, and at least one receive signal processor 3110 for processing frames received from one or more other STAs or APs through the at least one radio receiver 3104. The at least one transmit signal generator 3108 and the at least one receive signal processor 3110 can be independent modules of the communication apparatus 3100 that communicate with the at least one controller 3106 to accomplish the above described functions. Alternatively, the at least one transmit signal generator 3108 and the at least one receive signal processor 3110 can be included in the at least one controller 3106. Those skilled in the art will understand that the arrangement of these functional modules is flexible, and can vary depending on the actual needs and / or requirements. Data processing, storage, and other related control apparatus can be provided on an appropriate circuit board and / or in a chip set.

[0100] In various embodiments, the at least one radio transmitter 3102, the at least one radio receiver 3104, and the at least one antenna 3112 can be controlled by the at least one controller 3106. Further, while only one radio transmitter 3102 is shown, it will be understood that there can be more than one such transmitter.

[0101] In various embodiments, the at least one radio receiver 3104, along with the at least one receive signal processor 3110, form a receiver of the communication apparatus 3100. The receiver of the communication apparatus 3100 provides the functionality needed to process information containers. While only one radio receiver 3104 is shown, it will be understood that there can be more than one such receiver.

[0102] The communication apparatus 3100 provides the functionality needed for uplink multi-layer transmissions. For example, the communication apparatus 3100 can be a first communication apparatus, and the circuitry 3114 can generate a signal for one or more second communication apparatuses indicating whether uplink signals including two or more transmission layers are requested or enabled. The transmitter 3102 can transmit the signal to the one or more second communication apparatuses.

[0103] The signal can further include two or more second fields indicating two or more sets of transmission parameters corresponding to two or more transmission layers of the uplink signal, respectively, the two or more second fields being addressed by the same identifier. The signal can include a second field indicating two or more sets of transmission parameters corresponding to two or more transmission layers of the uplink signal. The signal can include a first field indicating whether the uplink signal is requested or enabled, the first field being separate from or included in each of the second field or the two or more second fields. The indication of whether the uplink signal is requested or enabled can be based on a presence of the second field or the two or more second fields, or based on a total number of the sets of transmission parameters. The second field or the two or more second fields can include two or more third fields respectively indicating two or more sets of transmission parameters for two or more transmission layers of the uplink signal. The second field or the two or more second fields can include a fourth field indicating resource unit (RU) allocation information for the two or more sets of transmission layers of the uplink signal. The second field or the two or more second fields can further include a fifth field indicating modulation and coding scheme (MCS) information for the two or more transmission layers of the uplink signal. The second field can further include a sixth field indicating a size of the second field. The receiver 3104 can receive, from one or more second communication devices, the uplink signal including two or more transmission layers, the uplink signal being generated based on the two or more sets of transmission parameters.

[0104] The signal can include a first field indicating whether the uplink signal is requested or enabled and a second field indicating a single set of transmission parameters for the uplink signal including a single transmission layer. The receiver 3104 can receive, from one or more second communication devices, the uplink signal including the single transmission layer, the uplink signal being generated based on the single set of transmission parameters.

[0105] The communication device 3100 can be a second communication device. The receiver 3104 can receive, from a first communication device, a signal indicating whether an uplink signal including two or more transmission layers is requested or enabled. The circuitry 3114 can demodulate and decode the signal to obtain two or more sets of transmission parameters for the uplink signal.

[0106] The circuit 3114 can generate the uplink signal based on the two or more sets of transmission parameters, and the transmitter 3102 can transmit the uplink signal to the first communication apparatus. The generated uplink signal can include a field for indicating whether the generated uplink signal includes the two or more transmission layers.

[0107] The signal can indicate to enable the uplink signal including the two or more transmission layers, and the circuit 3114 can further: obtain, from the signal, a single set of transmission parameters for the uplink signal including a single transmission layer; determine whether to generate the uplink signal including the single transmission layer based on the single set of transmission parameters or to generate the uplink signal including the two or more transmission layers based on the two or more sets of transmission parameters; and generate the uplink signal based on the determination.

[0108] The present disclosure can be realized by software, hardware, or software in cooperation with hardware. Each functional block used in the description of each embodiment described above can be partially or entirely implemented by an integrated circuit (IC) such as LSI (Large Scale Integration), and each process described in each embodiment can be controlled partially or entirely by the same LSI or a combination of LSIs. The LSI can be formed as a chip singularly, or can be formed as one chip so as to include a part or all of the functional blocks. The LSI can include a data input and output coupled thereto. The LSI here can be referred to as an IC, a system LSI, a super LSI, a ultra LSI, a VLSI, or a system on a chip (SoC) according to the degree of integration. However, the technology for integrating the circuit is not limited to the LSI, and can be realized by using a dedicated circuit, a general-purpose processor, or a special-purpose processor. Further, a FPGA (Field Programmable Gate Array) that can be programmed after the manufacture of the LSI, or a reconfigurable processor in which the connections and settings of circuit cells disposed inside the LSI can be reconfigured can be used. The present disclosure can be realized as a digital processing and / or an analog processing. The functional blocks can be integrated with various integrated circuit technologies, which are not limited to those mainly used at present. Biotechnology can also be applied.

[0109] The present disclosure can be realized by any kind of apparatus, device, or system having a communication function, which is referred to as a communication apparatus.

[0110] Some non-limiting examples of such communication devices can include telephones (e.g., cellular (cell) phones, smartphones), tablet computers, personal computers (PCs) (e.g., laptop computers, desktop computers, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices, Head Mounted Displays (HMDs), smartglasses), game consoles, digital book readers, telehealth / telemedicine (remote health and medicine) devices, and vehicles that provide communication functionality (e.g., automobiles, airplanes, ships), as well as various combinations thereof.

[0111] Communication devices are not limited to be portable or movable, and can also include any kind of devices, apparatuses, or systems that are non-portable or stationary, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in a network of "Internet of Things (IoT)".

[0112] Communication can include exchanging data, through, for example, a cellular system, a wireless LAN system, a satellite system, or the like, and various combinations thereof.

[0113] A communication device can include devices such as controllers or sensors that are coupled to a communication device that performs communication functions described in the present disclosure. For example, a communication device can include a controller or a sensor that generates control signals or data signals used by a communication device that performs communication functions of the communication device.

[0114] A communication device can also include infrastructure facilities such as base stations, access points, and any other devices, apparatuses, or systems that communicate with or control devices such as those in the above non-limiting examples.

[0115] Accordingly, it can be seen that the present embodiments provide a communication device and a method for uplink multi-layer transmission.

[0116] While example embodiments have been illustrated in the foregoing detailed description with reference to the accompanying drawings, it will be apparent to those of ordinary skill in the art that numerous modifications can be made without departing from the scope of the subject matter as set forth in the appended claims. Also, it will be understood that the example embodiments are examples and are not intended to limit the scope, applicability, or configuration of the disclosure in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an example embodiment, it being understood that various changes can be made in the function and arrangement of steps and operations described in the example embodiments without departing from the scope of the subject matter as set forth in the appended claims.

Claims

1. A first communication device, comprising: circuitry to generate a signal for one or more second communication devices, the signal indicating whether an uplink signal comprising two or more transmission layers is requested or enabled; and a transmitter to transmit the signal to the one or more second communication devices.

2. The first communication device of claim 1, wherein, the signal further comprising two or more second fields respectively indicating two or more sets of transmission parameters corresponding to the two or more transmission layers of the uplink signal, the two or more second fields being addressed by a same identifier.

3. The first communication device of claim 1, wherein, the signal comprising a second field indicating two or more sets of transmission parameters corresponding to the two or more transmission layers of the uplink signal.

4. The first communication device as claimed in claim 2 or 3, wherein, the signal comprising a first field indicating whether the uplink signal is requested or enabled, the first field being separate from the second field, or each of the two or more second fields, or being included in the second field, or each of the two or more second fields.

5. The first communication device as claimed in claim 2 or 3, wherein, the indication of whether the uplink signal is enabled or requested being based on a presence of the second field, or the two or more second fields, or on a total number of sets of transmission parameters.

6. The first communication device of any one of claims 2 to 5, wherein, the second field, or the two or more second fields, comprising two or more third fields respectively indicating the two or more sets of transmission parameters for the two or more transmission layers of the uplink signal.

7. The first communication device of any one of claims 2 to 6, wherein, the second field, or the two or more second fields, comprising a fourth field indicating resource unit (RU) allocation information for a set of two or more transmission layers of the uplink signal.

8. The first communication device of any one of claims 2 to 7, wherein, the second field, or the two or more second fields, further comprising a fifth field indicating modulation and coding scheme (MCS) information for the two or more transmission layers of the uplink signal.

9. The first communication device of any one of claims 3 to 8, wherein, the second field further comprising a sixth field indicating a size of the second field.

10. The first communication device of any one of claims 2 to 9, further comprising a receiver to receive, from the one or more second communication devices, the uplink signal comprising the two or more transmission layers, the uplink signal being generated based on the two or more sets of transmission parameters.

11. The first communication device of claim 1, wherein, the signal comprising a first field indicating whether the uplink signal is requested or enabled and a second field indicating a single set of transmission parameters for an uplink signal comprising a single transmission layer.

12. The first communication device of claim 11, further comprising a receiver to receive, from the one or more second communication devices, the uplink signal comprising the single transmission layer, the uplink signal being generated based on the single set of transmission parameters.

13. A second communication device, comprising: a receiver that receives a signal from a first communication device, the signal indicating whether an uplink signal including two or more transmission layers is requested or enabled; and circuitry that demodulates and decodes the signal to obtain two or more sets of transmission parameters for the uplink signal.

14. The second communication device of claim 12, wherein, The circuitry generates the uplink signal based on the two or more sets of transmission parameters, the second communication device further comprising a transmitter that transmits the uplink signal to the first communication device.

15. The second communication device of claim 12, wherein, The signal indicates that the uplink signal including the two or more transmission layers is enabled; and the circuitry further: obtains a single set of transmission parameters for an uplink signal including a single transmission layer from the signal; determines whether to generate an uplink signal including a single transmission layer based on the single set of transmission parameters or an uplink signal including two or more transmission layers based on the two or more sets of transmission parameters; and generates the uplink signal based on the determination.

16. The second communication device of claim 14, wherein, The generated uplink signal includes a field indicating whether the generated uplink signal includes two or more transmission layers.

17. A communication method comprising: generating a signal for one or more communication devices, the signal indicating whether an uplink signal including two or more transmission layers is requested or enabled; and transmitting the signal to the one or more communication devices.

18. A communication method comprising: receiving a signal, the signal indicating whether an uplink signal including two or more transmission layers is requested or enabled; and demodulating and decoding the signal to obtain two or more sets of transmission parameters for the uplink signal.

Images