Channel access method, terminal, and storage medium

Abstract

The embodiment of the present application relates to the field of wireless communication technology, and discloses a kind of slave channel access method, terminal and storage medium.This application, by being associated with the access point device negotiation slave channel access strategy, and jointly switch to slave channel access mode;Switch to slave channel access mode terminal device or access point device can execute slave channel access, and according to the related parameter when slave channel access strategy configuration is carried out data transmission on slave channel;After slave channel access is executed according to slave channel access strategy, when satisfying the preset reconfiguration condition, slave channel access strategy is updated by the way of re-negotiation with access point device, to adjust the related parameter when data transmission is carried out on slave channel according to slave channel access strategy.Make terminal device can execute slave channel access, save wireless resource at the same time, improve the stability of data transmission by the way of reconfiguration of slave channel access.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of wireless communication technology, in particular to a channel access method, a terminal and a storage medium. BACKGROUND

[0002] In a Wi-Fi system, a primary channel and a secondary channel are defined, which is originally used to increase the bandwidth in 802.11n by channel bonding. For example, a 40MHz channel sends beacon and management frames on a 20MHz primary channel, and sends data on another 20MHz secondary channel. In this way, the overall bandwidth of the device reaches 40MHz. Compared with the original device, the working bandwidth is increased, and the throughput is improved. At the same time, Wi-Fi maintains compatibility with devices that only support 20MHz. The traditional device that only supports 20MHz can still work normally by accessing the 20MHz primary channel.

[0003] In the standard, for a terminal working in 40MHz, the primary channel is 20MHz, and the secondary channel is also 20MHz. When accessing the channel, the terminal or the corresponding AP performs channel detection, and if the primary channel and the secondary channel are both idle, the terminal accesses the channel (sends data or management frames or action frames on the primary and secondary channels); if the primary channel is idle and the secondary channel is busy, the terminal only accesses the primary channel; if the primary channel is busy and the secondary channel is busy, the terminal does not access the channel; if the primary channel is busy and the secondary channel is idle, the terminal cannot access the channel. The purpose of the above access method is to give priority to the primary channel to ensure the forward compatibility of the device on the primary channel.

[0004] The inventor finds that at least the following problems exist in the related art: With the development of wireless technology, Wi-Fi supports larger and larger working bandwidths, such as 80MHz, 160MHz, and even 320MHz. However, the above-mentioned access method of the primary channel and the secondary channel has not changed and is still used today. This results in that when the primary channel is busy and the secondary channel is idle, the channel cannot be accessed, and more precisely, the secondary channel cannot be accessed. The bandwidth of the secondary channel increases with the overall channel bandwidth. The above-mentioned situation that the secondary channel cannot be utilized seriously wastes wireless resources. Therefore, in the recent discussion of the Wi-Fi 8 standard, there are schemes for how to fully utilize the secondary channel. The schemes mentioned are mostly to enable the terminal to access the secondary channel when the primary channel is busy and the secondary channel is idle. Or the definition of the granularity of the secondary channel. The granularity refers to the bandwidth or subchannel of the secondary channel, which is composed of one or several 20MHz channels. However, there is no description of utilizing the secondary channel and no discussion of reconfiguring the access to the secondary channel. SUMMARY

[0005] The purpose of this invention is to provide a channel access method, terminal, and storage medium, enabling terminal devices to perform channel access, saving wireless resources, and improving data transmission stability through channel access reconfiguration.

[0006] To address the aforementioned technical problems, embodiments of the present invention provide a method for accessing a secondary channel, comprising: negotiating a secondary channel access strategy with an associated access point device and jointly switching to a secondary channel access mode; wherein, the terminal device or access point device switching to the secondary channel access mode will be able to perform secondary channel access when the primary channel is busy and the secondary channel is idle, and configure relevant parameters for data transmission on the secondary channel according to the secondary channel access strategy; after performing secondary channel access according to the secondary channel access strategy, when a preset reconfiguration condition is met, updating the secondary channel access strategy by renegotiation with the access point device, so as to adjust the relevant parameters for data transmission on the secondary channel according to the secondary channel access strategy.

[0007] Embodiments of the present invention also provide a terminal, 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, the instructions being executed by the at least one processor to enable the at least one processor to perform the above-described channel access method.

[0008] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the above-described channel access method.

[0009] In this embodiment of the invention, a secondary channel access policy is negotiated with the associated access point device, and the devices jointly switch to the secondary channel access mode. The terminal device or access point device switched to the secondary channel access mode can perform secondary channel access when the primary channel is busy and the secondary channel is idle, and configures relevant parameters for data transmission on the secondary channel according to the secondary channel access policy. After performing secondary channel access according to the secondary channel access policy, when preset reconfiguration conditions are met, the secondary channel access policy is updated by renegotiating with the access point device to adjust the relevant parameters for data transmission on the secondary channel according to the secondary channel access policy. This enables the terminal device to perform secondary channel access, effectively utilizing secondary channel resources and saving wireless resources, while improving data transmission stability through the reconfiguration of secondary channel access.

