Communication apparatus and communication method for sharing a scheduled period

Abstract

The present disclosure provides a communication apparatus and a communication method for sharing a scheduled period, the communication apparatus, which operates in a first basic service set (BSS), comprising: circuity, which in operation, generates a first frame comprising information to share a part of a scheduled period of the first communication apparatus with a second communication apparatus, which operates in a second BSS, for transmitting one or more frames; and a transceiver, which in operation, transmits the first frame to the second communication apparatus.

Description

[0001] COMMUNICATION APPARATUS AND COMMUNICATION METHOD FOR SHARING A SCHEDULED PERIOD

[0002] TECHNICAL FIELD

[0003] [1] The present disclosure relates to communication apparatuses and methods for sharing a scheduled period, more particularly sharing a target wake time (TWT) service period (SP).

[0004] BACKGROUND

[0005] [2] The IEEE 802.11 standard specifies a target wake time (TWT) operation, which allows an access point (AP) to schedule a service period (SP), during which it can trigger data transmission from stations (STAs) within the basic service set (BSS).

[0006] [3] Building upon this, IEEE 802.11be introduces a restricted target wake time (R-TWT) operation aimed at enhancing protection and resource reservation for the delivery of latency-sensitive (LS) traffic during an SP.

[0007] [4] Currently, the IEEE 802.11 Task Group bn is considering a coordinated restricted TWT (C-R-TWT) operation. This proposed operation would enable multiple APs to coordinate their medium access for R-TWT SPs, thereby providing enhanced delivery of LS traffic.

[0008] [5] However, the conventional techniques still have challenges in achieving efficient data transmissions between APs and / or STAs during a TWT SP.

[0009] [6] Therefore, there is a need for communication apparatuses and methods that provide technical solutions to achieve a more efficient data transmissions between APs and / or STAs during a TWT SP.

[0010] [7] 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.

[0011] SUMMARY [8] In one aspect, the present disclosure refers to a first communication apparatus, which operates in a first basic service set (BSS), comprising, circuity, which in operation, generates a first frame comprising information to share a part of a scheduled period of the first communication apparatus with a second communication apparatus, which operates in a second BSS, for transmitting one or more frames, and a transceiver, which in operation, transmits the first frame to the second communication apparatus.

[0012] [9] In another aspect, the present disclosure refers to a second communication apparatus, which operates in a second BSS, comprising a transceiver, which in operation, receives a first frame, from a first communication apparatus, which operates in a first BSS, comprising information to share a part of a scheduled period of the first communication apparatus with the second communication apparatus for transmitting one or more frames, and transmits the one or more frames during the part of the scheduled period of the first communication apparatus shared with the second communication apparatus.

[0013]

[0010] In yet another aspect, the present disclosure refers to a communication method implemented by a first communication apparatus, which operates in a first BSS, comprising, generating a first frame comprising information to share a part of a scheduled period of the first communication apparatus with a second communication apparatus, which operates in a second BSS, for transmitting one or more frames, and transmitting the first frame to the second communication apparatus.

[0014]

[0011] In yet another aspect, the present disclosure refers to a communication method implemented by a second communication apparatus, which operates in a second BSS, comprising, receiving a first frame, from a first communication apparatus, which operates in a first BSS, comprising information to share a part of a scheduled period of the first communication apparatus, with the second communication apparatus for transmitting one or more frames, and transmitting the one or more frames during the part of the scheduled period of the first communication apparatus shared with the second communication apparatus.

[0015]

[0012] It should be noted that general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.

[0016]

[0013] Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. The benefits and / or advantages may be individually obtained by the various embodiments and features of the specification and drawings, which need not all be provided in order to obtain one or more of such benefits and / or advantages.

[0017] BRIEF DESCRIPTION OF THE DRAWINGS

[0018]

[0014] Embodiments of the disclosure will be better understood and readily apparent to one of ordinary skilled in the art from the following written description, by way of example only, and in conjunction with the drawings, in which:

[0019]

[0015] Figure 1 depicts a schematic diagram illustrating two BSSs (e.g., BSS1 and BSS2), each consisting of an AP (e.g., AP1 and AP2) connected to a STA (e.g., STA1 and STA2respectively).

[0020]

[0016] Figure 2 depicts a time-sequence diagram of an AP (e.g., AP1 ) ending a scheduled period (e.g., TWT SP) early according to at least one alternative method.

[0021]

[0017] Figure 3 depicts a time-sequence diagram according to an embodiment of the present disclosure.

[0022]

[0018] Figure 4 depicts a schematic view of a communication apparatus according to various embodiments of the present disclosure.

[0023]

[0019] Figure 5 shows a flowchart illustrating a communication method implemented by a first communication apparatus (e.g., AP1 ) according to various embodiments of the present disclosure.

[0024]

[0020] Figure 6 shows a flowchart illustrating a communication method implemented by a second communication apparatus (e.g., AP2) according to various embodiments of the present disclosure.

[0025]

[0021] Figure 7 depicts another time-sequence diagram according to an embodiment of the present disclosure.

[0026]

[0022] Figure 8 shows a flowchart illustrating the process where a first communication apparatus (e.g., AP1) coordinates with a second communication apparatus (e.g., AP2) to share a scheduled period (e.g., TWT SP).

[0023] Figure 9 shows a flowchart illustrating the process where a second communication apparatus (e.g., AP2) coordinates with a first communication apparatus (e.g., AP1 ) to share a scheduled period (e.g., TWT SP).

[0027]

[0024] Figure 10 shows an example format of a TWT Setup frame according to an embodiment of the present disclosure.

[0028]

[0025] Figures 11A and 11 B show example formats of a TWT element, e.g., included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0029]

[0026] Figure 12 shows another example format of a TWT element, e.g., included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0030]

[0027] Figure 13 shows yet another example format of a TWT element, e.g., included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0031]

[0028] Figure 14 shows yet another example format of a TWT element, e.g., included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0032]

[0029] Figure 15 shows an example format of an MU-RTS Trigger frame according to an embodiment of the present disclosure.

[0033]

[0030] Figures 16A and 16B show example formats of an MU-RTS TXS Trigger frame according to an embodiment of the present disclosure.

[0034]

[0031] Figures 17A and 17B show example formats of an RTS frame, and a CTS frame, respectively, according to an embodiment of the present disclosure.

[0035]

[0032] Figure 18 shows an example format of a Basic Trigger frame according to an embodiment of the present disclosure.

[0036]

[0033] Figure 19 shows an example format of a QoS Null frame according to an embodiment of the present disclosure.

[0037]

[0034] Figure 20 shows an example format of a Basic TXS Trigger frame according to an embodiment of the present disclosure.

[0038]

[0035] Figure 21 shows an example format of an MU-RTS TXS Trigger frame according to an embodiment of the present disclosure.

[0036] Figure 22 shows another example format of an MU-RTS TXS Trigger frame according to an embodiment of the present disclosure.

[0039]

[0037] Figure 23 depicts a schematic diagram illustrating possible frame transmission sequences according to an embodiment of the present disclosure.

[0040]

[0038] Figure 24 shows yet another example format of a TWT element, e.g., included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0041]

[0039] Figure 25 shows yet another time-sequence diagram according to an embodiment of the present disclosure.

[0042]

[0040] Figure 26A shows yet another example format of a TWT element, e.g., included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0043]

[0041] Figure 26B shows yet another example format of a TWT element, e.g., included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0044]

[0042] Figure 27 shows yet another example format of an MU-RTS TXS Trigger frame according to an embodiment of the present disclosure.

[0045]

[0043] Figure 28 shows another example format of a Basic Trigger frame according to an embodiment of the present disclosure.

[0046]

[0044] Figure 29 shows an example format of a Basic TXS Trigger frame according to an embodiment of the present disclosure.

[0047]

[0045] Figure 30 shows yet another time-sequence diagram according to an embodiment of the present disclosure.

[0048]

[0046] Figure 31 shows yet another time-sequence diagram according to an embodiment of the present disclosure.

[0049]

[0047] Figures 32A and 32B show yet other example formats of a TWT element, e.g. included in a TWT Setup frame, according to an embodiment of the present disclosure.

[0050]

[0048] Figure 33 shows yet another time-sequence diagram according to an embodiment of the present disclosure.

[0049] Figure 34 shows yet another time-sequence diagram according to an embodiment of the present disclosure.

[0051]

[0050] Figure 35 shows yet another time-sequence diagram according to an embodiment of the present disclosure.

[0052]

[0051] Figure 36 shows a flowchart illustrating the process undertaken in evaluating and joining a TWT according to an embodiment of the present disclosure.

[0053]

[0052] Figure 37 shows an example format of a Beacon frame, as an example of an advertise frame, according to an embodiment of the present disclosure.

[0054]

[0053] Figure 38 shows another example format of a TWT element, e.g., included in an advertise frame, according to an embodiment of the present disclosure.

[0055]

[0054] Figure 39 shows yet another example format of a TWT element, e.g., included in an advertise frame, according to an embodiment of the present disclosure.

[0056]

[0055] Figure 40 shows yet another example format of a TWT element, e.g., included in an advertise frame, according to an embodiment of the present disclosure.

[0057]

[0056] Figure 41 shows yet another example format of a TWT element, e.g., included in an advertise frame, according to an embodiment of the present disclosure.

[0058]

[0057] Figure 42 depicts yet another time-sequence diagram according to an embodiment of the present disclosure.

[0059]

[0058] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been depicted to scale. For example, the scale of some of the elements in the illustrations, block diagrams or flow charts may be exaggerated in respect to otherelements to help an accurate understanding of the present embodiments.

[0060] DETAILED DESCRIPTION OF THE EMBODIMENTS

[0061]

[0059] Some embodiments of the present disclosure will be described, by way of example only, with reference to the drawings. Like reference numerals and characters in the drawings refer to like elements or equivalents.

[0060] In the following paragraphs, certain exemplifying embodiments are explained with reference to access points (APs) and stations (STAs) for sharing a scheduled period, especially a TWT SP.

[0062]

[0061] In the context of IEEE 802.11 (Wi-Fi) technologies, a station, which is interchangeably referred to as a STA, is a communication apparatus that has the capability to use the 802.11 protocol. Based on the IEEE 802.11 -2016 definition, a STA can be any device that contains an IEEE 802.11 -conformant media access control (MAC) and physical layer (PHY) interface to the wireless medium (WM).

[0063]

[0062] For example, a STA may be a laptop, a desktop personal computer (PC), a personal digital assistant (PDA), an access point or a Wi-Fi phone in a wireless local area network (WLAN) environment. The STA may be fixed or mobile. In the WLAN environment, the terms “STA”, “wireless client”, “user”, “user device”, and “node” are often used interchangeably.

[0064]

[0063] Likewise, an AP, which may be interchangeably referred to as a wireless access point (WAP) in the context of IEEE 802.11 (Wi-Fi) technologies, is a communication apparatus that allows STAs in a WLAN to connect to a wired network. The AP usually connects to a router (via a wired network) as a standalone device, but it can also be integrated with or employed in the router.

[0065]

[0064] As mentioned above, a STA in a WLAN may work as an AP at a different occasion, and vice versa. This is because communication apparatuses in the context of IEEE 802.11 (Wi-Fi) technologies may include both STA hardware components and AP hardware components. In this manner, the communication apparatuses may switch between a STA mode and an AP mode, based on actual WLAN conditions and / or requirements.

[0066]

[0065] Further, a BSS, which is a fundamental building block of a WLAN as defined by IEEE 802.11 standards, comprises of a single AP and one or more STAs that communicate with each other. The AP serves as the central hub, managing communication and data transmission within the BSS by coordinating access to the wireless medium. Each STA connects to the AP to access network services and communicate with other devices within the same BSS.

[0066] It should be noted that AP1 should be understood as a first communication apparatus, or vice versa, throughout the description. Accordingly, AP2 should be understood as a second communication apparatus. It should be noted that subsequent APs may be described in a similar manner. The BSS and STA in the same BSS of AP1 will be referred to as BSS1 and STA1. It should be noted that other BSS and STA pertaining to other APs will also be named in in a similar manner. For example, AP2 and STA2 should be understood as apparatuses operating in BSS2.

[0067]

[0067] Figure 1 depicts a schematic diagram illustrating a system 100 comprising a BSS 102 (e.g., BSS1 ) and a BSS 152 (e.g., BSS2), each consisting of an AP 104 (e.g., AP1 ) and AP 154 (e.g., AP2) connected to a STA 106 (e.g., AP1 ) and a STA 156 (e.g., STA2) respectively. It should be noted that the Figure 1 is only an example of possible configurations of the BSSs. It should be noted that each BSS could comprise of multiple communication apparatuses (e.g., STAs). Communication apparatuses (e.g., AP1 , AP2, STA1 or STA2) in system 100 may operate on the same or an overlapping wireless channel and they may not all be within the communication range of one another. For example, STA2 may not be within the communication range of AP1 and STA1 , and STA1 may not be within the communication range of AP2 and STA2.

[0068]

