Method for transmitting low-latency traffic, multi-connection access point device, and site device

Abstract

The present disclosure relates to a method for transmitting low-latency traffic, a multi-connection access point device, and a multi-connection site device. The method for transmitting low-latency traffic comprises: determining a first radio frame, the first radio frame comprising first identification information and a first identification information identifier; migrating a first R-TWT scheduling of a first connection to a second connection, and transmitting, in a second R-TWT SP under the second connection in the first R-TWT scheduling, low-latency traffic corresponding to the first R-TWT scheduling; and sending the first radio frame. A R-TWT mechanism is improved, and the power consumption of a Wi-Fi network can be further reduced, thus achieving seamless transmission of low-latency traffic.

Description

Low-latency service transmission method, multi-connection access point device, and site device Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a low-latency service transmission method, a multi-connection access point device, and a multi-connection site device. Background Art

[0002] Among the Wi-Fi technologies currently under research, the Target Wake Time (TWT) mechanism has been proposed to support energy conservation in large-scale Internet of Things (IoT) devices. Furthermore, the Restricted-TWT (R-TWT) mechanism has been proposed to ensure the transmission of latency-sensitive traffic. To further reduce Wi-Fi network power consumption, the R-TWT mechanism needs to be improved.

[0003] Summary of the Invention

[0004] Embodiments of the present disclosure provide a low-latency service transmission method, a multi-connection access point device, and a multi-connection site device.

[0005] According to a first aspect of an embodiment of the present disclosure, a low-latency service transmission method is proposed, the method comprising:

[0006] determining a first radio frame;

[0007] The first radio frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection;

[0008] A first radio frame is sent.

[0009] According to a second aspect of an embodiment of the present disclosure, a low-latency service transmission method is proposed, the method comprising:

[0010] receiving a first radio frame;

[0011] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0012] According to a third aspect of an embodiment of the present disclosure, a multi-connection access point device is provided, the multi-connection access point device including:

[0013] A processing module, configured to determine a first radio frame;

[0014] The first radio frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection;

[0015] a transceiver module, configured to send a first wireless frame;

[0016] According to a fourth aspect of an embodiment of the present disclosure, a multi-connection site device is provided, the multi-connection site device including:

[0017] a transceiver module, configured to receive a first wireless frame;

[0018] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0019] According to a fifth aspect of an embodiment of the present disclosure, a multi-connection access point device is provided, the multi-connection access point device including:

[0020] one or more processors;

[0021] The multi-connection access point device is used to execute the low-latency service transmission method described in the optional implementation manner of the first aspect above.

[0022] According to a sixth aspect of an embodiment of the present disclosure, a multi-connection site device is provided, the multi-connection site device including:

[0023] one or more processors;

[0024] Among them, the multi-connection site device is used to execute the low-latency service transmission method described in the optional implementation method of the second aspect above.

[0025] According to the seventh aspect provided by an embodiment of the present disclosure, a communication system is provided, which includes a multi-connection access point device and a multi-connection site device, wherein the multi-connection access point device is configured to implement the low-latency service transmission method provided by the above-mentioned first aspect, and the multi-connection site device is configured to implement the low-latency service transmission method described in the optional implementation method of the above-mentioned second aspect.

[0026] According to the eighth aspect provided by the embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes the low-latency service transmission method described in the optional implementation of the first or second aspect above.

[0027] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0029] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0030] FIG2A is one of exemplary interaction diagrams of a communication method provided according to an embodiment of the present disclosure.

[0031] FIG2B is a schematic diagram of an exemplary scenario of a communication method provided according to an embodiment of the present disclosure.

[0032] FIG3A is one of exemplary flowcharts of a communication method provided according to an embodiment of the present disclosure.

[0033] FIG3B is a second exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0034] FIG3C is a third exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0035] FIG4 is a fourth exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0036] FIG5A is a second exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0037] FIG5B is a third exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0038] FIG6 is one of exemplary structural diagrams of a communication method provided according to an embodiment of the present disclosure.

[0039] FIG. 7 is a second exemplary structural diagram of a communication method provided according to an embodiment of the present disclosure.

[0040] FIG8 is a third exemplary structural diagram of a communication method provided according to an embodiment of the present disclosure.

[0041] FIG9 is a fourth exemplary structural diagram of a communication method provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0042] The embodiments of the present disclosure provide a low-latency service transmission method, a multi-connection access point device, and a multi-connection site device.

[0043] In a first aspect, an embodiment of the present disclosure provides a low-latency service transmission method, the method comprising:

[0044] determining a first radio frame;

[0045] The first radio frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP (R-TWT Service Period, R-TWT service time) of the first R-TWT scheduling under the second connection;

[0046] A first radio frame is sent.

[0047] In the above embodiment, the AP MLD (Access Point Multi-Link Device) determines a first wireless frame and carries first identification information in the first wireless frame. The first identification information indicates that the first R-TWT scheduling of the first connection is migrated to the second connection, and the low-latency service corresponding to the first R-TWT scheduling is transmitted within the second R-TWT SP under the second connection in the first R-TWT scheduling. In this way, when the first connection fails or is interrupted, the first R-TWT scheduling can continue to be executed and the low-latency service corresponding to the first R-TWT scheduling can be transmitted on the second connection. While avoiding the interruption of the transmission of the low-latency service corresponding to the first R-TWT scheduling, the clock deviation caused by the fact that the connection clock of the AP to which the AP MLD is attached is not completely synchronized is avoided, and the transmission of the low-latency service is delayed, thereby realizing seamless transmission of the low-latency service and further reducing the power consumption of the Wi-Fi network.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the first wireless frame includes an R-TWT migration element, and the R-TWT migration element carries a parameter information field for the first R-TWT scheduling.

[0049] In the above embodiment, by carrying the R-TWT migration element in the first wireless frame, during the process of performing the first R-TWT scheduling migration, the parameter information field of the first R-TWT scheduling can be determined according to the first wireless frame, and the first R-TWT scheduling of the first connection can be migrated to the second connection, thereby improving the migration rate and reducing the time required to migrate the first R-TWT scheduling.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the parameter information field of the first R-TWT scheduling includes at least one of the following:

[0051] A timer deviation subfield, where the timer deviation subfield indicates a timer deviation between the first connection and the second connection;

[0052] The second connection bitmap subfield indicates that the first R-TWT schedules a target connection that can be migrated, and the target connection includes the second connection.

[0053] In the above embodiment, by setting the timer deviation subfield between the first connection and the second connection in the parameter information field of the first R-TWT scheduling, it is convenient to adjust the target wake-up time of the first R-TWT scheduling under the new connection (second connection) after migration according to the clock deviation between the connection clocks of the first connection and the second connection during the process of performing the first R-TWT scheduling migration, so as to avoid the clock deviation between the connection clocks of the first connection and the second connection, which causes the target wake-up time of the first R-TWT scheduling under the second connection to be delayed, thereby affecting the transmission of low-latency services. By setting the second connection bitmap subfield in the parameter information field of the first R-TWT scheduling, it is convenient to determine the second connection to be migrated by the first R-TWT scheduling from the target connection that can be migrated by the first R-TWT scheduling indicated by the second connection bitmap subfield during the process of performing the first R-TWT scheduling migration.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include:

[0055] The R-TWT migration element also carries the first R-TWT SP scheduled by R-TWT under the first connection;

[0056] The time indicated by the first R-TWT SP is offset by the time shift timer to obtain the second R-TWT SP.

[0057] In the above embodiment, the R-TWT migration element carries the first R-TWT SP of the first R-TWT scheduling under the first connection, and the timer deviation between the first connection and the second connection, so that in the process of performing the first R-TWT scheduling migration, based on the first R-TWT SP and the timer deviation, the time offset timer deviation indicated by the first R-TWT SP is obtained to obtain the second R-TWT SP, and adjust the target wake-up time (i.e., the second R-TWT SP) of the first R-TWT scheduling under the new connection (second connection) after migration, so as to achieve the alignment of the target wake-up time after migration and the original target wake-up time (first R-TWT SP), and avoid the clock deviation caused by the incomplete synchronization of the connection clock of the AP MLD's affiliated AP, which affects the transmission of low-latency services and causes transmission delays.

[0058] In combination with some embodiments of the first aspect, in some embodiments, when there are multiple first R-TWT schedules, the parameter information field of the first R-TWT schedule includes at least one subfield; each subfield includes parameter information of a first R-TWT schedule.

[0059] In the above embodiment, by setting a subfield of parameter information for each first R-TWT scheduling in the parameter information field of the first R-TWT scheduling, it is convenient to determine the parameter information of each first R-TWT scheduling to be migrated through each subfield during the process of migrating the first R-TWT scheduling.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the R-TWT migration element also carries a migration timeout duration field; the migration timeout duration field indicates the maximum duration required to schedule the migration of the R-TWT of the first connection to the second connection.

[0061] In the above embodiment, the R-TWT migration element carries a migration timeout field, which facilitates the determination of the maximum duration required to migrate the R-TWT scheduling of the first connection to the second connection through the migration timeout field during the first R-TWT scheduling migration, thereby avoiding the time for executing the migration operation exceeding the maximum duration, affecting the transmission of low-latency services, and causing transmission delays.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the R-TWT migration element also carries a control field; the control field includes at least one of a migration timeout existence flag, a second connection bitmap size flag, and a timer deviation existence flag.

