Channel access method, electronic device and storage medium

Abstract

The embodiments of the present invention relate to the field of communications, and disclose a slave channel access method, an electronic device, and a storage medium. The method includes: after determining that a terminal has the slave channel access capability, negotiating slave channel access with the terminal, and reaching a consensus with the terminal on the slave channel access method; when the main channel is unavailable or busy, determining whether there is an idle slave channel in the slave channels that have reached a consensus with the terminal on the slave channel access method; sending MU‑RTS to the terminal on the determined idle slave channel; receiving CTS sent by the terminal on the slave channel indicated by the MU‑RTS or on the slave channel determined according to specific rules. The embodiments of the present invention improve the channel utilization rate of the terminal when transmitting data in MU‑MIMO and OFDMA modes by using slave channel access to transmit data when the main channel is busy.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a slave channel access method, electronic equipment and storage medium. Background Art

[0002] MU-RTS (MU-RTS Trigger fame) is introduced by Wi-Fi 6 and has all the benefits of the RTS / CTS mechanism. MU-RTS is transmitted by the Wireless Access Point (AP) to multiple terminals at one time, reducing the occupation of air interface resources by multiple RTS / CTS transmissions. The receiving end replies to CTS in the form of Multi-User Multiple-Input Multiple-Output (MU-MIMO). MU-RTS can be used as an efficient AP and terminal interaction method during OFDMA (Orthogonal Frequency Division Multiple Access) or MU-MIMO transmission. MU-RTS, as a trigger frame, is described in detail in the Wi-Fi 6 and Wi-Fi 7 standards.

[0003] In the existing channel access, MU-RTS is an enhancement of RTS. MU-RTS is transmitted on all available 20MHz of the channel. CTS is transmitted on the designated (primary) channel, or on the primary channel and repeatedly on the secondary channel. In the case of secondary channel access, when the primary channel is unavailable or busy, how to transmit MU-RTS and CTS has become an issue of concern in the industry. Summary of the invention

[0004] The purpose of the embodiments of the present invention is to provide a slave channel access method, electronic device and storage medium, which can access the slave channel when the main channel is busy, avoid the waste of slave channel resources caused by leading channel access according to the busy or idle situation of the main channel, and achieve the effect of improving channel utilization.

[0005] To solve the above technical problems, an embodiment of the present invention provides a slave channel access method, comprising:

[0006] After determining that the terminal has the secondary channel access capability, performing secondary channel access negotiation with the terminal and reaching a consensus with the terminal on the secondary channel access method;

[0007] When the main channel is unavailable or busy, determine whether there is an idle slave channel among the slave channels that have reached a consensus on the slave channel access mode with the terminal;

[0008] Send MU-RTS to the terminal on a determined idle slave channel;

[0009] The CTS sent by the terminal is received on the secondary channel indicated by the MU-RTS or on the secondary channel determined according to a specific rule.

[0010] An embodiment of the present application further provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor;

[0011] 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 so that the at least one processor can execute the slave channel access method as described above.

[0012] The embodiments of the present application further provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the slave channel access method as described above.

[0013] The implementation method of the present application determines that the terminal has the ability to access the slave channel, then negotiates with the terminal on the slave channel access, and reaches a consensus with the terminal on the slave channel access method; when the main channel is unavailable or busy, determines whether there is an idle slave channel in the slave channels on which the slave channel access method has been agreed with the terminal; sends MU-RTS to the terminal on the determined idle slave channel; receives CTS sent by the terminal on the slave channel indicated by MU-RTS or on the slave channel determined according to specific rules. In the above manner, when the main channel is unavailable or busy, the slave channel is utilized, which improves the data transmission efficiency while avoiding the waste of slave channel resources and improving the channel utilization rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a specific flow chart of a slave channel access method according to an embodiment of the present invention;

[0015] Figure 2 is a schematic diagram of a channel according to an embodiment of the present invention;

[0016] Figure 3 is a specific flow chart of a slave channel access method according to another embodiment of the present invention;

[0017] Figure 4 is a schematic diagram of channel coding according to another embodiment of the present invention Figure 1 ;

[0018] Figure 5 is a schematic diagram of channel coding according to another embodiment of the present invention Figure 2 ;

[0019] Figure 6 is a schematic diagram of channel coding according to another embodiment of the present invention Figure 3 ;

[0020] Figure 7 is a schematic diagram of CTS response transmission according to another embodiment of the present invention;

[0021] Figure 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the embodiments of the present application 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 present application, 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 also be implemented. The division of the following embodiments is for the convenience of description, and the specific implementation of the present application should not be construed as any limitation, and the various embodiments can be combined and referenced with each other under the premise of no contradiction.

[0023] In the Wi-Fi standard 802.11be Draft 3.1, the EHT variant User Info field format corresponding to the User Infofield list in the MU-RTS Trigger frame is as follows: Figure 1 As shown in the figure, B12 to B19 indicate on which primary channel the CTS corresponding to MU-RTS is transmitted. When the primary channel is unavailable or busy and a secondary channel is required to be accessed, how is the MU-RTS Trigger frame and CTS transmitted?

[0024] In order to solve the above problems, the implementation method of the present application provides a solution for slave channel access. The slave channel access is achieved through the execution process of negotiation between AP and terminal, channel perception by AP, transmission of RTS by AP to terminal, and transmission of CTS by terminal to AP. After the transmission of CTS is completed, the slave channel access is completed. In this process, the channels within the bandwidth are numbered, and the transmission method of MU-RTS trigger frame (hereinafter referred to as MU-RTS) and its response CTS are clarified. The channel utilization rate of the terminal is improved when transmitting in MU-MIMO and OFDMA mode.

[0025] One embodiment of the present application relates to a slave channel access method, such as Figure 1As shown, the specific implementation steps of the slave channel access method of the embodiment of the present application are as follows. It should be noted that the following content is only the implementation details provided for the convenience of understanding and is not necessary for the implementation of this solution.

[0026] Step 101: after determining that the terminal has the capability of slave channel access, conduct slave channel access negotiation with the terminal and reach a consensus with the terminal on the slave channel access method.

[0027] The slave channel may also be referred to as a secondary channel or a non-primary channel. When Wi-Fi detects that the primary channel is busy, if a slave channel is detected as idle, Wi-Fi can transmit information on the idle slave channel.

