Patent Description:
In a wireless communication scenario, a transmit end and a receive end are located in different radio channel environments. Therefore, it is very conducive for data communication if a bandwidth available to both the transmit end and the receive end can be negotiated based on channel availability of the transmit end and the receive end before data communication. To achieve this objective, in the <NUM>. 11ac standard, two bits (namely, a B5 bit and a B6 bit) in the first seven bits of a scrambling sequence (scrambling sequence) used by a non-high throughput (non-high throughput, non-HT) frame or a non-HT duplicated (duplicated) frame are used to indicate bandwidth modes. Four values of the two bits one-to-one correspond to four bandwidth modes. The four bandwidth modes are <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>).

Currently, the Institute of Electrical and Electronics Engineers (institute of electrical and electronics engineers, IEEE) is discussing the next-generation <NUM>. 11be standard after the <NUM>. Compared with the previous <NUM>. 11ax standard, the <NUM>. 11be standard supports data transmission with an extremely high throughput (extremely high throughput, EHT). 11be standard supports a maximum transmission bandwidth of <NUM>. Therefore, the <NUM>. 11be standard introduces bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>, such as <NUM>.

After the bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, how two devices negotiate a bandwidth mode is a technical problem to be urgently resolved.

<CIT> discloses methods, computer readable media, and apparatus for encoding and determining a bandwidth. <NUM> illustrates a service field bit assignment, including scrambler initialization, reserved service bits, R: reserved, and transmit order. The bits <NUM> through <NUM> may be used to encode the bandwidth information and an indication if static or dynamic bandwidth operation is supported.

"EHT RTS and CTS procedure", IEEE <NUM>-<NUM>/2125r2, discusses EHT PHY Support in MAC. 11be needs to define the MU-RTS/ RTS and CTS frames sent in a non-HT duplicate PPDU with preamble puncturing.

"Various Bit Order", IEEE <NUM>-<NUM>/0564r0, discusses VHT-SIG-B in SERVICE Field.

This application provides a bandwidth mode indication method and apparatus, so that in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>) are introduced, two devices can normally negotiate a bandwidth mode.

According to a first aspect, a bandwidth mode indication method is provided. The method includes: A transmit end generates a first frame, where the first frame is a non-HT frame or a non-HT duplicated frame, the first frame includes a service field, the service field includes a first field, the first field indicates whether a bandwidth mode indication field carried in the first frame indicates a target bandwidth mode, and the target bandwidth mode includes one or more of bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>; and then the transmit end sends the first frame to a receive end.

Based on the foregoing technical solution, the first frame uses only at least one bit in the service field as the first field, and does not increase or decrease a bit in the service field. In this way, backward compatibility of the first frame is ensured. In addition, the first field indicates whether the bandwidth mode indication field carried in the first frame is allowed to indicate the target bandwidth mode. In other words, because the service field of the first frame includes the first field, the bandwidth mode indication field carried in the first frame extends a range of bandwidth modes that can be indicated. Therefore, in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, two devices can negotiate, by transmitting the first frame, to use one bandwidth mode from more bandwidth modes.

In addition, that the first field is located in the service field of the first frame has the following advantages: (<NUM>) Currently, a reserved bit in a media access control (media access control, MAC) frame may be used by a chip vendor as a private indication bit. Therefore, if the reserved bit in the MAC frame is used as the first field, indication of the private bit is affected. However, using the bit in the service field as the first field can avoid affecting private use of the reserved bit in the MAC frame by the chip vendor. (<NUM>) Reserved bits in MAC frames of different types of conventional frames do not necessarily have the same location. Therefore, for the different types of transmission frames, implementation solutions of using the reserved bits in the MAC frames as the first field are different. The service field is a field introduced to perform a scrambling operation at a physical layer. The service field is located before the MAC frame, and the service field itself is a field at the physical layer, in other words, all types of conventional frames include the service field. In this way, using the bit in the service field as the first field is applicable to all types of conventional frames.

The first frame further includes a unicast/multicast bit. When the first field is set to a first preset value and the unicast/multicast bit is set to <NUM>, it indicates that the first frame does not carry the bandwidth mode indication field. Alternatively, when the first field is set to the first preset value and the unicast/multicast bit is set to <NUM>, it indicates that the first frame carries the bandwidth mode indication field and the bandwidth mode indication field indicates a bandwidth mode in a first bandwidth mode set, where the first bandwidth mode set includes <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>. Alternatively, when the first field is set to a second preset value and the unicast/multicast bit is set to <NUM>, it indicates that the first frame carries the bandwidth mode indication field and the bandwidth mode indication field indicates a bandwidth mode in a second bandwidth mode set, where the second bandwidth mode set includes the target bandwidth mode.

In a possible manner, when the first frame carries the bandwidth mode indication field and the first field is set to the first preset value, the bandwidth mode indication field occupies a B5 bit and a B6 bit in the first seven bits of a scrambling sequence.

In a possible manner, when the first frame carries the bandwidth mode indication field and the first field is set to the second preset value, the bandwidth mode indication field is one of the following cases: The bandwidth mode indication field occupies the B5 bit and the B6 bit in the first seven bits of the scrambling sequence; or the bandwidth mode indication field occupies at least three bits in the first seven bits of the scrambling sequence; or the bandwidth mode indication field occupies at least one bit in the last nine bits of the service field; or the bandwidth mode indication field occupies at least one bit in the first seven bits of the scrambling sequence and at least one bit in the last nine bits of the service field.

In a possible manner, when a value of the first field is the second preset value, the bandwidth mode indication field includes a fourth field and a fifth field. When the fourth field indicates that a total bandwidth is less than or equal to <NUM>, each of eight bits occupied by the fifth field corresponds to one <NUM> channel, and one bit indicates whether the <NUM> channel corresponding to the bit is idle. When the fourth field indicates that the total bandwidth is greater than <NUM> or equal to <NUM> or <NUM>+<NUM>, the fifth field includes four first bits, two second bits, and two third bits. Each of the four first bits corresponds to one <NUM> channel of a primary <NUM> channel, each of the two second bits corresponds to one <NUM> channel of a secondary <NUM> channel, and each of the two third bits corresponds to one <NUM> of a secondary <NUM>. The first bit indicates whether the <NUM> channel corresponding to the first bit is idle, the second bit indicates whether the <NUM> channel corresponding to the second bit is idle, and the third bit indicates whether the <NUM> channel corresponding to the third bit is idle.

The first field occupies bit <NUM> of the service field.

In a possible manner, the target bandwidth mode includes a preamble puncturing bandwidth mode and/or a non-preamble puncturing bandwidth mode.

According to a second aspect, a bandwidth mode indication method is provided. The method includes: A receive end receives a first frame, where the first frame is a non-HT frame or a non-HT duplicated frame, the first frame includes a service field, the service field includes a first field, the first field indicates whether a bandwidth mode indication field carried in the first frame indicates a target bandwidth mode, and the target bandwidth mode includes one or more of bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>; and then the receive end parses the first frame.

Based on the foregoing technical solution, the first frame uses only at least one bit in the service field as the first field, and does not increase or decrease a bit in the service field. In this way, backward compatibility of the first frame is ensured. The first field indicates whether the bandwidth mode indication field carried in the first frame is allowed to indicate the target bandwidth mode. In other words, because the service field of the first frame includes the first field, the bandwidth mode indication field carried in the first frame extends a range of bandwidth modes that can be indicated. Therefore, in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, two devices can negotiate, by transmitting the first frame, to use one bandwidth mode from more bandwidth modes.

According to a third aspect, a bandwidth mode indication method is provided, according to independent claim <NUM>.

Based on the foregoing technical solution, the second frame uses only at least one bit in the service field as the second field, and does not increase or decrease a bit in the service field. In this way, backward compatibility of the second frame is ensured. In addition, the second field indicates whether the bandwidth mode of the second frame is the target bandwidth mode. Therefore, in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, two devices can negotiate, by transmitting the second frame, to use one bandwidth mode from more bandwidth modes.

