Communication method and device

Abstract

The invention provides a communication method and device, relates to the technical field of communication, and can determine whether a statistical time delay currently reached by a certain TID or a certain service flow of a certain station in a BSS meets a QoS requirement or not, and timely adjust a scheduling strategy of the BBS, thereby improving the QoS performance of the station and improving the QoS performance guarantee of communication. The method comprises the following steps: a sending end device obtains a first MPDU; and transmitting the first MPDU. Wherein the first MPDU comprises a CCMP header field, the CCMP header field comprises a first field, and the first field is used for indicating the first time of the second MPDU or the second time of the second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the MAC layer of the transmitting end equipment, and the second time of the second MPDU is the time when the transmitting end equipment expects that the second MPDU arrives at the receiving end equipment; the second MPDU is the first MPDU or the next MPDU of the first MPDU.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods and apparatus. Background Technology

[0002] In a communication system, a site device can report information about one or more low-latency service flows to an access point device. Accordingly, the access point device can schedule the transmission associated with the one or more low-latency service flows based on the reported information to meet the low-latency requirements.

[0003] Among these issues, determining whether the statistical latency of different service flows in the basic service set (BSS) meets the quality of service (QoS) requirements, and adjusting the scheduling strategy of the BBS (or access point equipment) in a timely manner to improve communication performance, has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a communication method and apparatus that can determine whether the statistical latency of a certain TID or a certain service flow at a certain site in a BSS meets the QoS requirements, and adjust the BBS scheduling strategy in a timely manner to improve the QoS performance of the site and enhance the QoS performance guarantee of communication.

[0005] Firstly, a communication method is provided, which can be executed by a transmitting device. Unless otherwise specified, "transmitting device" in this application can refer to the transmitting device itself, a component within the transmitting device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the transmitting device. The method includes: the transmitting device acquiring a first Media Access Control (MAC) layer Protocol Data Unit (MPDU); and transmitting the first MPDU. The first MPDU includes a Cipher-Block Chaining Message Authentication Code Protocol (CCMP) header field. The CCMP header field includes a first field indicating a first time or a second time of a second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the MAC layer of the transmitting device; the second time of the second MPDU is the time when the transmitting device expects the second MPDU to arrive at the receiving device; the second MPDU is the first MPDU or the next MPDU after the first MPDU.

[0006] Based on this scheme, on the one hand, the sending device can carry a first field in the CCMP header field of the first MPDU. The first field can indicate the time when the first MPDU or the next MPDU of the first MPDU arrives at the MAC layer of the sending device, or the expected time when it arrives at the receiving device, so that the receiving device can determine the latency of the first MPDU. On the other hand, it can enable the receiving device to determine whether the actual time when the first MPDU or the next MPDU of the first MPDU arrives at the receiving device exceeds the time expected by the sending device. This allows the receiving device to monitor whether the corresponding service flow meets the latency requirements of the sending device, and thus enable the receiving device (such as access point device) to adjust the scheduling in a timely manner to reduce latency and improve connectivity performance.

[0007] The sending device can be an access point device or a site device, and the receiving device can be a site device or an access point device.

[0008] In this system, different service flows in the BSS can transmit data through one or more first MPDUs. The receiving device can monitor in real time whether the actual time of each MPDU in one or more first MPDUs corresponding to different service flows in the BSS exceeds the time expected by the sending device. In this way, the scheduling can be adjusted in a timely manner to reduce latency and better meet the latency requirements of different service flows in the BSS.

[0009] The time expected by the aforementioned sending device can also be understood as the time corresponding to the service QoS requirements.

[0010] The time mentioned above can be expressed as a moment or a timestamp.

[0011] One possible implementation is that the position of the first field in the CCMP header field is predefined; or, the position of the first field in the CCMP header field is determined according to first indication information; wherein the first indication information is used to indicate one or more of the following: the start position of the first field in the CCMP header field, the length of the first field, or the end position of the first field in the CCMP header field.

[0012] Based on this possible implementation, on the one hand, compared to the predefined position of the first field in the CCMP header, the first indication information can dynamically indicate the position of the first field in the CCMP header according to the actual communication scenario or communication situation, which can improve the diversity and flexibility of determining the position of the first field in the CCMP header. On the other hand, compared to indicating the position of the first field in the CCMP header through the first indication information, the predefined position of the first field in the CCMP header can reduce the signaling overhead of the air interface and simplify the implementation.

[0013] One possible implementation is that the first indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the enabling of the function of the CCMP header field to carry the first field.

[0014] Based on this possible implementation, several feasible solutions are provided for the transmission of the first instruction information, which can improve the flexibility and diversity of the transmission of the first instruction information.

[0015] One possible implementation is that the first field is determined based on a subset of bits from the timing synchronization function (TSF) in the beacon frame.

[0016] Based on this possible implementation, a feasible solution is provided for determining the time indicated by the first field.

[0017] One possible implementation is that the partial bits of the TSF corresponding to the first field are predefined; or, the partial bits of the TSF corresponding to the first field are determined according to the second indication information; wherein the second indication information is used to indicate one or more of the following: the position of the start bit of the partial bits of the TSF in the TSF, the position of the end bit of the partial bits of the TSF in the TSF, or the length of the partial bits of the TSF.

[0018] Based on this possible implementation, on the one hand, compared to the predefined partial bits of the TSF corresponding to the first field, the second indication information can dynamically indicate the partial bits of the TSF corresponding to the first field according to the actual communication scenario or communication situation. This can improve the diversity and flexibility of determining the partial bits of the TSF corresponding to the first field. Furthermore, it can flexibly adjust the partial bits of the TSF corresponding to the first field according to the different latency requirements of different service flows, such as latency accuracy, thereby meeting the latency performance monitoring needs of service flows with different latency requirements. On the other hand, compared to indicating the partial bits of the TSF corresponding to the first field through the second indication information, the predefined partial bits of the TSF corresponding to the first field can reduce air interface signaling overhead and simplify implementation.

[0019] One possible implementation is that the second indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the activation of the function of the CCMP header field to carry the first field.

[0020] Based on this possible implementation, several feasible solutions are provided for the transmission of the second instruction information, which can improve the flexibility and diversity of the transmission of the second instruction information.

[0021] One possible implementation is that the first field is protected by the message integrity code (MIC) in the first MPDU.

[0022] Based on this possible implementation, the first field can be protected by the MIC, which can improve the reliability of the first field transmission.

[0023] One possible implementation is that the first MPDU includes a second field; wherein the second field is used to indicate the presence of the first field in the CCMP header fields.

[0024] Based on this possible implementation, the receiving device can determine that the first field exists in the CCMP header fields, and then parse the first field. Similarly, when the first MPDU does not include the second field, the receiving device can determine that the first field does not exist in the CCMP header fields, and then does not need to parse the first field. This can improve the interaction efficiency between the receiving device and the sending device, and at the same time improve the working efficiency of the receiving device.

[0025] In one possible implementation, the first MPDU further includes a third field; wherein the third field is used to indicate that the first field indicates a first time of the second MPDU, or the third field is used to indicate that the first field indicates a second time of the second MPDU.

[0026] Based on this possible implementation, the receiving device can determine the time type indicated by the first field (such as the first time or the second time) according to the third field, providing a feasible solution for the receiving device to determine the time type indicated by the first field.

[0027] One possible implementation is that the position of the third field in the first MPDU is predefined; or, the position of the third field in the first MPDU is determined according to third indication information; wherein the third indication information is used to indicate the position of the third field in the first MPDU.

[0028] Based on this possible implementation, on the one hand, compared to the predefined position of the third field in the first MPDU, the third indication information can dynamically indicate the position of the third field in the first MPDU according to the actual communication scenario or communication situation, which can improve the diversity and flexibility of determining the position of the third field in the CCMP header fields. On the other hand, compared to indicating the position of the third field in the first MPDU through the third indication information, the predefined position of the third field in the first MPDU can reduce the signaling overhead of the air interface and simplify the implementation.

[0029] One possible implementation is that the third indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the activation of the function of the CCMP header field to carry the first field.

[0030] Based on this possible implementation, several feasible solutions are provided for the transmission of third instruction information, which can improve the flexibility and diversity of third instruction information transmission.

[0031] One possible implementation is that the third field is located in the MAC header field of the first MPDU; or, the third field is located in the CCMP header field of the first MPDU.

[0032] Based on this possible implementation, the flexibility and diversity of the position of the third field in the first MPDU can be improved.

[0033] One possible implementation is that the third field is protected by the MIC in the first MPDU.

[0034] Based on this possible implementation, the third field can be protected by the MIC, which can improve the reliability of the third field transmission.

[0035] One possible implementation is that the sending device sends a fourth indication information; wherein the fourth indication information is used to indicate that the first field indicates the first time of the second MPDU, or the fourth indication information is used to indicate that the first field indicates the second time of the second MPDU.

[0036] Based on this possible implementation, the receiving device can determine the time type indicated by the first field according to the fourth indication information. Compared with the third field, determining the time type indicated by the first field through the fourth indication information can reduce changes to the MPDU format and simplify the implementation.

[0037] One possible implementation is that the fourth indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the activation of the function of the CCMP header field to carry the first field.

[0038] Based on this possible implementation, several feasible solutions are provided for the transmission of the fourth instruction information, which can improve the flexibility and diversity of the transmission of the fourth instruction information.

[0039] One possible implementation is that the first MPDU includes a fourth field; wherein the fourth field is used to indicate the stream classification service (SCS) identifier (SCSID), and if the first MPDU includes the fourth field, the first field is used to indicate the first time of the second MPDU.

[0040] Based on this possible implementation, a feasible solution can be provided for determining the time type indicated by the first field by carrying a fourth field in the first MPDU to indicate the service flow to which the second MPDU belongs, and by implicitly indicating that the first field is used to indicate the first time of the second MPDU. Furthermore, by carrying a fourth field in the first MPDU, the identifier of the SCS or the delay bound corresponding to the second MPDU can also be implicitly indicated, thereby enabling the receiving device to determine the second time of the second MPDU based on the delay bound corresponding to the identifier of the SCS and the first time of the second MPDU.

[0041] One possible implementation is that the position of the fourth field in the first MPDU is predefined; or, the position of the fourth field in the first MPDU is determined according to fifth indication information; wherein the fifth indication information is used to indicate one or more of the following: the start position of the fourth field in the first MPDU, the length of the fourth field, or the end position of the fourth field in the first MPDU.

[0042] Based on this possible implementation, on the one hand, compared to the predefined positions of the four fields in the first MPDU, the fifth indication information can dynamically indicate the positions of the four fields in the first MPDU according to the actual communication scenario or communication situation, which can improve the diversity and flexibility of determining the positions of the four fields in the first MPDU. On the other hand, compared to indicating the positions of the four fields in the first MPDU through the fifth indication information, the predefined positions of the fourth field in the first MPDU can reduce the signaling overhead of the air interface and simplify the implementation.

[0043] One possible implementation is that the fifth indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the activation of the function of the CCMP header field to carry the first field.

[0044] Based on this possible implementation, several feasible solutions are provided for the transmission of the fifth instruction information, which can enhance the flexibility and diversity of the transmission of the fifth instruction information.

[0045] One possible implementation is that the fourth field is located in the MAC header field of the first MPDU; or, the fourth field is located in the CCMP header field of the first MPDU.

[0046] Based on this possible implementation, the flexibility and diversity of the position of the fourth field in the first MPDU can be improved.

[0047] One possible implementation is that the fourth field is protected by the MIC in the first MPDU.

[0048] Based on this possible implementation, the fourth field can be protected by the MIC, which can improve the reliability of the fourth field transmission.

[0049] One possible implementation is that the sending device sends capability information; wherein the capability information is used to indicate support for the first field carried in the CCMP header field.

[0050] One possible implementation is that the sending or receiving device of the first MPDU sends a first request frame and receives a first response frame. The first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field; the first response frame is used to indicate agreement to enable the function of carrying the first field in the CCMP header field.

[0051] Based on the two possible implementations mentioned above, the sending device (or receiving device) of the first MPDU can determine whether the receiving device (or sending device) of the first MPDU supports or agrees to include the first field in the CCMP header field. This can minimize the possibility of the receiving device being unable to recognize the first field even though the CCMP header field includes it. This can improve the interaction efficiency between the sending and receiving devices and reduce resource waste.

[0052] Optionally, the first request frame can also be used to request negotiation of relevant parameters with the receiving device (or the sending device).

[0053] Optionally, the first response frame can also be used to indicate relevant parameters.

[0054] Optionally, the first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field during uplink transmission; or, the first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field during downlink transmission; the first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field during both uplink and downlink transmission.

[0055] Alternatively, the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during uplink transmission and to negotiate relevant parameters; or, the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during downlink transmission and to negotiate relevant parameters; the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during both uplink and downlink transmission and to negotiate relevant parameters.

[0056] One possible implementation is that the sending device and the receiving device communicate through multiple links, the time corresponding to the first field is referenced to the time corresponding to the first link, the first link is included in the multiple links, and the identifier of the first link is the maximum or minimum value among the identifiers of the multiple links; or, a sixth indication information is sent; wherein the sixth indication information is used to indicate the identifier of the first link; or, the TSF time corresponding to the multiple links is required to be the same.