[0010] Furthermore, the secondary channel access strategy is negotiated with the associated access point device, including: sending an inquiry frame to the associated access point device to indicate support for switching to secondary channel access mode; the inquiry frame carries capability information indicating the device's capabilities, the number of secondary channels it can support, and the granularity of the secondary channels it can support; receiving a suggestion frame from the access point device based on the inquiry frame, the suggestion frame carrying temporary primary channel location information and secondary channel granularity information supported by the access point device; selecting the number and granularity of secondary channels to use for this access based on the suggestion frame to generate the secondary channel access strategy; and sending the secondary channel access strategy to the access point device via a response frame. This facilitates load balancing across frequency bands within the AP's bandwidth, allocating terminals to different secondary channels or different secondary channel granularities. Triggering secondary channel access reconfiguration on the service flow helps to specifically guarantee the QoS (Quality of Service) of the service flow. Especially for ultra-high reliability requirements, secondary channel access reconfiguration for service QoS is particularly important. Meanwhile, during the handover, the channel access mode can be maintained from the original access point to the target access point, which helps to maintain the continuity of terminal services. Attached Figure Description

[0011] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0012] Figure 1 This is a flowchart of a channel access method according to an embodiment of the present invention;

[0013] Figure 2 This is a schematic diagram of channel access policy negotiation interaction provided according to an embodiment of the present invention;

[0014] Figure 3 This is a schematic diagram of the terminal structure according to another embodiment of the present invention. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details are presented in the various embodiments of the present invention to facilitate a better understanding of this application. However, the technical solutions claimed in this application can be implemented even without these technical details and various changes and modifications based on the following embodiments. The division of the various embodiments below is for ease of description and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined with and referenced by each other without contradiction.

[0016] One embodiment of the present invention relates to a secondary channel access method, which can be applied to any terminal device capable of wirelessly connecting to an access point device, such as a mobile phone or computer. In this embodiment, a secondary channel access strategy is negotiated with the associated access point device, and both devices switch to the secondary channel access mode. The terminal device or access point device switched to the secondary channel access mode can perform secondary channel access when the primary channel is busy and the secondary channel is idle, and configures relevant parameters for data transmission on the secondary channel according to the secondary channel access strategy. After performing secondary channel access according to the secondary channel access strategy, when a preset reconfiguration condition is met, the secondary channel access strategy is updated by renegotiating with the access point device to adjust the relevant parameters for data transmission on the secondary channel according to the secondary channel access strategy. This enables the terminal device to perform secondary channel access, effectively utilizing secondary channel resources and saving wireless resources, while improving data transmission stability through secondary channel access reconfiguration. The implementation details of the secondary channel access method of this embodiment are described below. The following content is only for ease of understanding and is not essential for implementing this solution.

[0017] The terminal device and its associated AP operate only on the secondary channel, or when the primary channel is busy and the secondary channel is idle, data is transmitted only on the secondary channel, effectively improving Wi-Fi spectrum utilization. In general, to achieve this effect, the AP and terminal need to negotiate parameters such as the secondary channel operating mode, strategy, temporary primary channel location, temporary primary channel bandwidth, and secondary channel access granularity. Then, the AP and terminal begin co-operating in the secondary channel access mode based on the negotiation results. When the primary channel is busy and the secondary channel is idle, the AP or terminal can access and send / receive data on the current secondary channel. When both the AP and terminal enter the secondary channel access mode and begin operating, secondary channel access reconfiguration occurs, such as changes in secondary channel access granularity. After reconfiguration, both the AP and terminal begin operating in the secondary channel access mode according to the new configuration. Finally, the terminal or AP exits the secondary channel access mode. The terminal can restart the secondary channel access mode with other APs after exiting it.

[0018] In some cases, access is granted based on the negotiation result after channel access negotiation. In other cases, access begins at a predetermined time. In some cases, access is triggered by a trigger frame. In some cases, the trigger frame indicates that the channel access mode begins upon receipt of the frame. In some cases, the trigger frame indicates that the channel access mode has begun and data will be transmitted on the channel immediately following the trigger frame. In some cases, the trigger frame is transmitted at a specific granularity on the channel or on a channel group consisting of several 20MHz sub-channels. In some cases, the trigger frame is transmitted on at least one temporary master channel on the channel.

[0019] After providing a general example of the solution proposed in this application, the specific implementation details of this application will be explained below through various examples. The channel access method flow of this embodiment is as follows: Figure 1 As shown, in step 101, the terminal device (STA) negotiates with the associated access point device to obtain a secondary channel access policy and jointly switches the channel access mode to the secondary channel access mode. The terminal device or access point device that switches the channel access mode to the secondary channel access mode will be able to perform secondary channel access when the main channel is busy and the secondary channel is idle, and configure the relevant parameters for data transmission on the secondary channel according to the secondary channel access policy.