In addition, that the second field is located in the service field of the second frame has the following advantages: (<NUM>) Currently, a reserved bit in a MAC frame may be used by a chip vendor as a private indication bit. Therefore, if the reserved bit in the MAC frame is used as the second field, indication of the private bit is affected. However, using the bit in the service field as the second field can avoid affecting private use of the reserved bit in the MAC frame by the chip vendor. (<NUM>) Reserved bits in MAC frames of different types of conventional frames do not necessarily have the same location. Therefore, for the different types of transmission frames, implementation solutions of using the reserved bits in the MAC frames as the second field are different. The service field is a field introduced to perform a scrambling operation at a physical layer. The service field is located before the MAC frame, and the service field itself is a field at the physical layer, in other words, all types of conventional frames include the service field. In this way, using the bit in the service field as the second field is applicable to all types of conventional frames.

According to a fourth aspect, a bandwidth mode indication method is provided, according to independent claim <NUM>.

According to a ninth aspect, a communication apparatus is provided, according to independent claim <NUM>.

According to a tenth aspect, a communication apparatus is provided, according to independent claim <NUM>.

According to an eighteenth aspect, a computer-readable storage medium is provided, according to either of claims <NUM> or <NUM>.

According to a nineteenth aspect, a computer program product including computer instructions is provided. When the computer instructions are run on a computer, the computer is enabled to perform any method provided in any one of the first aspect to the eighth aspect.

According to a twentieth aspect, a chip is provided, including a processing circuit and a transceiver pin. The processing circuit and the transceiver pin are configured to implement any method provided in any one of the first aspect to the eighth aspect. The processing circuit is configured to perform a processing action in the corresponding method, and the transceiver pin is configured to perform a receiving/sending action in the corresponding method.

It should be noted that for technical effects brought by any design in the ninth aspect to the twentieth aspect, refer to technical effects brought by corresponding designs in the first aspect to the eighth aspect.

In descriptions of this application, unless otherwise specified, "/" means "or". For example, A/B may represent A or B. A term "and/or" in this specification describes only an association relationship between associated objects and indicates that there may be three relationships. In addition, "at least one" means one or more, and "a plurality of" means two or more. The terms such as "first" and "second" do not limit a quantity and an execution sequence, and the terms such as "first" and "second" do not indicate a definite difference either.

In this application, the word "example", "for example", or the like is used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as an "example" or with "for example" in this application should not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the word "example", "for example" or the like is intended to present a relative concept in a specific manner.

The WLAN starts from the <NUM>. 11a/g, goes through the <NUM>. 11n and the <NUM>. 11ac, and goes through the <NUM>. 11ax and the <NUM>. 11be that are currently discussed. For allowed transmission bandwidths of the WLAN, refer to Table <NUM>. 11n standard is also referred to as a high throughput (high throughput, HT), the <NUM>. 11ac standard is referred to as a very high throughput (very high throughput, VHT), the <NUM>. 11ax (Wi-Fi <NUM>) is referred to as an HE, the <NUM>. 11be (Wi-Fi <NUM>) is referred to as an extremely high throughput (extremely high throughput, EHT), and standards before the HT, such as the <NUM>. 11a/b/g, are collectively referred to as a non-high throughput (Non-HT). 11b uses a non-orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) mode, and therefore is not listed in Table <NUM>.

For example, channel distribution of a <NUM> bandwidth may be shown in <FIG>. A <NUM> channel may be divided into sixteen <NUM> channels. The sixteen <NUM> channels may be sequentially numbered from a high frequency to a low frequency, or may be sequentially numbered from a low frequency to a high frequency.

For example, in <FIG>, a channel <NUM> may be used as a primary <NUM> channel, and a channel <NUM> may be used as a secondary <NUM> channel. The channel <NUM> and the channel <NUM> may be aggregated as a primary <NUM> channel. A channel <NUM> and a channel <NUM> may be aggregated as a secondary <NUM> channel. The channel <NUM> to the channel <NUM> may be aggregated as a primary <NUM> channel. A channel <NUM> to a channel <NUM> may be aggregated as a secondary <NUM> channel. The channel <NUM> to the channel <NUM> may be aggregated as a primary <NUM> channel. A channel <NUM> to a channel <NUM> may be aggregated as a secondary <NUM> channel.

It should be noted that the primary <NUM> channel is not necessarily a <NUM> channel located at the beginning. For example, the channel <NUM> may be used as the primary <NUM> channel, the channel <NUM> may be used as the secondary <NUM> channel, the channel <NUM> and the channel <NUM> may be aggregated as the primary <NUM> channel, the channel <NUM> and the channel <NUM> may be aggregated as the secondary <NUM> channel, the channel <NUM> to the channel <NUM> may be aggregated as the primary <NUM> channel, the channel <NUM> to the channel <NUM> may be aggregated as the secondary <NUM> channel, the channel <NUM> to the channel <NUM> may be aggregated as the primary <NUM> channel, and the channel <NUM> to the channel <NUM> may be aggregated as the secondary <NUM> channel. The secondary channel may alternatively have another name, for example, a slave channel or an auxiliary channel. This embodiment of this application is not limited thereto.

In a standard after the <NUM>. 11a, to ensure backward compatibility, some control frames are sent in a non-HT duplicated manner on a channel with a bandwidth greater than <NUM>. In other words, the control frame uses a non-HT format (in other words, the control frame uses a format that complies with the <NUM>. 11a standard), and the control frame is copied to <NUM> channels in the channels for sending. For ease of description, a frame sent in the non-HT duplicated manner is referred to as a non-HT duplicated frame or a frame in a non-HT duplicated format below.

In a wireless communication scenario, a transmit end and a receive end are located in different radio channel environments. Therefore, it is very conducive for data communication if a bandwidth available to both the transmit end and the receive end can be negotiated based on channel availability of the transmit end and the receive end before data communication.

In the <NUM>. 11n standard, the non-HT duplicated frame or a non-HT frame includes a service field. For a structure of the service field, refer to <FIG>. The service field may be divided into two parts. The first seven bits of the service field are used to carry the first seven bits of a scrambling sequence, and the last nine bits of the service field are reserved service bits.

To implement an objective of negotiating a bandwidth mode, in the <NUM>. 11ac standard, a B5 bit and a B6 bit in the first seven bits of the scrambling sequence used by the non-HT duplicated frame or the non-HT frame are set as a CH_BANDWIDTH_IN_NON_HT field, where the CH_BANDWIDTH_IN_NON_HT field indicates a bandwidth mode.

The first seven bits of the scrambling sequence are sequentially numbered a B0 bit to the B6 bit from a low bit to a high bit. Therefore, the B5 bit is the sixth bit in the first seven bits of the scrambling sequence, and the B6 bit is the seventh bit in the first seven bits of the scrambling sequence.

For example, in the <NUM>. 11ac standard, correspondences between values of the CH_BANDWIDTH_IN_NON_HT field and bandwidth modes may be shown in Table <NUM>. A unit of a channel bandwidth (channel bandwidth, CBW) in Table <NUM> is MHz.

The bandwidth mode may also be referred to as the channel bandwidth. A bandwidth mode indicated by a CH_BANDWIDTH_IN_NON_HT field in a current frame is a channel bandwidth used for transmitting the frame.

Optionally, to enable the receive end to know whether the transmit end adds the CH_BANDWIDTH_IN_NON_HT field to the scrambling sequence, the transmit end uses a unicast (unicast)/multicast (multicast) bit in a transmitter address (transmitter address, TA) field in the non-HT duplicated frame or the non-HT frame to indicate whether the B5 bit and the B6 bit in the first seven bits of the scrambling sequence are used as the CH_BANDWIDTH_IN_NON_HT field. Specifically, if the unicast/multicast bit is set to <NUM>, it indicates that the B5 bit and the B6 bit in the first seven bits of the scrambling sequence are used as the CH_BANDWIDTH_IN_NON_HT field. If the unicast/multicast bit is set to <NUM>, it indicates that the B5 bit and the B6 bit in the first seven bits of the scrambling sequence are not used as the CH_BANDWIDTH_IN_NON_HT field.

With development of technologies, in the wireless communication scenario, bandwidth modes that may be used between the transmit end and the receive end may exceed the four bandwidth modes shown in Table <NUM>. For example, because the <NUM>. 11be standard supports a maximum transmission bandwidth of <NUM>, other bandwidth modes such as <NUM> may be used between the transmit end and the receive end that use the <NUM>. 11be standard.

Currently, the CH_BANDWIDTH_IN_NON_HT field supports only the four bandwidth modes shown in Table <NUM>. Therefore, in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, how the non-HT duplicated frame or the non-HT frame indicates a bandwidth mode is a technical problem that needs to be urgently resolved.