[0057] Based on this possible implementation, a reference time for the time corresponding to the first field can be determined, providing a feasible solution for the receiving device to statistically analyze latency performance.

[0058] Secondly, a communication method is provided, which can be executed by a transmitting device. Unless otherwise specified, "transmitting device" in this application can refer to the transmitting device itself, a component within the transmitting device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the transmitting device. The method includes: a receiving device acquiring a first MPDU; and monitoring the quality of service associated with the transmitting device based on a first field. The first MPDU includes a CCMP header field, which includes the first field, used to indicate a first time or a second time of a second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the media access control (MAC) layer of the transmitting device, and the second time of the second MPDU is the time when the transmitting device expects the second MPDU to arrive at the receiving device; the second MPDU is the first MPDU or the next MPDU after the first MPDU.

[0059] Based on this scheme, on the one hand, the first field can indicate the time when the first MPDU or the next MPDU of the first MPDU arrives at the MAC layer of the sending device, or the expected time when it arrives at the receiving device, so that the receiving device can determine the latency of the first MPDU; on the other hand, the receiving device can determine whether the actual time when the first MPDU or the next MPDU of the first MPDU arrives at the receiving device exceeds the time expected by the sending device, so that the receiving device can monitor whether the corresponding service flow meets the latency requirements of the sending device, and thus the receiving device (such as access point device) can adjust the scheduling in time to reduce latency and improve connectivity performance.

[0060] The sending device can be an access point device or a site device, and the receiving device can be a site device or an access point device.

[0061] In this system, different service flows in the BSS can transmit data through one or more first MPDUs. The receiving device can monitor in real time whether the actual time of each MPDU in one or more first MPDUs corresponding to different service flows in the BSS exceeds the time expected by the sending device. In this way, the scheduling can be adjusted in a timely manner to reduce latency and better meet the latency requirements of different service flows in the BSS.

[0062] The time expected by the aforementioned sending device can also be understood as the time corresponding to the service QoS requirements.

[0063] The time mentioned above can be represented as a moment or a timestamp.

[0064] One possible implementation is that the position of the first field in the CCMP header field is predefined; or, the position of the first field in the CCMP header field is determined according to first indication information; wherein the first indication information is used to indicate one or more of the following: the start position of the first field in the CCMP header field, the length of the first field, or the end position of the first field in the CCMP header field.

[0065] Based on this possible implementation, on the one hand, compared to the predefined position of the first field in the CCMP header, the first indication information can dynamically indicate the position of the first field in the CCMP header according to the actual communication scenario or communication situation, which can improve the diversity and flexibility of determining the position of the first field in the CCMP header. On the other hand, compared to indicating the position of the first field in the CCMP header through the first indication information, the predefined position of the first field in the CCMP header can reduce the signaling overhead of the air interface and simplify the implementation.

[0066] One possible implementation is that the first indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame is used to request the activation of the function of the CCMP header field to carry the first field.

[0067] Based on this possible implementation, several feasible solutions are provided for the transmission of the first instruction information, which can improve the flexibility and diversity of the transmission of the first instruction information.

[0068] One possible implementation is that the first field is determined based on a portion of the bits in the TSF of the beacon frame.

[0069] Based on this possible implementation, a feasible solution is provided for determining the time indicated by the first field.

[0070] One possible implementation is that the partial bits of the TSF corresponding to the first field are predefined; or, the partial bits of the TSF corresponding to the first field are determined according to the second indication information; wherein the second indication information is used to indicate one or more of the following: the position of the start bit of the partial bits of the TSF in the TSF, the position of the end bit of the partial bits of the TSF in the TSF, or the length of the partial bits of the TSF.

[0071] Based on this possible implementation, on the one hand, compared to the predefined partial bits of the TSF corresponding to the first field, the second indication information can dynamically indicate the partial bits of the TSF corresponding to the first field according to the actual communication scenario or communication situation. This can improve the diversity and flexibility of determining the partial bits of the TSF corresponding to the first field. Furthermore, it can flexibly adjust the partial bits of the TSF corresponding to the first field according to the different latency requirements of different service flows, such as latency accuracy, thereby meeting the latency performance monitoring needs of service flows with different latency requirements. On the other hand, compared to indicating the partial bits of the TSF corresponding to the first field through the second indication information, the predefined partial bits of the TSF corresponding to the first field can reduce air interface signaling overhead and simplify implementation.

[0072] One possible implementation is that the second indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame is used to request the activation of the function of the CCMP header field to carry the first field.

[0073] Based on this possible implementation, several feasible solutions are provided for the transmission of the second instruction information, which can improve the flexibility and diversity of the transmission of the second instruction information.

[0074] One possible implementation is that the first field is protected by the MIC in the first MPDU.

[0075] Based on this possible implementation, the first field can be protected by the MIC, which can improve the reliability of the first field transmission.

[0076] One possible implementation is that the first MPDU includes a second field; wherein the second field is used to indicate the presence of the first field in the CCMP header fields.

[0077] Based on this possible implementation, the receiving device can determine that the first field exists in the CCMP header fields, and then parse the first field. Similarly, when the first MPDU does not include the second field, the receiving device can determine that the first field does not exist in the CCMP header fields, and then does not need to parse the first field. This can improve the interaction efficiency between the receiving device and the sending device, and at the same time improve the working efficiency of the receiving device.

[0078] In one possible implementation, the first MPDU further includes a third field; wherein the third field is used to indicate that the first field indicates a first time of the second MPDU, or the third field is used to indicate that the first field indicates a second time of the second MPDU.

[0079] Based on this possible implementation, the receiving device can determine the time type indicated by the first field (such as the first time or the second time) according to the third field, providing a feasible solution for the receiving device to determine the time type indicated by the first field.

[0080] One possible implementation is that the position of the third field in the first MPDU is predefined; or, the position of the third field in the first MPDU is determined according to third indication information; wherein the third indication information is used to indicate the position of the third field in the first MPDU.

[0081] Based on this possible implementation, on the one hand, compared to the predefined position of the third field in the first MPDU, the third indication information can dynamically indicate the position of the third field in the first MPDU according to the actual communication scenario or communication situation, which can improve the diversity and flexibility of determining the position of the third field in the CCMP header fields. On the other hand, compared to indicating the position of the third field in the first MPDU through the third indication information, the predefined position of the third field in the first MPDU can reduce the signaling overhead of the air interface and simplify the implementation.

[0082] One possible implementation is that the third indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the activation of the function of the CCMP header field to carry the first field.

[0083] Based on this possible implementation, several feasible solutions are provided for the transmission of third instruction information, which can improve the flexibility and diversity of third instruction information transmission.

[0084] One possible implementation is that the third field is located in the MAC header field of the first MPDU; or, the third field is located in the CCMP header field of the first MPDU.

[0085] Based on this possible implementation, the flexibility and diversity of the position of the third field in the first MPDU can be improved.

[0086] One possible implementation is that the third field is protected by the MIC in the first MPDU.

[0087] Based on this possible implementation, the third field can be protected by the MIC, which can improve the reliability of the third field transmission.

[0088] One possible implementation is that the receiving device receives fourth indication information; based on the fourth indication information, the receiving device determines that the first field indicates a first time of the second MPDU, or determines that the first field indicates a second time of the second MPDU. Wherein, the fourth indication information is used to indicate that the first field indicates a first time of the second MPDU, or the fourth indication information is used to indicate that the first field indicates a second time of the second MPDU.

[0089] Based on this possible implementation, the receiving device can determine the time type indicated by the first field of the fourth indication information, compared with the third field, by using the fourth indication information. This can reduce changes to the MPDU format and simplify the implementation.

[0090] One possible implementation is that the fourth indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the activation of the function of the CCMP header field to carry the first field.

[0091] Based on this possible implementation, several feasible solutions are provided for the transmission of the fourth instruction information, which can improve the flexibility and diversity of the transmission of the fourth instruction information.

[0092] One possible implementation is that the first MPDU includes a fourth field; based on the fourth field, it is determined that the first field indicates the first time of the second MPDU. The fourth field is used to indicate the identifier of the SCS.

[0093] Based on this possible implementation, a feasible solution can be provided for determining the time type indicated by the first field by carrying a fourth field in the first MPDU to indicate the service flow to which the second MPDU belongs, or by implicitly indicating that the first field is used to indicate the first time of the second MPDU.

[0094] One possible implementation is that the receiving device determines the second time of the second MPDU based on the first time of the second MPDU and the delay limit corresponding to the identifier of the SCS.

[0095] Based on this possible implementation, by carrying a fourth field in the first MPDU, the identifier of the SCS or the delay limit corresponding to the second MPDU can be implicitly indicated. The receiving device can determine the second time of the second MPDU based on the delay limit corresponding to the identifier of the SCS and the first time of the second MPDU.

[0096] One possible implementation is that the position of the fourth field in the first MPDU is predefined; or, the position of the fourth field in the first MPDU is determined according to fifth indication information; wherein the fifth indication information is used to indicate one or more of the following: the start position of the fourth field in the first MPDU, the length of the fourth field, or the end position of the fourth field in the first MPDU.

[0097] Based on this possible implementation, on the one hand, compared to the predefined positions of the four fields in the first MPDU, the fifth indication information can dynamically indicate the positions of the four fields in the first MPDU according to the actual communication scenario or communication situation, which can improve the diversity and flexibility of determining the positions of the four fields in the first MPDU. On the other hand, compared to indicating the positions of the four fields in the first MPDU through the fifth indication information, the predefined positions of the fourth field in the first MPDU can reduce the signaling overhead of the air interface and simplify the implementation.

[0098] One possible implementation is that the fifth indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame can be used to request the activation of the function of the CCMP header field to carry the first field.

[0099] Based on this possible implementation, several feasible solutions are provided for the transmission of the fifth instruction information, which can enhance the flexibility and diversity of the transmission of the fifth instruction information.

[0100] One possible implementation is that the fourth field is located in the MAC header field of the first MPDU; or, the fourth field is located in the CCMP header field of the first MPDU.

[0101] Based on this possible implementation, the flexibility and diversity of the position of the fourth field in the first MPDU can be improved.

[0102] One possible implementation is that the fourth field is protected by the MIC in the first MPDU.

[0103] Based on this possible implementation, the fourth field can be protected by the MIC, which can improve the reliability of the fourth field transmission.

[0104] One possible implementation is that the receiving device receives capability information; wherein the capability information is used to indicate support for the first field carried in the CCMP header field.

[0105] One possible implementation is that the sending or receiving device receiving the first MPDU receives the first request frame and sends a first response frame. The first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field; the first response frame is used to indicate agreement to enable the function of carrying the first field in the CCMP header field.

[0106] Based on the two possible implementations mentioned above, the sending device (or receiving device) of the first MPDU can determine whether the receiving device (or sending device) of the first MPDU supports or agrees to include the first field in the CCMP header field. This can minimize the possibility of the receiving device being unable to recognize the first field even though the CCMP header field includes it. This can improve the interaction efficiency between the sending and receiving devices and reduce resource waste.

[0107] Optionally, the first request frame can also be used to request negotiation of relevant parameters with the receiving device.

[0108] Optionally, the first response frame can also be used to indicate relevant parameters.

[0109] Optionally, the first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field during uplink transmission; or, the first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field during downlink transmission; the first request frame can be used to request the enabling of the function of carrying the first field in the CCMP header field during both uplink and downlink transmission.

[0110] Alternatively, the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during uplink transmission and to negotiate relevant parameters; or, the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during downlink transmission and to negotiate relevant parameters; the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during both uplink and downlink transmission and to negotiate relevant parameters.

[0111] One possible implementation is that the sending device and the receiving device communicate through multiple links, the time corresponding to the first field is referenced to the time corresponding to the first link, the first link is included in the multiple links, and the identifier of the first link is the maximum or minimum value among the identifiers of the multiple links; or, a sixth indication information is sent; wherein the sixth indication information is used to indicate the identifier of the first link; or, the TSF time corresponding to the multiple links is required to be the same.

[0112] Based on this possible implementation, a reference time for the time corresponding to the first field can be determined, providing a feasible solution for the receiving device to statistically analyze latency performance.

[0113] Thirdly, a communication device is provided for implementing the method of the first aspect. This communication device may be the transmitting device described in the first aspect, or a device or component included in the transmitting device, such as a chip.

[0114] The communication device includes modules, units, or means that implement the methods described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0115] In some possible implementations, the communication device may include a processing module and a transceiver module. The transceiver module may include a sending module and a receiving module, respectively used to implement the sending and receiving functions of the first aspect and any possible implementation thereof. The processing module may be used to implement the processing functions of the first aspect and any possible implementation thereof. For example, the processing module is used to acquire a first MPDU; wherein the first MPDU includes a CCMP header field, the CCMP header field includes a first field, the first field being used to indicate a first time of a second MPDU or a second time of a second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the MAC layer of the sending device, and the second time of the second MPDU is the time when the sending device expects the second MPDU to arrive at the receiving device; the second MPDU is the first MPDU or the next MPDU of the first MPDU; the transceiver module is used to transmit the first MPDU.

[0116] Optionally, the transceiver module and processing module of the communication device in the third aspect may also perform the corresponding functions in the first aspect or any possible implementation of the first aspect, as detailed in the method examples, and the beneficial effects that can be achieved can also be found in the foregoing related content.

