Transmission opportunity sharing method, access point and storage medium

Abstract

The embodiment of the present invention relates to the field of wireless communication technology, and discloses a transmission opportunity sharing method, access point and storage medium. In the present invention, a first channel detection is performed to compete for a channel; after the competition for the channel ends, the transmission opportunity of the master / slave channel obtained through the competition is accessed in the master / slave channel to perform downlink transmission in the master / slave channel; the transmission opportunity is shared to perform uplink transmission in the master / slave channel; after the uplink transmission ends, the transmission opportunity will be returned; the current idle channel is determined from the master channel and the slave channel through a second channel detection; channel access is performed according to the current idle channel to try to continue to use the transmission opportunity. In the case of slave channel access, the remaining transmission opportunities returned are fully utilized. Channel resources can be used more fully.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of wireless communication technology, and in particular to a transmission opportunity sharing method, an access point and a storage medium. Background Art

[0002] In Wi-Fi, the concept of primary channel and secondary channel is introduced to increase bandwidth and expand the original channel. Secondary channel access, also known as non-primary channel access, mainly involves the process of secondary channel access, granularity, resource allocation, etc. For example, the channel bandwidth of the original channel is 20MHz. The bandwidth of the primary channel is 20MHz, and the bandwidth of the secondary channel is also 20MHz. The primary channel overlaps with the original channel to ensure forward compatibility. Also for forward compatibility, some frames, such as beacon frames, are only transmitted on the primary channel. At the same time, during channel detection, the detection result indicates that the primary channel is idle and the secondary channel is idle at the same time, and then access is made. If the detection result indicates that the primary channel is idle and the secondary channel is busy, then directly enter the primary channel. If the detection result indicates that the primary channel is busy and the secondary channel is idle at the same time, then do not access the primary channel and the secondary channel. If the detection result indicates that the primary channel is busy and the secondary channel is idle at the same time, then do not access the primary channel and the secondary channel. This strategy wastes channel resources to some extent. In particular, Wi-Fi 7 already supports a maximum channel bandwidth of 320MHz and a secondary channel of 160MHz. Even if the channel bandwidth is 160MHz, the slave channel bandwidth is as high as 80MHz, which is a serious waste of resources. Therefore, in order to fully utilize channel resources, a discussion on slave channel access has been carried out. It is mainly aimed at accessing the slave channel when the channel detection indicates that the main channel is busy and the slave channel is idle.

[0003] The inventors have found that there are at least the following problems in the related art: Sharing of transmission opportunities (TXOPs) from channel access is widely used as a way of fast uplink and downlink interaction, while TXOP sharing in the context of channel access is a technical gap in the related art. Solutions related to TXOP sharing in the context of channel access will also give rise to a large number of technical problems, such as how to return a shared TXOP, how the original TXOP owner can access the TXOP again after the TXOP is returned after the shared transmission ends, etc. Summary of the invention

[0004] The purpose of the embodiments of the present invention is to provide a transmission opportunity sharing method, access point and storage medium, so that the returned remaining TXOP can be fully used in the case of access from the channel, so that the channel resources can be more fully used.

[0005] To solve the above technical problems, an embodiment of the present invention provides a transmission opportunity sharing method, comprising: competing for channels through a first channel detection; after the channel competition ends, accessing the transmission opportunity of the master / slave channel obtained through competition to perform downlink transmission in the master / slave channel; sharing the transmission opportunity to perform uplink transmission in the master / slave channel; wherein, after the uplink transmission ends, the transmission opportunity will be returned; determining the current idle channel from the master channel and the slave channel through a second channel detection; and performing channel access according to the current idle channel to try to continue to use the transmission opportunity.

[0006] An embodiment of the present invention also provides an access point, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above-mentioned transmission opportunity sharing method.

[0007] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the above-mentioned transmission opportunity sharing method is implemented.

[0008] In the embodiment of the present invention, the first channel detection is used to compete for the channel; after the channel competition ends, the transmission opportunity of the master / slave channel obtained through the competition is accessed in the master / slave channel to perform downlink transmission in the master / slave channel; uplink transmission is performed in the master / slave channel by sharing the transmission opportunity; after the uplink transmission ends, the transmission opportunity will be returned; the current idle channel is determined from the master channel and the slave channel through the second channel detection; channel access is performed according to the current idle channel to try to continue to use the transmission opportunity. In the case of slave channel access, the remaining TXOP returned is fully used. Channel resources can be used more fully. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0010] Figure 1 is a schematic diagram of access point and terminal access transmission opportunities provided according to an embodiment of the related technology;

[0011] Figure 2 is a flow chart of a transmission opportunity sharing method provided according to an embodiment of the present invention;

[0012] Figure 31. It is a schematic diagram of a transmission opportunity of a master channel accessing a master-slave channel provided according to an embodiment of the present invention;

[0013] Figure 4 is a schematic diagram of a transmission opportunity of a primary channel accessing a secondary channel provided according to an embodiment of the present invention;

[0014] Figure 5 is a schematic diagram of a transmission opportunity of a slave channel accessing a master channel provided according to an embodiment of the present invention;

[0015] Figure 6 is a schematic diagram of a transmission opportunity of accessing a main channel after backing off from a channel provided according to an embodiment of the present invention;

[0016] Figure 7 is a schematic diagram of access transmission opportunities between access points provided according to an embodiment of the present invention;

[0017] Figure 8 is a schematic diagram of extending transmission opportunities between access points provided according to an embodiment of the present invention;

[0018] Fig. 9 It is a schematic structural diagram of an access point according to another embodiment of the present invention. DETAILED DESCRIPTION

[0019] To make the purpose, technical scheme and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. However, it will be appreciated by those skilled in the art that in the embodiments of the present invention, many technical details are proposed in order to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical scheme claimed in the present application can be implemented. The division of the following embodiments is for the convenience of description, and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined and referenced with each other without contradiction.

[0020] In the description of the embodiments of the present application, the technical terms "first", "second", etc. are only used to distinguish different objects, and cannot be understood as indicating or implying relative importance or implicitly indicating the number, specific order or primary and secondary relationship of the indicated technical features. In the description of the embodiments of the present application, the meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.

[0021] In the description of the embodiments of the present application, the term "and / or" is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists, A and B exist at the same time, and B exists. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0022] In the description of the embodiments of the present application, the term "multiple" refers to more than two (including two). Similarly, "multiple groups" refers to more than two groups (including two groups), and "multiple pieces" refers to more than two pieces (including two pieces).