To resolve this technical problem, embodiments of this application provide a bandwidth mode indication method and apparatus. The technical solutions provided in this application may be applied to various communication systems, for example, a system using the IEEE <NUM> standard. For example, the IEEE <NUM> standard includes but is not limited to the <NUM>. 11be standard or the next-generation <NUM> standard. Scenarios to which the technical solutions of this application are applicable include communication between an access point (access point, AP) and a station (station, STA), communication between APs, communication between STAs, and the like.

The STAs in this application may be various user terminals, user apparatuses, access apparatuses, subscriber stations, subscriber units, mobile stations, user agents, user devices, or other devices that have a wireless communication function. The user terminals may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices that have the wireless communication function or another processing device connected to a wireless modem; and include various forms of user equipment (user equipment, UE), mobile stations (mobile station, MS), terminals (terminal), terminal equipment (terminal equipment), portable communication devices, handheld devices, portable computing devices, entertainment devices, game devices or systems, global positioning system devices, or any other suitable device configured to perform network communication via wireless media. Herein, for ease of description, the devices mentioned above are collectively referred to as stations or STAs.

An access point AP in this application is an apparatus that is deployed in a wireless communication network and that provides a wireless communication function for a STA associated with the access point. The access point AP may be used as a hub of a communication system, and may be a communication device such as a base station, a router, a gateway, a repeater, a communication server, a switch, or a bridge. The base station may include a macro base station, a micro base station, a relay station, and the like in various forms. Herein, for ease of description, the devices mentioned above are collectively referred to as access points APs.

An embodiment of this application provides a first frame. The first frame is a non-HT duplicated frame or a non-HT frame, for example, an RTS frame or a CTS frame.

The first frame includes a service field. The service field carried in the first frame occupies <NUM> bits. In other words, compared with a non-HT duplicated frame or a non-HT frame defined in the <NUM>. 11n standard, no bit is added to or removed from the first frame provided in this application, so that the first frame has backward compatibility.

The service field of the first frame includes a first field, and the first field indicates whether a bandwidth mode indication field carried in the first frame is allowed to indicate a target bandwidth mode. The target bandwidth mode includes one or more of bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>. For example, the target bandwidth mode may include <NUM> (or <NUM>+<NUM>), <NUM>, or the like. This is not limited herein.

Optionally, the first field occupies at least one bit in B7 to B15 bits in the service field. For example, the first field occupies the B7 bit, a B11 bit, or the B15 bit in the service field.

In this embodiment of this application, when the first frame carries the bandwidth mode indication field, bits occupied by the bandwidth mode indication field are different from bits occupied by the first field.

Optionally, when the first field occupies one bit, that the first field indicates whether a bandwidth mode indication field carried in the first frame is allowed to indicate a target bandwidth mode includes: When the first field is set to a first preset value, the first field indicates that the bandwidth mode indication field carried in the first frame is not allowed to indicate the target bandwidth mode; or when the first field is set to a second preset value, the first field indicates that the bandwidth mode indication field carried in the first frame is allowed to indicate the target bandwidth mode.

For example, when the first field is implemented by using one bit, the first preset value may be <NUM>, and the second preset value may be <NUM>; or the first preset value may be <NUM>, and the second preset value may be <NUM>.

Optionally, when the first field occupies a plurality of bits, that the first field indicates whether a bandwidth mode indication field carried in the first frame is allowed to indicate a target bandwidth mode includes: When the first field is set to the first preset value, the first field indicates that the bandwidth mode indication field carried in the first frame is not allowed to indicate the target bandwidth mode; or when the first field is set to another value other than the first preset value, the first field indicates that the bandwidth mode indication field carried in the first frame is allowed to indicate the target bandwidth mode. There are one or more other values.

Optionally, when the first field occupies the plurality of bits, the first field may have another function. For example, the first field may further indicates a total bandwidth.

Optionally, the first frame may use any one of the following designs.

Design <NUM>: The first field occupies at least one bit, and the first frame indicates the bandwidth mode in the following manner (<NUM>-<NUM>) or (<NUM>-<NUM>).

(<NUM>-<NUM>): When the first field is set to the first preset value, the first frame does not carry the bandwidth mode indication field, or the bandwidth mode indication field carried in the first frame indicates a bandwidth mode in a first bandwidth mode set.

When the first field is set to the first preset value, the bandwidth mode indication field carried in the first frame is implemented by using two bits (for example, the B5 bit and the B6 bit) in the first seven bits of the scrambling sequence. Bandwidth modes included in the first bandwidth mode set are <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>). For correspondences between the values of the bandwidth mode indication field and the enumerated values of the bandwidth modes, refer to Table <NUM>. This is uniformly described herein, and details are not described below again.

(<NUM>-<NUM>): When the first field is set to the second preset value, the bandwidth mode indication field carried in the first frame indicates a bandwidth mode in a second bandwidth mode set. The second bandwidth mode set includes the target bandwidth mode.

Optionally, when the bandwidth mode indication field occupies one or two bits, the second bandwidth mode set does not include the four bandwidth modes: <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>. In other words, an intersection set between the second bandwidth mode set and the first bandwidth mode set is empty.

Optionally, when the bandwidth mode indication field occupies at least three bits, the second bandwidth mode set may include the four bandwidth modes: <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>). In other words, the first bandwidth mode set is a proper subset of the second bandwidth mode set. Based on this, the second bandwidth mode set includes at least five bandwidth modes.

Optionally, when the bandwidth mode indication field occupies the at least three bits, the second bandwidth mode set does not include the four bandwidth modes: <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>). In other words, the intersection set between the second bandwidth mode set and the first bandwidth mode set is empty. Based on this, a quantity of bandwidth modes included in the second bandwidth mode set is not limited in this embodiment of this application. For example, the second bandwidth mode set may include <NUM> or <NUM> bandwidth modes.

Design <NUM>: The first field occupies at least one bit, and the first frame further includes the unicast/multicast bit. The first frame indicates the bandwidth mode in the following manners (<NUM>-<NUM>), (<NUM>-<NUM>), or (<NUM>-<NUM>).

(<NUM>-<NUM>): When the unicast/multicast bit is set to <NUM>, it indicates that the first frame does not carry the bandwidth mode indication field.

(<NUM>-<NUM>): When the first field is set to the first preset value and the unicast/multicast bit is set to <NUM>, the bandwidth mode indication field carried in the first frame indicates the bandwidth mode in the first bandwidth mode set.

(<NUM>-<NUM>): When the first field is set to the second preset value and the unicast/multicast bit is set to <NUM> or <NUM>, the bandwidth mode indication field carried in the first frame indicates the bandwidth mode in the second bandwidth mode set.

Design <NUM>: The first field occupies at least one bit, and the first frame further includes the unicast/multicast bit. The first frame indicates the bandwidth mode in the following manners (<NUM>-<NUM>), (<NUM>-<NUM>), (<NUM>-<NUM>) or (<NUM>-<NUM>).

(<NUM>-<NUM>): When the first field is set to the first preset value and the unicast/multicast bit is set to <NUM>, it indicates that the first frame does not carry the bandwidth mode indication field.

(<NUM>-<NUM>): When the first field is set to the second preset value and the unicast/multicast bit is set to <NUM>, the bandwidth mode indication field carried in the first frame indicates a bandwidth mode in a third bandwidth mode set.

(<NUM>-<NUM>): When the first field is set to the second preset value and the unicast/multicast bit is set to <NUM>, the bandwidth mode indication field carried in the first frame indicates a bandwidth mode in a fourth bandwidth mode set.

In this embodiment of this application, at least one of the third bandwidth mode set and the fourth bandwidth mode set includes the target bandwidth mode. In addition, the bandwidth mode included in the third bandwidth mode set is different from the bandwidth mode included in the fourth bandwidth mode set.

In a possible manner, the third bandwidth mode set may include one or more of the four bandwidth modes: <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>), and/or the fourth bandwidth mode set may include one or more of the four bandwidth modes: <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>).

In another possible design, the third bandwidth mode set does not include the four bandwidth modes: <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>), and the fourth bandwidth mode set does not include the four bandwidth modes: <NUM>, <NUM>, <NUM>, and <NUM> (or <NUM>+<NUM>).