[0063] In the above embodiment, the R-TWT migration element carries a control field, which facilitates the determination of whether there is a maximum duration required to migrate the R-TWT scheduling of the first connection to the second connection, the size of the second connection bitmap, and whether there is a timer deviation through the migration timeout existence flag, the second connection bitmap size flag, and the timer deviation existence flag in the control field during the first R-TWT scheduling migration.

[0064] In combination with some embodiments of the first aspect, in some embodiments, when the migration timeout existence flag is set to the first parameter value, the R-TWT migration element is marked to carry a migration timeout duration field.

[0065] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the specific parameter value set by the migration timeout existence flag can be used to determine whether the R-TWT migration element carries the migration timeout duration field, thereby saving the time required to further identify the migration timeout duration field when the migration timeout existence flag is not the first parameter value. In addition, by setting the migration timeout existence flag to different parameter values ​​to identify whether the R-TWT migration element carries the migration timeout duration field, the amount of transmission data in the first wireless frame can also be saved.

[0066] In combination with some embodiments of the first aspect, in some embodiments, the second connection bitmap size identification bit is set to different parameter values, indicating that the sizes of the second connection bitmap are different.

[0067] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the size of the second connection bitmap can be determined, the number range of connections attached to the AP MLD can be determined, and then the number range of target connections that can be migrated by the first R-TWT scheduling can be determined based on the specific values ​​of each bit in the second connection bitmap.

[0068] In combination with some embodiments of the first aspect, in some embodiments, when the timer deviation existence identification bit is set to the second parameter value, the parameter information field indicating the first R-TWT scheduling includes a timer deviation subfield.

[0069] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the specific parameter value set by the timer deviation presence flag can be used to determine whether the parameter information field of the first R-TWT scheduling includes the timer deviation subfield, thereby saving the time required to further identify the timer deviation subfield when the timer deviation presence flag is not the first parameter value. In addition, by setting the timer deviation presence flag to different specific parameter values ​​to identify whether the parameter information field of the first R-TWT scheduling includes the timer deviation subfield, the amount of transmission data in the first wireless frame can also be saved.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the first connection and the second connection are non-simultaneous transmit and receive NSTR (Non-Simultaneous Transmit and Receive) connection pairs, and there is no timer deviation subfield in the parameter information field of the first R-TWT scheduling.

[0071] In the above embodiment, when the first connection and the second connection are non-simultaneous NSTR connection pairs, the timer deviation subfield is set to not exist in the parameter information field of the first R-TWT scheduling, so as to combine the correlation between the first connection and the second connection to determine whether there is a clock deviation between the connection clocks of the first connection and the second connection.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, migrating the first R-TWT scheduling of the first connection to the second connection may include:

[0073] Before the first connection fails or is interrupted, the first R-TWT scheduling is migrated to the second connection.

[0074] In the above embodiment, when the first connection fails or is interrupted, the first R-TWT scheduling is migrated to the second connection, and the first R-TWT scheduling can continue to be executed on the second connection, avoiding interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0075] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include:

[0076] receiving a second wireless frame; wherein the second wireless frame includes second identification information, and the second identification information identifies confirmation information for the first wireless frame;

[0077] Perform a migration operation to schedule the first R-TWT of the first connection to the second connection.

[0078] In the above embodiment, while informing the non-AP MLD (Non-Access Point Multi-Link Device) of the first R-TWT scheduling that needs to be migrated, the confirmation information of the non-AP MLD for the first wireless frame, that is, the second wireless frame, can be received. After receiving the second wireless frame, the first R-TWT scheduling of the first connection is migrated to the second connection to avoid interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0079] In combination with some embodiments of the first aspect, in some embodiments, the second radio frame includes: a parameter information field of the first R-TWT scheduling and a second connection bitmap subfield.

[0080] In the above embodiment, confirmation information specific to the first radio frame, ie, parameter information of the first R-TWT scheduling and the second connection bitmap, may be determined based on the second radio frame sent by the non-AP MLD.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments, the receiving the second radio frame may include:

[0082] Before the time indicated by the migration timeout duration field, a second radio frame is received in the first connection.

[0083] In the above embodiment, by receiving the second wireless frame through the first connection before the time indicated by the migration timeout duration field, it is further possible to migrate the first R-TWT scheduling to the second connection when the first connection fails or is interrupted, and the first R-TWT scheduling can continue to be executed on the second connection, thereby avoiding interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include:

[0085] After the time indicated by the migration super long duration field and without receiving the second wireless frame, a migration operation is performed to schedule the first R-TWT of the first connection to migrate to the second connection.

[0086] In the above embodiment, by directly migrating the first R-TWT scheduling of the first connection to the second connection after the time indicated by the migration timeout duration field and when no confirmation information of the non-AP MLD for the first wireless frame is received, the first R-TWT scheduling can be migrated to the second connection when the first connection fails or is interrupted, and the first R-TWT scheduling can continue to be executed on the second connection, thereby avoiding interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0087] In a second aspect, an embodiment of the present disclosure provides a low-latency service transmission method, the method comprising:

[0088] receiving a first radio frame;

[0089] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0090] In the above embodiment, the non-AP MLD receives a first radio frame, and carries first identification information in the first radio frame. The first R-TWT scheduling of the first connection is migrated to the second connection through the first identification information, and the low-latency service is transmitted within the second R-TWT SP under the second connection under the first R-TWT scheduling; in this way, the non-AP MLD can obtain relevant information of the first R-TWT scheduling to be migrated, so that when the first connection fails or is interrupted, the first R-TWT scheduling can be continued to be executed on the second connection within the second R-TWT SP under the second connection under the first R-TWT scheduling, while avoiding the interruption of the low-latency service transmission corresponding to the first R-TWT scheduling, and avoiding the clock deviation caused by the fact that the connection clock of the AP to which the AP MLD is attached is not completely synchronized, thereby delaying the transmission of the low-latency service, thereby realizing seamless transmission of the low-latency service.

[0091] In combination with some embodiments of the second aspect, in some embodiments, the first wireless frame includes an R-TWT migration element, and the R-TWT migration element carries a parameter information field for the first R-TWT scheduling.

[0092] In the above embodiment, by carrying the R-TWT migration element in the first wireless frame, during the process of performing the first R-TWT scheduling migration, the parameter information field of the first R-TWT scheduling can be determined according to the first wireless frame, and the first R-TWT scheduling of the first connection can be migrated to the second connection, thereby improving the migration rate and reducing the time required to migrate the first R-TWT scheduling.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the parameter information field of the first R-TWT scheduling includes at least one of the following:

[0094] A timer deviation subfield, where the timer deviation subfield indicates a timer deviation between the first connection and the second connection;

[0095] The second connection bitmap subfield indicates that the first R-TWT schedules a target connection that can be migrated, and the target connection includes the second connection.

[0096] In the above embodiment, by setting the parameter information field of the first R-TWT scheduling to include the timer deviation subfield between the first connection and the second connection, it is convenient to adjust the target wake-up time of the first R-TWT scheduling under the new connection (second connection) after the migration according to the clock deviation between the connection clocks of the first connection and the second connection during the migration of the first R-TWT scheduling, so as to avoid the clock deviation between the connection clocks of the first connection and the second connection, which causes the target wake-up time of the first R-TWT scheduling under the second connection to be delayed, thereby affecting the transmission of low-latency services. By setting the parameter information field of the first R-TWT scheduling to include the second connection bitmap subfield, it is convenient to determine the second connection to be migrated by the first R-TWT scheduling from the target connection that can be migrated by the first R-TWT scheduling indicated by the second connection bitmap subfield during the migration of the first R-TWT scheduling.

[0097] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include:

[0098] The R-TWT migration element also carries the first R-TWT SP scheduled by R-TWT under the first connection;

[0099] The time indicated by the first R-TWT SP is offset by the time shift timer to obtain the second R-TWT SP.

[0100] In the above embodiment, the R-TWT migration element carries the first R-TWT SP of the first R-TWT scheduling under the first connection and the timer deviation between the first connection and the second connection, so that in the process of performing the first R-TWT scheduling migration, based on the first R-TWT SP and the timer deviation, the time offset timer deviation indicated by the first R-TWT SP is obtained to obtain the second R-TWT SP, and adjust the target wake-up time (i.e., the second R-TWT SP) of the first R-TWT scheduling under the new connection (second connection) after migration, so as to achieve the alignment of the target wake-up time after migration and the original target wake-up time (first R-TWT SP), and avoid the clock deviation caused by the connection clock of the AP MLD's affiliated AP is not completely synchronized, which affects the transmission of low-latency services and causes transmission delays.

[0101] In combination with some embodiments of the second aspect, in some embodiments, when there are multiple first R-TWT schedules, the parameter information field of the first R-TWT schedule includes at least one subfield; each subfield includes parameter information of a first R-TWT schedule.

[0102] In the above embodiment, by setting a subfield of parameter information for each first R-TWT scheduling in the parameter information field of the first R-TWT scheduling, it is convenient to determine the parameter information of each first R-TWT scheduling to be migrated through each subfield during the process of migrating the first R-TWT scheduling.

[0103] In combination with some embodiments of the second aspect, in some embodiments, the R-TWT migration element also carries a migration timeout field; the migration timeout field indicates the maximum duration required to schedule the migration of the R-TWT of the first connection to the second connection.