[0023] An embodiment of the present invention relates to a transmission opportunity sharing method, which can be applied to a multi-connection device, and the multi-connection device can be used as an access point (AP), or a multi-connection device with multiple APs attached. When facing various TXOP sharing-related situations, the execution subject may change, such as the terminal sharing with the AP, or the AP sharing with the terminal, or the terminal P2P sharing TXOP, or an AP grabbing the TXOP and needing to share it with another AP. Regardless of whether the execution subject changes, the transmission opportunity sharing method proposed in the present application can be used, which will be described in detail below. In this embodiment, the first channel detection is used to compete for the channel; after the competition for the channel ends, the transmission opportunity of the master / slave channel obtained through the competition is accessed in the master / slave channel to perform downlink transmission in the master / slave channel; the transmission opportunity is shared to perform uplink transmission in the master / slave channel; after the uplink transmission ends, the transmission opportunity will be returned; the current idle channel is determined from the master channel and the slave channel through the second channel detection; channel access is performed according to the current idle channel to try to continue to use the transmission opportunity. In the case of slave channel access, the returned remaining TXOP is fully used. Channel resources can be used more fully. The following is a detailed description of the implementation details of the transmission opportunity sharing method of this embodiment. The following content is only provided for easy understanding of the implementation details and is not necessary for implementing this solution.

[0024] For ease of understanding, we first briefly explain the transmission opportunities accessed from the channel by taking the example of the execution subject being the AP and sharing the transmission opportunities with the terminal. Figure 1As shown, within a transmission opportunity (TXOP for short), the AP shares the TXOP with at least one terminal for uplink transmission. After the terminal completes the uplink transmission, the TXOP does not end (the corresponding parameter TXOP-REMAINING is not 0, and TXOP-REMAINING refers to a TXOP minus the time that the TXOP has been used). Then the access point (AP for short) performs a channel detection on the entire bandwidth. If the channel is idle, access the channel. At the same time, the AP transmits a point [coordination function] interframe space (PIFS for short, full name point [coordination function] interframe space) after the terminal completes the uplink transmission. According to the current access method, after the uplink transmission, the AP performs channel sensing and completes a channel detection (CCA, clear channel assessment) within the entire bandwidth. If the AP (access point) performs a channel detection on the entire bandwidth and the channel detection passes, access the channel, and the AP shares the TXOP with the terminal. The terminal returns the TXOP to the AP after the transmission is completed. The AP accesses the TXOP again. Similarly, in the case of primary channel access, if an AP just starts to access the channel, the channel detects that the primary channel is idle and the secondary channel is busy, and obtains the TXOP through primary channel access. Then it starts downlink transmission, and then shares the TXOP, and allocates the resources in the TXOP to another device for transmission; then the device ends the transmission; then the TXOP is returned to the AP, and how the AP can access the channel again is a problem. Similarly, in the case of secondary channel access, if an AP just starts to detect that the primary channel is busy and the secondary channel is idle, and obtains the TXOP through secondary channel access. Then it starts downlink transmission, and then shares the TXOP, and allocates the resources in the TXOP to another device for transmission; then the device ends the transmission; then the TXOP is returned to the AP, and how the AP can access the channel again is a problem.

[0025] After a brief understanding of channel access and transmission opportunity sharing, the implementation details of the transmission opportunity sharing method of this embodiment are specifically described below.

[0026] like Figure 2As shown, in step 101, the first channel detection is used to compete for the channel; this competition for the channel will lead to two types of results. The first type is that when the AP accesses the channel, it directly accesses the main channel (the slave channel is busy and the main channel is idle); the second type is that the AP starts to compete for the channel and only grabs the slave channel resources, and the main channel is busy. These two types of situations will give rise to many situations, and each has a corresponding embodiment, which will be discussed in turn later. Regardless of which type of situation, in step 102, after the competition for the channel ends, the transmission opportunity of the master / slave channel obtained through the competition is accessed in the master / slave channel to perform downlink transmission in the master / slave channel; in step 103, the transmission opportunity is shared to perform uplink transmission in the master / slave channel; wherein, after the uplink transmission ends, the transmission opportunity will be returned; in step 104, the current idle channel is determined from the master channel and the slave channel through the second channel detection; in an example, a PIFS can be transmitted at this time, and in step 105, channel access is performed according to the current idle channel to try to continue to use the transmission opportunity. Further, the specific method may be: when the current idle channel is the main channel, the main channel is accessed to continue the downlink transmission within the remaining time of the transmission opportunity; when the current idle channel is the slave channel, the slave channel is accessed to continue the downlink transmission within the remaining time of the transmission opportunity; when the current idle channel is the main channel and the slave channel, the main channel and the slave channel are accessed to continue the downlink transmission within the remaining time of the transmission opportunity; when the current idle channel is empty, the transmission opportunity is abandoned and enhanced distributed channel access backoff is performed. Further, when the current idle channel is the slave channel, the method of accessing the slave channel to continue the downlink transmission within the remaining time of the transmission opportunity may be: when the current idle channel is the slave channel, the transmission opportunity value of the access category corresponding to the slave channel before accessing is inherited according to the remaining time length of the transmission opportunity.

[0027] In addition, the second channel detection is not only a signal detection, but also multiple repeated channel detections can be performed as the second channel detection within a preset allocated time, and the detection result of the second channel detection is determined according to the multiple detection results generated by the multiple repeated channel detections. It is also possible to determine whether there is at least one contention window between the multiple repeated channel detections in the second channel detection according to the contention window determination parameter; wherein the contention window is used to create a backoff time before accessing the channel; wherein the contention window size includes one of the following factors and any combination thereof: main channel enhanced distributed channel access parameters, QoS service type, access type (AC, access category), transmission opportunity restriction parameters, whether it is a main channel. When the object for sharing the transmission opportunity is an access point device, after determining the current idle channel from the main channel and the slave channel through the second channel detection, a channel will be selected from the current idle channel for channel access according to the channel where the indication frame for returning the transmission opportunity is located to try to continue to use the transmission opportunity.

[0028] In order to better understand the specific application of the above method in various execution entities, the implementation details of the transmission opportunity sharing method of the present application will be specifically described below with the execution entity being an AP and an embodiment of sharing transmission opportunities with a terminal.

[0029] First, let's discuss the first type of result obtained in step 101, that is, when the AP accesses the channel, it directly accesses the primary channel (the secondary channel is busy and the primary channel is idle). Figure 3As shown, within a TXOP, the AP shares the TXOP with at least one terminal. After the uplink transmission is completed, when TXOP-REMAINING is not zero. AP regains the TXOP. AP enters step 104 at the end of the allocated time, performs a channel sensing on the entire channel, and transmits a PIFS at the end of the allocated time. In step 105, if both the main channel and the slave channel are idle, a physical layer protocol data unit (PPDU for short) is transmitted on the main channel and the slave channel. Otherwise, the AP enters the Enhanced Distributed Channel Access (EDCA) backoff step. When a transmission opportunity (TXOP) starts, it starts with the AP competing for the channel, only grabbing the main channel resources, and the slave channel is busy. Then the TXOP is shared with a terminal for uplink transmission. After the uplink transmission is completed, the TXOP is not ended. Then the AP performs channel sensing (does a CCA) on the entire bandwidth. If the channel is idle, access the channel. The advantage is that when the TXOP obtained by the AP on the primary channel is returned to the AP after sharing, the AP can detect the status of the secondary channel again and try to obtain resources on the secondary channel again, thereby extending the TXOP in the frequency domain and improving resource utilization.