Optionally, based on any one of the foregoing design <NUM> to design <NUM>, when a value of the first field is the second preset value, the bandwidth mode indication field carried in the first frame may use any one of the following implementations <NUM>-<NUM> to <NUM>-<NUM>.

Implementation <NUM>-<NUM>: The bandwidth mode indication field is implemented by using one or two bits in the first seven bits of the scrambling sequence.

For example, the bandwidth mode indication field may be implemented by using the B5 bit and the B6 bit in the first seven bits of the scrambling sequence.

Implementation <NUM>-<NUM>: The bandwidth mode indication field is implemented by using at least three bits in the first seven bits of the scrambling sequence.

For example, the bandwidth mode indication field may be implemented by using a B3 bit, the B5 bit, and the B6 bit in the first seven bits of the scrambling sequence.

Implementations <NUM>-<NUM>: The bandwidth mode indication field is implemented by using one or more bits in the last nine bits of the service field.

For example, the bandwidth mode indication field occupies six bits B9 to B14 of the service field.

Implementation <NUM>-<NUM>: The bandwidth mode indication field is implemented by using at least one bit in the first seven bits of the scrambling sequence and at least one bit in the last nine bits of the service field.

For example, the bandwidth mode indication field occupies the two bits B5 to B6 in the scrambling sequence and four bits B11 to B14 in the service field.

For example, the bandwidth mode indication field occupies the three bits B3, B5, and B6 in the scrambling sequence and the three bits B12 to B14 in the service field.

Optionally, the second bandwidth mode set, the third bandwidth mode set, or the fourth bandwidth mode set may include a preamble puncturing bandwidth mode and/or a non-preamble puncturing bandwidth mode. The non-preamble puncturing bandwidth mode may also be referred to as a preamble non-puncturing bandwidth mode.

For example, for the preamble puncturing bandwidth mode and the non-preamble puncturing bandwidth mode that are defined by the <NUM>. 11be based on non-orthogonal frequency division multiple access (non-orthogonal frequency division multiple access, non-OFDMA), refer to Table <NUM>. Table <NUM> shows <NUM> bandwidth modes. In Table <NUM>, one "<NUM>" or "X" corresponds to one <NUM> channel, "<NUM>" indicates that the corresponding <NUM> channel is idle, and "X" indicates that the corresponding <NUM> channel is busy or not available (no available).

In this embodiment of this application, for a preamble puncturing bandwidth mode, a total bandwidth corresponding to the bandwidth mode is a bandwidth when preamble puncturing is not performed. For example, the total bandwidth may be <NUM>, <NUM>, <NUM>, <NUM> (or <NUM>+<NUM>), or <NUM> (or <NUM>+<NUM>).

Design <NUM>: The first field occupies one bit, and the first frame indicates the bandwidth mode in the following manner (<NUM>-<NUM>) or (<NUM>-<NUM>).

(<NUM>-<NUM>): When the first field is set to the first preset value, the first frame does not carry the bandwidth mode indication field, or the bandwidth mode indication field carried in the first frame indicates the bandwidth mode in the first bandwidth mode set.

(<NUM>-<NUM>): When the first field is set to the second preset value, the bandwidth mode indication field carried in the first frame includes a fourth field and a fifth field. The fourth field indicates the total bandwidth. The fifth field indicates preamble puncturing information corresponding to the total bandwidth. In other words, the fifth field indicates availability of each channel corresponding to the total bandwidth.

The fourth field may occupy at least one bit, and the fifth field occupies at least one bit. The fourth field and the fifth field are located in the service field.

Optionally, the fourth field may use any one of the following implementations <NUM>-<NUM> to <NUM>-<NUM>.

Implementation <NUM>-<NUM>: The fourth field occupies one bit. The fourth field indicates the total bandwidth, and includes the following case <NUM>-<NUM> and/or case <NUM>-<NUM>.

Case <NUM>-<NUM>: When a value of the fourth field is an eleventh preset value, it indicates that the total bandwidth is less than or equal to <NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is a twelfth preset value, it indicates that the total bandwidth is greater than <NUM>, or the total bandwidth is equal to <NUM> or <NUM>+<NUM>.

Implementation <NUM>-<NUM>: The fourth field occupies two bits. The fourth field indicates the total bandwidth, and includes one or more of the following cases <NUM>-<NUM> to <NUM>-<NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is the eleventh preset value, it indicates that the total bandwidth is equal to <NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is the twelfth preset value, it indicates that the total bandwidth is equal to <NUM> or <NUM>+<NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is a thirteenth preset value, it indicates that the total bandwidth is equal to <NUM> or <NUM>+<NUM>.

For example, the eleventh preset value, the twelfth preset value, and the thirteenth preset value are <NUM>, <NUM>, and <NUM>.

Implementation <NUM>-<NUM>: The fourth field occupies three bits. The fourth field indicates the total bandwidth, and includes one or more of the following cases <NUM>-<NUM> to <NUM>-<NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is the twelfth preset value, it indicates that the total bandwidth is equal to <NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is the thirteenth preset value, it indicates that the total bandwidth is equal to <NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is a fourteenth preset value, it indicates that the total bandwidth is equal to <NUM> or <NUM>+<NUM>.

Case <NUM>-<NUM>: When the value of the fourth field is a fifteenth preset value, it indicates that the total bandwidth is equal to <NUM> or <NUM>+<NUM>.

For example, the eleventh preset value to the fifteenth preset value are sequentially <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>.

Optionally, the fifth field may use any one of the following implementations <NUM>-<NUM> to <NUM>-<NUM>.

Implementation <NUM>-<NUM>: The fifth field occupies eight bits. The fifth field indicates the preamble puncturing information corresponding to the total bandwidth, and includes the following case <NUM>-<NUM> or case <NUM>-<NUM>.

Case <NUM>-<NUM>: When the total bandwidth indicated by the fourth field is less than or equal to <NUM>, each bit in the fifth field corresponds to one <NUM> channel. One bit indicates whether the <NUM> channel corresponding to the bit is idle.

Optionally, channels corresponding to bits in the fifth field are sequentially set in an order from a low frequency to a high frequency. In this way, in the fifth field, a least significant bit corresponds to a low-frequency channel, and a most significant bit corresponds to a high-frequency channel.

Optionally, the channels corresponding to the bits in the fifth field are sequentially set in an order from a high frequency to a low frequency. In this way, in the fifth field, a least significant bit corresponds to a high-frequency channel, and a most significant bit corresponds to a low-frequency channel.

The foregoing correspondences between the bits and the channels are not only applicable to case <NUM>-<NUM> of the fifth field, but also applicable to another case of the fifth field or another field.

That one bit indicates whether a channel corresponding to the bit is idle may be as follows: When the bit is set to a seventh preset value, it indicates that the channel corresponding to the bit is available; or when the bit is set to an eighth preset value, it indicates that the channel corresponding to the bit is not available or busy. Optionally, the seventh preset value is <NUM>, and the eighth preset value is <NUM>. Alternatively, the seventh preset value is <NUM>, and the eighth preset value is <NUM>. This is uniformly described herein, and details are not described below again.

In this embodiment of this application, "a channel is not available or busy" may be replaced with "a channel is punctured", and "a channel is idle" may be replaced with "a channel is not punctured".

Case <NUM>-<NUM>: When the total bandwidth indicated by the fourth field is greater than <NUM>, each bit in the fifth field corresponds to one <NUM> channel. A first bit indicates whether a secondary <NUM> channel of a primary <NUM> channel is idle, and the first bit corresponds to the primary <NUM> channel. A second bit indicates whether a <NUM> channel corresponding to the second bit is idle. The second bit is any one of bits other than the first bit in the fifth field.

Case <NUM>-<NUM>: The fifth field includes four first bits, two second bits, and two third bits. Each of the four first bits corresponds to one <NUM> channel of a primary <NUM> channel, each of the two second bits corresponds to one <NUM> channel of a secondary <NUM> channel, and each of the two third bits corresponds to one <NUM> channel of a secondary <NUM> channel. The first bit indicates whether the <NUM> channel corresponding to the first bit is idle. The second bit indicates whether the <NUM> channel corresponding to the second bit is idle. The third bit indicates whether the <NUM> channel corresponding to the third bit is idle.