[0028] Specifically, if an idle slave channel is to be used to transmit information between the terminal and the AP, the AP and the terminal need to determine in advance that each other has the ability to access the slave channel before the slave channel access step can be performed. After confirming that both the AP and the terminal have the ability to access the slave channel, the AP and the terminal will negotiate the slave channel access. After the negotiation, the AP and the terminal reach a consensus on the access method of the slave channel. In some examples, the ability to access the slave channel can be embodied in the form of an identifier. The AP or the terminal carrying the identifier indicates that the AP or the terminal has the ability to access the slave channel. The present application does not impose specific restrictions on the specific embodiment and judgment method of the channel access capability. Only when the AP and the terminal both have the ability to access the slave channel and the AP and the terminal that have the ability to access the slave channel are confirmed to have the ability to access the slave channel will the slave channel access negotiation be performed. The content of the negotiation may at least include various parameters of the slave channel access such as the channel bandwidth, the adjustment method MCS, the slave channel access granularity, the slave channel contention window size, etc. The present application does not impose specific restrictions on this. After the negotiation, the AP and the terminal reach an agreement on the specific content of the previous negotiation, that is, the AP reaches a consensus with the terminal on the slave channel access method.

[0029] Step 102: When the master channel is unavailable or busy, determine whether there is an idle slave channel among the slave channels for which a slave channel access mode consensus has been reached with the terminal.

[0030] Specifically, the busy or idle status of the main channel can be sensed through channel sensing. When the main channel is sensed to be busy or unavailable, the slave channel can be sensed to determine whether there is an idle slave channel among the slave channels for which a consensus has been reached with the terminal on the slave channel access method, and then the idle slave channel can be used for transmission.

[0031] Step 103: Send MU-RTS to the terminal on the determined idle slave channel.

[0032] Specifically, after determining through channel sensing that there is an idle slave channel among the slave channels on which a consensus has been reached with the terminal on the slave channel access method, the AP sends MU-RTS to the terminal on the determined idle slave channel. When the number of determined idle slave channels is greater than 1, MU-RTS may be sent to the terminal on all determined idle slave channels, or one or more slave channels may be selected from all determined idle slave channels, and MU-RTS may be sent to the terminal on the selected one or more slave channels. The present application does not impose specific restrictions on whether the slave channels for sending MU-RTS to the terminal are all determined idle slave channels or a portion of all determined idle slave channels.

[0033] Step 104: Receive the CTS sent by the terminal on the secondary channel indicated by the MU-RTS or on the secondary channel determined according to a specific rule.

[0034] Specifically, after the AP sends MU-RTS to the terminal on a determined idle slave channel, if the terminal receives the MU-RTS sent from the slave channel, the terminal can transmit a return CTS on the slave channel where the MU-RTS was received; or, the AP indicates the slave channel on which the terminal returns the CTS in the MU-RTS sent to the terminal on the determined idle slave channel, and the AP receives the CTS sent by the terminal on the slave channel indicated by the MU-RTS; or, on a slave channel determined according to specific rules, the AP receives the CTS sent by the terminal. In some cases, CTS may also be called self-CTS, or CTS-to-self.

[0035] Compared with the related art, the above embodiment of the present application determines that the terminal has the ability to access the slave channel, then negotiates with the terminal on the slave channel access, and reaches a consensus with the terminal on the slave channel access method; when the main channel is unavailable or busy, determines whether there is an idle slave channel in the slave channel on which the slave channel access method has been agreed with the terminal; sends MU-RTS to the terminal on the determined idle slave channel; receives CTS sent by the terminal on the slave channel indicated by MU-RTS or on the slave channel determined according to specific rules. In the above manner, when the main channel is unavailable or busy, the slave channel is utilized, which improves the data transmission efficiency while avoiding the waste of slave channel resources and improving the channel utilization.

[0036] Another embodiment of the present invention relates to a method for accessing a slave channel. This embodiment is a refinement of the method for accessing a slave channel in the aforementioned embodiment, and the specific contents are as follows.

[0037] In one example, a specific implementation method of performing a slave channel access negotiation with a terminal and reaching a consensus with the terminal on the slave channel access method may be: determining the consensus content of the slave channel access method by sending and receiving a slave channel access negotiation frame with the terminal.

[0038] Specifically, when the AP needs to negotiate with the terminal for secondary channel access, the AP and the terminal can send a secondary channel access negotiation frame to each other for negotiation. For example, the terminal sends a secondary channel access negotiation frame to the AP, and after the AP receives the secondary channel access negotiation frame sent by the terminal, it returns a secondary channel access negotiation frame to the terminal, and after the terminal receives the secondary channel access negotiation frame returned by the AP, it reaches a consensus with the AP.

[0039] In an example, the slave channel access negotiation frame may include: a slave channel access request frame request frame initiated by the negotiation initiator, and a slave channel access response frame response frame fed back by the negotiation responder;

[0040] The consensus content of the slave channel access mode is carried in at least one of a slave channel access request frame and a slave channel access response frame.

[0041] Specifically, there is no active or passive relationship in the negotiation between the terminal and the AP. The party that initiates the secondary channel access negotiation will be the negotiation initiator, and the remaining party will be the negotiation responder. The negotiation initiator sends a secondary channel access request frame to the negotiation responder. After receiving the secondary channel access request frame, the negotiation responder returns a secondary channel access response frame to the negotiation initiator. For example, when the secondary channel access negotiation is initiated by the terminal, the terminal is the negotiation initiator and the AP is the negotiation responder. The terminal sends a secondary channel access request frame to the AP. After receiving the secondary channel access request frame, the AP returns a secondary channel access response frame to the terminal. When the secondary channel access negotiation is initiated by the AP, the AP is the negotiation initiator and the terminal is the negotiation responder. The AP sends a secondary channel access request frame to the terminal. After receiving the secondary channel access request frame, the terminal returns a secondary channel access response frame to the AP.

[0042] Specifically, since the AP and the terminal need to negotiate through the channel access negotiation frame to determine the consensus content of the channel access method, the consensus content of the channel access method can be carried in at least one of the channel access request frame requestframe and the channel access response frame response frame. The present application does not impose specific restrictions on this. Specifically, in some examples, the consensus content in the channel access negotiation frame includes at least: channel access bandwidth, available channel bitmap, channel access granularity, channel perception granularity, channel access modulation mode, channel contention window size, access type parameters and QoS (Quality of Service) parameters, or any one or a combination of two or more of them. The present application does not impose specific restrictions on the consensus content in the channel access negotiation frame.

[0043] In another example, the specific steps of determining in step 101 that the terminal has the ability to access the slave channel include:

[0044] Based on the information element field of the terminal, or the secondary channel access function identifier recorded by the receiving vector or the sending vector, determine whether the terminal has the secondary channel access function; based on the information element field of the terminal, or based on the receiving vector or the sending vector of the terminal, or the secondary channel access granularity identifier recorded by the channel access negotiation frame, determine that the terminal has the channel granularity for secondary channel access.

[0045] Specifically, it is possible to determine whether the terminal has the secondary channel access function based on the secondary channel access function identifier recorded in the information element field (information element field) of the terminal, or the receiving vector (RxVector) or the transmitting vector (TxVector). For example, if it is determined whether the terminal has the secondary channel access function based on the information element field (information element field) of the terminal, it can be specifically manifested that when the information element field (information element field) of the terminal is identified as 1, it is determined that the terminal has the secondary channel access function; when the information element field (information element field) of the terminal is identified as 0, it is determined that the terminal does not have the secondary channel access function.

[0046] After determining that the terminal or AP has the function of sub-channel access, the specific method of access should be further confirmed based on the sub-channel access granularity of the terminal or AP. The sub-channel access granularity can be understood as an attribute of the sub-channel access function. On the basis of determining that the terminal or AP has the function of sub-channel access, the sub-channel access is performed at a specific channel granularity. Similar to the process of determining the sub-channel access function, the channel granularity at which the terminal has sub-channel access can be determined based on the sub-channel access granularity identifier recorded by the terminal's information element field (information elementfield), or the receiving vector (RxVector) or the transmitting vector (TxVector). Specifically, the sub-channel access granularity can be 20MHz, 40MHz, 80MHz, 160MHz or 320MHz. The present application does not impose specific restrictions on the size of the sub-channel access granularity, and it can be adjusted according to specific needs in actual applications.

[0047] In some cases, the sub-channel access granularity may be included in the sub-channel access negotiation frame. The sub-channel access negotiation frame may include: a sub-channel access request frame request frame initiated by the negotiation initiator, and a sub-channel access response frame response frame fed back by the negotiation response end. That is, the sub-channel access granularity may be included in at least one of the sub-channel access request frame request frame and the sub-channel access response frame response frame, and the present application does not impose specific restrictions on this. Since the AP and the terminal determine the consensus content of the sub-channel access method by sending and receiving sub-channel access negotiation frames, when the sub-channel access granularity is included in the sub-channel access negotiation frame, the sub-channel access granularity is included in the sub-channel access consensus agreement reached by the terminal and the AP through negotiation.

[0048] In another example, the specific judgment process of determining whether there is an idle slave channel among the slave channels for which the slave channel access mode consensus has been reached with the terminal in step 102 may be:

[0049] Through binary backoff, channel detection is performed at a preset sensing granularity on a slave channel that has reached a consensus with the terminal on the slave channel access mode to obtain channel energy, and when it is detected that the channel energy is lower than a preset threshold value, it is determined that the slave channel corresponding to the sensing granularity is idle, or;

[0050] When it is detected that the channel energy is lower than a preset threshold value and it is detected that the network allocation vector indicates that the slave channel is idle, it is determined that the slave channel corresponding to the sensing granularity is idle;

[0051] The perception granularity is less than or equal to the access granularity of the slave channel in the consensus reached on the slave channel access method.

[0052] Specifically, in some cases, in step 102, while performing slave channel sensing, the master channel sensing may also be performed. The specific sensing process of the master channel sensing and the slave channel sensing is the same, and this application does not make a distinction. After completing a binary backoff sensing process, if the result is that the master channel is busy and the slave channel is idle, the slave channel access is performed.

[0053] The secondary channel perception granularity is the granularity at which the terminal or AP performs CCA (Clear Channel Assessment) to detect whether the secondary channel is busy or idle. It is usually 20MHz, and this application does not impose any specific restrictions on this. The secondary channel access granularity is the granularity at which the terminal accesses the secondary channel, which can be 20MHz, 40MHz, 80MHz, 160MHz, etc., and this application does not impose any specific restrictions on this. In general, the secondary channel perception granularity and the secondary channel access granularity in the secondary channel access method consensus are the same by default, and the secondary channel perception granularity can also be smaller than the secondary channel access granularity in the secondary channel access method consensus.

[0054] Binary Exponential Back off means that when encountering repeated conflicts, the station will repeat the transmission, but after each conflict, the average delay will double. Because when detecting whether there is an idle slave channel, all slave channels that have reached a consensus on the slave channel access method have been determined between the terminal and the AP, and the consensus content includes the slave channel access granularity. Through the binary backoff method, within the slave channel access granularity range in the consensus content, for the slave channels that have reached a consensus on the slave channel access method with the terminal, channel detection (CCA) is performed according to the preset slave channel perception granularity to obtain channel energy, and when it is detected that the channel energy is lower than the preset threshold value, it is determined that the slave channel corresponding to the perception granularity is idle.

[0055] Correspondingly, the slave channel sensing granularity within the slave channel access granularity is used to perform channel sensing on all slave channels, and access can only be performed when all slave channels corresponding to the slave channel sensing granularity within the slave channel access granularity are displayed as idle channels. In some cases, the access granularity of the slave channel includes at least one complete sensing granularity, or includes part of the channels in at least one sensing granularity. For example, when the slave channel access granularity is 40MHz and the slave channel sensing granularity is 20MHz, two 20MHz bandwidths are included in the slave channel access granularity. Only after each 20MHz bandwidth channel performs channel detection (CCA) to obtain channel energy, it is detected that the channel energy of each 20MHz bandwidth channel is lower than the preset threshold value, and it is determined that the two 20MHz slave channels corresponding to each 20MHz sensing granularity are idle. That is, when all sub-channels corresponding to the 20MHz slave channel sensing granularity within the 40MHz slave channel access granularity are displayed as idle channels, the terminal or AP performs slave channel access of the 40MHz granularity. Sub-channel interference can be avoided by performing slave channel access in the above manner.