[0030] Since step 105 corresponds to more than one situation, within a TXOP, after the uplink transmission is completed, when TXOP-REMAINING is not zero. AP regains the TXOP. After the AP performs a channel sensing on the entire channel at the end of the allocated time, the AP transmits a PIFS at the end of the allocated time. If the main channel is busy and the slave channel is idle at this time, the AP transmits the PPDU on the slave channel. Among them, the allocated time is the transmission time allocated to the terminal by the AP sharing the TXOP in a TXOP; TXOP-REMAINING refers to a TXOP minus the time that the TXOP has been used. For this situation, here is another example of the main channel accessing the slave channel transmission opportunity, such as Figure 4As shown, when a transmission opportunity (TXOP) starts, the AP competes for the channel and only grabs the main channel resources, and the slave channel is busy. Then the TXOP is shared with a terminal for uplink transmission. After the uplink transmission is completed, the TXOP is not ended. Then the AP performs a channel detection (also called clear channel assessment, abbreviated as CCA, full name clear channel assessment) on the entire bandwidth. If the main channel is busy and the slave channel is idle, the slave channel is accessed. In some cases, after the uplink transmission is completed, the AP accesses the TXOP again. After the CCA is completed, the AP indicates that the main channel is busy and the slave channel is idle. Then the AP starts downlink transmission after transmitting for a PIFS. In some cases, the AP can start downlink transmission after a contention window after the uplink transmission is completed. In some cases, the AP can perform channel detection after a contention window after the uplink transmission is completed. If the channel is idle, the AP starts downlink transmission. In some cases, after the uplink transmission is completed, the AP can perform multiple channel detections (for example, m times, where m is a positive integer and m>1) after the CCA result indicates that the primary channel is busy and the secondary channel is idle after the CCA result is completed. If the results of m times are that the channel is idle, the AP starts the downlink transmission.

[0031] The second type of result obtained in step 101 is discussed. When a transmission opportunity (TXOP) starts, the AP competes for the channel and only grabs the secondary channel resources, and the primary channel is busy. Then the TXOP is shared with at least one terminal for uplink transmission.

[0032] The allocated time refers to the transmission time allocated to the terminal by the AP in a TXOP. In some cases, when the TXOP obtained from the channel access returns to the TXOP owner after the TXOP sharing (the allocated time ends), when TXOP-REMAINING is not zero, such as Figure 5 situation. Figure 5A situation of slave channel access is given, TXOP sharing ends, and then channel sensing is performed on the entire channel bandwidth. The sensing result shows that the main channel is idle and the slave channel is busy. At this time, the AP continues to transmit on the main channel as a way of TXOP sharing. No AP can transmit on the main channel. After the AP performs a channel sensing on the entire channel at the end of the allocated time, the AP transmits a PIFS at the end of the allocated time. If the main channel is idle, access the main channel and transmit PPDU. In some cases, the AP transmits SIFS at the end of the allocated time, or does not transmit anything. Otherwise, enter the EDCA backoff process.

[0033] In some cases, if the channel detection result indicates that the primary channel is idle and the slave channel is also idle, the PPDU is transmitted on the primary channel and the slave channel. In some cases, the primary channel NAV is not zero and transmission on the primary channel is not possible. Downlink transmission on the primary channel can only be performed when the NAV of the primary channel is 0.

[0034] In some cases, the TXOP obtained by accessing the slave channel, when the TXOP is shared and returns to the TXOP owner (the allocated time ends), when TXOP-REMAINING is not zero. Regardless of whether the primary channel NAV is zero, the AP cannot transmit on the primary channel. After the AP performs a channel sensing on the slave channel at the end of the allocated time, the AP transmits a PIFS at the end of the allocated time. If the slave channel is idle, the PPDU is transmitted on the slave channel. In some cases, the AP transmits SIFS at the end of the allocated time, or does not transmit anything.

[0035] Otherwise, enter the EDCA backoff process. Otherwise, in some cases, return to the main channel and enter the EDCA backoff process. The EDCA process is only implemented on the slave channel. Otherwise, in some cases, return to the main channel and enter the EDCA backoff process. The EDCA process is only implemented on the entire channel (slave channel and main channel). In some cases, the EDCA backoff step is performed on the granularity of the slave channel. In some cases, the EDCA backoff step is performed on the temporary main channel at the granularity of the slave channel.

[0036] In some cases, when the TXOP obtained by accessing the slave channel is shared and returns to the TXOP owner (the allocated time ends), when TXOP-REMAINING is not zero. Regardless of whether the main channel NAV is zero, the AP cannot transmit on the main channel. After the AP performs a channel sensing on the entire bandwidth at the end of the allocated time, the AP transmits a PIFS at the end of the allocated time. If the slave channel is idle, transmit the PPDU on the slave channel. If the slave channel is idle, continue to access the slave channel; if the slave channel is busy, end and do not transmit on the current slave channel. Perform one of the following steps on the main channel:

[0037] At this time, if a CCA is performed at the end of the uplink transmission, the main channel is idle, and the NAV on the main channel is not zero,

[0038] Then wait for a contention window time, and then make a CCA. If the CCA indicates that the channel is idle, access the primary channel for downlink transmission. The contention window size can be configured by the AP.

[0039] At this time, if a CCA is performed at the end of the uplink transmission, the main channel is idle and the NAV on the main channel is zero,

[0040] Then wait for a contention window time, and then make a CCA. If the CCA indicates that the channel is idle, access the primary channel for downlink transmission. The contention window size can be configured by the AP.

[0041] At this time, if a CCA is performed at the end of the uplink transmission, the main channel is idle, and the NAV on the main channel is not zero,

[0042] Then n more CCAs are made. If the n CCAs all indicate that the channel is idle, the primary channel is accessed for downlink transmission. The value of n can be configured by the AP, or n is determined by the access category (AC).

[0043] At this time, if a CCA is performed at the end of the uplink transmission, the main channel is idle and the NAV on the main channel is zero,

[0044] Then n more CCAs are made. If the n CCAs all indicate that the channel is idle, the primary channel is accessed for downlink transmission. The value of n can be configured by the AP, or n is determined by the access category.

[0045] At this time, if a CCA is performed at the end of the uplink transmission, the main channel is idle, and the NAV on the main channel is not zero,

[0046] Then make n more CCAs. If CCA is idle, n-1. If CCA is busy, n remains unchanged. If the n CCAs all indicate that the channel is idle, access the main channel for downlink transmission. The value of n can be configured by the AP, or n is determined by

