Communication methods and devices

Abstract

This invention provides a communication method and apparatus for reducing the power consumption of multilink devices, applicable to wireless local area network systems that support the IEEE 802.11ax next-generation Wi-Fi protocol, such as 802.11be or EHT, or other 802.11 series protocols. [Solution] The access point multilink device generates a first physical layer protocol data unit (PPDU). The first PPDU carries first instruction information, which indicates that the wake-up of the first access point in a dosed state is permitted, or that the wake-up of the first access point in a dosed state is not permitted. The access point multilink device transmits the first PPDU via the first access point.

Description

Technical Field

[0001]

[0001] Cross-reference to Related Applications This application claims priority to Chinese Patent Application No. 202210291249.7, entitled "Communication Method and Device", filed with the China National Intellectual Property Administration on March 23, 2022, and Chinese Patent Application No. 202210323888.7, entitled "Communication Method and Device", filed with the China National Intellectual Property Administration on March 29, 2022, and the entire contents of both are incorporated herein by reference in their entirety.

[0002]

[0002] Technical Field This application relates to the field of wireless communication technologies, and in particular, to communication methods and devices.

Background Art

[0003]

[0003] According to the provisions of the Institute of Electrical and Electronics Engineers (IEEE) 802.11be Draft, a multicast data frame needs to be replicated and transmitted on all links of an access point (AP) multi-link device (MLD), and a multicast management frame needs to be independently transmitted on the corresponding link of the AP MLD.

[0004]

[0004] However, in this method of transmitting multicast data frames and multicast management frames, all links of the AP MLD need to wake up periodically to receive the multicast data frames and multicast management frames buffered on the AP side, which is not conducive to power saving of the AP MLD. Therefore, in the related art, it has been proposed that the AP within the AP MLD can switch to the power-saving (Doze) state, and an activation request may be sent to wake up the AP in the Doze state.

[0005]

[0005] However, when the battery level is extremely low, the NSTR mobile AP MLD may not expect the AP of the NSTR mobile AP MLD to be activated. As a result, the control over the AP MLD in the related technology is not sufficiently flexible. [Overview of the Initiative]

[0006]

[0006] This application provides a communication method and apparatus for improving the flexibility of controlling an access point multilink device.

[0007]

[0007] According to a first aspect, a communication method is provided which includes the following process: an access point multilink device generates a first physical layer protocol data unit (PPDU), the first PPDU carries first instruction information, the first instruction information indicating that waking up of the first access point in a doze state is permitted, or the first instruction information indicating that waking up of the first access point in a doze state is not permitted; the access point multilink device transmits the first PPDU.

[0008]

[0008] The power state of the first access point may include an awake state and a doze state. The first access point can receive and transmit message packets in the awake state. Specifically, an access point multilink device can receive and transmit message packets through the first access point when it is in the awake state. The first access point cannot receive or transmit message packets in the doze state. Specifically, an access point multilink device cannot receive or transmit message packets through the first access point when it is in the doze state, which reduces the power consumption of the access point multilink device to which the first access point belongs.

[0009]

[0009] Optionally, the default state of power save mode is the dosed state. In other words, the first access point is in the dosed state by default in power save mode. Specifically, the first instruction information may indicate that the wake-up of the first access point in power save mode is permitted, or the first instruction information may indicate that the wake-up of the first access point in power save mode is not permitted.

[0010]

[0010] In the method, if a first access point in an access point multilink device is in a dosed state, the access point multilink device can use first instruction information of the first PPDU to indicate whether to allow the first access point in the dosed state to be woken up. If the first instruction information indicates that the first access point in the dosed state is allowed to be woken up, the first access point may be woken up. If the first instruction information indicates that the first access point in the dosed state is not allowed to be woken up, the first access point may remain in the dosed state. Thus, the flexibility of controlling the AP MLD can be improved.

[0011]

[0011] An access point multilink device includes one or more access points. Generally, at least one of the one or more access points is configured to receive and transmit message packets (e.g., control frames and / or data frames). For example, an access point multilink device includes a first access point and a second access point, and there may be one or more first access points. The first access point is in a dosed state (or power saving, where the default state in power saving mode is the dosed state), and the second access point is in an awake state (or active mode, where in active mode the second access point is always in an awake state).

[0012]

[0012] For example, the method may be carried out through interaction between an access point multilink device and a station multilink device. For example, the access point multilink device transmits a first PPDU to the station multilink device. If the first access point is in a dose state (or power saving mode), the access point multilink device transmits the first PPDU to the station multilink device via a second access point, which is in an awakened state.

[0013]

[0013] In a possible implementation, the first instruction information includes a wake-up enable field which indicates that waking up the first access point in a dosed state is permitted or that waking up the first access point in a dosed state is not permitted.

[0014]

[0014] The wake-up enable field may occupy one or more bits.

[0015]

[0015] For example, the wake-up enable field is added to the reduced neighbor report element, and the wake-up enable field occupies 1 bit. When bit 1 is set to 1, it indicates that the wake-up of the first access point in the Daze state is permitted. If bit 1 is set to 0, it indicates that the wake-up of the first access point in the Daze state is not permitted.

[0016]

[0016] Optionally, the wake-up enable field indicates whether the wake-up of the first access point in power-saving mode is permitted or not, and the default state of power-saving mode is the dose state.

[0017]

[0017] In a possible implementation, the first instruction information includes a power management mode field, which indicates the power management mode of the first access point.

[0018]

[0018] The power management mode field may occupy multiple bits.

[0019]

[0019] For example, the power management mode field is added to the reduced neighbor report element, and the power management mode field occupies 2 bits and indicates the power management mode of the first access point. In some power management modes, state switching of the first access point is permitted. For example, in a power management mode, the first access point in a dosed state is permitted to be woken up. In some power management modes, state switching of the first access point is not permitted. For example, in a power management mode, the first access point in a dosed state is not permitted to be woken up.

[0020]

[0020] In a possible implementation, if the power management mode field is set to a first value, it indicates that the first access point is in active mode. In this case, the first access point remains in an awake state and is not allowed to switch states.

[0021]

[0021] In a possible implementation, if the power management mode field is set to a second value, it indicates that the first access point is in power saving mode and that a state switch (e.g., switching from dose state to awake state, or from awake state to dose state) is permitted. In this case, the default state of the first access point is the dose state, and based on certain conditions, the first access point switches from the dose state to the awake state, or from the awake state to the dose state.

[0022]

[0022] For example, the conditions for switching from the dozed state to the awake state include, but are not limited to, one or more of the following: Determining that data exists to be transmitted or received, receiving wake-up requests, periodically waking up, etc. The conditions for switching from the awake state to the dozed state include, but are not limited to, one or more of the following: This includes determining that there is no data to be transmitted or received, receiving instructions indicating power saving, periodic power saving, or similar actions.

[0023]

[0023] In a possible implementation, if the power management mode field is set to a third value, it indicates that the first access point is in sleep mode. In this case, the first access point remains in a dosed state, no state switching is permitted, and the first access point is not permitted to be woken up.

[0024]

[0024] In a possible implementation, if the first instruction indicates that the wake-up of the first access point, which is in a dosed state, is permitted, the station multilink device can decide whether or not to wake up the first access point. For example, the station multilink device may decide to wake up the first access point if there is data to be transmitted, or it may decide not to wake up the first access point if there is no data to be transmitted.

[0025]

[0025] When it is determined to wake up the first access point, the station multi-link device can wake up the first access point by transmitting a second PPDU. For example, after the access point multi-link device transmits the first PPDU, the access point multi-link device may further receive the second PPDU transmitted by the station multi-link device, and the second PPDU carries second indication information, and the second indication information is used to wake up the first access point corresponding to one or more links.

[0026]

[0026] After receiving the second PPDU, the access point multi-link device can wake up the first access point corresponding to one or more links. Generally, one link corresponds to one access point.

[0027]

[0027] Optionally, if there is data to be transmitted between multiple station multi-link devices and the access point multi-link device, the access point multi-link device may receive the second PPDU transmitted by the multiple station multi-link devices.

[0028]

[0028] The second PPDU may reuse the existing frame structure or may be based on a newly defined frame structure.

[0029]

[0029] In this implementation, when the first access point is permitted to be woken up, the access point multi-link device wakes up the first access point based on the indication information transmitted by the station multi-link device, as a result, further power saving can be achieved, and the flexibility of control can be guaranteed.

[0030]

[0030] In a possible implementation, the second instruction information includes a link instruction field, which indicates the link to be activated. In this implementation, the link instruction field specifies the link to be activated and requests that the first access point corresponding to the link be woken up.

[0031]

[0031] For example, the link instruction field may be a Link Bitmap field.

[0032]

[0032] In a possible implementation, the second PPDU includes a control field, in which the second instruction information is carried, and the control field specifies the link to be activated. In this implementation, the control field specifies the link to be activated and requests that the first access point corresponding to the link be woken up.

[0033]

[0033] For example, the control field may be an access point support request control field, and the access point support request control field carries second instruction information.

[0034]

[0034] In possible implementations, the access point assistance request control field further carries third instruction information indicating that the access point assistance request control field is used to wake up a first access point (which is in a dozed state) of a designated access point multilink device.

[0035]

[0035] In related technologies, the access point assistance request control field is used to request an access point multilink device to send a trigger frame on the corresponding link. Therefore, in order to distinguish it from the meaning shown in related technologies, in this implementation, the third instruction information may indicate that the access point assistance request control field is used to wake up the first access point and improve control accuracy.

[0036]

[0036] In a possible implementation, the access point multilink device transmits a third PPDU to the station multilink device, the third PPDU indicating the first access point that has been successfully woken up. In this implementation, after waking up the first access point, the access point multilink device can notify the station multilink device that the first access point has been woken up.

[0037]

[0037] Optionally, the first access point that is ultimately activated and is indicated by the third PPDU may be all or part of the first access point that the second PPDU requests to wake up.

[0038]

[0038] For example, the frame format of the third PPDU may be the same as or different from the frame format of the second PPDU.

[0039]

[0039] In a possible implementation, the access point multilink device transmits a fourth PPDU on the woken link to the station multilink device, the fourth PPDU implies that the first access point corresponding to the link has been woken up. In this implementation, the access point multilink device can notify the station multilink device that the first access point has been woken up.

[0040]

[0040] For example, the fourth PPDU may be a trigger frame or a PS pole frame.

[0041]

[0041] Optionally, the access point that transmits the fourth PPDU may be all or part of the first access point that the second PPDU requests to wake up.

[0042]

[0042] In possible implementations, the access point multilink device can receive wake-up requests by default. Optionally, the access point multilink device can notify the corresponding wake-up delay to indicate that the first access point will switch from the dozed state to the awake state after the wake-up delay.

[0043]

[0043] The wake-up delay is related to the time required for the first access point to switch from the dozed state to the awake state after receiving a wake-up request.

[0044]

[0044] For example, the first PPDU includes a wake-up delay field, which indicates the delay for the first access point to switch from a dozed state to an awake state.

[0045]

[0045] In another example, an access point multilink device transmits a fifth PPDU, which includes a wake-up delay field. In response, a station multilink device receives the fifth PPDU.

[0046]

[0046] Optionally, a fifth PPDU may further include a power saving operation support field, which indicates whether a wake-up delay field is present.

[0047]

[0047] Optionally, the fifth PPDU may further include a mode switching count field, which indicates the remaining time for the first access point to switch from the current mode to the target mode. The remaining time may be expressed as the number of TBTTs for the corresponding link.

[0048]

[0048] The fifth PPDU may further include a power management information field, which carries a wake-up field and a mode switching count field. Optionally, the fifth PPDU may further include a seventh instruction information, which indicates whether the power management information field is present.

[0049]

[0049] In some scenarios, the access point multilink device can transmit a fifth PPDU when the first access point is in power saving mode.

[0050]

[0050] In a possible implementation, the first access point in power-saving mode receives a wake-up request from one or more station multilink devices. After receiving the wake-up request, the first access point switches from a dosed state to an awakened state, and may switch back to a dosed state under certain conditions to reduce power consumption.

[0051]

[0051] For example, one or more station multilink devices transmit fourth instruction information on the link on which the first access point is located.

[0052]

[0052] If all station multilink devices that send wake-up requests set the fourth instruction information of the last PPDU sent to the first access point by the station multilink devices to 0, the first access point can switch from the awake state to the dose state, thereby reducing power consumption.

[0053]

[0053] For example, the fourth instruction information is a more data field.

[0054]

[0054] In another example, when the channel is idle, the first access point can switch from the awake state to the dose state to reduce power consumption.

[0055]

[0055] In a possible implementation, the access point multilink device transmits a reduced neighbor report element in which the target beacon transmission time information set field corresponding to the first access point and within the reduced neighbor report element carries only the multilink device parameter field, and the corresponding target beacon transmission time information length is set to a first length value, so that the legacy station ignores the first access point. In this implementation, the access point multilink device carries only the multilink device parameter field, so that the legacy station ignores the first access point (or the first link corresponding to the first access point).

[0056]