[0056] In some cases, when judging whether a slave channel is idle, in addition to considering the above-mentioned channel energy, it is also necessary to consider the situation of the network allocation vector (NAV). When the slave channel that has reached a consensus with the terminal on the slave channel access method is detected at a preset perception granularity to obtain the channel energy, and the channel energy of the slave channels corresponding to all the slave channel perception granularities within the slave channel access granularity is detected to be lower than the preset threshold value, the network allocation vector NAV is marked as 0 before slave channel access can be performed. For example, when the slave channel access granularity is 80MHz and the slave channel perception granularity is 20MHz, only after the 4 20MHz slave channels within the 80MHz slave channel access granularity perform channel detection (CCA) to obtain channel energy, it is detected that the channel energy of each 20MHz bandwidth channel is lower than the preset threshold value, and at the same time, the network allocation vectors NAV of the 4 20MHz slave channels are all 0. At this time, the 4 20MHz slave channels within the 80MHz channel access granularity are idle, and the slave channel access of the 80MHz slave channel access granularity is performed. In some cases, the sub-channel perception granularity can be limited. For example, in the previous example where the sub-channel access granularity is 80MHz, the sub-channel perception granularity of 40MHz is not used. Because the measurement of interference is more detailed when the sub-channel perception granularity is 20MHz compared to the perception granularity of 40MHz. Whether to limit the sub-channel perception granularity under a certain sub-channel access granularity can be set according to the needs of the actual application, and this application does not make specific limitations.

[0057] In one example, the access granularity of the slave channel corresponds to a continuous or discontinuous channel, and / or the access granularity of the slave channel has a binding or non-binding relationship with the channel.

[0058] Specifically, the access granularity of the slave channel corresponds to continuous or discontinuous channels. For example, when the slave channel access granularity is 40MHz, it can be two adjacent channels with a bandwidth of 20MHz, or it can be two non-adjacent channels with a bandwidth of 20MHz. The present application does not impose specific restrictions on the access granularity of the slave channel corresponding to continuous or discontinuous channels. The slave channel perception granularity and the slave channel access granularity are not limited to the slave channel bandwidth and the main channel bandwidth. For example, under a bandwidth of 320MHz, the main channel is 160MHz and the slave channel is also 160MHz. The slave channel perception granularity and the slave channel access granularity can be determined specifically according to the capabilities of the terminal and the AP. For example, when the slave channel perception granularity is 20MHz and the slave channel access granularity is 80MHz, at this time, the slave channel access can be accessed on four 80MHz bandwidths of 320MHz, without being limited by the 160MHz bandwidth limit of the main and slave channels.

[0059] Specifically, the access granularity of the channel has a binding or non-binding relationship with the channel, such as Figure 2 As shown in the figure, within the 160MHz bandwidth, when the channel access granularity is 40MHz and the channel perception granularity is 20MHz, if the channel perception CCA of G2 and G3 at the 40MHz access granularity respectively shows that the G2 and G3 channels are busy. At the same time, G21 and G22 are the 20MHz sub-channels of G2, the channel perception result of G21 is busy, and the channel perception result of G22 is idle; G31 and G32 are the 20MHz sub-channels of G3, the channel perception result of G31 is idle, and the channel perception result of G32 is busy. At this time, G22 and G31 constitute an idle channel with a 40MHz access granularity ( Figure 2 Idle Channel in the channel). That is, two adjacent 40MHz access granularities, each with a 20MHz channel, are combined into a 40MHz access granularity for secondary channel access. Since the channel access granularity is not bound to a specific channel, adjacent access granularities can be bound for secondary channel access, further improving channel utilization.

[0060] In some cases, channel binding access at adjacent access granularity can be understood as a capability of a terminal or access point. Based on the channel binding access identifier of the adjacent access granularity recorded by the receiving vector (RxVector) or the sending vector (TxVector) of the terminal or AP, it is determined whether the terminal or AP has the capability of channel binding access at adjacent access granularity. When the identifier is 0, it indicates that the terminal or AP supports channel binding at adjacent access granularity, and when the identifier is 1, it indicates that the terminal or AP does not support channel binding at adjacent access granularity. Compared with the related art, the above-mentioned embodiments of the present application can further reduce sub-channel interference by confirming the access capability of the slave channel, negotiating the access from the channel, reaching an access consensus, and introducing the access granularity from the channel, the perception granularity from the channel, and various access rules, which is conducive to the transmission of high-reliability services, and setting the access granularity of the slave channel to correspond to a continuous or discontinuous channel, and / or the access granularity of the slave channel has a binding or non-binding relationship with the channel, which can make the slave channel more flexible to access, and further improve the utilization of the channel.

[0061] Another embodiment of the present application relates to a slave channel access method. The slave channel access method of this embodiment is a further refinement of the slave channel access method in the previous embodiment, and the specific contents are as follows.

[0062] In step 104, when a CTS sent by a terminal is received on a slave channel indicated by MU-RTS, the indication method of a slave channel for receiving CTS from a slave terminal based on MU-RTS indication includes:

[0063] Based on the indication method of the RU Allocation field in the user infofield in the user info list field in the reused MU-RTS trigger frame, and based on the indication method of the improved RU Allocation field.

[0064] Specifically, sending MU-RTS to the terminal on the determined idle slave channel may be sending MU-RTS to the terminal on all the determined idle slave channels, and after receiving the MU-RTS, the terminal may receive the CTS sent by the terminal based on the slave channel indicated by the MU-RTS. Reuse means not increasing or decreasing the RU Allocation field value in the user info field in the user info list field in the existing MU-RTS trigger frame, and MU-RTS is transmitted on all available 20MHz bandwidths; improvement means increasing the RU Allocation field value in the user info field in the user info listfield in the MU-RTS trigger frame. For the RU Allocation field value or channel number, refer to 802.11be Draft 3.0.

[0065] In an example, the secondary channel for receiving the CTS sent by the terminal is determined by indicating the RU Allocation field in the user info field in the user info list field in the reused MU-RTS trigger frame, which may be:

[0066] Based on the joint indication of PS160 and RU Allocation field in the user info field, or the indication of UL BW subfield in the Common Info field in MU-RTS, the channel granularity of the main channel in the RU Allocation field (the field corresponding to RU allocation) is mapped to the channel granularity of the slave channel used to receive CTS.

[0067] Specifically, the two parameters of PS160 and RU Allocation field are used for joint indication, or only UL BWsubfield is used for indication. Both indication methods can map the channel number of the original main channel to the slave channel, without increasing or decreasing the user infofield in the user info list field in the MU-RTS trigger frame (trigger frame). The channel granularity of the main channel in the RU Allocation field is mapped to the channel granularity of the slave channel used to receive CTS. After mapping, the terminal can be directly instructed to transmit CTS on the slave channel with the specified channel number.

[0068] In another example, Figure 3 As shown, determining a secondary channel for receiving a CTS sent by a terminal based on an indication mode of an RU Allocation field in a user info field in a user infolist field in an improved MU-RTS trigger frame may specifically include the following steps:

[0069] Step 201: multiple new channel numbers are added to the RU Allocation field, where the channel numbers correspond to multiple groups of non-completely identical channel granularities within the channel bandwidth, and the channel granularities corresponding to the multiple new channel numbers include the channel granularity of the slave channel;

[0070] Specifically, Figure 4 As shown in the figure, the channel number is B7-B1 in the RU Allocation field. Temp represents the name of the secondary channel at different granularities, and temp can be replaced by secondary. For example, 70 (temp 20MHz is the 4th lowest 20MHz) can be replaced by 70 (secondary 20MHz is the 4th lowest 20MHz), where the channel number 70 is the decimal value of the RA Allocation field.

[0071] Step 202: Based on the joint indication of PS160 and RU Allocation field in the user info field, or the indication of UL BW subfield in the Common Info field in MU-RTS, determine the secondary channel for receiving CTS from the channel granularity of the secondary channel newly added in the RU Allocation field.

[0072] Specifically, after adding multiple new channel numbers in the RU Allocation field, that is, after the channel granularity of the slave channel is newly added in the RU Allocation field, the slave channel for receiving CTS can be determined from the channel granularity of the slave channel newly added in the RU Allocation field based on the joint indication of PS160 in the user info field and the RUAllocation field; or based on the indication of the UL BW subfield in the Common Info field in MU-RTS, the slave channel for receiving CTS can be determined from the channel granularity of the slave channel newly added in the RU Allocation field. After determining the slave channel for receiving CTS based on any of the above indication methods, the terminal is further instructed to transmit CTS on the slave channel with the specified channel number. It should be noted that the indication priority of the UL BW subfield is higher than the priority of the joint indication of PS160 and RU Allocationfield. When there is an indication in the UL BW subfield, CTS is transmitted in accordance with the indication of the UL BW subfield; when there is no indication in the UL BW subfield, CTS is transmitted in accordance with the joint indication of PS160 and RU Allocation field; when the indication of the UL BW subfield and the joint indication of PS160 and RU Allocation field appear at the same time, regardless of whether the two are the same or not, CTS is transmitted in accordance with the indication of the UL BW subfield.

[0073] In an example, a specific implementation method of adding multiple new channel numbers in the RU Allocation field may be:

[0074] When the total channel bandwidth is 320 MHz, the channel number is increased to 91 based on the existing channel numbers 61 to 69, and at least part of the channel access granularities corresponding to the increased channel numbers belong to the channel access granularity of the slave channel;

[0075] The corresponding relationship between the channel numbers corresponding to the channel access granularities belonging to the slave channel satisfies:

[0076] The larger the channel access granularity, the larger the corresponding channel number; and / or, the channel numbers corresponding to two channel access granularities with adjacent bandwidths are adjacent; and / or, according to the channel access granularity from small to large, each uncoded channel access granularity is traversed from low to high channel bandwidth, and the current uncoded channel access granularity and its respective advanced channel access granularities are channel-coded in sequence from small to large granularity.

[0077] Specifically, the channel coding method can be as follows: Figure 4 As shown in the figure, when the channel bandwidth is 320MHz, 61-64 and 70-81 are the channel numbers when the channel access granularity is 20MHz; 65-66 and 82-87 are the channel numbers when the channel access granularity is 40MHz; 67 and 88-90 are the channel numbers when the channel access granularity is 80MHz; 68 and 91 are the channel numbers when the channel access granularity is 160MHz. Figure 4 In the coding mode shown, CTS is transmitted according to the channel number of the slave channel. If the slave channel of CTS transmission is indicated based on the joint indication of PS160 and RU Allocation field in the user info field, the specific situation of determining the slave channel of CTS transmission is as follows. For example, when B7–B1 in the RUAllocation subfield in the user info field indicates 70, and B0=1 and PS160 in the user info field=0, the joint indication of PS160 and RU Allocation field indicates that CTS is transmitted on the fifth lowest 20 MHz bandwidth in the 320 MHz channel; when B7–B1 in the RU Allocation subfield in the user info field indicates 84, and B0=1 and PS160 in the user info field=1, the joint indication of PS160 and RU Allocation field indicates that CTS is transmitted on the fifth lowest 40 MHz bandwidth in the 320 MHz channel; when B7–B1 in the RU Allocation subfield indicates 89, and B0=1 and PS160 in the user info field=1, the joint indication of PS160 and RU Allocation field indicates that CTS is transmitted on the third lowest 80 MHz bandwidth in the 320 MHz channel.

[0078] by Figure 4 For example, if B7-B1 in the RU Allocation subfield in the user info field is set (indicated) to 88, and B0=1, and PS160 in the user info field is 0, the UL BW subfield also indicates that CTS is transmitted on the second lowest 80MHz bandwidth in the 160MHz channel. At this time, the channel bandwidth is 160MHz, and it is determined that CTS is transmitted on the second lowest 80MHz slave channel.

[0079] If B7–B1 in the RU Allocation subfield is set to 88 and B0=1, and the UL BW subfield also indicates that CTS is transmitted on the second lowest 80MHz bandwidth in the 160MHz channel, and PS160 is not received or set, the channel bandwidth is 160MHz in accordance with the instructions of the UL BW subfield, and CTS is transmitted on its second lowest 80MHz subordinate channel.

[0080] In some cases, when the channel bandwidth is 40MHz, the primary channel is the channel with the lowest 20MHz bandwidth, and 61primary20MHz is the lowest 20MHz. At this time, when accessing the slave channel, if the primary channel is busy, when accessing the slave channel (the second lowest 20MHz), when RUAllocation subfied is set to B0=0 in the transmitted MU-RTS trigger frame, and B7~B1=62, it means that the current CTS transmission channel is channel numbered 62. At this time, the RU Allocation setting does not indicate that the primary channel is 62. At this time, "62" represents the channel number, not the primary channel. In some cases, the CTS in response to the MU-RTS Trigger frame is transmitted in the resource unit indicated by the User Info field.

[0081] The channel coding method can also be Figure 5 As shown in FIG. 1 , when the channel bandwidth is 320MHz, 61-64, 70-73, 77-80, 84-87 are the channel numbers when the channel access granularity is 20MHz; 65-66, 74-75, 81-82 and 88-89 are the channel numbers when the channel access granularity is 40MHz; 67, 76, 83, 90 are the channel numbers when the channel access granularity is 80MHz; 68 and 91 are the channel numbers when the channel access granularity is 160MHz. In the coding method such as Figure 5 When shown, the process of transmitting CTS according to the channel number is the same as above Figure 4 The encoding method is similar and will not be described in detail in this application.