[0047] The access category determines the

[0048] At this time, if a CCA is performed at the end of the uplink transmission, the main channel is idle and the NAV on the main channel is zero,

[0049] Then make n more CCAs. If CCA is idle, n-1. If CCA is busy, n remains unchanged. If the n CCAs all indicate that the channel is idle, access the main channel for downlink transmission. The value of n can be configured by the AP, or n is determined by accesscategory.

[0050] In one example, the selection of channel access and the use of contention windows are related to the EDCA type, the service, or the access category (AC), as shown in the following:

[0051] In some cases, when a transmission opportunity (TXOP) begins, the AP competes for the channel. The primary channel is busy and the secondary channel is idle. Only the secondary channel resources are grabbed. Access is made on the secondary channel for downlink transmission. After that, the TXOP is shared with a terminal for uplink transmission. After the uplink transmission is completed, the TXOP does not end. Then the AP performs a CCA on the entire bandwidth. If the secondary channel is idle, it continues to access the secondary channel; if the secondary channel is busy, it ends and does not transmit on the current secondary channel. At the same time, some of the above steps are performed on the primary channel, using the following strategy:

[0052] In some cases, depending on the primary channel EDCA parameter or CW size,

[0053] The method may be based on the following factors: (1) the number of packets transmitted, (2) the number of packets received, (3) the number of packets received, (4) the number of packets received, (5) the number of packets received, (6) the number of packets received, (7) the number of packets received, (8) the number of packets received, (9) the number of packets received, (10) the number of packets received, (11) the number of packets received, (12) the number of packets received, (13) the number of packets received, (14) the number of packets received, (15) the number of packets received, (16) the number of packets received, (17) the number of packets received, (18) the number of packets received, (19) the number of packets received, (20) the number of packets received, (21) the number of packets received, (22) the number of packets received, (23) the number of packets received, (24) the number of packets received, (25) the number of packets received, (26) the number of packets received, (27) the number of packets received, (28) the number of packets received, (29) the number of packets received, (30) the number of packets received, (41) the number of packets received, (42) the number of packets received, (43) the number of packets received, (44) the number of packets received, (45) the number of packets received, (46) the number of packets received, (47) the number of packets received, (48) the number of packets received, (49) the number of packets received, (50) the number of packets received, (51) the number of packets received, (52) the number of packets received, (53) the number of packets received, (54) the number of packets received, (55) the number of packets received, (56) the number of packets received, (57) the number of packets received, (58) the number of packets received, (59) the number of packets received, (60) the number of packets received, (61) the number of packets received,

[0054] In some cases, it is decided to use at least one of the above schemes according to the primary channel EDCA parameter, or CW size (contention window size), or QoS service type, or TXOP limit, such as deciding whether to access when the primary channel NAV is 0. For example, when transmitting low-latency services, even if the primary channel NAV is not 0 and the primary channel is available (the channel is detected as idle), it is also necessary to transmit on the current primary channel.

[0055] In some cases, it is determined based on the primary channel EDCA parameter, or CW size (contention window size), or QoS service type, or TXOP limit to use at least one of the above schemes. For example, to transmit low-latency services, n can be set to a smaller value in advance, without a contention window (or with a smaller contention window value).

[0056] In some cases, at least one of the above solutions may be used based on the EDCA parameter of the primary channel, or the CW size (contention window size), or the QoS service type, or the TXOP limit. For example, to transmit a low-latency service, the remaining time of the TXOP on the current slave channel may be estimated in advance. If the slave channel resources are insufficient to transmit the low-latency service within the current TXOP, the primary channel may be transmitted when the channel detection result is idle, even if the NAV is not 0.

[0057] In some cases, the slave channel access needs to return to the primary channel before the primary channel NAV is 0, so the TXOP duration of the slave channel access can be estimated. In some cases, the above EDCA parameter is used when accessing the slave channel.

[0058] Regarding the contention window, if the process of performing multiple channel detections is called channel sensing, Figure 6 A case of slave channel access is given, TXOP sharing ends, and then channel sensing is performed on the entire channel bandwidth. The sensing result shows that the master channel is idle and the slave channel is busy. At this time, a contention window passes on the master channel. After the contention window ends, the AP performs channel sensing on the master channel. If the channel is sensed as idle, the AP continues to transmit on the master channel as a way of TXOP sharing.

[0059] In some cases, the contention window is a backoff time, that is, after the TXOP transmission is completed, the AP performs channel sensing (the result is idle), and after a contention window (backoff time, or backoff time, or waiting time for performing channel sensing again), it performs channel detection again. At this time, the detection result is idle, and then channel access is performed.

[0060] The purpose of the contention window is to take care of the services of other devices on the main channel for fairness, or to give priority to the transmission of low-latency services. There may be a situation where the NAV is not updated in time, so join the contention window and then back off before accessing.

[0061] In some cases, channel sensing is called channel sensing, and a channel sensing is called a CCA (clear channel assessment).

[0062] In one example, if the EHT AP determines that transmission of the MU-RTS TXS trigger frame is successful and the CS mechanism indicates that the medium is busy at the end of the allotted time, the AP may transmit after the CS mechanism indicates that the medium is idle at the TxPIFS slot boundary or start the EDCA backoff process.

[0063] In some cases, after accessing the slave channel, channel sensing indicates that the channel is busy at the end of the allocated time, and then the AP can perform channel sensing and transmit data when the channel is idle at the edge of a TxPIFS time slot, or directly perform the EDCA fallback step. The channel is sensed as idle (including the perception of the slave channel and the perception of the master channel). If the perception result is idle, the above embodiment can be applied to perform channel access, or continue to back off, or continue to perform channel sensing.

[0064] In some cases, the slave channel can be divided into multiple granularities. In the above embodiments, the "slave channel" mentioned is a granularity of the slave channel, such as 80MHz; for example, the master channel is 160MHz. This granularity is adjacent to the master channel. The slave channel is accessed according to a granularity of the slave channel access negotiated by the terminal and the AP.

[0065] In connection with this, when the TXOP is accessed again, the master and slave channels use the same or different access methods and access parameters, and the following embodiments are generated based on this:

[0066] In some cases, the AP starts competing for channels. The primary channel is busy and the secondary channel is idle. It only grabs one transmission opportunity (TXOP) of the secondary channel resources. It accesses the secondary channel and performs downlink transmission. After that, the TXOP is shared with a terminal resource for uplink transmission. After the uplink transmission is completed, the TXOP does not end. Then, the AP accesses (or shares) the TXOP again.

[0067] At this time, use the same access method (or access parameters) for the master channel and the slave channel.

[0068] A CCA detection is performed once, and if the CCA indicates that the slave channel is idle, the slave channel is accessed. At the same time, a CCA detection is performed once on the master channel, and if the CCA indicates that the slave channel is idle, the master channel is accessed. Similarly, the solutions of the above other embodiments can be used.

