CN116133151A

CN116133151A - Data transmission method and device and multi-link equipment

Info

Publication number: CN116133151A
Application number: CN202111352572.2A
Authority: CN
Inventors: 顾祥新
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2021-11-12
Filing date: 2021-11-16
Publication date: 2023-05-16
Also published as: WO2023083310A1

Abstract

The application discloses a data transmission method and device and a multi-link device; the method comprises the following steps: acquiring data of a first service and a first time interval; if the reaching time of the data of the first service is in the first time interval, transmitting the data of the first service in a limited target wake-up time service period rTWT SP mode; if the arrival time of the data of the first service is not within the first time interval, transmitting the data of the first service through a multilink redundancy transmission mode. It can be seen that, by introducing the first time interval and determining according to the position relationship between the first time interval and the arrival time of the data of the first service, the data of the first service is transmitted in the rTWT SP mode or in the multilink redundancy transmission mode, thereby being beneficial to realizing the possibility of transmitting the data in a more efficient and reasonable mode, further being beneficial to ensuring the QoS requirement of the service, reducing the channel resource overhead and improving the resource utilization rate.

Description

Data transmission method and device and multi-link equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a data transmission method and apparatus, and a multi-link device.

Background

Institute of electrical and electronics engineers (Institute of Electrical and Electronic Engineers, IEEE) institute of standards for IEEE 802.11be protocols for wireless local area networks (wireless local access network, WLAN) introduced a limited target wake time service period (restricted target wake time service period, rtvt SP) mechanism.

rtvt refers to a target wake-up time (TWT) with enhanced media access protection and reserved resources for delay sensitive traffic. When an rtvt SP is configured to a non-AP station (non-access point station, also simply referred to as STA or station), the STA may enter a wake mode from a sleep mode (sleep mode) when the rtvt SP arrives, and transmit and/or receive data on the rtvt SP, while other STAs except the STA may avoid or not preempt (occupy) the rtvt SP, and finally the STA returns to the sleep mode at the end of the rtvt SP.

In addition, the IEEE 802.11be protocol standard introduces a multi-link (ML) mechanism. Among other things, multi-link devices (MLDs) may support data transmission over multiple links.

Disclosure of Invention

The application provides a data transmission method, a data transmission device and a multi-link device, which are used for desirably introducing a first time interval, determining whether to transmit the data of a first service in an rTWT SP mode or a multi-link redundancy transmission mode according to the position relation between the first time interval and the arrival time of the data of the first service, thereby being beneficial to realizing the possibility of transmitting the data in a more effective and reasonable mode, further being beneficial to ensuring the QoS requirement of the service, reducing the spending of channel resources and improving the utilization rate of the resources.

In a first aspect, a data transmission method according to the present application includes:

acquiring data of a first service and a first time interval;

if the reaching time of the data of the first service is within the first time interval, transmitting the data of the first service in a limited target wake-up time service period rTWT SP mode;

and if the arrival time of the data of the first service is not within the first time interval, transmitting the data of the first service by a multi-link redundancy transmission mode.

It can be seen that the embodiment of the present application introduces a first time interval, and determines whether to transmit the data of the first service by using an rtvt SP method or a multilink redundancy transmission method according to a positional relationship between the first time interval and an arrival time of the data of the first service.

If the position relation is that the reaching time of the data of the first service is in the first time interval, transmitting the data of the first service in an rTWT SP mode; if the position relation is that the reaching time of the data of the first service is not in the first time interval, the data of the first service is transmitted in a multi-link redundancy transmission mode, so that the possibility of data transmission in a more effective and reasonable mode is facilitated, the QoS requirement of the service is facilitated to be ensured, the channel resource overhead is reduced, and the resource utilization rate is improved.

In a second aspect, a data transmission device according to the present application includes:

the acquisition unit is used for acquiring data of a first service and a first time interval;

a transmission unit, configured to transmit the data of the first service by means of a limited target wake-up time service period rtvt SP if the arrival time of the data of the first service is within the first time interval;

the transmission unit is further configured to transmit the data of the first service through a multi-link redundancy transmission mode if the arrival time of the data of the first service is not within the first time interval.

In a third aspect, the steps in the method as set forth in the first aspect are applied in a multi-link device.

In a fourth aspect, the present application is a multi-link device, including a processor, a memory, and a computer program or instructions stored on the memory, where the processor executes the computer program or instructions to implement the steps in the method designed in the first aspect.

In a fifth aspect, a chip according to the present application includes a processor, where the processor performs the steps in the method designed in the first aspect.

In a sixth aspect, a chip module according to the present application includes a transceiver component and a chip, where the chip includes a processor, and the processor executes the steps in the method designed in the first aspect.

A seventh aspect is a computer readable storage medium of the present application, in which a computer program or instructions are stored, which when executed, implement the steps in the method devised in the first aspect described above.

An eighth aspect is a computer program product according to the present application, comprising a computer program or instructions which, when executed, implement the steps in the method devised in the first aspect.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following description will briefly introduce the drawings that are needed in the embodiments or the description of the prior art, it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic architecture diagram of a wireless communication system according to an embodiment of the present application;

Fig. 2 is a schematic structural diagram of a frame body of a multilink element according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a frame body of a TID to Link mapping element according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a TID-to-link mapping control field according to an embodiment of the present application;

fig. 5 is a schematic diagram of a frame body of SCS descriptor element in an embodiment of the application;

fig. 6 is a schematic diagram of a frame body of an SCS request frame according to an embodiment of the present application;

fig. 7 is a schematic diagram of a frame body of an SCS response frame according to an embodiment of the application;

FIG. 8 is a schematic diagram of a frame body of a bTWT element according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a frame body broadcasting a TWT parameter setting field according to an embodiment of the present application;

fig. 10 is a schematic diagram of arrival time of data of a service and an rTWT SP according to an embodiment of the present application;

FIG. 11 is a schematic diagram of a first time interval and rTWT SP structure according to an embodiment of the present application;

fig. 12 is a flow chart of a data transmission method according to an embodiment of the present application;

fig. 13 is a functional unit block diagram of a data transmission device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a multi-link device according to an embodiment of the present application.

Detailed Description

In order to better understand the technical solutions of the present application, the following describes the technical solutions of the embodiments of the present application with reference to the drawings in the embodiments of the present application. It will be apparent that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden for the embodiments herein, are intended to be within the scope of the present application.

It should be understood that the terms "first," "second," and the like, as used in embodiments of the present application, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, software, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

The term "at least one" in the embodiments of the present application refers to one or more, and the term "a plurality" refers to two or more.

In the embodiment of the present application, "and/or" describes the association relationship of the association object, which indicates that three relationships may exist, for example, a and/or B may indicate the following three cases: a is present alone, while A and B are present together, and B is present alone. Wherein A, B can be singular or plural. The character "/" may indicate that the context-dependent object is an "or" relationship. In addition, the symbol "/" may also denote a divisor, i.e. performing a division operation.

The expression "at least one item(s)" or the like below in the embodiments of the present application refers to any combination of these items, including any combination of single item(s) or plural item(s). For example, at least one (one) of a, b or c may represent the following seven cases: a, b, c, a and b, a and c, b and c, a, b and c. Wherein each of a, b, c may be an element or a set comprising one or more elements.

In the embodiments of the present application, "of", "corresponding" and "indicated" may be used in a mixed manner. It should be noted that the meaning of what is meant is consistent when de-emphasizing the differences.

In the embodiment of the present application, "connection" refers to various connection modes such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in any way.

In the embodiments of the present application, "network" and "system" may be expressed as the same concept, and the communication system is a communication network.

The embodiment of the application can be applied to wireless local area networks (wireless local area network, WLAN). Currently, the protocol standard adopted by WLANs is the IEEE 802.11 family. Wherein the WLAN may include a plurality of basic service sets (basic service set, BSS), the devices in the basic service sets may include stations (access point station, AP STA, also simply referred to as AP or access point) of the access point and stations (none access point station, non-AP STA, also simply referred to as STA or station) of the non-access point, and each basic service set may include one access point and at least one station.

In addition, the devices in the basic service set may include multi-link devices (MLDs). The following will specifically describe each.

In particular, an access point may be an entity that provides network access via a wireless medium to stations connected thereto. The access point may access each wireless network client to ethernet, may be a network device of a wireless fidelity (wireless fidelity, wi-Fi) chip, and may be a device supporting various IEEE 802.11 protocol standards, which is not specifically limited.

For example, the access point may be a device supporting IEEE802.11 ac, IEEE802.11 n, IEEE802.11 g, IEEE802.11b, IEEE802.11ax, IEEE802.11be, the next generation WLAN protocol standard, etc. The access points may include a centralized controller, a Base Station (BS), a base transceiver station (base transceiver station, BTS), a site controller, a switch, and the like.

In the embodiments of the present application, the access point may include a device (or a device with a transceiver function) with a wireless communication function, for example, a chip system, a chip, and a chip module. The chip system may include a chip, and may further include other discrete devices, such as a transceiver device, etc.

In embodiments of the present application, an access point may communicate with an internet protocol (Internet Protocol, IP) network. Such as the internet, a private IP network or other data network, etc.

Specifically, the station may be a wireless communication chip, a wireless sensor, or a wireless communication terminal.

For example, a User Equipment (UE), remote/remote terminal (remote UE), access terminal, subscriber unit, subscriber station, mobile device, user terminal, smart terminal, wireless communication device, user agent or user equipment/cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device, vehicle mounted device, wearable device, etc., supporting Wi-Fi communication functions, without limitation.