[0082] The channel coding method can also be Figure 6 As shown in the figure, when the channel bandwidth is 320MHz, 80 to 91 are the channel numbers when the channel access granularity is 20MHz; 65 to 66, 74 to 79 are the channel numbers when the channel access granularity is 40MHz; 67, 71 to 73 are the channel numbers when the channel access granularity is 80MHz; 68 and 70 are the channel numbers when the channel access granularity is 160MHz. Figure 6When shown, the process of transmitting CTS according to the channel number is the same as above Figure 4 Similarly, this application will not go into details.

[0083] In another example, the step of determining a slave channel for receiving a CTS sent by a terminal according to a specific rule may include:

[0084] A channel for transmitting CTS is determined from idle slave channels by selecting a slave channel for transmitting CTS determined in advance through negotiation with the terminal. The selection rule includes:

[0085] Transmit on all idle 20MHz channels of the slave channel; or, transmit on all 20MHz channels in the idle access granularity of the slave channel; or, transmit on the lowest 20MHz channel in the idle access granularity of the slave channel; or, transmit on the highest 20MHz channel in the idle access granularity of the slave channel; or, transmit on the lowest channel in the idle access granularity of the slave channel; or, transmit on the highest channel in the idle access granularity of the slave channel; or, transmit on a designated special idle channel of the slave channel. This application does not limit the specific selection rules.

[0086] In another example, receiving a CTS from a terminal based on a slave channel indicated by the MU-RTS in step 104 may specifically include:

[0087] Based on the slave channel selected by the terminal from the slave channel indicated by MU-RTS and detected as idle on the terminal side, the slave terminal receives CTS; wherein the terminal transmits CTS using the slave channel selected by the terminal from the slave channel indicated by MU-RTS and detected as idle on the terminal side.

[0088] In some cases, in order to save signaling and reduce overhead, Figure 4 , Figure 5 , Figure 6 The numbering does not need to reach 91. Only some channels in the bandwidth are numbered, and the indication of all channels in the bandwidth is completed by joint indication. For example, Figure 4 In the example, you can only number up to 76, and use PS160 to map channels numbered 61 to 76 to channels numbered 77 to 91. After mapping, when PS160 is 1, the value of the RU Allocation field is 61, which can correspond to channel numbered 77.

[0089] Specifically, in one example, Figure 7As shown in the figure, the AP and non-AP STA1 (terminal 1) and non-AP STA2 (terminal 2) all work on a bandwidth of 160MHz and have the ability to access the secondary channel. The negotiated channel access granularity is 40MHz and they access the secondary channel. Figure 4 In this case, the third lowest 40MHz channel perception result is that the channel is idle, and the AP sends a MU-RTStrigger frame to non-AP STA1 and non-AP STA2 on this channel. Among them, the user info field of non-AP STA1 in the user info list in the MU-RTS trigger frame corresponds to the RA Allocation field of non-AP STA1, which is B0=1, B7-B1=70. Similarly, the RA Allocation field corresponding to the user info field of non-AP STA2 in the user info list in the MU-RTS trigger frame is B0=1, B7-B1=82. In this process, non-AP STA1 can only receive the MU-RTS trigger frame correctly on all 20MHz bandwidths in the 40MHz access granularity. Figure 4 The non-AP STA2 sends a CTS on the 20 MHz channel (70) shown in FIG. 1 ; only when the non-AP STA2 correctly receives the MU-RTS trigger frame on all 20 MHz bandwidths in the 40 MHz access granularity can it Figure 4 The CTS is sent on the 40 MHz channel (82) shown.

[0090] If the RA Allocation field in the MU-RTS trigger frame does not indicate the transmission mode of CTS, or the MU-RTS trigger frame is not transmitted, CTS can be transmitted on all idle 20MHz channels of the slave channel; or, CTS is transmitted on all 20MHz channels in the idle access granularity of the slave channel; or, CTS is transmitted on the lowest 20MHz channel in the idle access granularity of the slave channel; or, CTS is transmitted on the highest 20MHz channel in the idle access granularity of the slave channel; or, CTS is transmitted on the lowest channel in the idle access granularity of the slave channel; or, CTS is transmitted on the highest channel in the idle access granularity of the slave channel; or, CTS is transmitted on the idle designated special channel of the slave channel. Compared with the related art, the above-mentioned implementation method of the present application negotiates the slave channel access granularity when the terminal and the access point perform slave channel access. The MU-RTS trigger frame needs to be transmitted on the entire bandwidth occupied by each channel access granularity that is detected by channel (channel detection, CCA (clear channel assessment) shows that the channel is idle). And by reusing or improving the indication method of the RU Allocation field in the user info field in the user info list field in the MU-RTS trigger frame, the response CTS of the MU-RTS trigger frame only needs to be transmitted on a specific slave channel and a specific bandwidth. In the above manner, the terminal (receiver) does not have to transmit CTS on all available bandwidths, saving energy and reducing the burden on the terminal (receiver).

[0091] In some cases, the CTS frame in response to the MU-RTS is transmitted in the RU (resource unit) indicated by the UHR variant User Info field according to the above method, except for all punctured 20MHz channels indicated by a certain bitmap (punctured 20MHz channels refer to invalid channels). The UHR variant User Info field refers to the User Info field corresponding to future Wi-Fi standard versions after Wi-Fi 7.

[0092] Yet another embodiment of the present application relates to a slave channel access method. The slave channel access method in this embodiment is a supplement to the slave channel access method in the previous embodiment. The specific supplementary contents are as follows.

[0093] In a specific application, after the slave channel is accessed, the settings for slave channel access may need to be reconfigured or reconfigured due to changes in external reasons. The external reasons may be: changes in channel puncture leading to changes in unavailable channels, or changes in interference conditions, or changes in user working modes, or changes in the MSC range available to users, etc. This application does not limit the specific external reasons that may lead to the need to configure or reconfigure the settings for slave channel access.

[0094] The configuration items for reconfiguring the slave channel that has been accessed between the terminal include at least: slave channel access bandwidth, available channel bitmap, slave channel access granularity, slave channel perception granularity, slave channel access modulation mode, slave channel contention window size, access type parameter, and at least one of QoS parameters.