[0056] In a possible implementation, the access point multilink device transmits a reduced neighbor report element in which the target beacon transmission time information field type field, which corresponds to the first access point and is within the reduced neighbor report element, is set to a fourth value, so that the legacy station ignores the first access point. In this implementation, the access point multilink device sets the target beacon transmission time information field type field to a fourth value (or sets the target beacon transmission time information field type field to a first type value), so that the legacy station ignores the first access point (or the first link corresponding to the first access point).

[0057]

[0057] In a possible implementation, the access point multilink device transmits a reduced neighbor report element in which the target beacon transmission time information set field corresponding to the first access point and located within the reduced neighbor report element carries only the multilink device parameter field, the corresponding target beacon transmission time information length is set to a first length value, and the corresponding target beacon transmission time information field type field is set to a fourth value, so that the legacy station ignores the first access point. In this implementation, the access point multilink device carries only the multilink device parameter field, so that the legacy station ignores the first access point (or the first link corresponding to the first access point).

[0058]

[0058] In a possible implementation, the access point multilink device transmits a sixth PPDU, the sixth PPDU carries fifth instruction information, the fifth instruction information indicates whether transmission outside the restricted target wake time (rTWT) service period (SP) is permitted or whether transmission outside the rTWT SP is not permitted. In this implementation, the fifth instruction information instructs that transmission and reception of data outside the rTWT SP is prohibited, and as a result, the station multilink device can further save energy by preventing it from transmitting data to the access point multilink device outside the SP.

[0059]

[0059] For example, the fifth instruction information may be a newly added Transmission allowed Out of TWT SP field, which may occupy one or more bits.

[0060]

[0060] In possible implementations, the first PPDU includes a power management mode field, which further indicates a periodic power saving mode. In this implementation, the periodic power saving mode is specified by default to not allow transmission outside the rTWT SP, which can further save energy.

[0061]

[0061] In a possible implementation, when the TWT protocol is set up between the first access point and the corresponding first station, the first access point of the access point multilink device switches to an awake state before the TWT SP. In this implementation, the first access point automatically wakes up when in power saving mode, and the first station does not need to send a wake-up request. The power management mode here does not need to be set to a periodic power saving mode.

[0062]

[0062] According to a second embodiment, a communication method is provided which includes the following process: A station multilink device receives a first PPDU, the first PPDU carries first instruction information, the first instruction information indicates that the wake-up of the first access point in a dosed state is permitted, or the first instruction information indicates that the wake-up of the first access point in a dosed state is not permitted; and the station multilink device also determines whether to wake up the first access point.

[0063]

[0063] For example, if there is data to be transmitted or received, the station multilink device decides to wake up the first access point; or, if there is no data to be transmitted or received, the station multilink device decides not to wake up the first access point.

[0064]

[0064] In a possible implementation, the first instruction information includes a wake-up enable field, which indicates whether the wake-up of the first access point in a dosed state is permitted or not.

[0065]

[0065] In a possible implementation, the first instruction information includes a power management mode field, which indicates the power management mode of the first access point.

[0066]

[0066] In a possible implementation, if the power management mode field is a first value, it indicates that the first access point operates in active mode, the state of the first access point remains awake, and state switching is not permitted.

[0067]

[0067] In a possible implementation, if the power management mode field is a second value, it indicates that the first access point operates in power saving mode and state switching is permitted. For example, after receiving a wake-up request, the first access point switches from a dosed state to an awake state and, if certain conditions are met, switches back from the awake state to the dosed state.

[0068]

[0068] In a possible implementation, if the power management mode field is a third value, it indicates that the first access point operates in sleep mode and the state of the first access point remains in the dose state, and state switching is not permitted and the first access point is not permitted to be woken up.

[0069]

[0069] In a possible implementation, the first instruction information indicates that the first access point, which is in a dozed state, is permitted to be woken up.

[0070]

[0070] After the station multilink device has decided whether to allow the first access point to wake up, the station multilink device may further transmit a second PPDU, the second PPDU carrying a second instruction information, the second instruction information is used to wake up the first access point corresponding to one or more links.

[0071]

[0071] In a possible implementation, the station multilink device may further receive a seventh PPDU transmitted by the access point multilink device, the seventh PPDU carrying sixth instruction information, the sixth instruction information is used to wake up the first station corresponding to one or more links.

[0072]

[0072] In possible implementations, the second or sixth instruction information includes a link instruction field, which indicates the link to be woken up.

[0073]

[0073] In possible implementations, the second PPDU or the seventh PPDU includes a control field, and the second instruction information or the sixth instruction information is carried in the control field.

[0074]

[0074] In possible implementations, the control field is an access point support request control field, and the access point support request control field carries the second instruction information or the sixth instruction information.

[0075]

[0075] In possible implementations, the access point assistance request control field further carries third instruction information, which indicates that the access point assistance request control field is used to wake up a first access point that is in a dosed state and located in a specified access point multilink device.

[0076]

[0076] In a possible implementation, the station multilink device receives a third PPDU, which indicates the first access point that has been woken up.

[0077]

[0077] In a possible implementation, the station multilink device receives a fourth PPDU on the woken link, and the fourth PPDU indicates that the first access point corresponding to the link is being woken up.

[0078]

[0078] In a possible implementation, the first PPDU includes a wake-up delay field, which indicates the delay for the first access point to switch from a dozed state to an awake state.

[0079]

[0079] In a possible implementation, the station multilink device receives a fifth PPDU, the fifth PPDU includes a wake-up delay field.

[0080]

[0080] In possible implementations, a fifth PPDU may further include a power saving operation support field, which indicates whether a wake-up delay field is present.

[0081]

[0081] In a possible implementation, the first access point in power-saving mode is woken up by one or more station multilink devices. The station multilink devices may further transmit a fourth instruction, which is set to 0 to indicate that the station corresponding to the first access point has no data to transmit, and as a result the first access point of the access point multilink device switches back to a dose state, reducing power consumption.

[0082]

[0082] In possible implementations, the fourth instruction information is the information indicated by the More Data field.

[0083]

[0083] In a possible implementation, the station multilink device receives a reduced neighbor report element in which the target beacon transmission time information set field, which corresponds to the first access point and is located within the reduced neighbor report element, carries a multilink device parameter field in which the target beacon transmission time information length is set to a first length value, and as a result the legacy station ignores the first access point.

[0084]

[0084] In a possible implementation, the station multilink device receives a reduced neighbor report element in which the target beacon transmission time information field type corresponding to the first access point and located within the reduced neighbor report element is set to a first type value, so that the legacy station ignores the first access point.

[0085]

[0085] In a possible implementation, the station multilink device receives a reduced neighborhood report element in which the target beacon transmission time information set field corresponding to the first access point and located within the reduced neighborhood report element carries a multilink device parameter field in which the target beacon transmission time information length is set to a first length value and the corresponding target beacon transmission time information field type is set to a first type value, so that the legacy station ignores the first access point.

[0086]

[0086] According to a third embodiment, a communication device is provided. The communication device may be the aforementioned access point multilink device or station multilink device, or may be a chip located on the access point multilink device or station multilink device. The communication device can implement the method in any one of the embodiments described above.

[0087]

[0087] The communication device includes a processing unit and a transceiver unit.

[0088]

[0088] When the communication device is an access point multilink device, for example, the processing unit is configured to generate a first PPDU, the first PPDU carrying first instruction information, the first instruction information indicating that the wake-up of the first access point in a dosed state is permitted, or the first instruction information indicating that the wake-up of the first access point in a dosed state is not permitted; and the transceiver unit is configured to transmit the first PPDU.

[0089]

[0089] In a possible implementation, the first instruction information includes a wake-up enable field, which indicates that the wake-up of the first access point in a dosed state is permitted, or that the wake-up of the first access point in a dosed state is not permitted.

[0090]

[0090] In a possible implementation, the first instruction information includes a power management mode field which indicates whether the first access point in a dosed state is permitted to be woken up or whether the first access point in a dosed state is not permitted to be woken up.

[0091]

[0091] In possible implementations, the power management mode field further indicates that the first access point is in active mode, and / or the power management mode field further indicates that the first access point is in sleep mode.

[0092]

[0092] In a possible implementation, the first instruction information indicates that the first access point, which is in a dozed state, is permitted to be woken up.

[0093]

[0093] The transceiver unit is further configured to receive a second PPDU transmitted by the station multilink device, the second PPDU carrying second instruction information, the second instruction information is used to wake up the first access point corresponding to one or more links.

[0094]

[0094] In possible implementations, the second instruction information includes a link instruction field, which indicates the link to be woken up; or the second instruction information includes identifiers of a plurality of station multilink devices and a link instruction field corresponding to the identifier of each station multilink device; or the second instruction information is carried in a control field, which indicates the link to be woken up.

[0095]

[0095] In possible implementations, multiple station multilink devices correspond to the same multicast address or the same broadcast address.

[0096]

[0096] In a possible implementation, the second PPDU includes a control field, which carries the second instruction information.

[0097]

[0097] In possible implementations, the control field is an access point support request control field, and the access point support request control field carries second instruction information.

[0098]

[0098] In a possible implementation, the access point assistance request control field carries third instruction information indicating that the access point assistance request control field is used to wake up a first access point in a designated access point multilink device.

[0099]

[0099] In a possible implementation, the transceiver unit is further configured to transmit a third PPDU to a station multilink device, the third PPDU indicating the first access point that has been woken up.

[0100]

[0100] In a possible implementation, the transceiver unit is further configured to transmit a fourth PPDU to the station multilink device on the woken link, the fourth PPDU indicating that the first access point corresponding to the link has been woken up.

[0101]

[0101] In a possible implementation, the first PPDU includes a wake-up delay field, which indicates the delay for the first access point to switch from a dozed state to an awake state.

[0102]

[0102] In a possible implementation, the transceiver unit is further configured to transmit a fifth PPDU, the fifth PPDU including a wake-up delay field.

[0103]

[0103] In possible implementations, the fifth PPDU further includes a power saving operation support field, which indicates whether a wake-up delay field is present.

[0104]

[0104] In a possible implementation, the first access point in power-saving mode is woken up by one or more station multilink devices.

[0105]

[0105] The processing unit is further configured to switch the first access point from an awake state to a dose state when a fourth instruction information transmitted by one or more station multilink devices is received and the fourth instruction information is set to 0.

[0106]

[0106] In possible implementations, the fourth instruction information is the information indicated by the More Data field.

[0107]

[0107] In possible implementations, the processing unit is further configured to switch the first access point from an awake state to a dozed state when the channel is idle.

[0108]

[0108] In a possible implementation, the transceiver unit is further configured to transmit a reduced neighborhood report element, where the target beacon transmission time information set field corresponding to the first access point and located within the reduced neighborhood report element carries a multilink device parameter field, and the target beacon transmission time information length is set to a first length value, so that the legacy station ignores the first access point.

[0109]

[0109] In a possible implementation, the transceiver unit is further configured to transmit a reduced neighborhood report element, where the target beacon transmission time information field type corresponding to the first access point and located within the reduced neighborhood report element is set to a first type value, so that the legacy station ignores the first access point.

[0110]

[0110] In a possible implementation, the transceiver unit is further configured to transmit a sixth PPDU, the sixth PPDU carrying a fifth instruction information, the fifth instruction information indicating that transmission is permitted outside of the service period or that transmission is not permitted outside of the service period.

[0111]

[0111] In possible implementations, the first PPDU includes a power management mode field, which further indicates a periodic power saving mode.

[0112]

[0112] If the communication device is a station multilink device, for example, a transceiver unit is configured to receive a first physical layer protocol data unit (PPDU) which carries first instruction information, which indicates that the wake-up of the first access point in a dosed state is permitted, or that the wake-up of the first access point in a dosed state is not permitted; and a processing unit is configured to determine whether to wake up the first access point.

[0113]

[0113] In a possible implementation, the first instruction information includes a wake-up enable field, which indicates that the wake-up of the first access point in a dosed state is permitted, or that the wake-up of the first access point in a dosed state is not permitted.

[0114]

[0114] In possible implementations, the first instruction information includes a power management mode field which indicates whether the first access point in a dosed state is permitted to be woken up or whether the first access point in a dosed state is not permitted to be woken up.

[0115]

[0115] In possible implementations, the power management mode field notifies the first access point to switch to awake mode, and / or the power management mode field notifies the first access point to switch to dose mode.

[0116]

[0116] In a possible implementation, the first instruction information indicates that the first access point, which is in a dozed state, is permitted to be woken up.

[0117]

[0117] The transceiver unit is further configured to transmit a second PPDU, the second PPDU carrying a second instruction information, which is used to wake up a first access point corresponding to one or more links.

[0118]

[0118] In possible implementations, the second instruction information includes a link instruction field, which indicates the link to be woken up; or the second instruction information includes identifiers for a plurality of station multilink devices and a link instruction field corresponding to the identifier for each station multilink device; or the second instruction information is carried within a control field, which indicates the link to be woken up.

[0119]

[0119] In possible implementations, multiple station multilink devices correspond to the same multicast address or the same broadcast address.

[0120]

[0120] In possible implementations, the second PPDU includes a control field, which carries the second instruction information.

[0121]

[0121] In possible implementations, the control field is an access point support request control field, and the access point support request control field carries second instruction information.

[0122]

[0122] In possible implementations, the access point support request control field further carries third instruction information indicating that the access point support request control field is used to wake up a first access point in a designated access point multilink device.