[0069] At this time, different access methods (or access parameters) are used for the master channel and the slave channel. For example, m CCA detections are performed on the slave channel. If m CCAs indicate idleness, the slave channel is accessed. At the same time, n CCA detections are performed on the master channel.

[0070] If n CCAs indicate idleness, the master channel is accessed. Similarly, the solutions of other embodiments described above can be used. In some cases, if the master channel and the slave channel (one slave channel granularity) are adjacent in the frequency domain, the same parameters (or access methods) are used; if they are not adjacent, different parameters (or access methods) are used.

[0071] The access mode refers to the access method or access mode, or access parameters mentioned in the above embodiments, such as using a contention window, multiple channel sensing, access after one channel sensing PIFS, or EDCA, EDCA parameters, or considering NAV, or considering the channel service access category (AC, access category).

[0072] If the slave channel is idle, continue to access the slave channel; if the slave channel is busy, end and do not transmit on the current slave channel. If the master channel is idle, continue to access the master channel; if the master channel is busy, end and do not transmit on the current master channel. If both the master and slave channels are busy, start the EDCA backoff procedure.

[0073] In summary, the above-mentioned execution subject is AP, and the process of sharing transmission opportunities with the terminal can be simply described as follows: In some cases, the AP starts to compete for the channel, the main channel is busy, and the slave channel is idle. Only one transmission opportunity (TXOP) of the slave channel resource is grabbed. Access the slave channel and perform downlink transmission. After that, the TXOP is shared with a terminal resource for uplink transmission. After the uplink transmission is completed, or the TXOP is returned to the AP, the AP accesses the TXOP again, and accesses the main channel and the slave channel respectively. After exiting the TXOP, EDCA backoff is performed. In some cases, EDCA backoff is performed on the main channel, and in some cases, EDCA backoff is performed on the temporary main channel of the slave channel. In some cases, EDCA backoff on the slave channel uses the EDCA parameters newly designed for slave channel access. In some cases, EDCA backoff on the slave channel uses the EDCA parameters on the main channel for channel access.

