Data transmission method, apparatus, and device

Abstract

The present application provides a data transmission method, an apparatus, and a device. The method comprises: generating a wake-up token management instruction; sending the wake-up token management instruction to a target station device (target Non-AP MLD) having a quality of service request among a multiple link station device (Non-AP MLD), wherein the wake-up token management instruction carries wake-up token management parameters allocated by an AP MLD to the target Non-AP MLD on the basis of the quality of service request, and the wake-up token management instruction is used for managing a wake-up request from the target Non-AP MLD to the AP MLD.

Description

Data transmission methods, apparatus and equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 2025100634946, filed on January 15, 2025, entitled “Data Transmission Method, Apparatus and Device”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communications, and more specifically, to a data transmission method, apparatus, and device. Background Technology

[0004] Energy saving addresses the issue of wireless network devices consuming unnecessary power during inactive periods such as when the network is not in use or when network traffic is low. Its goal is to optimize device behavior, enabling it to flexibly switch between active and energy-saving modes to adapt to different scenarios, thereby minimizing energy consumption and extending the battery life of access point (AP) and non-AP station (STA) devices.

[0005] In the 802.11be protocol standard, devices with multi-link simultaneous transmission are called multiple link devices (MLDs). Among them, APs with multi-link functionality are called access point multiple link devices (AP MLDs), and site devices with multi-link functionality are called non-AP STA multiple link devices (Non-AP MLDs). Traditional technology proposes an unscheuduled AP MLD power save mechanism to achieve energy savings for the AP MLD, as shown in Figure 1. The principle of this unscheuduled AP MLD power save mechanism is to keep only one link active (link1 in Figure 1), while the remaining links are in a dormant state. The dormant links do not have the function of receiving / transmitting data. The Non-AP MLD wakes up other links by sending a wake-up request through the active link to enable data transmission with the AP MLD. For example, in Figure 1, the Non-AP MLD wakes up AP2 in the AP MLD, thus enabling data transmission on link2.

[0006] The unplanned AP MLD energy-saving mechanism achieves good energy-saving effect when there is less device data associated with the AP MLD. However, if it is applied to regular infrastructure AP MLD, the large number of non-AP MLDs associated with the AP MLD may lead to abuse of the wake-up mechanism, thus affecting the final energy-saving effect. Summary of the Invention

[0007] This application provides a data transmission method, apparatus, and device.

[0008] Firstly, a data transmission method is provided, applied to a multi-link access point device (AP MLD), the method comprising:

[0009] Generate wake-up token management instructions;

[0010] The wake-up token management instruction is sent to the target site device (Non-AP MLD) with a quality of service request in the multi-link site device (Non-AP MLD). The wake-up token management instruction carries the wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request. The wake-up token management instruction is used to manage the wake-up request of the target Non-AP MLD to the AP MLD.

[0011] In some embodiments, the wake-up token management parameters include the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, and the time unit;

[0012] The initial wake-up token count is used to indicate the initial wake-up count of the target Non-AP MLD to the AP MLD;

[0013] The maximum number of wake-up tokens is used to indicate the maximum number of times the target Non-AP MLD can wake up the AP MLD;

[0014] The wake-up token recovery rate is used to indicate the recovery rate between wake-up tokens to the target Non-AP MLD;

[0015] The time unit is used to indicate the recovery rate.

[0016] In some embodiments, the wake-up token management parameters further include a wake-up token validity period, used to indicate the valid usage time of the wake-up token to the target Non-AP MLD.

[0017] In some embodiments, the wake-up token management parameters include an exponent of the effective time and a tail of the effective time.

[0018] The validity period of the wake-up token is determined based on the validity period index, the validity period tail number, and the time unit, wherein the time unit is also used to indicate the unit of the validity period of the wake-up token.

[0019] In some embodiments, the wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD.

[0020] In some embodiments, the wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the quality of service request of the target Non-AP MLD, is the optimal link indicated by the target Non-AP MLD.

[0021] In some embodiments, the wake-up token management instruction also carries control information to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

[0022] In some embodiments, after sending the wake-up token management instruction to the target site device (Non-AP MLD) with a quality of service request in the Non-AP MLD, the method further includes:

[0023] Receive the wake-up request sent by the target Non-AP MLD according to the wake-up token management instruction;

[0024] Receive the target data transmitted by the target Non-AP MLD on its requested wake-up link.

[0025] In some embodiments, after sending the wake-up token management instruction to the target site device (Non-AP MLD) with a quality of service request in the Non-AP MLD, the process includes:

[0026] The wake-up token management parameters are updated based on preset update trigger conditions, and the updated wake-up token management parameters are sent to the target Non-AP MLD.

[0027] In some embodiments, the preset update triggering condition includes at least one of the following:

[0028] Monitor the number and / or frequency of wake-up token consumption by the target Non-AP MLD to reach a preset threshold;

[0029] The service quality update request reported by the target Non-AP MLD was received.

[0030] In some embodiments, updating the wake-up token management parameters includes at least one of the following:

[0031] Allocate a new initial wake-up token quantity, obtain the remaining wake-up token quantity of the target Non-AP MLD when the preset update trigger condition occurs, and calculate the updated initial wake-up token quantity based on the new initial wake-up token quantity and the remaining wake-up token data;

[0032] The wake-up token recovery rate and / or the wake-up token validity period are adjusted to obtain the adjusted wake-up token recovery rate and / or wake-up token validity period.

[0033] In some embodiments, prior to generating the wake-up token management instruction, the following steps are included:

[0034] Receive the quality of service request sent by the target Non-AP MLD.

[0035] In some embodiments, the quality of service request includes at least one of the following parameters:

[0036] Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD;

[0037] Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD;

[0038] Delay boundary, used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD;

[0039] Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD;

[0040] Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

[0041] Secondly, a data transmission method is provided, applied to a target Non-AP MLD with a Quality of Service (QoS) request in a Non-AP MLD, the method comprising:

[0042] Receive a wake-up token management instruction sent by the AP MLD, wherein the wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request;

[0043] A wake-up request is sent to the AP MLD according to the wake-up token management instruction.

[0044] In some embodiments, the wake-up token management parameters include the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, and the time unit;

[0045] The initial wake-up token count is used to indicate the initial wake-up count of the target Non-AP MLD to the AP MLD;

[0046] The maximum number of wake-up tokens is used to indicate the maximum number of times the target Non-AP MLD can wake up the AP MLD;

[0047] The wake-up token recovery rate is used to indicate the recovery rate between wake-up tokens to the target Non-AP MLD;

[0048] The time unit is used to indicate the recovery rate.

[0049] In some embodiments, the wake-up token management parameters further include a wake-up token validity period, used to indicate the valid usage time of the wake-up token for the target Non-AP MLD.

[0050] In some embodiments, the wake-up token management parameters include an exponent of the effective time and a tail of the effective time.

[0051] The validity period of the wake-up token is determined based on the validity period index, the validity period tail number, and the time unit, wherein the time unit is also used to indicate the unit of the validity period of the wake-up token.

[0052] In some embodiments, the wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD.