[0123]

[0123] In a possible implementation, the transceiver unit is further configured to receive a third PPDU, which indicates the first access point that has been woken up.

[0124]

[0124] In a possible implementation, the transceiver unit is further configured to receive a fourth PPDU on the woken link, the fourth PPDU indicating that the first access point corresponding to the link has been woken up.

[0125]

[0125] In a possible implementation, the first PPDU includes a wake-up delay field, which indicates the delay for the first access point to switch from a dozed state to an awake state.

[0126]

[0126] In a possible implementation, the transceiver unit is further configured to receive a fifth PPDU, the fifth PPDU including a wake-up delay field.

[0127]

[0127] In possible implementations, the fifth PPDU further includes a power saving operation support field, which indicates whether a wake-up delay field is present.

[0128]

[0128] In a possible implementation, a first access point in power-saving mode is woken up by one or more station multilink devices; and a transceiver unit is further configured to transmit a fourth instruction, which is set to 0, indicating that the corresponding station has no data to transmit.

[0129]

[0129] In possible implementations, the fourth instruction information is the information indicated by the More Data field.

[0130]

[0130] In possible implementations, the transceiver unit is configured to receive a reduced neighborhood report element, where the target beacon transmission time information set field corresponding to the first access point and located within the reduced neighborhood report element carries a multilink device parameter field, and the target beacon transmission time information length is set to a first length value, so that the legacy station ignores the first access point; or, the transceiver unit is further configured to receive a reduced neighborhood report element, where the target beacon transmission time information field type corresponding to the first access point and located within the reduced neighborhood report element is set to a first type value, so that the legacy station ignores the first access point.

[0131]

[0131] In a possible implementation, the transceiver unit is further configured to receive a sixth PPDU, the sixth PPDU carrying a fifth instruction information, the fifth instruction information indicating that transmission is permitted outside of service hours or that transmission is not permitted outside of service hours.

[0132]

[0132] In possible implementations, the first PPDU includes a power management mode field, which further indicates a periodic power saving mode.

[0133]

[0133] According to a fourth aspect, a communication device is provided which includes a processor configured to perform the method in any one of the above aspects.

[0134]

[0134] Optionally, the device further includes memory, which stores instructions, and the processor executes the instructions in memory, thereby performing one of the methods described above.

[0135]

[0135] Optionally, the memory may be located inside or outside the device.

[0136]

[0136] Optionally, the device further includes an interface circuit, and the processor is coupled to the interface circuit.

[0137]

[0137] Optionally, it has one or more processors and one or more memory.

[0138]

[0138] Optionally, the memory may be integrated with the processor, or the memory and processor may be located separately.

[0139]

[0139] In a particular implementation process, the memory may be non-transitory memory, such as read-only memory (ROM). The memory and processor may be integrated on a single chip or located separately on different chips. The type of memory and the arrangement of the memory and processor are not limited to the embodiments of this application.

[0140]

[0140] The communication device may be a chip, and the processor may be implemented using hardware or using software. When the processor is implemented using hardware, the processor may be a logic circuit, an integrated circuit, etc. When the processor is implemented using software, the processor may be a general-purpose processor and is implemented by reading software code stored in memory. The memory may be integrated into the processor or may be located outside the processor and exist independently.

[0141]

[0141] According to a fifth aspect, a processor is provided which includes an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method in any one of the above aspects.

[0142]

[0142] In a particular implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, etc. The input signal received by the input circuit may be, for example, received and input by a receiver, but is not limited thereto. The signal output by the output circuit may be, for example, output to a transmitter and transmitted by the transmitter, but is not limited thereto. The input circuit and the output circuit may be the same circuit, and the circuit may be configured as an input circuit and an output circuit at different points in time. The specific implementation of the processor and various circuits is not limited to the embodiments of this application.

[0143]

[0143] According to a sixth aspect, a computer program product is provided. The computer program product includes a computer program (which may be referred to as code or instructions) and when the computer program is executed, the computer is able to perform the method in any one of the preceding aspects.

[0144]

[0144] According to a seventh aspect, a computer-readable medium is provided. The computer-readable medium stores a computer program (which may be referred to as code or instructions). When the computer program is executed on a computer, the computer is able to perform the method in any one of the aforementioned aspects.

[0145]

[0145] According to the eighth aspect, a chip system is provided. The chip system includes a processor and interfaces configured to support a communication device when performing the functions of any one of the preceding aspects. In a possible design, the chip system further includes memory. The memory is configured to store information and data necessary for the communication device. The chip system may include a chip, or it may include a chip and other discrete components.

[0146]

[0146] According to the ninth aspect, a functional entity is provided. The functional entity is configured to carry out the method in any one of the aforementioned aspects.

[0147]

[0147] According to the tenth aspect, a communication system is provided which includes an access point multilink device according to the first aspect and a station multilink device according to the second aspect.

[0148]

[0148] For the technical effects brought about by any one of the implementations in the second through tenth aspects, please refer to the technical effects brought about by the first aspect. Further details will not be explained again.

[0149]

[0149] It should be noted that the communication methods provided in the first and second embodiments may be used separately or in combination. This is not limited to the present invention. [Brief explanation of the drawing]

[0150] [Figure 1]

[0150] Figure 1 is a diagram of a multilink device. [Figure 2]

[0151] Figure 2 is a diagram of the structure of the communication system. [Figure 3]

[0152] Figure 3 is a diagram of the structure of the communication system. [Figure 4]

[0153] Figure 4 is a diagram of the communication process according to the embodiment of the present application. [Figure 5]

[0154] Figure 5 shows the frame structure of a reduced neighbor report element according to an embodiment of the present application. [Figure 6]

[0155] Figure 6 shows the frame structure of a reduced neighbor report element according to an embodiment of the present application. [Figure 7A]

[0156] Figure 7A shows the frame structure of a reduced neighbor report element according to an embodiment of the present application. [Figure 7B]

[0157] Figure 7B shows the frame structure of a reduced neighbor report element according to an embodiment of the present application. [Figure 8]

[0158] Figure 8 shows the format of the access point assistance request control field according to an embodiment of the present application. [Figure 9]

[0159] Figure 9 shows the format of the access point assistance request control field according to the embodiment of the present application. [Figure 10]

[0160] Figure 10 shows a unicast TWT according to an embodiment of the present application. [Figure 11]

[0161] Figure 11 shows the format of a broadcast TWT element according to an embodiment of the present application. [Figure 12]

[0162] Figure 12 shows the frame structure of a multi-link element according to an embodiment of the present application. [Figure 13A]

[0163] Figure 13A shows the format of the Presence Bitmap field according to an embodiment of the present application. [Figure 13B]

[0164] Figure 13B is a diagram illustrating the format of a Multi-Link Control field according to an embodiment of the present application. [Figure 13C]

[0165] Figure 13C is a diagram illustrating the format of the Power Management Information field according to an embodiment of the present application. [Figure 13D]

[0166] Figure 13D is a diagram of the format of the common information field according to the embodiment of the present application. [Figure 13E]

[0167] Figure 13E is a diagram showing the format of the STA information field according to the embodiment of the present application. [Figure 13F]

[0168] Figure 13F is a diagram showing the format of the STA control field according to an embodiment of the present application. [Figure 14]

[0169] Figure 14 shows the frame structure of a reduced neighbor report element according to an embodiment of the present application. [Figure 15]

[0170] Figure 15 shows the frame structure of the Target Beacon Transmission Time (TBTT) information field according to the embodiment of the present application. [Figure 16]

[0171] Figure 16 shows the frame structure of the Basic Service Set Parameter (BSS Parameter) field according to an embodiment of the present application. [Figure 17]

[0172] Figure 17 is a diagram showing the structure of a communication device according to an embodiment of the present application. [Figure 18]

[0173] Figure 18 is a diagram showing the structure of a communication device according to an embodiment of the present application. [Figure 19]

[0174] Figure 19 is a diagram showing the structure of a communication device according to an embodiment of the present application. [Modes for carrying out the invention]

[0151]

[0175] The technical solution of this application will be explained below with reference to the attached drawings.

[0152]

[0176] The technical solutions in the embodiments of this application may be applicable to various communication systems, such as wireless local area network (WLAN) communication systems, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, 5th generation (5G) systems, new radio (NR), and future 6th generation (6G) systems.

[0153]

[0177] For example, embodiments of the present application may be applied to a WLAN system, and any protocol in the IEEE 802.11 series protocols used by the WLAN, such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bf, and future 802.11 protocols, is applicable to embodiments of the present application. The methods provided in the present application may be implemented by a communication device in a wireless communication system, or by a chip or processor within the communication device. Accordingly, the communication device supports communication using the IEEE 802.11 series protocols. While the embodiments of this application are primarily described using a network deployed with IEEE 802.11 as an example, it will be readily apparent to those skilled in the art that the embodiments of this application may be extended to other networks using various standards or protocols, such as Bluetooth, high-performance radio local area networks (LANs) (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard mainly used in Europe), wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other networks that are known or will be developed later. Accordingly, the various embodiments provided in this application are applicable to any suitable wireless network, regardless of the coverage and wireless access protocols used.

[0154]

[0178] WLANs can operate in both low-frequency and high-frequency bands. Low-frequency bands include sub-1 gigahertz (GHz), 2.4 GHz, 5 GHz, and 6 GHz, while high-frequency bands include 60 GHz. 802.11ax (Wi-Fi 6) and earlier multi-band wireless fidelity (Wi-Fi) are configured using multiple links, each typically setting up a different basic service set (BSS), and communication can be performed on only one link at a time with stations within the BSS to which that link belongs. The operation across links lacks sufficient coordination.

[0155]

[0179] The IEEE 802.11 Next Generation Wi-Fi Extremely High Throughput (EHT) protocol utilizes a new ultra-large bandwidth in the 6 GHz frequency band to transmit information packets, and multiple discontinuous links can also be aggregated to form this ultra-large bandwidth using multi-link coordination techniques. Devices capable of implementing multi-link coordination techniques are called multi-link devices (MLDs). MLDs include access point (AP) MLDs and / or non-AP MLDs. For example, a non-AP MLD may be a station (STA) MLD. An MLD may have multiple radio frequency modules operating on different frequency bands, channels, or links. For example, the frequency bands on which an MLD operates may be all or part of sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high-frequency 60 GHz, but are not limited to these. An MLD includes one or more affiliated stations, where a station may be an AP or STA. Each affiliated station has its own media access control (MAC) address. As shown in Figure 1, STA1 has its own low MAC address, i.e., link address 1, and STA2 has its own low MAC address, i.e., link address 2. The MLD also has a high MAC address, i.e., the MLD MAC address.

[0156]

[0180] MLDs have the potential to aggregate larger bandwidths and, using multilink coordination techniques, can, for example, share the MAC layer across multiple links to flexibly transmit message packets or send message packets of the same service to the same station simultaneously. AP MLDs can set up associations with non-AP MLDs on a single link and quickly perform association setups on multiple links.

[0157]

[0181] Figure 2 is a diagram of the architecture of a communication system to which the embodiments of this application are applicable. The communication system includes one or more AP MLDs and one or more non-AP MLDs. The AP MLDs include AP1 and AP2, and the non-AP MLDs include STA1 and STA2. Optionally, the communication system may further include one or more Legacy STAs. The communication system shown in the embodiments of this application is merely an example for illustrative purposes, and the communication systems to which this application is applicable are not limited thereto. This is uniformly described here, and further details are not described again below.

[0158]

[0182] As shown in Figure 3, AP MLD includes AP1 and AP2.

[0159] AP1 includes the AP1 PHY, AP1 lower MAC, and upper MAC. AP2 includes the AP2 PHY, AP2 lower MAC, and upper MAC. AP1 and AP2 share the upper MAC. Non-AP MLDs include STA1 and STA2.

[0160] STA1 includes the STA1 PHY, STA1 lower MAC, and upper MAC. STA2 includes the STA2 PHY, STA2 lower MAC, and upper MAC. STA1 and STA2 share the upper MAC, AP1 and STA1 are connected via link 1, and AP2 and STA2 are connected via link 2.

[0161]

[0183] When multiple links are set up, the non-AP MLD sends an Association Request frame on link 1, which carries the STA-side information for link 1 and the STA-side information for link 2. The Association Request frame may also carry a Multi-link Element, which is used to carry information about the MLD and information about stations within the MLD. The AP MLD sends an Association Response frame on link 1, which carries the AP-side information for link 1 and the AP-side information for link 2. In this way, STA1 and STA2 of the non-AP MLD establish associations with AP1 and AP2 of the AP MLD, respectively. The link used to exchange association request / response frames (Link 1) is referred to as the transmitted link, and the other link (Link 2) is referred to as the non-transmitted link.

[0162]

[0184] Before multiple links are set up, the STA can detect the presence of the AP using an active or passive scanning method, associate with the AP to set up the connection, and then perform the setup of multiple links. It is easy to understand that the purpose of associating the STA with the AP and setting up the connection is to set up one or more links (for example, Link 1 and Link 2 in Figure 2) used for communication between the STA and the AP.

[0163]