[0117] Fourthly, a communication device is provided for implementing the method of the second aspect described above. The communication device may be the receiving device described in the second aspect, or a device or component included in the receiving device, such as a chip.

[0118] The communication device includes modules, units, or means that implement the methods described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0119] In some possible implementations, the communication device may include a processing module and a transceiver module. The transceiver module may include a sending module and a receiving module, respectively used to implement the sending and receiving functions of the second aspect and any possible implementation thereof. The processing module may be used to implement the processing functions of the second aspect and any possible implementation thereof. For example, the processing module is used to acquire a first MPDU; wherein the first MPDU includes a CCMP header field, the CCMP header field includes a first field, the first field being used to indicate a first time of a second MPDU or a second time of a second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the MAC layer of the sending device, and the second time of the second MPDU is the time when the sending device expects the second MPDU to arrive at the receiving device; the second MPDU is the first MPDU or the next MPDU of the first MPDU; the processing module is also used to monitor the quality of service associated with the sending device based on the first field.

[0120] Optionally, the transceiver module and processing module of the communication device in the fourth aspect may also perform the corresponding functions in the second aspect or any possible implementation of the second aspect, as detailed in the method examples, and the beneficial effects that can be achieved can also be found in the foregoing related content.

[0121] Fifthly, a communication device is provided, comprising: at least one processor, the processor being configured to cause the communication device to perform the method described in any of the above aspects or possible implementations thereof by executing computer instructions stored in a memory or by logic circuitry. The communication device may be a transmitting end device in the first aspect or any possible implementation thereof, or a device or component included in the transmitting end device, such as a chip; or, the communication device may be a receiving end device in the second aspect or any possible implementation thereof, or a device or component included in the receiving end device, such as a chip.

[0122] In some possible implementations, the communication device also includes a memory for storing configuration files of computer instructions and / or logic circuits. Optionally, the memory is integrated with the processor, or the memory is independent of the processor.

[0123] A sixth aspect provides a communication device, comprising: a processor and a communication interface; the communication interface being used for inputting and / or outputting signals; the processor being used to execute a computer program or instructions to cause the communication device to perform the method described in any of the preceding aspects. The communication device may be a transmitting end device in the first aspect or any possible implementation of the first aspect, or a device or component included in the transmitting end device, such as a chip; or, the communication device may be a receiving end device in the second aspect or any possible implementation of the second aspect, or a device or component included in the receiving end device, such as a chip.

[0124] In some possible implementations, the communication interface is an interface circuit used to read and write computer instructions. For example, the interface circuit is used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0125] In some possible implementations, the communication interface is used to communicate with modules outside the communication device.

[0126] In some possible implementations, the communication device can be a chip or a chip system. When the device is a chip system, the chip system may include chips or contain chips and other discrete components.

[0127] A seventh aspect provides a communication device, comprising: a logic circuit and an interface circuit; the interface circuit being used for inputting information and / or outputting information; the logic circuit being used to perform the method described in any of the preceding aspects, processing the input information and / or generating output information. The communication device may be a transmitting end device in the first aspect or any possible implementation of the first aspect, or a device or component included in the transmitting end device, such as a chip; or, the communication device may be a receiving end device in the second aspect or any possible implementation of the second aspect, or a device or component included in the receiving end device, such as a chip.

[0128] Eighthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed by a processor, cause the methods described in any of the preceding aspects to be performed.

[0129] Ninth aspect, a computer program product is provided that, when executed by a processor, causes the method described in any of the preceding aspects to be performed.

[0130] It is understood that when the communication device provided by any of the third to seventh aspects is a chip, the aforementioned sending action / function can be understood as output information, and the aforementioned receiving action / function can be understood as input information.

[0131] The technical effects of any of the third to ninth aspects can be referred to the technical effects of the first aspect or any possible implementation of the first aspect, or the technical effects of the second aspect or any possible implementation of the second aspect, and will not be repeated here.

[0132] In a tenth aspect, a communication system is provided, comprising the transmitting end device described in the first aspect or any possible implementation thereof, and the receiving end device described in the second aspect or any possible implementation thereof. Attached Figure Description

[0133] Figure 1 A schematic diagram of an MPDU frame format provided in an embodiment of this application;

[0134] Figure 2 A schematic diagram of a frame control field provided in an embodiment of this application;

[0135] Figure 3 A schematic diagram of a sequence control field provided in an embodiment of this application;

[0136] Figure 4 A schematic diagram of a cache reporting control information subfield provided in an embodiment of this application;

[0137] Figure 5 A schematic diagram of a MAC header provided for an embodiment of this application;

[0138] Figure 6 A schematic diagram of an SCS request frame provided in an embodiment of this application;

[0139] Figure 7 A schematic diagram of an SCS descriptor list field provided in an embodiment of this application;

[0140] Figure 8 A schematic diagram of a sub-field of a service quality feature element provided in an embodiment of this application;

[0141] Figure 9 A schematic diagram of a control information subfield provided in an embodiment of this application;

[0142] Figure 10 A schematic diagram of an SCS response frame provided in an embodiment of this application;

[0143] Figure 11A schematic diagram of a communication system provided in an embodiment of this application;

[0144] Figure 12 A schematic diagram of another communication system provided in the embodiments of this application;

[0145] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0146] Figure 14 An interactive schematic diagram of a communication method provided in an embodiment of this application;

[0147] Figure 15 An interactive schematic diagram of another communication method provided in an embodiment of this application;

[0148] Figure 16 This is a schematic diagram of the structure of a transmitting device provided in an embodiment of this application;

[0149] Figure 17 This is a schematic diagram of the structure of a receiving device provided in an embodiment of this application;

[0150] Figure 18 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0151] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0152] MPDU frame format: (below) Figure 1 The frame format of an MPDU can include a frame control field, a duration field, an address 1 field, an address 2 field, an address 3 field, a sequence control field, a QoS control field, a high throughput (HT) control field, a frame body field, and a frame check sequence (FCS) field.

[0153] The format of the frame control field can be as follows: Figure 2As shown, B represents a byte (i.e., B0 represents byte 0), and the frame control field occupies a total of 16 bytes (i.e., B0-B15). The frame control field may include the protocol version subfield (occupying two bytes, i.e., B0-B1), the type subfield (occupying two bytes, i.e., B2-B3), the subtype subfield (occupying four bytes, i.e., B4-B7), the to distributionsystem (to DS) subfield (occupying one byte, i.e., B8), the from DS subfield (occupying one byte, i.e., B9), the more fragments subfield (occupying one byte, i.e., B10), the retry subfield (occupying one byte, i.e., B11), the power management subfield (occupying one byte, i.e., B12), the more data subfield (occupying one byte, i.e., B13), the protected frame subfield (occupying one byte, i.e., B14), and the HT control (HTC) presence subfield (occupying one byte, i.e., B15).

[0154] The duration field indicates the length of the MPDU, or the duration of the MPDU.

[0155] The Address 1 field is used to indicate the receive address (RA).

[0156] Address 2 is used to indicate the transmitter address (TA).

[0157] Address 3 is used to indicate the address of the multi-link device (MLD) associated with the receiving device, or address 3 is used to indicate the address of the AP (referring to the AP in the AP MLD) associated with the receiving device, or in the management frame, address 3 is used for filtering. For example, the receiving device can use address 3 to determine whether the MPDU belongs to the basic service set (BSS). If not, the MPDU will be discarded.

[0158] The format of the sequence control field can be as follows: Figure 3As shown, 'b' represents a bit, such as b0 being bit 0. The sequence control field occupies 16 bits (i.e., b0-b15). The sequence control field can include a fragment number subfield (occupying 4 bits, b0-b3) and a sequence number subfield (occupying 12 bits, b4-b15).

[0159] The format of the service quality control field can be shown in Table 1 below:

[0160] Table 1

[0161]

[0162] Based on Table 1, the Quality of Service (QoS) control field occupies 16 bytes (i.e., B0-B15). When the MPDU is a QoS data frame or a QoS null frame sent by the access point device, the QoS control field may include a service identifier subfield (occupying B0-B3), a service period end subfield (occupying B4), B5-B6 are acknowledgment policy subfields (occupying B5-B6), an A-MSDU occurrence subfield (occupying B7), and an AP buffer status subfield (occupying B8-B15). When the MPDU is a QoS data frame or a QoS null frame sent by the site device, the difference is that if the bit value corresponding to B4 is 0, the subfields on B8-B15 are the requested transmission opportunity duration subfields; if the bit value corresponding to B4 is 1, the subfields on B8-B15 are the queue size subfields.

[0163] Specifically, when the service type is a low-latency service, the HT control field in the 802.11be and 802.11bn protocols may include a buffer report control information subfield. The buffer report control information subfield can be as follows: Figure 4 As shown, the cached reporting control information subfield, which occupies 22 bits, can include a service identifier subfield (occupying 4 bits), a queue size scaling factor subfield (occupying 2 bits), a low latency queue size subfield (occupying 6 bits), a time encoding subfield for time synchronization function (occupying 1 bit), a head of line (HOL) packet delay type subfield (occupying 1 bit), and a head of line packet delay feedback subfield (occupying 9 bits).

[0164] Specifically, the Service Identifier subfield indicates the service identifier corresponding to the reported queue size; the Queue Size Scale Factor subfield indicates the unit of the low-latency queue size; the Low-Latency Queue Size subfield indicates the size of the low-latency queue corresponding to the service identifier; the TSF Time Encoding subfield indicates the starting bit of the TSF value, as shown in Table 2 below; the Head-of-Queue Packet Delay Feedback subfield indicates the packet enqueue time (i.e., the time when the packet arrives at the MAC layer of the sending device) or the packet expiration time (i.e., the time when the packet arrives at the receiving device); the Head-of-Queue Packet Delay Type subfield indicates the time type indicated by the Head-of-Queue Packet Delay Feedback subfield. For example, when the bit value of the Head-of-Queue Packet Delay Type subfield is set to 0, it can indicate that the Head-of-Queue Packet Delay Feedback indicates the packet enqueue time; when the bit value of the Head-of-Queue Packet Delay Type subfield is set to 1, it can indicate that the Head-of-Queue Packet Delay Feedback indicates the packet expiration time.

[0165] Table 2

[0166] TSF Time-Encoded Subfield The start bit of the TSF value 0 10 1 Reserved bits

[0167] Based on Table 2, when the bit value of the TSF time encoding field is 0, the starting bit of the TSF value is the 10th bit of the TSF; when the bit value of the TSF time encoding field is 1, the starting bit of the TSF value is the reserved bit of the TSF.

[0168] It is understandable that the sum of the packet enqueue time and the latency limit corresponding to the business identifier is the packet expiration time.

[0169] It is understandable that the access point device can schedule the relevant transmissions of the site device based on the cached reporting control information subfield sent by the site device.

[0170] The Cipher-Block Chaining Message Authentication Code Protocol (CCMP) allows the addition of a CCMP header field to the MPDU frame format to encrypt unicast / management frames and multicast frames. The MPDU frame format with the CCMP header field is as follows: Figure 5 As shown.

[0171] The MAC header can include Figure 1 The CCMP header format includes the frame control field, duration field, address 1 field, address 2 field, address 3 field, sequence control field, and quality of service control field. Figure 5 As shown, the data and MIC are located in Figure 1The frame body field and frame check sequence field are... Figure 1 The frame verification sequence field in the data.