In embodiments of the present application, stations may include non-access point enhanced high throughput stations (none AP extremely high throughput station, non-AP EHT STAs), non-access point high efficiency stations (none AP high efficiency station, non-AP HE STAs), and the like.

In the embodiments of the present application, the station may include a device (or a device with a transceiver function) with a wireless communication function, for example, a chip system, a chip, and a chip module. The chip system may include a chip, and may further include other discrete devices, such as a transceiver device, etc.

In particular, the multi-link device may support data transmission over multiple links. A multi-link device may include multiple access points or multiple stations, and different access points or different stations may operate on different carrier frequencies, e.g., 2.4GHz, 5GHz, 6GHz, etc.

If the multi-link device contains multiple access points, the multi-link device may be referred to as an access point multi-link device (AP MLD); if the multi-link device contains multiple stations, the multi-link device may be referred to as a Non-access point multi-link device (Non-AP MLD).

The wireless communication system according to the embodiment of the present application will be described by taking a multi-link device as an example.

Exemplary, the wireless communication system of the embodiments of the present application, please refer to fig. 1. The wireless communication system 10 may include an access point multi-link device/Non-access point multi-link device (AP MLD/Non-AP MLD) 110 and a Non-access point multi-link device (Non-AP MLD) 120.

Wherein the access point multilink device/non-access point multilink device 110 may comprise a plurality of access points/stations such as AP/STA 111, AP/STA 112, AP/STA 113, etc.

The non-access point multilink device 120 may contain multiple stations such as STA 121, STA 122, STA 123, etc.

Multiple links are established between the AP/non-AP device 110 and the non-AP device 120, including link 131 between AP/STA 111 and STA 121, link 132 between AP/STA 112 and STA 122, and link 133 between AP/STA 113 and STA 123, with different links having different operating carrier frequencies. For example, link 131 has an operating carrier frequency of 6GHz, link 132 has an operating carrier frequency of 5GHz, and link 133 has an operating carrier frequency of 2.4GHz.

It should be noted that the wireless communication system 10 may further include other multi-link devices, access points, or stations, etc. besides the access point multi-link device/non-access point multi-link device 110 and the non-access point multi-link device 120, which is not limited in particular.

The wireless communication system 10 may further include other network entities such as an access network (radio access network, RAN) device, a Core Network (CN) device, a network controller, a mobility management entity, etc., which are not particularly limited.

The communication between the access point multilink device/non-access point multilink device 110 and the non-access point multilink device 120 in the wireless communication system 10 may be wireless communication or wired communication, which is not particularly limited.

The following describes related matters related to the technical scheme of the present application.

1. Multilink (Multi-Link, ML)

The IEEE 802.11be protocol standard introduces a multilink mechanism. Among other things, multi-link devices (MLDs) may support data transmission over multiple links.

The multi-link device may be an access point multi-link device (AP MLD) or a Non-access point multi-link device (Non-AP MLD).

The AP MLD may comprise a plurality of Access Points (APs), the Non-AP MLD may comprise a plurality of Stations (STAs), and different access points or stations may operate on different carrier frequencies, e.g., on carrier frequencies of 2.4GHz, 5GHz, 6GHz, etc., or on two carrier frequencies in the 5GHz band.

Multiple links may be established between the AP MLD/Non-AP MLD and the Non-AP MLD, and data may be transmitted over the multiple links.

2. Multilink Element (Multi-Link Element)

The association request (Association Request) frame sent by the Non-AP MLD may contain multiple link elements.

Illustratively, as shown in FIG. 2, the multilink Element 20 may include an Element identifier (Element ID) field 210, a Length field 220, an Element descriptor extension (Element ID Extension) field 230, a multilink Control (Multi-Link Control) field 240, a Common information (Common Info) field 250, and a Link information (Link Info) field 260. Wherein the element ID field 210 is used to set an element ID value; the length field 220 is used to set the length of the multilink element 20; the element descriptor extension field 230 is used to extend the element descriptor field.

3. Traffic identifier to link mapping mechanism (Traffic ID-to-link MappingMechanism)

Data may be transmitted over multiple links and which links over which the data is transmitted over may be determined by a Traffic Identifier (TID) of the data.

The TID-to-link mapping mechanism may be used to determine how TID maps onto multiple links established between the multi-link device and the multi-link device.

By default (default mapping mode), all TIDs should map onto all links of the Downlink (DL) and Uplink (UL). When two multi-link devices (MLDs) explicitly negotiate a TID-to-link mapping, each TID may map to the same or different link sets.

If at least one TID maps onto a link, the link is defined as enabled (enabled); if no TID maps onto a link, the link is defined as disabled. At any point in time, the TID should always map onto at least one link unless admission control is used. By default (default mapping mode), all links should be enabled since TIDs map onto all links.

If a link is enabled, the link may be used for data transmission; if a link is disabled, the link is not available for transmission. For example, if the TID of an MSDU/A-MSDU maps onto a link, that link is enabled and the MSDU/A-MSDU may be transmitted on that link. In addition, management frames and control frames may also be transmitted over the enabled links.

A TID-to-link mapping element (TID-to-link mapping element) may be used to indicate on which links data corresponding (belonging, associated, or related) to a TID may be transmitted.

Illustratively, as shown in FIG. 3, the frame body of TID to link map element 30 may contain an element identifier field 310, a length field 320, an element identifier extension field 330, a TID to link map control field 340, a link map field 350 for TID 0, a link map field 360 for TID 7, and so on.

Wherein the link map field of TID n (

n e

0,1, …, 7) may indicate the links that are allowed to transmit data corresponding to TID n. If the value of the ith bit of the link map field of TID n (n ε {0,1, …,7 }) is 1, then TID n is indicated to be mapped onto the link with which the link ID (link ID) is associated.

As shown in fig. 4, TID-to-link map control field 340 may include a direction subfield 3401, a default link map subfield 3402, a reserved subfield 3403, and a link map presence indication subfield 3404. Wherein the direction subfield 3401 is set to 0 (downlink) if the TID-to-link mapping element 30 provides TID-to-link mapping information specifically for data transmitted on the downlink. The direction subfield 3401 is set to 2 if the TID-to-link mapping element 30 provides TID-to-link mapping information specifically for data transmitted on the downlink and uplink.

If TID to link mapping element 30 represents a default TID to link mapping, default link mapping subfield 3402 is set to 1; otherwise, set to 0.

The link map presence indication subfield 3404 may indicate whether a TID n link map field is present in the TID-to-link map element 30. If the value of the nth bit of the link map presence indication subfield 3404 is 1, a link map field indicating TID n is present in the TID-to-link map element 30; otherwise, a link map field indicating TID n is not present in TID-to-link map element 30.

4. Flow classification service (Stream Classification Service, SCS) procedure

A Stream Classification Service (SCS) enables a station to request a particular QoS treatment to be applied to unicast MSDUs classified as a particular stream from its associated access point. Wherein the QoS characteristics of the particular flow are described by a traffic specification (Traffic Specification, TSPEC) element, the particular flow containing an MSDU of the incoming access point that matches parameters specified in one or more traffic classification elements (traffic classification element, TCLAS element).

The SCS descriptor element (SCS descriptor element) defines information about the flow class.

Illustratively, as shown in fig. 5, the frame body of SCS descriptor element 50 may contain an element descriptor field 510, a length field 520, an SCS identifier field 530, a request type field 540, an internal access category priority element 550, a TCLAS element field 560, a TCLAS process element field 570, a TSPEC element 580, and an optional subelement 590.

Wherein the element descriptor field 510 is used to set the SCS descriptor value; the value of the length field 520 is set to 1+n, n representing the total length of the SCS descriptor list (SCS Descriptor List) field element;

the request type field 540 is set to a number to identify the type of SCS request;

The SCS identifier field 530 is set to a non-zero value selected by the site for identifying the SCS stream specified in the SCS descriptor list field;

TCLAS element field 560 contains zero or more TCLAS information elements to specify how the incoming MSDUs are classified as part of the SCS stream;

when the request type field 540 is equal to "add" or "change," there are one or more TCLAS elements;

when the request type field 540 is equal to "remove," there is no TCLAS element;

TCLAS process element field 570 may appear when there are multiple TCLAS elements in TCLAS element field 560 and contain TCLAS process elements that define how the multiple TCLAS elements are processed;

TSPEC element field 580 contains zero or one TSPEC element to describe the traffic characteristics and QoS requirements of the traffic stream belonging to this SCS stream;

when request type field 540 equals "add" or "change," zero or one TSPEC elements are present;

when request type field 540 equals "delete", no TSPEC element is present;

optional subelement 590 contains zero or more subelements.

TCLAS process element field 570 is used to define how multiple TCLAS information elements are processed when multiple TCLAS elements are present.

The SCS descriptor element 50 is contained in the SCS request frame (SCS request frame).

The SCS request frame may be used to request stream classification such as add (add), change (change) or delete (remove).

Illustratively, as shown in fig. 6, the frame body of the SCS request frame 60 may include a category field 610, an action field 620, a dialog token field 630, and an SCS descriptor list field 640. Wherein the action field 620 is used to set a value specified for the SCS request frame; the dialog token field 630 is set to a non-zero value that is unique among the SCS request frames sent to the access point, while the access point has not received a corresponding SCS response frame; the SCS descriptor list field 640 contains one or more SCS descriptor elements.

The SCS response frame is used to respond to the SCS request frame.