[0185] In a passive scanning process, the STA can receive management frames (e.g., beacon frames or broadcast probe response frames) transmitted by the AP on a channel. For example, the STA can search for beacon frames transmitted by the AP by jumping across various channels. Once the STA obtains management information from the AP through the beacon frames, the STA can further communicate with the AP through probe request frames or probe response frames to obtain other information from the AP.

[0164]

[0186] In the active scanning process, the STA can actively broadcast a probe request frame if no beacon frame is detected through listening. After receiving the probe request frame, if certain conditions (which are not limited to the embodiments of this application) are met, the AP can initiate random channel access to reply with a probe response frame.

[0165]

[0187] To support STA's high-speed scanning, APs can carry a Reduced Neighbor Report Element within their beacon frame or probe response frame to report relevant information about the corresponding AP. In this way, during scanning, the STA can obtain information about nearby APs and select the appropriate AP for association, resulting in the STA not having to continuously scan channels and thus reducing the STA's scan time. According to 802.11 be, an affiliated AP must carry information about another affiliated AP belonging to the same AP MLD as its affiliated AP in its Reduced Neighbor Report Element. In the case of an STA, a nearby AP refers to an AP near the STA, and in the case of an AP, a nearby AP refers to an AP near the AP.

[0166]

[0188] Two MLDs (e.g., an AP MLD and a non-AP MLD) can communicate with each other over a setup link (e.g., Link 1 and Link 2). If the channel spacing between the two radio frequency modules in the MLD is sufficiently large, the links corresponding to the two radio frequency modules can operate independently and do not interfere with each other. If the two links in the MLD support transmitting data on one link and receiving data on the other link simultaneously, then the two links support simultaneous transmit and receive (STR). Otherwise, the two links support non-transmittable STR.

[0167]

[0189] The implementation of AP MLD is NSTR mobile AP MLD. According to the 802.11 be protocol, NSTR mobile AP MLD does not support STR (i.e., it normally supports NSTR), while another type of AP MLD supports STR. NSTR mobile AP MLD can implement the functions of AP MLD in non-AP MLD by using software. In some scenarios, a mobile phone may be configured as an NSTR mobile AP MLD to enable association with another device. For an NSTR link pair in an NSTR mobile AP MLD, one link may be defined as the Primary Link and the other as the Non-primary Link. The AP corresponding to the Primary Link is called the Primary AP, and the AP corresponding to the Non-primary Link is called the Non-primary AP. Non-primary APs are not permitted to send Beacon frames and reply with Probe Response frames, which can prevent legacy STAs from being associated with non-primary APs. Non-AP MLDs can carry relevant information about the non-primary link over the primary link in order to perform operations using the non-primary link.

[0168]

[0190] To reduce MLD power consumption and implement MLD power saving, stations such as non-primary APs may be dosed when not needed, and stations in a dosed state can be woken up by using a wake-up request. However, in some cases, for example, if an NSTR mobile AP MLD is at a very low battery level and operating in low battery level mode, the NSTR mobile AP MLD may not want to be woken up. Therefore, embodiments of the present application provide a communication method to indicate whether an access point in a dosed state is permitted to be woken up.

[0169]

[0191] Figure 4 shows a communication method according to an embodiment of the present application. The method includes the following steps.

[0170]

[0192] S401: An access point multilink device (hereinafter referred to as AP MLD) generates a first PPDU. The first PPDU carries first instruction information, which indicates that a first access point (hereinafter referred to as AP) in a dosed state is permitted to be woken up, or that a first AP in a dosed state is not permitted to be woken up.

[0171]

[0193] Generally, the power state of an AP (Access Point) includes either an awake state or a doze state. In possible cases, in power save mode (PS mode), the AP can switch between the awake state and the doze state, and the default state in power save mode is the doze state. Unless otherwise specified, the power state in power save mode is the doze state.

[0172]

[0194] S402:AP MLD sends the first PPDU.

[0173]

[0195] Optionally, the AP MLD includes a first AP and a second AP, where the first AP is in a dozed state and the second AP is in an awake state, and the AP MLD can transmit the first PPDU through the second AP.

[0174]

[0196] For example, the AP MLD transmits a first PPDU to a station multilink device (hereinafter referred to as a non-AP MLD or STA MLD). In response, the non-AP MLD receives the first PPDU and, based on the first PPDU, decides whether to wake up the first AP.

[0175]

[0197] In the implementation, if the first instruction indicates that waking up the first AP while it is in a dosed state is not permitted, the non-AP MLD decides not to wake up the first AP. If the first instruction indicates that waking up the first AP while it is in a dosed state is permitted, the non-AP MLD may decide whether to wake up the first AP based on whether there is data to be sent or received. For example, if there is data to be sent or received, the non-AP MLD decides to wake up the first AP; or if there is no data to be sent or received, the non-AP MLD decides not to wake up the first AP. It should be understood that this is merely an example of how the non-AP MLD decides whether to wake up the first AP.

[0176]

[0198] In the aforementioned solution, if the first AP in the AP MLD is in a dosed state, the AP MLD can use the first instruction information of the first PPDU to indicate whether to allow the first AP in the dosed state to be woken up. If the first instruction information indicates that the first AP in the dosed state can be woken up, the first AP may be woken up. If the first instruction information indicates that the first AP in the dosed state cannot be woken up, the first AP may remain in the dosed state. Thus, the flexibility of controlling the AP MLD can be improved.

[0177]

[0199] Allowing the wake-up of the first AP in a dosed state may mean that the first AP is permitted to be woken up by using a wake-up request, and / or that the first AP is permitted to be woken up periodically. Not allowing the wake-up of the first AP in a dosed state may mean that the first AP is not permitted to be woken up by using a wake-up request, and / or that the first AP is not permitted to be woken up periodically.

[0178]

[0200] In implementation 1.1, the first instruction information includes a wake-up enable field, which indicates whether the wake-up of the first AP in the dose state is permitted or not.

[0179]

[0201] The wake-up enable field may occupy one or more bits. If the wake-up enable field has a first value (for example, one bit is 1 or 0), it can indicate that the first AP in a dosed state is permitted to be woken up. If the wake-up enable field has a second value (for example, one bit is 0 or 1), it can indicate that the first AP in a dosed state is not permitted to be woken up.

[0180]

[0202] For example, in this implementation 1.1, the wake-up enable field may be carried in a reduced neighbor report element (RNR element) for instruction.

[0181]

[0203] In related technologies, the frame structure of the RNR element within a beacon frame is shown in Figure 5 and includes an MLD identification (identity, ID) field (occupying 8 bits), a Link ID field (occupying 4 bits), a BSS Parameter Change Count field (occupying 8 bits), a Power Management Mode field (occupying 1 bit), a Doze field (occupying 1 bit), and a Reserved field (occupying 2 bits). When the Power Management Mode field is set to 0, it indicates active mode; when the Power Management Mode field is set to 1, it indicates power save mode. When the Power Management Mode field is set to 1, the Doze field is valid; when the Doze field is set to 0, it indicates an active state; and when the Doze field is set to 1, it indicates a dose state. When a non-primary AP is in active mode, its power state is awake. When a non-primary AP is in power-saving mode, its power state can switch between awake and dosed states.

[0182]

[0204] Unlike Figure 5, Figure 6 shows the frame structure of an RNR element, which includes the MLD ID field (occupying 8 bits), the Link ID field (occupying 4 bits), the BSS parameter change count field (occupying 8 bits), the Power Management Mode field (occupying 1 bit), the Dose field (occupying 1 bit), the Wake-up Enable field (occupying 1 bit), and the Reserved field (occupying 1 bit). When the Dose field is set to 1, the Wake-up Enable field is enabled. When the Wake-up Enable field is set to 1, it indicates that the wake-up of the first AP in the dosed state is permitted. When the Wake-up Enable field is set to 0, it indicates that the wake-up of the first AP in the dosed state is not permitted.

[0183]

[0205] In implementation 1.2, the first instruction information includes a power management mode field, which indicates whether the wake-up of the first AP in a dosed state is permitted or not.

[0184]

[0206] The power management mode field may occupy one or more bits.

[0185]

[0207] Optionally, the power management mode field may further indicate that the first AP is in Active mode and / or Sleep mode.

[0186]

[0208] For example, if the power management mode field is set to the third value, it indicates that the first AP is in active mode, the first AP remains in the awake state, and state switching is not permitted; When the Power Management Mode field is set to the fourth value, it indicates that the first AP is in PS mode, the default state of the first AP is the Daze state, and state switching is permitted; When the Power Management Mode field is set to the fifth value, it indicates that the first AP is in sleep mode, the first AP remains in a dozed state, state switching is not permitted, and wake-up is not permitted (for example, a non-AP MLD is not permitted to send a wake-up request for wake-up).

[0187]

[0209] In this implementation 1.2, the power management mode field can be carried by an RNR element for instruction.

[0188]

[0210] Unlike Figure 5, Figure 7A shows the frame structure of an RNR element, which includes an MLD ID field (occupying 8 bits), a Link ID field (occupying 4 bits), a BSS parameter change count field (occupying 8 bits), a power management mode field (occupying 2 bits), and a reserved field (occupying 2 bits). In one example, Table 1 shows the power management modes indicated by the power management mode field.

[0189] If the power management mode field is set to 00 (i.e., the third value is 00), it indicates that the first AP is in active mode.

[0190] If the power management mode field is set to 10 (i.e., the fourth value is 10), it indicates that the first AP is in PS mode.

[0191] If the power management mode is set to 11 (i.e., the fifth value is 11), it indicates that the first AP is in sleep mode.

[0192] Table 1 further shows that the power management mode field is set to a sixth value (for example, the sixth value is 01) as Reserved.

[0193] Table 1

[0194] [Table 1]

[0211] Unlike Figure 5, Figure 7B further illustrates the frame structure of an RNR element, which includes the MLD ID field (occupying 8 bits), the Link ID field (occupying 4 bits), the BSS parameter change count field (occupying 8 bits), the power management mode field (occupying 2 bits), the dose field (occupying 1 bit), and the reserved field (occupying 1 bit). For the power management modes indicated by the power management mode field, see the example in Table 1. Further details are not provided here.

[0195]

[0212] If the first instruction indicates that the wake-up of the first AP, which is in a dose state, is permitted, then the first AP is permitted to be woken up by using a wake-up request and / or to be woken up periodically.

[0196]

[0213] If a wake-up is performed using a wake-up request, after S402, the non-AP MLD may send a second PPDU to the AP MLD, which then receives the second PPDU. The second PPDU carries second instruction information, which is used to wake up the first AP corresponding to one or more links.

[0197]

[0214] It is possible to understand that an AP MLD can also transmit a seventh PPDU to a non-AP MLD, which receives the seventh PPDU, which carries sixth instruction information, and that the sixth instruction information is used to wake up a first STA corresponding to one or more links.

[0198]

[0215] The frame structure of the second PPDU transmitted by a non-AP MLD may be the same as or different from the frame structure of the sixth PPDU transmitted by an AP MLD.

[0199]

[0216] In Implementation 2.1, the second or sixth instruction information includes a link instruction field, which indicates the link (or the first STA or first AP corresponding to the link) that is requested to be woken up.

[0200]

[0217] The link indicator field can occupy one or more bits. For example, if the MLD supports 16 links, the link indicator field may occupy 16 bits, each bit corresponding to one link. If a bit is set to a seventh value (e.g., 1 or 0), it indicates that the link corresponding to the bit is requested to wake up. If a bit is set to an eighth value (e.g., 0 or 1), it indicates that the link corresponding to the bit is not to be woken up.

[0201]

[0218] For example, the link instruction field may also be a link bitmap field.

[0202]

[0219] Optionally, the link instruction field may be carried in a Link Recommendation frame, and the frame type of the Link Recommendation frame may be an EHT Action frame.

[0203]

[0220] Table 2 shows the field format in a link-recommended frame, including a Category field, an EHT action field, and a link bitmap field (occupying 16 bits). Sequence numbers in the table may refer to the order.

[0204] Table 2

[0205] [Table 2]

[0221] For example, implementation 2.1 is applicable to a scenario in which a non-AP MLD sends a link instruction field to an AP MLD. In another example, implementation 2.1 is applicable to a unicast scenario, in which the non-AP MLD may be used as the transmitting end for sending the link instruction field to an AP MLD, or the AP MLD may be used as the transmitting end for sending the link instruction field to a non-AP MLD. Naturally, in some cases, implementation 2.1 is applicable to multicast or broadcast scenarios. The AP MLD can send a seventh PPDU separately to each of the multiple non-AP MLDs, which is equivalent to carrying the link instruction field in a unicast frame for instruction.

[0206]

[0222] In implementation 2.2, the second instruction information (or sixth instruction information) includes identifiers for multiple station multilink devices (or multiple access point multilink devices) and a link instruction field corresponding to the identifier of each station multilink device.

[0207]

[0223] The similarities between the link instruction field in Implementation 2.2 and the link instruction field in Implementation 2.1 will not be explained in detail.

[0208]

[0224] Identifiers for multiple station multilink devices may be represented by an association ID (AID) list element. The link instruction field may be a multi-link traffic element and indicates information about the preferred link used for transmission.

[0209]

[0225] Optionally, multiple station multilink devices can correspond to the same multicast address or the same broadcast address.

[0210]