[0172] For the CCMP header, the packet number (PN) occupies 6 bytes, from low byte to high byte, corresponding to PN0-PN5 respectively. The third byte of the CCMP header is a reserved byte. The fourth byte of the CCMP header is the key identifier (Key ID) field. The key identifier field includes a fine timing management (FTM) subfield (the bit value of the FTM subfield is set to 1 when the MPDU is a protected fine timing management frame (fine TMF), an extended initialization vector (ExtIV) subfield (the bit value of the ExtIV subfield is always set to 1), an identifier subfield (bits 6 and 7 of the key identifier field are the key identifier subfield), and reserved bits.

[0173] CCMP also protects certain fields in the MAC header. These protected fields can be collectively referred to as Additional Authentication Data (AAD). AAD may include: the Version Protocol subfield, Type subfield, To DS subfield, From DS subfield, and more fragment subfields in the Frame Control field; Address 1 field, Address 2 field, Address 3 field; the Fragment Number subfield in the Sequence Control field; and the Quality of Service (QoS) control field.

[0174] It is understandable that the subfields of subtype, retry, power management, more data, protected frame, and HT control in the frame control field are not protected (masked out), and the subfield of sequence number in the sequence control field is not protected.

[0175] Stream classification service (SCS) mechanism: In the 802.11be standard, low latency is an important indicator. Site devices can report one or more service quality characteristic parameters associated with low-latency service flows to access point devices through the SCS mechanism. Correspondingly, access point devices can optimize scheduling based on one or more service quality characteristic parameters associated with low-latency service flows to reduce the latency of those one or more service flows.

[0176] Among them, the service quality characteristic parameters can be: latency limit and MAC service data unit (MSDU) delivery ratio.

[0177] Multiple MPDUs can be aggregated to obtain an MSDU; the MSDU delivery rate is the ratio of the number of MPDUs corresponding to the MSDU that arrive at the receiving device without timeout to the total number.

[0178] The SCS mechanism is explained in detail below:

[0179] A site device can send an SCS request frame to the access point device associated with the site device, reporting one or more low-latency service flows. The format of the SCS request frame can be as follows: Figure 6 As shown, an SCS request frame may include a category field, a robust action field, a dialog token field, and an SCS descriptor list field.

[0180] The category field indicates the category to which the action frame belongs.

[0181] The Robust Action field indicates which frame is in that category.

[0182] The dialogue token field is used to determine the corresponding SCS response frame. That is, if the value indicated by the dialogue token field in the SCS response frame corresponding to the SCS request frame is the same as the value indicated by the dialogue token field in the SCS request frame, the site device can determine the SCS response frame corresponding to the SCS request frame.

[0183] The description of the SCS response frame can be found in the following description of the SCS response frame, and will not be repeated here.

[0184] The format of the SCS descriptor list field can be as follows: Figure 7As shown, the SCS descriptor list may include the element ID subfield, length subfield, SCS identifier (SCSID) subfield, request type subfield, intra-access category priority element subfield, traffic classification (TCLAS) element subfield, traffic allocation processing element subfield, QoS characteristics element subfield, and optional subelements subfield.

[0185] The element identifier field is used to indicate the identifier assigned to the SCS stream.

[0186] The length subfield indicates the length of the SCS descriptor list field, which can also be understood as the duration of the SCS descriptor list field.

[0187] The request type subfield is used to indicate the type of request, such as Add (ADD) (in which case the bit value of the request type field can be set to 00), Remove (in which case the bit value of the request type field can be set to 01), and Change (in which case the bit value of the request type field can be set to 10).

[0188] The priority element subfield within the access category is optional, and the specific format can be as follows: Figure 7 As shown, the priority element subfield within the access category can occupy one byte. The priority element subfield within the access category can include the user priority subfield (occupying three bits), the alternate queue subfield (occupying one bit, indicating whether an alternate queue is established for the SCS flow), the drop eligibility subfield (occupying one bit, indicating whether the packets of the SCS flow can be dropped when there are not enough resources), and the reserve subfield (occupying three bits).

[0189] The Flow Classification subfield is optional and indicates how to identify the SCS flow, carrying the criteria for determining the SCS flow. The SCS descriptor list field can carry one or more Flow Classification subfields.

[0190] The Service Quality Feature element subfield is used to indicate the service identifier mapped to the SCS flow and the corresponding service quality parameters. The format of the Service Quality Feature element subfield can be as follows: Figure 8 As shown, the numbers represent the number of bytes occupied by each subfield. Service Quality Feature element subfields may include: Element Identifier, Length, Element ID Extension, Control Information, Minimum Service Interval, Maximum Service Interval, Minimum Data Rate, Delaybound, Maximum MSDU Size, Service Start Time, Service Start Time Link ID, Mean Data Rate, Burst Size, MSDU Lifetime, MSDU Delivery Info, and Medium Time.

[0191] The format of the control information subfield can be as follows: Figure 9 As shown in (a), the control information subfield can occupy four bytes, where b represents a bit, such as b0 representing the 0th bit. The control information subfield may include a direct subfield (occupying two bits, i.e., b0-b1), a service identifier subfield (occupying four bits, i.e., b2-b5), a user priority subfield (occupying three bits, i.e., b6-b8), a presence bitmap of additional parameters subfield (occupying sixteen bits, i.e., b9-b24), a link identifier (linkID) subfield (occupying four bits, i.e., b25-b28), and reserved bits (occupying three bits, i.e., b29-b31).

[0192] Specifically, the direction subfield indicates the direction of the SCS flow. For example, a bit value of 00 indicates uplink, 10 indicates downlink, 01 indicates a peer-to-peer (P2P) direct link, and 11 is a reserved value. The first 8 bits of the service identifier subfield indicate the service identifier, and the last 8 bits are reserved values. The user priority subfield indicates the service identifier mapped by the SCS flow, and can use 0-7 to represent user priority, with the same values ​​as in the service identifier subfield. The link identifier subfield indicates the link identifier corresponding to the direct link transmission.

[0193] The latency upper limit subfield indicates the maximum latency allowed for low-latency packets, in microseconds.

[0194] The MSDU submission information subfields can be as follows: Figure 9 As shown in (b), the MSDU delivery information subfield can occupy 8 bits. The MSDU delivery information subfield can include an MSDU delivery rate subfield (occupying four bits, i.e., b0-b3) and an MSDU count exponent subfield (occupying four bits, i.e., b4-b7). The MSDU delivery rate subfield indicates the packet delivery rate required under a given latency limit.

[0195] Understandably, latency cap and MSDU delivery rate are two important parameters in the Quality of Service (QoS) parameters.

[0196] Based on the above description of the SCS request frame, after receiving the SCS request frame, the access point device will send an SCS response frame to the site device. The format of the SCS response frame can be as follows: Figure 10 As shown, an SCS response frame may include a category field, a robust action field, a dialogue token field, a count field, an SCS status list field, and an SCS descriptor list.

[0197] The category field indicates the category to which the SCS request frame belongs.

[0198] The Robust Action field indicates which frame is in that category.

[0199] The dialogue token field must be consistent with the dialogue token in the corresponding SCS request frame.

[0200] The quantity field indicates the number of SCSIDs in the SCS status list.

[0201] The SCS status list field includes one or more SCS status groups. The SCS status list field may include a SCSID subfield (an identifier indicating the SCS) and a status code subfield (indicating whether the requested SCSID is accepted; for example, a status code of 1 indicates that the requested SCSID is accepted, and a status code of 0 indicates that the requested SCSID is not accepted).

[0202] Based on the above description of the SCS mechanism, when a site device reports a low-latency service flow through the SCS mechanism, the HT control field in the MPDU frame format can include a buffered reporting control information subfield, which allows the access point device to determine the packet expiration time required by the service flow and enables the access point device to prioritize scheduling to meet the low-latency requirements of the service flow.

[0203] Among these issues, determining whether the statistical latency of different service flows in the BSS meets QoS requirements and adjusting the scheduling strategy of the BBS (or AP MLD) in a timely manner to improve communication performance has become an urgent problem to be solved.

[0204] To address the aforementioned technical problems, this application provides a communication method, comprising: a transmitting device acquiring a first MPDU; and transmitting the first MPDU. The first MPDU includes a CCMP header field, which includes a first field indicating a first time or a second time of a second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the MAC layer of the transmitting device, and the second time of the second MPDU is the time when the transmitting device expects the second MPDU to arrive at the receiving device; the second MPDU is either the first MPDU or the next MPDU following the first MPDU.

[0205] In this embodiment, on the one hand, the transmitting device can carry a first field in the CCMP header field of the first MPDU. The first field can indicate the time when the first MPDU or the next MPDU of the first MPDU arrives at the MAC layer of the transmitting device, or the expected time when it arrives at the receiving device, so that the receiving device can determine the latency of the first MPDU. On the other hand, it can enable the receiving device to determine whether the actual time when the first MPDU or the next MPDU of the first MPDU arrives at the receiving device exceeds the time expected by the transmitting device. This allows the receiving device to monitor whether the corresponding service flow meets the latency requirements of the transmitting device, and thus enable the receiving device (such as an access point device) to adjust the scheduling in a timely manner to reduce latency and improve connectivity performance.

[0206] The sending device can be an access point device or a site device, and the receiving device can be a site device or an access point device.

[0207] In this system, different service flows in the BSS can transmit data through one or more first MPDUs. The receiving device can monitor in real time whether the actual time of each MPDU in one or more first MPDUs corresponding to different service flows in the BSS exceeds the time expected by the sending device. In this way, the scheduling can be adjusted in a timely manner to reduce latency and better meet the latency requirements of different service flows in the BSS.

[0208] The communication method provided in this application embodiment is applicable to wireless local area networks (WLANs) that support relevant IEEE standards. These relevant IEEE standards include: 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn / Ultra High Resolution (UHR) / Wireless Fidelity (Wi-Fi) 8, 802.11ad, 802.11ay, 802.11bf / sensing, Ultra Wideband (UWB) / 802.15, etc., and are not limited thereto.

[0209] For example, such as Figure 11 The diagram shown is a structural schematic of a communication system provided in this application. The communication system may include access point equipment and site equipment. The access point equipment can function as either a transmitting or receiving device; the site equipment can function as either a transmitting or receiving device.

[0210] There can be one or more access point devices, and there can be one or more site devices.

[0211] The access point device can be a device that supports multiple WLAN standards, such as the 802.11be standard or future Wi-Fi standards; it can also be a device that supports the 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, UHR, and Wi-Fi 8 standards, without any restrictions.

[0212] For example, access point devices can be terminal devices with Wi-Fi chips, network devices, communication servers, routers, switches, bridges, computers, etc. Access point devices can also serve as access points for mobile users to access wired networks, primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. Of course, they can also be deployed outdoors. An access point device acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet.

[0213] For example, the site device can be a device that supports multiple WLAN standards such as the 802.11be standard or future Wi-Fi standards; it can also be a device that supports the 802.11a / b / g standard, the 802.11n standard, the 802.11ac standard, the 802.11ax standard, the 802.11be standard, the 802.11bn standard / UHR standard / Wi-Fi 8 standard, without limitation.

[0214] For example, site equipment can be wireless communication chips, wireless sensors, wireless communication terminals, communication servers, routers, switches, bridges, computers, etc. For example, site equipment can be mobile phones supporting Wi-Fi communication, tablets supporting Wi-Fi communication, set-top boxes supporting Wi-Fi communication, smart TVs supporting Wi-Fi communication, smart wearable devices supporting Wi-Fi communication, vehicle communication equipment supporting Wi-Fi communication, and computers supporting Wi-Fi communication, etc., without restriction.

[0215] The aforementioned communication system can be applied to communication between an AP and multiple STAs, to communication between two STAs, or to communication between an AP multi-link device (MLD) and multiple non-AP MLDs.

[0216] The embodiments in this application can also be applied to... Figure 12 The communication system shown may include at least one AP multi-link device (MLD) and at least one STA MLD.

[0217] Among them, the AP MLD can include at least two APs (such as AP0 and AP1), and the STA MLD can include at least two STAs (such as STA0 and STA1). AP0 can communicate with STA0 through link 0, and AP1 can communicate with STA1 through link 1.

[0218] It should be noted that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0219] In practical implementation, Figure 11 and Figure 12 As shown in the figure: Each access point device and site device can adopt Figure 13 The shown composition structure, or including Figure 13 The components shown. Figure 13 This is a schematic diagram illustrating the composition of a communication device 1300 provided in an embodiment of this application. The communication device 1300 can be a site device or a chip or system-on-a-chip within a site device; it can also be an access point device or a chip or system-on-a-chip within an access point device. For example... Figure 13 As shown, the communication device 1300 includes a processor 1301, a transceiver 1302, and a communication line 1303.

[0220] Furthermore, the communication device 1300 may also include a memory 1304. The processor 1301, the memory 1304, and the transceiver 1302 can be connected via a communication line 1303.

[0221] The processor 1301 can be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 1301 can also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.

[0222] Transceiver 1302 is used to communicate with other devices or other communication networks. These other communication networks can be Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. Transceiver 1302 can be a module, circuit, transceiver, or any device capable of enabling communication.

[0223] Communication line 1303 is used to transmit information between the components included in communication device 1300.

[0224] Memory 1304 is used to store instructions. These instructions can be computer programs.

[0225] The memory 1304 may be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions; it may also be a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions; it may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0226] It should be noted that the memory 1304 can exist independently of the processor 1301, or it can be integrated with the processor 1301. The memory 1304 can be used to store instructions, program code, or some data, etc. The memory 1304 can be located inside or outside the communication device 1300, without limitation. The processor 1301 is used to execute the instructions stored in the memory 1304 to implement the communication method provided in the following embodiments of this application.

[0227] In one example, processor 1301 may include one or more CPUs, for example Figure 13 CPU0 and CPU1 in the CPU.

[0228] As an optional implementation, the communication device 1300 includes multiple processors, for example, besides Figure 13 In addition to processor 1301, it may also include processor 1307.

[0229] As an optional implementation, the communication device 1300 also includes an output device 1305 and an input device 1306. For example, the input device 1306 is a device such as a keyboard, mouse, microphone, or joystick, and the output device 1305 is a device such as a display screen or speaker.

[0230] It should be noted that the communication device 1300 can be a desktop computer, laptop computer, network server, mobile phone, tablet computer, wireless terminal, embedded device, chip system, or other device. Figure 13 Equipment with a similar structure. Furthermore... Figure 13 The structural composition shown does not constitute a limitation on the communication device, except... Figure 13 In addition to the components shown, the communication device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0231] In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.

[0232] Furthermore, the actions, terms, etc., involved in the various embodiments of this application can be referenced interchangeably without limitation. The message names or parameter names in the messages exchanged between the various devices in the embodiments of this application are merely examples, and other names may be used in specific implementations without limitation.

[0233] The following is combined Figure 11 and Figure 12 The communication system shown refers to the following Figure 14 The communication method provided in the embodiments of this application is described below, wherein the sending device can be... Figure 11 and Figure 12 Any access point device or site device in the communication system shown, the receiving device can also be Figure 11 and Figure 12 Any station device or access point device in the communication system shown. The transmitting or receiving device described in the following embodiments may have... Figure 13 The component shown.