Implementation <NUM>-<NUM>: The fifth field occupies <NUM> bits. The fifth field indicates the preamble puncturing information corresponding to the total bandwidth, and includes the following case <NUM>-<NUM> or case <NUM>-<NUM>.

Case <NUM>-<NUM>: When the total bandwidth indicated by the fourth field is less than or equal to <NUM>, each of the eight bits in the fifth field corresponds to one <NUM> channel. One bit indicates whether the <NUM> channel corresponding to the bit is idle.

Case <NUM>-<NUM>: When the total bandwidth indicated by the fourth field is greater than <NUM>, the fifth field includes four first bits, two second bits, and four third bits. Each of the four first bits corresponds to one <NUM> channel of the primary <NUM> channel. Each of the two second bits corresponds to one <NUM> channel of the secondary <NUM> channel. Each of the four third bits corresponds to one <NUM> channel of the secondary <NUM> channel. The first bit indicates whether the <NUM> channel corresponding to the first bit is idle. The second bit indicates whether the <NUM> channel corresponding to the second bit is idle. The third bit indicates whether the <NUM> channel corresponding to the third bit is idle.

Case <NUM>-<NUM>: When the total bandwidth indicated by the fourth field is greater than <NUM>, the fifth field includes eight first bits and two second bits. Each of the eight first bits corresponds to one <NUM> channel of the primary <NUM> channel. Each of the two second bits corresponds to one <NUM> channel of the secondary <NUM> channel. The first bit indicates whether the <NUM> channel corresponding to the first bit is idle. The second bit indicates whether the <NUM> channel corresponding to the second bit is idle.

Design <NUM>: The first field occupies two bits, and the first frame indicates the bandwidth mode in the following manners (<NUM>-<NUM>), (<NUM>-<NUM>), or (<NUM>-<NUM>).

(<NUM>-<NUM>): When the first field is set to the second preset value, the first field indicates that the total bandwidth is less than or equal to <NUM>, and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is less than or equal to <NUM>.

(<NUM>-<NUM>): When the first field is set to a third preset value, the first field indicates that the total bandwidth is greater than <NUM> (or the total bandwidth is equal to <NUM>), and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is greater than <NUM>.

Design <NUM>: The first field occupies two bits, and the first frame indicates the bandwidth mode in the following manners (<NUM>-<NUM>), (<NUM>-<NUM>), (<NUM>-<NUM>), or (<NUM>-<NUM>).

(<NUM>-<NUM>): When the first field is set to the second preset value, the first field indicates that the total bandwidth is equal to <NUM>, and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is equal to <NUM>.

(<NUM>-<NUM>): When the first field is set to the third preset value, the first field indicates that the total bandwidth is equal to <NUM>, and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is equal to <NUM>.

(<NUM>-<NUM>): When the first field is set to a fourth preset value, the first field indicates that the total bandwidth is equal to <NUM>, and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is equal to <NUM>.

Design <NUM>: The first field occupies three bits, and the first frame indicates the bandwidth mode in the following manners (<NUM>-<NUM>), (<NUM>-<NUM>), (<NUM>-<NUM>), (<NUM>-<NUM>), or (<NUM>-<NUM>).

(<NUM>-<NUM>): When the first field is set to the fourth preset value, the first field indicates that the total bandwidth is equal to <NUM>, and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is equal to <NUM>.

(<NUM>-<NUM>): When the first field is set to a fifth preset value, the first field indicates that the total bandwidth is equal to <NUM>, and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is equal to <NUM>.

(<NUM>-<NUM>): When the first field is set to a sixth preset value, the first field indicates that the total bandwidth is equal to <NUM>, and the bandwidth mode indication field indicates whether each channel is idle when the total bandwidth is equal to <NUM>.

Optionally, based on any one of the design <NUM> to the design <NUM>, when the total bandwidth indicated by the first field is less than or equal to <NUM>, the bandwidth mode indication field includes any one of the following implementation <NUM>-<NUM> or implementation <NUM>-<NUM>.

Implementation <NUM>-<NUM>: The bandwidth mode indication field occupies eight bits, and each bit in the bandwidth mode indication field corresponds to one <NUM> channel. One bit indicates whether the <NUM> channel corresponding to the bit is idle.

Implementation <NUM>-<NUM>: The bandwidth mode indication field occupies <NUM> bits, and each of the eight fields in the bandwidth mode indication field corresponds to one <NUM> channel. One bit indicates whether the <NUM> channel corresponding to the bit is idle.

Optionally, based on any one of the design <NUM> to the design <NUM>, when the total bandwidth indicated by the first field is greater than <NUM>, or the total bandwidth indicated by the first field is equal to <NUM>, the bandwidth mode indication field includes any one of the following implementations <NUM>-<NUM> to <NUM>-<NUM>.

Implementation <NUM>-<NUM>: The bandwidth mode indication field occupies eight bits, and each bit in the bandwidth mode indication field corresponds to one <NUM> channel. The first bit indicates whether the secondary <NUM> channel of the primary <NUM> channel is idle, and the first bit corresponds to the primary <NUM> channel. The second bit indicates whether the <NUM> channel corresponding to the second bit is idle. The second bit is any one of bits other than the first bit in the bandwidth mode indication field.

Implementation <NUM>-<NUM>: The bandwidth mode indication field occupies eight bits, the bandwidth mode indication field includes four first bits, two second bits, and two third bits, each of the four first bits corresponds to one <NUM> channel of the primary <NUM> channel, each of the two second bits corresponds to one <NUM> channel of the secondary <NUM> channel, and each of the two third bits corresponds to one <NUM> of the secondary <NUM> channel. The first bit indicates whether the <NUM> channel corresponding to the first bit is idle. The second bit indicates whether the <NUM> channel corresponding to the second bit is idle. The third bit indicates whether the <NUM> channel corresponding to the third bit is idle.

Implementation <NUM>-<NUM>: The bandwidth mode indication field occupies <NUM> bits, and the bandwidth mode indication field includes four first bits, two second bits, and four third bits. Each of the four first bits corresponds to one <NUM> channel of the primary <NUM> channel. Each of the two second bits corresponds to one <NUM> channel of the secondary <NUM> channel. Each of the four third bits corresponds to one <NUM> channel of the secondary <NUM> channel. The first bit indicates whether the <NUM> channel corresponding to the first bit is idle. The second bit indicates whether the <NUM> channel corresponding to the second bit is idle. The third bit indicates whether the <NUM> channel corresponding to the third bit is idle.

Implementation <NUM>-<NUM>: The bandwidth mode indication field occupies <NUM> bits, and the bandwidth mode indication field includes eight first bits and two second bits. Each of the eight first bits corresponds to one <NUM> channel of the primary <NUM> channel. Each of the two second bits corresponds to one <NUM> channel of the secondary <NUM> channel. The first bit indicates whether the <NUM> channel corresponding to the first bit is idle. The second bit indicates whether the <NUM> channel corresponding to the second bit is idle.

Based on the foregoing first frame, as shown in <FIG>, an embodiment of this application provides a bandwidth mode indication method.

S101: The transmit end generates the first frame.

The transmit end supports the <NUM>. 11be standard, or supports the next-generation <NUM> standard of the <NUM>. 11be standard. It may be understood that the transmit end may be backward compatible with a previous standard protocol, for example, support the <NUM>. 11ax standard and the <NUM>. 11ax standard before the <NUM>. 11ax standard. The transmit end may be an AP, or may be a STA.

The transmit end may determine a value of a related field (for example, the first field) in the first frame based on factors such as a requirement of the transmit end and a protocol supported by a peer device (namely, a receive end in the following).

For example, when the receive end supports the <NUM>. 11be standard, the transmit end may set the value of the first field in the first frame to the first preset value or the second preset value. When the receive end does not support the <NUM>. 11be standard, the transmit end can only set the value of the first field in the first frame to the first preset value. S102: The transmit end sends the first frame to the receive end, so that the receive end receives the first frame. S103: The receive end parses the first frame.

In this embodiment of this application, when the receive end learns, through parsing, that the value of the first field in the first frame is the second preset value, the receive end may determine that the transmit end of the first frame (namely, the transmit end) supports the <NUM>. 11be standard or the next-generation <NUM> standard.