[0104] In the above embodiment, the R-TWT migration element carries a migration timeout field, which facilitates the determination of the maximum duration required to migrate the R-TWT scheduling of the first connection to the second connection through the migration timeout field during the first R-TWT scheduling migration, thereby avoiding the time for executing the migration operation exceeding the maximum duration, affecting the transmission of low-latency services, and causing transmission delays.

[0105] In combination with some embodiments of the second aspect, in some embodiments, the R-TWT migration element also carries a control field; the control field includes at least one of a migration timeout existence flag, a second connection bitmap size flag, and a timer deviation existence flag.

[0106] In the above embodiment, the R-TWT migration element carries a control field, which facilitates the determination of whether there is a maximum duration required to migrate the R-TWT scheduling of the first connection to the second connection, the size of the second connection bitmap, and whether there is a timer deviation through the migration timeout existence flag, the second connection bitmap size flag, and the timer deviation existence flag in the control field during the first R-TWT scheduling migration.

[0107] In combination with some embodiments of the second aspect, in some embodiments, when the migration timeout existence flag is set to the first parameter value, the R-TWT migration element is marked to carry a migration timeout duration field.

[0108] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the specific parameter value set by the migration timeout existence flag can be used to determine whether the R-TWT migration element carries the migration timeout duration field, thereby saving the time required to further identify the migration timeout duration field when the migration timeout existence flag is not the first parameter value. In addition, by setting the migration timeout existence flag to different parameter values ​​to identify whether the R-TWT migration element carries the migration timeout duration field, the amount of transmission data in the first wireless frame can also be saved.

[0109] In combination with some embodiments of the second aspect, in some embodiments, the second connection bitmap size identification bit is set to different parameter values, indicating that the sizes of the second connection bitmap are different.

[0110] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the size of the second connection bitmap can be determined, and the number range of target connections that can be migrated by the first R-TWT scheduling can be determined.

[0111] In combination with some embodiments of the second aspect, in some embodiments, when the timer deviation existence flag is set to the second parameter value, the parameter information field indicating the first R-TWT scheduling includes a timer deviation subfield.

[0112] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the specific parameter value set by the timer deviation presence flag can be used to determine whether the parameter information field of the first R-TWT scheduling includes the timer deviation subfield, thereby saving the time required to further identify the timer deviation subfield when the timer deviation presence flag is not the first parameter value. In addition, by setting the timer deviation presence flag to different specific parameter values ​​to identify whether the parameter information field of the first R-TWT scheduling includes the timer deviation subfield, the amount of transmission data in the first wireless frame can also be saved.

[0113] In combination with some embodiments of the second aspect, in some embodiments, the first connection and the second connection are non-simultaneous transmit and receive NSTR (Non-Simultaneous Transmit and Receive) connection pairs, and there is no timer deviation subfield in the parameter information field of the first R-TWT scheduling.

[0114] In the above embodiment, when the first connection and the second connection are non-simultaneous NSTR connection pairs, the timer deviation subfield is set to not exist in the parameter information field of the first R-TWT scheduling, so as to combine the correlation between the first connection and the second connection to determine whether there is a clock deviation between the connection clocks of the first connection and the second connection.

[0115] In conjunction with some embodiments of the second aspect, in some embodiments, migrating the first R-TWT scheduling of the first connection to the second connection may include:

[0116] Before the first connection fails or is interrupted, the first R-TWT scheduling is migrated to the second connection.

[0117] In the above embodiment, when the first connection fails or is interrupted, the first R-TWT scheduling is migrated to the second connection, and the first R-TWT scheduling can continue to be executed on the second connection, avoiding interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0118] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include:

[0119] Determine a second radio frame; the second radio frame includes second identification information, and the second identification information identifies confirmation information for the first radio frame;

[0120] Send a second wireless frame; instruct to perform a migration operation of migrating the first R-TWT scheduling of the first connection to the second connection.

[0121] In the above embodiment, the second wireless frame can be determined based on the received first wireless frame, the confirmation information for the first wireless frame can be identified by the second identification information carried by the second wireless frame, and the confirmation information of the first wireless frame can be sent to the AP MLD, instructing the AP MLD to migrate the first R-TWT scheduling of the first connection to the second connection, so as to avoid the interruption of the low-latency service transmission corresponding to the first R-TWT scheduling.

[0122] In combination with some embodiments of the second aspect, in some embodiments, the second wireless frame includes: parameter information of the first R-TWT scheduling and a second connection bitmap.

[0123] In the above embodiment, the second radio frame including the parameter information of the first R-TWT scheduling and the second connection bitmap can be determined based on the information parsed from the first radio frame.

[0124] In conjunction with some embodiments of the second aspect, in some embodiments, sending the second radio frame may include:

[0125] Before the time indicated by the migration timeout duration field, the second radio frame is sent under the first connection.

[0126] In the above embodiment, by sending the second wireless frame through the first connection before the time indicated by the migration timeout duration field, confirmation information for the first wireless frame can be sent to the AP MLD to instruct the AP MLD to migrate the first R-TWT scheduling to the second connection when the first connection fails or is interrupted, and continue to execute the first R-TWT scheduling on the second connection, so as to avoid interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0127] In a third aspect, an embodiment of the present disclosure provides a multi-connection access point device, the multi-connection access point device including:

[0128] A processing module, configured to determine a first radio frame;

[0129] The first radio frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service within the second R-TWT SP under the second connection under the first R-TWT scheduling;

[0130] a transceiver module, configured to send a first wireless frame;

[0131] In a fourth aspect, an embodiment of the present disclosure provides a multi-connection site device, the multi-connection site device including:

[0132] a transceiver module, configured to receive a first wireless frame;

[0133] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting low-latency services within the second R-TWT SP under the second connection under the first R-TWT scheduling.

[0134] In a fifth aspect, an embodiment of the present disclosure provides a multi-connection access point device, the multi-connection access point device including:

[0135] one or more processors;

[0136] The terminal is used to execute the low-latency service transmission method described in the optional implementation manner of the first aspect above.

[0137] In a sixth aspect, an embodiment of the present disclosure provides a multi-connection site device, the multi-connection site device including:

[0138] one or more processors;

[0139] The terminal is used to execute the low-latency service transmission method described in the optional implementation manner of the second aspect above.

[0140] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, which includes a multi-connection access point device and a multi-connection site device, wherein the multi-connection access point device is configured to implement the low-latency service transmission method provided in the first aspect above, and the multi-connection site device is configured to implement the low-latency service transmission method described in the optional implementation method of the second aspect above.

[0141] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the low-latency service transmission method described in the optional implementation of the first or second aspect above.

[0142] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the low-latency service transmission method described in the optional implementation of the first or second aspect.

[0143] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the low-latency service transmission method described in the optional implementation of the first or second aspect above.

[0144] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the low-latency service transmission method described in the optional implementation of the first or second aspect above.

[0145] It is understandable that the aforementioned multi-connection access point device, multi-connection station device, communication system, storage medium, program product, computer program, chip, or chip system is used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0146] The embodiments of the present disclosure propose a low-latency service transmission method, a multi-connection access point device, and a multi-connection site device to further improve the R-TWT mechanism and reduce Wi-Fi network power consumption.

[0147] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0148] In some embodiments, terms such as low-latency service transmission and information processing method, communication method, etc. can be replaced with each other, terms such as multi-connection access point device and information processing device, communication device, etc. can be replaced with each other, terms such as multi-connection site device and information processing device, communication device, etc. can be replaced with each other, and terms such as information processing system, communication system, etc. can be replaced with each other.

[0149] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0150] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0151] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0152] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0153] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0154] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0155] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0156] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0157] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0158] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0159] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0160] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0161] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0162] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0163] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0164] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0165] As shown in FIG1 , a communication system 100 includes a multi-connection access point device 101 and a multi-connection station device 102 .

[0166] In some embodiments, an access point (AP) device is a device with wireless to wired bridging functionality, and is responsible for extending services provided by a wired network to a wireless network. The multi-connection AP device 101 is an AP device that supports multi-connection communication functionality.

[0167] In some embodiments, a station device (STA), such as an electronic device with wireless network access capability, provides a frame delivery service to enable information to be transmitted. The multi-connection station device 102 is a station device that supports multi-connection communication capabilities.

[0168] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0169] FIG2A is an interactive diagram of a low-latency service transmission method according to an embodiment of the present disclosure. As shown in FIG2A , an embodiment of the present disclosure relates to a low-latency service transmission method, the method comprising:

[0170] Step 201: AP MLD determines a first wireless frame; wherein the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0171] The first connection is the connection before the first R-TWT scheduling migration, which can also be called the original connection. The second connection is the connection after the first R-TWT scheduling migration, which can also be called the target connection.

[0172] Optionally, the first AP working in the first connection and the second AP working in the second connection belong to the same multi-connection access point device AP MLD.

[0173] TWT is a technology used for energy conservation, aiming to further reduce the power consumption of Wi-Fi networks. Specifically, TWT technology enables STAs and APs to negotiate the service period (SP) to determine the STA's sleep and wake-up time and frequency; the STA remains active and communicates during the service period, allowing it to sleep outside of the service period to achieve energy conservation. In addition, TWT technology can also enable the AP to provide higher quality services to multiple STAs, minimize contention or overlap, and improve spectrum efficiency while reducing Wi-Fi network power consumption.