[0020] In one example, such as Figure 2As shown, the secondary channel access strategy is obtained through negotiation with the connected access point device. This can be achieved as follows: The terminal device sends an inquiry frame (or secondary channel access inquiry frame) to the access point device to indicate its support for switching to secondary channel access mode. The inquiry frame carries capability information indicating its own capabilities, information indicating the number of secondary channels it can support, and information indicating the granularity of the secondary channels it can support. The terminal device receives a suggestion frame (or secondary channel access suggestion frame) from the access point device based on the inquiry frame. The suggestion frame carries information about the temporary primary channel location supported by the access point device and the granularity of the secondary channels supported by the access point device. Based on the suggestion frame, the terminal device selects the number of secondary channels and the granularity of the secondary channels to be used for this access, thereby generating a secondary channel access strategy. Finally, the terminal device sends the secondary channel access strategy to the access point device via a response frame (or secondary channel access response frame).

[0021] The granularity of a slave channel can be 20MHz, 40MHz, 80MHz, or 160MHz. Slave channel access granularity refers to further subdividing a connected slave channel into smaller subbands or subchannels for access. In some embodiments, information such as the number and granularity of supported slave channels is included in beacons, probe request responses, and association responses. Alternatively, it may be included in the information control frame (ICF) for slave channel access, or in the aforementioned query frames, suggestion frames, or response frames.

[0022] In some cases, after receiving an inquiry frame from a terminal, the AP, based on its capabilities and the number and bandwidth of supported slave channels, sends a configuration suggestion frame to the terminal. The terminal sends a response frame simply to acknowledge this. In other cases, the terminal does not send a response frame.

[0023] In some cases, the terminal does not send an inquiry frame. After the access point (AP) learns that the terminal supports access from the channel, it directly sends a suggestion frame. Upon receiving this suggestion frame, the terminal sends a response frame.

[0024] In some cases, the terminal and the access point (AP) only send a channel access suggestion frame. In other cases, this frame may be called a channel access control frame, or simply a control frame.

[0025] In some cases, the terminal and the access point (AP) only exchange either an ICF (Initial Control Frame) or an initial control response (ICR) information frame (as an initial acknowledgment frame). The ICF carries information about accessing the secondary channel, such as granularity, secondary channel bandwidth, and the temporary primary channel position within the secondary channel. The AP sends the ICF to the terminal, and upon receiving the ICF, the terminal responds by sending an ICR to the AP to negotiate, informing the AP whether it agrees to access the secondary channel. In some cases, there is no subsequent ICF or ICR; the AP notifies the terminal to enter secondary channel access mode by sending an ICF to the terminal. In some situations, the ICF is a trigger frame.

[0026] In some cases, the interrogation frame is not present, and only the ICF (as the initial control frame) is used to complete the channel access configuration, reconfiguration, enabling the channel access function, or disabling the channel access function; or the interrogation frame itself is an ICF frame.

[0027] In step 102, after the terminal device performs secondary channel access according to the secondary channel access policy, when the preset reconfiguration conditions are met, it updates the secondary channel access policy by renegotiation with the access point device, so as to adjust the relevant parameters for data transmission on the secondary channel according to the secondary channel access policy.

[0028] The access parameters and modes determined through access negotiation are not static. Reconfiguration can be performed under various conditions. In one example, preset reconfiguration conditions include: the access point device entering power-saving mode, and changes in the number of temporary primary channels, the location of temporary primary channels, the granularity of secondary channels, or the operating bandwidth in the terminal devices; and / or, the number of terminal devices operating on the same bandwidth reaches a first preset value; and / or, the secondary channel granularity is canceled because the number of accessing terminal devices is less than the minimum limit; and / or, the number or type of pending services on the terminal devices meets preset service-triggered reconfiguration requirements; and / or, the terminal device's operating state, operating mode, capability mode, spatial flow, or service flow changes.

[0029] The preset reconfiguration conditions are closely related to the reconfiguration scenarios, and examples will be given below:

[0030] In some cases, parameters such as the number of temporary primary channels, the location of temporary primary channels, and the granularity of secondary channel access between the terminal and the AP may change. For example, when the AP is in power-saving mode, its operating bandwidth narrows. It is necessary to reconfigure the secondary channel access parameters. The reconfiguration process may, for example, involve the AP sending a beacon to indicate a change in its supported operating bandwidth, or the AP initiating a channel switching mechanism to indicate a change in its operating bandwidth. Alternatively, a dedicated power-saving frame may be created. In some cases, the parameters for the AP and terminal operating on the secondary channel are sent along with the command indicating a change in the AP's power-saving operating bandwidth. This includes secondary channel parameters such as the location, width, number of temporary primary channels, and granularity of secondary channel access. In some cases, secondary channel parameters such as the location, width, number, and granularity of temporary primary channels automatically become invalid when the AP's operating bandwidth changes in power-saving mode. The AP and terminal cease operating in secondary channel access mode until they re-establish secondary channel access mode with the new parameters. The specific establishment steps can be applied to Example 1. In some cases, the query frame is a re-association request frame, and the suggestion frame is a re-association response frame. In some cases, the above reconfiguration only completes the setting of channel access parameters and modes, but channel access is not started. A trigger frame or a dedicated frame indicates that channel access has started.