[0234] Figure 14 A flowchart of a communication method provided in an embodiment of this application is shown below. Figure 14 As shown, the method may include:

[0235] S1401, The transmitting device obtains the first MPDU.

[0236] The first MPDU includes a CCMP header field, and the frame format of the first MPDU can be referred to above. Figure 5 The content shown will not be repeated here.

[0237] The CCMP header fields include a first field, and the frame format of the CCMP header fields can be as described above. Figure 5 The content shown will not be repeated here.

[0238] The first field can be described as a timing information field.

[0239] It is understood that the first field may occupy reserved bits in the CCMP header field, or the first field may be a newly added field in the CCMP header field, or the first field may reuse an existing field in the CCMP header field; this application does not limit this.

[0240] In the first example, taking the first field occupying reserved bits in the CCMP header fields as an example, the first field can occupy one or more reserved bits in the reserved field corresponding to the third byte in the CCMP header fields, or the first field can occupy one or more reserved bits in the key identifier field in the CCMP header fields.

[0241] In the second example, taking the first field as a newly added field in the CCMP header fields as an example, one or more fields can be added at the end of the CCMP header fields to carry the first field; or, one or more fields can be added at the beginning of the CCMP header fields to carry the first field.

[0242] In the third example, taking the reuse of an existing field in the CCMP header field as an example, the first field can occupy one or more PN fields in the CCMP header field, or it can occupy one or more bits in a PN field.

[0243] The first field is used to indicate the first time of the second MPDU or the second time of the second MPDU.

[0244] The second MPDU can be either the first MPDU or the next MPDU after the first MPDU. For example, the first field can indicate the first time of the first MPDU or the second time of the first MPDU, or the first field can indicate the first time of the next MPDU after the first MPDU or the second time of the next MPDU after the first MPDU.

[0245] The first time of the second MPDU is the time when the second MPDU arrives at the MAC layer of the sending device.

[0246] The first time can be described as the time of joining the team.

[0247] For example, the first time can be a moment or a timestamp, without limitation.

[0248] The second time of the second MPDU is the time when the transmitting device expects the second MPDU to arrive at the receiving device.

[0249] The second time can be described as the expiration time.

[0250] For example, the second time can be a moment or a timestamp, without limitation.

[0251] It is understandable that the time the sending device expects the second MPDU to arrive at the receiving device can also be interpreted as the time corresponding to the service QoS requirements.

[0252] It is understandable that the sum of the first time and the upper limit of the delay of the second MPDU can be the second time of the second MPDU. For example, the first time of the second MPDU can be T1, the upper limit of the delay can be Δ, and the second time of the second MPDU can be T1+Δ.

[0253] The latency limit can be indicated by the sending device through the SCS request frame, or it can be predefined, or it can be indicated by the sending device through other frames. This application does not limit it in this regard.

[0254] S1402, The transmitting device transmits the first MPDU; correspondingly, the receiving device acquires the first MPDU.

[0255] The transmitting device can transmit the first MPDU to the physical (PHY) layer and encapsulate the first MPDU into a first physical layer protocol data unit (PPDU) and send the first PPDU to the receiving device. Correspondingly, the receiving device can receive the first PPDU from the transmitting device and decapsulate the first PPDU to obtain the first MPDU.

[0256] S1403. The receiving device monitors the quality of service associated with the sending device based on the first field.

[0257] The quality of service associated with the sending device can be determined based on whether the actual time of the first MPDU arriving at the receiving device exceeds the time the sending device expects the first MPDU to arrive at the receiving device. The expected time of the first MPDU arriving at the receiving device is determined based on a first field. For example, the greater the difference between the actual time of the first MPDU arriving at the receiving device and the expected time of the first MPDU arriving at the receiving device, the worse the quality of service associated with the sending device.

[0258] Regarding whether the actual time of arrival of the first MPDU at the receiving end device exceeds the time expected by the sending end device for the first MPDU to arrive at the receiving end device, this application proposes two possible implementations:

[0259] In one possible implementation, the receiving device receives a first MPDU from the sending device. The CCMP header field of the first MPDU includes a first field that indicates the first time of the first MPDU. Based on the first time of the first MPDU, the receiving device can determine the second time of the first MPDU (i.e., the time when the sending device expects the first MPDU to arrive at the receiving device), and thus determine whether the actual time of arrival of the first MPDU at the receiving device exceeds the second time of the first MPDU.

[0260] Alternatively, the receiving device receives a first MPDU from the sending device. The CCMP header field of the first MPDU includes a first field, which can indicate the second time of the first MPDU (i.e., the time when the sending device expects the first MPDU to arrive at the receiving device). The receiving device can directly determine whether the actual time the first MPDU arrives at the receiving device exceeds the second time of the first MPDU.

[0261] In a second possible implementation, the receiving device receives a first MPDU from the sending device. The CCMP header field of the first MPDU includes a first field that indicates the first time of the next MPDU (i.e., the first field in the previous MPDU indicates the first time of the first MPDU). The receiving device can determine the second time of the first MPDU (i.e., the time when the sending device expects the first MPDU to arrive at the receiving device) based on the time indicated by the first field in the previous MPDU, and thus determine whether the actual time of arrival of the first MPDU at the receiving device exceeds the second time of the first MPDU.

[0262] Alternatively, the receiving device receives a first MPDU from the sending device. The CCMP header field of the first MPDU includes a first field, which can indicate the second time of the next MPDU (i.e., the first field in the previous MPDU indicates the second time of the first MPDU). The receiving device can determine the second time of the first MPDU (i.e., the time when the sending device expects the first MPDU to arrive at the receiving device) based on the time indicated by the first field in the previous MPDU, and thus determine whether the actual time of arrival of the first MPDU at the receiving device exceeds the second time of the first MPDU.

[0263] Based on the second possible implementation, when the first MPDU is the first MPDU, the first field in the first MPDU indicates the first time / second time of the second MPDU. To determine the first time / second time of the first MPDU, the first time / second time of the first MPDU can be determined by subtracting a preset time interval from the first time / second time of the second MPDU, or by predefining the first time / second time of the first MPDU; or it can be assumed that the actual time of the first MPDU arriving at the receiving device does not exceed the second time of the first MPDU. This application does not limit this.

[0264] It is understandable that when the receiving device is an access point device, the access point device can adjust the uplink transmission scheduling based on the quality of service associated with the access point device; when the receiving device is a site device, the site device can report the quality of service associated with the site device to the access point device so that the access point device can adjust the downlink transmission scheduling.

[0265] Based on the above Figure 14 The communication method shown allows the sending device to carry a first field in the CCMP header field of the first MPDU. This first field indicates the time when the first MPDU or its next MPDU arrives at the sending device's MAC layer, or the expected time it will arrive at the receiving device, enabling the receiving device to determine the latency of the first MPDU. Furthermore, it allows the receiving device to determine whether the actual arrival time of the first MPDU or its next MPDU exceeds the time expected by the sending device (which can also be understood as the time corresponding to the service QoS requirements). This allows the receiving device to monitor whether the corresponding service flow meets the sending device's latency requirements, and consequently, the receiving device (such as an access point device) can adjust the scheduling in a timely manner to reduce latency and improve connectivity performance.

[0266] Based on the above Figure 14 In the communication method shown, optionally, the sending device can be a site device and the receiving device can be an access point device; or, the sending device can be an access point device and the receiving device can be a site device.

[0267] Specifically, when the sending device is a site device and the receiving device is an access point device, the access point device can determine the actual time when the first MPDU from the site device arrives at the access point device. At the same time, the access point device can determine the time when the site device expects the first MPDU to arrive at the access point device based on the first field in the first MPDU from the site device. Then, it can determine whether the actual time when the first MPDU arrives at the access point device exceeds the time when the site device expects the first MPDU to arrive at the access point device, so as to determine the quality of service associated with the uplink transmission between the site device and the access point device.

[0268] Specifically, when the sending device can be an access point device and the receiving device can be a site device, the site device can determine the actual arrival time of the first MPDU from the access point device. Simultaneously, the site device can determine the expected arrival time of the first MPDU from the access point device based on the first field in the first MPDU. Furthermore, the site device can determine whether the actual arrival time of the first MPDU exceeds the expected arrival time, and report the average packet latency performance over a period of time to the access point device. Further, the access point device can determine the quality of service (QoS) associated with the downlink transmission between the access point device and the site device based on the information reported by the site device.

[0269] Furthermore, when the sending device can be an access point device and the receiving device can be a site device, the sending device can approximate the arrival time of the first MPDU at the receiving end based on the time when the acknowledgment frame (ACK) of the first MPDU is received, thereby allowing the receiving device to calculate downlink packet latency performance without requiring any additional feedback.

[0270] Based on the above description of the first MPDU, optionally, the transmitting device can divide the MSDU into one or more MPDUs (the first MPDU can be one of the multiple MPDUs) for transmission; correspondingly, the receiving device can obtain the MPDU and, based on the first field in the MPDU, calculate the MSDU delivery rate (i.e., the ratio of the number of MSDUs that meet the delay requirements of the transmitting device to the total number of MSDUs is the MSDU delivery rate), and determine the service quality associated with the transmitting device based on the MSDU delivery rate. For example, when the MSDU delivery rate is less than or equal to the MSDU delivery rate expected by the transmitting device, the service quality associated with the transmitting device is poor; when the MSDU delivery rate is greater than the MSDU delivery rate expected by the transmitting device, the service quality associated with the transmitting device is good.

[0271] The MSDU delivery rate expected by the sending device can be predefined or indicated by the sending device (such as by the first field or by the SCS request frame, etc.), without restriction.

[0272] In this context, the quality of service associated with the sending device can also be understood as the quality of service of the service flow between the access point device and the sending device. That is, there may be one or more service flows between the sending device and the receiving device, and the quality of service associated with each service flow can be determined by statistically analyzing the delivery rate of the MSDU corresponding to each service flow.

[0273] To calculate the delivery rate of MSDUs, taking N MSDUs as an example, assuming there is no fragmentation, i.e., each MSDU is sent via an MPDU, and the first MPDU is one of multiple MPDUs, the receiving device can determine the actual arrival time of the first MPDU (i.e., MSDU) and the expected arrival time of the sending device (i.e., the second time of the first MPDU) based on the two possible implementations in S1403 above. Similarly, the receiving device can record the actual arrival time of each MPDU (i.e., MSDU) among the N MPDUs (i.e., MSDUs) and the expected arrival time of the sending device. Furthermore, assuming there are N1 MPDUs whose actual arrival time exceeds the expected arrival time of the sending device, the receiving device can determine (N-N1) / N as the MSDU delivery rate.

[0274] Understandably, when the receiving device is an access point device, the access point device can use the MSDU delivery rate to calculate the service quality associated with the service flow; or, when the receiving device is a site device, the site device can determine the MSDU delivery rate using the aforementioned method and report the MSDU delivery rate to the access point device. Alternatively, the site device can report whether the actual arrival time of each MPDU among the multiple MPDUs included in the MSDU exceeds the access point device's expected arrival time for that MPDU. The access point device can then determine the MSDU delivery rate based on the information reported by the site device. Furthermore, the access point device can use the MSDU delivery rate to calculate the service quality associated with the service flow.

[0275] Understandably, by including the first field in the CCMP header field of the first MPDU, the receiving device can monitor in real time whether the actual time of arrival of each MPDU in one or more first MPDUs corresponding to different service flows in the BSS exceeds the time expected by the sending device. By determining the delivery rate of the MSDU, the service quality associated with the service flow can be statistically analyzed, and the scheduling can be adjusted in a timely manner to reduce latency and better meet the latency requirements of different service flows in the BSS.

[0276] In addition, compared to the service quality parameters reported by site devices related to service flows, access point devices can use the first field to statistically analyze the service quality associated with service flows, which can effectively reduce the signaling overhead of the air interface and reduce the implementation complexity of site devices.

[0277] Based on the above description of the first field, optionally, the position of the first field in the CCMP header field can be predefined, or the position of the first field in the CCMP header field can be determined based on the first instruction information.

[0278] The first indication information is used to indicate one or more of the following: the start position of the first field in the CCMP header field, the length of the first field, or the end position of the first field in the CCMP header field.

[0279] In the first example, the first indication information can indicate the starting position of the first field in the CCMP header field (such as B0). The ending position of the first field in the CCMP header field (B0+L) can be determined according to the predefined length (L) of the first field, and thus the position of the first field in the CCMP header field can be determined (i.e., B0-(B0+L)).

[0280] In the second example, the first indication information can indicate the starting position (e.g., B0) and length (L) of the first field in the CCMP header field, and can determine the ending position (B0+L) of the first field in the CCMP header field, and thus determine the position of the first field in the CCMP header field (i.e., B0-(B0+L)).

[0281] In the third example, the first indication information can indicate the start position (e.g., B0) and end position (e.g., B1) of the first field in the CCMP header field, which can directly determine the position of the first field in the CCMP header field (i.e., TB0-B1).

[0282] Optionally, the access point device may indicate the position of the first field in the CCMP header field to the site device via unicast, multicast, or broadcast, without restriction.