[0068] Figure 2 depicts a time-sequence diagram 200 of an AP (e.g., AP1), which operates in a BSS (e.g., BSS1 ) ending a schedule period (e.g., a target wake time (TWT) service period (SP) early according to an alternative method. In the alternative method, AP1 sends an advertise frame 202, which provides information, such as the start time and duration, for an upcoming scheduled period 204 (e.g., a trigger-enabled R-TWT SP). It should be noted that the advertisement 202 from AP1 (e.g., contained in a management frame) hereon may also be referred to as an advertise frame, At the time of the scheduled period (e.g., trigger-enabled R-TWT SP), AP1 contends for the wireless medium and obtains a TXOP (e.g., by sending a Trigger frame) with a TXOP duration 206 for communication with its associated STA (e.g., STA1). It should be noted that the advertise frame may be referred to as a third frame in the present disclosure. The advertise frame may be, e.g., a Beacon frame or Probe Response frame, and may be a unicast frame, a multicast frame or a broadcast frame. It should be noted that the third frame is not described in a sequential order; the indexing is used solely to differentiate between the different frames as disclosed in the claims of the present disclosure.

[0069]

[0069] After completing its communication with STA1, AP1 ends the TXOP duration 206 early by transmitting a contention free-end (CF-End) frame 208. By sending the CF-End frame 208, AP1 indicates the end of its transmissions (e.g., during the TXOP) and in doing so, releases the wireless medium (e.g., TXOP) for use by other devices (e.g., AP2, STA2, STA1 ), thereby allowing the other devices to contend for the medium and transmit their frames. Alternatively, or in addition, the CF-End frame 208 indicates the end of the scheduled period, to allow other devices to determine that the scheduled period has ended early.

[0070]

[0070] A neighbouring AP (e.g., AP2), which operates in a different BSS (e.g., BSS2), that receives the CF-End frame 208 may then contend for medium access to transmit its own frames (e.g., LS data) to its associated STA (e.g., STA2). This mechanism may potentially reduce transmission latency for AP2. Overall, it should be understood that this approach improves the efficiency of medium utilization and can help in reducing delays by allowing neighbouring APs to access the medium once it is no longer in use by another AP.

[0071]

[0071] However, a limitation of the above alternative method is that there are still delays in transmitting the LS data from AP2 to STA2 since AP2 will have to contend for medium access after AP1 transmits the CF-End frame 208.

[0072]

[0072] Figure 3 depicts a time-sequence diagram 300 where an AP (e.g., AP1 ), which operates in a BSS (e.g., BSS1 ) shares its TXOP duration with a neighbouring AP (e.g., AP2), which operates in another BSS (e.g., BSS2), within the scheduled period (e.g., TWT SP) of AP1 . AP1 may share a part of the scheduled period (e.g., TWT SP) with AP2 from BSS2 by sending a frame to share the TXOP to AP2. This sharing mechanism allows AP2 to utilize the medium, which was originally contended by AP1 during API ’s scheduled period, for its own data transmissions or to trigger data from its associated STAs (e.g., STA2). By sharing the TXOP, AP1 allows AP2 to access the medium sooner than it might otherwise be able to, especially in a scenario where medium access is highly contested or prioritized. This cooperative approach thus reduces latency for data delivery by eliminating the need for AP2 to contend for medium access before being able to transmit its LS data, when AP1 already has won contention for the wireless medium. This reduction in latency for data delivery and elimination of the need for AP2 to contend for medium access improves overall network efficiency and performance and reduces delays in data transmission within a BSS due to TXOPs from neighbouring APs during a TWT SP. This is particularly advantageous in dense network environments where multiple APs and STAs are competing for limited bandwidth, and timely data delivery is crucial for certain applications.

[0073]

[0073] Figure 4 depicts a schematic view of a communication apparatus 400 according to the present disclosure.

[0074] As shown in Figure 4, the communication apparatus 400 may include circuitry 402, a transceiver 404 comprising at least one radio transmitter 406 and at least one radio receiver 408, and at least one antenna 410 (for simplicity, only one radio transmitter, radio receiver, and antenna are depicted in Figure 4 for illustration purposes). The circuitry 402 may include at least one controller 412 for use in software and hardware-aided execution of tasks that the at least one controller 412 is designed to perform, including control of communications with one or more other communication apparatuses in a network with sharing of TWT SPs. The circuitry 402 may further include at least one transmission signal generator 414 and at least one receive signal processor 416. The at least one controller 412 may control the at least one transmission signal generator 414 for generating frames and physical layer protocol data units (PPDUs) to be sent through the at least one radio transmitter 406 to one or more other communication apparatuses, where the frames, for example, may include TWT Setup frame, multi-user request to send (MU-RTS) Trigger frame, MU-RTS triggered TXOP sharing (TXS) Trigger frame, request to send (RTS) frame, clear to send (CTS) frame, Basic Trigger frame, quality of service (QoS) Null frame, Basic TXS Trigger frame, Beacon frame, Probe Request frame, Probe Response frame, QoS Data frame; and the PPDUs, for example, may be PPDUs used for non-trigger-based communications, PPDUs used for trigger-based downlink transmissions if the communication apparatus 400 is an AP, or PPDUs used for trigger-based uplink transmissions if the communication apparatus 400 is a STA. Additionally, the PPDUs may be in a duplicate transmission format (e.g., where a transmission may be replicated in two or more channels).

[0074]

[0075] The at least one controller 412 may control the at least one receive signal processor 416 for processing frames and PPDUs received through the at least one radio receiver 408 from one or more other communication apparatuses under the control of the at least one controller 412, where the frames, for example, may include TWT Setup frame, MU-RTS Trigger frame, MU-RTS TXS Trigger frame, RTS frame, CTS frame, Basic Trigger frame, QoS Null frame, Basic TXS Trigger frame, Beacon frame, Probe Request frame, Probe Response frame, QoS Data frame; and the PPDUs, for example, may be PPDUs used for non-trigger-based communications, PPDUs used for trigger-based uplink transmissions if the communication apparatus 400 is an AP, or PPDUs used for triggerbased downlink transmissions if the communication apparatus 400 is a STA. Additionally, the PPDUs may be in a duplicate transmission format (e.g., where a transmission may be replicated in two or more channels).

[0076] The at least one transmission signal generator 414 and the at least one receive signal processor 416 may be stand-alone modules of the communication apparatus 400 that communicate with the at least one controller 412 for the aforementioned functions, as shown in Figure 4. Alternatively, the at least one transmission signal generator 414 and the at least one receive signal processor 416 may be included in the at least one controller 412. It is appreciable to those skilled in the art that the arrangement of these functional modules is flexible and may vary depending on practical needs and / or requirements. The data processing, storage, and other relevant control apparatus can be provided on an appropriate circuit board and / or in chipsets. In various embodiments, when in operation, the transceiver 404 and the at least one antenna 410 may be controlled by the at least one controller 412.

[0075]

[0077] Figure 5 shows a flowchart 500 illustrating a communication method implemented by a first communication apparatus according to various embodiments of the present disclosure. In step 502, a first communication apparatus (e.g., AP1 in 300), which operates in a first BSS (e.g., BSS1 in 300) generates a first frame comprising information to share a part of a scheduled period of the first communication apparatus with a second communication apparatus (e.g., AP2 in 300), which operates in a second BSS (e.g., BSS2 in 300), for transmitting one or more frames. This is followed by step 504, wherein the first frame is transmitted to the second communication apparatus. The first frame, for example, may refer to a TWT Setup frame, a Basic Trigger frame, a Basic TXS trigger frame, an MU- RTS Trigger frame, an MU-RTS TXS Trigger frame or a QoS Null frame. It should be noted that the first frame is not described in a sequential order; the indexing is used solely to differentiate between the different frames as disclosed in the claims of the present disclosure. The first frame, as described herein, may additionally be understood as a share frame (described later) which comprises information to share a part of a scheduled period with another communication apparatus. Additionally, examples of a scheduled period may be, but not limited to, a TWT SP, including e.g., an R-TWT SP or C-R-TWT SP, for the purpose of illustrating the embodiments of the invention. A skilled person should appreciate that the scheduled period may be applied to other types of service periods.

[0076]

[0078] Figure 6 shows a flowchart 600 illustrating a communication method implemented by a second communication apparatus (e.g., AP2 in 300), which operates in a second BSS (e.g., BSS2 in 300) according to various embodiments of the present disclosure. In step 602, the second communication apparatus receives a first frame, from a first communication apparatus (e.g., AP1 in 300), which operates in a first BSS (e.g., BSS1 in 300), comprising information to share a part of a scheduled period of the first communication apparatus, with the second communication apparatus for transmitting one or more frames. This is followed by step 604, wherein the second communication apparatus transmits the one or more frames during the part of the scheduled period of the first communication apparatus shared with the second communication apparatus.

[0077]

[0079] Figure 7 depicts a time-sequence diagram 700 according to an embodiment of the present disclosure. In this embodiment, an AP (e.g., AP1 ), which operates in a BSS (e.g., BSS1) accepts a join request 702 from a neighbouring AP (e.g., AP2), which operates in another BSS (e.g., BSS2), requesting AP1 to share (e.g., by joining a TWT corresponding to its TWT SP) the scheduled period 712 (e.g., a trigger-enabled R-TWT SP) with AP2. It should be noted that the join request 702 (e.g., contained in a management frame) from AP2 hereon may also be referred to as a join frame, whereas the acceptance 704 (e.g., contained in a management frame) of the join request 702 may also be referred to as an accept frame. The accept frame and join frame as disclosed herein may also be referred to as a second frame and a fifth frame, respectively, in the present disclosure. The accept frame and the join frame may be a TWT Setup frame. It should be noted that the second and fifth frames are not described in a sequential order; the indexing is used solely to differentiate between the different frames as disclosed in the claims of the present disclosure. In this embodiment, this process begins before the scheduled period (e.g., trigger-enabled R-TWT SP 712). AP2 from the neighbouring BSS2 sends the join frame 702 to request to be shared the R-TWT SP managed by AP1 . AP1 receives this join frame and sends an accept frame 704 as a response to AP2, accepting AP2 to join in the scheduled period (e.g., trigger-enabled R-TWT SP 712). Upon joining of the scheduled period (e.g., trigger-enabled R-TWT SP 712), AP1 may be expected or required to share the R-TWT SP with AP2, and AP2 may be expected or required to avoid transmitting over the start time of the R-TWT SP to allow priority for AP1 to gain access to the medium.

[0078]

[0080] At the start of the R-TWT SP, AP1 gains access to the medium, e.g., by contending for the wireless medium and obtaining a TXOP, and sends an MU-RTS Trigger frame 706 to AP2, which is followed by AP2 sending a CTS frame 708 to AP1. This exchange is useful for coordinating access and protecting the SP from interference, especially from hidden nodes that might not be aware of the impending transmissions. It should be noted that hidden nodes refer to devices within the wireless network that are not directly within communication range or not detectable to a particular AP due to physical obstructions, distance or interference. It should also be noted that the transmitted MU-RTS Trigger frame 706 from AP1 hereon may also be referred to as a protect frame. After receiving the CTS frame 708, during the R-TWT SP, AP1 shares a part 710 of the TXOP duration with AP2, allowing AP2 to use the medium for its transmissions. The part 710 shared by AP1 with AP2 may be after or before some communication within BSS1 (e.g., a triggered data exchange 716 within BSS1 ), and may be less than or equal to the remaining TXOP duration left in the TXOP.

[0079]

[0081] AP1 shares the R-TWT SP with AP2 by transmitting a frame 714 (e.g., a Trigger frame) to AP2, which enables AP2 to transmit its own frames (e.g., LS data) to the associated station (e.g., STA2) in its BSS (e.g., BSS2). It should be noted that the transmitted frame 714 from AP1 hereon may also be referred to as a share frame. This coordination allows AP2 to serve its LS traffic earlier than it might otherwise be able to, without need for additional contention of the wireless medium by AP2.

[0080]

[0082] Figure 8 shows a flowchart 800 illustrating the process for a first communication apparatus (e.g., AP1 in 700), which coordinates with a second communication apparatus (e.g., AP2 in 700) to share a scheduled period (e.g., TWT SP 712). In step 802, the first communication apparatus receives a join request (e.g., join frame 702) from the second communication apparatus to join a TWT of the first communication apparatus (e.g., a TWT corresponding to TWT SP 712). In step 804, the first communication apparatus responds by sending an accept frame (e.g., 704) to this join request, accepting the request of the second communication apparatus for sharing the TWT SP. In step 806, at the start of the TWT SP, the first communication apparatus contends for the medium, attempting to access the communication channel. In step 808, following the contention, the first communication apparatus transmits a protect frame (e.g., MU-RTS Trigger frame 706) to the second communication apparatus to solicit a CTS frame (e.g., 708) from the second communication apparatus. In step 810, the first communication apparatus receives the CTS frame (e.g., 708) from the second communication apparatus. This MU-RTS / CTS frame exchange protects the TWT SP against potential hidden nodes. In step 812, after the MU-RTS / CTS frame exchange and during the TWT SP, the first communication apparatus transmits a share frame (e.g., Trigger frame 714) to the second communication apparatus, granting it opportunity to transmit frames (e.g., LS data in 700). The protect frame as disclosed herein may be referred to as a fourth frame in the present disclosure. The protect frame may be an MU-RTS Trigger frame, an MU-RTS TXS Trigger frame or an RTS frame. It should be noted that the fourth frame is not described in a sequential order; the indexing is used solely to differentiate between the different frames as disclosed in the claims of the present disclosure.

[0083] Figure 9 shows a flowchart 900 illustrating the process for a second communication apparatus (e.g., AP2 in 700), which coordinates with a first communication apparatus (e.g., AP1 in 700) to share a scheduled period (e.g., TWT SP 712). The process begins in step 902, with the second communication apparatus transmitting a join request (e.g., join frame 702) to a first communication apparatus to request to share the TWT SP of the first communication apparatus. In step 904, the second communication apparatus receives an accept frame (e.g., 704) from the first communication apparatus, accepting the second communication apparatus’ join request. In step 906, during the TWT SP, the second communication apparatus receives a protect frame (e.g., MU-RTS Trigger frame 706) from the first communication apparatus and sends a CTS frame (e.g., 708) back to the first communication apparatus in step 908. This is followed by step 910, where the second communication apparatus receives a share frame (e.g., 714) from the first communication apparatus, granting the second apparatus opportunity for transmission during the TWT SP. In step 912, the second communication apparatus then initiates one or more frame exchanges (e.g., within its own BSS, for LS traffic (e.g., LS data in 700)).

[0081]

[0084] Figure 10 shows an example format of a TWT Setup frame 1000 according to an embodiment of the present disclosure. The TWT Setup frame may be, but is not limited to, a frame transmitted from a second communication apparatus (e.g., AP2 in 700) to a first communication apparatus (e.g., AP1 in 700), wherein the frame is a join frame (e.g., 702) indicating a request to share the scheduled period (e.g., TWT SP 712) of the first communication apparatus. The TWT Setup frame may also be a frame transmitted from the first communication apparatus to the second communication apparatus, wherein the frame is an accept frame (e.g., 704) indicating acceptance of a request to share the scheduled period (e.g., TWT SP 712) of the first communication apparatus.

[0082]

[0085] The TWT Setup frame 1000 comprises a MAC Header field. Within the MAC Header field, the Type field is set to "00", indicating the frame is a "Management" frame, and the Subtype field is set to "1101", specifying the subtype as "Action." The frame further includes a Category field, which is set to "22", indicating that it is an "Unprotected S1 G" management frame. The Unprotected S1 G Action field is set to "6", designating the specific action as "TWT Setup."

[0083]

[0086] Additionally, the TWT Setup frame 1000 includes a Dialog Token field used to match requests and responses between devices. The TWT Setup frame also contains at least one TWT element that provides specific details about a TWT SP, which may include timing and duration parameters. Finally, the frame 1000 includes a frame check sequence (FCS) field, which is used for error detection to ensure the integrity of the data after transmission.

[0084]

[0087] Figures 11A and 11 B show example formats of a TWT element when included in a TWT Setup frame 1000 according to an embodiment of the present disclosure. The TWT Setup frame 1000 may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is an accept frame (e.g., 704), or may be, but is not limited to, a frame transmitted from a second communication apparatus (e.g., AP2 in 700) to a first communication apparatus (e.g., AP1 in 700), wherein the frame is a join frame (e.g., 702). The TWT element in Figure 11 A is an example of a TWT element when included in a join frame (e.g., 702) and the TWT element in Figure 11 B is an example of a TWT element when included in an accept frame (e.g., 704). The TWT elements 1100 and 1150 have the Element ID fields set to "216" to identify the TWT function. Following the Element ID, the Length field specifies the size of the TWT elements.

[0085]

[0088] The Control field within the TWT element contains control-related information essential for the TWT operation. In a join frame requesting sharing of a broadcast TWT SP, such as an R-TWT SP (e.g., TWT SP 712), in the Control field within the TWT element, the Negotiation Type is set to "3", indicating the management of Broadcast TWT memberships, and the TWT Parameter Information field contains a Broadcast TWT Parameter Set field. The Broadcast TWT Parameter Set field comprises a Request Type field, Target Wake Time field, Nominal Minimum TWT Wake Duration Field, TWT Wake Interval Mantissa, Broadcast TWT info field, and Restricted TWT Traffic Info field, wherein the Restricted TWT Traffic Info field includes a Target Wake Time field, Nominal Minimum TWT Wake Duration field, and TWT Wake Interval Mantissa field that have values that are set based on R-TWT SP. In the Broadcast TWT Info field, the Restricted TWT Traffic Info Present is set to “1 ” to indicate that Restricted TWT Traffic Info is present. The Broadcast TWT ID field is set to indicate an ID identifying to the R-TWT SP. For the TWT element in a join frame, the information about the R-TWT SP may have been obtained from a prior frame reception (e.g., an advertise frame) sent by the first communication apparatus (e.g., AP1 in 700). The advertise frame as disclosed herein will be further explained in the embodiments below.

[0086]

[0089] Further, specifically to Figure 11A, the Request Type field within the Broadcast TWT Parameter Set field comprises a TWT Request field set to “1 ” indicating a request to join a TWT, TWT Setup command set to “2” indicating, for example, “Demand TWT", i.e., a demand for the identified TWT, and Trigger field set to “1” to indicate that triggering is enabled during the SP. In Figure 11B, the Request Type field within the Broadcast TWT Parameter Set field comprises a TWT Request field set to “0” indicating that it is a response to a request to join a TWT, TWT Setup command set to “4” indicating “Accept TWT”, i.e., acceptance of the request to join a TWT, and Trigger field set to “1” to indicate that triggering is enabled during the TWT SP. It should be noted that different parameters may be used to indicate different configurations depending on the type of frame.

[0087]

[0090] Figure 12 shows an example format of a TWT element 1200 when included in a TWT Setup frame according to an embodiment of the present disclosure. The TWT Setup frame may be, but is not limited to, a frame transmitted from a second communication apparatus (e.g., AP2 in 700) to a first communication apparatus (e.g., AP1 in 700), wherein the frame is a join frame (e.g., 702). The Restricted TWT Info field comprises a Traffic Info Control field and reserved bits. The reserved bits are present when within the Traffic Info Control field, either or both the DL TID Bitmap Valid field and UL TID Bitmap Valid fields are set to “0” to indicate as invalid. The number of reserved bits may be up to 2 octets and may be used for one or more of such as a Preferred Allocation Duration field, Min Delay Bound field, Preferred Allocation Delay field and an ACI Bitmap field. These different fields indicate the specific configurations required for priority, QoS or urgency indication of the frames (e.g., LS data in 700) to be transmitted by the second communication apparatus (e.g., AP2 in 700).

[0088]

[0091] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may provide information which may cause the first communication apparatus (e.g., AP1 in 700) to share (e.g., by sending share frame 714) the scheduled period (e.g., TWT SP 712) with the second communication apparatus at an earlier or later time or order. For example, information regarding the priority or urgency of the traffic may be included in the join frame (e.g., 702). These may include one or more of such as a Min Delay Bound field to indicate how soon the frames (e.g., LS data in 700) of the second communication apparatus may need to be sent out, a Preferred Allocation Delay field to indicate a delay for when the sharing should occur (e.g., based on a share frame (e.g., Trigger frame 714)) during the SP, and an access category index (ACI) Bitmap field to indicate the access categories (ACs) of the frames (e.g., LS data in 700) of the second communication apparatus to be sent out.

[0092] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may provide information which may affect the duration of the part of the SP (e.g., 710) to be shared by the first communication apparatus (e.g., AP1 in 700) during the scheduled period (e.g., TWT SP 712). For example, a Preferred Allocation Duration field may be included by the second communication apparatus to indicate the desired duration to be shared during the scheduled period. This improve resource management by enabling the first communication apparatus to share the scheduled period appropriately.

[0089]

[0093] In an embodiment, the first communication apparatus (e.g., AP1 in 700) may use the information provided by the second communication apparatus (e.g., AP2 in 700) to determine whether to accept the join request from the second communication apparatus. This avoids accepting a request that cannot be appropriately supported.

[0090]

[0094] In an embodiment the first communication apparatus (e.g., AP1 in 700) may stop serving another communication apparatus during the scheduled period (e.g., TWT SP 712), for example by removing the another communication apparatus from being a member for the R-TWT SP, when accepting join request (e.g., 702) of the second communication apparatus (e.g., AP2 in 700) to join the R-TWT SP. This may be useful in satisfying higher priority needs of the second communication apparatus.

[0091]

[0095] In an embodiment, in the case the TWT may not be trigger-enabled (i.e., Trigger field of the TWT element set to “0” for the TWT), a trigger may still be used as the share frame to share the TWT SP with the second communication apparatus.

[0092]

[0096] Figure 13 shows yet another example format of a TWT element 1300 when included in a TWT Setup frame according to an embodiment of the present disclosure. The TWT Setup frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is an accept frame (e.g., 704). The Restricted TWT Traffic Info field of the Broadcast TWT Parameter Set field comprise a Traffic Info Control field, and reserved bits when the DL TID Bitmap Valid or UL TID Bitmap Valid field is set to “0” to indicate as invalid. The number of reserved bits may be up to 2 octets and may be used to contain a Peer AP ID field. The Peer AP ID field is set to indicate the identifier of another communication apparatus (e.g., AP2), wherein the identifier may have a size of 1 Octet or less. The identifier may be used in the share frame (e.g., 714) from the first communication apparatus (e.g., AP1 in 700) to identify the second communication apparatus (e.g., AP2 in 700) as being shared the allocation (e.g., TXOP duration in 700).

[0097] In an embodiment, a first communication apparatus (e.g., AP1 in 700) may be able to uniquely identify the second communication apparatus (e.g., AP2 in 700) to share its scheduled period (e.g., TWT SP 712). A unique identifier may be provided by the first communication apparatus with the second communication apparatus in the accept frame (e.g., 704) or by another prior exchange (e.g., negotiation for coordinating between APs). This may be useful to differentiate between multiple communication apparatuses being served by the first communication apparatus during the scheduled period.

[0093]

[0098] Figure 14 shows yet another example format of a TWT element 1400 when included in a TWT Setup frame according to an embodiment of the present disclosure. The TWT Setup frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is an accept frame (e.g., 704). The Restricted Traffic Info field of the Broadcast TWT Parameter Set field further comprises a Traffic Info Control field. Within the Traffic Info Control field, a TXOP Return Request field may be set as “1 ” to indicate a request for the shared TXOP duration (e.g., 710) to be returned after use.

[0094]

[0099] In an embodiment, a first communication apparatus (e.g., AP1 in 700), in acceptance of a join request (e.g., join frame 702) from a second communication apparatus (e.g., AP2 in 700) requesting to share a scheduled period (e.g., TWT SP 712) of the first communication apparatus, may transmit a TWT Setup frame (e.g., accept frame 704) to the second communication apparatus, including a TXOP Return Request field set as “1 ” to indicate a request for a return of any remaining TXOP after the second communication apparatus has finished transmitting its frames (e.g., LS data in 700). The second communication apparatus may return the TXOP, for example, by also sending a share frame (e.g., a Trigger frame) to the first communication apparatus. This may allow AP1 to regain access of the allocation and be able to send additional frames if needed. In another embodiment the TXOP return request may be included in the share frame which may allow more dynamic control by AP1 during the scheduled period.

[0095]

[0100] In an embodiment, the information exchanged by the join frame (e.g., 702) and accept frame (e.g., 704) may be implicitly or explicitly included in a separate frame exchange (i.e., not using TWT Setup frames) or agreement between the first communication apparatus (e.g., AP1 in 700) and the second communication apparatus (e.g., AP2 in 700). For example, negotiation for multi-communication apparatus (e.g., AP) coordination may be implemented. This may occur over a wireless medium or over another communication channel (e.g., Ethernet). This may occur through an intermediary or central entity (e.g., multi-AP coordinator or multi-link entity). In such cases, the join frame and accept frame may be omitted from the sequence. This reuses frame exchanges and medium usage.

[0096]

[0101] In an embodiment, the information exchanged by the join frame and accept frame may be implicitly established between the first communication apparatus and the second communication apparatus based on multi-communication apparatus coordination grouping or multi-link device relationship. In such cases, the join frame and accept frame may be omitted from the sequence. This reuses frame exchanges and medium usage.

[0097]

[0102] Figure 15 shows an example format of an MU-RTS Trigger frame 1500 according to an embodiment of the present disclosure. The MU-RTS Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a protect frame (e.g., 706). The MU-RTS Trigger frame begins with a Frame Control field, which includes the Type and Subtype subfields. The Type field is set to "01", indicating a "Control" frame, and the Subtype field is set to "0010", identifying the frame as a "Trigger" frame. Following the Frame Control field, the Duration field specifies the period for which the medium is reserved, helping to coordinate access among multiple devices.

[0098]

[0103] The frame also includes a Receiver Address (RA) field, set to a broadcast address, which indicates that the frame is intended for all devices. Alternatively, the RA may be set to the address of the target communication apparatus. The Transmitter Address (TA) field contains the address of the transmitting communication apparatus (e.g., AP1 of 700), identifying the source of the frame. Within the Common Info field, the Trigger Type is set to "3", indicating the frame's variant as MU-RTS, used for managing multi-user access to the medium. Additionally, the TXS Mode field is set to "0", indicating that the frame does not initiate a TXS procedure.

[0099]

[0104] The User Info List contains one or more User Info fields comprising specific details for each user or device involved in the TXOP. Each User Info field includes an AID12 field (a 12-bit association identifier or encoded value), which identifies a target communication apparatus (e.g., AP2 of 700), and an RU (Resource Unit) Allocation field, which specifies the allocation of channel resources. A Padding field consisting of bits set to “1” may be included to allow sufficient time for the response. The frame concludes with an FCS field for error detection, ensuring data integrity after transmission.

[0105] Figures 16A and 16B show example formats of an MU-RTS TXS Trigger frame according to an embodiment of the present disclosure. The MU-RTS Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a protect frame (e.g., 706) or a share frame (e.g., 714). Building upon the fields already described in MU-RTS Trigger frame of Figure 14, the MU-RTS TXS Trigger frame contains additional fields and functionalities. The Common Info field includes the Trigger Type, set to "3" for MU-RTS variant, and the TXS Mode may be set to indicate whether a scheduled AP can transmit within its own BSS.

[0100]

[0106] Within the User Info List, one or more User Info fields comprising specific details for each user or device involved in the TXOP. Each User Info field includes the AID12 field, which identifies a target communication apparatus (e.g., AP2 of 700), and the RU Allocation, which provides information about the resources units (RUs) to be allocated. The information about the RUs may include such as the channel and bandwidth information. Additionally, there is an Allocation Duration field that may be set to indicate the length of time to be allocated to the target communication apparatus.

[0101]

[0107] Referring to MU-RTS TXS Trigger frame 1600 of Figure 16A, e.g., when transmitted at the start of the scheduled period as a protect frame (e.g., 706), the Allocation Duration field may specify a duration, or indicate no allocation with a "0". Indicating a “0” may inform the recipient that the allocation does not start immediately following this frame. The frame may also include a field indicating a delayed start of the allocation such as a 1 -bit Delayed field, which may be set to “1 ” to indicate that the start of the allocation is delayed, or an Allocation Start Delay field, composed of, e.g., 9 bits, which specifies a delay duration before the shared allocation (e.g., 710) begins, providing more control over scheduling.

[0102]

[0108] Referring to MU-RTS TXS Trigger frame 1650 of Figure 16B, e.g., when transmitted as a share frame (e.g., 714), the Common Info field includes a TXS mode which is set to indicate that the scheduled AP can transmit in its own BSS. The one or more User Info field within the User Info List field includes an AID12 field that indicates an ID for the target communication apparatus (e.g., AP2 of 700).

[0103]

[0109] In an embodiment, a first communication apparatus (e.g., AP1 in 700) may share the scheduled period (e.g., TWT SP 712) with the second communication apparatus (e.g., AP2 in 700) to send LS data (e.g., LS data in 700) by sending an MU-RTS TXS Trigger frame (e.g., 714). The second communication apparatus may respond with a CTS frame before proceeding to use the TWT SP.

[0104]

[0110] In an embodiment, the Allocation Duration field in an MU-RTS TXS Trigger frame, e.g., as a protect frame (e.g., 706) or share frame (e.g., 714), and may be set to allocate all or part of the remaining duration in the scheduled SP (e.g., TWT SP 712).

[0105]

[0111] In an embodiment, the first communication apparatus (e.g., AP1 in 700) may use an MU-RTS TXS Trigger frame (e.g., 1600), e.g., as a protect frame or share frame, and indicate the intended allocation duration and the RU to be shared with the second communication apparatus (e.g., AP2 in 700 during the scheduled period (e.g., TWT SP 712). It may indicate a delayed start, e.g., by flag (i.e., a 1 -bit indication field) or duration field, wherein a flag uses less bits in the frame and may allow the first communication apparatus more flexibility during the scheduled period and a duration field uses more bits but provides more information which may have other benefits (e.g., the second communication apparatus may save power while waiting for the expected allocation start). Another alternative may be to set the Allocation Duration field to “0” which uses no additional bits but does not indicate an intended allocation duration. These options provide more flexibility for the sharing.

[0106]

[0112] Figures 17A and 17B show example formats of an RTS frame, and a CTS frame, respectively, according to an embodiment of the present disclosure. The RTS frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a protect frame (e.g., 706). The RTS frame 1700 starts with a Frame Control field that includes the Type field set to "01" for control frames and the Subtype field set to "1011 ”, indicating that it is an RTS frame. The Duration field specifies the period for which the medium is requested. The RA field contains the address of the target communication apparatus that the transmitting device intends to communicate with, while the TA field holds the address of the communication apparatus transmitting the RTS frame. The frame ends with an FCS field, which is used for error detection.

[0107]

[0113] The CTS frame 1750 may be, but is not limited to, a frame transmitted from a second communication apparatus (e.g., AP2 in 700) to a first communication apparatus (e.g., AP1 in 700), wherein the frame is a response to a protect frame (e.g., an RTS, MU- RTS Trigger or MU-RTS TXS Trigger frame) or share frame (e.g., an MU-RTS TXS Trigger), and it may be, but is not limited to, a frame transmitted from a first communication apparatus to a second communication apparatus, wherein the frame is a share frame (e.g., 714). The Frame Control field in the CTS frame also has the Type field set to "01" for control frames, but the Subtype field is set to "1100", distinguishing it as a CTS frame. The Duration field, when sent as a response, is set based on the content of the frame it is in response to (e.g., RTS, MU-RTS Trigger, MU-RTS TXS Trigger), and the RA field contains the TA from the frame it is in response to (e.g., RTS, MU-RTS Trigger, MU-RTS TXS Trigger). The Duration field, when not sent as a response, e.g., but as a share frame, is set based on the duration to be shared (e.g., 710), and the RA field may be set to the address of the target communication apparatus for the sharing. The CTS frame concludes with an FCS field for error detection.

[0108]

[0114] In an embodiment, the first communication apparatus (e.g., AP1 in 700) may use an RTS frame at the start of the scheduled period as the protect frame (e.g., 706), to solicit a CTS frame from only the second communication apparatus (e.g., AP2 in 700). This may be a simpler option compared to using a Trigger frame when sharing the scheduled period with only one neighbouring communication apparatus (e.g., the second communication apparatus).

[0109]

[0115] In an embodiment, the second communication apparatus (e.g., AP2 in 700) transmits a CTS frame in response to the protect frame, e.g., an RTS, MU-RTS Trigger or MU-RTS TXS Trigger frame from the first communication apparatus (e.g., AP1 in 700). This provides hidden node protection in the channel.

[0110]

[0116] In an embodiment, the CTS frame may also be sent in a duplicate format (e.g., non-HT duplicate PPDU) over multiple channels to extend hidden node protection to those channels. It should be noted that duplicate format transmission refers to a format of transmission where the transmission may be replicated in two or more channels to be received.

[0111]

[0117] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may determine not to transmit the CTS frame in response to the protect frame (e.g., MU-RTS Trigger frame 706) if the second communication apparatus does not have frames (e.g., LS data in 700) to send during the scheduled period or if the intended shared allocation parameters, e.g., allocation duration, is determined to be not suitable.

[0112]

[0118] Figure 18 shows an example format of a Basic Trigger frame 1800 according to an embodiment of the present disclosure. The Basic Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a share frame (e.g., 714). The Basic Trigger frame begins with a Frame Control field, which includes the Type field set to "01" for control frames and the Subtype field set to "0010", indicating it is a Trigger frame. The Duration field specifies the time period for which the medium is reserved, providing necessary timing information for coordinating access.

[0113]

[0119] The Basic Trigger frame 1800 also includes an RA field, containing the address of the target communication apparatus (e.g., AP2 in 700) that is intended to receive the communication and may be a broadcast address when including one or more User Info fields, e.g., to target multiple communication apparatuses. The TA field specifies the address of the communication apparatus (e.g., AP1 in 700) sending the frame. Within the Common Info field, the Trigger Type is set to "0", indicating that it is a Basic variant, which can be used for basic triggering.

[0114]

[0120] The User Info List field, which may be optionally included, provides specific details for each user or device involved in the transmission. Each User Info field within this list contains an AID12 field that identifies the specific target communication apparatus, along with an RU Allocation field that specifies the allocation of RUs based on the intended communication.

[0115]

[0121] The frame may also include a Padding field to allow sufficient time for the response. The frame concludes with an FCS field, which is used for error detection, ensuring the integrity of the frame after transmission.

[0116]

[0122] Figure 19 shows an example format of a QoS Null frame 1900 according to an embodiment of the present disclosure. The QoS Null frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a share frame (e.g., 714). The QoS Null frame begins with a Frame Control field, which includes the Type field set to "10", indicating a Data frame, and the Subtype field set to "1100", specifying the frame as a QoS Null frame. The Duration field indicates the time for which the medium is reserved.

[0117]

[0123] Three address fields (Address 1 , Address 2, and Address 3) follow, which are typically used for identifying the source, destination, and possibly a third entity like a transmitting AP or a BSSID (basic service set Identifier). The Sequence Control field provides sequencing information to ensure proper order and manage duplicate frames.

[0124] The QoS Control field carries information specific to quality of service, such as priority levels and traffic identifier information, which helps manage the handling of data streams according to their importance or requirements. The HT Control field is used for control-related information.

[0118]

[0125] Within the HT Control frame is a HE Variant field, which includes an A-Control subfield. Within the A-Control subfield, there are Control ID and Control Information fields.

[0119]

[0126] In an embodiment, a Basic Trigger, CTS or QoS Null frame may be used to allocate all the remaining TXOP to the second communication apparatus, or based on information exchanged before (e.g., allocation duration indicated in the previously exchanged protect frame (e.g., 706), join frame (e.g. 702) or accept frame (e.g., 704), part of it. This reduces processing and transmission overhead.

[0120]

[0127] In an embodiment, the QoS Null frame may define a new value for the Control ID field in the A-Control field and relevant parameters in the Control Information field to carry information regarding the allocation sharing (e.g., allocation duration).

[0121]

[0128] Figure 20 shows an example format of a modified Basic Trigger frame for sharing hereon known as a Basic TXS Trigger frame 2000 according to an embodiment of the present disclosure. The Basic TXS Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a share frame (e.g., 714). The Basic TXS Trigger frame begins with a Frame Control field, which includes the Type field set to "01" indicating a control frame, and the Subtype field set to "0010", identifying it specifically as a Trigger frame. The Duration field specifies the period for which the medium is reserved.

[0122]

[0129] Following these initial fields, the frame includes an RA field, which may contain the address of the target communication apparatus or the broadcast address. Alternatively, the RA may be set to the address of the target communication apparatus. The TA field identifies the address of the communication apparatus sending the frame. The Common Info field includes a Trigger Type set to "0", indicating it is a Basic variant, and a TXS Mode field that provides information on whether the scheduled AP can transmit within its own BSS. As an alternative, a new Trigger Type value may be added to indicate it as a Basic TXS variant.

[0130] The User Info List field contains one or more User Info fields, which provide specific details about the users or devices involved in the transmission. Each User Info field includes an AID12 field that identifies a target communication apparatus, an RU Allocation field specifying the RUs allocated for the transmission, and an Allocation Duration field that indicates the allocated duration for the transmission activities.

[0123]

[0131] Additionally, the frame may include a Padding field, which may be included to ensure sufficient time for the response, and an FCS field, which provides error detection capabilities to maintain data integrity after transmission.

[0124]

[0132] In an embodiment, a Basic Trigger frame may be modified (e.g., to a Basic TXS Trigger frame) to include fields similar to the MU-RTS TXS Trigger frame but not soliciting a CTS frame. This may be beneficial for indicating a sharing of the TXOP in advance or to share the TXOP without additionally soliciting a CTS frame (e.g., to avoid repeated CTS within the same TXOP).

[0125]

[0133] Figure 21 shows an example format of an MU-RTS TXS Trigger frame 2100 according to an embodiment of the present disclosure. The MU-RTS TXS Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a share frame (e.g., 714). Within this frame, an additional field, Response Not Required, is included, which may be set to "1 " (e.g., indicating true) such that the recipient does not send an immediate response (e.g., a CTS frame 708). This may be used to avoid soliciting a CTS frame for a second time during the same TXOP. The Response Not Required field may be contained in the User Info field to solicit different behaviour for multiple target recipients.

[0126]

[0134] In an embodiment, an MU-RTS TXS Trigger frame (e.g., share frame 714) may indicate that a CTS response is not required, such that it may be disallowed or optional for the second communication apparatus to send a CTS response. This may be used, e.g., to avoid soliciting a second CTS within the same TXOP from the second communication apparatus.

[0127]

[0135] Figure 22 shows another example format of an MU-RTS TXS Trigger frame according to an embodiment of the present disclosure. The MU-RTS TXS Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is a share frame (e.g., 714). Within the User Info field of this frame, the Allocation Duration field may be set to the duration to be allocated, or as “0”, which may indicate sharing the full remaining duration of the TXOP or to allow a predetermined frame sequence. An Allocation Start Delay field is included in the frame, consisting of 9 bits, to specify a delay period before or time when the allocation duration begins.

[0128]

[0136] In an embodiment, the MU-RTS TXS Trigger frame (e.g., share frame 714) may indicate an allocation start delay to inform the second communication apparatus (e.g., AP2 in 700) of a delayed start of the allocation to be shared. If a start delay duration or time is specified, the second communication apparatus may start using the allocation once the delay period is completed or time is reached. This may provide advance notice to the second communication apparatus or allow use of the time before the delayed allocation to be used for other purposes.

[0129]

[0137] In an embodiment, the MU-RTS TXS Trigger frame (e.g., share frame 714) may include multiple User Info fields intended for one or more neighbouring APs (e.g., including AP2 in 700) that may be involved in the scheduled period. Allocations may be sequentially shared based on the order of the User Info field and the time to start each allocation may be determined from based on the Allocation Duration field of the User Info fields or by including an Allocation Start Delay field in the User Info fields. In the case of multiple neighbouring APs using the same RU, the CTS may be sent by the one or more neighbouring APs, based on Allocation Delay or based on a flag to indicate a response is not required (e.g., Response Not Required field included the User Info field in 2100). This allows the sharing of the scheduled period with multiple communication apparatuses efficiently based on a single share frame.

[0130]

[0138] Figure 23 depicts a diagram 2300 illustrating exemplifying sequences for a protect frame transmitted before the shared period (e.g., at the beginning of a scheduled period) and a share frame to share the TXOP during the scheduled period.

[0131]

[0139] The links between the frame options show potential sequence combinations, illustrating how one frame type or action can link to another. While not all possible sequences are shown to be linked, however, it should be noted that other pathways beyond those explicitly depicted may also be valid. In some sequences, possible benefits may include reduced CTS transmission overhead, simplified frames transmitted, and more information provided. It should be noted that a link does not imply an immediately consecutive sequence but rather is an indication of an order of the sequence. The use of each link may have different characteristics which are suitable in different scenarios.

[0132]

[0140] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may transmit or receive LS traffic or data within its own BSS (e.g., BSS2 in 700) using the shared allocation (e.g., 710) during the scheduled period (e.g., TWT SP 712) of a neighbouring AP (e.g., AP1 ). LS data or traffic may be determined or identified at the AP or STA originating the traffic. This may allow LS traffic to reduce transmission latency during the scheduled period of the neighbouring AP. The LS traffic may be periodic and may be expected to be sent out during or around the time of the scheduled period.

[0133]

[0141] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may fully utilize the shared allocation (e.g., 710) during the scheduled period (e.g., TWT SP 712). This allows AP2 to clear as much of its transmit buffer during the shared allocation.

[0134]

[0142] In an embodiment, non-LS data may also be transmitted by the second communication apparatus (e.g., AP2 in 700) during the shared allocation (e.g., 710) within the scheduled period (e.g., TWT SP 712) when there is no LS data to be transmitted. This may help efficient utilization of the medium since a separate contention of the medium may be avoided.

[0135]

[0143] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may release excess time in the shared allocation (e.g., 710) by, for example, sending a CF- End frame after it has finished using the shared allocation. This allows other communication apparatuses to contend and use the wireless medium before the original end of the shared allocation.

[0136]

[0144] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may return the TXOP of the first communication apparatus (e.g., AP1 in 700) by, for example, sending, e.g., a Trigger frame, CTS or QoS Null frame, to the first communication apparatus after it has finished its use of the allocation. This may have been requested by the first communication apparatus during the acceptance of the request to join the scheduled period of the first communication apparatus (e.g., accept frame 704) or during the advertisement of the scheduled period (e.g., advertise frame). This allows the first communication apparatus to regain control of the allocation and use it for other purposes.

[0145] Figure 24 shows yet another example format of a TWT element 2400 when included in a TWT Setup frame according to an embodiment of the present disclosure. The TWT Setup frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 700) to a second communication apparatus (e.g., AP2 in 700), wherein the frame is an accept frame (e.g., 704). Within the TWT Parameter Information field of the TWT element, the Request Type field specifies the nature of the TWT request. For example, a TWT Request value of "0" indicates a response to the request to join a TWT. The Trigger field, set to "1", indicates that triggering is enabled during the SP. The Broadcast TWT Recommendation field may indicate a value indicating that peer AP triggering is allowed, to indicate whether peer APs are permitted to trigger another AP, or STA, during the shared allocation to share the shared allocation (e.g., 710). An alternative may be to include a dedicated Peer AP Trigger Allowed field in the Traffic Info Control field of the Restricted TWT Traffic Info field. The Peer AP Trigger Allowed field may indicate whether the peer AP triggering another communication apparatus to share the shared allocation (e.g., 710) is allowed, for example, indicating by a value of "1" to indicate it is allowed. Another alternative may be is to include a Peer AP Trigger Allowed field using the Restricted TWT Traffic Info field, which has more reserved bits than in the existing Traffic Info Control field when setting the DL TID Bitmap Valid field (or UL TID Bitmap Valid) in the Traffic Info Control to “0” indicating invalid. The Peer AP Trigger Allowed field may also use more than 1 bit to indicate more specific or granular behaviour allowed during the shared allocation.

[0137]

[0146] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may trigger STAs in its own BSS (e.g., BSS2 in 700) for transmitting LS data during the shared allocation (e.g., 710). This may be allowed by default or may be permitted based on content of the accept frame or the advertise frame from the first communication apparatus (e.g., AP1 ). For example, based on indications in the Broadcast TWT Recommendation field, or a dedicated field (e.g., Peer AP Trigger Allowed field indicating peer AP triggering allowed, in the TWT element). This allows the first communication apparatus to manage the behaviour during the shared allocation and limit the behaviour of the second communication apparatus in certain scenarios.

[0138]

[0147] In an embodiment, the second communication apparatus (e.g., AP2 in 700) may trigger a third communication apparatus (e.g., AP3) to share the allocation shared by AP1 with AP2, with AP3. This may be allowed by default or may be permitted based on content in the accept frame or advertise frame from the first communication apparatus (e.g., AP1 in 700). This may provide a third communication apparatus with time to transmit its frames during the scheduled period. The third communication apparatus may be decided by the second communication apparatus or may be decided based on information from the first communication apparatus, e.g., in the share frame (e.g., 714), such as based on the User Info List field of the TWT element.

[0139]

[0148] Figure 25 shows another time-sequence diagram 2500 according to an embodiment of the present disclosure. The sequence begins with a second communication apparatus (e.g., AP2), which operates in a second BSS (e.g., BSS2) sending a join frame 2502 to a first communication apparatus (e.g., AP1 ) , which operates in a first BSS (e.g., BSS1 ), to request to be shared the scheduled period 2504 (e.g., R- TWT SP), including a request for resource unit (RU) allocation or specific channel allocation. This join request is responded to by the first communication apparatus sending an accept frame 2506, which may include details about the RU or channel allocation to be shared. During the shared TWT SP, AP1 transmits a share frame to AP2, enabling AP2 to transmit frames (e.g., LS data) to its associated STA (e.g., STA2) in BSS2.

[0140]

[0149] In an embodiment, the first communication apparatus (e.g., AP1 in 2500) triggers the second communication apparatus (e.g., AP2 in 2500) to allow it to transmit frames in its BSS in a specific channel (e.g., AP2’s primary channel). During the shared allocation, AP2 proceeds to use only the allocated RUs or channels allocated by AP1. This allows AP1 to continue to use or share other RUs or channels which were not shared with AP2 in the same time allocation.

[0141]

[0150] In an embodiment, during the request to join (e.g., sending a join frame 2502), the second communication apparatus (e.g., AP2) may request one or more specific channels to be allocated (i.e., shared) during the scheduled period 2504 (e.g., R-TWT SP). It should be noted that a channel may comprise one or more smaller channels, including e.g., a wider channel and a punctured channel. Further, a channel may be primary or nonprimary channel. It should be noted that a primary channel refers to a channel that may be a main, common or expected channel of communication for the BSS or device.

[0142]

[0151] In an embodiment, the first communication apparatus (e.g., AP1 ) may not solicit a CTS from its associated STA (e.g., STA1 ), by not sending the protect frame (e.g., MU- RTS Trigger frame).

[0143]

[0152] In an embodiment, the CTS frames from STA1 and AP2 may be transmitted in non- HT duplicate format (e.g., non-HT duplicate PPDU) over two or more channels. Alternatively, the CTS frame from may be only on a specific channel, e.g., STA1 may transmit CTS on channels or RUs not shared with AP2.

[0144]

[0153] In an embodiment, the second communication apparatus (e.g., AP2) may have prepared the recipient of the LS data (e.g., STA2) to receive in the allocated channel during the shared allocation (e.g., by providing information such as operating channel or a scheduled period advertised by AP2), prior to the scheduled period.

[0145]

[0154] The advantageous effect of the arrangement of Figure 25 would be that the scheduled period (e.g., R-TWT) can be used to serve multiple BSS’s traffic (e.g., LS traffic) concurrently over multiple channels in the same time allocation.

[0146]

[0155] Figure 26A shows yet another example format of a TWT element 2600 when included in a TWT Setup frame, according to an embodiment of the present disclosure. The TWT setup frame may be, but is not limited to, a frame transmitted from a second communication apparatus (e.g., AP2 in 2500) to a first communication apparatus (e.g., AP1 in 2500), wherein the frame is a join frame (e.g., 2502). Within the Control field, the Negotiation Type field is set to “3”, indicating that the element is used to manage Broadcast TWT memberships. The Request Type field within the Broadcast TWT Parameter Set field comprises TWT Request field set to "1" for requesting or scheduling STAs, and a TWT Setup Command field set to "2" for “Demand TWT”. The Trigger field set to "1" indicates that triggering is enabled during the TWT SP.

[0147]

[0156] The Broadcast TWT Info field within the Broadcast TWT Parameter Set field of the TWT element 2600 includes a Broadcast TWT Persistence field which may be reused to include an RU Allocation field or, alternatively, a TWT Channel field, to indicate requested RUs or channel and bandwidth. The TWT Channel field may use a bitmap format to indicate the different channels and bandwidth options, e.g., it may be similar to an existing TWT Channel field of the Individual TWT Parameter Set field of a TWT element in the IEEE 802.11 standard.

[0148]

[0157] Figure 26B shows yet another example format of a TWT element 2650 when included in a TWT Setup frame, according to an embodiment of the present disclosure. The TWT Setup frame 2650 may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 2500) to a second communication apparatus (e.g., AP2 in 2500), wherein the frame is an accept frame (e.g., 2502). The Request Type field within the Broadcast TWT Parameter Set field specifies that TWT Request is set to "0" for responding or scheduling STAs and a TWT Setup Command field set to "4" for “Accept TWT”. The Trigger field set to "1" indicates that triggering is enabled during the TWT SP.

[0149]

[0158] The Broadcast TWT Info field within the Broadcast TWT Parameter Set field of the TWT element 2650 may include a Broadcast TWT Persistence field which may be reused to include an RU Allocation field or, alternatively, a TWT Channel field, which indicates RUs or channel and bandwidth to be allocated for the shared allocation. The TWT Channel field may use a bitmap format to indicate the different channels and bandwidth options, e.g., it may be similar to an existing TWT Channel field of the Individual TWT Parameter Set field of a TWT element in the IEEE 802.11 standard.

[0150]

[0159] In an embodiment, the Broadcast TWT Persistence field (1 octet) may be reused to contain information about a requested channel or RU. For example, when Negotiation Type field is “3”, TWT Request is “1”, and it is transmitted by an AP (e.g., AP2 in 2500) to the TWT responding / scheduling AP (e.g., AP1 in 2500), the RU Allocation is present and includes RUs to be shared for the shared allocation. Alternatively, a TWT Channel field may include the accepted channel and bandwidth to be shared for the shared allocation.

[0151]

[0160] In an embodiment, the Broadcast TWT Persistence field (1 octet) may be reused to contain information about the accepted channel. For example, when Negotiation Type is “3”, TWT Request is “0” and it is transmitted by an AP (e.g., AP1 in 2500) to the TWT requesting / scheduled STA (e.g., AP2 in 2500), the RU Allocation is present and includes RUs to be shared for the shared allocation. Alternatively, a TWT Channel field may be present and include the requested channel and bandwidth to be shared for the shared allocation.

[0152]

[0161] In an embodiment, the protect frame (e.g., MU-RTS in 2500) is transmitted in a channel covering the intended channel to be allocated. This ensures hidden node protection for the channel to be allocated.

[0153]

[0162] In an embodiment, the protect frame (e.g., MU-RTS in 2500) may be transmitted in duplicate format (e.g., non-HT duplicate PPDU) e.g., transmitted over two or more channels used in the scheduled period. This ensures hidden node protection for the channel to be allocated.

[0154]

[0163] In an embodiment, the first communication apparatus (e.g., AP1 in 2500) may set the RU Allocation field for the second communication apparatus (e.g., AP2 in 2500) in the accept frame 2506, based on one or more RUs or channels requested in the join frame (e.g., 2502). The RU allocations or channels may be same as or covering less than requested by AP2.

[0155]

[0164] In an embodiment, the protect frame (e.g., MU-RTS Trigger frame) may indicate the allocated channel and the second communication apparatus (e.g., AP2 in 2500) switches to the channel following this step. This may give time for AP2 to switch prior to receiving the share frame (e.g., Trigger in 2500).

[0156]

[0165] Figure 27 shows an example format of an MU-RTS TXS Trigger frame 2700 according to an embodiment of the present disclosure. The MU-RTS TXS Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 2500) to a second communication apparatus (e.g., AP2 in 2500), wherein the frame is a share frame (e.g., Trigger in 2500). The Common Info field includes a Trigger Type set to "3", identifying it as an MU-RTS variant, and a TXS Mode that indicates that the scheduled AP can transmit within its own BSS. The User Info List field comprises detailed information for each user or device involved in the transmission. Each User Info field includes an AID12 field that identifies a target communication apparatus. It also includes an RU Allocation field that specifies the RUs allocated for the transmission. The Allocation Duration field details the allocated duration for the transmission, indicating how long the allocated resource allocation will last.