[0031] Besides determining whether to initiate reconfiguration based on the aforementioned energy-saving modes, reconfiguration can also be initiated based on the number and capabilities of the terminals. For example, in some cases, the current AP supports multiple bandwidths, such as a maximum support of 320MHz bandwidth. However, many terminals operate at 80MHz. To improve wireless network performance and balance the complexity of access points across different frequency bands, when the number of terminals operating on a certain bandwidth exceeds a certain threshold, the terminals initiate channel access reconfiguration. In some cases, such as a large number of terminals operating at 80MHz competing for the 80MHz spectrum resources, while the other 240MHz resources are not fully utilized, the terminals initiate channel reconfiguration based on the number of terminals currently operating on the 80MHz bandwidth. This divides the remaining 240MHz bandwidth into three 80MHz sub-bands, evenly switching these terminals to each 80MHz bandwidth. The performance of the current 80MHz terminals can be measured based on their number; for example, if the number exceeds 100, 75 of them can be evenly distributed across the other three 80MHz operating bandwidths. A threshold can be set for the number of terminals for each type of working bandwidth. When the number exceeds a certain limit, these terminals will be distributed evenly or unevenly across the entire working bandwidth of the AP.

[0032] For terminals operating in slave channel mode, when they are no longer operating in slave channel mode, or when they switch to other access points, similarly, when the number of terminals operating or parking at a certain slave channel granularity is small, below a certain number, the access point cancels that slave channel access granularity and switches the terminal to the main channel or another slave channel access granularity. In some cases, this slave channel access granularity is a combination of several 20MHz sub-channels within the slave channel, which can be called a slave channel group or a sub-channel group of slave channels. In some cases, there are terminal number limits for each slave channel access granularity, namely a maximum number limit and a minimum number limit. When the number is less than the minimum number, the slave channel access granularity is canceled. In some cases, this user number limit is included in the slave channel negotiation related frame or in the ICF frame used for slave channel access. In some cases, the signaling for adding or canceling a slave channel access granularity is included in the enhanced multi-link element (or basic multilinkelement). In some cases, it is included in a newly defined secondary channel access element or a newly defined non-primary channel access element. In other cases, it is included in a beacon, a probe response, or an association response frame. In some cases, adding or canceling a secondary channel access granularity is signaled by a bitmap where a bit of 0 indicates cancellation, and a bit of 1 indicates establishment or updating of the granularity's parameters.

[0033] When changes occur in service or service flow transmission, in some cases, due to the arrival or impending arrival of new services, or a reduction in service types, the services that the terminal needs to carry change. This leads to changes in the terminal's access channel duration, access bandwidth, or the number of access connections. If the terminal is operating in slave channel access mode, this will affect its slave channel access. For example, if a new service has low latency requirements, a separate slave channel access granularity can be established for the current terminal, specifically for transmitting low-latency services. The current slave channel granularity, established for the current terminal, does not experience latency due to competition between terminals within the AP. However, in other slave channel granularities, or when multiple terminals coexist on the primary channel, uplink low-latency service transmission will experience latency due to competition. In some cases, service flows trigger slave channel reconfiguration, which may include at least some service types or service identifiers (Traffi Identifiers, or TIDs). This signaling is typically contained in a basic multilink element or a newly defined multilink element. In some cases, it may be contained in a newly defined secondary channel access element or a newly defined non-primary channel access element. In some cases, it is included in a beacon, in a programmer's response, or in an association response frame.

[0034] When the operating state, mode, capability mode, or spatial flow of a terminal device changes, reconfiguration of the channel access may occur under certain circumstances. For example, some terminals initially maintain a connection and communicate with the AP. Later, if the number of working antennas or the workflow changes, the channel access mode is terminated. Alternatively, the granularity and bandwidth of the channel access may be reconfigured. In some cases, this reconfiguration is accomplished via trigger frames or control frames. In some cases, the control frame or trigger frame is sent to the AP by the terminal. In some cases, the trigger frame or control frame is sent to the terminal by the AP. In some cases, the trigger frame or control frame is sent to the terminal by the AP. After receiving the trigger frame or control frame, the terminal sends an acknowledgment frame. In some cases, the terminal or AP does not send an acknowledgment frame after receiving the trigger frame or control frame. In some cases, the terminal or AP does not send an acknowledgment frame after receiving the trigger frame or control frame and then transmits data on the channel. In some cases, the data is solicited by the trigger frame or control frame. In some cases, the control frame or trigger frame is transmitted on the channel. The above situations are not limited and can be reasonably combined in certain circumstances.