[0283] For example, the first indication information may be located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; or the first indication information may be transmitted separately.

[0284] The capability information is used to indicate support for the first field in the CCMP header.

[0285] The first request frame is used to request the enabling of the function of carrying the first field in the CCMP header field.

[0286] The capability information and the first request frame can be found in the following description of the capability information and the first request frame, which will not be repeated here.

[0287] Based on the above description of the position of the first field in the CCMP header, on the one hand, compared to the predefined position of the first field in the CCMP header, the access point device can dynamically indicate the position of the first field in the CCMP header to the site device through the first indication information according to the actual communication scenario or communication situation, which can improve the diversity and flexibility of determining the position of the first field in the CCMP header. On the other hand, compared to indicating the position of the first field in the CCMP header through the first indication information, the predefined position of the first field in the CCMP header can reduce the signaling overhead of the air interface and simplify the implementation.

[0288] Optionally, the first field can be determined based on a portion of the TSF bits in the beacon frame. That is, the information on a portion of the TSF bits in the beacon frame can be carried in the first field, and the information corresponding to the portion of the TSF bits is the first time / second time of the second MPDU.

[0289] For example, the TSF occupies 8 bytes, each byte including 8 bits. The information corresponding to all bits in the second byte (i.e., bits 8-15 in the TSF) can be carried in the first field, in which case the minimum time (or unit) indicated by the first field can be 256 microseconds; or, the information corresponding to some bits in the second byte (i.e., bits 10-15 in the TSF) can be carried in the first field, in which case the minimum time indicated by the first field can be 1024 microseconds; or, the information corresponding to bits 9-16 in the TSF can be carried in the first field, in which case the minimum time indicated by the first field can be 512 microseconds; or, the information corresponding to bits 10-16 in the TSF can be carried in the first field, in which case the minimum time indicated by the first field can be 1024 microseconds.

[0290] Optionally, some bits of the TSF corresponding to the first field can be predefined; or, some bits of the TSF corresponding to the first field can be determined based on the second indication information.

[0291] The second indication information is used to indicate one or more of the following: the position of the start bit of a portion of the TSF in the TSF, the position of the end bit of a portion of the TSF in the TSF, or the length of a portion of the TSF.

[0292] In the first example, the second indication information can indicate the position of the start bit of a portion of the TSF in the TSF (e.g., the bit corresponding to B0 in the TSF is the start bit of a portion of the TSF). Based on the length of the predefined first field (e.g., L, or it can be described as the first field occupying L bits), the position of the end bit of a portion of the TSF in the TSF (i.e., B0+L) can be determined, and thus the position of a portion of the TSF in the TSF (i.e., B0-(B0+L)) can be determined.

[0293] In the second example, the second indication information can indicate the position of the start bit of the partial bits of the TSF in the TSF (e.g., the bit corresponding to B0 in the TSF is the start bit of the partial bits of the TSF) and the length of the first field (e.g., L, or it can be described as the first field occupying L bits), which can determine the position of the end bit of the partial bits of the TSF in the TSF (i.e., B0+L), and thus determine the position of the partial bits of the TSF in the TSF (i.e., B0-(B0+L)).

[0294] In the third example, the second indication information can indicate the position of the start bit of a portion of the TSF in the TSF (e.g., the bit corresponding to B0 in the TSF is the start bit of a portion of the TSF) and the position of the end bit of a portion of the TSF in the TSF (e.g., the bit corresponding to B1 in the TSF is the end bit of a portion of the TSF), and can directly determine the position of a portion of the TSF in the TSF (i.e., B0-B1).

[0295] Optionally, the access point device may indicate a portion of the TSF corresponding to the first field to the site device via unicast, or via multicast, or via broadcast, without restriction.

[0296] For example, the second indication information may be located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; or the second indication information may be transmitted separately.

[0297] Based on the above description of the partial bits of the TSF corresponding to the first field, on the one hand, compared to the predefined partial bits of the TSF corresponding to the first field, the second indication information can dynamically indicate the partial bits of the TSF corresponding to the first field according to the actual communication scenario or communication situation. This can improve the diversity and flexibility of determining the partial bits of the TSF corresponding to the first field. Furthermore, it can flexibly adjust the partial bits of the TSF corresponding to the first field according to the different latency requirements of different service flows, such as latency accuracy, thereby meeting the latency performance monitoring needs of service flows with different latency requirements. On the other hand, compared to indicating the partial bits of the TSF corresponding to the first field through the second indication information, the predefined partial bits of the TSF corresponding to the first field can reduce air interface signaling overhead and simplify implementation.

[0298] Based on the above description of the first instruction information and the second instruction information, the first instruction information and the second instruction information may be located in the same message transmission or in different message transmissions, and this application does not limit this.

[0299] Optionally, the first field can be protected by the MIC in the first MPDU.

[0300] For example, the first field can be part of AAD.

[0301] AAD can be referred to in the above description of AAD, and will not be repeated here.

[0302] Optionally, the first six bytes of the TSF can be used as the PN field in the CCMP header of the first MPDU; that is, the information in the first six bytes of the TSF can be carried in the PN field of the CCMP header. Alternatively, the second to seventh bytes of the TSF can be used as the PN field in the CCMP header of the first MPDU.

[0303] Based on the above description of the first field, optionally, the access point device can send capability information to the site device to indicate whether the access point device supports carrying the first field in the CCMP header field. Similarly, the site device can send capability information to the access point device to indicate whether the site device supports carrying the first field in the CCMP header field.

[0304] Specifically, the sending device can send capability information to the receiving device; correspondingly, the receiving device can receive capability information from the sending device.

[0305] The capability information is used to indicate support for carrying the first field in the CCMP header.

[0306] It is understandable that if the receiving device receives capability information, the receiving device can determine that the sending device supports carrying the first field in the CCMP header field; if the receiving device does not receive capability information, the receiving device can determine that the sending device does not support carrying the first field in the CCMP header field.

[0307] For example, taking capability information occupying one bit as an example, the bit value can be set to 1 to indicate that the first field is supported in the CCMP header field; or, the bit value can be set to 0 to indicate that the first field is supported in the CCMP header field.

[0308] The capability information can also be described as indicating whether it is supported to carry the first field in the CCMP header field.

[0309] It is understandable that by setting different bit values, the receiving device can determine whether to support carrying the first field in the CCMP header field based on the different bit values.

[0310] For example, taking capability information occupying one bit as an example, the bit value can be set to 1 to indicate that the first field is supported in the CCMP header field; the bit value can be set to 0 to indicate that the first field is not supported in the CCMP header field. Alternatively, the bit value can be set to 0 to indicate that the first field is supported in the CCMP header field; the bit value can be set to 1 to indicate that the first field is not supported in the CCMP header field.

[0311] Based on the above description of capability information, the receiving device can determine whether the sending device supports carrying the first field in the CCMP header field.

[0312] Optionally, the access point device may send a first request frame to the site device to request the site device to enable the function of carrying the first field in the CCMP header field. Similarly, the site device may send a first request frame to the access point device to request the access point device to enable the function of carrying the first field in the CCMP header field.

[0313] Specifically, the sending device can send a first request frame to the receiving device; correspondingly, the receiving device can receive the first request frame from the sending device.

[0314] The first request frame is used to request the enabling of the function of carrying the first field in the CCMP header field.

[0315] Furthermore, if the device receiving the first request frame agrees to enable the function of carrying the first field in the CCMP header field, it may return the first response frame or not (i.e., it agrees to enable the function of carrying the first field in the CCMP header field by default); or, if the device receiving the first request frame does not agree to enable the function of carrying the first field in the CCMP header field, it may return the first response frame or not (i.e., it does not agree to enable the function of carrying the first field in the CCMP header field by default).

[0316] In one example, returning a first response frame can indicate agreement to enable the feature of including the first field in the CCMP header, while not returning a first response frame can indicate disagreement. For instance, when a device receives a first request frame and agrees to enable the feature of including the first field in the CCMP header, it can return a first response frame. Taking the first response frame as an example (occupying one bit), the bit value can be set to 1 to indicate agreement to enable the feature; or, the bit value can be set to 0 to indicate agreement to enable the feature.

[0317] In another example, a first response frame is returned regardless of whether the user agrees to enable the feature of including the first field in the CCMP header. For instance, assuming the first response frame occupies one bit, the bit value can be set to 1 to indicate agreement to enable the feature, and to 0 to indicate disagreement. Alternatively, the bit value can be set to 0 to indicate agreement to enable the feature, and to 1 to indicate disagreement.

[0318] Based on the above description of the first request frame and the first response frame, optionally, the first request frame can be a newly defined request frame or an SCS request frame, and this application does not limit it in this regard.

[0319] For example, when the first request frame is an SCS request frame, the SCS request frame can be reused and a newly defined element can be carried, or an extended field can be added to the Quality of Service feature element to carry relevant indication information to negotiate the enabling of the function of carrying the first field in the CCMP header field.

[0320] Optionally, the first response frame can be a newly defined response frame or an SCS response frame; this application does not limit this.

[0321] Based on the above description of the first request frame and the first response frame, the sending device (or receiving device) of the first MPDU can determine that the receiving device (or sending device) of the first MPDU supports or agrees to include the first field in the CCMP header field. This can minimize the possibility of the receiving device being unable to recognize the first field even though the CCMP header field includes it, thereby improving the interaction efficiency between the sending and receiving devices and reducing resource waste.

[0322] Based on the above description of the first request frame, optionally, the first request frame can also be used to request negotiation of relevant parameters; correspondingly, the first response frame can also be used to indicate relevant parameters.

[0323] For example, the relevant parameters can be one or more of the following: first indication information, second indication information, third indication information, fourth indication information, or fifth indication information.

[0324] The first or second instruction information can be referred to in the above description of the first or second instruction information, and the third, fourth or fifth instruction information can be referred to in the following description of the third, fourth or fifth instruction information, which will not be repeated here.

[0325] Optionally, the first request frame may request to enable the function of carrying the first field in the CCMP header field during uplink transmission (i.e., the CCMP header field of the first MPDU sent by the site device to the access point device includes the first field, while the CCMP header field of the first MPDU sent by the access point device to the site device does not include the first field); or, the first request frame may request to enable the function of carrying the first field in the CCMP header field during downlink transmission (i.e., the CCMP header field of the first MPDU sent by the access point device to the site device includes the first field, while the CCMP header field of the first MPDU sent by the site device to the access point device does not include the first field); or, the first request frame may request to enable the function of carrying the first field in the CCMP header field during both uplink and downlink transmission (i.e., the CCMP header field of the first MPDU sent by the site device to the access point device includes the first field, and simultaneously, the CCMP header field of the first MPDU sent by the access point device to the site device also includes the first field).

[0326] Alternatively, the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during uplink transmission and to negotiate relevant parameters; or, the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during downlink transmission and to negotiate relevant parameters; the first request frame can be used to request the activation of the function of carrying the first field in the CCMP header field during both uplink and downlink transmission and to negotiate relevant parameters.

[0327] For example, when the first request frame is an SCS request frame, the SCS request frame can be reused and a newly defined element or the direction subfield in the QoS feature element of the SCS request frame can be carried to indicate whether uplink or downlink is enabled, or whether uplink or downlink carries the first field in the CCMP header. The specific location of the direction subfield in the SCS request frame can be found in [reference needed]. Figures 6-9 .

[0328] Based on the above description of the first MPDU including the first field, optionally, the first MPDU may also include a second field to indicate to the receiving device that the first field exists in the CCMP header fields.

[0329] The second field is used to indicate that the first field exists in the CCMP header fields.

[0330] It is understandable that when the first MPDU carries the second field, the receiving device can determine that the first field exists in the CCMP header field, and thus can parse the first field; when the first MPDU does not carry the second field, the receiving device can determine that the first field does not exist in the CCMP header field, and thus will not parse the first field. This can improve the interaction efficiency between the receiving device and the sending device, and at the same time improve the working efficiency of the receiving device.

[0331] For example, taking the second field occupying one bit as an example, the bit value can be set to 1 to indicate that the first field exists in the CCMP header field; or, the bit value can be set to 0 to indicate that the first field does not exist in the CCMP header field.

[0332] The second field can also be described as indicating whether the first field exists in the CCMP header fields.

[0333] It is understandable that different bit values ​​can be set for the second field so that the receiving device can determine whether the first field exists in the CCMP header field by using different bit values.

[0334] For example, taking the second field occupying one bit as an example, the bit value can be set to 1 to indicate that the first field exists in the CCMP header field; the bit value can be set to 0 to indicate that the first field does not exist in the CCMP header field. Alternatively, the bit value can be set to 0 to indicate that the first field exists in the CCMP header field; the bit value can be set to 1 to indicate that the first field does not exist in the CCMP header field.

[0335] Optionally, the second field can be located in the MAC header field of the first MPDU (e.g., it can be a newly added field in the MAC header field, or it can occupy the reserved bits in the MAC header field, or it can reuse the existing field in the MAC header field), or it can be located in the CCMP header field of the first MPDU (e.g., it can be a newly added field in the CCMP header field, or it can occupy the reserved bits in the CCMP header field, or it can reuse the existing field in the CCMP header field), without any restrictions.

[0336] For example, the second field can be placed before the first field in the CCMP header fields.