[0226] Table 3 shows the field format in a link recommendation frame, including a category field, an EHT action field, an AID list element, and a multilink traffic element. Sequence numbers in the table may refer to the order.

[0211] Table 3

[0212] [Table 3]

[0227] For example, implementation 2.2 is applicable to multicast or broadcast scenarios. Another example is that implementation 2.2 is applicable to scenarios where an AP MLD sends a link instruction field to a non-AP MLD. Naturally, in some cases, implementation 2.2 is applicable to unicast scenarios.

[0213]

[0228] In implementation 2.3, the second PPDU (or the seventh PPDU) includes a Control field, the second instruction information (or the sixth instruction information) is carried in the Control field, and the Control field indicates the link requested to wake up.

[0214]

[0229] The control field can occupy one or more bits. For example, if an MLD supports 16 links, the control field could occupy 16 bits, with each bit corresponding to one link.

[0215]

[0230] For example, the control field may be an Access Point Assistance Request (ARR) control field, and the ARR control field contains second (or sixth) instruction information. For example, the ARR control field is carried in the HT control field within the MAC protocol data unit (MPDU) frame header.

[0216] Figure 8 shows the format of the ARR control field, which includes an Assisted Access Point Link Identifier (Assisted AP Link ID) field (occupying 16 bits) and a reserved field (occupying 4 bits).

[0217]

[0231] Optionally, the access point support request control field may further carry third instruction information, which indicates that the access point support request control field is used to wake up a dosed first AP within a specified access point multilink device.

[0218]

[0232] In related technologies, the ARR control field is used by the STA MLD to request the AP MLD to send a Trigger frame on a specified link in order to assist the non-AP MLD when performing synchronization. To distinguish whether the ARR control field is used to request the AP MLD to send a Trigger frame on the corresponding link (i.e., the specified link) or to request the AP MLD to wake up on the corresponding link, If the third instruction information is the ninth value (for example, one bit is 0 or 1), the third instruction information is used to request the AP MLD to wake up on the corresponding link; or, If the third instruction information is the tenth value (for example, one bit is 0 or 1), the third instruction information is used to request the AP MLD to send a trigger frame on the corresponding link.

[0219]

[0233] Figure 9 shows the format of the ARR control field, which includes an Aided AP Link ID bitmap field (occupying 16 bits), a Type field (occupying 1 bit), and a Reserved field (occupying 3 bits). When the Type field is set to 0, the AP MLD is requested to send a trigger frame on the corresponding link. When the Type field is set to 1, it indicates that the AP MLD is requested to wake up on the corresponding link. The Aided AP Link ID bitmap field indicates the link that is requested to wake up. For example, a non-AP MLD requests that the corresponding link be woken up by sending a wake-up request that carries the ARR control field.

[0220]

[0234] When the first AP switches from a dozed state to an awake state, it is possible to assume that it does not transmit an ARR control field (the type field is set to 1) and all STAs corresponding to the first AP are in a dozed state, and that it transmits an ARR control field (the type field is set to 1) and all STAs corresponding to the first AP are in an awake state in either power-saving mode or active mode.

[0221]

[0235] Implementation 2.3 is applicable to unicast scenarios, or to multicast or broadcast scenarios.

[0222]

[0236] In implementation 2.4, the second instruction (or sixth instruction) includes a More Data field, which indicates a request to wake up the link corresponding to the first AP.

[0223]

[0237] The More Data field may occupy one or more bits.

[0224]

[0238] The More Data field may be used to inform AP MLD whether there is data to be transmitted.

[0225] If the More Data field is set to an eleventh value (for example, bit 1 is 1 or 0), it indicates that there is data to be transmitted or received, and the link corresponding to the first AP is requested to wake up.

[0226] If the More Data field is set to a 12th value (for example, if one bit is 0 or 1), it indicates that there is no data to send or receive, and the link corresponding to the first AP will not wake up.

[0227]

[0239] For example, a non-AP MLD transmits an MPDU over the primary link, where the MPDU includes a More Data field used to inform the first AP whether the data to be transmitted or received is being transmitted over the non-primary link.

[0228]

[0240] In another example, a non-AP MLD transmits an MPDU over a non-primary link, where the MPDU includes a More Data field used to inform the first AP whether the data to be transmitted or received is being carried over a non-primary link.

[0229]

[0241] In another example, a non-AP MLD transmits a synchronized (sync) MPDU over the primary and non-primary links, where the synchronized MPDU includes a more data field used to inform the first AP whether there is any data to be transmitted or received. The more data field in the synchronized MPDU transmitted over the primary and non-primary links is set to the same value.

[0230]

[0242] If the AP is to be periodically woken up, a periodic active time period and a periodic dose time period may be set according to TWT technology to control the AP so that it is periodically woken up. The AP is in an awake state during the active time period and in a dosed state during the dose time period.

[0231]

[0243] TWT includes individual TWTs and broadcast TWTs.

[0232]

[0244] In each TWT, each STA can set up a separate TWT protocol with the AP, and each STA can have a corresponding active time period and a corresponding dose time period.

[0233]

[0245] As shown in Figure 10, the STA is used as a TWT request station (TWT request STA) to send a TWT request frame to the AP to request setting the wake time; the AP is used as a TWT response station (TWT response STA) to send a TWT response frame to the TWT request STA. The TWT protocol is set up between the TWT request STA and the TWT response STA. The TWT protocol may include one or more rTWT SPs.

[0234]

[0246] After the TWT protocol is set up, the TWT request STA and TWT response STA maintain an awake state in the negotiated rTWT SP to facilitate data reception and transmission. Outside of the time cycle, the TWT request STA and / or TWT response STA can perform power saving through dozing.

[0235]

[0247] It is possible to understand that a TWT request STA may also be an AP, and a TWT response STA may also be an STA.

[0236]

[0248] In broadcast TWT, a group of STAs can set up a public TWT protocol with an AP. The group of STAs may correspond to the same active time period and the same dose time period.

[0237]

[0249] An AP can carry information about one or more broadcast TWTs in a beacon frame, each broadcast TWT represented by the AP's MAC address and a broadcast TWT identifier (TWT ID). If an STA intends to join a broadcast TWT after receiving a beacon frame, the STA can send a broadcast TWT setup request message to the AP to join the broadcast TWT. During broadcast TWT setup, the STA is required to specify the broadcast TWT ID in order to request to join a particular broadcast TWT. After joining a broadcast TWT, the STA can wake up based on the SP indicated by the TWT parameter set and communicate with the AP. It should be noted that if an STA supports broadcast TWTs but does not explicitly join a broadcast TWT ID, the STA will by default join the broadcast TWT with broadcast TWT ID=0.

[0238]

[0250] The TWT parameter set can indicate the duration of rTWT SP occurrences and the duration of each rTWT SP, potentially further illustrating the broadcast TWT life cycle. The broadcast TWT life cycle is measured in units of beacon frame intervals and represents the duration of the setup broadcast TWT.

[0239]

[0251] Figure 11 shows the format of a broadcast TWT element, which includes an element ID field, a length field, a control field, and a TWT parameter information field.

[0240] The control fields include the Neighbor Discovery Protocol (NDP) Paging Indicator field, the Responder PS mode field, the Negotiation Type field, the TWT Information Frame Disabled field, the Wake Duration Unit field, and the Reserved field.

[0241] The TWT parameter information fields include the Request Type field, Target Wake Time field, Nominal Minimum TWT Wake Duration field, TWT Wake Interval Mantissa field, and Broadcast TWT Info field.

[0242] The Request Type field includes the TWT Request field, TWT Setup Command field, Trigger field, Last Broadcast Parameter Set field, Flow Type field, Broadcast TWT Recommendation field, TWT Wake Interval Exponent field, and Reserved field.

[0243] The Broadcast TWT Information field includes the Reserved field, the Broadcast TWT ID field, and the Broadcast TWT Persistence field.

[0244]

[0252] AP MLD allows adding Link Unavailability information to a reserved field in the RNR element to indicate whether a link is available. For example, if the Link Unavailability information is set to 1, it indicates that the corresponding link is unavailable for transmission, and if the Link Unavailability information is set to 0, it indicates that the corresponding link is available for transmission.

[0245]

[0253] Alternatively, AP MLD can specify the Link Unavailability Count time and Link Unavailability Duration in the per-STA Profile field within the Multi-link element of the beacon frame. The frame structure of the multi-link element is shown in Figure 12 and includes an Element ID field, a Length field, an Element ID Extension field, a Multi-Link Control field, a Common Info field, and a Link Info field. The Common Info field carries common information about multiple stations in the MLD and information about the MLD. The Link Info field carries information about stations on each link in the MLD and includes one or more per-STA Profile fields. The per-STA Profile field includes a Subelement ID field, a Length field, and a Data field. The data fields include the Station Control (STA) field, the Station Information (STA) field, and the Station Profile (STA Profile) field. The STA Profile field includes one or more fields, one or more elements, and a Non-Inheritance Element. The Multilink Control field carries the type of the Multilink element (for example, two variants defined in the current protocol, such as the Basic variant and the Probe Request variant, or another type) and a Presence Bitmap field indicating which fields are missing.

[0246] The format of the presence bitmap field may be as shown in Figure 13A and may include an MLD MAC Address Present field (occupying 1 bit), a Link ID Info Present field (occupying 1 bit), a BSS Parameters Change Count Present field (occupying 1 bit), a Medium Synchronization Delay Information Present field (occupying 1 bit), an Enhanced Multi-Link (EML) Capabilities Present field (occupying 1 bit), an MLD Capabilities Present field (occupying 1 bit), and a Reserved field (occupying 6 bits).

[0247]

[0254] However, AP MLD cannot precisely determine when instructions should be executed by using link unavailable information or per-STA profile fields, and therefore data may still be sent and received outside the SP.

[0248]

[0255] In implementation 3.1, the AP transmits a sixth PPDU, which carries a fifth instruction information indicating whether transmission outside the rTWT SP is permitted or not. In this implementation, the AP uses the fifth instruction information to instruct the system to prohibit the reception and transmission of data outside the rTWT SP. This prevents data transmission and reception from occurring outside the rTWT SP, thereby further saving power.

[0249]

[0256] For example, the fifth instruction information includes a Transmission allowed Out of TWT SP field, which may occupy one or more bits.

[0250] If the TWT SP outside transmission permission field is set to the 13th value (for example, bit 1 is 1 or 0), it indicates that transmission outside the rTWT SP is permitted.

[0251] If the TWT SP outside transmission permission field is set to a 14th value (for example, bit 1 is 0 or 1), it indicates that transmission outside the rTWT SP is not permitted.

[0252]

[0257] As an option, a TWT SP external transmission permission field can be added to the TWT element.

[0253]

[0258] In implementation 3.2, the first PPDU includes a power management mode field, which further indicates a periodic power save mode. In periodic power save mode, it may be indicated by default that transmission outside the rTWT SP is not permitted.

[0254]

[0259] For example, if the Power Management Mode field in Table 1 is set to the sixth value (for example, the sixth value is 01), it indicates a periodic power saving mode.

[0255]

[0260] In implementation 3.3, if the fifth instruction indicates that transmission outside the rTWT SP is not permitted, the power management mode field further indicates a periodic power saving mode. In other words, implementation 3.3 is a combination of implementation 3.1 and implementation 3.2.

[0256]

[0261] For STA MLDs that do not support the TWT protocol, the STA MLD is not permitted to use the AP MLD and non-primary links for transmission when the AP MLD is operating in periodic power-saving mode. If the STA MLD supports and is compatible with the TWT protocol, and the AP MLD is operating in periodic power-saving mode, the STA MLD is permitted to use the AP MLD and non-primary links for transmission at the SP.

[0257]

[0262] In implementation 3.4, if the first AP is in power saving mode (e.g., a dose state in power saving mode) and the TWT protocol is set up between the first AP and the corresponding STA, i.e., member station (member STA), the first AP can automatically wake up before or when the TWT SP starts, and the corresponding STA does not need to send a wake-up request for the wake-up.

[0258]

[0263] Optionally, the first AP and its corresponding member STA automatically wake up before the TWT SP begins in order to perform data exchange. Channel access can be initiated based on parameter information indicated by the network allocation vector synchronization delay (NAVSyncDelay) or the media synchronization delay information subfield of the multilink element. For example, channel access may be initiated after wake-up. The duration between the point in time when the first AP switches to the awake state and the start of the TWT SP is not limited in this case.

[0259]

[0264] In this implementation 3.4, the power management mode field may not indicate a periodic power saving mode.

[0260]

[0265] Furthermore, the first AP in power-saving mode does not transmit beacon frames. In this case, when transmitting beacon frames, another AP in the AP MLD (e.g., the second AP) may carry the TWT element in the link information of the first AP within the multilink element.

[0261]

[0266] According to implementations 3.1 to 3.4, after the first AP in power-saving mode in the AP MLD is woken up by one or more STA MLDs, the STA MLD can determine that the first AP in the AP MLD is in an awake state in the following implementations.

[0262]

[0267] In implementation 4.1, the AP MLD sends a third PPDU to the STA MLD, where the third PPDU indicates the first AP that is ultimately woken up.

[0263]

[0268] Optionally, AP MLD may transmit a third PPDU on the primary or non-primary link.