[0053] In some embodiments, the wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the quality of service request of the target Non-AP MLD, is the optimal link indicated by the target Non-AP MLD.

[0054] In some embodiments, the wake-up token management instruction also carries control information to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

[0055] In some embodiments, after sending a wake-up request to the AP MLD according to the wake-up token management instruction, the process includes:

[0056] The target data is transmitted to the AP MLD via the wake-up link requested by the target Non-AP MLD.

[0057] In some embodiments, after receiving the wake-up token management instruction sent by the AP MLD, the process includes:

[0058] The AP MLD receives an updated wake-up token management instruction, which includes updated wake-up token management parameters. The updated wake-up token management parameters are obtained by the AP MLD updating the wake-up token management parameters based on preset update trigger conditions.

[0059] In some embodiments, prior to receiving the wake-up token management instruction sent by the AP MLD, the process includes:

[0060] Send the quality of service request to the AP MLD;

[0061] The quality of service request includes at least one of the following parameters:

[0062] Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD;

[0063] Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD;

[0064] Delay boundary, used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD;

[0065] Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD;

[0066] Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

[0067] In some embodiments, the method further includes:

[0068] After each data transmission with the AP MLD is completed, the number of initial wake-up tokens allocated by the AP MLD is decremented by 1.

[0069] Thirdly, a data transmission device is provided, comprising:

[0070] The generation module is used to generate wake-up token management instructions;

[0071] The sending module is used to send a wake-up token management instruction to a target Non-AP MLD with a quality of service request in a multi-link site device (Non-AP MLD). The wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request. The wake-up token management instruction is used to manage the wake-up request of the target Non-AP MLD to the AP MLD.

[0072] Fourthly, a data transmission device is provided, comprising:

[0073] The receiving module is used to receive a wake-up token management instruction sent by the AP MLD. The wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on a quality of service request. The quality of service request is sent by the target Non-AP MLD in the Non-AP MLD.

[0074] The wake-up request module is used to send a wake-up request to the AP MLD according to the wake-up token management instruction.

[0075] Fifthly, an access point device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the methods described in the first aspect or its various implementations.

[0076] In a sixth aspect, a site device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to perform the methods in the second aspect or its implementations described above.

[0077] In a seventh aspect, a chip is provided for implementing the methods of any one of the first to second aspects or their respective implementations. Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the methods of any one of the first to second aspects or their respective implementations.

[0078] Eighthly, a readable storage medium is provided for storing a computer program that causes a computer to perform the methods of any one of the first to second aspects or their respective implementations.

[0079] A ninth aspect provides a communication device, comprising: a processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the methods of any one of the first to second aspects or their respective implementations.

[0080] In a tenth aspect, a communication system is provided, including an access point device and a terminal device, wherein the access point device is configured to perform the method of any one of the first aspects or its implementations described above, and the terminal device is configured to perform the method of any one of the second aspects or its implementations described above.

[0081] The above technical solution generates and sends a wake-up token management instruction to a target Non-AP MLD with a quality of service request within the Non-AP MLD. This wake-up token management instruction then manages the wake-up requests from the target Non-AP MLD to the AP MLD. Since the wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request, such as allocating a larger number of wake-up tokens indicating the number of wake-up requests to Non-AP MLDs with critical data transmission based on the quality of service request, and allocating very few or no wake-up tokens to Non-AP MLDs with low-priority data transmission that is not real-time, it can achieve refined and differentiated management of different target Non-AP MLDs. This can avoid the problem of Non-AP MLDs abusing wake-up requests to AP MLDs in dense device scenarios while taking into account quality of service, thus improving the energy-saving effect of the unplanned AP MLD energy-saving mechanism. Attached Figure Description

[0082] Figure 1 is a schematic diagram of data transmission interaction in an embodiment of the unplanned AP MLD energy-saving mechanism.

[0083] Figure 2 is a schematic diagram of a communication system applicable to an embodiment of this application.

[0084] Figure 3 is one of the interactive schematic diagrams of a data transmission method provided in an embodiment of this application.

[0085] Figure 4 is a schematic diagram of the frame structure of the wireless network management action frame provided in an embodiment of this application.

[0086] Figure 5 is a schematic diagram of the frame structure of the wake-up token management element field provided in an embodiment of this application.

[0087] Figure 6 is a second interactive schematic diagram of a data transmission method provided in an embodiment of this application.

[0088] Figure 7 is one of the schematic block diagrams of a data transmission device provided according to an embodiment of this application.

[0089] Figure 8 is a second schematic block diagram of a data transmission device provided according to an embodiment of this application.

[0090] Figure 9 is a schematic block diagram of a communication device provided according to an embodiment of this application.

[0091] Figure 10 is a schematic block diagram of a chip provided according to an embodiment of this application.

[0092] Figure 11 is a schematic block diagram of a communication system provided according to an embodiment of this application. Detailed Implementation

[0093] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.

[0094] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Furthermore, the terms "first" and "second," etc., used herein are used only to distinguish different objects and not to describe a particular order.

[0095] It should be noted that, in the embodiments of this application, "at least one item" refers to one item or more items, "more items" refers to two items or more, and "at least two items" refers to two items or more. "At least one of the following items" or similar expressions can refer to any combination of these items. For example, at least one item of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0096] It should be noted that in the embodiments of this application, "and / or" indicates that the connected objects can have three relationships. For example, "A and / or B" can represent three scenarios: only A exists, only B exists, and both A and B exist simultaneously. The character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0097] It should be understood that the "instruction" mentioned in the embodiments of this application can be a direct instruction or an indirect instruction. For example, A instructing B can mean that A directly instructs B, such as B being obtainable through A; or it can mean that A indirectly instructs B, such as A instructing C, where B is obtainable through C, for example, B and C are related.

[0098] The technical solutions provided in this application can be applied to wireless local area network (WLAN) systems, such as WiFi protocols. These WiFi protocols may include, but are not limited to, the 802.11 series protocols, such as 802.11a, 802.11ax, 802.11ac, 802.11b, 802.11be, 802.11g, 802.11n, 802.11bn, or next-generation protocols.

[0099] Figure 2 shows a schematic structural diagram of a communication system 100 applicable to an embodiment of this application. The communication system 100 may include an access point device 110 and a site device 120. The site device 120 can access the network through the access point device 110.

[0100] Access points can support communication or sensing based on WiFi protocols, such as 802.11a, 802.11ax, 802.11ac, 802.11b, 802.11be, 802.11g, 802.11n, 802.11bn, or next-generation protocols.

[0101] The site can support communication or sensing based on WiFi protocols, such as 802.11a, 802.11ax, 802.11ac, 802.11b, 802.11be, 802.11g, 802.11n, 802.11bn, or next-generation protocols.

[0102] The communication in the communication system 100 can be communication between access points and stations, or communication between stations, or communication between access points.

[0103] An access point acts as a bridge connecting wired and wireless networks. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet.

[0104] Site equipment is also called a site or non-access point site or non-access point node, and access point equipment is also called an access point or access point site or access point node. In other words, in a sense, an access point is also a type of site.