[0174] In low-latency transmission scenarios, the real-time data traffic of many applications has strict delay requirements, for example, the average delay or maximum delay is on the order of a few milliseconds to tens of milliseconds, and the applications require real-time data traffic to have extremely small jitter and strong reliability. In order to further ensure the communication of low-latency services, the restricted-target wake time (R-TWT) is proposed based on the technology of TWT. The R-TWT mechanism allows the AP to use enhanced media access protection mechanism and resource reservation mechanism to provide more predictable delay to distinguish delay-sensitive traffic from other types of traffic, so that the AP can reduce the worst-case delay and / or reduce jitter to provide more reliable services.

[0175] Specifically, R-TWT is used to serve low-latency services, such as those with an average delay of less than 10 milliseconds. Within the R-TWT SP, only services identified as low-latency services communicate, while other communication services are suspended or postponed during this phase, thereby ensuring the transmission of low-latency services.

[0176] In an embodiment of the present disclosure, an R-TWT planning device (e.g., an AP MLD, or Scheduling AP MLD) and a planned device (e.g., a non-AP MLD, or Scheduled non-AP MLD) may pre-establish an R-TWT schedule. Optionally, the first R-TWT schedule may be an R-TWT schedule initiated by a first AP to a first STA associated with the first AP.

[0177] For ease of description, the following mainly describes an example of an AP communicating with a STA under multiple connections. However, the example embodiments of the present disclosure are not limited to this. Figure 2B shows a multi-connection TWT agreement establishment scenario established between a non-AP MLD and an AP MLD provided in an embodiment of the present disclosure. In this scenario, the AP MLD and the non-AP MLD have 3 subordinate APs and 3 subordinate STAs, respectively; wherein, it is assumed that AP1 communicates with STA1 through the corresponding first communication connection (or link) Link 1 (i.e., AP1-STA1 corresponds to Link1), similarly, AP2 communicates with STA2 through the corresponding second connection Link 2 (i.e., AP2-STA2 corresponds to Link2), and AP3 communicates with STA3 through the third connection Link 3 (i.e., AP3-STA3 corresponds to Link3).

[0178] In a wireless LAN, a Basic Service Set (BSS) consists of an AP and one or more stations (STAs) communicating with the AP. If the coverage of two or more BSSs overlap, an Overlapping Basic Service Set (OBSS) is formed. Based on the application scenario shown in Figure 2B, AP1 and STA1 can form BSS1, AP2 and STA2 can form BSS2, and AP3 and STA3 can form BSS3.

[0179] In some scenarios, such as when the connection mapped by the R-TWT schedule is interrupted or fails, such as when the connection is released or the connection is not enabled after establishment, the R-TWT schedule under the connection that is about to be interrupted or failed can be migrated, for example, to a connection with normal service transmission, so as to continue to execute the R-TWT schedule on the migrated connection, thereby avoiding interruption of low-latency service transmission corresponding to the R-TWT schedule.

[0180] As shown in Figure 2B, the R-TWT scheduling under link1 includes R-TWT Schedule1 (R-TWT scheduling 1) and R-TWT Schedule2 (R-TWT scheduling 2). When link1 fails or is interrupted, the first R-TWT scheduling that needs to be migrated may include R-TWT Schedule1 and R-TWT Schedule2. As shown in Figure 2B, R-TWT Schedule1 can be migrated from link1 to link3, and R-TWT Schedule2 can be migrated from link1 to link2. In the process of migrating R-TWT Schedule1, link1 is the above-mentioned first connection, and link3 is the above-mentioned second connection. In the process of migrating R-TWT Schedule2, link1 is the above-mentioned first connection, and link2 is the above-mentioned second connection.

[0181] In some scenarios, the target wake-up time in R-TWT scheduling (such as R-TWT SP, R-TWT service time) is the relative time under the connection where the R-TWT scheduling is located. Since the connection clocks of the APs attached to the same AP MLD are not completely synchronized, there is a certain clock deviation between the connection clocks under each connection (such as the delay t' shown in Figure 2B). During the process of R-TWT scheduling migration, if low-latency service transmission is performed according to the target wake-up time of R-TWT scheduling migration, it may cause the target wake-up time of R-TWT scheduling under the original connection before migration (i.e., the first connection) and the new connection after migration (i.e., the second connection) to be delayed, affecting the transmission of low-latency services.

[0182] Optionally, in an embodiment of the present disclosure, the first wireless frame includes a beacon frame or a probe response frame.

[0183] Optionally, migrating the first R-TWT scheduling of the first connection to the second connection includes: migrating the first R-TWT scheduling to the second connection before the first connection fails or is interrupted.

[0184] In the above embodiment, when the first connection fails or is interrupted, the first R-TWT scheduling is migrated to the second connection, and the first R-TWT scheduling can continue to be executed on the second connection, avoiding interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0185] Optionally, the first wireless frame includes an R-TWT migration (R-TWT Migration) element, and the R-TWT migration element carries a field for parameter information of the first R-TWT scheduling (i.e., R-TWT migration information).

[0186] Before the first connection fails or is interrupted, the AP MLD broadcasts the migration information of the first R-TWT scheduling through the R-TWT Migration element. Specifically, the AP MLD carries the R-TWT Migration element in the first radio frame to broadcast the parameter information of the first R-TWT scheduling.

[0187] Optionally, the R-TWT migration element may further include at least one of the following: an element identification field, a length field, a control field, and a migration timeout field. As an example, the format of the R-TWT migration element is shown in Table 1 below:

[0188] Table 1:

[0189] As shown in Table 1, the R-TWT migration elements include but are not limited to the element identification (element ID) field, the length (Length) field, the control (Control) field, the migration timeout (Migration Timeout) field, the R-TWT migration information (R-TWT Migration Info) field, etc.

[0190] Optionally, the control field may be used as the first field, the migration timeout field may be used as the second field, and the parameter information field of the first R-TWT scheduling may be used as the third field.

[0191] In the above embodiment, by carrying the R-TWT migration element in the first wireless frame, during the process of performing the first R-TWT scheduling migration, the parameter information field of the first R-TWT scheduling is determined according to the first wireless frame, and the first R-TWT scheduling of the first connection is migrated to the second connection, thereby improving the migration rate and reducing the time required to migrate the first R-TWT scheduling.

[0192] Optionally, the parameter information field of the first R-TWT scheduling includes at least one of the following:

[0193] A timer deviation subfield, where the timer deviation subfield indicates a timer deviation between the first connection and the second connection;

[0194] The second connection bitmap subfield indicates that the first R-TWT schedules a target connection that can be migrated, and the target connection includes the second connection.

[0195] Optionally, in the second connection bitmap, the connection with the bit set to 1 is the target connection that can be migrated by the first R-TWT scheduling.

[0196] In the above embodiment, by setting the parameter information field of the first R-TWT scheduling to include a timer deviation subfield between the first connection and the second connection, it is convenient to adjust the target wake-up time of the first R-TWT scheduling under the new connection (second connection) after migration according to the clock deviation between the connection clocks of the first connection and the second connection during the migration of the first R-TWT scheduling, thereby avoiding the clock deviation between the connection clocks of the first connection and the second connection, resulting in a delay in the target wake-up time of the first R-TWT scheduling under the second connection, affecting the transmission of low-latency services.

[0197] By setting the parameter information field of the first R-TWT scheduling to include the second connection bitmap subfield, it is convenient to determine the second connection for migrating the first R-TWT scheduling from the target connections that can be migrated by the first R-TWT scheduling indicated by the second connection bitmap subfield during the process of migrating the first R-TWT scheduling.

[0198] Optionally, the above method may further include:

[0199] The R-TWT migration element also carries the first R-TWT SP scheduled by R-TWT under the first connection;

[0200] The time indicated by the first R-TWT SP is offset by the time shift timer to obtain the second R-TWT SP.