[0264]

[0269] For example, after receiving a second PPDU (e.g., a link recommendation frame), the AP MLD can reply with a corresponding eighth PPDU (e.g., a link recommendation frame). The eighth PPDU includes a link indicator field to indicate the link (or the first AP corresponding to the link) that will ultimately be woken up. For example, if the MLD supports 16 links, the link indicator field may occupy 16 bits, each bit corresponding to one link. If a bit is set to 1 or 0, it indicates that the link corresponding to that bit will be woken up. If a bit is set to 0 or 1, it indicates that the link corresponding to that bit will not be woken up.

[0265]

[0270] In implementation 4.2, the AP MLD transmits a fourth PPDU to the STA MLD on the link to be woken up, where the fourth PPDU implicitly indicates that the first AP corresponding to the link is to be woken up.

[0266]

[0271] Optionally, the AP MLD can transmit the fourth PPDU on a non-primary link.

[0267]

[0272] For example, the fourth PPDU may be a trigger frame or a PS poll frame.

[0268]

[0273] In implementation 4.3, the AP MLD accepts a wake-up request by default and switches from the doze state to the awake state after a wake-up delay.

[0269]

[0274] The wake-up delay is the time for the first AP to switch from the doze state to the awake state. In other words, the wake-up delay is determined based on the delay required for the first AP to switch from the doze state to the awake state. For example, if the delay for the first AP to switch from the doze state to the awake state is T, the wake-up delay may be T + t or T - t. Optionally, after receiving the wake-up request, the first AP requires time t to analyze the wake-up request and then requires time T to switch from the doze state to the awake state. In this case, the wake-up delay may be T + t.

[0270]

[0275] For example, the first PPDU may further include a wake-up delay field, and the wake-up delay field indicates the delay for the first AP to switch from the doze state to the awake state.

[0271]

[0276] In another example, the AP MLD transmits a fifth PPDU, where the fifth PPDU includes a wake-up delay field that indicates a delay for the first AP to switch from the doze state to the awake state.

[0272]

[0277] Optionally, the fifth PPDU further includes a power save operation support field that indicates whether the wake-up delay field exists.

[0273]

[0278] For example, the wake-up delay field and the optional power save operation support field are carried in the multi-link control field.

[0274] FIG. 13B is a diagram of a possible format of the multi-link control field, including a Maximum Number of Simultaneous Links field (occupying 4 bits), a sounding reference signal (SRS) Support field (occupying 1 bit), a TID-to-link Mapping Negotiation Supported field (occupying 2 bits), a Frequency Separation For STR field (occupying 5 bits), an AAR Support field (occupying 1 bit), a Power Save Operation Support field (occupying 1 bit), and a Wakeup Delay field (occupying 2 bits). When the Power Save Operation Support field is set to 1 or 0, the Wakeup Delay field exists. When the Power Save Operation Support field is set to 0 or 1, the Wakeup Delay field does not exist.

[0275]

[0279] The wake-up delay field indicates the delay required for the first AP to switch from the dozed state to the awake state. See the example in Table 4 for the delay indicated by the wake-up delay field. If the wake-up delay field is set to a first value, for example, 00 (or 1), it indicates that the wake-up delay is 0 microseconds (μs). If the wake-up delay field is set to a second value, for example, 01 (or 1), it indicates that the wake-up delay is 32 μs. If the wake-up delay field is set to a third value, for example, 10 (or 2), it indicates that the wake-up delay is 64 μs. If the wake-up delay field is set to a fourth value, for example, 11 (or 3), it indicates that the wake-up delay is 128 μs.

[0276] Table 4

[0277] [Table 4]

[0280] After the wake-up delay, the first AP may be considered to have switched to an awake state. Correspondingly, after the wake-up delay, the non-AP MLD can initiate channel access by using the first STA (which is in an awake state) that corresponds to the first AP, and the AP MLD and the non-AP MLD can communicate over the link between the first AP and the first STA.

[0278]

[0281] The fifth PPDU may include a mode switch count field. The mode switch count field indicates the remaining time for the first AP to switch from its current mode to the target mode. For example, the mode switch count field indicates the number of additional TBTTs required for the mode switch.

[0279]

[0282] For example, the wake-up delay field and the optional mode switch count field are carried in the Power Management Information field. Figure 13C shows possible formats for the Power Management Information field, including the Power Management Mode field (occupying 2 bits), the Wake-up Delay field (occupying 2 bits), the Reserved field (occupying 4 bits), and the Mode Switch Count field (occupying 8 bits). See Table 1 for the modes indicated by the Power Management Mode field. See Table 4 for the delays indicated by the Wake-up Delay field.

[0280]

[0283] The fifth PPDU is capable of carrying beacon frames. With respect to the mode switching count field, if the field corresponds to the non-primary link of the NSTR mobile AP MLD, the NSTR mobile AP MLD does not transmit beacon frames on the non-primary link, so the TBTT corresponding to the field refers to the TBTT of the primary link, i.e., the number of additional TBTTs required for the first AP corresponding to the primary link to perform a mode switch.

[0281]

[0284] The power management information field may be carried in the common information field and / or in the link information field.

[0282]

[0285] When the power management information field is carried in the common information field, Figure 13D shows possible formats for the common information field, including a common information length field (occupying 1 octet), an MLD MAC address field (occupying 6 octets), a link ID information field (occupying 0 or 1 octet), a BSS parameter change count field (occupying 0 or 1 octet), a media synchronization delay information field (occupying 0 or 2 octets), an EML capability field (occupying 0 or 2 octets), an MLD capability field (occupying 0 or 2 octets), and a power management information field (occupying 0 or 2 octets).

[0283]

[0286] When the power management information field is carried in the link information field, Figure 13E shows possible formats for the STA information field, including an STA information length field (occupying 1 octet), an STA MAC address field (occupying 0 or 6 octets), a Beacon Interval field (occupying 0 or 2 octets), a delivery traffic indication map (DTIM) information field (occupying 0 or 2 octets), an NSTR indication bitmap field (occupying 0, 1, or 2 octets), a BSS parameter change count field (occupying 0 or 1 octet), and a power management information field (occupying 0 or 2 octets).

[0284]

[0287] The fifth PPDU may contain seventh instruction information, which indicates whether the mode switching count field is present. For example, the seventh instruction information is added to the STA control field to indicate whether the power management information field is present. Figure 13F shows a possible format of the STA control field, which includes the Link ID field (occupying 4 bits), Complete Profile field (occupying 1 bit), STA MAC address presence field (occupying 1 bit), Beacon interval presence field (occupying 1 bit), DTIM information presence field (occupying 1 bit), NSTR Link Pair field (occupying 1 bit), NSTR Bitmap Size field (occupying 1 bit), BSS parameter change count presence field (occupying 1 bit), power management information presence field (occupying 1 bit), and reserved field (occupying 4 bits). For example, if the value of the power management information presence field is 1, it indicates that the power management information field is present. If the value of the Power Management Information Existence field is 0, it indicates that the Power Management Information field does not exist.

[0285]

[0288] According to implementations 4.1 to 4.3, after a first AP in power-saving mode in an AP MLD is woken up by one or more non-AP MLDs, the first AP may, in some cases, switch back from the awake state to the dozed state.

[0286]

[0289] For example, if a channel is in an idle state, the first AP can switch from an awake state to a dozed state.

[0287]

[0290] The channel may be in an idle state periodically.

[0288]

[0291] Regarding another example, when the first AP switches to the awake state, if all non-AP MLDs that sent wake-up requests set the more data field to 0, the first AP can switch from the awake state to the doze state.

[0289]

[0292] Specifically, one or more STA MLDs may send the fourth indication information to the AP MLD. When the AP MLD receives the fourth indication information sent by one or more STA MLDs and the fourth indication information indicates the 15th value, the first AP of the AP MLD can switch from the awake state to the doze state.

[0290]

[0293] The fourth indication information may occupy one or more bits. For example, the fourth indication information occupies 1 bit, and when 1 bit is set to 0 (i.e., the 15th value is set to 0), the first AP switches from the awake state to the doze state.

[0291]

[0294] For example, the fourth indication information is the information indicated by the more data field and indicates whether there is data to be transmitted. As an option, when the AP MLD performs data reception and transmission with multiple STA MLDs, if all STA MLDs send the more data field to the AP MLD and the more data field is set to 0, the AP MLD determines that the STA corresponding to the first AP in all STA MLDs does not have data to be transmitted, and the first AP in the AP MLD can switch to the doze state. The data to be transmitted may be referred to as a buffered unit (BU).

[0292]

[0295] For example, one or more STA MLDs send a data frame containing a More Data field set to 0, a Quality of Service (QoS) Null frame, or a control frame to the AP MLD to notify the first AP to switch from the awake state to the dose state.

[0293]

[0296] If STA MLD wishes to retransmit data after the first AP has switched to a dozed state, STA MLD can wake up the first AP again by using implementation 3.1 or 3.3.

[0294]