[0074] The solution of the embodiment of the present application is applied to the following situations, such as the terminal shares with the AP, or the AP shares with the terminal, or the terminal P2P shares the TXOP, or an AP seizes the TXOP and needs to share it with another AP (AP coordination. In some cases, the above method process can also be used in the TXOP holder (owner) and the TXOP responder (TXOP responder) to return the TXOP, which is also applicable to the case of TXOP sharing. This will be discussed below.

[0075] For the sake of distinction, the device used for sharing (the executor of the method proposed in this application) is temporarily referred to as device 1, and the device to be shared is referred to as device 2. Device 1 and device 2 can be AP terminals, multi-connected AP devices, multi-connected non-AP devices, APs attached to multi-connected AP devices, or STAs attached to multi-connected non-AP devices.

[0076] When a device 1 performs channel detection to access a channel, the channel detection result indicates that the main channel is busy and the slave channel is idle (either through EDCA or EDCA newly defined for slave channel access), assume that device 1 obtains a TXOP through slave channel access. At this time, device 1 transmits in the TXOP it obtains and shares the TXOP with another device 2. At this time, device 2, after receiving the data from device 1, is about to start transmission.

[0077] Optionally, before the device 2 starts transmitting, it performs a channel detection on the slave channel. If the detection result is idle, it transmits on the slave channel. Otherwise, it does not transmit.

[0078] Optionally, before device 2 starts uplink transmission, it performs channel detection on the master channel and the slave channel. If the detection result of the slave channel is idle, transmission is performed on the slave channel. Otherwise, transmission is not performed on the slave channel. If the detection result of the master channel is idle, transmission is performed on the master channel. Otherwise, transmission is not performed on the master channel. In some cases, the transmission performed by device 2 is an uplink transmission to device 1; in some cases, the transmission performed by device 2 is a downlink transmission.

[0079] In some cases. When a device 1 performs channel detection to access a channel, and the channel detection result indicates that the main channel is busy and the slave channel is idle (or the result is obtained through EDCA, or the newly defined EDCA for slave channel access), device 1 obtains TXOP through slave channel access. At this time, device 1 transmits the TXOP it obtained and shares the TXOP with another device 2. At this time, device 2, after receiving the data from device 1, is about to start uplink transmission, or device 2 uses the above channel access scheme and parameters to access the slave channel, or device 2 uses the above channel access scheme and parameters to access the main channel.

[0080] In one example, the impact of TXOP definition is discussed. In some cases, the TXOP time length or dot11EDCATableTXOPLimit obtained from the channel access is used or inherited from the TXOP value of the corresponding access category (AC) of the main channel (or the entire channel). In some cases, a new TXOP value is defined for the slave channel access, including dot11EDCATableTXOPLimit or contention window size.

[0081] In some cases, the slave channel access uses its own set of EDCA parameters, which at least includes dot11EDCATableTXOPLimit, or the contention window size. In some cases, when the main channel NAV is 0, the current TXOP transmission is forced to end and return to the main channel. Perform EDCA backoff steps. In some cases, when the main channel NAV is 0, if the current TXOP is transmitting a service, after the service transmission is completed, the current TXOP transmission is ended and returns to the main channel. Perform EDCA backoff steps. In some cases, such as when a low-latency service is transmitted on the slave channel, when the main channel NAV is 0, the service transmission in the current TXOP is not ended. At this time, if the above situation (allocated time is not 0) occurs and the TXOP is regained, the method of switching from the channel TXOP to the main channel in the above embodiment is applied.

[0082] In some cases, the TXOP duration of the slave channel access is the remaining time after the relevant frame is received on the channel and the pre-estimated NAV is reduced to zero. If the TXOP obtained from the slave channel access is 0 when the NAV is 0, it returns to the main channel and performs the EDCA backoff procedure. In some cases, the TXOP obtained in this way can only be shared within the slave channel. For example, when the AP obtains a TXOP through slave channel access, shares it with at least one terminal (allocated time is not 0), and then re-acquires the TXOP, the remaining TXOP can only be re-acquired within the slave channel, and the following will not occur. Figure 4 The situation shown.

[0083] In some cases, when reacquiring the remaining TXOP from the channel, the following cases are given as examples:

[0084] ·AP (TXOP holder) performs channel sensing on the secondary channel at the end of the allocated time, and transmits a PIFS at the end of the allocated time. If the secondary channel is idle, PPDU is transmitted on the secondary channel. Otherwise, it returns to the primary channel and starts the EDCA backoff procedure.

[0085] In some cases, after the AP performs a channel sensing on the secondary channel at the end of the allocated time, the AP transmits a SIFS at the end of the allocated time, or does not transmit anything. If the secondary channel is idle, the AP transmits the PPDU on the secondary channel. Otherwise, the AP returns to the primary channel and starts the EDCA backoff procedure.

[0086] In some cases, after the AP performs a channel sensing on the secondary channel at the end of the allocated time, the AP does not transmit anything in a contention window (a waiting time) at the end of the allocated time, and then performs channel detection. If the secondary channel is idle, the PPDU is transmitted on the secondary channel. Otherwise, it returns to the primary channel and starts the EDCA backoff procedure. In some cases, the contention window is determined by the configuration or by the Access category.

[0087] In some cases, after the AP performs a channel sensing on the secondary channel at the end of the allocated time, the AP transmits the result at the end of the allocated time and performs multiple channel detections. If the secondary channel detection results are all idle, the PPDU is transmitted on the secondary channel. Otherwise, the primary channel is returned and the EDCA backoff procedure is started. The specific detection steps are determined by the AP configuration or the Access category.

[0088] In some cases, when device 1 is an AP and device 2 is also an AP, device 1 is called AP1 and device 2 is called AP2. AP1 obtains TXOP by accessing the slave channel and shares it with AP2. The master and slave channels of AP2 are staggered with those of AP1. Figure 7 As shown, AP1 shares TXOP with AP2. After AP2 completes the transmission, it returns TXOP to AP1. When AP1 accesses the channel again, it uses the above solution to access the channel. For example, Figure 7 As shown, a method with a contention window is used to obtain the primary channel.

[0089] exist Figure 7 In the example shown, in some cases, the slave channel obtained by AP1 is shared with AP2. From the perspective of AP2, it is working on the master channel. The following are examples:

[0090] In some cases, AP2 transmits only on the primary channel of AP2 within the shared TXOP (transmits only on the shared bandwidth and within the shared TXOP duration).

[0091] In some cases, AP2 can only perform channel sensing on the bandwidth of the shared TXOP before transmission. If the channel sensing result is idle, it will transmit in the shared TXOP. Otherwise, it will not transmit.

[0092] In some cases, before AP2 transmits, it performs channel sensing on the entire bandwidth of AP2. If the channel sensing result of AP2's main channel is idle, it transmits on AP2's main channel. Otherwise, it does not transmit on AP2's main channel.

[0093] If the channel sensing result on the slave channel of AP2 is idle, AP2 transmits on the slave channel of AP2. Otherwise, AP2 does not transmit on the slave channel of AP2. In some cases, can AP2 perform channel sensing on its slave channel before transmitting on the shared TXOP?

[0094] Awareness is configurable. In some cases, it is configured in an Agreement reached at the beginning of AP coordination.

[0095] In some cases, the channel sensing step before AP2 transmits on the shared TXOP can be replaced by

[0096] In the above embodiment of switching from the channel TXOP to the main channel, n CCAs are performed within the contention window, or

[0097] NAV is 0 test.

[0098] In some cases, the AP2 transmits to a terminal attached to the AP2 in the shared TXOP.

[0099] In a shared TXOP (in the bandwidth of the TXOP), before uplink transmission, a CCA may be performed once in accordance with the above embodiment, and then n CCAs may be performed in the contention window, or a NAV is checked to be 0.

[0100] In some cases, the AP2 transmits to a terminal attached to the AP2 in the shared TXOP.

[0101] On the shared TXOP, on the primary channel and the secondary channel of the terminal, the terminal uses the scheme in the embodiment of switching from the secondary channel TXOP to the primary channel, performs a CCA, starts the contention window, performs n CCAs, or checks that the NAV is 0, and performs channel access. In some cases, both the terminal and AP2 support secondary channel access.

[0102] Next, we discuss Figure 7In the example of TXOP sharing between two APs, in some cases, the primary and secondary channels of AP1 and AP2 are staggered. Before transmission, AP2 can only perform channel sensing on the bandwidth of the shared TXOP. If the channel sensing result is idle, it will transmit in the shared TXOP. Otherwise, it will not transmit. In some cases, including Figure 7 In the example of TXOP sharing between two APs, the main channels and the secondary channels of AP1 and AP2 are staggered. Before transmission, AP2 performs channel sensing on the entire bandwidth of AP2. If the result of channel sensing on the main channel of AP2 is idle, transmission is performed on the main channel of AP2, otherwise, transmission is not performed on the main channel of AP2. If the result of channel sensing on the secondary channel of AP2 is idle, transmission is performed on the secondary channel of AP2. Otherwise, transmission is not performed on the secondary channel of AP2. In some cases, both the terminal and AP2 support secondary channel access.

[0103] The following example shows how to return TXOP. Figure 7 In some cases shown, when TXOP is returned to AP1, the returned frame, such as CF-end frame, ACK frame, Batch ACK frame, will be transmitted on which channel, and AP1 will continue to access which channel. For example:

[0104] For example, if the frame from AP2 indicating the return of TXOP is transmitted on the slave channel of AP1, AP1 continues to access AP1's

[0105] Slave channel. Do not access the main channel.

[0106] For example, if the frame from AP2 indicating the return of TXOP is transmitted on the primary channel of AP1, AP1 continues to access AP1's

[0107] Master channel. Do not access slave channels.

[0108] For example, if the frame from AP2 indicating the return of TXOP is transmitted on the primary channel and the secondary channel of AP1, AP1 continues to receive

[0109] Enter the slave channel and master channel of AP1.

[0110] In some cases, the returned frames from AP2 are transmitted on the primary channel of AP1, and AP1 accesses the primary channel and the secondary channel of AP1. Or in some cases, the returned frames from AP2 are transmitted on the secondary channel of AP1, and AP1 accesses the primary channel and the secondary channel of AP1.

[0111] In some cases, the shared device (such as AP2) can only transmit data on the TXOP of the bandwidth indicated by the sharing device. In some cases, the indication is implicit, such as AP1 obtains the TXOP on the AP1 slave channel through slave channel access, and the TXOP can only be shared with AP2 on the AP1 slave channel, regardless of whether the TXOP corresponds to the AP2 master channel or the AP2 slave channel. At AP1. After AP2 returns the TXOP (TXOP-REMAINING is not 0), AP1 can only continue to access the TXOP on the initial slave channel. In some cases, a channel detection is performed first. If the channel detection result is idle, the TXOP is accessed after a period of time, otherwise the EDCA backoff step is performed. In some cases, the time is changed to PIFS, or SIFS, or 0. In some cases, the EDCA backoff step is performed on the entire channel bandwidth. In some cases, the EDCA backoff step is performed on the slave channel granularity. In some cases, the EDCA backoff step is performed on the temporary master channel at the slave channel granularity.

[0112] In one example, after accessing the master / slave channel by utilizing the transmission opportunity, negotiation is performed through the master / slave channel to confirm whether the transmission opportunity extension condition is currently met; when the transmission opportunity extension condition is met, the transmission opportunity will be utilized to simultaneously access the master channel and the slave channel; wherein the transmission opportunity extension condition will be determined by the service type and / or access category of the current transmission, and / or the transmission opportunity sharing mode.

[0113] In the following examples, the implementation method of extending the transmission opportunity (TXOP) will be exemplified, that is, if the current device only accesses the TXOP on the primary channel, the implementation method of extending the TXOP to the entire channel (primary channel and slave channel) in the frequency domain, and if the current device only accesses the TXOP on the slave channel, the implementation method of extending the TXOP to the entire channel (primary channel and slave channel) in the frequency domain will be given. In some cases, the target channel for the TXOP extension is a slave channel adjacent to the primary channel, or a portion of the slave channel. In some cases, the target channel for the TXOP extension is a primary channel adjacent to the slave channel, or a portion of the primary channel.

[0114] In some cases, whether to perform TXOP extension is a capability. The capability is included in a beacon, a probe response frame, a negotiation frame from a channel access, an energy saving frame, or a working mode control / configuration frame. In some cases, the capability is a field, which occupies one bit. 0 indicates that TXOP extension is not supported, and 1 indicates that TXOP extension is supported.

[0115] In the following examples, various examples of TXOP extension to deal with QoS services or low-latency services will be given. Specifically: In some cases, whether TXOP extension can be performed is determined by the service type. Service types include low-latency services. In some cases, if the current access point transmits low-latency services and currently occupies the TXOP of the primary channel, TXOP extension is allowed on the secondary channel. In some cases, whether TXOP extension is allowed when transmitting low-latency services is included in the secondary channel access control frame (initial control frame, ICF), such as a 1-bit in the frame, 0 means allowed, 1 means not allowed. In some cases, whether to extend the TXOP obtained only on the primary channel is a capability, marked by a bit 0 for allowed, 1 for not allowed. Similarly, whether to extend the TXOP obtained only on the secondary channel is a capability, marked by a bit 0 for allowed, 1 for not allowed.

[0116] In the following examples, various examples related to TXOP extension and services will be given. Specifically: In some cases, if the current access point transmits a low-latency service and the currently occupied TXOP is a slave channel, TXOP extension is allowed on the primary channel. In some cases, the TXOP extension enable is 1 bit, which is included in the slave channel access control frame. The indicator for supporting TXOP slave channel access in the trigger frame is one bit, 0 for not supported, and 1 for supported. In some cases, if the terminal device or AP supports slave channel access, TXOP extension is supported by default. In some cases, if the terminal device or AP supports slave channel access, additional negotiation is required, or configuration is required to determine whether TXOP extension is supported.

[0117] In some cases, TXOP extension is allowed only for specific QoS or specific access categories. Optionally, this information is included in the channel access control frame, or a field in the channel access control frame, or the EDCA access category description. For example, a field is defined in the EDCA parameter set element, with one bit: 0, indicating that TXOP extension is allowed for the access category, and 1 indicates that it is not allowed. In some cases, the signaling is a bitmap corresponding to each access category, 0 indicates that TXOP extension is allowed for the corresponding access category, and 1 indicates that it is not allowed. In some cases, whether to perform TXOP extension for low-latency services is included in the low latency control frame. Define a bit: 0, indicating that TXOP extension is allowed, and 1 indicates that it is not allowed.

[0118] In the following examples, various examples of TXOP extension when multiple APs or multiple AP MLDs (access point multi-connected devices) collaborate will be given: In some cases, whether the AP collaboration supports TXOP frequency domain extension will be negotiated and determined when multiple APs collaborate. It is included in the ICF (initial control frame) for TXOP sharing, or the trigger frame, or in the multi-AP collaboration request frame, or in the multi-AP collaboration response frame.

[0119] The following will take the case where two APs share TXOP as an example to explain that in some cases, supporting access from a channel is a capability. Or it is called TXOP frequency domain extension. In some cases, two APs that perform multi-AP collaboration, such as AP1 and AP2, do not have this capability, but AP2 has it, then AP2 performs TXOP extension on the TXOP it obtains. In some cases, AP1 and AP2 can be in a multi-AP collaboration relationship, or AP2 is a relay station of AP1.

[0120] In some cases, TXOP frequency domain extension is not limited by whether the TXOP is shared from other devices. As long as AP2 is capable of TXOP extension, AP2 needs to reacquire the TXOP after the TXOP allocated to its terminal ends, and then TXOP extension can be performed. Channel detection can be performed on the entire channel. If the channel detection result is idle, transmission is performed on all channels. A similar process is as follows Figure 8As shown. AP1 obtains a TXOP of the main channel and shares it with AP2. After AP2 finishes transmitting to its own terminal, AP2 needs to continue transmitting and needs to re-obtain TXOP. Then AP2 performs channel detection on the entire channel again. The detection result shows that the main channel is idle and the secondary channel is idle. AP2 continues to transmit. In some cases, when both AP1 and AP2 have TXOP expansion capabilities, AP2 can only perform the above operations by sharing the TXOP from AP1, or Figure 7 The operation shown.

[0121] In some cases, TXOP extension capability, or TXOP frequency domain extension capability, refers to the ability to access a slave channel, or the ability to access a non-primary channel. In some cases, TXOP extension refers to TXOP frequency domain extension, and TXOP is extended on adjacent or non-adjacent channels in the frequency domain, on a slave channel or a primary channel. In some cases, TXOP extension is a way to access a slave channel, or a way to access a non-primary channel.

[0122] The following are examples of TXOP extension when the channel combinations corresponding to the TXOP extension capabilities of two APs are inconsistent: In one example, AP1 shares the TXOP it has obtained with AP2. AP2 ends the transmission with its own terminal, but the shared TXOP has not ended yet. When AP2 regains the TXOP, it extends the TXOP. AP2 performs channel detection on the entire channel. If the channel detection result is idle, it accesses the corresponding channel. Otherwise, the TXOP is terminated and AP2 performs EDCA backoff. In some cases, only when the main channel and the slave channel of AP1 and AP2 are not staggered, as shown below Figure 8 Or in one example, only when the master channel and slave channel of AP1 and AP2 are staggered, as shown in the following example, Figure 7 In one example, two APs sharing a TXOP cannot obtain a new TXOP by performing TXOP extension, regardless of whether they have the TXOP extension capability. Another AP can only use the TXOP within the frequency and time domains of the TXOP originally specified by the shared AP. In some cases, TXOPs are shared between APs for multipe AP coordination.

[0123] The following examples are used to illustrate the location of TXOP extension: In some cases, when AP1 shares TXOP with AP2, AP1 sends a trigger frame to AP2 containing the duration and / or frequency range of the shared TXOP. After AP2 receives the TXOP sharing trigger frame, it immediately or after SIFS, attempts to extend the TXOP and performs channel detection on the entire channel of AP2. If the channel is detected as idle, AP2 transmits data on the explicitly idle channel. Otherwise, AP2 does not share the TXOP. In some cases, AP2, such as Figure 7 or Figure 8 In some cases, whether AP2 can immediately extend the TXOP after receiving the trigger frame for sharing the TXOP is indicated in the trigger frame, 0 means that it cannot be extended immediately, and 1 means that it can be extended immediately. In some cases, the specific position where AP2 extends the TXOP is determined by the received trigger frame indication, such as the specific time after which the TXOP can be extended.

[0124] In some cases, whether the TXOP can be extended is determined by the TXOP sharing mode. There are now two TXOP sharing modes, namely, the TXOP obtained by the terminal is shared with the access point, or the TXOP obtained by the access point is shared with the terminal, and the other mode is that the TXOP obtained by the terminal is shared with another terminal. The third mode is that the TXOP obtained by the newly defined access point is shared with another AP. In some cases, at least one of the above three cases / modes supports TXOP extensibility. In some cases, at least one of the above three cases / modes supports TXOP extensibility and is configurable, using the above-mentioned ICF or through negotiation configuration, the relevant configuration and mode indication are included in the ICF or negotiation frame, and the relevant signaling is similarly designed and will not be repeated.

[0125] In some cases, the AP2 obtains the TXOP through a terminal sharing, not through AP1. Or the AP1 shares the TXOP of a part of the slave channel in the frequency domain of AP2, or the AP1 shares the TXOP of a part of the slave channel in the frequency domain of AP2 and includes a temporary main channel. The temporary main channel is a channel with the function of the main channel defined to replace the main channel when the slave channel is accessed, or it is called the second main channel. In some cases, the AP1 and / or AP2 are multi-connection access devices, or access points attached to multi-connection devices of different access points.

[0126] In this embodiment, the first channel detection is used to compete for the channel; after the channel competition is over, the transmission opportunity of the master / slave channel obtained through the competition is accessed in the master / slave channel to perform downlink transmission in the master / slave channel; uplink transmission is performed in the master / slave channel by sharing the transmission opportunity; after the uplink transmission is over, the transmission opportunity will be returned; the current idle channel is determined from the master channel and the slave channel through the second channel detection; channel access is performed according to the current idle channel to try to continue to use the transmission opportunity. In the case of slave channel access, the remaining TXOP returned is fully used. Channel resources can be used more fully.

[0127] The steps of the above method are divided only for clear description. When implemented, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this application; adding insignificant modifications to the algorithm or process or introducing insignificant designs without changing the core design of the algorithm and process are all within the scope of protection of this application.

[0128] Another embodiment of the present invention relates to an access point, such as Fig. 9 As shown, it includes at least one processor 901; and a memory 902 that is communicatively connected to the at least one processor; wherein the memory 902 stores instructions that can be executed by the at least one processor 901, and the instructions are executed by the at least one processor 901 so that the at least one processor 901 can execute the transmission opportunity sharing method as described above.

[0129] Among them, the memory 902 and the processor 901 are connected in a bus manner, and the bus may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors 901 and the memory 902 together. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art, and therefore, are not further described herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. The data processed by the processor 901 is transmitted on a wireless medium through an antenna, and further, the antenna also receives data and transmits the data to the processor 901.

[0130] The processor 901 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management and other control functions. The memory 902 can be used to store data used by the processor 901 when performing operations.

[0131] Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0132] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0133] Those skilled in the art will appreciate that the above-mentioned embodiments are specific examples for implementing the present invention, and in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present invention.