[0201] As an example, when the time indicated by the first R-TWT SP is t1 to t2 and the timer offset is t', the time indicated by the second R-TWT SP is (t1+t') to (t2+t').

[0202] In the above embodiment, the R-TWT migration element carries the first R-TWT SP of the first R-TWT scheduling under the first connection and the timer deviation between the first connection and the second connection, so that in the process of performing the first R-TWT scheduling migration, based on the first R-TWT SP and the timer deviation, the time offset timer deviation indicated by the first R-TWT SP is obtained to obtain the second R-TWT SP, and adjust the target wake-up time (i.e., the second R-TWT SP) of the first R-TWT scheduling under the new connection (second connection) after migration, so as to achieve alignment of the target wake-up time after migration with the original target wake-up time (first R-TWT SP), and avoid the clock deviation caused by the incomplete synchronization of the connection clock of the affiliated AP of the AP MLD, which affects the transmission of low-latency services and causes transmission delays.

[0203] Optionally, when there are multiple first R-TWT schedules, the parameter information field of the first R-TWT schedule includes at least one subfield; each subfield includes parameter information of a first R-TWT schedule.

[0204] As an example, the format of each subfield in the parameter information field of the first R-TWT scheduling is as shown in Table 2 below:

[0205] Table 2:

[0206] As shown in Table 2, each subfield in the parameter information field of the first R-TWT scheduling includes but is not limited to a Destination Link Bitmap subfield, a TSF Offset subfield, and the like.

[0207] Optionally, the quantity information of the first R-TWT scheduling, that is, the number of R-TWT scheduling that needs to be migrated, can be determined by the number of subfields in the parameter information field of the first R-TWT scheduling.

[0208] Optionally, each subfield may also include the identification information of the first R-TWT scheduling corresponding to the subfield (for example, the identification of the R-TWT scheduling), the original connection information (the connection before migration), and the target connection information (the target connection of migration).

[0209] In the above embodiment, by setting a subfield of parameter information for each first R-TWT scheduling in the parameter information field of the first R-TWT scheduling, it is convenient to determine the parameter information of each first R-TWT scheduling to be migrated through each subfield during the process of migrating the first R-TWT scheduling.

[0210] Optionally, the R-TWT migration element also carries a migration timeout duration field; the migration timeout duration field indicates the maximum duration required to schedule the migration of the R-TWT of the first connection to the second connection.

[0211] The migration timeout duration may be determined based on the time when the first radio frame is determined and the time when the first connection fails, or based on the time when the first radio frame is determined and the time when the first connection is interrupted. For example, if the time when the first radio frame is determined is t3, the time when the first connection fails is t4, and the time when the first connection is interrupted is t5, the maximum duration indicated by the migration timeout duration field may be set to (t4-t3) or (t5-t3).

[0212] In the above embodiment, the R-TWT migration element carries a migration timeout field, which facilitates the determination of the maximum duration required to migrate the R-TWT scheduling of the first connection to the second connection through the migration timeout field during the first R-TWT scheduling migration, thereby avoiding the time for executing the migration operation exceeding the maximum duration, affecting the transmission of low-latency services, and causing transmission delays.

[0213] Optionally, the R-TWT migration element also carries a control field; the control field includes at least one of a migration timeout existence flag, a second connection bitmap size flag, and a timer deviation existence flag.

[0214] As an example, the format of the control field is shown in Table 3 below:

[0215] Table 3:

[0216] As shown in Table 3, the control field includes but is not limited to a Migration Timeout Present flag, a TSF Offset Present flag, a Destination Link Bitmap Size, and the like.

[0217] The parameter value of the corresponding parameter can be identified by setting the identification bit in the control field to a different value.

[0218] Optionally, the control field can be the first field in the R-TWT migration element, that is, the numerical value of each identification bit in the first field can be used to determine whether to parse other fields (such as the second field and the third field) in the R-TWT migration element.

[0219] In the above embodiment, the R-TWT migration element carries a control field, which facilitates the determination of whether there is a maximum duration required to migrate the R-TWT scheduling of the first connection to the second connection, the size of the second connection bitmap, and whether there is a timer deviation through the migration timeout existence flag, the second connection bitmap size flag, and the timer deviation existence flag in the control field during the first R-TWT scheduling migration.

[0220] Optionally, when the migration timeout existence flag is set to the first parameter value, it indicates that the R-TWT migration element carries a migration timeout duration field.

[0221] As an example, when the migration timeout existence flag is set to the first parameter value (for example, 1), it indicates that the R-TWT migration element carries the migration timeout duration field; otherwise, it indicates that the R-TWT migration element does not carry the migration timeout duration field.

[0222] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the specific parameter value set by the migration timeout existence flag can be used to determine whether the R-TWT migration element carries the migration timeout duration field, thereby saving the time required to further identify the migration timeout duration field when the migration timeout existence flag is not the first parameter value. In addition, by setting the migration timeout existence flag to different parameter values ​​to identify whether the R-TWT migration element carries the migration timeout duration field, the amount of transmission data in the first wireless frame can also be saved.

[0223] Optionally, the second connection bitmap size flag is set to a different parameter value, indicating that the size of the second connection bitmap is different.

[0224] As an example, when the second connection bitmap size flag is set to 1, it indicates that the size of the second connection bitmap is 16 bits, that is, the number of connections attached to the AP MLD attached to the second connection (that is, the AP MLD attached to the first connection) is 16; when the second connection bitmap size flag is set to 0, it indicates that the size of the second connection bitmap is 8 bits, that is, the number of connections attached to the AP MLD attached to the second connection (that is, the AP MLD attached to the first connection) is 8.

[0225] Optionally, based on the specific value of each bit in the second connection bitmap, it can be determined whether the connection indicated by the bit is the target connection. For example, when the value of the bit is 1, it can be determined that the connection indicated by the bit is the target connection that can be migrated by the first R-TWT scheduling; when the value of the bit is 0, it can be determined that the connection indicated by the bit is not the target connection that can be migrated by the first R-TWT scheduling.

[0226] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the size of the second connection bitmap can be determined, the number range of connections attached to the AP MLD can be determined, and then the number range of target connections that can be migrated by the first R-TWT scheduling can be determined based on the specific values ​​of each bit in the second connection bitmap.

[0227] Optionally, when the timer deviation existence flag is set to the second parameter value, the parameter information field indicating the first R-TWT scheduling includes a timer deviation subfield.

[0228] As an example, when the timer deviation presence identification bit is set to the second parameter value (for example, 1), the parameter information field identifying the first R-TWT scheduling includes a timer deviation subfield; otherwise, the parameter information field identifying the first R-TWT scheduling does not include a timer deviation subfield.

[0229] In the above embodiment, during the process of performing the first R-TWT scheduling migration, the specific parameter value set by the timer deviation presence flag can be used to determine whether the parameter information field of the first R-TWT scheduling includes the timer deviation subfield, thereby saving the time required to further identify the timer deviation subfield when the timer deviation presence flag is not the first parameter value. In addition, by setting the timer deviation presence flag to different specific parameter values ​​to identify whether the parameter information field of the first R-TWT scheduling includes the timer deviation subfield, the amount of transmission data in the first wireless frame can also be saved.

[0230] Optionally, the first connection and the second connection are non-simultaneous transmit and receive (NSTR) connection pairs, and there is no timer deviation subfield in the parameter information field of the first R-TWT scheduling.

[0231] When the first connection and the second connection are non-simultaneous NSTR connection pairs, information transmission on the first connection does not affect information transmission on the second connection, and it can be determined that there is no timer deviation between the connection clocks of the first connection and the second connection. The first R-TWT can be directly scheduled to the first R-TWT SP of the first connection as the second R-TWT SP of the first R-TWT scheduled to the second connection.

[0232] In the above embodiment, when the first connection and the second connection are non-simultaneous NSTR connection pairs, the timer deviation subfield is set to not exist in the parameter information field of the first R-TWT scheduling, so as to combine the correlation between the first connection and the second connection to determine whether there is a clock deviation between the connection clocks of the first connection and the second connection.

[0233] Step 202: The AP MLD sends a first radio frame to the non-AP MLD.

[0234] Step 203: The non-AP MLD determines a second radio frame; the second radio frame includes second identification information, and the second identification information identifies confirmation information for the first radio frame.

[0235] Optionally, the second radio frame includes a parameter information field of the first R-TWT scheduling and a second connection bitmap subfield.

[0236] The second radio frame may include other subfields in the first radio frame except the timer offset subfield and the migration timeout field.

[0237] Optionally, in the second radio frame, the target connection indicated by the second connection bitmap in the second connection bitmap subfield may be: a second connection obtained after selecting the target connection indicated by the second connection bitmap in the first radio frame. For example, when the target connections indicated in the first radio frame include link-a, link-b, and link-c, the target connection indicated in the second radio frame is link-b, that is, the non-AP MLD can select the final migrated second connection from the target connections that can be migrated by the first R-TWT scheduling.

[0238] In the above embodiment, specific confirmation information made by the non-AP MLD for the first radio frame, ie, the parameter information of the first R-TWT scheduling and the second connection bitmap, can be determined according to the second radio frame determined by the non-AP MLD.

[0239] Step 204: The non-AP MLD sends a second radio frame to the AP MLD, instructing the AP MLD to perform a migration operation of migrating the first R-TWT scheduling of the first connection to the second connection.

[0240] In the above embodiment, the second wireless frame can be determined based on the received first wireless frame, the confirmation information for the first wireless frame can be identified by the second identification information carried by the second wireless frame, and the confirmation information of the first wireless frame can be sent to the AP MLD, instructing the AP MLD to migrate the first R-TWT scheduling of the first connection to the second connection, so as to avoid the interruption of the low-latency service transmission corresponding to the first R-TWT scheduling.

[0241] Optionally, the non-AP MLD may send a second radio frame to the AP MLD in the first connection before the time indicated by the migration timeout duration.

[0242] In the above embodiment, by sending the second wireless frame through the first connection before the time indicated by the migration timeout duration field, confirmation information for the first wireless frame can be sent to the AP MLD to instruct the AP MLD to migrate the first R-TWT scheduling to the second connection when the first connection fails or is interrupted, and continue to execute the first R-TWT scheduling on the second connection, so as to avoid interruption of low-latency service transmission corresponding to the first R-TWT scheduling.

[0243] In this way, the second wireless frame can be sent through the first connection before the time indicated by the migration timeout period arrives, so that the AP MLD migrates the first R-TWT scheduling to the second connection, and continues to execute the first R-TWT scheduling on the second connection, avoiding the interruption of low-latency service transmission corresponding to the first R-TWT schedule and avoiding migration timeout.

[0244] Step 205: If the AP MLD receives a second radio frame before the time indicated by the migration timeout duration field, it migrates the first R-TWT scheduling to any second connection indicated by the second connection bitmap in the second radio frame. The time indicated by the first R-TWT SP of the R-TWT scheduling under the first connection is offset by the timer deviation between the first connection and the second connection to obtain the second R-TWT SP of the second AP under the second connection of the first R-TWT scheduling. Within the second R-TWT SP, the second STA associated with the second AP transmits the low-latency service corresponding to the first R-TWT scheduling.

[0245] Optionally, after the time indicated by the migration timeout duration field of the AP MLD, if the second radio frame is not received, any target connection indicated by the second connection bitmap in the first radio frame can be used as the second connection, and the first R-TWT scheduling can be migrated to the second connection. And for the time indicated by the first R-TWT SP of the R-TWT scheduling under the first connection, the timer deviation between the first connection and the second connection is offset to obtain the second R-TWT SP of the second AP under the second connection of the first R-TWT scheduling. Within the second R-TWT SP, the second STA associated with the second AP transmits the low-latency service corresponding to the first R-TWT scheduling.

[0246] Optionally, when there are multiple first R-TWT schedulings, AP MLD can migrate each first R-TWT scheduling separately according to the migration method described in step 205, and determine the second R-TWT SP after migration. Within the determined second R-TWT SP, the second STA associated with the second AP transmits the low-latency service corresponding to the first R-TWT scheduling.

[0247] In an embodiment of the present disclosure, when the first connection fails or is interrupted, the first R-TWT scheduling can continue to be executed on the second connection within the second R-TWT SP under the first R-TWT scheduling. While avoiding the interruption of the low-latency service transmission corresponding to the first R-TWT scheduling, the clock deviation caused by the fact that the connection clock of the affiliated AP of the AP MLD is not completely synchronized is avoided, which delays the transmission of the low-latency service and realizes seamless transmission of the low-latency service.

[0248] In some embodiments, terms such as "frame" and "radio frame" may be used interchangeably.

[0249] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0250] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0251] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0252] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0253] The communication method according to the embodiments of the present disclosure may include at least one of steps 201 to 205. For example, step 201 may be implemented as an independent embodiment, step 201 + step 202 may be implemented as an independent embodiment, step 201 + step 202 + step 205 may be implemented as an independent embodiment, and step 201 + step 202 + step 203 + step 204 + step 205 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0254] In some embodiments, the steps of determining the various fields in the R-TWT migration element (eg, element identification field, length field, control field, migration timeout field, etc.) in step 201 may be performed in an interchanged order or simultaneously.