[0035] The following example illustrates the method for enabling the secondary channel access mode. The secondary channel access strategy can be negotiated with an existing access point device to obtain the strategy. Alternatively, before sending an inquiry frame to the access point device, a service binding relationship can be established through negotiation with the existing access point device. The terminal device with the service binding relationship with the access point device will send an inquiry frame to the access point device with which it has the service binding relationship when it receives a low-latency service transmission request. Specifically, in some cases, the secondary channel access mode is bound to a service flow. For example, if a device transmits a low-latency service, and the device supports secondary channel access, it will automatically start the secondary channel access mode. This binding relationship is determined during the secondary channel access negotiation and is included in the secondary channel access control frame. Alternatively, the binding relationship is included in the secondary channel access trigger frame. In some cases, the binding relationship is a signaling signal, or a bitmap corresponding to each service type, where a 1 for the corresponding service type indicates binding to that service, and otherwise indicates not binding to that service. In some cases, this signaling signal is included in the basic multilink element; in others, it is included in a beacon or in a probe response frame. In certain situations, if the service stops or the corresponding TID no longer maps to the current connection, the channel access mode will automatically stop. The receiving method can either end immediately or after several target beacon transmission times (TBTT).

[0036] The following example illustrates how to terminate the slave channel access mode. When a control frame for terminating the slave channel access mode is received, the slave channel access mode is terminated via the control frame; or, when a command to terminate slave channel access is received, the slave channel access mode is terminated after the currently ongoing transmission opportunity is completed. Specifically: In some cases, a terminal operating in slave channel access mode terminates the slave channel access mode upon receiving a control frame. In some cases, a terminal operating in slave channel access mode terminates the slave channel access mode upon receiving the aforementioned slave channel access suggestion frame again. In some cases, a terminal operating in slave channel access mode terminates the slave channel access mode if it is currently accessing a slave channel (primary channel busy, slave channel idle, and data being transmitted on the slave channel), upon completing the current transmission opportunity (TXOP). In some cases, a terminal operating in slave channel access mode receives a command to terminate slave channel access; if it is not currently accessing a slave channel (primary channel idle, slave channel idle, and data being transmitted simultaneously on both channels), it terminates the slave channel access mode upon completing the current TXOP. Alternatively, it may terminate the slave channel access mode immediately. In some cases, when a terminal operating in slave channel access mode receives a command to terminate slave channel access, if it is not currently connected to a slave channel (the master channel is idle, the slave channel is busy, and data is being transmitted simultaneously on both channels), it terminates slave channel access mode upon completion of the current TXOP. Alternatively, it may terminate slave channel access mode immediately. In some cases, slave channel access mode is a time period; upon its end, the terminal or AP's slave channel access mode automatically terminates. This time period is included in slave channel access negotiation-related frames or ICF frames used for slave channel access. In some cases, slave channel access mode is a time period; upon its end, the terminal or AP's slave channel access mode automatically terminates within several TBTTs. In some cases, the number of TBTTs is a default time, such as within two TBTTs. This time is included in slave channel access negotiation-related frames or ICF frames used for slave channel access. In some cases, slave channel access mode is a time period; upon its end, the terminal or AP's slave channel access mode automatically terminates within several TBTTs. The specific number of TBTTs is determined by negotiation frames, suggestion frames, or control frames.

[0037] In one example, in the secondary channel access mode, the terminal device continues to remain in the secondary channel access mode during seamless roaming with other access point devices; or, in the secondary channel access mode, the terminal device negotiates with other access point devices to determine whether to remain in the secondary channel access mode during seamless roaming with other access point devices.

[0038] When switching channel access modes, the default settings can be maintained, not maintained, or determined through negotiation as needed. Examples of these three scenarios will be discussed separately:

[0039] In cases where the secondary access mode is maintained, in some embodiments, when a terminal configured for secondary access mode switches between two access point devices, if the terminal was in secondary access mode with the original access point, it continues to maintain secondary access mode after switching to the new access point. Both access point devices support secondary access and have secondary access capabilities. The terminal also has secondary access capabilities. In some cases, both access point devices support secondary access and have secondary access capabilities, and these capabilities are enabled. The terminal also has secondary access capabilities, and these capabilities are enabled. In some cases, the switch is a normal switch between the two access point devices. In some cases, the switch is a seamless switch between the two access point devices. In some cases, secondary access or secondary access mode is initiated at the original access point by a trigger frame, control frame, or management frame. During the switch, the secondary access mode is not maintained at the target access point. In some cases, this mode operates within a single transmission opportunity. In some cases, semi-static secondary channel access or secondary channel access mode is initiated at the original access point by a trigger frame, control frame, or management frame. Upon handover, the secondary channel access mode continues at the target access point. In some cases, this mode operates across multiple transmission opportunities. In some cases, after the terminal switches to a new access point, if the new access point supports at least one of the following sets {secondary channel bandwidth, secondary channel access granularity, number of temporary primary channels, primary channel bandwidth}, and these values ​​are within the terminal's capabilities, then the terminal continues to maintain secondary channel access mode with the new access point.