[0105] In some scenarios, access points and sites can be devices used in vehicle networking, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0106] In some scenarios, the access point can be a terminal device (such as a mobile phone) with a WiFi chip or a network device (such as a router).

[0107] In this application embodiment, the site can be a mobile phone, tablet computer, computer, virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control, set-top box, wireless device in self-driving, vehicle communication device, wireless device in remote medical, wireless device in smart grid, wireless device in transportation safety, wireless device in smart city or smart home, wireless device, wireless communication chip, etc. that support WLAN or WiFi technology.

[0108] It should be understood that Figure 2 only illustrates one access point and two sites. Optionally, the communication system 100 may include multiple access points or other numbers of sites, which is not limited in this embodiment.

[0109] Optionally, the communication system 100 may also include other devices, such as network controllers, gateways, and other network entities, which are not limited in this application.

[0110] To facilitate understanding of the embodiments of this application, the related technologies are described.

[0111] As shown in Figure 1, a data transmission method based on the unplanned AP MLD power saving mechanism is provided. In this unplanned AP MLD power saving mechanism, only link1 (2.4GHz) is active, while the other links are in a dormant state. The Non-AP MLD sends a wake-up request to the AP MLD through link1. The wake-up request can exist in the UL PPDU with AAR (uplink physical layer protocol data unit carrying AAR) shown in Figure 1. When the AP MLD receives the wake-up request, it replies with an acknowledgment frame (Block Ack, abbreviated as BA) to the Non-AP MLD. The AP MLD and the Non-AP MLD then transmit data on the awakened link (Link2). This unplanned AP MLD power-saving mechanism achieves good energy savings when the data associated with the AP MLD is relatively small. However, when applied to regular infrastructure AP MLDs, due to the large number of Non-AP MLDs associated with each AP MLD, the wake-up behavior of Non-AP MLDs may be abused if not managed properly. For example, a Non-AP MLD with only a small amount of data or low-priority uplink traffic might still request to wake up the 6GHz band (maximum bandwidth up to 320MHz), resulting in significant bandwidth waste and ultimately impacting energy-saving performance. Furthermore, if other Non-AP MLDs have higher-priority traffic requiring more bandwidth, this will cause unnecessary waiting delays for them.

[0112] The technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, all of which fall within the protection scope of the embodiments of this application.

[0113] Figure 3 is an interactive schematic diagram of the data transmission method according to an embodiment of this application. The method is applied to a multi-link access point device (AP MLD) and includes:

[0114] S110, Generate wake-up token management instructions.

[0115] S120, a wake-up token management instruction is sent to the target Non-AP MLD with a quality of service request in the multi-link site device Non-AP MLD. The wake-up token management instruction carries the wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request. The wake-up token management instruction is used to manage the wake-up request of the target Non-AP MLD to the AP MLD.

[0116] The data transmission method provided in this application generates and sends a wake-up token management instruction to a target Non-AP MLD with a quality of service request in a Non-AP MLD. This wake-up token management instruction then manages the wake-up requests from the target Non-AP MLD to the AP MLD. Since the wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request, such as allocating a larger number of wake-up tokens indicating the number of wake-up requests to Non-AP MLDs with critical data transmission based on the quality of service request, and allocating very few or no wake-up tokens to Non-AP MLDs with low-priority, non-real-time data transmission, it enables refined and differentiated management of different target Non-AP MLDs. This approach can avoid the problem of Non-AP MLDs abusing wake-up requests to AP MLDs in densely populated device scenarios while maintaining quality of service, thus improving the energy-saving effect of unplanned AP MLD energy-saving mechanisms.

[0117] It should be noted that the number of wakeup tokens represents the number of times the Non-AP MLD can wake up the AP MLD, that is, the number of times the Non-AP MLD can transmit data with the AP MLD. For example, in some embodiments, each wakeup token only allows the Non-AP MLD to send a wakeup request to the AP MLD once, thereby transmitting data with the AP MLD. Therefore, the wakeup request behavior of the Non-AP MLD to the AP MLD can be controlled by allocating a certain number of wakeup tokens to the Non-AP MLD. The wakeup token recovery rate represents the recovery rate of the wakeup token. If the Non-AP MLD wants to send a wakeup request to the AP MLD, but the wakeup token has not yet recovered, the wakeup request is not allowed to be sent, which also enables the control of the Non-AP MLD's wakeup request behavior to the AP MLD. It can be understood that the wakeup token management parameters include the number of wakeup tokens and the wakeup token recovery rate, thus enabling the control of the Non-AP MLD's wakeup behavior.

[0118] It is understood that the AP MLD generates wake-up token management instructions based on a quality of service request sent by the target Non-AP MLD. In some embodiments, step S110 includes receiving the quality of service request sent by the target Non-AP MLD. This quality of service request includes at least one of the following parameters:

[0119] Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD.

[0120] Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD.

[0121] Delay boundary, used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD.

[0122] Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD.

[0123] Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

[0124] These parameters will be used when the AP MLD assigns wake-up token management parameters to the target Non-AP MLD, such as: determining the initial number of wake-up tokens based on traffic identification information, minimum data rate, and latency boundary; and determining the wake-up token recovery rate based on the minimum service interval and maximum service interval.

[0125] Specifically, in some implementations, Traffic Identifier (TID) information can divide data services into 8 levels, using TID 0 to 7 to represent the priority of different service types. The larger the TID value, the higher the priority. The initial number of Wakeup Tokens and the maximum number of Wakeup Tokens can be allocated according to the TID value. The higher the priority, the more initial Wakeup Tokens are allocated and the larger the maximum number of Wakeup Tokens is set.

[0126] Minimum Data Rate: This represents the minimum data transmission rate (in kbps) required by the target Non-AP MLD to transmit the target data. It indicates the minimum bandwidth guarantee required for the target data. If this value is greater than a certain threshold, the AP MLD can determine that the Non-AP MLD has a greater need to wake up a high-bandwidth link. The initial number of Wakeup Tokens can be allocated based on this parameter.

[0127] Delay Bound: The maximum allowable latency (in µs) for the target Non-AP MLD to transmit target data; ensuring that real-time service data (such as voice, video calls, or online games) can be processed with low latency in the network. The initial and maximum number of Wakeup Tokens can be allocated based on the delay boundary.

[0128] Minimum Service Interval: This represents the shortest time interval (in microseconds) between two target data transmissions. A shorter minimum service interval means that data transmissions occur more frequently, requiring a faster Wakeup Token recovery rate. It can determine the minimum Wakeup Token recovery rate.

[0129] Maximum Service Interval: Represents the longest time interval (in microseconds) between two target data transmissions; combined with the minimum service interval, a suitable Wakeup Token recovery rate is determined.

[0130] In some embodiments, the Quality of Service (QoS) request is carried in a Probe Request frame or a (Re)Association Request frame; the Wake-up Token Management instruction is carried in a Radio Network Management Action frame. Utilizing existing frame structures to transmit QoS requests and Wake-up Token Management instructions simplifies the design complexity.