[0157]

[0166] Figure 28 shows an example format of a Basic Trigger frame 2800 according to an embodiment of the present disclosure. The Basic Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 2500) to a second communication apparatus (e.g., AP2 in 2500), wherein the frame is a share frame (e.g., Trigger in 2500). Within the Common Info field, the Trigger Type is set to "0", indicating it is a Basic variant. The User Info List field, which may be optionally included, provides specific information for each user or device involved in the transmission. Each User Info field includes an AID12 field that identifies a target communication apparatus, ensuring the frame reaches the correct recipient. Additionally, the RU Allocation field specifies the RUs allocated for the transmission.

[0158]

[0167] Figure 29 shows an example format of a Basic TXS Trigger frame 2900 according to an embodiment of the present disclosure. The Basic TXS Trigger frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 2500) to a second communication apparatus (e.g., AP2 in 2500), wherein the frame is a share frame (e.g., Trigger in 2500). Within the Common Info field, the Trigger Type is set to "0", indicating it is a Basic variant. The TXS Mode field specifies whether the scheduled AP (e.g., AP2 in 2500) can transmit within its own BSS (e.g., BSS2 in 2500). The User Info List field, which includes one or more User Info fields, includes the AID12 field, identifying the target communication apparatus, and the RU Allocation field, which specifies the RUs allocated for the transmission. Additionally, there is an Allocation Duration field indicating the allocated duration for the transmission.