[0040] In cases where the secondary channel access mode is not maintained, in some embodiments, a terminal configured for secondary channel access mode does not maintain its secondary channel access capability when switching between two access point devices. Both access point devices support secondary channel access. In some cases, the handover is a normal handover between the two access point devices. In other cases, the handover is a seamless handover between the two access point devices. In some cases, the secondary channel access mode between the terminal and the original access point automatically stops after the terminal is de-associated with or disconnected from the original access point, or after a connection is broken. In some cases, the secondary channel access mode is the secondary channel access mode on a connection between the terminal and an access point. In some cases, the secondary channel access mode is the secondary channel access mode between the terminal device and the access point device. In some cases, the secondary channel access mode between the terminal and the original access point is not maintained by default when the terminal connects to the new access point. In some cases, the new access point does not support secondary channel access mode, and therefore, the secondary channel access mode between the terminal and the original access point is not maintained by default when the terminal connects to the new access point.

[0041] Regarding the discussion of whether the secondary channel access mode is automatically continued, for example, during handover, whether the terminal continues its secondary channel access mode is determined by a bit, a subfield, contained in the link reconfiguration frame used for seamless handover, or in the link reconfiguration request frame or link reconfiguration response frame. 0 indicates continuation, and 1 indicates no continuation. In some cases, the handover is seamless. In other cases, continuation of the secondary channel access mode during handover requires the target connection and the original connection to have the same bandwidth. In some cases, the secondary channel access model-related parameters are contained in an element, which is included in the link reconfiguration frame used for seamless handover, or in the link reconfiguration request frame or link reconfiguration response frame. If the element is included in the frame, it indicates that the secondary channel access mode is automatically continued during handover. In some cases, the secondary channel access mode is maintained during handover only if both the target access point and the original access point support and enable secondary channel access.

[0042] When negotiating during channel access mode switching, the negotiation signaling is included in the link reconfiguration frame. Broadly speaking, negotiation can also be viewed as a reconfiguration process.

[0043] In some embodiments, negotiation includes the secondary channel access capabilities supported by the access point or terminal, such as bandwidth, granularity, and the number of temporary primary channels. In some cases, this signaling is included in a link reconfiguration frame. In some implementations, this signaling is included in a basic multi-link element enhanced for seamless handover, or a seamless roaming element defined for seamless handover. In some cases, this signaling is included in a newly defined frame for seamless handover, such as a seamless handover request frame, a seamless handover confirmation frame, or a seamless handover response frame. In some cases, the aforementioned frames or elements contain a signaling / field indicating whether secondary channel access negotiation should be performed during handover or initial access, with 0 indicating no negotiation and 1 indicating negotiation. In some cases, the aforementioned frames or elements contain a signaling / field indicating whether secondary channel access mode continuation should be performed between the terminal and the new access point during handover, with 0 indicating no continuation and 1 indicating continuation. In some cases, if the aforementioned frame or element contains a handover notification or advertisement for secondary channel access capability, then secondary channel access negotiation will be performed by default during handover or initial access. In some cases, when the terminal and the original access point are operating in secondary channel access mode, and the terminal needs to switch to a new access point, the terminal needs (or may) negotiate with the new access point whether to continue operating in secondary channel access mode. In some cases, this negotiation is completed by the original access point and the new access point. Secondary channel access related information is included in the seamless access request frame or in the seamless access proposal frame. In some cases, when the terminal and the original access point are not operating in secondary channel access mode, and the terminal needs to switch to a new access point, the terminal does not need to negotiate with the new access point whether to continue operating in secondary channel access mode. In some cases, this negotiation is completed by the original access point and the new access point. Secondary channel access related information is included in the seamless access request frame or in the seamless access proposal frame. In some cases, the negotiation of the channel access mode during seamless handover is not limited to whether the channel access mode between the terminal and the original access point is maintained between the terminal and the new access point. The negotiation content includes the granularity of the channel access mode, bandwidth, or duration, and the services that can be transmitted on the channel. This information is contained in the link reconfiguration frame, link reconfiguration request frame, link reconfiguration response frame, or multi-link element.

[0044] The following example illustrates the situation during link reconfiguration in channel access mode:

[0045] In some cases, the slave channel access mode is connection-level. This means that each access point attached to a multi-connection device can have different slave channel access modes, which can be enabled or disabled independently. In other cases, the slave channel access mode is multi-connection device-level. This means that each access point attached to a multi-connection device can have the same slave channel access mode, which can be enabled or disabled simultaneously.

[0046] In one example, the access point device is an Access Point Multiple Connection Device (AP MLD). During connection reconfiguration, if both the AP MLD and the terminal device are in slave channel access mode, and a new connection is added between the terminal device and the AP MLD, then the device corresponding to the newly added connection will operate in slave channel access mode. The purpose of link reconfiguration is to add and remove links from a multi-connection device. Specifically, in some cases, slave channel access mode may be maintained, transferred, or terminated during link reconfiguration.