[0297] The method described above, provided in the embodiments of this application, may also be applied to a regular AP MLD, where no legacy STA exists on the corresponding link of the regular AP MLD. If a legacy STA exists and the AP MLD wishes to disable the link (i.e., the STA MLD associated with the AP MLD cannot map the STA MLD's traffic identifier (TID) to the link), or if the AP MLD wishes to configure the link as a clean link (i.e., the link is dedicated to the transmission of low-latency services), the AP MLD can make legacy frames transmitted on the link to be configured unidentifiable by the STA, and as a result, the legacy STA will not use the associated link to transmit data. For example, suppose an AP MLD has links 1, 2, and 3, and the AP MLD wishes to configure link 3 as a clean link. The AP MLD can configure a clean link. Thus, even if a legacy STA discovers that the link is available, the legacy STA cannot associate with link 3.

[0295]

[0298] For example, an AP MLD may transmit a Reduced Neighbor Report element, and the Target Beacon Transmission Time (TBTT) info set field, which corresponds to the first AP and is within the Reduced Neighbor Report element, carries the Multilink Device Parameters (MLD Parameters) field, where the TBTT info length is set to a first length value (e.g., 3), and as a result, the legacy STA ignores the first AP or the first link corresponding to the first AP.

[0296]

[0299] For example, AP MLD can transmit a Beacon frame over the first link, where the Beacon frame carries reduced neighbor report elements.

[0297]

[0300] Optionally, the TBTT info Field Type within the reduced neighbor report element can be set to 0 or 1.

[0298]

[0301] Optionally, the TBTT information field type within the reduced neighbor report element can be set to 0 or 1.

[0299]

[0302] In another example, AP MLD may send a reduced neighbor report element, and the TBTT information field type corresponding to the first AP and within the reduced neighbor report element is set to the 16th value (for example, the 16th value is set to 1), and as a result, the legacy STA ignores the first AP or the first link corresponding to the first AP.

[0300]

[0303] The format of the reduced neighbor report element may be as shown in Figure 14. The reduced neighbor report element includes an Element ID field, a Length field, and one or more Neighbor AP info fields. The Neighbor AP info field includes a TBTT info Header field, an Operating Class field, a Channel Number field, and one or more TBTT info set fields. The TBTT info Header field includes a TBTT info field type field, a Filtered neighbor AP field, a Reserved field, a TBTT info count field, and a TBTT info length field. The TBTT info set field includes one or more TBTT info fields.

[0301]

[0304] The Operation Class field indicates the operation class of the reported AP's operation channel, with 0 being a reserved value for the Operation Class field.

[0302]

[0305] The channel number field indicates the channel number corresponding to the operating channel of the reported AP, where 0 is a reserved value for the channel number field. Based on the operating class field and the channel number field, the STA can determine the specific location of the AP's channel on the frequency band.

[0303]

[0306] The TBTT Information Field Type field indicates the TBTT Information Type. This field and the TBTT Information Length field indicate the format of the TBTT Information Field. Here, 1, 2, and 3 are reserved values ​​for the TBTT Information Field Type field.

[0304]

[0307] The filtering neighbor AP field indicates whether the service set identifiers (SSIDs) of all basic service sets (BSS) carried in the neighbor AP information field match the SSIDs in the probe request frame.

[0305]

[0308] Reserved fields occupy 1 bit.

[0306]

[0309] The TBTT information count field indicates the number of TBTT information fields included in the TBTT information set field.

[0307]

[0310] The TBTT information length field indicates the length of each TBTT information field. The format of the information carried by TBTT information fields of different lengths may be as shown in Table 5.

[0308] Table 5

[0309] [Table 5] TIFF2026090260000007.tif44170

[0311] The possible formats for the TBTT information field are shown in Figure 15 and include the Neighbor AP Target Beacon Transmission Time Offset (Neighbor AP TBTT offset) field, the Basic Service Set Identifier (BSS identifier, BSSID) field, the Short SSID field, the BSS parameter field, the 20 MHz PSD field, and the MLD parameter field.

[0310]

[0312] The Neighbor AP TBTT Offset field occupies 0 or 1 octet and indicates the offset between the BSS sending the report and the reported BSS beacon frame transmission time, where the unit is time unit (TU), i.e., 1024 microseconds or 1 millisecond. A field of 254 indicates that the offset is 254 TU or greater, and a field of 255 indicates that the specific offset is unknown.

[0311]

[0313] The BSSID field is an optional field that occupies 0 or 6 octets and indicates the BSSID corresponding to the reported BSS.

[0312]

[0314] The Short SSID field is an optional field that occupies 0 or 4 octets and indicates the SSID of the BSS.

[0313]

[0315] The BSS parameter field is an optional field, occupying 0 or 1 octet, and indicates the relevant parameters of the BSS. As shown in Figure 16, the BSS parameter field may include the On-channel Tunneling (OCT) recommended field, the Same SSID field, the Multiple BSSID field, the Transmitted BSSID field, the Member Of ESS With 2.4 / 5 GHz Co-Located AP field, the Unsolicited Probe Response Active field, the Co-located AP field, and the Reserved field. The OCT recommended field is placed at bit 0 and indicates that the reported BSS expects to exchange managed media protocol data units (MPDUs) with the reported AP through the OCT mechanism. The "Same SSID" field is placed at bit 1 and indicates whether the reported AP and the AP transmitting the element have the same SSID. The "Multiple BSSID" field is placed at bit 2 and indicates whether the reported AP is part of a set of multiple BSSIDs. The "Transmitted BSSID" field is placed at bit 3. If the reported AP is part of a set of multiple BSSIDs, it further indicates whether the reported AP is a transmitted BSSID or a non-transmitted BSSID. The "ESS Member" field for 2.4 / 5 GHz Equivalent Location APs is placed at bit 4 and indicates whether the reported AP is located at the same location as a 2.4 / 5 GHz AP (i.e., whether the reported AP is a 6 GHz-only AP) and whether it is a member of an extended service set.The Unrequested Probe Response Active field is located at bit 5 and indicates whether the reported AP allows active probe responses. The Equivalent AP field is located at bit 6 and indicates whether the reported AP and the AP that sent the report are in equivalent positions. The Reserved field is located at bit 7.

[0314]

[0316] The 20 MHz PSD field is an optional field that occupies 0 or 1 octet and represents the maximum transmit power spectral density.

[0315]

[0317] The MLD parameter field occupies 0 or 3 octets and indicates the relevant MLD parameter. The field may include the following subfields: Multilink Device Identifier (MLD ID) field, Link Identifier (Link ID) field, BSS Parameter Change Count field, and Reserved field. The MLD ID field occupies 8 bits and indicates the identifier of the AP MLD. The Link ID field occupies 4 bits and indicates the link identifier corresponding to the reported AP. The BSS Parameter Change Count field occupies 8 bits. If a key update occurs in the reported AP, the value of this field increases. Otherwise, the value of this field remains unchanged. The Reserved field occupies 4 bits.

[0316]

[0318] The above implementations can be used separately or in combination.

[0317]

[0319] In embodiments of the present application, it is possible to understand that an access point multilink device (or a component of an access point multilink device (e.g., a chip or circuit)) and / or a station multilink device (or a component of a station multilink device) may perform some or all of the steps in embodiments of the present application. These steps or operations are merely examples. Other operations or various variations of operations may be further performed in embodiments of the present application. Furthermore, the steps may be performed in an order different from the order presented in embodiments of the present application, and not all operations in embodiments of the present application may be performed.

[0318]

[0320] In the following embodiments of this application, the names of messages or parameters within a device's message are merely examples, and messages or parameters may have other names in specific implementations. This is not particularly limited to the embodiments of this application. Furthermore, the sequences, names, values, information carried, meanings, or octets / bits occupied by fields within a frame structure are merely examples. This is not particularly limited to the embodiments of this application.

[0319]

[0321] In the embodiments provided in this application, the methods provided in the embodiments of this application are described separately in terms of the interaction between an access point multilink device and a station multilink device. To perform the functions in the methods provided in the embodiments of this application, the access point link device or station multilink device includes a hardware structure and / or software module, and the functions can be performed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. Whether any of the multiple functions are performed by using a hardware structure, a software module, or a combination of a hardware structure and a software module depends on the specific application and design constraints of the technical solution.

[0320]

[0322] The following describes a communication device configured to implement the above method in the embodiments of this application, with reference to the attached drawings. Therefore, all of the above may be used in the following embodiments. Repeating information will not be described again.

[0321]

[0323] Figure 17 shows possible representations of a communication device according to an embodiment of the present application. The communication device 1700 can be configured to perform functions or steps performed by an access point multilink device or station multilink device in an embodiment of the method described above. The communication device may include an optional processing unit 1701 and a transceiver unit 1702. A storage unit may be further included as an option. The storage unit may be configured to store instructions (code or program) and / or data. The processing unit 1701 and the transceiver unit 1702 can be coupled to the storage unit. For example, the processing unit 1701 can read instructions (code or program) and / or data from the storage unit and perform the corresponding method. The aforementioned units may be arranged independently or may be partially or fully integrated.

[0322]

[0324] In some possible implementations, the communication device 1700 can perform the behavior and functions of the access point link device in the embodiments of the above-described method accordingly. For example, the communication device 1700 may be an AP MLD or a component used in the AP MLD (e.g., a chip or circuit). The transceiver unit 1702 may be configured to perform all receive or transmit operations performed by the access point link device in the embodiments described above, e.g., S402 in the embodiment shown in Figure 4, and / or other processes used to support the technology described herein. The processing unit 1701 may be configured to perform all operations except the receive and transmit operations performed by the access point multilink device in the embodiments described above, e.g., generating the first PPDU in S401 in the embodiment shown in Figure 4, and / or other processes used to support the technology described herein.

[0323]

[0325] For example, processing unit 1701 is configured to generate a first PPDU, the first PPDU carrying first instruction information, which indicates that the wake-up of the first access point in a dosed state is permitted, or that the wake-up of the first access point in a dosed state is not permitted; and transceiver unit 1702 is configured to transmit the first PPDU via the first access point.

[0324]

[0326] In the optional configuration, the first instruction information includes a wake-up enable field, which indicates whether the wake-up of the first access point in a dosed state is permitted or not.

[0325]

[0327] In the optional configuration, the first instruction information includes a power management mode field, which indicates whether the wake-up of the first access point in a dosed state is permitted or not.

[0326]

[0328] In the optional configuration, the power management mode field further indicates that the first access point switches to active mode, and / or the power management mode field further indicates that the first access point switches to sleep mode.

[0327]

[0329] In the optional scheme, the first instruction indicates that the first access point, which is in a dozed state, is permitted to be woken up.

[0328]

[0330] The transceiver unit 1702 is further configured to receive a second PPDU transmitted by the station multilink device, the second PPDU carrying second instruction information, which is used to wake up the first access point corresponding to one or more links.

[0329]

[0331] In the optional configuration, the second instruction information includes a link instruction field, which indicates the link to be woken up; or the second instruction information includes identifiers for multiple station multilink devices and a link instruction field corresponding to the identifier of each station multilink device; or the second instruction information is carried in a control field, which indicates the link to be woken up.

[0330]

[0332] In the optional configuration, multiple station multilink devices correspond to the same multicast address or the same broadcast address.

[0331]

[0333] In the optional configuration, the second PPDU includes a control field, which carries the second instruction information.

[0332]

[0334] In the optional configuration, the control field is an access point support request control field, and the access point support request control field carries second instruction information.

[0333]

[0335] In the optional configuration, the access point assistance request control field further carries third instruction information indicating that the access point assistance request control field is used to wake up a first access point in a dozed state within a designated access point multilink device.

[0334]

[0336] In an optional configuration, the transceiver unit 1702 is further configured to transmit a third PPDU to a station multilink device, the third PPDU indicating the first access point that has been woken up.

[0335]

[0337] In an optional configuration, the transceiver unit 1702 is further configured to transmit a fourth PPDU to the station multilink device on the woken link, the fourth PPDU indicating that the first access point corresponding to the link has been woken up.

[0336]

[0338] In the optional configuration, the first PPDU includes a wake-up delay field, which indicates the delay for the first access point to switch from a dozed state to an awake state.

[0337]

[0339] In a possible implementation, the transceiver unit 1702 is further configured to transmit a fifth PPDU, the fifth PPDU including a wake-up delay field.

[0338]

[0340] In possible implementations, a fifth PPDU further includes a power-saving operation field, which indicates whether a wake-up delay field exists.

[0339]

[0341] In the optional configuration, the first access point, which is in power-saving mode, is woken up by one or more station multilink devices.

[0340]

[0342] The processing unit 1701 is further configured to switch the first access point from an awake state to a dose state when it receives a fourth instruction information transmitted by one or more station multilink devices and the fourth instruction information is set to 0.

[0341]

[0343] In the optional configuration, the fourth instruction information is the information indicated by the More Data field.

[0342]

[0344] In possible implementations, the processing unit is further configured to switch the first access point from an awake state to a dozed state when the channel is idle.

[0343]

[0345] In an optional configuration, the transceiver unit 1702 is further configured to transmit a reduced neighborhood report element, where the target beacon transmission time information set field, corresponding to the first access point and located within the reduced neighborhood report element, carries a multilink device parameter field, and the target beacon transmission time information length is set to a first length value, so that the legacy station ignores the first access point.

[0344]

[0346] In an optional configuration, the transceiver unit 1702 is further configured to transmit a reduced neighborhood report element, where the target beacon transmission time information field type corresponding to the first access point and located within the reduced neighborhood report element is set to a first type value, resulting in the legacy station ignoring the first access point.

[0345]

[0347] In an optional configuration, the transceiver unit 1702 is further configured to transmit a sixth PPDU, the sixth PPDU carrying a fifth instruction information, the fifth instruction information indicating that transmission is permitted outside of the service period or that transmission is not permitted outside of the service period.

[0346]

[0348] In possible implementations, the first PPDU includes a power management mode field, which further indicates a periodic power saving mode.

[0347]

[0349] In some possible implementations, the communication device 1700 can perform the behavior and functions of the station multilink device in the embodiments of the above-described method accordingly. For example, the communication device 1700 may be a non-AP MLD or STA MLD, or a component (e.g., a chip or circuit) used in a non-AP MLD or STA MLD. The transceiver unit 1702 may be configured to perform all receive or transmit operations performed by the station multilink device in the embodiments described above, e.g., S402 in the embodiment shown in Figure 4, and / or other processes used to support the technology described herein. The processing unit 1701 may be configured to perform all operations other than the receive and transmit operations performed by the station multilink device in the embodiments described above, e.g., deciding whether to wake up the first access point, and / or other processes used to support the technology described herein.

[0348]

[0350] For example, transceiver unit 1702 is configured to receive a first PPDU, the first PPDU carrying first instruction information, the first instruction information indicating that the wake-up of the first access point in a dosed state is permitted, or the first instruction information indicating that the wake-up of the first access point in a dosed state is not permitted; and processing unit 1701 is configured to determine, based on the first PPDU, whether to wake up the first access point.

[0349]

[0351] In the optional configuration, the first instruction information includes a wake-up enable field, which indicates whether the wake-up of the first access point in a dosed state is permitted or not.

[0350]

[0352] In the optional configuration, the first instruction information includes a power management mode field, which indicates whether the wake-up of the first access point in a dosed state is permitted or not.

[0351]

[0353] In the optional configuration, the power management mode field notifies the first access point to switch to awake mode, and / or the power management mode field notifies the first access point to switch to dose mode.

[0352]

[0354] In the optional configuration, the first instruction indicates that the first access point, which is in a dose state in power-saving mode, is permitted to be woken up.

[0353]

[0355] The transceiver unit 1702 is further configured to transmit a second PPDU, the second PPDU carrying a second instruction information, which is used to wake up the first access point corresponding to one or more links.

[0354]

[0356] In the optional configuration, the second instruction information includes a link instruction field, which indicates the link to be woken up; or the second instruction information includes identifiers for multiple station multilink devices and a link instruction field corresponding to the identifier of each station multilink device; or the second instruction information is carried within a control field, which indicates the link to be woken up.

[0355]

[0357] In the optional configuration, multiple station multilink devices correspond to the same multicast address or the same broadcast address.

[0356]

[0358] In the optional configuration, the second PPDU includes a control field, which carries the second instruction information.

[0357]

[0359] In the optional configuration, the control field is an access point support request control field, and the access point support request control field carries second instruction information.

[0358]

[0360] In the optional configuration, the access point assistance request control field further carries third instruction information indicating that the access point assistance request control field is used to wake up a first access point in a dozed state within a designated access point multilink device.

[0359]

[0361] In a possible implementation, the transceiver unit 1702 is further configured to receive a third PPDU, which indicates the first access point that has been woken up.

[0360]

[0362] In a possible implementation, the transceiver unit 1702 is further configured to receive a fourth PPDU on the woken link, the fourth PPDU indicating that the first access point corresponding to the link has been woken up.

[0361]

[0363] In the optional configuration, the first PPDU includes a wake-up delay field, which indicates the delay for the first access point to switch from a dozed state to an awake state.

[0362]

[0364] In an optional configuration, the transceiver unit is further configured to receive a fifth PPDU, the fifth PPDU including a wake-up delay field.

[0363]

[0365] In the optional configuration, the fifth PPDU further includes a power saving operation field, which indicates whether a wake-up delay field is present.

[0364]

[0366] In an optional configuration, a first access point in power-saving mode is woken up by one or more station multilink devices; and the transceiver unit 1702 is further configured to transmit a fourth instruction, which is set to 0, notifying the first access point to switch from the awake state to the dose state.

[0365]

[0367] In the optional configuration, the fourth instruction information is the information indicated by the More Data field.

[0366]

[0368] In an optional configuration, the transceiver unit 1702 is configured to receive a reduced neighborhood report element, where the target beacon transmission time information set field corresponding to the first access point and located within the reduced neighborhood report element carries a multilink device parameter field, and the target beacon transmission time information length is set to a first length value, so that the legacy station ignores the first access point; or, the transceiver unit 1702 is further configured to receive a reduced neighborhood report element, where the target beacon transmission time information field type corresponding to the first access point and located within the reduced neighborhood report element is set to a first type value, so that the legacy station ignores the first access point.

[0367]

[0369] In an optional configuration, the transceiver unit 1702 is further configured to receive a sixth PPDU, the sixth PPDU carrying a fifth instruction information, the fifth instruction information indicating that transmission is permitted outside of service hours or not permitted outside of service hours.

[0368]

[0370] In the optional configuration, the first PPDU includes a power management mode field, which further indicates a periodic power saving mode.

[0369]

[0371] It should be noted that the communication device 1700 can be configured to perform embodiments of the method described above. For specific steps, descriptions, and corresponding beneficial effects, please refer to the embodiments of the method described above. Details are not described again here.

[0370]

[0372] It should be understood that in the embodiments of this application, the processing unit 1701 may be implemented by a processor / processing circuit or a circuit component related to a processor / processing circuit, and the transceiver unit 1702 may be implemented by a transceiver / transceiver interface, a circuit component related to a transceiver / transceiver interface, or a communication interface.

[0371]

[0373] Figure 18 shows possible representations of a communication device according to an embodiment of the present application. The communication device 1800 may include a processor 1801 and a transceiver 1805, and optionally further include a memory 1802. The communication device may be used as a PPDU generation and transmission device in the present application, or as a PPDU receiving device in the present application.

[0372]

[0374] Transceiver 1805 may also be referred to as a transceiver unit, transceiver machine, transceiver circuit, etc., and is configured to implement transceiver functionality. Transceiver 1805 may include a receiver and a transmitter. The receiver may also be referred to as a receiver machine, receiver circuit, etc., and is configured to perform receiving functionality. The transmitter may also be referred to as a transmitter machine, transmitter circuit, etc., and is configured to perform transmitting functionality.

[0373]

[0375] Memory 1802 is capable of storing a computer program or software code or instruction 1804, which may also be referred to as firmware. Processor 1801 can control the MAC layer and PHY layer by executing a computer program or software code or instruction 1803 within processor 1801, or by calling a computer program or software code or instruction 1804 stored in memory 1802, to implement the PPDU communication method provided in the following embodiments of the present application. Processor 1801 may be a central processing unit (CPU), and memory 1802 may be, for example, read-only memory (ROM) or random access memory (RAM).

[0374]

[0376] The processor 1801 and transceiver 1805 described in this application may be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), hybrid signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, and the like.