[0159]

[0168] In an embodiment, the share frame (e.g., Trigger in 2500) may be transmitted in a channel covering the intended channel to be allocated. The RU allocation is set to indicate the intended RUs allocated. The second communication apparatus (e.g., AP2 in 2500), upon receipt of the share frame, may switch to the intended channel after this trigger. This allows the second communication apparatus to switch channels dynamically only when the allocation is shared.

[0160]

[0169] In an embodiment, the share frame (e.g., Trigger in 2500) may be transmitted only in the intended channel to be allocated. In this case, the second communication apparatus (e.g., AP2 in 2500) receiving the share frame may have already switched to the intended channel based on the accept (e.g., 2506) or the protect frame (e.g., MU-RTS in 2500). This may reduce delays due to switching channels after receiving the share frame.

[0161]

[0170] In an embodiment, the share frame (e.g., Trigger in 2500) may be transmitted in duplicate format (e.g., non-HT duplicate PPDU) by the first communication apparatus (e.g., AP1 in 2500). For example, transmitted over two or more channels to be allocated in the shared allocation. In this case, the second communication apparatus (e.g., AP2 in 2500) receiving the share frames may have already switched to the intended channel based on the accept frame (e.g., 2506) or the protect frame (e.g., MU-RTS in 2500). This may allow AP1 to address multiple target communication apparatuses.