Illustratively, as shown in fig. 7, the frame body of the SCS response frame 70 may include a category field 710, an action field 720, a dialog token field 730, and an SCS status list field 740. Wherein the action field 720 is used to set a value specified for the SCS response frame; the dialog token field 730 is set to a non-zero value of the corresponding SCS request frame; the SCS status list field 740 contains one or more SCS descriptor elements. The SCS status list field 740 contains one or more SCS status.

The SCS state contains an SCSID field and a state field. Wherein the SCSID field is set to a value of an SCSID field in an SCS descriptor element received in the SCS request frame; the status field is used to indicate the status of the SCSID of the request.

5. Target Wake Time (TWT) mechanism

TWT mechanisms enable stations to determine when and how often they wake up to send and/or receive data, thereby facilitating reduced power consumption and improved spectral efficiency.

TWTs first appear in the IEEE 802.11ah "wi-Fi HaLow" standard, which is used to support energy-saving operation in a large-scale internet of things environment. With the development of the IEEE 802.11ax standard, the functionality of TWT is further extended, which enables the IEEE 802.11ax standard to optimize the power saving mechanism of the device more, providing a more reliable and power saving transmission mechanism. In the IEEE 802.11ax standard, the TWT mechanism has been modified to support trigger-based uplink transmissions on the basis of IEEE 802.11ah, thereby extending the range of TWT operation.

In the TWT mechanism, a schedule may be established between a station and an access point (the schedule is negotiated between the station and the access point), which may consist of TWT service periods (TWT service period, TWT SP).

Upon arrival of the negotiated TWT SP, the station enters a wake mode from a sleep mode (sleep mode) and performs data transmission. If in the trigger enabled mode, the station needs to wait for a trigger frame (trigger frame) sent by the access point for uplink data transmission. When the TWT SP ends, the station reverts back to sleep mode.

Each station and access point may negotiate independently such that each terminal has a separate TWT SP. Alternatively, the access point may group the stations according to the set TWT SPs, so that the TWT SPs may be broadcast to the stations in the same group to improve communication efficiency.

6. TWT element (TWT element)

rtvt is a broadcast TWT (btvt), and the btvt element may be carried in a management frame (management frame) that may include an association frame (association frame), a reassociation frame (reassociation frame), a probe frame (probe frame), a beacon frame (beacon frame), a TWT setup frame (TWT setup frame), and the like.

Illustratively, as shown in FIG. 8, the bTWT Element 80 may include an Element identifier (Element ID) field 810, a Length field 820, a Control field 830, and a TWT parameter information field (TWT Parameter Information) 840.

The TWT parameter information (TWT Parameter Information) field 840 may include a separate TWT parameter set field (a single Individual TWT Parameter Set field) or at least one broadcast TWT parameter set field (one or more Broadcast TWT Parameter Set fields).

Illustratively, as shown in fig. 9, the broadcast TWT parameter set field 90 includes a Request Type (Request Type) field 910, a Target Wake Time (Target Wake Time) field 920, a nominal minimum TWT Wake duration (Nominal Minimum TWT Wake Duration) field 930, a TWT Wake interval mantissa (TWT Wake Interval Mantissa) field 940, a broadcast TWT information (Broadcast TWT Info) field 950, and a limited TWT traffic information (Restricted TWT Traffic Info) field 960.

The target wake time field 920 may be used to indicate a start position/start time (start time) of the TWT SP, among other things. The nominal minimum TWT wake duration field 930 may be used to indicate the length of time/duration of the TWT SP. The TWT wake interval mantissa field 940 may be used to indicate the period of the TWT SP.

7. TWT mode of operation

The TWT may have the following modes of operation:

1) TWT-only (Individal) mode

In the IndividualTWT mode, a station may negotiate a specific TWT SP with an access point independently, which may be stored in the access point's schedule. The station wakes up at the TWT SP and exchanges frames with the access point. Each terminal need only know the TWT SPs negotiated with the access point itself, and not the TWT SPs of other stations.

2) Broadcast (TWT) mode

The Broadcast TWT mode is an operating mechanism that is managed by the access point in charge. In Broadcast TWT mode, the TWT SP is Broadcast by the access point. Typically, the access point will broadcast the TWT SP for the current round in a beacon frame. In some special cases, the access point will also broadcast in other management frames, such as Association frames, or Probe Response frames.

It should be noted that, in the Broadcast TWT mode, the station needs to apply to the access point to become a Broadcast TWT member to execute the Broadcast TWT. Wherein the application as a Broadcast TWT member is accomplished by exchanging management frames (e.g., TWT setup) between the station and the access point, and carrying TWT elements through the management frames.

When a station applies to become a member of the Broadcast TWT, the station will operate according to the last received TWT SP. At this point, this type of station is also referred to as TWT scheduled STA (TWT Scheduled STA) and the access point is referred to as TWT schedule AP (TWT Scheduling AP).

A station that applies to be a member of the Broadcast TWT will wake up when the TWT SP arrives,

and at the end of the TWT SP, the station of the Broadcast TWT member reverts back to sleep mode until the next round of Broadcast TWT SP arrives.

8. Limited target wake-up time (rtvt)

rtvt refers to TWTs with enhanced media access protection and reserved resources for delay sensitive traffic (latency sensitive traffic). When an rtvt SP is configured for a certain station, the station may wake up when the rtvt SP arrives, and transmit and/or receive data on the rtvt SP, while other STAs except the STA may avoid or not preempt (occupy) the rtvt SP, and finally the station returns to the sleep mode at the end of the rtvt SP.

The rtwtt SP is a Broadcast TWT, i.e. belongs to the Broadcast TWT mode described above, and is dedicated to traffic with delay sensitivity, low delay and real time.

The access point may broadcast an rtvt SP allocated for a certain service to STAs through a management frame and a muting element to prevent old-system STAs from preempting channels within the rtvt SP.

In addition, rTWT SP may have the following problem of affecting resource usage:

although the traffic data can have periodic characteristics, it also cannot guarantee accurate periodicity due to delay jitter. For this reason, the duration of rTWT SP allocated to the service needs to consider the delay arrival of data of the service due to delay jitter, for example, increasing the duration of rTWT SP to cover the data of the service as much as possible for extending the arrival time, thereby resulting in a decrease in the effective usage of rTWT SP resources.

There may be retransmissions of the data of the traffic. For this reason, the duration of rtwts SP allocated to the service also needs to consider data retransmission, such as increasing the duration of rtwts SP to satisfy data transmission, thereby further reducing the effective usage of rtwts SP resources.

In summary, there is still a problem with using rtvt SPs only to transmit traffic data (e.g., delay sensitive traffic data).

The following is an example of uplink/downlink data transmission.

For example, as shown in fig. 10, the AP MLD and the non-AP MLD are configured with rTWT SPs for the traffic through negotiation. Upon arrival of the rTWT SP, the non-AP MLD enters a wake mode from a sleep mode. At the end of the rTWT SP, the non-AP MLD reverts back to sleep mode. Wherein, the starting position of the rTWT SP is A, and the ending position of the rTWT SP is B.

For the process of transmitting the data of the service on the downlink, the remote server will transmit the data of the service to the AP MLD first, and then the AP MLD uses rTWT SP to transmit the data of the service to the non-AP MLD.

However, in the process of transmitting the data of the service to the STA MLD by the remote server, the data of the service needs to reach the AP MLD first, and multi-hop transmission through the IP network is required, and in the multi-hop transmission, the data of the service may be delayed to reach the AP MLD due to delay jitter. The arrival time of the data of the service may be C or C' due to delay jitter.

If the arrival time of the service is C ', the duration between C' and B is smaller, namely the time is shorter. If the duration between C' and B is less than the time required for transmitting the data of the service, the data of the service cannot be transmitted on rTWT SP, so that the QoS requirement of the service cannot be guaranteed, the channel resource overhead is increased, and the resource utilization rate of rTWT SP is reduced.

If the arrival time of the service is C (the last rTWT SP is completely missed), and the time between C and A is longer, namely, the time is longer, so that the data of the service needs to wait for a longer time to be transmitted on the rTWT SP, the QoS requirement of the service cannot be guaranteed, the channel resource overhead is increased, and the resource utilization rate of the rTWT SP is reduced.

Similarly, in the process of transmitting the data of the service on the uplink, the data of the service generated by the application layer (such as the application APP in the application layer) of the Non-AP MLD is transmitted to the STA in the Non-AP MLD (the STA can be regarded as a communication module of the Non-AP MLD, such as a WIFI module), and then the STA in the Non-AP MLD uses rTWT SP to transmit the data of the service to the AP MLD.

However, in the process of transmitting the data of the service generated by the application layer of the Non-AP MLD to the STAs in the Non-AP MLD, the data of the service may be delayed to reach the STAs in the Non-AP MLD due to delay jitter. The arrival time of the data of the service is also C or C' due to delay jitter. At this time, similar to the above, there is a problem that the data of the service cannot be transmitted on the rTWT SP, or the data of the service needs to wait for a long time to be transmitted on the rTWT SP, etc.

It should be noted that, since there is a change in the data size of the data of the service, the change in the data size may also cause that all the data of the service cannot be transmitted on rtvt SP.

Based on this, the embodiment of the application introduces a first time interval, and determines whether to transmit the data of the first service by using the rtvt SP method or the multilink redundancy transmission method according to the position relationship between the first time interval and the arrival time of the data of the first service. If the position relation is that the reaching time of the data of the first service is in the first time interval, transmitting the data of the first service in an rTWT SP mode; if the position relation is that the reaching time of the data of the first service is not in the first time interval, the data of the first service is transmitted in a multi-link redundancy transmission mode, so that the possibility of data transmission in a more effective and reasonable mode is facilitated, the QoS requirement of the service is facilitated to be ensured, the channel resource overhead is reduced, and the resource utilization rate is improved.