[0131] In some embodiments, the wake-up token management parameters include an initial number of wake-up tokens, a maximum number of wake-up tokens, a wake-up token recovery rate, and a time unit. The initial number of wake-up tokens indicates the initial number of times the target Non-AP MLD will wake up the AP MLD. The maximum number of wake-up tokens indicates the maximum number of times the target Non-AP MLD will wake up the AP MLD. The wake-up token recovery rate indicates the recovery rate between wake-up tokens to the target Non-AP MLD. The time unit indicates the unit of the recovery rate.

[0132] As mentioned earlier, the wake-up token management parameters include the allocation of wake-up token quantity. More specifically, these parameters include the initial wake-up token quantity and the maximum wake-up token quantity, as well as the wake-up token recovery rate and time unit. The initial wake-up token quantity indicates the number of initial wake-ups the target Non-AP MLD will make to the AP MLD. This quantity can be determined based on information such as traffic identification information, minimum data rate, and latency boundaries in the service quality requests reported by the target Non-AP MLD. For example, a larger initial wake-up token quantity can be allocated to high-priority, high-transmission-rate, and low-latency target Non-AP MLDs, while a smaller initial wake-up token quantity can be allocated to low-priority, low-transmission-rate, and high-latency target Non-AP MLDs. This ensures service quality for different target Non-AP MLDs while managing wake-up requests from different target Non-AP MLDs, preventing the abuse of wake-up requests. The maximum number of wake-up tokens indicates the maximum number of times a target Non-AP MLD can wake up an AP MLD. This can be determined based on traffic identification information in the service quality requests reported by the target Non-AP MLD. For example, the maximum number of wake-up tokens can be allocated to high-priority target Non-AP MLDs, a medium number to medium-priority targets, and fewer to low-priority targets. The goal of the maximum number of wake-up tokens is to limit the total number of wake-up tokens held by a target Non-AP MLD, effectively preventing low-priority traffic from accumulating too many wake-up tokens and frequently waking up the link in a short period, interfering with the normal data transmission of other Non-AP MLDs, and especially avoiding impacting the data transmission of high-priority traffic. The wake-up token recovery rate is used to indicate the recovery rate between wake-up tokens to the target Non-AP MLD. It can be determined based on information such as the minimum service interval and maximum service interval in the service quality requests reported by the target Non-AP MLD. For example, if the maximum service interval is very small, a faster wake-up token recovery rate is assigned to that target Non-AP MLD. Assigning different wake-up token recovery rates to different target Non-AP MLDs ensures the service quality of target Non-AP MLDs with different transmission frequencies and prevents the abuse of wake-up requests. The time unit is used to indicate the unit of recovery rate; for example, the unit indicating the recovery rate is units per microsecond (µs), thus ensuring the consistency and accuracy of the recovery rate.

[0133] In some embodiments, the wake-up token management parameters further include a wake-up token validity period, used to indicate the valid usage time of the wake-up token to the target Non-AP MLD.

[0134] In this embodiment, by setting the validity period of the wake-up token, wake-up tokens that have not been used within the validity period can be reclaimed, thereby achieving automatic cleanup of wake-up tokens that have not been used within the validity period, reducing the management overhead of wake-up tokens, and ensuring that network resources are dynamically optimized.

[0135] It's worth noting that the wake-up token validity period can be determined based on the traffic identification information in the service quality request reported by the target Non-AP MLD and the network load of the currently active links. For example, a longer wake-up token validity period can be allocated to high-priority traffic with low network load on currently active links, thus fully utilizing network links and ensuring service quality.

[0136] In some embodiments, the wake-up token management parameters include an effective time index and an effective time tail. The wake-up token's effective time is determined based on the effective time index, the effective time tail, and the time unit, wherein the time unit is also used to indicate the unit of the wake-up token's effective time.

[0137] Furthermore, in some implementations, Among them, t 有效 The value t represents the validity period of the wake-up token. 指数 The value of t represents the effective time exponent. 尾数 The value represents the last digit of the valid time, and the time unit indicates the time unit; in some embodiments, the time unit is microseconds (µs). The wake-up token validity time calculated using this formula is more accurate.

[0138] In some implementations, the wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD.

[0139] Furthermore, in some embodiments, the wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the quality of service request of the target Non-AP MLD, is the optimal link indicated by the target Non-AP MLD.

[0140] In this embodiment, when the AP MLD sends a wake-up token management command to the target Non-AP MLD, it also sends the link identifier of the optimal link recommended based on link interference information, link power consumption information, and quality of service request to the target Non-AP MLD, so that the target Non-AP MLD can select a wake-up link. It is understood that when the target Non-AP MLD sends a wake-up request to the AP MLD, it can choose to use the optimal link or not, and instead use another link as the wake-up link. The wake-up request carries the link identifier of the wake-up link selected by the target Non-AP MLD.

[0141] In some embodiments, the wake-up token management instruction also carries control information to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

[0142] In some specific implementations, a single bit can be used to represent a parameter. A bit value of 1 indicates that the corresponding parameter exists, while a bit value of 0 indicates that the corresponding parameter does not exist. This further ensures the validity of each parameter.

[0143] In some embodiments, the wake-up token management instruction is carried in a Wireless Network Management Action Frame (WNM Action Frame). The frame structure of this WNM Action Frame is shown in Figure 4. A Type setting of 3 indicates that the wake-up token management instruction is carried in the WNM Token Management element field. Upon receiving the wake-up token management instruction, the target Non-AP MLD replies with an existing WNM Notification Response frame to acknowledge receipt of the instruction.

[0144] Specifically, in some embodiments, the specific format of the wake-up token management element field is shown in Figure 5. The initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity time, the time unit, and the wake-up link information can be represented as shown in Table 1 below:

[0145] Table 1

[0146] In some embodiments, after step S120, the method further includes:

[0147] Receive the wake-up request sent by the target Non-AP MLD according to the wake-up token management instruction.

[0148] Receive the target data transmitted by the target Non-AP MLD on its requested wake-up link.

[0149] After receiving the wake-up token management command from the AP MLD, if the AP MLD has enabled the unplanned power saving scheme and the Non-AP MLD needs to wake up the dormant link for uplink data transmission, it will send a wake-up request to the AP MLD based on the wake-up token management command. Each time a wake-up request is sent and the uplink data transmission is completed, an initial wake-up token is consumed. If the accumulated wake-up tokens exceed the maximum number of wake-up tokens, the maximum number of wake-up tokens will be maintained and will not be increased. When the wake-up token validity period expires, the unused initial wake-up tokens within the validity period will be cleared. In this way, the wake-up behavior of the target Non-AP MLD can be managed, and the overhead of managing wake-up tokens can be reduced.

[0150] The wake-up request carries the wake-up link identifier selected by the target Non-AP MLD. This wake-up link can be the optimal link indicated by the AP MLD to the target Non-AP MLD, or it can be another link among multiple links. After receiving the wake-up request, the AP MLD changes the status of the corresponding wake-up link from the sleep state to the wake-up state (if it was previously in the wake-up state, it remains in the wake-up state), so that the target Non-AP MLD can transmit target data to the AP MLD from this wake-up link.