[0162]

[0171] In an embodiment, the share frame (e.g., Trigger in 2500) may be transmitted, by the first communication apparatus (e.g., AP1 in 2500), in a channel not covering the intended channel to be allocated. In such a case, the second communication apparatus (e.g., AP2 in 2500) receiving the share frame may be required to perform clear channel assessment (CCA) on the intended channel before proceeding to use the shared allocation in the intended channel. This may allow AP1 to simplify its operation to only use the channel not covering the intended channel to be allocated, or to reduce power consumption.

[0172] In an embodiment, the share frame (e.g., Trigger in 2500) may include padding bits in the frame to give time for the second communication apparatus (e.g., AP2) to switch channels (e.g., to maintain a Short Interframe Space (SIFS) interval between the share frame and next frame). The padding bits may come after an integrity check field, e.g., an FCS, inside the frame to allow the content before the padding to be decoded first. Alternatively, the padding could come after the FCS field to match other frame formats. The amount of padding to include may be negotiated with the join frame (e.g., 2502) or another exchange, e.g., an exchange for to establish coordination between multiple APs.

[0163]

[0173] In an embodiment, the share frame (e.g., Trigger in 2500) may include multiple User Info fields intended for multiple APs that may be involved in the scheduled period (e.g., R-TWT SP 2504).