It should be noted that, since there is a change in the data size of the data of the first service, the change in the data size may also cause that all the data of the first service cannot be transmitted on rtvt SP. Therefore, if there is first data that fails to complete transmission at the rTWT SP among the data of the first service, the first data is regarded as data that arrives outside the first time interval.

That is, the arrival time of the first data is not within the first time interval. Therefore, the embodiment of the application can transmit the first data based on the same principle, namely, the first data is transmitted through a multi-link redundancy transmission mode, so that the data which cannot be transmitted on the rTWT SP is transmitted through the multi-link redundancy transmission mode.

To achieve the above technical solutions and the corresponding technical effects, further explanation is given below on other contents, concepts and meanings that may be related to them.

1. First service

1) Definition of first service

In the embodiment of the present application, the first service may be a delay sensitive (latency sensitive) service, a stream classification service (stream classification service, SCS) service, a real-time application (RTA) service, a low latency (low latency) service, or the like, which is not limited in particular.

It should be noted that RTA is an application program that runs in a time range perceived by a user as instant or current. The delay must be less than a defined value, typically in seconds. Whether a given application meets the RTA conditions may depend on the Worst Case Execution Time (WCET), i.e., the maximum length of time required for a task or set of tasks defined on a given hardware platform.

The data of the RTA has strict delay requirements, such as extremely low average delay, delay of several milliseconds to several tens of milliseconds, smaller jitter (jitter), and the like, so that the reliability of the data transmission and communication process is guaranteed.

2) Service characteristics of a first service

It should be noted that, since there is a distinction between uplink and downlink in the data transmission of the present application, the data of the first service may be uplink data or downlink data.

For uplink data, it is understood that the data of the first service is generated by an application layer (such as APP) of the Non-AP MLD, and then the data of the first service is transmitted to the AP MLD by the Non-AP MLD through an uplink.

For downlink data, it may be understood that, in the process that the data of the first service is generated by the remote server and then sent to the Non-AP MLD, the AP MLD forwards the data of the first service to the Non-AP MLD on the downlink.

In the embodiment of the present application, the service characteristics of the first service may include a time point, a data volume, a delay requirement, a period, and the like.

For example, in connection with fig. 5 above, the traffic characteristics of the first traffic may be indicated/represented/characterized/described/carried by the TSPEC element in TSPEC element field 580.

Similarly, the service characteristics of the first service may include a service characteristic of downlink data and/or a service characteristic of uplink data. There may be a difference between the traffic characteristics of the downstream data and the traffic characteristics of the upstream data.

In addition, the traffic characteristics of the first traffic may be Non-AP MLD notified to AP MLD. For example, the Non-AP MLD informs the service characteristics of the first service by sending SCS request frame to the AP MLD.

3) How to acquire the first service

The data transmission of the present application is distinguished between uplink and downlink, so that the first service is also obtained with a certain difference.

For uplink data transmission, the Non-AP MLD obtains data of the first service from an application layer (e.g., APP).

For downlink data transmission, the application layer of the Non-AP MLD interacts with the application layer of the remote server, and the data of the first service is forwarded through the AP MLD relay to achieve acquisition.

4) Illustrative examples

The following is an exemplary description of the interaction process between Non-AP MLDs and AP MLDs.

Example 1:

case of one Non-AP MLD and one AP MLD:

1) The first Non-AP MLD includes a first STA, a second STA and a third STA, and the first AP MLD includes a first AP, a second AP and a third AP.

2) Three links, namely link1 between the first STA and the first AP, link2 between the second STA and the second AP and link3 between the third STA and the third AP, are established between the first Non-AP MLD and the first AP MLD.

3) The first STA requests SCS traffic through SCS request frame and informs the first AP MLD of traffic characteristics (e.g., time point, data amount, latency requirement, period, etc.) of the SCS traffic through SCS request frame.

Example 2:

two Non-AP MLD and one AP MLD cases:

1) The first Non-AP MLD includes a first STA, a second STA and a third STA, the first AP MLD includes a first AP, a second AP and a third AP, and the second Non-AP MLD includes a fourth STA and a fifth STA.

3) Two links, namely link1 between the fourth STA and the first AP and link2 between the fifth STA and the second AP, are established between the second Non-AP MLD and the first AP MLD.

4) The first STA requests the first SCS service through the first SCS request frame and informs the first AP MLD of service characteristics (e.g., time point, data amount, latency requirement, period, etc.) of the first SCS service through the first SCS request frame.

5) The fourth STA requests the second SCS service through the second SCS request frame and informs the first AP MLD of service characteristics (e.g., time point, data amount, latency requirement, period, etc.) of the second SCS service through the second SCS request frame.

2. Multiple links established by both sides of multiple link equipment

In the embodiment of the present application, the multiple links established by both sides of the multi-link device (such as Non-AP MLD and AP MLD) may be one of all links initially established, multiple links of TID mapping of data (TID mapped links), and multiple links of default mapping (default mapped links).

It should be noted that the links of the TID map of data may be indicated by TID-to-link map elements (TID-to-link Mapping element). That is, the TID-to-link mapping element may indicate on which of the established plurality of links data corresponding (belonging to, associated with, or related to) TID may be transmitted.

As shown in fig. 3, the link map field of TID n (n e {0,1, …,7 }) may indicate the links that are allowed to transmit data corresponding to TID n. If the value of the ith bit of the link map field of TID n (n ε {0,1, …,7 }) is 1, then TID n is indicated to be mapped onto the link with which the link ID (link ID) is associated.

In addition, at default mapping, each TID should map onto all links that were initially established. That is, the default mapped plurality of links may be all links initially established.

As shown in fig. 4, if TID-to-link mapping element 30 represents a default TID-to-link mapping, default link mapping subfield 3402 is set to 1; otherwise, set to 0.

3、rTWT

1) Definition of rTWT

It should be noted that, the meaning of rtvt may be described in detail in the above "8, limited target wake time (rtvt)".

Additionally, rTWT may include at least one of: duration of rTWT, start position of rTWT, end position of rTWT, period of rTWT.

The duration of rTWT may be understood as the time length of rTWT, the duration of rTWT, the period of rTWT, the rTWT service period (rTWT SP), and the like, which is similar to the nominal minimum TWT wake duration field 930 in fig. 9, without specific limitation.

The start position of rtvt may be understood as the start position of rtvt, the start time of rtvt (start time), the start time of rtvt, and the like, similar to the target wake time field 920 in fig. 9, which is not particularly limited.

The end position of rtvt is understood as the end time of rtvt, etc., and is not particularly limited.

The period of rtvt, it will be appreciated that the interval (interval) of rtvt, etc., is similar to the TWT wake interval mantissa field 940 in fig. 9, and is not particularly limited.

2) Purpose of using rTWT

In embodiments of the present application, rtvt operation allows a multi-link device (e.g., AP MLD) to use enhanced media access protection and resource reservation mechanisms to provide more predictable latency, reduce worst-case latency or jitter, and provide higher reliability for transmitting data of a first service.

3) How to configure rTWT SP

In some embodiments, rtvt SP may be configured according to the traffic characteristics of the first traffic.

For example, the Non-AP MLD informs the AP MLD of the traffic characteristics of the first traffic, and the AP MLD configures rtwtsp for transmitting the data of the first traffic according to the traffic characteristics of the first traffic.

It should be noted that, configuring rtvt SP according to the service characteristics of the first service can ensure that the configured rtvt SP more meets the requirements (such as QoS, transmission amount, transmission time, etc.) of the first service, thereby ensuring the accuracy of configuration.

In some embodiments, rtwts SPs may be configured according to a configuration request that requests configuration of rtwts SPs to traffic.

For example, the Non-AP MLD sends a configuration request to the AP MLD requesting that rTWT SPs be configured for the first service, and the AP MLD configures rTWT SPs for transmitting data of the first service according to the configuration request.

4) How to notify rTWT SP

In combination with the content in the foregoing "2) Broadcast (Broadcast) TWT mode", in the application embodiment, the rtwtt SP may be a Broadcast TWT, so after configuring the rtwtt SP on a link in the plurality of established establishment, the AP MLD needs to Broadcast the rtwtt SP corresponding to the link in the AP MLD to notify the STA corresponding to the link in the Non-AP MLD.

For example, in fig. 1, after AP MLD 110 configures rtvt SP on link 131, AP 111 needs to broadcast the rtvt SP on link 131 to notify STA 121.

In some embodiments, rtwts SP may be broadcast via TWT elements in beacon frames. The TWT element may be known from the content of the "6" and the "TWT element" (element), and will not be described herein.

5) How to negotiate rTWT SP

Because rtwtt SP is a Broadcast TWT, after completing rtwtt SP configuration on a link in multiple established links, the AP MLD needs to Broadcast the rtwtt SP for the AP corresponding to the link in the AP MLD. At this time, the STA corresponding to the one link in the Non-AP MLD may acquire the rTWT SP. However, before the STA uses the rTWT SP, the STA needs to negotiate with the AP, and the negotiation procedure can be as follows:

mode 1: the STA sends an action frame (action frame) to the AP to request to use the rTWT SP, and the AP feeds back the action frame to the STA to complete the negotiation.