[0151] In some embodiments, after step S120, the method further includes:

[0152] The wake-up token management parameters are updated based on preset update trigger conditions, and the updated wake-up token management parameters are sent to the target Non-AP MLD.

[0153] In some embodiments, the preset update triggering conditions include at least one of the following:

[0154] Monitor the number and / or frequency of wake-up token consumption by the target Non-AP MLD to reach a preset threshold.

[0155] The service quality update request reported by the target Non-AP MLD was received.

[0156] In some embodiments, updating the wake-up token management parameters includes at least one of the following:

[0157] Allocate a new initial wake-up token quantity, obtain the remaining wake-up token quantity of the target Non-AP MLD when the preset update trigger condition occurs, and calculate the updated initial wake-up token quantity based on the new initial wake-up token quantity and the remaining wake-up token data.

[0158] The wake-up token recovery rate and / or the wake-up token validity period are adjusted to obtain the adjusted wake-up token recovery rate and / or wake-up token validity period.

[0159] To better manage the wake-up behavior of the target Non-AP MLD, the wake-up token management parameters assigned to the target Non-AP MLD are not static, but change according to the consumption of wake-up tokens and the changes in the target Non-AP MLD's own needs. It should be noted that parameters such as traffic identification information, minimum data rate, and latency boundaries are initial configurations reported in advance by the Non-AP MLD. These parameters may change dynamically due to business adjustments, and therefore will be updated based on timely reports from the Non-AP MLD or adjusted according to the AP MLD's perception.

[0160] For example, when the number of wake-up tokens consumed by the target Non-AP MLD far exceeds the preset threshold, or the number of consumptions is far less than the preset threshold, or when the frequency of the target Non-AP MLD consuming its initial wake-up tokens to zero is greater than the preset threshold, or when a service quality update request is received from the target Non-AP MLD (e.g., a smaller latency boundary), the wake-up token management parameters are updated. It can be understood that if the number of wake-up tokens consumed by the target Non-AP MLD far exceeds the preset threshold, or the frequency of the target Non-AP MLD consuming all its wake-up tokens exceeds the preset threshold, it indicates that the service quality requirements of the target Non-AP MLD are not met. Therefore, the number of initial wake-up tokens allocated to the target Non-AP MLD is increased, and the wake-up token recovery rate is increased to meet the service quality requirements of the target Non-AP MLD. The increased number of initial wake-up tokens and the increased wake-up token recovery rate are updated in the wake-up token management parameters and sent to the target Non-AP MLD so that the target Non-AP MLD can use the updated wake-up token management parameters to request wake-up from the AP MLD. Understandably, if the latency boundary of the target Non-AP MLD decreases (requiring higher latency) or the maximum service interval decreases (increasing the frequency of target data transmission), the original wake-up token recovery rate may not meet the service quality requirements of the target Non-AP MLD. Therefore, it is necessary to increase the wake-up token recovery rate and issue it to the target Non-AP MLD. Understandably, if a decrease in the priority reported by the target Non-AP MLD is detected, the wake-up token validity period can be reduced to reduce the resource overhead of managing wake-up tokens and improve resource utilization.

[0161] In some specific embodiments, updating the initial wake-up token count may include: allocating a new initial wake-up token count, obtaining the remaining wake-up token count of the target Non-AP MLD when a preset update trigger condition occurs, and calculating the sum of the new initial wake-up token count and the remaining wake-up token count as the updated initial wake-up token count, so as to make full use of the allocated wake-up tokens. It is worth noting that if the sum of the new initial wake-up token count and the remaining wake-up token count is greater than the maximum wake-up token count, then the maximum wake-up token count is used as the updated initial wake-up token count to avoid the target Non-AP MLD accumulating too many wake-up tokens, affecting other Non-AP MLDs. In some specific embodiments, updating the initial wake-up token count may include: allocating a new initial wake-up token count, using the new initial wake-up token count to update the wake-up token count of the target Non-AP MLD, that is, directly using the new initial wake-up token count as the wake-up token count of the target Non-AP MLD, thus avoiding the situation where the wake-up token count exceeds the maximum wake-up token count.

[0162] This application embodiment also provides a data transmission method, which is applied to a target Non-AP MLD with a quality of service request in a Non-AP MLD. Referring to Figure 6, the method includes the following:

[0163] S210, receive a wake-up token management instruction sent by the AP MLD, the wake-up token management instruction carrying wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request.

[0164] S220, a wake-up request is sent to the AP MLD according to the wake-up token management instruction.

[0165] The data transmission method provided in this application receives a wake-up token management instruction sent by the AP MLD and sends a wake-up request to the AP MLD based on the wake-up token management instruction. Since the wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request, the wake-up token management parameters can manage the wake-up request behavior of the target Non-AP MLD. For example, according to the quality of service request, a larger number of wake-up tokens indicating the number of wake-up requests can be allocated to Non-AP MLDs with critical data transmission, while very few or no wake-up tokens can be allocated to Non-AP MLDs with low-priority data transmission that is not real-time. Therefore, it can realize fine-grained and differentiated management of different target Non-AP MLDs. While taking into account the quality of service, it can avoid the problem of Non-AP MLD abusing the wake-up of AP MLD in device-dense scenarios, and improve the energy-saving effect of the unplanned AP MLD energy-saving mechanism.

[0166] It should be noted that the number of wakeup tokens represents the number of times the Non-AP MLD can wake up the AP MLD, that is, the number of times the Non-AP MLD can transmit data with the AP MLD. For example, in some embodiments, each wakeup token only allows the Non-AP MLD to send a wakeup request to the AP MLD once, thereby transmitting data with the AP MLD. Therefore, the wakeup request behavior of the Non-AP MLD to the AP MLD can be controlled by allocating a certain number of wakeup tokens to the Non-AP MLD. The wakeup token recovery rate represents the recovery rate of the wakeup token. If the Non-AP MLD wants to send a wakeup request to the AP MLD, but the wakeup token has not yet recovered, the wakeup request is not allowed to be sent, which also enables the control of the Non-AP MLD's wakeup request behavior to the AP MLD. It can be understood that the wakeup token management parameters include the number of wakeup tokens and the wakeup token recovery rate, thus enabling the control of the Non-AP MLD's wakeup behavior.

[0167] In some embodiments, the wake-up token management parameters include an initial number of wake-up tokens, a maximum number of wake-up tokens, a wake-up token recovery rate, and a time unit. The initial number of wake-up tokens indicates the initial number of times the target Non-AP MLD will wake up the AP MLD. The maximum number of wake-up tokens indicates the maximum number of times the target Non-AP MLD will wake up the AP MLD. The wake-up token recovery rate indicates the recovery rate between wake-up tokens to the target Non-AP MLD. The time unit indicates the unit of the recovery rate.

[0168] In some embodiments, the wake-up token management parameters further include a wake-up token validity period, used to indicate the valid usage time of the wake-up token for the target Non-AP MLD.