Based on the technical solution shown in <FIG>, the first frame uses only at least one bit in the service field as the first field, and does not increase or decrease a bit in the service field. In this way, backward compatibility of the first frame is ensured. The first field indicates whether the bandwidth mode indication field carried in the first frame is allowed to indicate the target bandwidth mode. In other words, because the service field of the first frame includes the first field, the bandwidth mode indication field carried in the first frame extends a range of bandwidth modes that can be indicated. Therefore, in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, two devices can negotiate, by transmitting the first frame, to use one bandwidth mode from more bandwidth modes.

In this embodiment of this application, that the first field is located in the service field of the first frame has the following advantages: (<NUM>) Currently, a reserved bit in a MAC frame may be used by a chip vendor as a private indication bit. Therefore, if the reserved bit in the MAC frame is used as the first field, indication of the private bit is affected. However, using the bit in the service field as the first field can avoid affecting private use of the reserved bit in the MAC frame by the chip vendor. (<NUM>) Reserved bits in MAC frames of different types of conventional frames do not necessarily have the same location. Therefore, for the different types of transmission frames, implementation solutions of using the reserved bits in the MAC frames as the first field are different. The service field is a field introduced to perform a scrambling operation at a physical layer. The service field is located before the MAC frame, and the service field itself is a field at the physical layer, in other words, all types of conventional frames include the service field. In this way, using the bit in the service field as the first field is applicable to all types of conventional frames.

An embodiment of this application provides a second frame. The second frame is a non-HT duplicated frame or a non-HT frame, for example, an RTS frame or a CTS frame.

The second frame includes a service field. The service field carried in the second frame occupies <NUM> bits. In other words, compared with the non-HT duplicated frame or the non-HT frame defined in the <NUM>. 11n standard, no bit is added to or removed from the second frame provided in this application, so that the second frame has backward compatibility.

The service field of the second frame includes a second field, the second field indicates whether a bandwidth mode of the second frame is a target bandwidth mode, and the target bandwidth mode includes one or more of bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>.

Optionally, the target bandwidth mode includes a preamble puncturing bandwidth mode and/or a non-preamble puncturing bandwidth mode.

Optionally, the second field occupies at least one bit in B7 to B15 bits in the service field. For example, the second field occupies the B7 bit, a B11 bit, or the B15 bit in the service field.

In this embodiment of this application, that the second field indicates whether a bandwidth mode of the second frame is a target bandwidth mode includes the following case (<NUM>-<NUM>) or case (<NUM>-<NUM>).

(<NUM>-<NUM>): When the second field is set to a ninth preset value, the second field indicates that the bandwidth mode of the second frame is not the target bandwidth mode.

Based on the case (<NUM>-<NUM>), the first frame does not carry the bandwidth mode indication field, or the bandwidth mode indication field carried in the first frame indicates the bandwidth mode in the first bandwidth mode set. In this case, the bandwidth mode indication field carried in the first frame is implemented by using two bits (for example, the B5 bit and the B6 bit) in the first seven bits of the scrambling sequence. Bandwidth modes included in the first bandwidth mode set are <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>. For the correspondences between the values of the bandwidth mode indication field and the enumerated values of the bandwidth modes, refer to Table <NUM>. This is uniformly described herein, and details are not described below again.

(<NUM>-<NUM>): When the second field is set to a tenth preset value, the second field indicates that the bandwidth mode of the second frame is the target bandwidth mode.

Optionally, the second frame further includes a unicast/multicast bit, and the case (<NUM>-<NUM>) may be further classified into the following case (<NUM>-<NUM>-<NUM>) or case (<NUM>-<NUM>-<NUM>).

(<NUM>-<NUM>-<NUM>): When the second field is set to the tenth preset value and the unicast/multicast bit is set to <NUM>, the second field indicates that the bandwidth mode of the second frame is a first bandwidth mode.

(<NUM>-<NUM>-<NUM>): When the second field is set to the tenth preset value and the unicast/multicast bit is set to <NUM>, the second field indicates that the bandwidth mode of the second frame is a second bandwidth mode.

Both the first bandwidth mode and the second bandwidth mode belong to the target bandwidth mode, and the first bandwidth mode is different from the second bandwidth mode. For example, the first bandwidth mode is <NUM>, and the second bandwidth mode is <NUM>.

For example, when the second field is implemented by using one bit, the ninth preset value may be <NUM>, and the tenth preset value may be <NUM>; or the tenth preset value may be <NUM>, and the ninth preset value may be <NUM>.

Based on the foregoing second frame, as shown in <FIG>, an embodiment of this application provides a bandwidth mode indication method.

S201: The transmit end generates the second frame.

The transmit end supports the <NUM>. 11be standard, or supports the next-generation <NUM> standard of the <NUM>. 11be standard. It may be understood that the transmit end may be backward compatible with the previous standard protocol, for example, support the <NUM>. 11ax standard and the <NUM>. 11ax standard before the <NUM>. 11ax standard. The transmit end may be an AP, or may be a STA.

The transmit end may determine a value of a related field (for example, the second field) in the second frame based on factors such as the requirement of the transmit end and the protocol supported by the receive end.

S202: The transmit end sends the second frame to the receive end, so that the receive end receives the second frame.

S203: The receive end parses the second frame.

Based on the technical solution shown in <FIG>, the second frame uses only at least one bit in the service field as the second field, and does not increase or decrease a bit in the service field. In this way, backward compatibility of the second frame is ensured. In addition, the second field indicates whether the bandwidth mode of the second frame is the target bandwidth mode. Therefore, in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, two devices can negotiate, by transmitting the second frame, to use one bandwidth mode from more bandwidth modes.

For example, the first field or the second field may have another name, for example, an EHT bandwidth indication field. This is not limited in this embodiment of this application.

In this embodiment of this application, that the second field is located in the service field of the second frame has the following advantages: (<NUM>) Currently, a reserved bit in a MAC frame may be used by a chip vendor as a private indication bit. Therefore, if the reserved bit in the MAC frame is used as the second field, indication of the private bit is affected. However, using the bit in the service field as the second field can avoid affecting private use of the reserved bit in the MAC frame by the chip vendor. (<NUM>) Reserved bits in MAC frames of different types of conventional frames do not necessarily have the same location. Therefore, for the different types of transmission frames, implementation solutions of using the reserved bits in the MAC frames as the second field are different. The service field is a field introduced to perform a scrambling operation at a physical layer. The service field is located before the MAC frame, and the service field itself is a field at the physical layer, in other words, all types of conventional frames include the service field. In this way, using the bit in the service field as the second field is applicable to all types of conventional frames.

Currently, the transmit end sends an RTS frame after backoff is terminated. The transmit end may send the RTS frame in a non-HT duplicated manner. In the RTS frame, a CH_BANDWIDTH_IN_NON_HT field indicates a bandwidth mode, and a DYN_BANDWIDTH_IN_NON_HT field indicates a bandwidth negotiation mode.

The CH_BANDWIDTH_IN_NON_HT field is implemented by using the B5 bit and the B6 bit in the first seven bits of the scrambling sequence. The DYN_BANDWIDTH_IN_NON_HT field is implemented by using the B4 bit in the first seven bits of the scrambling sequence. When the DYN_BANDWIDTH_IN_NON_HT field is set to <NUM>, it indicates static bandwidth negotiation. When the DYN_BANDWIDTH_IN_NON_HT field is set to <NUM>, it indicates dynamic bandwidth negotiation.

After the receive end receives the RTS frame, when the DYN_BANDWIDTH_IN_NON_HT field is set to <NUM>, if an NAV indicates idle, and a bandwidth CCA detection result indicated by the RTS frame is idle, the receive end replies with a non-HT duplicated CTS frame by using a bandwidth indicated by the RTS frame.

After the receive end receives the RTS frame, when the DYN_BANDWIDTH_IN_NON_HT field is set to <NUM>, if the NAV indicates idle, and the bandwidth CCA detection result indicated by the RTS frame is that all or some channels (including the primary <NUM> channel) are idle, the receiving station replies with the non-HT duplicated CTS frame by using a bandwidth the same as or smaller than that of the RTS frame.

The Applicant finds that when the bandwidth mode indicated by the CH_BANDWIDTH_IN_NON_HT field in the RTS frame is <NUM>, regardless of whether the DYN_BANDWIDTH_IN_NON_HT field is set to <NUM> or <NUM>, the receive end uses the same processing manner: When the primary <NUM> channel is busy, the receive end does not reply with the CTS frame; and when the primary <NUM> channel is idle, the receive end replies with the CTS frame, and the CH_BANDWIDTH_IN_NON_HT field carried in the CTS frame indicates <NUM>.