[0255] In some embodiments, step 203 and step 204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0256] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0257] FIG3A is a flow chart illustrating a low-latency service transmission method according to an embodiment of the present disclosure. As shown in FIG3A , an embodiment of the present disclosure relates to a low-latency service transmission method. Optionally, the above method can be applied to AP MLD 101.

[0258] As shown in FIG3A , the method includes:

[0259] Step 3101, determining a first radio frame;

[0260] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0261] The optional implementation of step 3101 can refer to the optional implementation of step 201 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0262] Step 3102: Send the first wireless frame.

[0263] The optional implementation of step 3102 can refer to the optional implementation of step 202 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0264] In some embodiments, after determining the first radio frame, the AP MLD 101 may send the first radio frame to the non-AP MLD 102 .

[0265] Alternatively, the non-AP MLD 102 may determine the second radio frame based on the received first radio frame. Specific methods for determining the second radio frame may refer to the optional implementation of step 203 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0266] Step 3103: Perform the migration operation of the first R-TWT scheduling. That is, migrate the first R-TWT scheduling of the first connection to the second connection, and transmit the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0267] The optional implementation of step 3103 can refer to the optional implementation of step 205 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0268] Optionally, the specific manner of performing the migration operation of the first R-TWT scheduling can be determined based on the time indicated by the migration timeout duration field and whether the second wireless frame is received, and the first R-TWT scheduling of the first connection can be migrated to the second connection based on the determined manner of performing the migration operation of the first R-TWT scheduling.

[0269] The low-latency service method involved in the embodiments of the present disclosure may include at least one of steps 3101 to 3103. For example, step 3101 may be implemented as an independent embodiment, step 3101 + step 3102 may be implemented as an independent embodiment, and step 3101 + step 3102 + step 3103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0270] In some embodiments, referring to the optional implementation of step 201, the steps of determining the various fields in the R-TWT migration element (e.g., element identification field, length field, control field, migration timeout field, etc.) in step 3101 can be exchanged in order or performed simultaneously.

[0271] FIG3B is a flow chart of a low-latency service transmission method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a low-latency service transmission method, which can optionally be applied to AP MLD 101.

[0272] As shown in FIG3B , the method includes:

[0273] Step 3201, determining a first radio frame;

[0274] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0275] The optional implementation of step 3201 can refer to the optional implementation of step 201 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0276] Step 3202: Send the first wireless frame.

[0277] The optional implementation of step 3202 can refer to the optional implementation of step 202 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0278] In some embodiments, after determining the first radio frame, the AP MLD 101 may send the first radio frame to the non-AP MLD 102 .

[0279] Alternatively, the non-AP MLD 102 may determine the second radio frame based on the received first radio frame. Specific methods for determining the second radio frame may refer to the optional implementation of step 203 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0280] Step 3203: Determine the specific method for performing the migration operation of the first R-TWT scheduling based on the time indicated by the migration timeout duration field and whether the second radio frame is received, and migrate the first R-TWT scheduling of the first connection to the second connection based on the determined method for performing the migration operation of the first R-TWT scheduling. Transmit the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection under the first R-TWT scheduling.

[0281] The optional implementation of step 3203 can refer to the optional implementation of step 205 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0282] Optionally, the second radio frame may be determined by the non-AP MLD 102. For optional implementations thereof, reference may be made to the optional implementations of step 203 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0283] Optionally, the second radio frame may be sent by the non-AP MLD 102. For optional implementations thereof, reference may be made to the optional implementations of step 204 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0284] The low-latency service method involved in the embodiments of the present disclosure may include at least one of steps 3201 to 3203. For example, step 3201 may be implemented as an independent embodiment, step 3201 + step 3202 may be implemented as an independent embodiment, and step 3201 + step 3202 + step 3203 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0285] In some embodiments, referring to the optional implementation of step 201, the steps of determining the various fields in the R-TWT migration element (e.g., element identification field, length field, control field, migration timeout field, etc.) in step 3201 can be exchanged in order or performed simultaneously.

[0286] FIG3C is a flow chart of a low-latency service transmission method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a low-latency service transmission method, which can optionally be applied to AP MLD 101.

[0287] As shown in FIG3C , the method includes:

[0288] Step 3301, determining a first radio frame;

[0289] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0290] The optional implementation of step 3301 can refer to the optional implementation of step 201 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0291] Step 3302: Send the first wireless frame.

[0292] The optional implementation of step 3302 can refer to the optional implementation of step 202 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0293] In some embodiments, after determining the first radio frame, the AP MLD 101 may send the first radio frame to the non-AP MLD 102 .

[0294] Alternatively, the non-AP MLD 102 may determine the second radio frame based on the received first radio frame. Specific methods for determining the second radio frame may refer to the optional implementation of step 203 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0295] Step 3303a: If a second radio frame is received before the time indicated by the migration timeout field, the first R-TWT scheduling can be migrated to any second connection indicated by the second connection bitmap in the second radio frame. The low-latency service corresponding to the first R-TWT scheduling is transmitted within the second R-TWT SP under the second connection of the first R-TWT scheduling.

[0296] Step 3303b: After the time indicated by the migration timeout field, if no second radio frame is received, any target connection indicated by the second connection bitmap in the first radio frame can be used as the second connection, and the first R-TWT schedule can be migrated to the second connection. The low-latency service corresponding to the first R-TWT schedule is transmitted within the second R-TWT SP under the second connection of the first R-TWT schedule.

[0297] The optional implementation of step 3303a and step 3303b can refer to the optional implementation of step 205 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0298] Optionally, the second radio frame may be determined by the non-AP MLD 102. For optional implementations thereof, reference may be made to the optional implementations of step 203 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0299] Optionally, the second radio frame may be sent by the non-AP MLD 102. For optional implementations thereof, reference may be made to the optional implementations of step 204 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0300] The low-latency service method involved in the embodiments of the present disclosure may include at least one of steps 3301 to 3303a. For example, step 3301 may be implemented as an independent embodiment, steps 3301 and 3302 may be implemented as independent embodiments, and steps 3301, 3302, and 3303a may be implemented as independent embodiments, but are not limited thereto.

[0301] The low-latency service method involved in the embodiments of the present disclosure may include at least one of steps 3301 to 3303b. For example, step 3301 may be implemented as an independent embodiment, steps 3301 and 3302 may be implemented as independent embodiments, and steps 3301, 3302, and 3303b may be implemented as independent embodiments, but are not limited thereto.

[0302] In some embodiments, referring to the optional implementation of step 201, the steps of determining the various fields in the R-TWT migration element (e.g., element identification field, length field, control field, migration timeout field, etc.) in step 3301 can be exchanged in order or performed simultaneously.

[0303] FIG4 is a flow chart illustrating a low-latency service transmission method according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure relates to a low-latency service transmission method, which can optionally be applied to a non-AP MLD 102.

[0304] As shown in FIG4 , the above method includes:

[0305] Step 401: Receive a first radio frame.

[0306] Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0307] The optional implementation of step 401 can refer to the optional implementation of step 202 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.