For example, in fig. 1, after AP MLD 110 configures rtvt SP on link 131, AP 111 needs to broadcast the rtvt SP on link 131 to notify STA 121. Before STA 121 uses the rtvt SP, STA 121 sends an action frame to AP 111 to request to use the rtvt SP, and AP 111 feeds back the action frame to STA 121 to complete the negotiation.

Mode 2: the AP sends an unsolicited action frame directly to the STA to complete the negotiation.

That is, rTWT SP of the present embodiment may be negotiated through an action frame (action frame).

6) Illustrative examples

The interaction between Non-AP MLDs and AP MLDs is described below as an example.

Example 1:

case of one Non-AP MLD and one AP MLD:

3) The first STA requests SCS traffic through SCS request frame and informs the first AP of traffic characteristics (e.g., time point, data amount, latency requirement, period, etc.) of the SCS traffic through SCS request frame.

4) The first AP configures rtvt SPs for the SCS service according to service characteristics of the SCS service.

5) The first AP configures an rtwtt SP on link1 and broadcasts the rtwtt SP on link1 via the TWT element in the beacon frame.

6) After broadcasting the rtvt SP, the first STA and the first AP negotiate through an action frame, so that the first STA uses the rtvt SP to transmit data of the SCS service to the first STA in the rtvt SP.

Example 2:

two Non-AP MLD and one AP MLD cases:

4) The first STA requests the first SCS service through the first SCS request frame and informs the first AP of service characteristics (e.g., time point, data amount, latency requirement, period, etc.) of the first SCS service through the first SCS request frame.

5) The fourth STA requests the second SCS service through the second SCS request frame and informs the first AP of service characteristics (e.g., time point, data amount, latency requirement, period, etc.) of the second SCS service through the second SCS request frame.

6) The first AP configures the same rtvt SP according to the traffic characteristics of the first SCS traffic and the traffic characteristics of the second SCS traffic.

7) The first AP configures an rTWT SP on link1 and broadcasts the rTWT SP on link1 through TWT elements in the beacon frame.

8) After broadcasting the rtvt SP, the first STA and the first AP negotiate through a first action frame to enable the first STA to use the rtvt SP, and the fourth STA and the first AP negotiate through a second action frame to enable the fourth STA to use the rtvt SP, so as to transmit data of the first SCS service to the first STA and transmit data of the second SCS service to the fourth STA in the rtvt SP.

Example 3:

two Non-AP MLD and one AP MLD cases:

6) The first AP configures a first rTWT SP according to the service characteristics of the first SCS service.

7) The first AP configures a second rTWT SP according to the service characteristics of the second SCS service.

8) The first AP configures a first rTWT SP and a second rTWT SP on link1 and broadcasts the first rTWT SP and the second rTWT SP through TWT elements in the beacon frame on link 1.

9) After broadcasting the first rtvt SP and the second rtvt SP, the first STA negotiates with the first AP through the first action frame to enable the first STA to use the first rtvt SP in order to transmit data of the first SCS service to the first STA in the first rtvt SP.

10 After broadcasting the first rtvt SP and the second rtvt SP, the fourth STA negotiates with the first AP through the second action frame to enable the fourth STA to use the second rtvt SP in order to transmit the data of the second SCS service to the fourth STA in the second rtvt SP.

4. Multilink redundancy transmission

It should be noted that, when data is being transmitted on a certain link of the multiple links established by both sides of the multi-link device, the data generally does not need to be retransmitted on other links than the link to save transmission resources. However, in order to improve the reliability of data transmission and reduce the delay of data transmission, the present application introduces a multilink redundancy transmission mechanism.

1) Definition of multilink redundancy transmission

A multi-link redundancy transmission is understood to be a transmission in which, when data of a service is transmitted (e.g., newly transmitted or retransmitted) on one of a plurality of links, the data of the service may be being transmitted simultaneously on other links than the link or have been transmitted on other links but not yet acknowledged as successful (e.g., the sender has not yet received an ACK frame fed back by the receiver, etc.). This is illustrated below.

For example, in fig. 1, when AP/STA 111 is transmitting some data to STA 121 over link 131, AP/STA 112 is simultaneously transmitting the data to STA 122 over link 132 and/or AP/STA 113 is simultaneously transmitting the data to STA 123 over link 133; or,

when AP/STA 111 transmits some data to STA 121 over link 131, AP/STA 112 has transmitted the data to STA 122 over link 132, but AP/STA 112 has not received an ACK frame fed back by STA 122 for the data.

2) Maximum number of links for simultaneous transmission of data for traffic in multi-link redundancy transmission

In the multi-link redundancy transmission, data of the service may be transferred simultaneously on a plurality of links established by the Non-AP MLD and the AP MLD. However, the greater the number of links that are occupied for simultaneous transmission of data in a multi-link redundancy transmission, the greater the channel resources that will be occupied.

In order to avoid or reduce occupation of channel resources, the embodiments of the present application need to negotiate the maximum number of links occupied by data of a simultaneous transmission service in a multi-link redundancy transmission.

For example, in the example above for fig. 1, if AP MLD/Non-AP MLD 110 negotiates with Non-AP MLD 120 that the maximum number of links occupied by data for simultaneous transmission of traffic in a multi-link redundancy transmission is 2, AP/STA 112 may simultaneously transmit data to STA 122 on link 132 but may not simultaneously transmit data to STA 123 on link 133 when AP/STA 111 transmits the data to STA 121 on link 131.

In some possible embodiments, the Non-AP MLD and the AP MLD may negotiate a maximum number of links occupied by data of the first service transmitted simultaneously in the multi-link redundancy transmission through an action frame, that is, the maximum number of links occupied by data of the first service transmitted simultaneously in the multi-link redundancy transmission is carried by the action frame.

For example, in connection with fig. 5 above, when the maximum number of links occupied by data of the first service transmitted simultaneously in the multilink redundancy transmission is negotiated between the Non-AP MLD and the AP MLD through an SCS request frame (the SCS request frame belongs to one of the action frames), the maximum number of links may be indicated/represented/characterized/carried by a certain field in the SCS descriptor element 50. For example, the certain field may be in an optional subelement 590.

Example 1:

case of one Non-AP MLD and one AP MLD:

3) The first STA requests SCS traffic through SCS request frame and informs the first AP MLD of the maximum link number of 2 for simultaneously transmitting data of the SCS traffic in the multi-link redundancy transmission through SCS request frame.

That is, only data of SCS traffic can be multi-link redundancy transmitted between Non-AP MLD and AP MLD on 2 links out of the three links at most.

Example 2:

two Non-AP MLD and one AP MLD cases:

4) The first STA requests the first SCS service through the first SCS request frame and informs the first AP MLD of the maximum link number 2 of the data simultaneously transmitting the first SCS service in the multi-link redundancy transmission through the first SCS request frame.

That is, only at most 2 links among the three links between the first Non-AP MLD and the first AP MLD can carry out multi-link redundancy transmission on the data of the first SCS service.

5) The fourth STA requests the second SCS service through the second SCS request frame and informs the first AP MLD of the maximum link number 2 of the data simultaneously transmitting the second SCS service in the multi-link redundancy transmission through the second SCS request frame.

That is, only at most 2 of the two links between the second Non-AP MLD and the first AP MLD can carry out multi-link redundancy transmission on the data of the SCS service.

5. A first time interval

For downlink data transmission, in the process of transmitting service data to STAMLD by the remote server, the service data needs to reach AP MLD after multi-hop transmission through the IP network, and delay jitter may cause delay arrival of the service data in multi-hop transmission, so that the service data delay arrival may cause a situation that rtwtt SP configured for the service data cannot be used effectively.

Similarly, in uplink data transmission, in the process of transmitting the data of the service generated by the application layer of the Non-AP MLD to the STAs in the Non-AP MLD, the data of the service may be delayed to reach the STAs in the Non-AP MLD due to delay jitter, so that the situation that the rtvt SP configured for the data of the service cannot be effectively used may be caused due to the data delay of the service.

1) Definition of a first time interval

In order to ensure the QoS requirement of the service, reduce the channel resource overhead and improve the resource utilization rate, the embodiment of the application introduces a first time interval, and the first time interval can be used for confirming whether the data of the first service can be transmitted in an rTWT SP mode. It can also be said that the first time interval may be used to confirm whether the data of the first service is transmitted by rtvt SP or multi-link redundancy.

It should be noted that, the "first time interval" in the embodiment of the present application is a representation of a time interval, and different representations may exist in different standard protocols, but only have the same function, which is not specifically limited in the scope of protection of the embodiment of the present application.

In addition, since there is a distinction between uplink and downlink in the data transmission of the present application, there is a certain distinction in configuring the first time interval.

For example, when the AP MLD configures a first time interval for uplink data transmission, the AP MLD needs to negotiate to send the first time interval to the Non-AP MLD, e.g., by carrying the first time interval with a management frame (or action frame, etc.) to send to the Non-AP MLD.

When the AP MLD configures a first time interval for downlink data transmission, the AP MLD does not need to transmit the first time interval to the Non-AP MLD, but only needs to store the first time interval itself.

In order to define the first time interval, the embodiment of the present application needs to determine a duration of the first time interval, a starting position of the first time interval, an ending position of the first time interval, a period of the first time interval, and the like, that is, the first time interval may include at least one of the following: the duration of the first time interval, the starting position of the first time interval, the ending position of the first time interval and the period of the first time interval.

(1) Duration of the first time interval

The duration of the first time interval is understood to be the time length of the first time interval, the duration of the first time interval (duration), the period of the first time interval, and the like, which are not particularly limited.