[0095] Among them, in the available channel bitmap, bitmap refers to the setting of 0 or 1 through the smallest unit bit, indicating the value or state corresponding to a certain element. If the value or state corresponding to a certain element changes, it may be necessary to reconfigure the available channel bitmap. When high-priority services need to be transmitted, due to terminal complexity, battery energy and other reasons, it may be necessary to adjust the slave channel access granularity. When accessing from the channel, the backoff window size / contention window size needs to be adjusted, that is, the binary backoff channel perception indicates that the slave channel is idle. When accessing from the channel, it is not accessed immediately, but it is necessary to wait for a period of time (listen time / listen period) before accessing the channel; or, after waiting for a period of time, if the CCA shows that the channel is idle, access the channel immediately. This waiting time (listen time / listen period) can be called the slave channel backoff window or the slave channel contention window.

[0096] After the AP and the access point have negotiated and reached a consensus (agreement), and work in the channel access mode, the agreement needs to be adjusted due to some external reasons. At this time, the terminal proposes to reconfigure at least one of the channel access bandwidth, available channel bitmap, channel access granularity, channel perception granularity, channel access modulation mode, channel contention window size, access type parameter, and QoS parameter through the (reconfigure) request frame.

[0097] In one example, the specific steps of reconfiguring the slave channel that has been connected to the terminal may be:

[0098] The secondary channel that has been accessed with the terminal is reconfigured by sending and receiving a secondary channel reconfiguration negotiation frame with the terminal, or by directly sending a reconfiguration instruction frame (reconfigure) response frame / reconfiguration frame of secondary channel access to the terminal.

[0099] The slave channel reconfiguration negotiation frame may include: a slave channel reconfiguration request frame (reconfigure) and a slave channel reconfiguration response frame (reconfigure) .

[0100] Specifically, when the accessed slave channel is reconfigured by sending and receiving slave channel reconfiguration negotiation frames between the AP and the terminal, the specific process may be: the terminal first sends a slave channel reconfiguration negotiation frame (reconfigure) request frame to the AP; after receiving the channel reconfiguration negotiation frame (reconfigure) request frame, the AP replies with a slave channel reconfiguration response frame (reconfigure) response frame to the terminal, and the AP and the terminal reach an agreement on the modified object or value, and then the terminal and the access point use the new reconfigured parameters to access or transmit the slave channel.

[0101] When the AP reconfigures the accessed secondary channel by directly sending a reconfiguration command frame of secondary channel access to the terminal, the specific process may be: the AP directly sends a reconfiguration command frame of secondary channel access to the terminal, and the reconfiguration command frame includes the object to be reconfigured and its recommended value. If the terminal receives the reconfiguration command frame of secondary channel access and confirms the modification, an ACK frame is returned, otherwise the ACK frame is not sent. After receiving the ACK frame, the AP accesses or transmits the secondary channel according to the reconfigured parameters.

[0102] In one example, after accessing the slave channel according to any of the above-mentioned slave channel access methods, after the preset slave channel access termination condition is met, the slave channel access that has been started between the terminal is terminated, and the termination condition includes at least one of the following situations: the slave channel access time has arrived; and the operation of terminating the slave channel access is actively initiated.

[0103] Specifically, the AP and the terminal negotiate and determine to end the transmission from the channel after a certain timer is zero. In practical applications, the timer can be started by a slave channel access negotiation frame, that is, the timer can be started by a slave channel access request frame or a slave channel access response frame. Alternatively, the timer is automatically started after a consensus agreement is reached on the slave channel access. In some cases, the timer can be set with an initial value, and the countdown starts after it is started. The initial value set for the timer can be included in the agreement reached on the slave channel access, or in the slave channel negotiation request frame request frame, or in the slave channel negotiation response frame response frame. In the case where reconfiguration is required after the slave channel access, the timer can also be started by a slave channel access reconfiguration frame. The timer can reset the timing value by the slave channel access reconfiguration frame, or pause or delay the timer end time when there is suddenly more data to be transmitted. In some cases, after the timer is zero, if the terminal is transmitting data in the current TXOP, the terminal immediately ends the slave channel transmission (mode) after completing the current TXOP data transmission, or ends the slave channel access mode after a period of time after the terminal completes the current TXOP data transmission. Among them, TXOP (Transmission opportunity) is a transmission time for a transmitting device to access a channel after completing a set of CCA. This application does not impose specific restrictions on the relevant settings of the timer. As long as the operation of ending the access to the channel by setting the access time falls within the protection scope of this application.

[0104] Specifically, the secondary channel access can also be terminated by actively initiating an operation to terminate the secondary channel access. Specifically, the system management entity (SME) of the terminal issues a request primitive and transmits a secondary channel access request frame. The action type field in the secondary channel access element is set to "Exit secondary channel access mode" or "end secondary channel access mode". This process can be expressed as "To exit secondary channel access mode, the non-AP STA's SME shall issue an MLME-Secondary MODE request primitive to send a secondary channel access ModeRequest frame with an Action Type field in the secondary channel accesselement set to "Exit secondary channel access mode". " In some cases, the name of the secondary channel access request frame can be a secondary channel access negotiation frame, or a secondary channel access reconfiguration frame, or a secondary channel access response frame, or a secondary channel access mode request frame, or a secondary channel access mode response frame.

[0105] Another embodiment of the present invention relates to an electronic device, such as Figure 8 As shown, it includes at least one processor 302; and a memory 301 that is communicatively connected to the at least one processor 302; wherein the memory 301 stores instructions that can be executed by the at least one processor 302, and the instructions are executed by the at least one processor 302 so that the at least one processor 302 can execute any of the above-mentioned embodiments of the channel access method.

[0106] The memory 301 and the processor 302 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 302 and the memory 301 together. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore 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 302 is transmitted on a wireless medium via an antenna, and further, the antenna also receives data and transmits the data to the processor 302.

[0107] The processor 302 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 301 can be used to store data used by the processor 302 when performing operations.

[0108] Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements any of the above-mentioned embodiments of the slave channel access method when executed by a processor.

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