[0308] Optionally, the first radio frame may be determined by AP MLD 101. For optional implementations thereof, reference may be made to the optional implementations of step 201 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0309] Step 402: Determine a second radio frame; wherein the second radio frame includes second identification information, and the second identification information identifies confirmation information for the first radio frame.

[0310] The optional implementation of step 402 can refer to the optional implementation of step 203 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0311] Step 403: Send a second wireless frame to instruct the execution of a migration operation of migrating the first R-TWT scheduling of the first connection to the second connection.

[0312] Optionally, the second radio frame may be sent by the non-AP MLD 102. For optional implementations thereof, reference may be made to the optional implementations of step 204 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0313] Optionally, the migration operation may be performed by AP MLD 101. For its optional implementation, please refer to the optional implementation of step 205 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0314] The low-latency service method involved in the embodiments of the present disclosure may include at least one of steps 401 to 403. For example, step 401 may be implemented as an independent embodiment, and steps 401+402+403 may be implemented as independent embodiments, but are not limited thereto.

[0315] FIG5A is an interactive diagram of a low-latency service transmission method according to an embodiment of the present disclosure. As shown in FIG5A , an embodiment of the present disclosure relates to a low-latency service transmission method, the method comprising:

[0316] Step 5101: AP MLD101 determines a first wireless frame; wherein the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0317] The optional implementation of step 5101 can be found in the optional implementation of step 201 in Figure 2A, step 3101 in Figure 3A, step 3201 in Figure 3B, step 3301 in Figure 3C, and other related parts in the embodiments involved in Figures 2A, 3A, 3B, and 3C, which will not be repeated here.

[0318] Step 5102: AP MLD101 sends a first radio frame to non-AP MLD102.

[0319] The optional implementation of step 5102 can be found in the optional implementation of step 202 in Figure 2A, step 3102 in Figure 3A, step 3202 in Figure 3B, the optional implementation of step 3302 in Figure 3C, and other related parts in the embodiments involved in Figures 2A, 3A, 3B, and 3C, which will not be repeated here.

[0320] Step 5103: the non-AP MLD 102 determines a second radio frame; the second radio frame includes second identification information, and the second identification information identifies confirmation information for the first radio frame.

[0321] The optional implementation of step 5103 can refer to the optional implementation of step 203 in Figure 2, step 402 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0322] Step 5104: non-AP MLD102 sends a second radio frame to AP MLD103, instructing AP MLD101 to perform a migration operation of migrating the first R-TWT scheduling of the first connection to the second connection.

[0323] The optional implementation of step 5104 can refer to the optional implementation of step 204 in Figure 2, step 403 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0324] Step 5105: If AP MLD101 receives a second radio frame before the time indicated by the migration timeout duration field, the first R-TWT scheduling is migrated to any second connection indicated by the second connection bitmap in the second radio frame. The time indicated by the first R-TWT SP of the R-TWT scheduling under the first connection is offset by the timer deviation between the first connection and the second connection to obtain the second R-TWT SP of the second AP under the second connection of the first R-TWT scheduling. Within the second R-TWT SP, the second STA associated with the second AP transmits the low-latency service corresponding to the first R-TWT scheduling.

[0325] The optional implementation of step 5105 can be found in the optional implementation of step 205 of Figure 2, the optional implementation of step 3103 of Figure 3A, step 3203 of Figure 3B, step 3303a of Figure 3C, and step 403 of Figures 2A, 3A, 3B, 3C, and 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0326] FIG5B is an interactive diagram of a low-latency service transmission method according to an embodiment of the present disclosure. As shown in FIG5B , an embodiment of the present disclosure relates to a low-latency service transmission method, the method comprising:

[0327] Step 5201: AP MLD101 determines a first wireless frame; wherein the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

[0328] The optional implementation of step 5201 can be found in the optional implementation of step 201 in Figure 2A, step 3101 in Figure 3A, step 3201 in Figure 3B, step 3301 in Figure 3C, and other related parts in the embodiments involved in Figures 2A, 3A, 3B, and 3C, which will not be repeated here.

[0329] Step 5202: AP MLD101 sends a first radio frame to non-AP MLD102.

[0330] The optional implementation of step 5202 can be found in the optional implementation of step 202 in Figure 2A, step 3102 in Figure 3A, step 3202 in Figure 3B, the optional implementation of step 3302 in Figure 3C, and other related parts in the embodiments involved in Figures 2A, 3A, 3B, and 3C, which will not be repeated here.

[0331] Step 5203: The non-AP MLD 102 determines a second radio frame; the second radio frame includes second identification information, and the second identification information identifies confirmation information for the first radio frame.

[0332] The optional implementation of step 5203 can refer to the optional implementation of step 203 in Figure 2, step 402 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0333] Step 5204: non-AP MLD102 sends a second radio frame to AP MLD103, instructing AP MLD101 to perform a migration operation of migrating the first R-TWT scheduling of the first connection to the second connection.

[0334] The optional implementation of step 5204 can refer to the optional implementation of step 204 in Figure 2, step 403 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0335] Step 5205: After the time indicated by the migration timeout field, if the second radio frame is not received by AP MLD101, any target connection indicated by the second connection bitmap in the first radio frame can be used as the second connection, and the first R-TWT scheduling can be migrated to the second connection. The time indicated by the first R-TWT SP of the R-TWT scheduling under the first connection is offset by the timer deviation between the first connection and the second connection to obtain the second R-TWT SP of the second AP under the second connection of the first R-TWT scheduling. Within the second R-TWT SP, the second STA associated with the second AP transmits the low-latency service corresponding to the first R-TWT scheduling.

[0336] The optional implementation of step 5205 can be found in the optional implementation of step 205 of Figure 2, the optional implementation of step 3103 of Figure 3A, step 3203 of Figure 3B, and step 3303b of Figure 3C, as well as step 403 of Figures 2A, 3A, 3B, 3C, and 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0337] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0338] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0339] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0340] FIG6 is a schematic diagram of the structure of a multi-connection access point device according to an embodiment of the present disclosure. As shown in FIG6 , the multi-connection access point device 600 may include at least one of a processing module 601 and a transceiver module 602 .

[0341] In some embodiments, the above-mentioned processing module 601 is used to determine a first wireless frame; wherein the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting low-latency services within the second R-TWT SP under the second connection under the first R-TWT scheduling.

[0342] Optionally, the transceiver module 602 is configured to execute at least one of the communication steps of sending and / or receiving (eg, step 202 and step 204, but not limited thereto) executed by the multi-connection access point device 101 in any of the above methods, which will not be described in detail herein.

[0343] Optionally, the processing module is configured to execute at least one of the other steps (eg, step 201 and step 205 , but not limited thereto) executed by the multi-connection access point device 101 in any of the above methods, which will not be described in detail herein.

[0344] FIG7 is a schematic diagram of the structure of a multi-connection site device according to an embodiment of the present disclosure. As shown in FIG7 , the multi-connection site device 700 may include at least one of a processing module 701 and a transceiver module 702 .

[0345] In some embodiments, the processing module 701 is configured to determine a second radio frame, wherein the second radio frame includes second identification information, and the second identification information identifies confirmation information for the first radio frame.

[0346] Optionally, the transceiver module 702 is used to execute at least one of the communication steps such as sending and / or receiving (eg, step 202, step 204, but not limited thereto) executed by the multi-connection site device 102 in any of the above methods, which will not be described in detail here.

[0347] Optionally, the processing module is configured to execute at least one of the other steps (such as step 203 , but not limited thereto) executed by the multi-connection site device 102 in any of the above methods, which will not be described in detail here.

[0348] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0349] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0350] Figure 8 is a schematic diagram of the structure of a multi-connection access point device 800 proposed in an embodiment of the present disclosure. Multi-connection access point device 800 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user device, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Multi-connection access point device 800 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0351] As shown in Figure 8, a multi-connection access point device 800 includes one or more processors 801. Processor 801 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Multi-connection access point device 800 is used to perform any of the above methods.

[0352] In some embodiments, the multi-connection access point device 800 further includes one or more memories 802 for storing instructions. Optionally, all or part of the memory 802 may be located outside the multi-connection access point device 800.

[0353] In some embodiments, the multi-connection access point device 800 further includes one or more transceivers 803. When the multi-connection access point device 800 includes one or more transceivers 803, the transceiver 803 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 202 and step 204, but not limited thereto), and the processor 801 performs at least one of the other steps (for example, step 201 and step 205, but not limited thereto).

[0354] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0355] In some embodiments, the multi-connection access point device 800 may include one or more interface circuits 804. Optionally, the interface circuit 804 is connected to the memory 802. The interface circuit 804 may be configured to receive signals from the memory 802 or other devices, and may be configured to send signals to the memory 802 or other devices. For example, the interface circuit 804 may read instructions stored in the memory 802 and send the instructions to the processor 801.

[0356] The multi-connection access point device 800 described in the above embodiment may be a network device or a terminal, but the scope of the multi-connection access point device 800 described in the present disclosure is not limited thereto, and the structure of the multi-connection access point device 800 may not be limited by FIG8 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0357] Figure 9 is a schematic diagram of the structure of a multi-connection site device 900 proposed in an embodiment of the present disclosure. Multi-connection site device 900 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user device, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Multi-connection site device 900 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0358] As shown in Figure 9, a multi-connection site device 900 includes one or more processors 901. Processor 901 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Multi-connection site device 900 is used to perform any of the above methods.