Claims

1. A transmission opportunity sharing method, characterized in that: Applied to a first access point device, the method includes: Compete for a channel by first channel detection; After the contention for the channel ends, the transmission opportunity of the master / slave channel obtained through the competition is accessed in the master / slave channel to perform downlink transmission to the terminal in the master / slave channel; By sharing the transmission opportunity with the terminal, so that the terminal performs uplink transmission in the master / slave channel; Wherein, after the uplink transmission is completed, the transmission opportunity will be returned; Determine a current idle channel from the master channel and the slave channel through a second channel detection; Channel access is performed according to the current idle channel to try to continue to utilize the transmission opportunity.

2. The transmission opportunity sharing method according to claim 1, characterized in that: The performing channel access according to the current idle channel to try to continue to utilize the transmission opportunity comprises: When the current idle channel is a primary channel, accessing the primary channel to continue the downlink transmission during the remaining time of the transmission opportunity; When the current idle channel is a slave channel, accessing the slave channel to continue the downlink transmission during the remaining time of the transmission opportunity; When the current idle channel is a master channel and a slave channel, accessing the master channel and the slave channel to continue the downlink transmission during the remaining time of the transmission opportunity; When the current idle channel does not exist, the transmission opportunity is abandoned and enhanced distributed channel access backoff is performed.