[0337] Optionally, this application also proposes a communication method that enables the receiving device to determine the time type indicated by the first field (such as a first time or a second time), that is, the receiving device can determine whether the first field indicates the first time of the second MPDU or the second time of the second MPDU based on the communication method. This application proposes three possible designs:

[0338] In the first possible design, the transmitting device can indicate the time type indicated by the first field to the receiving device through the third field. That is, the first MPDU may include the third field, which is used to indicate that the first field indicates the first time of the second MPDU, or the third field is used to indicate that the first field indicates the second time of the second MPDU.

[0339] The third field can be described as a timing information type field.

[0340] For example, taking the third field occupying one bit as an example, the bit value can be set to 1 to indicate that the first field indicates the first time of the second MPDU; the bit value can be set to 0 to indicate that the first field indicates the second time of the second MPDU. Alternatively, the bit value can be set to 0 to indicate that the first field indicates the first time of the second MPDU; the bit value can be set to 1 to indicate that the first field indicates the second time of the second MPDU.

[0341] It is understood that the third field can be located in the MAC header field of the first MPDU (e.g., it can be a newly added field in the MAC header field, it can occupy the reserved bits in the MAC header field, or it can reuse the existing field in the MAC header field), or the third field can be located in the CCMP header field of the first MPDU (e.g., it can be a newly added field in the CCMP header field, it can occupy the reserved bits in the CCMP header field, or it can reuse the existing field in the CCMP header field), without any restrictions.

[0342] Specifically, the position of the third field in the first MPDU can be predefined or determined based on the third indication information.

[0343] The third indication information is used to indicate the specific location of the third field in the first MPDU.

[0344] Optionally, the access point device may indicate the position of the third field in the first MPDU to the site device via unicast, multicast, or broadcast, without restriction.

[0345] For example, the third indication information may be located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; or the third indication information may be transmitted separately.

[0346] Optionally, the third field can be protected by the MIC in the first MPDU.

[0347] For example, the third field can be part of AAD.

[0348] In the second possible design, the sending device can indicate the time type indicated by the first field to the receiving device through the fourth indication information. That is, the sending device can send the fourth indication information to the receiving device, and the receiving device can receive the fourth indication information from the sending device and determine the time type indicated by the first field based on the fourth indication information.

[0349] The fourth indication information is used to indicate that the first field indicates the first time of the second MPDU, or the fourth indication information is used to indicate that the first field indicates the second time of the second MPDU.

[0350] For example, taking the fourth indication information occupying one bit as an example, the bit value can be set to 1 to indicate that the first field indicates the first time of the second MPDU; the bit value can be set to 0 to indicate that the first field indicates the second time of the second MPDU. Alternatively, the bit value can be set to 0 to indicate that the first field indicates the first time of the second MPDU; the bit value can be set to 1 to indicate that the first field indicates the second time of the second MPDU.

[0351] For example, the fourth indication information may be located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; or the fourth indication information may be transmitted separately.

[0352] Based on the above description of the first and second possible designs, compared to the second possible design, in the first possible design, the receiving device can determine the third field in the first MPDU and determine the time type indicated by the first field in the first MPDU based on the third field, which can improve the accuracy of determining the time type indicated by the first field; compared to the first possible design, in the second possible design, the changes to the first MPDU frame format can be minimized, which can reduce the complexity of implementation.

[0353] In a third possible design, the first MPDU may include a fourth field, which is used to indicate the identifier of the SCS. If the first MPDU includes a fourth field, the first field is used to indicate the first time of the second MPDU. That is, the receiving device can determine the first time of the second MPDU indicated by the first field based on the fourth field.

[0354] Understandably, the SCS request frame will carry the SCS identifier (i.e., SCSID). SCSID occupies 8 bits, and the high four bits of SCSID can be set to 0 or be the same as TID.

[0355] In one example, the fourth field can indicate the lower four bits of the SCSID. In this case, the fourth field can occupy four bits to reduce signaling overhead.

[0356] In another example, the lower four bits of the fourth field can carry the lower four bits of SCSID, and the higher four bits of the fourth field can carry TID. In this case, the fourth field can occupy eight bits.

[0357] It is understandable that by carrying a fourth field in the first MPDU to indicate the service flow to which the second MPDU belongs, and implicitly indicating that the first field is used to indicate the first time of the second MPDU, a feasible solution can be provided for determining the time type indicated by the first field. Furthermore, by carrying a fourth field in the first MPDU, the identifier of the SCS or the latency limit corresponding to the second MPDU can also be implicitly indicated, thereby enabling the receiving device to determine the second time of the second MPDU based on the latency limit corresponding to the SCS identifier and the first time of the second MPDU.

[0358] Optionally, the fourth field may be located in the MAC header field of the first MPDU; or, the fourth field may be located in the CCMP header field of the first MPDU.

[0359] For example, the fourth field can be carried using reserved bits in the CCMP header field.

[0360] Optionally, the position of the fourth field in the first MPDU can be predefined; or, the position of the fourth field in the first MPDU can be determined based on the fifth instruction information.

[0361] The fifth indication information is used to indicate one or more of the following: the starting position of the fourth field in the first MPDU, the length of the fourth field, or the ending position of the fourth field in the first MPDU.

[0362] In the first example, the fifth indication information can indicate the starting position of the fourth field in the first MPDU (e.g., B0). Based on the predefined length of the fourth field (e.g., L), the ending position of the fourth field in the first MPDU (i.e., B0+L) can be determined, and thus the specific position of the fourth field in the first MPDU (i.e., B0-(B0+L)) can be determined.

[0363] In the second example, the fifth indication information can indicate the starting position (e.g., B0) and length (e.g., L) of the fourth field in the first MPDU, determine the ending position (i.e., B0+L) of the fourth field in the first MPDU, and thus determine the specific position of the fourth field in the first MPDU (i.e., B0-(B0+L)).

[0364] In the third example, the fifth indication information can indicate the starting position (e.g., B0) and ending position (e.g., B1) of the fourth field in the first MPDU, and can directly determine the specific position of the fourth field in the first MPDU (i.e., B0-B1).

[0365] Optionally, the access point device may indicate the position of the fourth field in the first MPDU to the site device via unicast, multicast, or broadcast, without restriction.

[0366] For example, the fifth instruction information may be located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; or the fifth instruction information may be transmitted separately.

[0367] Optionally, the fourth field is protected by the MIC in the first MPDU.

[0368] For example, the fourth field can be part of AAD.

[0369] Based on the third possible design, when the first MPDU does not include the fourth field, the receiving device can determine the time type indicated by the first field according to the third field or the fourth indication information. Alternatively, it can be predefined that when the first MPDU does not include the fourth field, the first field indicates the second time of the second MPDU. This application does not limit this.

[0370] Based on the above three possible designs, the first and second possible designs can explicitly indicate the time type indicated by the first field, while the third possible design can implicitly indicate the time type indicated by the first field.

[0371] Based on the description of the above communication method, the embodiments in this application can also be applied to multi-link communication scenarios (as described above). Figure 12 As shown in the figure, the sending device and the receiving device can communicate through multiple links. Since the time corresponding to different links may be different, the time indicated by the first field can be referenced by the time corresponding to one of the links (such as the first link); or, to force the TSF time corresponding to multiple links to be the same, the time indicated by the first field can be referenced by the time corresponding to any link.

[0372] The first link can be predefined, or it can be determined according to preset rules, or it can be determined according to the sixth instruction information.

[0373] The sixth indication information is used to indicate the identifier of the first link.

[0374] In the first example, taking the first link as a predefined one, assuming there are three links (such as link 1, link 2, and link 3), the first link can be predefined as link 1; or, the first link can be predefined as link 2; or, the first link can be predefined as link 3.

[0375] In the second example, the first link is determined according to a preset rule. This preset rule can specify that the identifier of the first link is the maximum or minimum value among the identifiers of multiple links. For example, assuming there are three links (e.g., the identifier of link 1 is 1, the identifier of link 2 is 2, and the identifier of link 3 is 3), when the preset rule specifies that the identifier of the first link is the minimum value among the identifiers of multiple links, the minimum value among the identifiers of the three links can be determined to be 1, thus identifying the first link as link 1; when the preset rule specifies that the identifier of the first link is the maximum value among the identifiers of multiple links, the maximum value among the identifiers of the three links can be determined to be 3, thus identifying the first link as link 3.

[0376] In the third example, taking the determination of the first link based on the sixth indication information as an example, assuming there are three links (such as the identifier of link 1 being 1, the identifier of link 2 being 2, and the identifier of link 3 being 3), when the sixth indication information indicates 1, the first link can be determined to be link 1; or, when the sixth indication information indicates 2, the first link can be determined to be link 2; or, when the sixth indication information indicates 3, the first link can be determined to be link 3.

[0377] Based on the above description of the reference time for determining the time corresponding to the first field, a feasible solution is provided for the receiving device to statistically analyze latency performance.

[0378] Based on the above description of the sixth indication information, optionally, the access point device can indicate the identifier of the first link to the site device via unicast, or the access point device can indicate the identifier of the first link to the site device via multicast, or the access point device can indicate the identifier of the first link to the site device via broadcast, without restriction.

[0379] For example, the sixth instruction information may be located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; or the sixth instruction information may be transmitted separately.

[0380] It is understandable that when the sixth indication information is located in the first request frame, assuming the first request frame is an SCS request frame, the link identifier subfield of the service start time in the service quality feature element field of the SCS request frame can be reused to carry the sixth indication information. The position of the link identifier subfield of the service start time in the SCS request frame can be referenced... Figures 6-8 .

[0381] Based on the description of the above communication method, this application also proposes a communication method for access point equipment to estimate the resource requirements of site equipment, and to provide the necessary resources to the site equipment in a timely manner to reduce latency. The specific steps are as follows: Figure 15 As shown:

[0382] S1501, The site equipment obtains the first information.

[0383] The first piece of information is used to indicate the scheduling cycle or polling cycle.

[0384] Optionally, the first information can be predefined, or the first information can be carried in the beacon frame, or the first information can be determined based on the service interval in the SCS request frame.

[0385] For example, the first information can be determined based on the minimum service interval field in the service quality feature element field of the SCS request frame (i.e., the time indicated by the minimum service interval subfield is the scheduling period or the polling period), or the first information can be determined based on the maximum service interval field in the service quality feature element field of the SCS request frame (i.e., the time indicated by the maximum service interval subfield is the scheduling period or the polling period).

[0386] The Quality of Service (QoS) feature element fields in the SCS request frame can be referenced as described above. Figure 8 The description.

[0387] It is understood that the scheduling period or polling period corresponding to at least two of the first service flows in different first service flows may be different or the same, and this application does not limit this.

[0388] S1502. The site device sends the second information to the access point device based on the first information; correspondingly, the access point device receives the second information from the site device.

[0389] The second piece of information is used to indicate the size of the buffer that must be sent before the next estimated scheduling time arrives, otherwise the packet delay will exceed the delay limit.

[0390] The next estimated scheduling time is determined based on the first information.

[0391] In the first example, the next estimated scheduling time can be the current time plus the scheduling period or polling period indicated by the first information. For example, if the current time is T0 and the scheduling period or polling period is Δ, the next estimated scheduling time can be T0+Δ.

[0392] In the second example, taking the determination of the first information based on the maximum service interval sub-field in the service quality feature element field of the SCS request frame as an example, after the SCS session is successfully established, the scheduling time can be calculated according to the start time of the SCS session and the maximum service interval, and this scheduling time is the next estimated scheduling time; or, taking the determination of the first information based on the minimum service interval sub-field in the service quality feature element field of the SCS request frame as an example, after the SCS session is successfully established, the scheduling time can be calculated according to the start time of the SCS session and the maximum service interval, and this scheduling time is the next estimated scheduling time.

[0393] S1503. The access point device adjusts the scheduling resources associated with the site device based on the second information.

[0394] The access point device can determine the buffer size that must be sent before the next estimated scheduling time based on the second information, and adjust the scheduling resources associated with the site device according to the required buffer size. For example, when the buffer size is large, the scheduling resources associated with the site device can be increased.

[0395] based on Figure 15 The communication method shown allows the access point device to determine the buffer size that must be sent before the next estimated scheduling time arrives based on the second information. This allows the device to determine in advance whether to adjust the scheduling resources associated with the site device, thus minimizing the possibility of the access point device being unable to meet the resource requirements of the site device and improving the reliability of communication.

[0396] based on Figure 14 and Figure 15 The communication method shown can... Figure 14 The communication method shown is Figure 15 The communication methods shown are used in combination at this time. Figure 14 The transmitting device can be an access point device, and the receiving device can be a site device; or, it can be... Figure 14 The communication method shown is Figure 15 The communication method shown is used alone, and this application does not limit it.

[0397] The various embodiments of this application can be implemented independently or in combination, without limitation. Unless otherwise specified or in conflict of logic, the terminology and / or descriptions between the different embodiments provided in this application are consistent and can be referenced mutually. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0398] It is understood that in the embodiments of this application, the executing entity may perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the various steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0399] The foregoing primarily describes the solutions provided in this application from the perspective of device-to-device interaction. It is understood that each device, in order to achieve the aforementioned functions, includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art will readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0400] This application embodiment can divide each device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. The module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0401] When dividing each function into modules according to its corresponding function. Figure 16 A transmitting device 160 is shown, which can perform the above-described... Figure 14 and Figure 15 The actions performed by the sending device in the method shown, and all related content of each step involved in the above method embodiments, can be referenced from the functional description of the corresponding functional module. The technical effects that can be obtained can be referred to the above method embodiments, and will not be repeated here.