It can be learned that for the RTS frame or the CTS frame defined in the current standard, when the CH_BANDWIDTH_IN_NON_HT field is set to <NUM>, the DYN_BANDWIDTH_IN_NON_HT field has a redundant state.

Based on this, an embodiment of this application provides a third frame. The third frame is a non-HT duplicated frame or a non-HT frame, for example, an RTS frame or a CTS frame.

The third frame includes a bandwidth negotiation field and a bandwidth mode indication field. The bandwidth negotiation field and the bandwidth mode indication field in the third frame jointly indicate a bandwidth mode of the third frame. The bandwidth mode of the third frame is <NUM>, <NUM>, <NUM>, <NUM>+<NUM> or <NUM>, or a first bandwidth mode. The first bandwidth mode is one of bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>, for example, <NUM>.

The bandwidth negotiation field occupies the B4 bit in the first seven bits of the scrambling sequence. The bandwidth mode indication field occupies the B5 bit and the B6 bit in the first seven bits of the scrambling sequence.

Optionally, that the bandwidth negotiation field and the bandwidth mode indication field jointly indicate a bandwidth mode used by the third frame includes the following cases:.

In this embodiment of this application, when the bandwidth negotiation field is set to <NUM>, it indicates that static bandwidth negotiation is used. When the bandwidth negotiation field is set to <NUM>, it indicates that dynamic bandwidth negotiation is used.

Based on the foregoing third frame, as shown in <FIG>, an embodiment of this application provides a bandwidth mode indication method.

S301: The transmit end generates the third frame.

The transmit end may determine values of the bandwidth negotiation field and the bandwidth mode indication field in the third frame based on factors such as the requirement of the transmit end and the protocol supported by the receive end.

For example, when the receive end supports the <NUM>. 11be standard or the next-generation <NUM> standard, the transmit end may set the bandwidth negotiation field in the third frame to <NUM>, and set the bandwidth mode indication field to <NUM>.

S302: The transmit end sends the third frame to the receive end, so that the receive end receives the third frame.

S303: The receive end parses the third frame.

Based on the technical solution shown in <FIG>, compared with the conventional technology in which a non-HT frame or a non-HT duplicated frame can negotiate to use one bandwidth mode in four bandwidth modes only by using a bandwidth mode indication field, the third frame provided in this application fully uses a redundant state in the bandwidth negotiation field and the bandwidth mode indication field to indicate a new bandwidth mode (the first bandwidth mode). Therefore, the bandwidth negotiation field and the bandwidth mode indication field in the third frame jointly indicate one of five bandwidth modes. In this way, the third frame is transmitted between two devices, and one of the five bandwidth modes can be used through negotiation. In addition, compared with the non-HT frame or the non-HT duplicated frame defined in the <NUM>. 11n standard, no bit is added to or removed from the third frame provided in this application. In this way, backward compatibility of the third frame is ensured.

After the bandwidths supported by the <NUM>. 11be standard are extended to <NUM>, the device can use more bandwidth modes. For the transmit end, an MU-RTS frame sent by the transmit end may use a user information field (user info field) of a special AID to carry the bandwidth mode indication field. In this way, the bandwidth mode indication field may occupy more bits (for example, <NUM> bits), so that the bandwidth mode indication field is applicable to a scenario in which there are more bandwidth modes in a communication system.

However, for the receive end, the CTS frame used to respond to the MU-RTS frame is a conventional frame, so that the CTS frame does not have sufficient idle bits for use by the bandwidth mode indication field. Therefore, the current CTS frame is not applicable to the scenario in which more bandwidth modes are introduced to the communication system.

To resolve this technical problem, an embodiment of this application provides a fourth frame. The fourth frame is used to respond to the MU-RTS frame or the RTS frame. Compared with a MAC frame that is of the current CTS frame and that occupies <NUM> bits, a MAC frame of the fourth frame occupies <NUM>+N bits, where N is a positive integer. One or more of the N bits indicates a bandwidth mode. The bandwidth mode may be a preamble puncturing bandwidth mode or a non-preamble puncturing bandwidth mode.

In this way, when the fourth frame includes all fields carried in the CTS frame, the fourth frame may further provide more idle bits to indicate the bandwidth mode, to indicate one bandwidth mode from the at least five bandwidth modes.

In this embodiment of this application, N is less than or equal to <NUM>. A specific reason is as follows:
Currently, the CTS frame is usually sent at a rate of <NUM> Mbps, and a length of one OFDM symbol is <NUM> microseconds, so that one OFDM symbol can transmit <NUM> bits (<NUM> Mbps*<NUM> microseconds) of data. Because one byte has eight bits, one OFDM symbol can transmit three bytes.

As shown in <FIG>, in addition to a preamble part that is also included in a non-HT frame, the CTS frame further includes a service field (<NUM> bytes), a frame control (frame control) field (<NUM> bytes), a duration (duration) field (<NUM> bytes), a receiver address (receiver address, RA) field (<NUM> bytes), a frame check sequence (frame check sequence, FCS) field (<NUM> bytes), and a tail (tail) (<NUM> bits). In other words, the CTS frame needs to use <NUM> bytes+<NUM> bits to carry the foregoing fields. Therefore, the CTS frame needs six OFDM symbols for transmission. It should be noted that, in the foregoing calculation process, a time period required for transmitting a physical frame header part is ignored, because the transmission time period of the physical frame header part is fixed for all non-HT frames.

A NAV reset mechanism based on RTS/CTS or MU-RTS/CTS interaction is supported in the current standard: If a station updates its NAV for the last time based on the RTS frame or MU-RTS frame and does not receive PHY-RXSTART. indication within NAVTimeout, the station may reset the NAV, in other words, ignore an update of the NAV by the RTS or MU-RTS. NAVTimeout is calculated from a time point at which a MAC layer receives a PHY-RXEND. indication primitive of the RTS or MU-RTS frame.

NAVTimeout is a fixed time length defined in the current standard, and is specifically equal to (<NUM>×aSIFSTime)+(CTS_Time)+aRxPHYStartDelay+(<NUM>×aSlotTime), where aSIFSTime=<NUM> microseconds, CTS_Time is transmission duration of the CTS frame, aRxPHYStartDelay is a physical layer receiving delay, and aSlotTime=<NUM> microseconds.

Because NAVTimeout is the fixed time length, to ensure normal execution of the NAV reset mechanism based on the RTS/CTS or MU-RTS/CTS interaction, transmission duration of the fourth frame should be consistent with transmission duration of the CTS frame. In other words, the fourth frame also needs six OFDM symbols for transmission. The six OFDM symbols can transmit a maximum of <NUM> bytes of data. Therefore, compared with the CTS frame, a maximum of <NUM> bits may be added to the fourth frame. In other words, N is less than or equal to <NUM>.

Optionally, N may be equal to <NUM>. In this way, the fourth frame may meet a rule of increasing a length of the MAC frame by an integer byte.

The following specifically describes the fourth frame by using an example in which N=<NUM>.

The MAC frame of the fourth frame occupies <NUM> bytes. As shown in <FIG>, a MAC frame of the fourth frame includes a frame control field, a duration field, a transmitter address field, a frame check sequence field, and a third field. The frame control field occupies two bytes, the duration field occupies two bytes, the transmitter address field occupies six bytes, the frame check sequence field occupies four bytes, and the third field occupies one byte.

A location of the third field in the fourth frame is not limited in this embodiment of this application. For example, the third field may also be located between the transmitter address field and the duration field.

In this embodiment of this application, K bits in the third field indicates a bandwidth mode of the fourth frame.

Optionally, the fourth frame further includes a service field, and the service field occupies <NUM> bits. The K bits in the third field and M bits in the service field jointly indicate the bandwidth mode of the fourth frame, where M is a positive integer.

For example, when K+M=<NUM>, that the K bits in the third field and the M bits in the service field jointly indicate the bandwidth mode of the fourth frame includes: Each of the <NUM> bits corresponds to one <NUM> channel, and a value of one bit indicates whether the <NUM> channel corresponding to the bit is idle. The foregoing <NUM> bits include the K bits in the third field and the M bits in the service field.