[0375]

[0377] The communication device 1800 may further include an antenna 1806. The modules / units included in the communication device 1800 are merely illustrative examples and are not limited to those in this application.

[0376]

[0378] As described above, the communication device 1800 described in the above embodiments may be an AP MLD or an STA MLD. However, the scope of communication devices described in this application is not limited to these, and the structure of the communication device may not be limited by Figure 18. An AP MLD includes one or more APs, and an STA MLD includes one or more STAs.

[0377]

[0379] The AP may be a multi-antenna / multi-radio frequency AP or a single-antenna / single-radio frequency AP. The antenna / radio frequency AP is configured to transmit / receive data packets. In implementation, the antenna portion or radio frequency portion of the AP may be separated from the main body portion of the AP, or may be in a remote layout configuration. In implementation, the STA may be a single-antenna / radio frequency STA or a multi-antenna / multi-radio frequency STA, or may be a device with more than two antennas. The antenna / radio frequency STA is configured to transmit / receive data packets. In implementation, the antenna portion or radio frequency portion of the STA may be separated from the main body portion of the STA, or may be in a remote layout configuration.

[0378]

[0380] The communication device in this application may, alternatively, be a standalone device or part of a larger device. For example, the implementation of the communication device may be as follows: (1) Independent integrated circuits (ICs), chips, chip systems, or chip subsystems; (2) A set having one or more ICs, wherein the IC set also includes a storage component configured to store data or instructions; (3) Modules that can be embedded in another device; (4) Receivers, intelligent terminals, wireless devices, handsets, mobile units, vehicle-mounted devices, cloud devices, artificial intelligence devices, etc.; or (5) Others, etc.

[0379]

[0381] For cases where the communication device is implemented as a chip or chip system, please refer to the diagram of the chip structure shown in Figure 19. The chip shown in Figure 19 includes a processor 1901 and an interface 1902. There may be one or more processors 1901 and multiple interfaces 1902. The interface 1902 is configured to receive and transmit signals. Optionally, the chip or chip system may include a memory 1903. The memory 1903 is configured to store program instructions and data required by the chip or chip system.

[0380]

[0382] Furthermore, the embodiments of this application do not limit the scope of protection and applicability of the claims. A person skilled in the art can make adaptive modifications to the function and arrangement of the elements in this application without departing from the scope of the embodiments of this application, or can omit, replace, or add various processes or components as appropriate.

[0381]

[0383] Embodiments of the present application further provide a computer-readable storage medium. The computer-readable storage medium stores a computer program; when the computer-readable storage medium is executed by a computer, the functions of the embodiments of the method described above are performed.

[0382]

[0384] Embodiments of this application further provide a computer program product. When the computer program product is executed by a computer, the functions of the embodiments of the method described above are performed.

[0383]

[0385] Embodiments of the present application further provide a chip system. The chip system includes a processor and an interface and is configured to support a communication transmission device when performing functions related to an access point or station in the embodiments of the above-described method, for example, when determining or processing at least one of the data and information in the above-described method. In a possible design, the chip system further includes memory. The memory is configured to store the information and data required by the communication device. The chip system may include a chip, or it may include a chip and other discrete components.

[0384]

[0386] The embodiments of this application provide a functional entity configured to implement the aforementioned communication method.

[0385]

[0387] The embodiments of this application provide a communication system. The communication system includes an access point multilink device and a station multilink device that implement the aforementioned communication method.

[0386]

[0388] It should be understood that the process sequence numbers do not imply the execution sequences in the various embodiments of this application. The execution sequences of a process must be determined according to the function and internal logic of the process and should not be construed as any limitation to the implementation processes of the embodiments of this application.

[0387]

[0389] A person skilled in the art will recognize, in combination with the examples described in the embodiments disclosed in this specification, that the units and algorithmic steps may be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether the function is performed by hardware or by software depends on the specific application and the design constraints of the technical implementation. A person skilled in the art may use different methods to implement the described function for each particular application, but such implementation should not be considered to extend beyond the scope of this application.

[0388]

[0390] For convenience and concise explanation, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, apparatus, and units should be referred to in the corresponding processes in the embodiments of the method. Further details are not described here.

[0389]

[0391] It should be understood that, in some embodiments provided in this application, the systems, apparatus, and methods disclosed may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementations. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling, or communication connection shown or described may be implemented through some interface. Indirect coupling or communication connection between apparatus or units may be implemented in an electrical, mechanical, or other form.

[0390]

[0392] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, may be located in one place, or may be distributed across multiple network units. All or part of the units can be selected based on the actual requirements to achieve the objectives of implementing the embodiment.

[0391]

[0393] Furthermore, the functional units in the embodiments of this application may be integrated into a single processing unit, and each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0392]

[0394] When a function is implemented in the form of a software function unit and sold or used as an independent product, the function can be stored on a computer-readable storage medium. Based on this understanding, the technical implementation of the present application, or the portion that contributes to the prior art, or a portion of the technical implementation, may be implemented in the form of a software product. A computer software product is stored on a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0393]

[0395] The sequence of steps in the embodiments of this application may be modified, combined, or eliminated based on actual requirements.

[0394]

[0396] The modules / units of the apparatus in the embodiments of this application may be combined, divided, and removed based on actual requirements.

[0395]

[0397] In this application, "and / or" describes a relationship of relevance to describe related objects, indicating that three relationships may exist. For example, A and / or B can represent three cases: A exists only, both A and B exist, and B exists only. The letter " / " generally indicates an "or" relationship between related objects. In this application, "at least one" means one or more, and "multiple" means two or more. It should also be understood that in the description of this application, terms such as "first" and "second" are used only for distinction and explanation, and should not be understood as indicators or suggestions of relative importance, nor as indicators or suggestions of sequence.

[0396]

[0398] Furthermore, unless otherwise specified in this application, the same or similar parts in the embodiments should be referenced to one another. Unless otherwise specified or unless there is a logical conflict, the terminology and / or descriptions in the embodiments and the implementations / methods / implementation methods in this application are consistent and can be referenced to one another between different embodiments and between implementations / methods / implementation methods in embodiments. The technical features and implementations / methods / implementation methods in different embodiments may be combined to form new embodiments, implementations, methods, or implementation methods based on the internal logical relationships of the technical features.

[0397]

[0399] The embodiments described above are intended solely to illustrate the technical implementation of the present application and are not intended to limit the present application. Although the present application is described in detail with reference to the embodiments described above, those skilled in the art will understand that further modifications can be made to the technical implementations described in the embodiments described above, or equivalent substitutions can be made to some of their technical features, without departing from the scope of the technical implementations of the embodiments of the present application.

Claims

1. A communication method applicable to a first multilink device, which: A step of generating a first physical layer protocol data unit (PPDU), wherein the first PPDU indicates that the wake-up of a first station in a dose state is permitted, and the first station is in power-saving mode; and Steps to send the first PPDU; A method that includes this.

2. In the method according to claim 1, The first PPDU includes a wake-up enable field, which indicates that waking up the first station in the dose state is permitted; or, A method wherein the first PPDU includes a power management mode field, the power management mode field indicating that the wake-up of the first station in the dose state is permitted.

3. In the method of claim 2, The power management mode field further indicates that the first station is in active mode, and / or The power management mode field further indicates that the first station is in the power saving mode.

4. The method according to claim 1, further: A method comprising the step of receiving a second PPDU transmitted by a second multilink device, wherein the second PPDU is used to wake up a first station corresponding to one or more links.

5. The method according to claim 4, wherein the second PPDU includes an assistance request control field.

6. The method according to claim 5, wherein the support request control field is used to wake up the first station.

7. The method according to claim 4, further: A step of transmitting a third PPDU to the second multilink device, wherein the third PPDU indicates the activated first station; or A step of transmitting a fourth PPDU to the second multilink device on an activated link, wherein the fourth PPDU indicates that the first station corresponding to the link is activated; A method that includes this.

8. The method according to claim 4, further: A method comprising the step of transmitting a fifth PPDU, wherein the fifth PPDU includes a wake-up delay field, the wake-up delay field indicating a delay for the first station to switch to an awakened state.

9. The method according to claim 8, wherein the fifth PPDU further includes a power saving operation support field, the power saving operation support field indicating whether the wake-up delay field is present.

10. The method according to claim 4, further: Steps in which the first station switches from awake state to dose state when a fourth instruction is received and the fourth instruction is set to 0; or If the channel is idle, the first station switches from an awake state to a dozed state; A method that includes this.

11. The method according to claim 10, wherein the first PPDU includes a more data field.

12. The method according to claim 1, further: A step of transmitting a reduced neighborhood report element, wherein a target beacon transmission time information set field corresponding to the first station and located within the reduced neighborhood report element carries a multilink device parameter field, the target beacon transmission time information length is set to a first length value, and as a result the legacy station ignores the first station; or A step of transmitting a reduced neighborhood report element, wherein the target beacon transmission time information field type corresponding to the first station and located within the reduced neighborhood report element is set to a value of the first type, so that the legacy station ignores the first station; A method that includes this.

13. The method according to claim 1, further: The steps include transmitting a sixth PPDU, the sixth PPDU carrying fifth instruction information, the fifth instruction information indicating that the transmission is permitted outside the service period or that the transmission is not permitted outside the service period; and / or A method wherein the first PPDU includes a power management mode field, and the power management mode field further indicates a periodic power saving mode.

14. A communication device which is an access point multilink device or is applied to an access point multilink device, comprising at least one processor, wherein the at least one processor is coupled to memory; The memory is configured to store programs or instructions; and The communication device is configured such that the at least one processor is configured to execute the program or instructions stored in the memory, and as a result the device performs the method according to any one of claims 1 to 13.

15. A computer-readable storage medium containing a program or instruction, wherein when the program or instruction is executed, the method according to any one of claims 1 to 13 is executed.

16. A computer program wherein, when the computer program is executed on a computer, the method described in any one of claims 1 to 13 is executed.

17. A communication system including a multilink device configured to perform the method described in any one of claims 1 to 13.

18. A chip system comprising at least one processor and memory, wherein the at least one processor is coupled to the memory, the memory is configured to store a program or instruction, and when the program or instruction is executed by the processor, the method according to any one of claims 1 to 13 is performed.

Images