In the embodiment of the present application, the duration of the first time interval may be an absolute value or a fixed value, and may be defined by a standard protocol, preconfigured, configured by an AP MLD, and configured by negotiation between the AP MLD and a Non-AP MLD, which is not particularly limited.

(2) Start position of first time interval

The starting position of the first time interval is understood to be the starting time (start time) of the first time interval, the starting time of the first time interval, and the like, which are not particularly limited.

In the embodiment of the present application, the starting position of the first time interval may be before or after the starting position of the rtvt SP.

It should be noted that, since the arrival time of the data of the first service may be before or after the start position of the rtvt SP, the start position of the first time interval in the embodiment of the present application may also be before or after the start position of the rtvt SP, which is beneficial to improving the flexibility of defining the first time interval.

In addition, the starting position of the first time interval may be more capable of guaranteeing communication robustness before the starting position of the rtvt SP.

In the embodiment of the present application, the starting position of the first time interval may be implemented in the following two ways:

Mode 1: the initial position of the first time interval is configured as an absolute value or a fixed value, that is, the initial position of the first time interval is an absolute initial position or a fixed initial position, and may be preset, configured by a standard protocol, configured by an AP MLD, and configured by negotiation between the AP MLD and a Non-AP MLD, which is not particularly limited.

In addition, the embodiment of the present application may configure the absolute start position or the fixed start position to be periodic, that is, the absolute start position or the fixed start position is periodic, so as to be beneficial to ensure that the start position of the first time interval is also periodic.

It can be seen that, by configuring the starting position of the first time interval as an absolute value or a fixed value, it is beneficial to configure different starting positions of the first time interval for different Non-AP MLDs, so as to improve the flexibility and diversity of configuration.

Mode 2: the starting position of the first time interval is configured by an offset (offset). Wherein,,

the offset is used to represent an offset between a starting position of the first time interval and a starting position of the rTWT; or,

the offset is used to represent an offset between a starting position of the first time interval and an ending position of the rTWT.

It should be noted that, this offset is referred to as "first offset" in the embodiment of the present application, and other terms may be used instead, so long as they have the same function and meaning, and all fall within the scope of protection required by the present application, which is not specifically limited.

In addition, the first offset may be defined by a standard protocol, preconfigured, AP MLD configured, and negotiated between AP MLD and Non-AP MLD, which is not particularly limited.

Therefore, when the initial position of the first time interval needs to be configured later, the embodiment of the application can introduce the first offset, and configure the initial position of the first time interval through the first offset and the configured rtvt, thereby being beneficial to improving the configuration efficiency and being easier to implement.

(3) End position of first time interval

The end position of the first time period is understood to be the end time of the first time period, or the like, which is not particularly limited.

In the embodiment of the present application, the end position of the first time interval may be within the rtvt SP, or the end position of the first time interval may be before the end position of the rtvt SP, or the end position of the first time interval may be before the start position of the rtvt SP.

It should be noted that, since the arrival time of the data of the first service may be before or after the start position of the rtvt SP, the end position of the first time interval in the embodiment of the present application may also be within the rtvt SP, before the end position of the rtvt SP, or before the start position of the rtvt SP, which is beneficial to improving the flexibility of defining the first time interval.

In this embodiment of the present application, if the duration of the first time interval and the starting position of the first time interval are configured, the ending position of the first time interval may be according to the duration of the first time interval and the starting position of the first time interval, without separate configuration.

In the embodiment of the present application, if the starting position of the first time interval is not configured, the ending position of the first time interval is required to be independent. At this time, the end position of the first time interval may also adopt a similar implementation manner as described above:

mode 1: the end position of the first time interval is configured as an absolute value or a fixed value, that is, the end position of the first time interval is an absolute end position or a fixed end position, and may be configured by negotiation between the AP MLD and the Non-AP MLD, which is defined by a standard protocol and is preconfigured, configured by the AP MLD, and is not particularly limited.

In addition, the embodiment of the present application may configure the absolute end position or the fixed end position to be periodic, that is, the absolute end position or the fixed end position is periodic, so as to be beneficial to ensure that the end position of the first time interval is also periodic.

It can be seen that, by configuring the end position of the first time interval as an absolute value or a fixed value, it is beneficial to configure different end positions of the first time interval for different Non-AP MLDs, so as to improve the flexibility and diversity of configuration.

Mode 2: the end position of the first time interval is configured by an offset (offset). Wherein,,

the offset is used to represent an offset between an end position of the first time interval and a start position of the rTWT; or,

the offset is used to represent an offset between the end position of the first time interval and the end position of rTWT.

It should be noted that, this offset is referred to as "second offset" in the embodiment of the present application, and other terms may be used instead, so long as they have the same function and meaning, and all fall within the scope of protection required by the present application, which is not specifically limited.

In addition, the second offset may be defined by a standard protocol, preconfigured, AP MLD configured, and negotiated between AP MLD and Non-AP MLD, which is not particularly limited.

Therefore, when the end position of the first time interval needs to be configured later, the embodiment of the application can introduce the second offset, and configure the end position of the first time interval through the second offset and the configured rtvt, thereby being beneficial to improving the configuration efficiency and being easier to implement.

(4) Period of first time interval

In combination with the content of "(2) the start position of the first time interval" and "(3) the end position of the first time interval", the period of the first time interval can be realized as follows:

mode 1: the period of the first time interval is the period of the absolute starting position or the fixed starting position.

It should be noted that, since the absolute start position or the fixed start position is periodic, the embodiment of the present application may take the period of the absolute start position or the fixed start position as the period of the first time interval, so as to be convenient for implementation.

Mode 2: the period of the first time interval is the period of the absolute end position or the fixed end position.

It should be noted that, since the absolute end position or the fixed end position is periodic, the embodiment of the present application may use the period of the absolute end position or the fixed end position as the period of the first time interval, so as to facilitate implementation.

Mode 3: the period of the first time interval is determined by the period of rTWT SP.

It should be noted that the period of the rtvt SP may be expressed as a time interval between the start position of the current rtvt SP and the start position of its neighboring rtvt SP. Therefore, in the embodiment of the present application, the starting position of the first time interval is determined according to the first offset, and then the time interval represented by the period of the rtvt SP is used as the time interval between the starting position of the current first time interval and the starting position of the adjacent first time interval, so that the period of the first time interval is determined according to the period of the rtvt SP, so as to facilitate implementation.

In addition, the period of the rTWT SP may be expressed as a time interval between the end position of the current rTWT SP and the end position of its neighboring rTWT SP. Therefore, the embodiment of the application determines the end position of the first time interval according to the second offset, and then takes the time interval represented by the period of the rtvt SP as the time interval between the end position of the current first time interval and the end position of the adjacent first time interval, thereby determining the period of the first time interval according to the period of the rtvt SP, so as to facilitate implementation.

(5) Illustrative examples

For example, as shown in fig. 11, the AP MLD and the non-AP MLD are configured with rTWT SP and time intervals for the traffic through negotiation. Upon arrival of the rTWT SP, the non-AP MLD enters a wake mode from a sleep mode. At the end of the rTWT SP, the non-AP MLD reverts back to sleep mode. Wherein, the starting position of the rTWT SP is P, the ending position of the rTWT SP is Q, and the duration of the rTWT SP is L.

The AP MLD and the non-AP MLD configure a time interval 1110 for the traffic through negotiation. The starting position of the time interval 1110 is M, the ending position of the time interval 1110 is N, and the duration of the time interval 1110 is l. Wherein M is according to the offset T _offset And P, N is determined from M and l.

2) How to acquire the first time interval

In view of the foregoing, since there is a distinction between uplink and downlink in the data transmission of the present application, the first time interval may be defined by a standard protocol, preconfigured, configured by an AP MLD, and configured by negotiation between the AP MLD and a Non-AP MLD, which is not particularly limited.

For uplink data transmission, when the AP MLD negotiates with the Non-AP MLD to configure the first time interval, or the AP MLD configures the first time interval, information for configuring the first time interval (such as a start position of the first time interval, an end position of the first time interval, a period of the first time interval, a duration of the first time interval, a first offset, or a second offset) may be carried through a management frame.

For example, when the AP MLD configures a first time interval for uplink data transmission, the AP MLD sends an action frame to the Non-AP MLD, where the action frame carries information for configuring the first time interval, so that the first time interval is acquired through the action frame.

3) Illustrative examples

Example 1:

case of one Non-AP MLD and one AP MLD:

5) The first AP configures the rtwtt SP on link1 and broadcasts the rtwtt SP on link1 via the TWT element in the beacon frame. At this time, the first STA may acquire the rTWT SP.

6) After broadcasting the rtvt SP, the first STA and the first AP negotiate with each other through an action frame, so that the first STA uses the rtvt SP to facilitate the first AP and the first STA to transmit the data of the SCS service in the rtvt SP.

For uplink data transmission:

7) The action frame carries information for configuring the time interval 1, so that the first STA determines the time interval 1 according to the information for configuring the time interval 1, and obtains the time interval 1.

8) The first STA acquires data of the SCS service from the APP. At this time, if the arrival time of the SCS service data is within the time interval 1, the first STA transmits the SCS service data to the first AP through the rTWT SP method on link 1;

if the arrival time of the data of the SCS service is not within the time interval 1, the first STA transmits the data of the SCS service to the first AP through a multi-link redundancy transmission manner on link 1.

For downstream data transmission:

7) The first AP configures time interval 1 for the SCS traffic, but does not need to transmit to the first STA.