[0169] In some embodiments, the wake-up token management parameters include an effective time index and an effective time tail. The wake-up token's effective time is determined based on the effective time index, the effective time tail, and the time unit, wherein the time unit is also used to indicate the unit of the wake-up token's effective time.

[0170] In some embodiments, the wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD.

[0171] In some embodiments, the wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the quality of service request of the target Non-AP MLD, is the optimal link indicated by the target Non-AP MLD.

[0172] In some embodiments, the wake-up token management instruction also carries control information to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

[0173] In some embodiments, after step S220, the following is included:

[0174] The target data is transmitted to the AP MLD via the wake-up link requested by the target Non-AP MLD.

[0175] In some embodiments, after step S210, the following is included:

[0176] The AP MLD receives an updated wake-up token management instruction, which includes updated wake-up token management parameters. The updated wake-up token management parameters are obtained by the AP MLD updating the wake-up token management parameters based on preset update trigger conditions.

[0177] In some embodiments, prior to step S210, the following is included:

[0178] The service quality request is sent to the AP MLD so that the AP MLD generates a wake-up token management instruction based on the following parameters of the service quality request.

[0179] The quality of service request includes at least one of the following parameters:

[0180] Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD.

[0181] Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD.

[0182] Delay boundary, used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD.

[0183] Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD.

[0184] Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

[0185] In some embodiments, the method further includes:

[0186] After each data transmission with the AP MLD is completed, the number of initial wake-up tokens allocated by the AP MLD is decremented by 1.

[0187] The target Non-AP MLD manages its own wake-up token management parameters. For example, after each data transmission with the AP MLD, the target Non-AP MLD decrements its initial wake-up token count by 1. If the count is exhausted (i.e., the number of wake-up tokens held is 0), and the AP MLD has not yet allocated any new wake-up tokens to the target Non-AP MLD, then the target Non-AP MLD is not allowed to initiate a wake-up request to the AP MLD. During this process, from the time the current wake-up token is used up until the next wake-up token is available, a wake-up request to the AP MLD is not allowed.

[0188] It should be understood that the data transmission method applied to the target Non-AP MLD with a quality of service request in the embodiments of this application can achieve the corresponding technical effects of each step of the data transmission method applied to the AP MLD of a multi-link access point device. To avoid repetition, it will not be described again here.

[0189] The method embodiments of this application have been described in detail above with reference to Figures 3 to 6. The device embodiments of this application have been described in detail below with reference to Figures 7 to 11. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be referred to the method embodiments.

[0190] Figure 7 shows a schematic block diagram of a data transmission apparatus 200 according to an embodiment of this application. The data transmission apparatus 200 can be a multi-link access point device, or a component within a multi-link access point device, such as a chip, circuit, or module. The data transmission apparatus 200 of Figure 7 includes:

[0191] The generation module 210 is used to generate wake-up token management instructions.

[0192] The sending module 220 is used to send a wake-up token management instruction to a target Non-AP MLD with a quality of service request in a multi-link site device Non-AP MLD. The wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request. The wake-up token management instruction is used to manage the wake-up request of the target Non-AP MLD to the AP MLD.

[0193] The data transmission device provided in this embodiment generates and sends a wake-up token management instruction to a target Non-AP MLD with a quality of service request in the Non-AP MLD. This wake-up token management instruction then manages the wake-up requests from the target Non-AP MLD to the AP MLD. Since the wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request, for example, allocating a larger number of wake-up tokens indicating the number of wake-up requests to Non-AP MLDs with critical data transmission based on the quality of service request, and allocating very few or no wake-up tokens to Non-AP MLDs with low-priority, non-real-time data transmission, it can achieve refined and differentiated management of different target Non-AP MLDs. This can avoid the problem of Non-AP MLDs abusing wake-up requests to AP MLDs in densely populated device scenarios while maintaining quality of service, thus improving the energy-saving effect of the unplanned AP MLD energy-saving mechanism.

[0194] In some embodiments, the wake-up token management parameters include an initial number of wake-up tokens, a maximum number of wake-up tokens, a wake-up token recovery rate, and a time unit. The initial number of wake-up tokens indicates the initial number of times the target Non-AP MLD will wake up the AP MLD. The maximum number of wake-up tokens indicates the maximum number of times the target Non-AP MLD will wake up the AP MLD. The wake-up token recovery rate indicates the recovery rate between wake-up tokens to the target Non-AP MLD. The time unit indicates the unit of the recovery rate.

[0195] In some embodiments, the wake-up token management parameters further include a wake-up token validity period, used to indicate the valid usage time of the wake-up token to the target Non-AP MLD.

[0196] In some embodiments, the wake-up token management parameters include an effective time index and an effective time tail. The wake-up token's effective time is determined based on the effective time index, the effective time tail, and the time unit, wherein the time unit is also used to indicate the unit of the wake-up token's effective time.

[0197] In some embodiments, the wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD.

[0198] In some embodiments, the wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the quality of service request of the target Non-AP MLD, is the optimal link indicated by the target Non-AP MLD.

[0199] In some embodiments, the wake-up token management instruction also carries control information to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

[0200] In some embodiments, the apparatus further includes a wake-up request receiving module, configured to receive a wake-up request sent by the target Non-AP MLD according to the wake-up token management instruction after sending a wake-up token management instruction to the target site device Non-AP MLD that has a quality of service request in the Non-AP MLD.

[0201] The target data receiving module is used to receive the target data transmitted by the target Non-AP MLD on its requested wake-up link.

[0202] In some embodiments, the device further includes: a first parameter update module, configured to update the wake-up token management parameters based on preset update trigger conditions, and send the updated wake-up token management parameters to the target Non-AP MLD.

[0203] In some embodiments, the preset update triggering condition includes at least one of the following:

[0204] Monitor the number and / or frequency of wake-up token consumption by the target Non-AP MLD to reach a preset threshold.

[0205] The service quality update request reported by the target Non-AP MLD was received.

[0206] The update of the wake-up token management parameters includes at least one of the following:

[0207] Allocate a new initial wake-up token quantity, obtain the remaining wake-up token quantity of the target Non-AP MLD when the preset update trigger condition occurs, and calculate the updated initial wake-up token quantity based on the new initial wake-up token quantity and the remaining wake-up token data.

[0208] The wake-up token recovery rate and / or the wake-up token validity period are adjusted to obtain the adjusted wake-up token recovery rate and / or wake-up token validity period.

[0209] In some embodiments, the first quality of service request module is configured to receive the quality of service request sent by the target Non-AP MLD. The quality of service request includes at least one of the following parameters:

[0210] Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD.

[0211] Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD.

[0212] The delay boundary is used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD.

[0213] Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD.

[0214] Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

[0215] It should be understood that the apparatus 200 according to the embodiments of this application may correspond to the multi-link access point device in the method embodiments of this application, and the various units in the apparatus 200 and the other operations and / or functions described above are respectively for implementing the corresponding processes applied to the multi-link access point device in the embodiments of FIG3 to FIG5. For the sake of brevity, they will not be described in detail here.

[0216] Figure 8 is a schematic block diagram of another data transmission device 300 provided according to an embodiment of this application. The data transmission device 300 can be a multi-link site device, or a component within a multi-link site device, such as a chip, circuit, or module.