[0164]

[0174] In an embodiment, a CTS or QoS Null frame may be used for the share frame (e.g., Trigger in 2500) and the channel or RU allocated may be determined based on the content of the accept frame (e.g., 2506).

[0165]

[0175] In an embodiment, another Trigger frame such as Buffer Status Report Poll (BSRP) Trigger frame or Bandwidth Query Report Poll (BQRP) Trigger frame may be used as the share frame (e.g., Trigger in 2500).

[0166]

[0176] Figure 30 shows yet another time-sequence diagram 3000 according to an embodiment of the present disclosure. A second communication apparatus (e.g., AP2), which operates in a second BSS (e.g., BSS2) begins the process by sending a join frame 3002 to a first communication apparatus (e.g., AP1 ), which operates in a first BSS (e.g., BSS1 ). In an embodiment, the join frame may comprise a request for specific channels or RUs to be shared, and may include a duration to be shared, by AP1 with AP2 during a scheduled period (e.g., a trigger-enabled R-TWT SP) of AP1. AP1 responds with an accept frame 3004, confirming the allocation of RUs or channels for the SP. AP1 may share a part or whole of the scheduled period with AP2. AP2 may contend for medium access at the beginning of the schedule period and, during the scheduled period, send or trigger transmission of frames (e.g., LS data) within BSS2 in the allocated channel or RUs. Concurrently, during the scheduled period, AP1 may contend and send or trigger the transmission of frames (e.g., LS data) within BSS1 using non-allocated channels or RUs.

[0167]

[0177] During the shared allocation, AP2 operates independently from AP1 , utilizing the scheduled period to transmit frames (e.g., LS data) to STA2. This process does not require direct triggering from AP1 , as AP2 contends for the wireless medium at the beginning of the scheduled period based on the negotiated configuration. Utilizing the sequence as depicted in Figure 30, AP2 may use the scheduled period without being triggered by AP1 by contending at the start of the scheduled period for the negotiated channel or RUs. AP1 does not transmit over the allocated channel or RUs during the scheduled period, or duration negotiated. It should be noted that STA2 may be able to receive frames from AP2 in the allocated channels or RUs based on prior information provided by AP2, wherein the prior information may be such as operating channel or advertisement of a scheduled period. Advantageously, this may improve the efficiency of the data transmission for AP1 and AP2 during the scheduled period as AP1 does not need to manage the channel access of AP2.

[0168]

[0178] In an embodiment, the second communication apparatus (e.g., AP2 in 3000) may request to be shared the scheduled period of a first communication apparatus (e.g., AP1 in 3000) for a specific channel or RU, by sending a join frame (e.g., 3002) to AP1 , and AP1 may indicate this mode of operation, wherein AP2 may operate independently while using the negotiated channel or RUs, by sending an accept frame (e.g., 3004), for example by using a flag (e.g., a 1 -bit field using a reserved bit in the Traffic Info Control field, in the Restricted TWT Traffic Info field, in the TWT Parameter Information field, in the TWT element).

[0169]

[0179] Figure 31 shows yet another time-sequence diagram 3100 according to an embodiment of the present disclosure. A second communication apparatus (e.g., AP2), after being triggered (e.g., 3106), can transmit frames (e.g., LS data) in its own BSS (e.g., BSS2) concurrently with a first communication apparatus (e.g., AP1 ), which operates in a first BSS (e.g., BSS1) using the same channel as the first communication apparatus. In this setup, AP1 and AP2, along with, potentially, the associated STAs involved in the data exchange (e.g., STA1 and STA2), use specific transmission and reception configurations. These configurations include settings such as one or more of transmit power and beamforming patterns, which are selected to avoid interference between communication links. The process begins with AP2 sending a join frame 3102 to AP1 , requesting to be shared a part of a scheduled period (e.g., a trigger-enabled R-TWT SP) of AP1. The join frame may identify one or more transmission and reception configurations that AP2 intends to use during the shared allocation. AP1 responds with an accept frame 3104, confirming the configurations to be used during the shared allocation. At the start of the R-TWT SP, AP1 contends for the medium and sends a protect frame (e.g., an MU-RTS Trigger frame) and AP2 responds with a CTS frame. This provides hidden node protection.

[0180] AP1 may send or trigger transmission of frames within BSS1 prior to, or alternatively during or after, the shared allocation. AP1 shares the allocation with AP2 by sending a share frame (e.g., Trigger 3106) to AP2. AP2, having received the share frame, can transmit frames (e.g., LS data) to its associated STA (e.g., STA2) within BSS2 using the accepted transmission and reception configurations. In the example, the sequence concludes with BA frame transmitted by STA2 to the AP2. For the transmission of the BA frame, STA2 may use a transmission and reception configuration based on information provided by AP2, wherein the information may be such as an advertised scheduled period requiring a specific transmission and reception configuration by STA2, or an indication in the LS data frame from AP2 informing a configuration to be used in the response. During the shared allocation, AP1 , AP2, and STAs involved in the data exchange may use only specific transmission and reception configurations involving such as transmitting power or beamforming patterns, to avoid interfering with each other’s communication. Utilizing the above sequence as described in Figure 31 , and due to the use of complementary transmit and receive configurations between the communication apparatuses, the AP2 may serve traffic (e.g., LS traffic) in its own BSS using the full channel bandwidth of the allocation concurrently with the AP1 , thereby improving overall network efficiency and performance. In an embodiment, the transmission and reception configurations may be determined before or during the scheduled period prior to the transmission of frames during the shared allocation.

[0170]

[0181] In an embodiment, the determining of suitable or complementary transmission and reception configurations may involve additional transmissions such as one or more sounding packets between the APs and STAs. In an embodiment, the configurations may have been selected based on the second communication apparatus’ (e.g., AP2 in 3100) target communication apparatus for communication (e.g., STA2 in 3100) during the shared allocation and may have been selected based on the expected impact on the first communication apparatus’ (e.g., AP1 in 3100) expected communications based on API ’s transmission and reception configurations. AP2 may have discovered API ’s expected transmission and reception configuration to be used during the scheduled period, for example, by an advertise frame or some other frame exchange. Suitable configurations may have been established during exchanges with AP1 , for example during a setup for coordinated spatial reuse (C-SR) or coordinated beamforming (C-BF) operation. AP1 may accept the request to join, for example, if it determined that AP2’s proposed transmission and reception configuration is unlikely to interfere with API ’s use of the shared allocation.

[0182] In an embodiment, thejoin frame from the second communication apparatus (e.g., AP2 in 3100) may simply indicate a request to be triggered by the first communication apparatus (e.g., AP1 in 3100) for C-SR or C-BF, without indication of specific transmit or receive configurations to be used. In this case, AP2 may simply be expected to apply the appropriate transmit or receive configuration based on prior knowledge API ’s expected transmission and reception configuration to be used during the scheduled period. AP1 may accept the request to join based on a trust or relationship with AP2, for example, if AP1 and AP2 are in a coordinating AP group or are collocated in a common entity.

[0171]

[0183] Figures 32A and 32B show example formats of a TWT element when included in a TWT Setup frame according to an embodiment of the present disclosure. The TWT Setup frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 3100) to a second communication apparatus (e.g., AP2 in 3100), wherein the frame is an accept frame (e.g., 3104), or may be, but is not limited to, a frame transmitted from a second communication apparatus (e.g., AP2 in 3100) to a first communication apparatus (e.g., AP1 in 3100), wherein the frame is a join frame (e.g., 3102). The TWT element in Figure 32A is an example of a TWT element when included in the join frame and the TWT element in Figure 32B is an example of a TWT element when included in the accept frame. Referring to TWT element 3200 of Figure 32A, the Request Type field within the Broadcast TWT Parameter Set field comprises a TWT Request set to "1" for requesting or scheduling STAs, a TWT Setup Command set to "2" for “Demand TWT”. The Trigger field set to "1" indicates that the triggering is enabled during the TWT SP. Referring to TWT element 3250 of Figure 32B, the Request Type field within the Broadcast TWT Parameter Set field comprises a TWT Request field set to “0” indicating that it is a response to a request to join a TWT, TWT Setup command set to “4” indicating “Accept TWT” and Trigger field set to “1” to indicate that triggering is enabled during the TWT SP. In Figures 32A and 32B, a C-SR / C-BF Config Bitmap field (e.g., up to 1 octet) may be included using reserved bits by setting the DL TID Bitmap Valid (or UL TID Bitmap Valid) to “0” indicating invalid. The C-SR / C-BF Config Bitmap field indicates one or more configuration parameters to be used by the second communication apparatus during the shared allocation. In Figure 32B, the C-SR / C-BF Config Bitmap field may be included and used to indicate either the accepted transmission and reception configuration of the second communication apparatus, or the expected transmission and reception configuration to be used by AP1.

[0184] In an embodiment, a second communication apparatus (e.g., AP2 in 3100) may indicate its intended transmission and reception configuration to be used during the scheduled period (e.g., R-TWT SP) in the TWT element’s Restricted TWT Traffic Info field, e.g., in the join frame, advertise frame or share frame. For example, the configuration may be represented by a bitmap where each bit represents a different configuration (or set of configurations).

[0172]

[0185] In an embodiment, a first communication apparatus (e.g., AP1 in 3100) may indicate the accepted transmission and reception configurations to be used in the accept frame (e.g., 3104) based on information in the join frame (e.g., 3102) from the second communication apparatus (e.g., AP2) or a prior exchange with the second communication apparatus.

[0173]

[0186] In an embodiment, the first communication apparatus (e.g., AP1 in 3100) may transmit the accept frame (e.g., 3104) and indicate the same or lesser configurations than indicated by a second communication apparatus (e.g., AP2 in 3100) in the join frame (e.g., 3102), for example, based on its determination of likely interference with APIs intended communication during the scheduled period (e.g., R-TWT SP).

[0174]

[0187] In an embodiment, a second communication apparatus (e.g., AP2 in 3100) may transmit frames (e.g., LS data) within its own BSS (e.g., BSS2), during the shared allocation, using the transmission and reception configurations that have been agreed with the first communication apparatus (e.g., AP1 ).

[0175]

[0188] Figure 33 shows yet another time-sequence diagram 3300 according to an embodiment of the present disclosure. After a first communication apparatus (e.g., AP1 ) transmits an accept frame 3302 to a second communication apparatus (e.g., AP2), the second communication apparatus (e.g., AP2) transmits frames 3304 (e.g., LS data) to an associated STA (e.g., STA2) in a BSS (e.g., BSS2), without being triggered by the first communication apparatus, and by contending at the start of the scheduled period (e.g., R- TWT SP) independently to obtain access to the medium. In an embodiment, AP2 may use transmission and reception configurations as agreed with AP1 , which avoid interfering with APTs communication during the shared allocation. In an embodiment, AP2 may request in its join frame and AP1 may indicate this mode of operation, wherein AP2 may operate independently while using the negotiated transmission and reception configurations, by sending the accept frame using a field (e.g., a 1 -bit field using a reserved bit in the Traffic Info Control field, in the Restricted TWT Traffic Info field, in the TWT Parameter Information field, in the TWT element). AP1 may share a part or whole of the scheduled period with AP2.The advantageous effect is that the scheduled period can be used to serve multiple BSS’s LS traffic concurrently over a single channel without AP1 managing AP2’s channel access.

[0176]

[0189] Figure 34 shows yet another time-sequence diagram 3400 according to an embodiment of the present disclosure. After an accept frame 3402 is sent from a first communication apparatus (e.g., AP1 ) to a second communication apparatus (e.g., AP2), the second communication apparatus advertises a scheduled period (e.g., R-TWT SP2) within the second BSS (e.g., BSS2) that partially or fully overlaps with the scheduled period (e.g., R-TWT SP) of the first communication apparatus through transmission of an peer advertise frame (e.g., 3404). It should be noted that the peer advertise frame may also be referred to as a sixth frame in the present disclosure. The peer advertise frame may be, e.g., a Beacon frame or Probe Response frame, and may be a unicast frame, a multicast frame or a broadcast frame. It should be noted that the sixth frame is not described in a sequential order; the indexing is used solely to differentiate between the different frames as disclosed in the claims of the present disclosure. The overlapping scheduled period (e.g., R-TWT SP2) within the second BSS may facilitate protection of the scheduled period and may also prepare one or more other communication apparatus in BSS2 for involvement during the shared allocation with AP2. For example, STAs involved in the new scheduled period may stay awake during the period and may operate in specific RUs or channels or with specific transmission and reception configurations.

[0177]

[0190] In an embodiment, the second communication apparatus (e.g., AP2) may wait for a share frame from the first communication apparatus (e.g., AP1 ) before transmitting during the overlapping scheduled period (e.g., R-TWT SP2) in the second BSS (e.g., BSS2). In an embodiment, the overlapping scheduled period (e.g., R-TWT SP2) may not specify any member APs and STAs or may specify as members only AP and STAs which may be involved in the communication with the second communication apparatus (e.g., AP2) during the scheduled period (e.g., R-TWT SP). In an embodiment, the second communication apparatus (e.g., AP2) may schedule a quiet time interval or other types of scheduled periods to prepare one or more target communication apparatuses to operate in a specific way or to protection of the start or duration of the scheduled period of AP1 .

[0178]

[0191] Figure 35 shows yet another time-sequence diagram 3500 according to an embodiment of the present disclosure. Prior to transmitting a join frame (e.g., 3504) to join the scheduled period of a neighbouring first communication apparatus (e.g., AP1 ), a second communication apparatus (e.g., AP2) passively discovers the scheduled period (e.g., R-TWT SP) by receiving an advertise frame (e.g., 3502) from the neighbouring AP (e.g., AP1 ). Upon processing the advertise frame, the AP2 determines the suitability of the scheduled period for its own use, for example, based on timing and operation information. AP2 then sends the join frame to AP1 to join the R-TWT SP. An advantageous effect of this is that an AP (e.g., AP2) can discover a neighbouring AP’s (e.g., API ’s) scheduled period (e.g., TWT SP) to join, thus improving the efficiency of channel utilization for APs and / or STAs during the scheduled period.