For example, the <NUM> bits may include eight bits in the third field and eight bits in the service field. The eight bits in the service field may be any eight of the last nine bits (namely, the B7 bit to the B15 bit) of the service field.

Optionally, when the M bits in the service field include a B0 bit to a B6 bit in the service field, it needs to be ensured that not all of the B0 bit to the B6 bit are set to <NUM>, to avoid that a scrambling process cannot work normally.

Based on the foregoing third frame, this application provides a bandwidth mode indication method.

S401: The transmit end generates the fourth frame.

For specific descriptions of the fourth frame, refer to the foregoing descriptions.

In a possible implementation, when the transmit end determines that the receive end supports the <NUM>. 11be standard or the next-generation <NUM> standard, the transmit end generates the fourth frame.

S402: The transmit end sends the fourth frame, so that the receive end receives the fourth frame.

S403: The receive end parses the fourth frame.

Based on the technical solution shown in <FIG>, compared with the existing CTS frame, the fourth frame has more idle bits that indicate bandwidth modes. In this way, in a scenario in which other bandwidth modes other than <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM> are introduced, the transmit end sends the third frame to the receive end, to use one bandwidth mode from more bandwidth modes.

The following mainly describes the solutions provided in embodiments of this application from a perspective of a communication apparatus. It may be understood that, to implement the foregoing functions, the communication apparatus includes corresponding hardware structures and/or software modules for performing the functions. A person of ordinary skill in the art should easily be aware that, in combination with the examples described in embodiments disclosed in this specification, modules, algorithms and steps may be implemented by hardware or a combination of hardware and computer software in this application. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraint conditions of the technical solutions.

In embodiments of this application, the apparatus may be divided into functional modules based on the foregoing method examples. For example, each functional module may be obtained through division based on a corresponding function, or two or more functions may be integrated into one functional module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module. In this embodiment of this application, module division is an example, and is merely a logical function division. In actual implementation, another division manner may be used. An example in which each function module is obtained through division based on each corresponding function is used below for description.

<FIG> shows a communication apparatus according to an embodiment of this application. The communication apparatus includes a processing module <NUM> and a communication module <NUM>.

In a possible manner, when the communication apparatus serves as a transmit end, the processing module <NUM> is configured to perform step S101 in <FIG>, and the communication module is configured to perform step S102 in <FIG>.

In another possible design, when the communication apparatus serves as the transmit end, the processing module <NUM> is configured to perform step S201 in <FIG>, and the communication module <NUM> is configured to perform step S202 in <FIG>.

In another possible design, when the communication apparatus serves as the transmit end, the processing module <NUM> is configured to perform step S301 in <FIG>, and the communication module <NUM> is configured to perform step S302 in <FIG>.

In another possible design, when the communication apparatus serves as the transmit end, the processing module <NUM> is configured to perform step S401 in <FIG>, and the communication module <NUM> is configured to perform step S402 in <FIG>.

In another possible design, when the communication apparatus serves as a receive end, the processing module <NUM> is configured to perform step S103 in <FIG>, and the communication module <NUM> is configured to perform step S102 in <FIG>.

In another possible design, when the communication apparatus serves as the receive end, the processing module <NUM> is configured to perform step S203 in <FIG>, and the communication module <NUM> is configured to perform step S202 in <FIG>.

In another possible design, when the communication apparatus serves as the receive end, the processing module <NUM> is configured to perform step S303 in <FIG>, and the communication module <NUM> is configured to perform step S302 in <FIG>.

In another possible design, when the communication apparatus serves as the receive end, the processing module <NUM> is configured to perform step S403 in <FIG>, and the communication module <NUM> is configured to perform step S402 in <FIG>.

<FIG> is a diagram of a structure of a possible product form of a communication apparatus according to an embodiment of this application.

In a possible product form, the communication apparatus in this embodiment of this application may be a communication device, and the communication device includes a processor <NUM> and a transceiver <NUM>. Optionally, the communication device further includes a storage medium <NUM>.

In a possible manner, when the communication device is used as a transmit end, the processor <NUM> is configured to perform step S101 in <FIG>, and the transceiver <NUM> is configured to perform step S102 in <FIG>.

In another possible design, when the communication device is used as the transmit end, the processor <NUM> is configured to perform step S201 in <FIG>, and the transceiver <NUM> is configured to perform step S202 in <FIG>.

In another possible design, when the communication device is used as the transmit end, the processor <NUM> is configured to perform step S301 in <FIG>, and the transceiver <NUM> is configured to perform step S302 in <FIG>.

In another possible design, when the communication device is used as the transmit end, the processor <NUM> is configured to perform step S401 in <FIG>, and the transceiver <NUM> is configured to perform step S402 in <FIG>.

In another possible design, when the communication device is used as a receive end, the processor <NUM> is configured to perform step S103 in <FIG>, and the transceiver <NUM> is configured to perform step S102 in <FIG>.

In another possible design, when the communication device is used as the receive end, the processor <NUM> is configured to perform step S203 in <FIG>, and the transceiver <NUM> is configured to perform step S202 in <FIG>.

In another possible design, when the communication device is used as the receive end, the processor <NUM> is configured to perform step S303 in <FIG>, and the transceiver <NUM> is configured to perform step S302 in <FIG>.

In another possible design, when the communication device is used as the receive end, the processor <NUM> is configured to perform step S403 in <FIG>, and the transceiver <NUM> is configured to perform step S402 in <FIG>.

It should be understood that the communication apparatus shown in <FIG> implements any function of the transmit end or the receive end in the solutions provided in embodiments of this application.

As a possible product form, the communication apparatus described in embodiments of this application may be implemented by using a chip. The chip includes a processing circuit <NUM> and a transceiver pin <NUM>. Optionally, the chip may further include a storage medium <NUM>.

In another possible product form, the communication apparatus described in embodiments of this application may alternatively be implemented by using the following circuit or component: one or more field programmable gate arrays (field programmable gate arrays, FPGA), programmable logic devices (programmable logic devices, PLD), controllers, state machines, gate logic, discrete hardware components, any other appropriate circuits, or any combination of circuits that can perform the functions described in this application.

It should be understood that computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium, a semiconductor medium (for example, a solid-state drive), or the like.

Based on the foregoing descriptions of the implementations, a person skilled in the art may clearly understand that for the purpose of convenient and brief descriptions, division into the foregoing functional modules is merely used as an example for descriptions. During an actual application, the foregoing functions can be allocated to different functional modules for implementation based on a requirement, in other words, an inner structure of an apparatus is divided into different functional modules to implement all or a part of the functions described above.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one or more physical units, may be located in one place, or may be distributed on different places.

When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a readable storage medium. Based on such an understanding, the technical solutions of embodiments of this application essentially, or the part contributing to the conventional technology, or all or some of the technical solutions may be implemented in the form of a software product. The software product is stored in a storage medium and includes several instructions for instructing a device (which may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or some of the steps of the methods described in embodiments of this application.

Claim 1:
A bandwidth mode indication method, wherein the method comprises:
generating a frame (S101), wherein the frame is a non-high throughput, non-HT, frame or a non-high throughput duplicated, non-HT duplicated, frame, the frame comprises a service field, the service field occupises <NUM> bits B0-B15, first seven bits B0-B6 of the service field carry a scrambling sequence, and the frame further comprises a unicast/multicast bit;
wherein the unicast/multicast bit indicates whether a bandwidth mode indication field carried in the frame indicates a bandwidth mode; and
when the unicast/multicast bit is set to <NUM> and a B7 bit of the service field is set to a first preset value, the bandwidth mode indication field carried in the frame indicates a bandwidth mode in a first bandwidth mode set, wherein the first bandwidth mode set comprises <NUM>, <NUM>, <NUM>, and <NUM>+<NUM> or <NUM>;
when the unicast/multicast bit is set to <NUM> and the B7 bit of the service field is set to a second preset value, the bandwidth mode indication field carried in the frame indicates a bandwidth mode in a second bandwidth mode set, wherein the second bandwidth mode set comprises a target bandwidth mode, and the target bandwidth mode comprises <NUM> or <NUM>+<NUM>;
when the unicast/multicast bit is set to <NUM>, the bandwidth mode indication field is not used to indicate the bandwidth mode; and
the method further comprises sending the frame (S102).