8) The first AP obtains data of the SCS service from the remote server. At this time, if the arrival time of the SCS service data is within the time interval 1, the first AP transmits the SCS service data to the first STA on link1 through the rTWT SP mode;

If the arrival time of the data of the SCS service is not within the time interval 1, the first AP transmits the data of the SCS service to the first STA through a multi-link redundancy transmission manner on link 1.

Example 2:

two Non-AP MLD and one AP MLD cases:

6) The first AP MLD configures the same rtvt SP according to the traffic characteristics of the first SCS traffic and the traffic characteristics of the second SCS traffic.

7) The first AP configures the rTWT SP at link1 and broadcasts the rTWT SP over link1 via TWT elements in the beacon frame. At this time, the first STA and the fourth STA acquire the rTWT SP.

For uplink data transmission:

9) The first action frame carries information for configuring the time interval 1, so that the first STA determines the time interval 1 according to the information for configuring the time interval 1, and acquires the time interval 1.

The second action frame carries information for configuring the time interval 2, so that the fourth STA determines the time interval 2 according to the information for configuring the time interval 2, and the acquisition of the time interval 2 is realized.

10 The first STA acquires data of the first SCS service from the APP. At this time, if the arrival time of the data of the first SCS service is within the time interval 1, the first STA transmits the data of the first SCS service to the first AP through the rTWT SP manner on link 1;

If the arrival time of the data of the first SCS service is not within the time interval 1, the first STA transmits the data of the first SCS service to the first AP through the multi-link redundancy transmission mode on link 1.

11 Fourth STA acquires data of the second SCS service from the APP. At this time, if the arrival time of the data of the second SCS service is within the time interval 2, the fourth STA transmits the data of the second SCS service to the first AP through the rtvt SP manner on the link 1;

if the arrival time of the data of the second SCS service is not within the time interval 2, the fourth STA transmits the data of the second SCS service to the first AP through the multi-link redundancy transmission manner on link 1.

For downstream data transmission:

9) The first AP configures time interval 1 for the first SCS traffic, but does not need to transmit to the first STA.

10 The first AP configures time interval 2 for the second SCS service, but does not need to transmit to the fourth STA.

11 The first AP obtains data of the first SCS service from the remote server. At this time, if the arrival time of the data of the first SCS service is within the time interval 1, the first AP transmits the data of the first SCS service to the first STA on link1 through the rTWT SP mode;

if the arrival time of the data of the first SCS service is not within the time interval 1, the first AP transmits the data of the first SCS service to the first STA through a multi-link redundancy transmission manner on link 1.

12 The first AP obtains data of the second SCS service from the remote server. At this time, if the arrival time of the data of the second SCS service is within the time interval 2, the first AP transmits the data of the second SCS service to the fourth STA on link1 through the rtvt SP mode;

if the arrival time of the data of the second SCS service is not within the time interval 2, the first AP transmits the data of the second SCS service to the fourth STA through the multi-link redundancy transmission mode on link 1.

Example 3:

two Non-AP MLD and one AP MLD cases:

8) The first AP broadcasts the first rtwtsp and the second rtwtsp over link1 via the TWT elements in the beacon frame. At this time, both the first STA and the fourth STA acquire the first rTWT SP and the second rTWT SP.

9) After broadcasting the first rtvt SP and the second rtvt SP, the first STA negotiates with the first AP through the first action frame to enable the first STA to use the first rtvt SP in order to transmit data of the first SCS service to the first STA in the first rtvt SP. 10 After broadcasting the first rtvt SP and the second rtvt SP, the fourth STA negotiates with the first AP through the second action frame to enable the fourth STA to use the second rtvt SP in order to transmit the data of the second SCS service to the fourth STA in the second rtvt SP.

For uplink data transmission:

10 The first STA carries information for configuring the time interval 1 in the first action frame, so that the first STA determines the time interval 1 according to the information for configuring the time interval 1, and obtains the time interval 1.

11 The information for configuring the time interval 2 is carried in the second action frame, so that the fourth STA determines the time interval 2 according to the information for configuring the time interval 2, and the acquisition of the time interval 2 is realized.

12 The first STA acquires data of the first SCS service from the APP. At this time, if the arrival time of the data of the first SCS service is within the time interval 1, the first STA transmits the data of the first SCS service to the first AP through the first rtvt SP manner on the link 1;

if the arrival time of the data of the first SCS service is not within the time interval 1, the first STA transmits the data of the first SCS service to the first AP through a multi-link redundancy transmission manner on link 1.

13 Fourth STA acquires data of the second SCS service from the APP. At this time, if the arrival time of the data of the second SCS service is within the time interval 2, the fourth STA transmits the data of the second SCS service to the first AP through the second rTWT SP manner on the link 1;

if the arrival time of the data of the second SCS service is not within the time interval 2, the fourth STA transmits the data of the second SCS service to the first AP through the multi-link redundancy transmission mode on link 1.

For downstream data transmission:

10 The first AP configures time interval 1 for the first SCS service, but does not need to transmit to the first STA.

11 The first AP configures time interval 2 for the second SCS service, but does not need to transmit to the fourth STA.

12 The first AP obtains data of the first SCS service from the remote server. At this time, if the arrival time of the data of the first SCS service is within the time interval 1, the first AP transmits the data of the first SCS service to the first STA through the first rTWT SP manner on the link 1;

13 The first AP obtains data of the second SCS service from the remote server. At this time, if the arrival time of the data of the second SCS service is within the time interval 2, the first AP transmits the data of the second SCS service to the fourth STA on the link1 through the second rtvt SP manner;

In summary, an example of a data transmission method according to an embodiment of the present application is described below. The steps described in fig. 12 may be performed by a multi-link device (such as an AP MLD or a Non-AP MLD), a chip module, an AP, an STA, or the like, which is not limited in particular.

Fig. 12 is a schematic flow chart of a data transmission method according to an embodiment of the present application, which specifically includes the following steps:

s1210, acquiring data of a first service and a first time interval.

It should be noted that, for the first service, the contents of the foregoing "1 and the first service" and other related contents may be detailed, which will not be described herein.

For the first time interval, the contents in the above "5, the first time interval" and other related contents may be described in detail, which will not be repeated.

S1220, if the arrival time of the data of the first service is within the first time interval, the data of the first service is transmitted by the limited target wake-up time service period rTWT SP mode.

It should be noted that, for rtvt, details of "8, restricted target wake time (rtvt)" and details of "3, rtvt" and other related contents may be found, and will not be described herein.

S1230, if the arrival time of the data of the first service is not within the first time interval, transmitting the data of the first service by the multilink redundancy transmission mode.

It should be noted that, for the multilink redundancy transmission, details of the foregoing "4" and "multilink redundancy transmission" and other related contents may be described, which will not be repeated.

Specifically, the first time interval includes at least one of: the duration of the first time interval, the starting position of the first time interval, the ending position of the first time interval and the period of the first time interval.

It should be noted that, for the first time interval, the content in the foregoing "5 and the first time interval" and other related content may be detailed, so that the first time interval is defined by at least one of a duration of the first time interval, a starting position of the first time interval, an ending position of the first time interval, and a period of the first time interval.

Specifically, the starting position of the first time interval is before the starting position of the limited target wake-up time service period.

It should be noted that, for the start position of the first time interval, the content in "(2) the start position of the first time interval" and other related content can be described in detail. Since the arrival time of the data of the first service may be before the start position of the rtvt SP, the start position of the first time interval in the embodiment of the present application may also be before the start position of the rtvt SP. Wherein, the starting position of the first time interval may be more capable of guaranteeing communication robustness before the starting position of the rtvt SP.

In particular, the end position of the first time interval is within the limited target wake-up time service period.

It should be noted that, regarding the end position of the first time interval, the content in "(3) the end position of the first time interval" and other related content can be described in detail. Since the arrival time of the data of the first service may be before the start position of the rtvt SP, the end position of the first time interval in the embodiment of the present application may also be more capable of ensuring communication robustness before the rtvt SP.

Specifically, the starting position of the first time interval is an absolute starting position.

Therefore, by configuring the starting position of the first time interval as an absolute value, different starting positions of the first time interval are configured for different Non-AP MLDs, and the flexibility and diversity of configuration are improved.

In particular, the absolute starting position is periodic.

Specifically, the period of the first time interval is the period of the absolute start position.

It can be seen that the period of the configuration first time interval is realized by the period of the absolute starting position.

Specifically, the starting position of the first time interval is determined by a first offset, where the first offset is used to represent an offset between the starting position of the first time interval and the starting position of the limited target wake-up time service period.

Specifically, the period of the first time interval is determined by the period of the limited target wake-up time service period.

Specifically, the first time interval is carried by the action frame.

It can be seen that the first time interval is carried by the action frame to achieve the acquisition of the first time interval.

Specifically, the limited target wake-up time service period is established through action frame negotiation.

It should be noted that, for the limited target wake time service period, details of "3, rTWT" and other related contents can be found, so that negotiation is implemented through action frames to establish the limited target wake time service period.

Specifically, the limited target wake-up time service period is configured according to the traffic characteristics of the first traffic.

It can be seen that configuring the limited target wake-up time service period according to the service characteristics of the first service is beneficial to improving the accuracy of configuration.

Specifically, the limited target wake time service period is broadcast via a target wake time element in the beacon frame.

It can be seen that broadcasting the limited target wake-up time service period is achieved by the target wake-up time element in the beacon frame.

Specifically, the first traffic is requested by a stream classification service request frame.

It can be seen that the stream classification service requests frames to fulfill the request for the first service for subsequent transmission of data of the first service.