[0179]

[0192] Figure 36 shows a flowchart 3600 illustrating the process undertaken by a second communication apparatus (e.g., AP2), which operates in a second BSS (e.g., BSS2), in determining to send a join frame for a scheduled period of a first communication apparatus (e.g., AP1 ), which operates in a first BSS (e.g., BSS1 ) according to an embodiment of the present disclosure. The process begins in step 3602, with AP2 receiving a frame from AP1 , which advertises one or more scheduled period (e.g., TWT SPs). In step 3604, AP2 then processes the received frame to determine the suitability of the one or more advertised scheduled periods (e.g., TWT SPs) for accommodating the transmissions (e.g., for LS data) in its BSS (e.g., BSS2). In step 3606, if a suitable scheduled period (e.g., TWT SP) is identified, AP2 sends a request to AP1 to join the suitable scheduled period (e.g., TWT SP).

[0180]

[0193] Figure 37 shows an example format of a Beacon frame 3700 according to an embodiment of the present disclosure. The Beacon frame may be, but is not limited to, a frame transmitted from a first communication apparatus (e.g., AP1 in 3500) to a second communication apparatus (e.g., AP2 in 3500), wherein the frame is an advertise frame. The Beacon frame includes a MAC header and contains fields such as a Timestamp, Beacon Interval, zero or more TWT element(s), and an FCS. The frame's type is set to "00", indicating that it is a management frame, and its subtype is "1000", specifying that it is a Beacon frame. One or more TWT elements may be included in the Beacon frame to advertise a TWT SP and the TWT element is identified by an Element ID of “216”. This element includes fields for Length, Control, and TWT Parameter Information. The Control field indicates Negotiation Type as “2” specifying that the element broadcasts TWT schedules.

[0181]

[0194] Within the Broadcast TWT Parameter set field, the Request Type field specifies that the TWT Request is set as “0” indicating a “TWT responding STA / scheduling AP” and Trigger is set as “1 ” to indicating that triggering is enabled. The Target Wake Time field indicates the scheduled time for SP of the TWT, during which members are awake to communicate with the AP. The Nominal Minimum TWT Wake Duration indicates the minimum period that devices are expected to remain awake for communication during the TWT SP for on the TWT. The TWT Wake Interval Mantissa provides additional information on intervals, e.g., between consecutive TWT SPs. Lastly the Broadcast TWT Info field comprises a Restricted TWT Traffic Info Present field which is set as “0” to indicate absence of the Restricted TWT Traffic Info field, Restricted TWT schedule info field which indicates information about the state of the schedule, and Broadcast TWT ID that is set to identify the TWT.

[0182]

[0195] In an embodiment, a first communication apparatus (e.g., AP1 in 3500) advertises the scheduled period (e.g., trigger-enabled R-TWT SP in 3500) by including a TWT element in a management frame, (e.g., 3502, which may be a Beacon frame). The advertisement informs the information about the scheduled period. For example, in case of a TWT SP, time and minimum wake duration of one or more TWT SPs, the Broadcast TWT Parameter Set subfields, e.g., Broadcast TWT ID, Target Wake Time, etc. advertising the target TWT SP. The advertise frame may also be a unicast management frame (e.g., a Probe Response) which may be addressed to a second communication apparatus (e.g., AP2 in 3500), and may be exchanged during a frame exchange related to AP coordination, or it may have been addressed to a third communication apparatus and overheard by the second communication apparatus. In an embodiment, AP1 may indicate that the scheduled period (e.g., trigger-enabled R-TWT SP in 3500) may be joined byAPs, by indicating via the Broadcast TWT Recommendation field that APs (e.g., including AP2 in 3500) may join.

[0183]

[0196] Figure 38 shows an example format of a TWT element when included in an advertise frame (e.g., 3800) according to an embodiment of the present disclosure. Within the Request Type field of the Broadcast TWT Parameter Set field, the Broadcast TWT Recommendation is set to indicate for APs to join. Within the Broadcast TWT info, the Restricted TWT Schedule info field is set as “2” to indicate full R-TWT schedule. In an embodiment, a first communication apparatus (e.g., AP1 in 3500) may indicate that the R-TWT may be joined by only APs, for example, by setting Restricted TWT Schedule info to 2, and setting the Broadcast TWT Recommendation field to indicate that APs can join. This setting indicates that the TWT schedule is active but is not accepting new memberships from STAs while accepting APs to join. Such a scheduled period may be useful for coordinating AP frame exchanges.

[0197] Figure 39 shows another example format of a TWT element when included in an advertise frame (e.g., 3900) according to an embodiment of the present disclosure. Within the Broadcast TWT Info field, the Restricted TWT Traffic Present info field is set as “1 ” to indicate the presence of Restricted TWT Traffic. The Traffic Info Control field within the Restricted TWT Traffic Info field includes a TXOP Return Request field (e.g., consisting of 1 bit) that is set to indicate “Requested”. In an embodiment, a first communication apparatus (e.g., AP1 in 3500) may indicate that a second communication apparatus (e.g., AP2 in 3500) should return excess TXOP duration to the first communication apparatus (e.g., AP1 in 3500) by sending an advertise frame including a flag, which is set to indicate the request for a return of the TXOP. This may allow AP1 to regain access of the allocation and be able to send additional frames if needed. If a return is not requested, AP2 may, for example, decide to release the excess TXOP duration by sending a CF-End frame.

[0184]

[0198] Figure 40 shows yet another example format of a TWT element when included in an advertise frame (e.g., 4000) according to an embodiment of the present disclosure. Within the Request Type field, the Broadcast TWT Recommendation field may indicate that peer AP triggering is allowed, meaning that peer APs are permitted to trigger another AP, or STA, during the shared allocation, to further share the shared allocation (e.g., R- TWT SP in 3500). An alternative indication may be to include a Peer AP Trigger Allowed field in the Traffic Info Control field of the Restricted TWT Traffic Info field. The Peer AP Trigger Allowed field may be set as “1 ” to indicate allowance of peer AP triggering to share the shared allocation. Another alternative is to include a Peer AP Trigger Allowed field using the Restricted TWT Traffic Info field’s reserved bits, which are more than in the existing Traffic Info Control field, by setting the DLTID Bitmap Valid field (or UL TID Bitmap Valid) in the Traffic Info Control to “0” indicating invalid. The Peer AP Trigger Allowed field may also indicate more granular behaviour of use of the shared allocation by using more than 1 bit, for example, to inform what traffic the allocation may be used for. In an embodiment, a first communication apparatus (e.g., AP1 in 3500) may indicate in the Peer AP trigger Allowed field that a second communication apparatus (e.g., AP2 in 3500) is permitted to share the shared allocation by, e.g., sending a Trigger frame to other STAs or other APs. The Trigger frame that may be sent by the second communication apparatus (e.g., AP2) to other STAs or other APs may be referred to as a seventh frame in the present disclosure. It should be noted that the seventh frame is not described in a sequential order; the indexing is used solely to differentiate between the different frames as disclosed in the claims of the present disclosure.

[0199] Figure 41 shows yet another example format of a TWT element when included in an advertise frame (e.g., 4100) according to an embodiment of the present disclosure. Within the Broadcast TWT Info field, the Restricted TWT Traffic Info Present field is set as “1” to indicate presence of the Restricted TWT Traffic Info. The Restricted TWT Traffic Info field comprises Traffic Info Control field which further indicates that DL TID Bitmap Valid field is set as “0” to indicate as invalid. Additionally, a C-SR / C-BF Config Bitmap field (e.g., up to 1 octet) indicates the transmission and reception configurations intended to be used by a first communication apparatus (e.g., AP1 in 3500) during the scheduled period (e.g., R-TWT SP in 3500). In an embodiment, AP1 may indicate its intended transmission and reception configuration to be used during the R-TWT SP in the TWT element’s Restricted TWT Traffic Info Field by, e.g., using a bitmap, wherein each bit represents different configuration (or set of configurations).

[0185]

[0200] Figure 42 depicts yet another time-sequence diagram 4200 according to an embodiment of the present disclosure. The time-sequence starts with a second communication apparatus (e.g., AP2), which operates in a second BSS (e.g., BSS2), sending a management frame 4202, comprising information indicating a request for information regarding one or more schedule periods, to a first communication apparatus (e.g., AP1 ), which operates in a first BSS (e.g., BSS1 ). In an embodiment, the frame may be a unicast message, multicast or broadcast message, and may be, but is not limited to, a Probe Request frame. In an embodiment, wherein the request for information is using a Probe Request frame, AP1 responds with a Probe Response as the advertise frame containing an advertisement of one or more schedule periods (e.g., such as a trigger- enabled R-TWT SP). An advantageous effect of this would be that an AP will be able to discover a neighbouring AP’s TWT to join more actively and quickly.

[0186]

[0201] In an embodiment, the advertise frame (e.g., in 4200) may additionally indicate an ID (e.g., a Peer AP ID field contained in a Restricted TWT Traffic Info field, in a Broadcast TWT Parameter Set field, in a TWT Parameter Information field, in a TWT element) to be used by a first communication apparatus (e.g., AP1 in 700) to uniquely identify a second communication apparatus (e.g., AP2 in 700) in the share frame (e.g., Trigger in 700). In an embodiment, AP2 may be in a coordinating AP group with AP1 where APs support each other such as by coordinating schedules and sharing allocations.

[0187]

[0202] Alternatively, a second communication apparatus (e.g., AP2 in 4200) can send a broadcast or multicast frame to request information from all or multiple neighbouring APs to discover their scheduled periods (e.g., TWT SPs). Afirst communication apparatus (e.g., AP1 in 4200), upon receiving this broadcast request, may reply with a unicast, multicast or broadcast message advertising its relevant scheduled periods. This method enables AP2 to gather information about TWT SPs from multiple neighbouring APs concurrently and quickly. The message from AP2 may additionally include an identifier for AP1 to uniquely identify AP2 for use in the share frame, facilitating communication and coordination. This identifier may serve to distinguish AP2 from multiple APs that AP1 may share a scheduled period with. In an embodiment, AP2 may transmit a multicast or broadcast request and receive one or more advertise frames from one or more communication apparatuses.

[0188]

[0203] As described above, the embodiments of the present disclosure provide advanced communication systems, methods, and apparatuses for managing scheduled periods (e.g., TWT SPs) in network communications.

[0189]

[0204] The present disclosure can be realized through software, hardware, or a combination of both. Each functional block mentioned in the description of each embodiment can be partly or entirely implemented using a Large-Scale Integration (LSI), such as an integrated circuit. Each process described in each embodiment may be controlled either partly or entirely by the same LSI or by a combination of LSIs. The LSI can be implemented as individual chips or as a single chip containing part or all of the functional blocks. It may include data input and output capabilities. The term LSI may be used interchangeably with IC, system LSI, super LSI, or ultra LSI, depending on the level of integration. However, the implementation is not limited to LSIs and may include a dedicated circuit, general-purpose processor, or special-purpose processor. Additionally, technologies like FPGA (Field Programmable Gate Array) or reconfigurable processors, where circuit cells within the LSI can be reconfigured, may also be utilized. The present disclosure can be realized through digital or analog processing. If future integrated circuit technology, driven by advances in semiconductor technology or other derivative technologies, replaces LSIs, the functional blocks could be integrated using these new technologies. The use of biotechnology is also a possibility.

[0190]

[0205] The present disclosure can be realized by any apparatus, device, or system capable of communication, collectively referred to as a communication apparatus.

[0191]