[0359] In some embodiments, the multi-connection site device 900 further includes one or more memories 902 for storing instructions. Optionally, all or part of the memories 902 may also be located outside the multi-connection site device 900.

[0360] In some embodiments, the multi-connection site device 900 further includes one or more transceivers 903. When the multi-connection site device 900 includes one or more transceivers 903, the transceiver 903 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 202 and step 204, but not limited thereto), and the processor 901 performs at least one of the other steps (for example, step 203, but not limited thereto).

[0361] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0362] In some embodiments, the multi-connection-site device 900 may include one or more interface circuits 904. Optionally, the interface circuit 904 is connected to the memory 902 and may be configured to receive signals from the memory 902 or other devices, or to send signals to the memory 902 or other devices. For example, the interface circuit 904 may read instructions stored in the memory 902 and send the instructions to the processor 901.

[0363] The multi-connection site device 900 described in the above embodiment may be a network device or a terminal, but the scope of the multi-connection site device 900 described in the present disclosure is not limited thereto, and the structure of the multi-connection site device 900 may not be limited by FIG. 9 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0364] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the multi-connection access point device 800, the multi-connection access point device 800 performs any of the above methods. When the instructions are executed on the multi-connection site device 900, the multi-connection site device 900 performs any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0365] The present disclosure also provides a program product. When executed by a multi-connection access point device 800, the program product causes the multi-connection access point device 800 to perform any of the above methods. When executed by a multi-connection station device 900, the program product causes the multi-connection station device 900 to perform any of the above methods. Optionally, the program product is a computer program product.

[0366] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A low-latency service transmission method, characterized in that: The method comprises: determining a first radio frame; The first radio frame includes first identification information, and the first identification information identifies: migrating the first restricted target wake-up time R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second restricted target wake-up time service time R-TWT SP of the first R-TWT scheduling under the second connection; The first radio frame is sent.

2. The method according to claim 1, characterized in that The first wireless frame includes an R-TWT migration element, and the R-TWT migration element carries a parameter information field of the first R-TWT scheduling.

3. The method according to claim 2, characterized in that The parameter information field of the first R-TWT scheduling includes at least one of the following: a timer deviation subfield, the timer deviation subfield indicating a timer deviation between the first connection and the second connection; A second connection bitmap subfield, wherein the second connection bitmap subfield indicates that the first R-TWT schedules a migratable target connection, and the target connection includes the second connection.

4. The method according to claim 3, characterized in that The method further comprises: The R-TWT migration element also carries the first R-TWT SP of the R-TWT scheduled under the first connection; The time indicated by the first R-TWT SP is offset by the timer deviation to obtain a second R-TWT SP.

5. The method according to claim 3, characterized in that: When there are multiple first R-TWT schedules, the parameter information field of the first R-TWT schedule includes at least one subfield; each of the subfields includes parameter information of the first R-TWT schedule.

6. The method according to claim 3, characterized in that: The R-TWT migration element also carries a migration timeout duration field; the migration timeout duration field indicates the maximum duration required to schedule the migration of the R-TWT of the first connection to the second connection.

7. The method according to claim 6, characterized in that The R-TWT migration element also carries a control field; The control field includes at least one of a migration timeout existence flag, a second connection bitmap size flag, and a timer deviation existence flag.

8. The method according to claim 7, characterized in that When the migration timeout existence flag is set to the first parameter value, it indicates that the R-TWT migration element carries the migration timeout duration field.

9. The method according to claim 7, characterized in that: The second connection bitmap size identification bit is set to different parameter values, indicating that the sizes of the second connection bitmap are different.

10. The method according to claim 7, characterized in that When the timer deviation existence flag is set to a second parameter value, it indicates that the parameter information field of the first R-TWT scheduling includes the timer deviation subfield.

11. The method according to claim 10, characterized in that The first connection and the second connection are mutually non-simultaneous NSTR connection pairs, and the parameter information field of the first R-TWT scheduling does not include the timer deviation subfield.

12. The method according to claim 1, characterized in that The migrating the first R-TWT scheduling of the first connection to the second connection includes: Before the first connection fails or is interrupted, the first R-TWT is scheduled to be migrated to the second connection.

13. The method according to claim 6, characterized in that The method further comprises: receiving a second wireless frame; the second wireless frame includes second identification information, the second identification information identifying the first wireless Confirmation information of line frame; Perform a migration operation to migrate the first R-TWT scheduling of the first connection to the second connection.

14. The method according to claim 13, characterized in that The second radio frame includes: a parameter information field of the first R-TWT scheduling and the second connection bitmap subfield.

15. The method according to claim 13 or 14, characterized in that The receiving the second radio frame comprises: The second radio frame is received under the first connection before the time indicated by the migration timeout duration field.

16. The method according to claim 13 or 14, characterized in that The method further comprises: After the time indicated by the migration super long duration field and without receiving the second wireless frame, a migration operation is performed to schedule the first R-TWT of the first connection to migrate to the second connection.

17. A low-latency service transmission method, characterized in that: The method comprises: receiving a first wireless frame; Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

18. The method according to claim 17, characterized in that The first wireless frame includes an R-TWT migration element, and the R-TWT migration element carries a parameter information field of the first R-TWT scheduling.

19. The method according to claim 18, characterized in that The parameter information field of the first R-TWT scheduling includes at least one of the following: a timer deviation subfield, the timer deviation subfield indicating a timer deviation between the first connection and the second connection; A second connection bitmap subfield, wherein the second connection bitmap subfield indicates that the first R-TWT schedules a migratable target connection, and the target connection includes the second connection.

20. The method according to claim 19, characterized in that The method further comprises: The R-TWT migration element also carries the first R-TWT SP of the R-TWT scheduled under the first connection; The time indicated by the first R-TWT SP is offset by the timer deviation to obtain the second R-TWT SP.

21. The method according to claim 19, characterized in that When there are multiple first R-TWT schedules, the parameter information field of the first R-TWT schedule includes at least one subfield; each of the subfields includes parameter information of the first R-TWT schedule.

22. The method according to claim 19, characterized in that The R-TWT migration element also carries a migration timeout duration field; the migration timeout duration field indicates the maximum duration required to schedule the migration of the R-TWT of the first connection to the second connection.

23. The method according to claim 22, characterized in that The R-TWT migration element also carries a control field; The control field includes at least one of a migration timeout existence flag, a second connection bitmap size flag, and a timer deviation existence flag.

24. The method according to claim 22, characterized in that When the migration timeout existence flag is set to the first parameter value, it indicates that the R-TWT migration element carries the migration timeout duration field.

25. The method according to claim 22, characterized in that The second connection bitmap size identification bit is set to different parameter values, indicating that the sizes of the second connection bitmap are different.

26. The method according to claim 22, characterized in that When the timer deviation existence flag is set to a second parameter value, it indicates that the parameter information field of the first R-TWT scheduling includes the timer deviation subfield.

27. The method according to claim 26, characterized in that The first connection and the second connection are mutually non-simultaneous NSTR connection pairs, and the parameter information field of the first R-TWT scheduling does not include the timer deviation subfield.

28. The method according to claim 17, characterized in that The migrating the first R-TWT scheduling of the first connection to the second connection includes: Before the first connection fails or is interrupted, the first R-TWT is scheduled to be migrated to the second connection.

29. The method according to claim 22, characterized in that The method further comprises: Determine a second radio frame; the second radio frame includes second identification information, and the second identification information identifies confirmation information for the first radio frame; Send the second wireless frame; instruct to perform a migration operation of migrating the first R-TWT scheduling of the first connection to the second connection.

30. The method according to claim 29, characterized in that The second radio frame includes: a parameter information field of the first R-TWT scheduling and the second connection bitmap subfield.

31. The method according to claim 29 or 30, characterized in that The sending the second wireless frame includes: Before the time indicated by the migration timeout duration, the second radio frame is sent under the first connection.

32. A multi-connection access point device, characterized in that: The multi-connection access point device comprises: A processing module, configured to determine a first radio frame; The first radio frame includes first identification information, and the first identification information identifies: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling in the second R-TWT SP under the second connection under the first R-TWT scheduling; A transceiver module is used to send the first wireless frame.

33. A multi-connection site device, characterized in that: The multi-connection site device comprises: A transceiver module, configured to receive a first wireless frame; Among them, the first wireless frame includes first identification information, and the first identification information indicates: migrating the first R-TWT scheduling of the first connection to the second connection, and transmitting the low-latency service corresponding to the first R-TWT scheduling within the second R-TWT SP under the second connection.

34. A multi-connection access point device, characterized in that: include: one or more processors; The multi-connection access point device is used to execute the low-latency service transmission method according to any one of claims 1 to 16.

35. A multi-connection site device, characterized in that: include: one or more processors; The multi-connection site device is used to execute the low-latency service transmission method described in any one of claims 17 to 31.

36. A communication system, characterized in that: It comprises a multi-connection access point device and a multi-connection site device, wherein the multi-connection access point device is configured to implement the low-latency service transmission method described in any one of claims 1 to 16, and the multi-connection site device is configured to implement the low-latency service transmission method described in any one of claims 17 to 31.

37. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device executes a low-latency service transmission method as described in any one of claims 1 to 16 or any one of claims 17 to 31.

Images