[0402] The transmitting device 160 may include a transceiver module 1601 and a processing module 1602. Exemplarily, the transmitting device 160 may be a communication device, or a chip or other combination device or component having the aforementioned transmitting device functions applied in a communication device. When the transmitting device 160 is a communication device, the transceiver module 1601 may be a transceiver, which may include an antenna and radio frequency circuits, etc.; the processing module 1602 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs. When the transmitting device 160 is a component having the aforementioned transmitting device functions, the transceiver module 1601 may be a radio frequency unit; the processing module 1602 may be a processor (or processing circuit), such as a baseband processor. When the transmitting device 160 is a chip system, the transceiver module 1601 may be an input / output interface of a chip (e.g., a baseband chip); the processing module 1602 may be a processor (or processing circuit) of the chip system, and may include one or more central processing units. It should be understood that the transceiver module 1601 in the embodiments of this application can be implemented by a transceiver or transceiver-related circuit components; the processing module 1602 can be implemented by a processor or processor-related circuit components (or, referred to as processing circuit).

[0403] For example, the transceiver module 1601 can be used to perform... Figure 14 and Figure 15 In the illustrated embodiment, all transmit and receive operations performed by the transmitting device, and / or other processes used to support the techniques described herein; the processing module 1602 can be used to perform Figure 14 and Figure 15 The embodiments shown include all operations performed by the transmitting device other than the sending and receiving operations, and / or other processes used to support the techniques described herein.

[0404] Figure 17 A receiving device 170 is shown, which can perform the above-described actions. Figure 14 and Figure 15 The actions performed by the receiving device in the method shown, and all related content of each step involved in the above method embodiments, can be referenced from the functional description of the corresponding functional module. The technical effects that can be obtained can be referred to the above method embodiments, and will not be repeated here.

[0405] The receiving device 170 may include a transceiver module 1701 and a processing module 1702. Exemplarily, the receiving device 170 may be a communication device, or a chip or other combination device or component having the aforementioned receiving device functions applied in a communication device. When the receiving device 170 is a communication device, the transceiver module 1701 may be a transceiver, which may include an antenna and radio frequency circuits, etc.; the processing module 1702 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs. When the receiving device 170 is a component having the aforementioned receiving device functions, the transceiver module 1701 may be a radio frequency unit; the processing module 1702 may be a processor (or processing circuit), such as a baseband processor. When the receiving device 170 is a chip system, the transceiver module 1701 may be an input / output interface of a chip (e.g., a baseband chip); the processing module 1702 may be a processor (or processing circuit) of the chip system, and may include one or more central processing units. The transceiver module 1701 in this embodiment can be implemented by a transceiver or transceiver-related circuit components; the processing module 1702 can be implemented by a processor or processor-related circuit components (or, referred to as processing circuit).

[0406] For example, transceiver module 1701 can be used to perform... Figure 14 and Figure 15 In the illustrated embodiment, all transmit and receive operations performed by the receiving device, and / or other processes used to support the techniques described herein; processing module 1702 can be used to perform Figure 14 and Figure 15 The embodiments shown include all operations performed by the receiving device other than the transmit and receive operations, and / or other processes used to support the techniques described herein.

[0407] As another feasible approach Figure 16 The transceiver module 1601 can be replaced by a transceiver unit, which can integrate the functions of the transceiver module 1601; the processing module 1602 can be replaced by a processor, which can integrate the functions of the processing module 1602. Furthermore, Figure 16 The transmitting device 160 shown may also include a memory. Alternatively, Figure 17 The transceiver module 1701 can be replaced by a transceiver unit, which can integrate the functions of the transceiver module 1701; the processing module 1702 can be replaced by a processor, which can integrate the functions of the processing module 1702. Furthermore, Figure 17 The receiver device 170 shown may also include a memory.

[0408] Alternatively, when the processing module 1602 is replaced by a processor and the transceiver module 1601 is replaced by a transceiver, the transmitting end device 160 involved in the embodiments of this application can also be... Figure 18 The communication device 180 shown. Alternatively, when the processing module 1702 is replaced by a processor and the transceiver module 1701 is replaced by a transceiver, the receiving end device 170 involved in the embodiments of this application can also be Figure 18 The communication device 180 shown.

[0409] The processor can be logic circuit 1801, and the transceiver can be interface circuit 1802. Furthermore, Figure 18 The communication device 180 shown may also include a memory 1803.

[0410] This application also provides a computer program product that, when executed by a computer, can implement the functions of any of the above method embodiments.

[0411] This application also provides a computer program that, when executed by a computer, can implement the functions of any of the above method embodiments.

[0412] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be an internal storage unit of the terminal (including a data sending end and / or a data receiving end) of any of the foregoing embodiments, such as the terminal's hard disk or memory. The computer-readable storage medium can also be an external storage device of the terminal, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal. Further, the computer-readable storage medium can include both the terminal's internal storage unit and external storage devices. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0413] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0414] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0415] In this application, "at least one (item)" means one or more. "More than one" means two or more. "At least two (items)" means two or three or more. "And / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple. "...when" and "if" both mean that a corresponding action will be taken under certain objective circumstances, not a time limit, nor do they require a judgment action at the time of implementation, nor do they imply any other limitations.

[0416] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0417] In this application, "sending information to...(terminal device)" can be understood as the destination of the information being the terminal device. This can include sending information directly or indirectly to the terminal device. "Receiving information from...(terminal device)" can be understood as the source of the information being the terminal device, and can include receiving information directly or indirectly from the terminal device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source.

[0418] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0419] In the several embodiments provided in this application, the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0420] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0421] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0422] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of this application embodiment, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

Claims

1. A communication method, characterized in that, include: Obtain a first Media Access Control (MAC) Protocol Data Unit (MPDU); wherein the first MPDU includes a Counter Mode Cipher Block Chaining Message Complete Code (CCMP) header field, the CCMP header field including a first field, the first field being used to indicate a first time of a second MPDU or a second time of the second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the Media Access Control (MAC) layer of the transmitting device, the second time of the second MPDU is the time when the transmitting device expects the second MPDU to arrive at the receiving device; the second MPDU is the first MPDU or the next MPDU of the first MPDU; Transmit the first MPDU.

2. The method according to claim 1, characterized in that, The first field is positioned in a predefined location within the CCMP header fields; or The position of the first field in the CCMP header field is determined according to the first indication information; wherein, the first indication information is used to indicate one or more of the following: the start position of the first field in the CCMP header field, the length of the first field, or the end position of the first field in the CCMP header field.

3. The method according to claim 2, characterized in that, The first indication information is located in one or more of the following: beacon frame, broadcast frame, capability information, or first request frame; wherein, the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame is used to request to enable the function of the CCMP header field to carry the first field.

4. The method according to any one of claims 1-3, characterized in that, The first field is determined based on a portion of the bits in the timing synchronization function TSF in the beacon frame.

5. The method according to claim 4, characterized in that, The TSF bits corresponding to the first field are predefined; or The partial bits of the TSF corresponding to the first field are determined according to the second indication information; wherein, the second indication information is used to indicate one or more of the following: the position of the start bit of the partial bits of the TSF in the TSF, the position of the end bit of the partial bits of the TSF in the TSF, or the length of the partial bits of the TSF.

6. The method according to claim 5, characterized in that, The second indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein, the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame is used to request to enable the function of the CCMP header field to carry the first field.

7. The method according to any one of claims 1-6, characterized in that, The first field is protected by the Message Complete Code (MIC) in the first MPDU.

8. The method according to any one of claims 1-7, characterized in that, The first MPDU includes a second field; wherein the second field is used to indicate that the first field exists in the CCMP header field.

9. The method according to any one of claims 1-8, characterized in that, The first MPDU further includes a third field; wherein the third field is used to indicate that the first field indicates a first time of the second MPDU, or the third field is used to indicate that the first field indicates a second time of the second MPDU.

10. The method according to claim 9, characterized in that, The position of the third field in the first MPDU is predefined; or The position of the third field in the first MPDU is determined according to the third indication information; wherein, the third indication information is used to indicate the position of the third field in the first MPDU.

11. The method according to claim 10, characterized in that, The third indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein, the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame is used to request to enable the function of the CCMP header field to carry the first field.

12. The method according to any one of claims 9-11, characterized in that, The third field is located in the MAC header field of the first MPDU; or The third field is located in the CCMP header field of the first MPDU.

13. The method according to any one of claims 9-12, characterized in that, The third field is protected by the MIC in the first MPDU.

14. The method according to any one of claims 1-8, characterized in that, Before obtaining the first MPDU, the method further includes: Send a fourth indication message; wherein the fourth indication message is used to indicate that the first field indicates the first time of the second MPDU, or the fourth indication message is used to indicate that the first field indicates the second time of the second MPDU.

15. The method according to claim 14, characterized in that, The fourth indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein, the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame is used to request to enable the function of the CCMP header field to carry the first field.

16. The method according to any one of claims 1-8, characterized in that, The first MPDU includes a fourth field; wherein the fourth field is used to indicate the identifier of the Stream Classification Service (SCS), and when the first MPDU includes the fourth field, the first field is used to indicate the first time of the second MPDU.

17. The method according to claim 16, characterized in that, The position of the fourth field in the first MPDU is predefined; or The position of the fourth field in the first MPDU is determined according to the fifth indication information; wherein the fifth indication information is used to indicate one or more of the following: the starting position of the fourth field in the first MPDU, the length of the fourth field, or the ending position of the fourth field in the first MPDU.

18. The method according to claim 17, characterized in that, The fifth indication information is located in one or more of the following: beacon frame, multicast frame, broadcast frame, capability information, or first request frame; wherein, the capability information is used to indicate support for the CCMP header field to carry the first field, and the first request frame is used to request to enable the function of the CCMP header field to carry the first field.

19. The method according to any one of claims 16-18, characterized in that, The fourth field is located in the MAC header field of the first MPDU; or The fourth field is located in the CCMP header field of the first MPDU.

20. The method according to any one of claims 16-19, characterized in that, The fourth field is protected by the MIC in the first MPDU.

21. The method according to any one of claims 1-20, characterized in that, Before obtaining the first MPDU, the method further includes: Send capability information; wherein the capability information is used to indicate that the CCMP header field supports carrying the first field.

22. The method according to any one of claims 1-21, characterized in that, Before obtaining the first MPDU, the method further includes: Send a first request frame; wherein the first request frame is used to request the enabling of the function of the CCMP header field carrying the first field; Receive a first response frame; wherein the first response frame is used to indicate agreement to enable the function of carrying the first field in the CCMP header field.

23. The method according to any one of claims 1-22, characterized in that, The transmitting device and the receiving device communicate through multiple links. The time corresponding to the first field is referenced to the time corresponding to the first link, and the first link is included in the multiple links. The identifier of the first link is the maximum or minimum value among the identifiers of the multiple links; or Send a sixth indication message; wherein the sixth indication message is used to indicate the identifier of the first link; or The TSF times corresponding to the multiple links are the same.

24. A communication method, characterized in that, include: Obtain a first Media Access Control (MAC) Protocol Data Unit (MPDU); wherein the first MPDU includes a Counter Mode Cipher Block Chaining Message Complete Code (CCMP) header field, the CCMP header field including a first field, the first field being used to indicate a first time of a second MPDU or a second time of the second MPDU; the first time of the second MPDU is the time when the second MPDU arrives at the Media Access Control (MAC) layer of the transmitting device, the second time of the second MPDU is the time when the transmitting device expects the second MPDU to arrive at the receiving device; the second MPDU is the first MPDU or the next MPDU of the first MPDU; Based on the first field, monitor the quality of service associated with the sending device.

25. The method according to claim 24, characterized in that, The first MPDU includes a fourth field; wherein the fourth field is used to indicate the identifier of the Stream Classification Service (SCS); Based on the fourth field, it is determined that the first field indicates the first time of the second MPDU.

26. The method according to claim 25, characterized in that, The second time of the second MPDU is determined based on the first time of the second MPDU and the delay limit corresponding to the identifier of the SCS.

27. The method according to any one of claims 24-26, characterized in that, Before obtaining the first MPDU, the method further includes: Receive fourth indication information; wherein, the fourth indication information is used to indicate that the first field indicates the first time of the second MPDU, or, the fourth indication information is used to indicate that the first field indicates the second time of the second MPDU; Based on the fourth indication information, it is determined that the first field indicates the first time of the second MPDU, or it is determined that the first field indicates the second time of the second MPDU.

28. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run computer programs or instructions, or to cause the communication device to perform the communication method as described in any one of claims 1-23, or to cause the communication device to perform the communication method as described in any one of claims 24-27, via logic circuitry.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the communication method as described in any one of claims 1-23, or cause the communication device to perform the communication method as described in any one of claims 24-27.

30. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are executed, they cause the communication method as described in any one of claims 1-23 to be executed, or cause the communication method as described in any one of claims 24-27 to be executed.

Images