[0047] In some cases, during link reconfiguration, if the terminal and access point multi-connection device are operating in slave channel access mode, and a new connection is added between the terminal and access point multi-connection device, the new connection will operate in slave channel access mode. In other cases, during link reconfiguration, the link reconfiguration request frame or link reconfiguration response frame includes whether the newly added connection should retain the current slave channel access mode. In some cases, this information is a single bit, 1 indicating retention and 0 indicating non-retention. In some cases, during link reconfiguration, newly added connections do not enable slave channel access mode by default. In some cases, during link reconfiguration, if a connection between the terminal and access point is disconnected, the slave channel access mode corresponding to that connection on the terminal side terminates with the disconnection. In some cases, during link reconfiguration, if a connection between the terminal and access point is disconnected, and the terminal was in slave channel access mode on that connection before the disconnection. Shortly after, if the terminal reconnects to the connection (corresponding AP), it will default to using the secondary channel access mode on that connection. In some cases, during link reconfiguration, if a connection between the terminal and the access point is broken and the terminal was in secondary channel access mode on that connection before the break, and the terminal reconnects shortly after, if the bit for retaining the secondary channel access mode is 1 in the link reconfiguration request / response frame or in the corresponding newly defined secondary channel access mode in the basic multiple link element, then the terminal will start using secondary channel access mode on that connection. Otherwise, secondary channel access mode will not be enabled.

[0048] In some cases, the information regarding whether the secondary channel access mode should continue during seamless handover is contained in the link reconfiguration request / response frame used for seamless handover, or in the seamless roaming request / response frame, or transmitted from the current access point (AP or AP MLD) to the target access point (AP or AP MLD). Alternatively, in some cases, the current terminal may include information from the current access point or a candidate access point indicating whether the candidate access point is operating in secondary channel access mode, or whether to continue in that secondary channel access mode. Or, in some cases, when the target AP MLD re-establishes the context with the terminal, the method described in this patent may be selected to continue, not continue, or renegotiate whether to enable secondary channel access mode.

[0049] In some cases, when accessing via a secondary channel, the secondary channel access mode is for a period of time. If this period does not end before the handover, the secondary channel access mode will continue to be used (keeping the secondary channel access enabled) after a seamless handover, until the remaining time of the secondary channel access expires or is exhausted.

[0050] When link switching occurs, the access mode from the secondary channel also needs to be handled accordingly. For example, during link switching, the secondary channel mode switching information determines whether the secondary channel access mode should continue. If it is determined to continue, the secondary channel access mode will be used after the link switch; if it is determined not to continue, the secondary channel access mode will be terminated after the link switch. The secondary channel mode switching information will be carried in the channel switching element sent by the access point device or pre-stored in the terminal device. Alternatively, when link switching occurs, the secondary channel access mode of the previous connection can be retained by default. For example, if the secondary channel access mode was enabled on the previous connection, it will be enabled by default on the channel after the switch. Otherwise, it will not be enabled. When link switching occurs, a new field is defined in the channel switching element or reserved information is enabled, using one bit to indicate whether the secondary channel access mode of the previous connection (channel) should be retained. For example, a bit of 1 indicates that the secondary channel access mode of the previous connection should be retained, such as when the secondary channel access mode was enabled on that connection. If this bit is set to 0, the access mode will be enabled by default on the new channel. Otherwise, it will not be enabled. In some cases of link switching, after the AP and associated terminals switch to the new channel, the access mode will not be enabled by default. In some situations, the access mode occurs over a period of time. If channel switching occurs within this period, the terminals and AP will enable the access mode on the new channel by default; otherwise, it will not be enabled.

[0051] The following example illustrates the situation where a connection (re)establishment occurs. In one example, during link (re)setup, a new AP attached to an Access Point Multi-Link device is enabled, or an existing AP is removed. During link (re)setup, the probe response frame, the (re)association request frame, or the (re)association response frame contains information about whether the newly established AP is enabled in slave channel access mode. For example, at least one of these frames contains a bit indicating whether slave channel access mode is enabled. In some cases, this bit is contained in the basic multi-link element. In some cases, if the current Access Point Multi-Link device and / or associated non-Access Point Multi-Link devices are both operating in slave channel access mode, the newly established AP is enabled in slave channel access mode or has slave channel access capability.

[0052] In this embodiment, a secondary channel access policy is negotiated with the associated access point device, and the channel access mode is switched to secondary channel access mode. The terminal device or access point device that switches to secondary channel access mode can perform secondary channel access when the primary channel is busy and the secondary channel is idle, and configures relevant parameters for data transmission on the secondary channel according to the secondary channel access policy. After performing secondary channel access according to the secondary channel access policy, when preset reconfiguration conditions are met, the secondary channel access policy is updated by renegotiating with the access point device to adjust the relevant parameters for data transmission on the secondary channel according to the secondary channel access policy. This enables the terminal device to perform secondary channel access, effectively utilizing secondary channel resources and saving wireless resources, while improving data transmission stability through the reconfiguration of secondary channel access.