[0217] As shown in Figure 8, the data transmission device 300 includes:

[0218] The receiving module 310 is used to receive a wake-up token management instruction sent by the AP MLD. The wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on a quality of service request. The quality of service request is sent by the target Non-AP MLD in the Non-AP MLD.

[0219] The wake-up request module 320 is used to send a wake-up request to the AP MLD according to the wake-up token management instruction.

[0220] The data transmission device provided in this embodiment receives a wake-up token management instruction sent by the AP MLD and sends a wake-up request to the AP MLD based on the wake-up token management instruction. Since the wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request, the wake-up token management parameters can manage the wake-up request behavior of the target Non-AP MLD. For example, according to the quality of service request, a larger number of wake-up tokens indicating the number of wake-up requests can be allocated to Non-AP MLDs with critical data transmission, while very few or no wake-up tokens can be allocated to Non-AP MLDs with low-priority data transmission that is not real-time. Therefore, it can realize fine-grained and differentiated management of different target Non-AP MLDs. While taking into account the quality of service, it can avoid the problem of Non-AP MLD abusing the wake-up of AP MLD in device-dense scenarios, and improve the energy-saving effect of the unplanned AP MLD energy-saving mechanism.

[0221] In some embodiments, the wake-up token management parameters include an initial number of wake-up tokens, a maximum number of wake-up tokens, a wake-up token recovery rate, and a time unit. The initial number of wake-up tokens indicates the initial number of times the target Non-AP MLD will wake up the AP MLD. The maximum number of wake-up tokens indicates the maximum number of times the target Non-AP MLD will wake up the AP MLD. The wake-up token recovery rate indicates the recovery rate between wake-up tokens to the target Non-AP MLD. The time unit indicates the unit of the recovery rate.

[0222] In some embodiments, the wake-up token management parameters further include a wake-up token validity period, used to indicate the valid usage time of the wake-up token for the target Non-AP MLD.

[0223] In some embodiments, the wake-up token management parameters include an effective time index and an effective time tail. The wake-up token's effective time is determined based on the effective time index, the effective time tail, and the time unit, wherein the time unit is also used to indicate the unit of the wake-up token's effective time.

[0224] In some embodiments, the wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD.

[0225] In some embodiments, the wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the quality of service request of the target Non-AP MLD, is the optimal link indicated by the target Non-AP MLD.

[0226] In some embodiments, the wake-up token management instruction also carries control information to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

[0227] In some embodiments, the apparatus further includes a target data transmission module, configured to transmit target data to the AP MLD via the wake-up link requested by the target Non-AP MLD after sending a wake-up request to the AP MLD according to the wake-up token management instruction.

[0228] In some embodiments, the device further includes: a second parameter update module, configured to receive an updated wake-up token management instruction sent by the AP MLD, the updated wake-up token management instruction containing updated wake-up token management parameters; the updated wake-up token management parameters are obtained by the AP MLD updating the wake-up token management parameters based on preset update trigger conditions.

[0229] In some embodiments, the apparatus further includes: a second quality of service request module, configured to send the quality of service request to the AP MLD before receiving the wake-up token management instruction sent by the AP MLD. The quality of service request includes at least one of the following parameters:

[0230] Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD.

[0231] Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD.

[0232] The delay boundary is used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD.

[0233] Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD.

[0234] Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

[0235] In some embodiments, the apparatus further includes a management module, configured to decrement the number of initial wake-up tokens allocated by the AP MLD by 1 each time data transmission with the AP MLD is completed.

[0236] It should be understood that the apparatus 300 according to the embodiments of this application can correspond to the target Non-AP MLD in the method embodiments of this application, and the various units in the apparatus 300 and the other operations and / or functions described above are respectively for implementing the corresponding process of the target Non-AP MLD in the method embodiments shown in FIG6. For the sake of brevity, they will not be described in detail here.

[0237] This application provides an access point device, which includes a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to implement the method applied to the multi-link access point device in this application.

[0238] This application provides a site device, which includes a processor and a memory for storing computer programs. The processor is used to call and run the computer programs stored in the memory to implement the method applied to a target Non-AP MLD in this application.

[0239] Figure 9 is a schematic structural diagram of a communication device 500 provided in an embodiment of this application. The communication device 500 shown in Figure 9 includes a processor 510, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0240] Optionally, as shown in FIG9, the communication device 500 may further include a memory 520. The processor 510 can call and run a computer program from the memory 520 to implement the methods in the embodiments of this application. For example, when the communication device 500 is an access point device, the processor 510 can call and run a computer program from the memory 520 to implement the various steps of the method embodiments executed by the multi-link access point device, achieving the same technical effect. When the communication device 500 is a site device, the processor 510 can call and run a computer program from the memory 520 to implement the various steps of the method embodiments executed by the multi-link target site device, achieving the same technical effect.

[0241] Alternatively, the memory 520 may be a separate device independent of the processor 510, or it may be integrated into the processor 510.

[0242] Optionally, as shown in FIG9, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0243] Optionally, transceiver 530 may include a transmitter and a receiver. Transceiver 530 may further include antennas, and the number of antennas may be one or more.

[0244] Figure 10 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 600 shown in Figure 10 includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0245] Optionally, as shown in FIG10, chip 600 may further include memory 620. Processor 610 can retrieve and run computer programs from memory 620 to implement the methods in the embodiments of this application.

[0246] Alternatively, the memory 620 may be a separate device independent of the processor 610, or it may be integrated into the processor 610.

[0247] Optionally, the chip 600 may also include an input interface 630. The processor 610 can control the input interface 630 to communicate with other devices or chips, for example, to acquire information or data sent by other devices or chips.

[0248] Optionally, the chip 600 may also include an output interface 640. The processor 610 can control the output interface 640 to communicate with other devices or chips, for example, to output information or data to other devices or chips.

[0249] Optionally, the chip can be applied to the access point device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the multi-link access point device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0250] Optionally, the chip can be applied to the site equipment in the embodiments of this application, and the chip can implement the corresponding processes implemented by the multi-link target site equipment in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0251] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0252] Figure 11 is a schematic block diagram of a communication system 700 provided in an embodiment of this application. As shown in Figure 11, the communication system 700 includes an access point device 710 and a site device 720.

[0253] The access point device 710 can be used to implement the corresponding functions implemented by the multi-link access point device in the above method, and the site device 720 can be used to implement the corresponding functions implemented by the multi-link target site device in the above method. For the sake of brevity, these will not be elaborated here.

[0254] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0255] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0256] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0257] This application also provides a readable storage medium storing a computer program that, when executed by a processor, implements the various processes of the above method embodiments.

[0258] Optionally, the readable storage medium can be applied to the access point device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the access point device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0259] Optionally, the readable storage medium can be applied to the site device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the third site device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0260] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the various processes of the above-described method embodiments.

[0261] Optionally, the computer program product can be applied to the access point device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the access point device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0262] Optionally, the computer program product can be applied to the site device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the third site device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0263] This application also provides a computer program. When executed by a processor, this computer program implements the various processes of the above-described method embodiments.