[0206] Non-limiting examples of such communication apparatuses include phones (e.g., cellular phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, and vehicles equipped with communication functionality (e.g., automotive, airplanes, ships), and various combinations thereof.

[0192]

[0207] The communication apparatus is not restricted to being portable or movable and can also include non-portable or stationary devices, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and other devices in a network of an "Internet of Things (loT)".

[0193]

[0208] The communication may involve exchanging data through various systems, including cellular systems, wireless LAN systems, satellite systems, and combinations thereof.

[0194]

[0209] The communication apparatus may include devices such as controllers or sensors coupled to a communication device performing communication functions as described in the present disclosure. For example, it may include a controller or a sensor that generates control signals or data signals used by a communication device performing the communication functions of the apparatus.

[0195]

[0210] The communication apparatus may also include infrastructure facilities, such as base stations, access points, and other devices or systems that communicate with or control the apparatuses mentioned in the above non-limiting examples.

[0196]

[0211] It is understood that while some properties of the various embodiments have been described with reference to a device, corresponding properties also apply to the methods described in the various embodiments, and vice versa.

[0197]

[0212] A person skilled in the art will appreciate that numerous variations and / or modifications can be made to the present disclosure as shown in the specific embodiments without departing from the spirit or scope of the disclosure as broadly described. The present embodiments are, therefore, considered illustrative and not restrictive in all respects.

[0213] In the following paragraphs, certain exemplifying embodiments are explained with reference to terms related to Wi-Fi networks and the present disclosure regarding communication apparatuses and methods for sharing a scheduled period, namely:

[0198] Example 1. A first communication apparatus, which operates in a first basic service set (BSS), comprising: circuity, which in operation, generates a first frame comprising information to share a part or whole of a scheduled period of the first communication apparatus with a second communication apparatus, which operates in a second BSS, for transmitting one or more frames; and a transceiver, which in operation, transmits the first frame to the second communication apparatus.

[0199] Example 2. The first communication apparatus of example 1 , wherein the scheduled period of the first communication apparatus is a target wake time (TWT) service period (SP).

[0200] Example 3. The first communication apparatus of example 1 , wherein, prior to the scheduled period, the transceiver receives, from the second communication apparatus, a join frame, which comprises a request for the sharing of the part or whole of the scheduled period with the second communication apparatus, and transmits a second frame to the second communication apparatus in response to the join frame to accept the request for sharing.

[0201] Example 4. The first communication apparatus of example 1 , wherein prior to transmitting the first frame, the transceiver, in operation, is further configured to transmit a third frame to the second communication apparatus before the scheduled period, wherein the third frame is one of a unicast, multicast or broadcast frame, and comprises information about the scheduled period of the first communication apparatus.

[0202] Example 5. The first communication apparatus of example 4, wherein the third frame further comprises one or more information, said information selected from a group consisting of:

[0203] (i) an indication that the part or whole of the scheduled period may be shared with one or more communication apparatuses that includes the second communication apparatus; (ii) an indication that the part or whole of the scheduled period shared with the second communication apparatus may be further shared, by the second communication apparatus, with a third communication apparatus; and

[0204] (iii) a configuration for transmission and reception to be used by the first communication apparatus during the scheduled period.

[0205] Example 6. The first communication apparatus of example 1 , wherein the first frame further comprises one or more information, said information selected from a group consisting of:

[0206] (i) a unique identifier to identify the second communication apparatus, the unique identifier having been established between the first communication apparatus and the second communication apparatus before the scheduled period;

[0207] (ii) a request for the second communication apparatus to return any unused duration of the part of the scheduled period shared with the second communication apparatus; and

[0208] (iii) an indication that a response to the first frame is not required.

[0209] Example 7. The first communication apparatus of example 1 , wherein the first frame comprises one or more information, said information selected from a group consisting of:

[0210] (i) a duration of the part or whole of the scheduled period to be shared with the second communication apparatus;

[0211] (ii) a time or duration value that may be used to determine the start time of the part or whole of the scheduled period to be shared with the second communication apparatus;

[0212] (iii) one or more channels, bandwidth or resource units for the part or whole of the scheduled period to be shared with the second communication apparatus;

[0213] (iv) a configuration for transmission and reception to be used during the part or whole of the scheduled period to be shared with the second communication apparatus; and

[0214] (v) an indication that a whole part of the scheduled period is shared with the second communication apparatus.

[0215] Example 8. The first communication apparatus of example 1 , wherein the transceiver is further configured to transmit a fourth frame during the scheduled period and prior to transmitting the first frame, to solicit a clear to send (CTS) frame from the second communication apparatus. Example 9. The first communication apparatus of example 3, wherein the second frame comprises one or more information, said information selected from a group consisting of:

[0216] (i) one or more of channels, bandwidth or resource units for the part or whole of the scheduled period to be shared with the second communication apparatus;

[0217] (ii) a configuration for transmission and reception to be used during the part of the scheduled period to be shared with the second communication apparatus;

[0218] (iii) a unique identifier to identify the second communication apparatus;

[0219] (iv) a request for the second communication apparatus to return any unused duration of the part or whole of the scheduled period shared with the second communication apparatus; and

[0220] (v) an indication that the part or whole of the scheduled period shared with the second communication apparatus may be further shared, by the second communication apparatus, with a third communication apparatus.

[0221] Example 10. The first communication apparatus of example 8, wherein the fourth frame comprises one or more information, said information selected from a group consisting of:

[0222] (i) a duration of the part or whole of the scheduled period to be shared with the second communication apparatus;

[0223] (ii) an indication of a delayed a start of the part or whole of the scheduled period to be shared with the second communication apparatus;

[0224] (iii) a time or duration value that may be used to determine the start time of the part or whole of the scheduled period to be shared with the second communication apparatus;

[0225] (iv) one or more channels, bandwidth or resource units for the part or whole of the scheduled period to be shared with the second communication apparatus; and

[0226] (v) a configuration for transmission and reception to be used during the part or whole of the scheduled period to be shared with the second communication apparatus.

[0227] Example 11 . The first communication apparatus of example 1 , wherein the first and second communication apparatuses are included in a group of communication apparatuses that coordinate and cooperate with each other for use of a communication medium. Example 12. A second communication apparatus, which operates in a second BSS, comprising a transceiver, which in operation, receives a first frame, from a first communication apparatus, which operates in a first BSS, comprising information to share a part or whole of a scheduled period of the first communication apparatus with the second communication apparatus for transmitting one or more frames; and transmits the one or more frames during the part of the scheduled period of the first communication apparatus shared with the second communication apparatus.

[0228] Example 13. The second communication apparatus of example 12, wherein the scheduled period of the first communication apparatus is a TWT SP.

[0229] Example 14. The second communication apparatus of example 12, further comprising: circuity, which in operation, generates a fifth frame comprising information to request the first communication apparatus to share the part or whole of the scheduled period of the first communication apparatus with the second communication apparatus for transmitting one or more frames; and a transceiver, which in operation, transmits the fifth frame to the first communication apparatus.

[0230] Example 15. The second communication apparatus of example 14, wherein the fifth frame further comprises one or more information, said information selected from a group consisting of:

[0231] (i) a duration of the part or whole of the scheduled period to be shared with the second communication apparatus;

[0232] (ii) a time or duration value that may be used to determine the start time of the part or whole of the scheduled period to be shared with the second communication apparatus;

[0233] (iii) one or more channels, bandwidth or resource units for the part or whole of the scheduled period to be shared with the second communication apparatus;

[0234] (iv) a configuration for transmission and reception to be used during the part or whole of the scheduled period to be shared with the second communication apparatus; and

[0235] (v) one or more of latency requirements, categorization, priority or urgency of the one or more frames to be transmitted.

[0236] Example 16. The second communication apparatus of example 12, wherein the one or more frames are transmitted during the part or whole of the scheduled period shared with the second communication apparatus in accordance with transmission and operation requirements indicated in the first frame.

[0237] Example 17. The second communication apparatus of example 12, wherein the transceiver, in operation, after receiving a third frame from the first communication apparatus comprising information indicating the scheduled period of the first communication apparatus, transmits a sixth frame, which is one of a unicast, multicast or broadcast frame, to a third communication apparatus in the second BSS, the sixth frame comprising information indicating a scheduled period of the second communication apparatus, wherein the scheduled period of the second communication apparatus overlaps partially or fully with the scheduled period of the first communication apparatus.

[0238] Example 18. The second communication apparatus of example 12, further comprising: circuitry, which in operation, generates a seventh frame comprising information to share, with a third communication apparatus, a part or whole of the scheduled period shared by the first communication apparatus with a second communication apparatus; and a transceiver, which in operation, transmits the seventh frame to the third communication apparatus.

[0239] Example 19. A communication method implemented by a first communication apparatus, which operates in a first BSS, comprising: generating a first frame comprising information to share a part or whole of a scheduled period of the first communication apparatus with a second communication apparatus, which operates in a second BSS, for transmitting one or more frames; and transmitting the first frame to the second communication apparatus.

[0240] Example 20. A communication method implemented by a second communication apparatus, which operates in a second BSS, comprising: receiving a first frame, from a first communication apparatus, which operates in a first BSS, comprising information to share a part or whole of a scheduled period of the first communication apparatus, with the second communication apparatus for transmitting one or more frames; and transmitting the one or more frames during the part of the scheduled period of the first communication apparatus shared with the second communication apparatus.

Claims

CLAIMS1. A first communication apparatus, which operates in a first basic service set (BSS), comprising: circuity, which in operation, generates a first frame comprising information to share a part of a scheduled period of the first communication apparatus with a second communication apparatus, which operates in a second BSS, for transmitting one or more frames; and a transceiver, which in operation, transmits the first frame to the second communication apparatus.

2. The first communication apparatus of claim 1 , wherein the scheduled period of the first communication apparatus is a target wake time (TWT) service period (SP).

3. The first communication apparatus of claim 1 , wherein, prior to the scheduled period, the transceiver receives, from the second communication apparatus, a fifth frame, which comprises a request for the sharing of the part of the scheduled period with the second communication apparatus, and transmits a second frame to the second communication apparatus in response to the fifth frame.

4. The first communication apparatus of claim 1 , wherein prior to transmitting the first frame, the transceiver, in operation, is further configured to transmit a third frame to the second communication apparatus before the scheduled period, wherein the third frame is one of a unicast, multicast or broadcast frame, and comprises information indicating the scheduled period of the first communication apparatus.

5. The first communication apparatus of claim 4, wherein the third frame further comprises one or more information, said information selected from a group consisting of:(i) an indication that the part of the scheduled period may be shared with one or more communication apparatuses that includes the second communication apparatus;(ii) an indication that the part of the scheduled period shared with the second communication apparatus may be further shared, by the second communication apparatus, with a third communication apparatus; and(iii) a configuration for transmission and reception that may be used by the first communication apparatus during the scheduled period.

6. The first communication apparatus of claim 1 , wherein the first frame further comprises one or more information, said information selected from a group consisting of:(i) a unique identifier to identify the second communication apparatus, the unique identifier having been established between the first communication apparatus and the second communication apparatus before the scheduled period;(II) a request for the second communication apparatus to return any unused duration of the part of the scheduled period shared with the second communication apparatus; and(Hi) an indication that a response to the first frame is not required.

7. The first communication apparatus of claim 1 , wherein the first frame comprises one or more information, said information selected from a group consisting of:(i) a duration of the part or whole of the scheduled period to be shared with the second communication apparatus;(ii) a time or duration value that may be used to determine the start time of the part or whole of the scheduled period to be shared with the second communication apparatus;(iii) one or more channels, bandwidth or resource units for the part or whole of the scheduled period to be shared with the second communication apparatus;(iv) a configuration for transmission and reception that may be used during the part or whole of the scheduled period to be shared with the second communication apparatus; and(v) an indication that a whole part of the scheduled period is shared with the second communication apparatus.

8. The first communication apparatus of claim 1 , wherein the transceiver is further configured to transmit a fourth frame during the scheduled period and prior to transmitting the first frame, to solicit a clear to send (CTS) frame from the second communication apparatus.

9. The first communication apparatus of claim 3, wherein the second frame comprises one or more information, said information selected from a group consisting of:(i) one or more of channels, bandwidth or resource units for the part of the scheduled period to be shared with the second communication apparatus;(ii) a configuration for transmission and reception that may be used during the part of the scheduled period to be shared with the second communication apparatus;(iii) a unique identifier to identify the second communication apparatus;(iv) a request for the second communication apparatus to return any unused duration of the part of the scheduled period shared with the second communication apparatus; and(v) an indication that the part of the scheduled period shared with the second communication apparatus may be further shared, by the second communication apparatus, with a third communication apparatus.

10. The first communication apparatus of claim 8, wherein the fourth frame comprises one or more information, said information selected from a group consisting of:(i) a duration of the part or whole of the scheduled period to be shared with the second communication apparatus;(ii) an indication of a delayed a start of the part or whole of the scheduled period to be shared with the second communication apparatus;(iii) a time or duration value that may be used to determine the start time of the part or whole of the scheduled period to be shared with the second communication apparatus;(iv) one or more channels, bandwidth or resource units for the part or whole of the scheduled period to be shared with the second communication apparatus; and(v) a configuration for transmission and reception that may be used during the part of the scheduled period to be shared with the second communication apparatus.

11. The first communication apparatus of claim 1 , wherein the first and second communication apparatuses are included in a group of communication apparatuses that coordinate and cooperate with each other for use of a communication medium.

12. A second communication apparatus, which operates in a second BSS, comprising a transceiver, which in operation, receives a first frame, from a first communication apparatus, which operates in a first BSS, comprising information to share a part of a scheduled period of the first communication apparatus with the second communication apparatus for transmitting one or more frames; and transmits the one or more frames during the part of the scheduled period of the first communication apparatus shared with the second communication apparatus.

13. The second communication apparatus of claim 12, wherein the scheduled period of the first communication apparatus is a TWT SP.

14. The second communication apparatus of claim 12, further comprising: circuity, which in operation, generates a fifth frame comprising information to request the first communication apparatus to share the part of the scheduled period of the first communication apparatus with the second communication apparatus for transmitting one or more frames; anda transceiver, which in operation, transmits the fifth frame to the first communication apparatus.

15. The second communication apparatus of claim 14, wherein the fifth frame further comprises one or more information, said information selected from a group consisting of:(i) a duration of the part or whole of the scheduled period to be shared with the second communication apparatus;(ii) a time or duration value that may be used to determine the start time of the part or whole of the scheduled period to be shared with the second communication apparatus;(iii) one or more channels, bandwidth or resource units for the part of the scheduled period to be shared with the second communication apparatus;(iv) a configuration for transmission and reception that may be used during the part or whole of the scheduled period to be shared with the second communication apparatus; and(v) one or more of latency requirements, categorization, priority or urgency of the one or more frames to be transmitted.

16. The second communication apparatus of claim 12, wherein the one or more frames are transmitted during the part of the scheduled period shared with the second communication apparatus in accordance with transmission or operation requirements indicated in the first frame.

17. The second communication apparatus of claim 12, wherein the transceiver, in operation, after receiving a third frame from the first communication apparatus comprising information indicating the scheduled period of the first communication apparatus, transmits a sixth frame, which is one of a unicast, multicast or broadcast frame, to a third communication apparatus in the second BSS, the sixth frame comprising information indicating a scheduled period of the second communication apparatus, wherein the scheduled period of the second communication apparatus overlaps partially or fully with the scheduled period of the first communication apparatus.

18. The second communication apparatus of claim 12, further comprising: circuitry, which in operation, generates a seventh frame comprising information to share, with a third communication apparatus, a part of the scheduled period shared by the first communication apparatus with a second communication apparatus; and a transceiver, which in operation, transmits the seventh frame to the third communication apparatus.

19. A communication method implemented by a first communication apparatus, which operates in a first BSS, comprising: generating a first frame comprising information to share a part or whole of a scheduled period of the first communication apparatus with a second communication apparatus, which operates in a second BSS, for transmitting one or more frames; and transmitting the first frame to the second communication apparatus.

20. A communication method implemented by a second communication apparatus, which operates in a second BSS, comprising: receiving a first frame, from a first communication apparatus, which operates in a first BSS, comprising information to share a part of a scheduled period of the first communication apparatus, with the second communication apparatus for transmitting one or more frames; and transmitting the one or more frames during the part of the scheduled period of the first communication apparatus shared with the second communication apparatus.

Images