Specifically, the first service is one of a stream classification service, a low-delay service and a real-time application service.

Specifically, the maximum number of links occupied by simultaneously transmitting the data of the first service in the multilink redundancy transmission is carried by the action frame.

It should be noted that, for the maximum number of links occupied by the data of the first service transmitted simultaneously in the multi-link redundancy transmission is carried by the action frame, the content in the foregoing "4" and the content in the multi-link redundancy transmission "and other related content may be described in detail, which will not be described herein.

Therefore, the maximum link number occupied by the data of the first service transmitted simultaneously in the multi-link redundancy transmission is negotiated through the action frame, so that channel resources occupied by the multi-link redundancy transmission are avoided, and the resource utilization rate is improved.

The foregoing description of the embodiments of the present application has been presented primarily from a method-side perspective. It will be appreciated that the multi-link device, in order to achieve the above-described functionality, comprises corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will appreciate that the various illustrative methods, modules, units, or algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a method, function, module, unit, or step is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described methods, functions, modules, units, or steps using different methods for each particular application, but such implementation should not be considered beyond the scope of the present application.

The embodiment of the application can divide functional units/modules of the multi-link device according to the method example. For example, each functional unit/module may be divided corresponding to each function, or two or more functions may be integrated in one functional unit/module. The integrated functional units/modules described above may be implemented in hardware or in software. It should be noted that the division of the functional units/modules in the embodiments of the present application is schematic, but only one logic function is divided, and another division manner may be implemented in actual implementation.

In the case of using integrated units/modules, fig. 13 is a functional unit block diagram of a data transmission apparatus of the application embodiment. The data transmission apparatus 1300 may include: an acquisition unit 1301 and a transmission unit 1302.

The acquiring unit 1301 may be a module unit for transmitting and receiving signals, data, information, and the like.

The transmission unit 1302 may be a module unit for processing and transmitting signals, data, information, and the like, and is not particularly limited.

In some embodiments, the acquisition unit 1301 and the transmission unit 1302 may be integrated in one unit. For example, the acquisition unit 1301 and the transmission unit 1302 may be integrated in a processing unit, or the acquisition unit 1301 and the transmission unit 1302 may be integrated in a communication unit.

In some embodiments, acquisition unit 1301 and transmission unit 1302 may be separate units. For example, the acquisition unit 1301 may include a communication unit. The transmission unit 1302 may include a processing unit and a communication unit.

The communication unit may be a communication interface, transceiver circuit, etc.

The processing unit may be a processor or controller, and may be, for example, a central processing unit (central processing unit, CPU), a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA), or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processing unit may also be a combination that implements computing functionality, e.g., comprising one or more microprocessor combinations, a combination of DSPs and microprocessors, etc.

In some embodiments, the data transmission apparatus 1300 may further include a storage unit for storing a computer program or instructions executed by the data transmission apparatus 1300. The memory unit may be a memory.

In some embodiments, the data transmission device 1300 may be a chip or a chip module.

In a specific implementation, the acquisition unit 1301 and the transmission unit 1302 are configured to perform the steps as described in the method embodiments described above. The following is a detailed description.

An acquiring unit 1301, configured to acquire data of a first service and a first time interval;

a transmitting unit 1302, configured to transmit the data of the first service in a limited target wake-up time service period rtvt SP if the arrival time of the data of the first service is within a first time interval;

the transmission unit 1302 is further configured to transmit the data of the first service by a multi-link redundancy transmission method if the arrival time of the data of the first service is not within the first time interval.

It should be noted that, the specific implementation of each operation in the embodiment shown in fig. 13 may be described in detail in the above-shown method embodiment, which is not described herein.

In particular, the absolute starting position is periodic.

Specifically, the period of the first time interval is determined by the period of the limited target wake-up time service period and the first offset.

Specifically, the first time interval is carried by the action frame.

Referring to fig. 14, fig. 14 is a schematic structural diagram of a multi-link device according to an embodiment of the present application. The multi-link device 1400 includes a processor 1410, a memory 1420, and a communication bus for connecting the processor 1410 and the memory 1420.

Memory 1420 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (compact disc read-only memory, CD-ROM), memory 1420 is used to store program code and transmitted data for execution by multi-link device 1400.

The multi-link device 1400 may also include a communication interface that may be used to receive and transmit data.

Processor 1410 may be one or more CPUs. In the case where the processor 1410 is one CPU, the CPU may be a single core CPU or a multi-core CPU.

The processor 1410 in the multi-link device 1400 is configured to execute computer programs or instructions 1421 stored in the memory 1420 to implement the following: acquiring data of a first service and a first time interval; if the reaching time of the data of the first service is in the first time interval, transmitting the data of the first service in a limited target wake-up time service period rTWT SP mode; if the arrival time of the data of the first service is not within the first time interval, transmitting the data of the first service through a multilink redundancy transmission mode.

It should be noted that, the specific implementation of each operation may be described in the above-illustrated method embodiment, and the multi-link device 1400 may be used to perform the method on the multi-link device side of the method embodiment of the present application, which is not described herein in detail.

In particular, the absolute starting position is periodic.

Specifically, the first time interval is carried by the action frame.

The embodiment of the application also provides a chip, which comprises a processor, a memory and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to realize the steps described in the embodiment of the method.

The embodiment of the application also provides a chip module, which comprises a transceiver component and a chip, wherein the chip comprises a processor, a memory and a computer program or instructions stored on the memory, and the processor executes the computer program or instructions to realize the steps described in the embodiment of the method.

The present application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the steps described in the method embodiments above.

Embodiments of the present application also provide a computer program product comprising a computer program or instructions which, when executed, implement the steps described in the method embodiments above.

In the foregoing embodiments, the descriptions of the embodiments of the present application are focused on each embodiment, and for a portion of one embodiment that is not described in detail, reference may be made to the related descriptions of other embodiments.

The steps of a method or algorithm described in the embodiments of the present application may be implemented in hardware, or may be implemented by executing software instructions by a processor. The software instructions may be comprised of corresponding software modules that may be stored in RAM, flash memory, ROM, erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a terminal or management device. It is also possible that the processor and the storage medium reside as discrete components in a terminal or management device.

Those of skill in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application may be implemented, in whole or in part, in software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

The respective apparatuses and the respective modules/units included in the products described in the above embodiments may be software modules/units, may be hardware modules/units, or may be partly software modules/units, and partly hardware modules/units. For example, for each device or product applied to or integrated on a chip, each module/unit included in the device or product may be implemented in hardware such as a circuit, or at least part of the modules/units may be implemented in software program, where the software program runs on a processor integrated inside the chip, and the rest (if any) of the modules/units may be implemented in hardware such as a circuit; for each device and product applied to or integrated in the chip module, each module/unit contained in the device and product can be realized in a hardware manner such as a circuit, different modules/units can be located in the same component (such as a chip, a circuit module and the like) or different components of the chip module, or at least part of the modules/units can be realized in a software program, the software program runs on a processor integrated in the chip module, and the rest (if any) of the modules/units can be realized in a hardware manner such as a circuit; for each device, product, or application to or integrated with the terminal, each module/unit included in the device, product, or application may be implemented by using hardware such as a circuit, different modules/units may be located in the same component (for example, a chip, a circuit module, or the like) or different components in the terminal, or at least part of the modules/units may be implemented by using a software program, where the software program runs on a processor integrated inside the terminal, and the remaining (if any) part of the modules/units may be implemented by using hardware such as a circuit.

The foregoing embodiments have been provided for the purpose of illustrating the embodiments of the present application in further detail, and it should be understood that the foregoing embodiments are merely illustrative of the embodiments of the present application and are not intended to limit the scope of the embodiments of the present application, and any modifications, equivalents, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application are included in the scope of the embodiments of the present application.

Claims

1. A data transmission method, comprising:

acquiring data of a first service and a first time interval;

2. The method of claim 1, wherein the first time interval comprises at least one of: the duration of the first time interval, the starting position of the first time interval, the ending position of the first time interval and the period of the first time interval.

3. The method of claim 2, wherein a starting location of the first time interval is prior to a starting location of the limited target wake-up time service period.

4. The method of claim 2, wherein an end position of the first time interval is within the limited target wake time service period.

5. A method according to claim 2 or 3, characterized in that the starting position of the first time interval is an absolute starting position.

6. The method of claim 5, wherein the absolute starting position is periodic.

7. The method of claim 6, wherein the period of the first time interval is a period of the absolute starting position.

8. A method according to claim 2 or 3, wherein the starting position of the first time interval is determined by a first offset representing an offset between the starting position of the first time interval and the starting position of the limited target wake-up time service period.

9. The method of claim 8, wherein a period of the first time interval is determined by a period of the limited target wake-up time service period.

10. The method of claim 1, wherein the first time interval is carried by an action frame.

11. The method of claim 1, wherein if there is first data in the data of the first traffic that fails to complete transmission within the limited target wake time service period rtvt SP, the first data is considered to be data arriving outside the first time interval.

12. The method of claim 1, wherein the maximum number of links occupied by simultaneously transmitting data of the first service in the multi-link redundancy transmission is carried by an action frame.

13. A data transmission apparatus, comprising:

14. A multi-link device comprising a processor, a memory and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to implement the steps of the method of any one of claims 1-11.

15. A chip comprising a processor, wherein the processor performs the steps of the method of any one of claims 1-12.

16. A computer readable storage medium, characterized in that it stores a computer program or instructions which, when executed, implement the steps of the method of any one of claims 1-12.