[0264] Optionally, the computer program can be applied to the access point device in the embodiments of this application. The computer program causes the processor to execute the corresponding process implemented by the access point device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0265] Optionally, the computer program can be applied to the site device in the embodiments of this application. The computer program causes the processor to execute the corresponding process implemented by the third site device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0266] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0267] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0268] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0269] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0270] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0271] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0272] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data transmission method, wherein, The method, applied to a multi-link access point (AP) MLD, includes: Generate wake-up token management instructions; The wake-up token management instruction is sent to the target site device (Non-AP MLD) with a quality of service request in the multi-link site device (Non-AP MLD). The wake-up token management instruction carries the wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request. The wake-up token management instruction is used to manage the wake-up request of the target Non-AP MLD to the AP MLD.

2. The method according to claim 1, wherein, The wake-up token management parameters include the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, and the time unit. The initial wake-up token count is used to indicate the initial wake-up count of the target Non-AP MLD to the AP MLD; The maximum number of wake-up tokens is used to indicate the maximum number of times the target Non-AP MLD can wake up the AP MLD; The wake-up token recovery rate is used to indicate the recovery rate between wake-up tokens to the target Non-AP MLD; and The time unit is used to indicate the recovery rate.

3. The method according to claim 2, wherein, The wake-up token management parameters also include a wake-up token validity period, which is used to indicate the valid usage time of the wake-up token to the target Non-AP MLD; The validity period of the wake-up token is determined based on the validity period index, the validity period tail number, and the time unit, wherein the time unit is also used to indicate the unit of the validity period of the wake-up token.

4. The method according to any one of claims 1-3, wherein, The wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD. The wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the target Non-AP MLD's quality of service request, is the optimal link indicated by the target Non-AP MLD.

5. The method according to claim 4, wherein, The wake-up token management instruction also carries control information, which is used to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

6. The method according to any one of claims 1-5, wherein, After sending the wake-up token management instruction to the target site device (Non-AP MLD) with a quality of service request in the Non-AP MLD, the process includes: The wake-up token management parameters are updated based on preset update trigger conditions, and the updated wake-up token management parameters are sent to the target Non-AP MLD.

7. The method according to claim 6, wherein, The preset update triggering conditions include at least one of the following: Monitor the number and / or frequency of wake-up token consumption by the target Non-AP MLD to reach a preset threshold; The service quality update request reported by the target Non-AP MLD was received.

8. The method according to claim 6, wherein, The update of the wake-up token management parameters includes at least one of the following: Allocate a new initial wake-up token quantity, obtain the remaining wake-up token quantity of the target Non-AP MLD when the preset update trigger condition occurs, and calculate the updated initial wake-up token quantity based on the new initial wake-up token quantity and the remaining wake-up token data; The wake-up token recovery rate and / or the wake-up token validity period are adjusted to obtain the adjusted wake-up token recovery rate and / or wake-up token validity period.

9. The method according to any one of claims 1-8, wherein, The quality of service request shall include at least one of the following parameters: Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD; Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD; Delay boundary, used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD; Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD; or, Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

10. A data transmission method, wherein, The method, applied to a target Non-AP MLD with a Quality of Service (QoS) request in a Non-AP MLD, includes: Receive a wake-up token management instruction sent by the AP MLD, wherein the wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request; A wake-up request is sent to the AP MLD according to the wake-up token management instruction.

11. The method according to claim 10, wherein, The wake-up token management parameters include the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, and the time unit. The initial wake-up token count is used to indicate the initial wake-up count of the target Non-AP MLD to the AP MLD; The maximum number of wake-up tokens is used to indicate the maximum number of times the target Non-AP MLD can wake up the AP MLD; The wake-up token recovery rate is used to indicate the recovery rate between wake-up tokens to the target Non-AP MLD; and The time unit is used to indicate the recovery rate.

12. The method according to claim 11, wherein, The wake-up token management parameters also include the wake-up token validity period, which is used to indicate the valid usage time of the wake-up token for the target Non-AP MLD; The validity period of the wake-up token is determined based on the validity period index, the validity period tail number, and the time unit, wherein the time unit is also used to indicate the unit of the validity period of the wake-up token.

13. The method according to any one of claims 10-12, wherein, The wake-up token management instruction also carries wake-up link information, which is used to indicate the optimal link for data transmission to the target Non-AP MLD. The wake-up link information indicates that the AP MLD, based on the link's interference information, the link's power consumption information, and the target Non-AP MLD's quality of service request, is the optimal link indicated by the target Non-AP MLD.

14. The method according to claim 13, wherein, The wake-up token management instruction also carries control information, which is used to indicate the initial number of wake-up tokens, the maximum number of wake-up tokens, the wake-up token recovery rate, the wake-up token validity period, the time unit, and whether the wake-up link information exists.

15. The method according to any one of claims 10-14, wherein, After receiving the wake-up token management instruction sent by the AP MLD, the following is included: The AP MLD receives an updated wake-up token management instruction, which includes updated wake-up token management parameters. The updated wake-up token management parameters are obtained by the AP MLD updating the wake-up token management parameters based on preset update trigger conditions.

16. The method according to any one of claims 10-15, wherein, Before receiving the wake-up token management instruction sent by the AP MLD, the following steps are included: Send the quality of service request to the AP MLD; The quality of service request includes at least one of the following parameters: Traffic identification information is used to indicate the priority information of the target data to be transmitted by the target Non-AP MLD; Minimum data rate, used to indicate the minimum transmission rate required for the target data to be transmitted by the target Non-AP MLD; Delay boundary, used to indicate the maximum allowable delay for the target data to be transmitted by the target Non-AP MLD; Minimum service interval, used to indicate the shortest time interval between two target data transmissions by the target Non-AP MLD; or, Maximum service interval, used to indicate the longest time interval between two target data transmissions by the target Non-AP MLD.

17. A data transmission device, wherein, include: The generation module is used to generate wake-up token management instructions; The sending module is used to send a wake-up token management instruction to a target Non-AP MLD with a quality of service request in a multi-link site device (Non-AP MLD). The wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on the quality of service request. The wake-up token management instruction is used to manage the wake-up request of the target Non-AP MLD to the AP MLD.

18. A data transmission apparatus, wherein, include: The receiving module is used to receive a wake-up token management instruction sent by the AP MLD. The wake-up token management instruction carries wake-up token management parameters allocated by the AP MLD to the target Non-AP MLD based on a quality of service request. The quality of service request is sent by the target Non-AP MLD in the Non-AP MLD. The wake-up request module is used to send a wake-up request to the AP MLD according to the wake-up token management instruction.

19. An access point device, wherein, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1-9.

20. A site device, wherein, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 10-16.

21. A readable storage medium, wherein, Used to store a computer program that causes a computer to perform the method as claimed in any one of claims 1-9, or the method as claimed in any one of claims 10-16.

22. A communication system, wherein, It includes an access point device and a site device, the access point device being used to perform the method as described in any one of claims 1-9, and the site device being used to perform the method as described in any one of claims 10-16.

Images