[0110] 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 slave channel access method, characterized in that: include: After determining that the terminal has the secondary channel access capability, performing secondary channel access negotiation with the terminal and reaching a consensus with the terminal on the secondary channel access method; When the main channel is unavailable or busy, determine whether there is an idle slave channel among the slave channels that have reached a consensus on the slave channel access mode with the terminal; Send MU-RTS to the terminal on a determined idle slave channel; Receiving a CTS sent by a terminal on a slave channel indicated by the MU-RTS or on a slave channel determined according to a specific rule; The indication method of the slave channel receiving CTS from the slave terminal based on the MU-RTS indication includes: an indication method based on an improved RUAllocation field; Determining a secondary channel for receiving a CTS sent by a terminal based on an indication of an RU Allocation field in a user infofield in a user info list field in an improved MU-RTS trigger frame includes: Adding multiple new channel numbers in the RU Allocation field, the channel numbers corresponding to multiple groups of non-completely identical channel granularities within the channel bandwidth, the channel granularities corresponding to the multiple new channel numbers including the channel granularity of the slave channel; Based on the joint indication of PS160 and RU Allocation field in the user info field, or the indication of UL BW subfield in Common Info field in MU-RTS, determine the slave channel for receiving CTS from the channel granularity of the slave channel newly added in the RU Allocation field; Add multiple new channel numbers in the RU Allocation field, including: When the total channel bandwidth is 320 MHz, the channel number is increased to 91 based on the existing channel numbers 61 to 69, and at least part of the channel granularities corresponding to the increased channel numbers belong to the channel granularities of the slave channels; wherein the corresponding relationship of the channel numbers corresponding to the channel granularities belonging to the slave channels satisfies: The larger the channel granularity, the larger the corresponding channel number; and / or, The channel numbers corresponding to two channel granularities with adjacent bandwidths are adjacent; and / or, Each uncoded channel granularity is traversed from small to large channel granularity and from low to high channel bandwidth, and channel coding is performed on the current uncoded channel granularity and its respective advanced channel granularities in sequence from small to large granularity.

2. The method according to claim 1, characterized in that The performing the secondary channel access negotiation with the terminal and reaching a consensus with the terminal on the secondary channel access mode includes: By sending and receiving slave channel access negotiation frames with the terminal, the consensus content of the slave channel access method is determined.

3. The method according to claim 2, characterized in that The determining that the terminal has a slave channel access capability includes: Based on the information element field of the terminal, or the secondary channel access function identifier recorded by the receiving vector or the sending vector, determine whether the terminal has the secondary channel access function; based on the information element field of the terminal, or based on the receiving vector or the sending vector of the terminal, or the secondary channel access granularity identifier recorded by the channel access negotiation frame, determine that the terminal has the channel granularity for secondary channel access.

4. The method according to claim 2, characterized in that: The slave channel access negotiation frame includes: a slave channel access request frame initiated by the negotiation initiator, and a slave channel access response frame fed back by the negotiation responder; The consensus content of the slave channel access method is carried in at least one of the slave channel access request frame and the slave channel access response frame.

5. The method according to any one of claims 2 to 4, characterized in that: The consensus content includes at least one of the following: channel access bandwidth, available channel bitmap, channel access granularity, channel perception granularity, channel access modulation mode, channel contention window size, access type parameters, and QoS parameters.

6. The method according to any one of claims 2 to 4, characterized in that: The determining whether there is an idle slave channel among the slave channels for which a slave channel access mode consensus has been reached with the terminal includes: Through binary backoff, channel detection is performed on the slave channel for which a slave channel access mode consensus has been reached with the terminal according to a preset perception granularity to obtain channel energy, and when it is detected that the channel energy is lower than a preset threshold value, it is determined that the slave channel corresponding to the perception granularity is idle, or; When it is detected that the channel energy is lower than a preset threshold value and it is detected that the network allocation vector indicates that the slave channel is idle, it is determined that the slave channel corresponding to the sensing granularity is idle; The perception granularity is less than or equal to the access granularity of the slave channel in the consensus reached on the slave channel access method.

7. The method according to claim 6, characterized in that The access granularity of the slave channel includes at least one complete perception granularity, or includes a partial channel in at least one perception granularity.

8. The method according to claim 6, characterized in that The access granularity of the slave channel corresponds to a continuous or discontinuous channel, and / or the access granularity of the slave channel has a binding or non-binding relationship with the channel.

9. The method according to claim 1, characterized in that: The sending the MU-RTS to the terminal on the determined idle slave channel includes: The MU-RTS is sent to the terminal on all the idle slave channels determined.

10. The method according to claim 1, characterized in that The indication method of the slave channel receiving CTS from the slave terminal based on the MU-RTS indication also includes: an indication method based on the RU Allocation field in the user info field in the user info listfield in the reused MU-RTS trigger frame.

11. The method according to claim 10, characterized in that Determining a secondary channel for receiving a CTS sent by a terminal based on an indication of an RU Allocation field in a user info field in a user info list field in a reused MU-RTS trigger frame includes: Based on the joint indication of PS160 and RU Allocation field in the user info field, or the indication of UL BW subfield in Common Info field in MU-RTS, the channel granularity of the primary channel in the RU Allocation field is mapped to the channel granularity of the secondary channel used to receive CTS.

12. The method according to claim 1, characterized in that Determining the slave channel for receiving the CTS sent by the terminal according to the specific rule includes: A channel for transmitting CTS is determined from the idle slave channels by selecting a slave channel for transmitting CTS determined in advance through negotiation with the terminal, and the selection rule includes: Transmit on all idle 20MHz channels of the slave channel; Transmit on all 20 MHz channels in the access granularity from the idle channels; Transmit on the lowest 20 MHz channel in the access granularity of the idle channel; Transmit on a channel with a maximum access granularity of 20 MHz from the idle channels; Transmitting on the lowest channel in the access granularity from the idle channels; Transmitting on the highest channel in the access granularity from the idle ones of the channels; Transmit on a designated special channel that is idle from the channel.

13. The method according to claim 1, characterized in that The configuration items for reconfiguring the slave channel that has been accessed between the terminal include at least: slave channel access bandwidth, available channel bitmap, slave channel access granularity, slave channel perception granularity, slave channel access modulation mode, slave channel contention window size, access type parameter, and at least one of QoS parameters.

14. The method according to claim 13, characterized in that The reconfiguring of the slave channel connected to the terminal includes: The slave channel connected to the terminal is reconfigured by sending and receiving a slave channel reconfiguration negotiation frame to the terminal, or by directly sending a reconfiguration instruction frame to the terminal.

15. The method according to claim 1, characterized in that Also includes: After a preset slave channel access termination condition is met, the slave channel access started with the terminal is terminated, where the termination condition includes at least one of the following situations: The slave channel access time has arrived; Actively initiate the operation of ending slave channel access.

16. An electronic device, 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 slave channel access method according to any one of claims 1 to 15.

17. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the slave channel access method according to any one of claims 1 to 15 is implemented.

Images