[0053] The steps described above are for clarity only. In practice, they can be combined into one step or some steps can be split 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 or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this application.

[0054] Another embodiment of the present invention relates to a terminal, such as Figure 3As shown, it includes at least one processor 301; and a memory 302 communicatively connected to the at least one processor; wherein the memory 302 stores instructions executable by the at least one processor 301, the instructions being executed by the at least one processor 301 to enable the at least one processor 301 to perform the channel access method as described above.

[0055] The memory 302 and processor 301 are connected via a bus, which can include any number of interconnecting buses and bridges. The bus connects various circuits of one or more processors 301 and memory 302 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 therefore will not be described further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 301 is transmitted over a wireless medium via an antenna, which further receives data and transmits it to processor 301.

[0056] Processor 301 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. Memory 302 can be used to store data used by processor 301 during operation.

[0057] Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the above-described method embodiments.

[0058] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0059] Those skilled in the art will understand that the above embodiments are specific examples of implementing the present invention, and in practical applications, various changes in form and detail may be made without departing from the spirit and scope of the present invention.

Claims

1. A method for accessing a channel, characterized in that, Applied to a terminal device, the method includes: The access policy is negotiated with the associated access point equipment to obtain the access policy from the channel, and then the two devices switch to the access policy from the channel. Among them, the terminal device or access point device that switches to the secondary channel access mode will be able to perform secondary channel access when the main channel is busy and the secondary channel is idle, and configure the relevant parameters for data transmission on the secondary channel according to the secondary channel access strategy. After executing the secondary channel access according to the secondary channel access policy, when the preset reconfiguration conditions are met, the secondary channel access policy is updated by renegotiation with the access point device, so as to adjust the relevant parameters when transmitting data on the secondary channel according to the secondary channel access policy. The step of negotiating a secondary channel access strategy with the associated access point device and jointly switching to the secondary channel access mode includes: By sending an inquiry frame to the associated access point device to indicate that it supports switching to the secondary access mode; The query frame carries capability information indicating its own capabilities, information indicating the number of slave channels it can support, and information indicating the granularity of slave channels it can support. The access point device receives a suggestion frame based on the query frame. The suggestion frame carries temporary primary channel location information supported by the access point device and secondary channel granularity information supported by the access point device. The number of slave channels and the granularity of slave channels to be used in this access are selected based on the proposed frame to generate the slave channel access strategy; The channel access policy is sent to the access point device via a response frame; The preset reconfiguration conditions include: The access point device enters power-saving mode, and the number of temporary primary channels, the location of temporary primary channels, the granularity of the secondary channels, or the operating bandwidth in the terminal device change; and / or, The number of terminal devices operating on the same bandwidth reaches a first preset value; and / or, The slave channel granularity is cancelled because the number of connected terminal devices is less than the minimum limit; and / or, The number or type of services to be processed by the terminal device meets the preset reconfiguration requirements triggered by the services; and / or, The working state, working mode, capability mode, spatial flow, or service flow of the terminal device may change.

2. The channel access method according to claim 1, characterized in that, The method of obtaining the channel access strategy through negotiation with the access point device with existing connection also includes: Before sending the query frame to the access point device, negotiate with the existing access point device to establish a service binding relationship; Specifically, the terminal device that has the service binding relationship with the access point device will send the query frame to the access point device with the service binding relationship when it receives a low-latency service transmission request.

3. The channel access method according to claim 1, characterized in that, The method further includes: When a control frame for terminating the slave channel access mode is received, the slave channel access mode is terminated via the control frame; or, When a command to terminate the access via the channel is received, the access via the channel mode is terminated after the currently ongoing transmission opportunity is completed.

4. The channel access method according to claim 1, characterized in that, In the secondary channel access mode, during seamless roaming with other access point devices, the channel access mode is maintained in the secondary channel access mode; or, In the secondary channel access mode, during seamless roaming with other access point devices, the terminal device determines whether to remain in the secondary channel access mode by negotiating with the other access point devices.

5. The channel access method according to claim 1, characterized in that, The access point device is a multi-connection device with one access point. The method further includes: When a connection reconfiguration process is underway, and both the access point multi-connection device and the terminal device are in the slave channel access mode, and a new connection is added between the terminal device and the access point multi-connection device, then the device corresponding to the newly added connection is made to work in the slave channel access mode.

6. The channel access method according to claim 5, characterized in that, The method further includes: During the channel switching process, the channel mode switching information is used to determine whether the channel access mode needs to be continued. If it is determined that the slave channel access mode should continue to be used, then the slave channel access mode will continue to be used after the channel switch; if it is determined that the slave channel access mode should not continue to be used, then the slave channel access mode will end after the channel switch. The channel mode switching information will be carried in the channel switching element sent by the access point device or pre-stored in the terminal device.

7. A terminal, 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 to enable the at least one processor to perform the channel access method as described in any one of claims 1 to 6.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the channel access method according to any one of claims 1 to 6.

Images