3. The transmission opportunity sharing method according to claim 2, characterized in that: When the current idle channel is a slave channel, accessing the slave channel to continue the downlink transmission during the remaining time of the transmission opportunity includes: When the current idle channel is a slave channel, the transmission opportunity value of the access category corresponding to the access to the slave channel before accessing the slave channel is inherited according to the remaining time length of the transmission opportunity.

4. The transmission opportunity sharing method according to any one of claims 1 to 3, characterized in that: The second channel detection includes: A plurality of repeated channel detections are performed within a preset allocated time as the second channel detection, and a detection result of the second channel detection is determined according to a plurality of detection results generated by the plurality of repeated channel detections.

5. The transmission opportunity sharing method according to claim 4, characterized in that: The method further comprises: determining, according to a contention window determination parameter, whether at least one contention window still exists between the multiple repeated channel detections in the second channel detection; The contention window is used as a backoff time before the last channel access.

6. The transmission opportunity sharing method according to claim 1, characterized in that: The method further comprises: After determining the current idle channel from the master channel and the slave channel through the second channel detection, a PIFS is transmitted.

7. The transmission opportunity sharing method according to claim 1, characterized in that: The method further comprises: When the transmission opportunity is shared with the second access point, after determining the current idle channel from the main channel and the slave channel through the second channel detection, a channel will be selected from the current idle channels for channel access based on the channel where the indication frame for returning the transmission opportunity is located to try to continue to use the transmission opportunity.

8. The transmission opportunity sharing method according to claim 7, characterized in that: The method further comprises: Whenever the transmission opportunity is used to access the master / slave channel, negotiation is performed through the master / slave channel to confirm whether a transmission opportunity extension condition is currently met; When the transmission opportunity extension condition is met, the transmission opportunity is utilized to simultaneously access the master channel and the slave channel; The transmission opportunity extension condition is determined by one or any combination of the following information: The service type of the current transmission, the access category, the transmission opportunity sharing mode, whether the first access point supports the slave channel access capability, and whether the master / slave channels of the first access point and the second access point are staggered.

9. An access point, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the transmission opportunity sharing method according to any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the transmission opportunity sharing method according to any one of claims 1 to 8 is implemented.

Images