Stream classification service-based communication method and apparatus - Patent Application 20070122997

Abstract

The stream classification service-based communication method and apparatus are applicable to wireless local area network systems supporting next-generation Wi-Fi protocols such as IEEE 802.11ax, for example, 802.11be, Wi-Fi 7, or EHT, or, for another example, 802.11 series protocols such as next-generation 802.11be protocols, Wi-Fi 8, or UHR, and may further be applied to UWB-based wireless personal area network systems, sensing systems, etc. The method includes a receiving end sending a measurement request and a transmitting end correspondingly receiving the measurement request, where the measurement request includes an identifier of a stream classification service SCS stream. The transmitting end sends a measurement report, and the receiving end correspondingly receives the measurement report, where the measurement report includes an identifier of the SCS stream and QoS measurement data of the SCS stream. The feedback granularity of the measurement report is effectively improved.

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present application relate to the field of communication technologies, and in particular to a stream classification service-based communication method and apparatus. [Background technology]

[0002] This application claims priority to Chinese Patent Application No. 202211202722.6, entitled "Stream Classification Service-Based Communication Method and Apparatus," filed with the State Intellectual Property Office of the People's Republic of China on September 29, 2022, which is incorporated herein by reference in its entirety.

[0003] With the development of mobile Internet and the widespread use of smart terminals, data traffic is increasing rapidly. Wireless local area network (WLAN) technology, with its advantages of high data rates and low costs, has become one of the mainstream mobile broadband access technologies.

[0004] The Institute of Electrical and Electronics Engineers (IEEE) 802.11 series is the main standard used for WLAN technology. As users increasingly demand higher quality of communication service, the IEEE 802.11be standard has emerged, which can meet user requirements in terms of high throughput, low jitter, low latency, etc. The IEEE 802.11be standard is also known as the extremely high throughput (EHT) standard. For example, the 802.11be standard may support a stream classification service (SCS) mechanism. Specifically, a station (STA) may negotiate quality of service (QoS) parameters for an SCS stream with an associated access point (AP). Furthermore, the STA may transmit data of the SCS stream with QoS requirements to the associated AP. After the STA sends a medium access control (MAC) service data unit (MSDU), the STA also needs to feed back a measurement report to the AP. However, there is a need to improve the feedback granularity of measurement reports. Summary of the Invention

[0005] The embodiments of the present application provide a stream classification service-based communication method and apparatus for effectively improving the feedback granularity of measurement reports. According to a first aspect, an embodiment of the present application provides a stream classification service-based communication method, the method comprising:

[0006] The method includes receiving a measurement request, the measurement request including an identifier of a stream classification service SCS stream, and sending a measurement report, the measurement report including an identifier of the SCS stream and quality of service (QoS) measurement data for the SCS stream.

[0007] In this embodiment of the present application, the measurement request and the measurement report include an identifier of the SCS stream, so that both communication parties can effectively know the SCS stream to which the measurement request and the measurement report are sent, and the feedback granularity of the measurement report can be effectively improved. Optionally, the receiving end can effectively optimize the QoS of the SCS stream based on the QoS of the SCS stream indicated by the measurement report, thereby performing optimization targeted at the QoS of the SCS stream. This not only improves the optimization efficiency, but also effectively improves the QoS of the SCS stream.

[0008] In a possible implementation, if the receiving end of the measurement report is a multi-link device (MLD), the measurement request includes the MLD medium access control MAC address.

[0009] For example, the MLD MAC address can be understood as the receiving end address of the measured MSDU. In this embodiment of the present application, if the receiving end of the measurement report is a multi-link device, the receiving end address is set to the MLD MAC address. Correspondingly, the transmitting end sends the MSDU on any link between the transmitting end and the multi-link device. In other words, the transmitting end can select more links to send the MSDU. For example, the transmitting end can send the MSDU on a link with good channel conditions to improve the flexibility of sending the MSDU by the transmitting end and increase throughput.

[0010] In a possible implementation, the information about the interface between the logic link control (LLC) layer and the MAC layer includes an identifier of the SCS stream.

[0011] In this embodiment of the present application, the interface information includes the SCSID of the SCS stream, so that the transmitting end can effectively know the SCSID corresponding to the MSDU sent by the transmitting end, or the SCSID to which the MSDU sent by the transmitting end belongs, which helps the transmitting end to collect statistics on the QoS measurement data of the SCS stream and determine whether it needs to discard the MSDU whose delay exceeds the delay bound.

[0012] In a possible implementation, the method further includes the step of the transmitting end performing packet discarding based on an identifier of the SCS stream and a QoS requirement of the SCS stream.

[0013] In this embodiment of the present application, the transmitting end performs packet discarding based on the identifier of the SCS stream and the QoS requirement of the SCS stream, effectively avoiding the case where the transmitting end continues to send the MSDU after the delay boundary is exceeded, which increases the transmission power consumption and wastes resources. Therefore, the interface information includes the SCSID of the MSDU, so that not only can the transmission power be saved, but also the sending resources and receiving resources of the receiving end can be effectively saved.

[0014] In a possible implementation, the method further comprises sending an SCS request, the SCS request comprising an identifier of the SCS stream and a QoS requirement for the SCS stream. In this embodiment of the present application, the transmitting end may negotiate QoS with the receiving end by using an SCS request. In a possible implementation, the QoS requirements include a delay bound and a MAC service data unit MSDU lifetime.

[0015] In a possible implementation, the method further includes the steps of sending a delay status report, where the delay status report indicates a remaining time for discarding MSDUs in a transmission queue for a TID corresponding to the SCS stream; receiving a trigger frame; and sending multiple SCS streams corresponding to the TID based on the trigger frame.

[0016] In this embodiment of the present application, the receiving end can know, based on the remaining time for discarding the MSDU, that the MSDU in the transmission queue of the TID may be discarded by the transmitting end within the remaining time, so that the receiving end can use the trigger frame to schedule the transmitting end to send the MSDU in the transmission queue of the TID, to avoid the case where the transmitting end discards the MSDU because the transmitting end does not send the MSDU in time.

[0017] In a possible implementation, the measurement request further includes a traffic identifier (TID) of the SCS stream, where the TID of the SCS stream is any value between 0 and 7.

[0018] It can be understood that the TID may be referred to as a traffic ID, or may be referred to as a traffic identifier, a communication identifier, etc. This is not limited in this embodiment of the present application.

[0019] In a possible implementation, the measurement report further includes at least one of first information and second information, where the first information indicates the number of MSDUs that have been successfully sent and acknowledged within the QoS requirements of the SCS stream, and the second information indicates the number of MSDUs that have been discarded within the SCS stream.

[0020] In this embodiment of the present application, statistics about the first information and the second information of the SCS stream are collected, so as to effectively improve the feedback granularity of the measurement report of the SCS stream. According to a second aspect, an embodiment of the present application provides a stream classification service-based communication method, the method comprising: sending a measurement request, the measurement request including an identifier of a stream classification service SCS;

[0021] receiving a measurement report, the measurement report including an identifier of the SCS stream and quality of service QoS measurement data for the SCS stream. In a possible implementation, if the receiving end of the measurement report is a multi-link device MLD, the measurement request includes the MLD medium access control MAC address.

[0022] In a possible implementation, the method further includes receiving a delay status report, the delay status report indicating a remaining time for discarding MSDUs in a transmission queue for a TID corresponding to the SCS stream, and sending a trigger frame based on the delay status report.

[0023] In a possible implementation, the measurement request further includes a traffic identifier TID of the SCS stream, where the traffic identifier TID of the SCS stream is any value between 0 and 7.

[0024] In a possible implementation, the measurement report further includes at least one of first information and second information, where the first information indicates the number of MAC service data units MSDUs that have been successfully sent and acknowledged within the QoS requirements of the SCS stream, and the second information indicates the number of discarded MSDUs in the SCS stream.

[0025] According to a third aspect, an embodiment of the present application provides a communication device configured to perform the method of the first aspect or any one of the possible implementations of the first aspect. The communication device includes a unit that performs the method of the first aspect or any one of the possible implementations of the first aspect. For example, the communication device may include a processing unit and a transceiver unit.

[0026] According to a fourth aspect, an embodiment of the present application provides a communication device configured to perform the method of the second aspect or any one of the possible implementations of the second aspect. The communication device includes a unit that performs the method of the second aspect or any one of the possible implementations of the second aspect. For example, the communication device may include a processing unit and a transceiver unit.

[0027] According to a fifth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to execute the method of the first aspect or any one of the possible implementations of the first aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method of the first aspect or any one of the possible implementations of the first aspect is performed. In a possible implementation, the memory is located outside the communication device. In a possible implementation, the memory is located inside the communication device.

[0028] In this embodiment of the present application, the processor and memory may alternatively be integrated into one device, i.e., the processor and memory may alternatively be integrated together. In a possible implementation, the communication device further includes a transceiver configured to receive signals and / or transmit signals.

[0029] According to a sixth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to execute the method of the second aspect or any one of the possible implementations of the second aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method of the second aspect or any one of the possible implementations of the second aspect is performed. In a possible implementation, the memory is located outside the communication device. In a possible implementation, the memory is located inside the communication device.

[0030] In this embodiment of the present application, the processor and memory may alternatively be integrated into one device, i.e., the processor and memory may alternatively be integrated together. In a possible implementation, the communication device further includes a transceiver configured to receive signals and / or transmit signals.

[0031] According to a seventh aspect, an embodiment of the present application provides a communication device, the communication device including a logic circuit and an interface, the logic circuit coupled to the interface, the logic circuit configured to input a measurement request via the interface and output a measurement report via the interface.

[0032] Optionally, the logic circuitry is specifically configured to analyze the measurement request when the measurement request is input via the interface. Optionally, the logic circuitry is configured to determine a measurement report based on the measurement request and output the measurement report via the interface. In a possible implementation, the logic circuitry is further configured to perform packet discarding based on an identifier of the SCS stream and a QoS requirement of the SCS stream. In a possible implementation, the interface is further configured to output an SCS request. Optionally, the logic circuitry is further configured to determine an SCS request and output the SCS request via the interface.

[0033] In a possible implementation, the interface is further configured to output a delay status report and input a trigger frame, and the logic circuit is further configured to send out MSDUs in the transmit queue of the TID based on the trigger frame. Optionally, the logic circuitry is further configured to determine a delay status report and output the delay status report via the interface.

[0034] It can be understood that the communication device in the seventh aspect can be a chip or a device including a chip. For a specific description of the seventh aspect, please refer to the first aspect.

[0035] According to an eighth aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface. The logic circuit is coupled to the interface, and the logic circuit is configured to output a measurement request via the interface. The interface is configured to input a measurement report. In a possible implementation, the interface is further configured to input a delay status report and to output a trigger frame. In a possible implementation, the interface is further configured to output an SCS request.

[0036] It can be understood that the communication device in the eighth aspect can be a chip or a device including a chip. For a specific description of the eighth aspect, please refer to the second aspect.

[0037] According to a ninth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, which, when run on a computer, performs the method of the first aspect or any one of the possible implementations of the first aspect.

[0038] According to a tenth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, which, when run on a computer, performs the method of the second aspect or any one of the possible implementations of the second aspect.

[0039] According to an eleventh aspect, an embodiment of the present application provides a computer program product, the computer program product including a computer program or computer code, which, when run on a computer, performs the method of the first aspect or any one of the possible implementations of the first aspect.

[0040] According to a twelfth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program or computer code, which, when run on a computer, performs the method of the second aspect or any one of the possible implementations of the second aspect.

[0041] According to a thirteenth aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the first aspect or any one of the possible implementations of the first aspect.

[0042] According to a fourteenth aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the second aspect or any one of the possible implementations of the second aspect.

[0043] According to a fifteenth aspect, an embodiment of the present application provides a communication system, the communication system including a transmitting end and a receiving end, the transmitting end configured to perform the method of the first aspect or any one of possible implementations of the first aspect, and the receiving end configured to perform the method of the second aspect or any one of possible implementations of the second aspect. [Brief explanation of the drawings]

[0044] [Figure 1] 1 is a diagram of the architecture of a communication system according to an embodiment of the present application; [Figure 2]FIG. 2 is a diagram of another communication system architecture according to an embodiment of the present application. [Figure 3] 1 is a diagram of a connection scheme between a multi-link AP and a multi-link STA according to an embodiment of the present application; [Figure 4] 1 is a schematic flowchart of a stream classification service-based communication method according to an embodiment of the present application; [Figure 5a] FIG. 2 is a diagram of a format of an SCS request according to an embodiment of the present application. [Figure 5b] FIG. 1 is a diagram of the format of an SCS descriptor element according to an embodiment of the present application. [Figure 5c] FIG. 1 is a diagram of an SCS response frame format according to an embodiment of the present application. [Figure 6a] FIG. 10 is a diagram of a measurement request format according to an embodiment of the present application. [Figure 6b] FIG. 1 is a diagram of a measurement report format according to an embodiment of the present application. [Figure 7] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 8] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 9] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0045] To make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described with reference to the accompanying drawings.

[0046] The terms "first," "second," etc. in the specification, claims, and accompanying drawings of this application are used merely to distinguish different objects and are not used to describe a particular order. In addition, terms such as "comprise" and "have," as well as any other variations thereof, are intended to include a non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but instead optionally includes further steps or units that are not listed, or optionally includes other steps or units that are inherent to those processes, methods, products, or devices.

[0047] The term "embodiment" in this specification means that a specific configuration, structure, or feature described in combination with an embodiment may be included in at least one embodiment of the present application. Phrases appearing in various places in this specification do not necessarily refer to the same embodiment, nor are they an embodiment that is independent or optional and exclusive of another embodiment. It may be explicitly or implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0048] In this application, "at least one" means one or more, "multiple" means two or more, "at least two" means two or more, and "and / or" is used to describe an associative relationship between related objects, indicating that three relationships may exist. For example, "A and / or B" may indicate three cases: only A is present, only B is present, or both A and B are present, where A and B may be singular or plural. "Or" indicates that two relationships may exist, e.g., only A is present or only B is present. If A and B are not mutually exclusive, it may indicate that three relationships exist, e.g., only A is present, only B is present, or both A and B are present. The character " / " typically indicates an "or" relationship between related objects. "At least one of the following items" or similar expressions means any combination of these items. For example, at least one of a, b, or c may represent a, b, c, "a and b," "a and c," "b and c," or "a and b and c."

[0049] The technical solutions provided in the embodiments of the present application may be applied to WLAN systems, such as Wi-Fi. For example, the methods provided in the embodiments of the present application are applicable to IEEE 802.11 series protocols, such as 802.11a / b / g protocol, 802.11n protocol, 802.11ac protocol, 802.11ax protocol, 802.11be protocol, or next-generation protocols. Examples are not listed herein. The technical solutions provided in the embodiments of the present application may further be applied to UWB technology-based wireless personal area networks (WPANs). For example, the methods provided in the embodiments of the present application are applicable to IEEE 802.15 series protocols, such as 802.15.4a protocol, 802.15.4z protocol, 802.15.4ab protocol, or future-generation UWB WPAN protocols. Examples are not listed herein. The technical solutions provided in the embodiments of the present application may be further applied to various other communication systems, such as, for example, internet of things (IoT) systems, vehicle to X (V2X) systems, and narrow band internet of things (NB-IoT) systems, and may be further applied to devices in the internet of things (IoT) of vehicles, internet of things nodes, sensors, etc., such as smart cameras, smart remote controls, and smart water / electricity meters in smart homes, sensors in smart cities, or may be further applied to long term evolution (LTE) systems, fifth-generation (5G) communication systems, new communication systems emerging in future communication developments, etc.

[0050] The embodiments of the present application primarily use WLANs, particularly networks conforming to the IEEE 802.11 series of standards, as illustrative examples, such as systems supporting Wi-Fi 7, which may also be referred to as "extremely high throughput (EHT)," and systems supporting Wi-Fi 8, which may also be referred to as "ultra high reliability (UHR)" or "ultra high reliability and throughput (UHRT)." Those skilled in the art will readily understand that various aspects of the embodiments of the present application can be extended to other networks using various standards or protocols, such as Bluetooth®, high performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard and primarily used in Europe), wide area networks (WANs), or other networks known or developed in the future. Therefore, regardless of the coverage area and wireless access protocol used, various aspects provided in the embodiments of the present application can be applied to any suitable wireless network.

[0051] The method provided in the embodiments of the present application may be implemented by a communication device in a wireless communication system, for example, the communication device may be an access point (AP) or a station (STA).

[0052] An access point is a device that has wireless communication capabilities, supports communication or sensing by using a WLAN protocol, and has the capability of communicating with or sensing other devices (e.g., stations or other access points) in a WLAN network. Of course, an access point may also have the capability of communicating with or sensing other devices. Alternatively, an access point corresponds to a bridge connecting a wired network and a wireless network. The main function of an access point is to connect various wireless network clients together and connect the wireless network to Ethernet. In a WLAN system, an access point may be referred to as an access point station (AP STA). A device with wireless communication capabilities may be an entire device, or a chip or processing system installed in the entire device. A device with a chip or processing system installed may implement the methods and functions in the embodiments of the present application under the control of the chip or processing system. An AP in the embodiments of the present application is a device that provides services to STAs and may support 802.11 series protocols, subsequent protocols, etc. For example, an access point may be an access point for terminals (e.g., mobile phones) to access a wired (or wireless) network, and is mainly deployed in homes, buildings, and campuses. A typical coverage radius is tens to hundreds of meters. Of course, the access point may alternatively be located outdoors. In another example, the AP may be a communication entity such as a communication server, a router, a switch, or a network bridge. The AP may include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP may alternatively be a chip and processing system in these various forms of devices to implement the methods and functions in the embodiments of the present application.

[0053] A station is a device with wireless communication capabilities, supports communication or sensing by using a WLAN protocol, and has the ability to communicate with or sense other stations or access points in a WLAN network. In a WLAN system, a station may be referred to as a non-access point station (non-AP STA). For example, a STA is any user communication device that allows a user to communicate with an AP or sense an AP to communicate with the WLAN. A device with wireless communication capabilities may be an entire device, or a chip or processing system installed in the entire device. Devices with these chips or processing systems may implement the methods and functions in the embodiments of the present application under the control of the chip or processing system. For example, a station may be a wireless communication chip, a wireless sensor, or a wireless communication terminal, and may also be referred to as a user. In another example, the station may be a mobile phone that supports Wi-Fi communication functionality, a tablet computer that supports Wi-Fi communication functionality, a set-top box that supports Wi-Fi communication functionality, a smart television that supports Wi-Fi communication functionality, a smart wearable device that supports Wi-Fi communication functionality, an in-vehicle communication device that supports Wi-Fi communication functionality, or a computer that supports Wi-Fi communication functionality.

[0054] WLAN systems can provide high-speed and low-latency transmission. With the continuous development of WLAN application scenarios, WLAN systems are expected to be applied to more scenarios and industries, such as the Internet of Things industry, vehicle-to-X industry, banking industry, corporate offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, shopping malls, supermarkets, squares, streets, workplaces, warehouses, etc. Of course, a device (e.g., an access point or station) supporting WLAN communication or sensing may be a sensor node in a smart city (e.g., a smart water meter, a smart electricity meter, or a smart air quality detection node), a smart device in a smart home (e.g., a smart camera, a projector, a display, a television, a speaker, a refrigerator, or a washing machine), a node in the Internet of Things, an entertainment terminal (e.g., a wearable device such as an augmented reality (AR) or virtual reality (VR) device), a smart device in a smart office (e.g., a printer, a projector, a loudspeaker, or a speaker), a vehicle-to-X device in a vehicle-to-X scenario, infrastructure in everyday life scenarios (e.g., a vending machine, a self-service navigation console in a shopping mall or supermarket, a self-service cash register device, or a self-service ordering machine), a device in a large stadium or music venue, etc. For example, the access point and station may be a device used in a vehicle-to-X scenario, an Internet of Things node or a sensor in the Internet of Things, a smart camera, a smart remote control, and a smart water or electricity meter in a smart home, or a sensor in a smart city, respectively. The specific forms of the STA and AP are not limited to the embodiments of the present application and are merely examples for the purposes of explanation herein.

[0055] For example, a communication system to which the methods provided in the embodiments of the present application can be applied may include an access point and a station. For example, the embodiments of the present application may be applicable to communication or sensing scenarios between an AP and a STA, between APs, or between STAs in a WLAN. This is not limited to the embodiments of the present application. Optionally, an AP may communicate with or sense a single STA, or an AP may communicate with or sense multiple STAs simultaneously. Specifically, communication or sensing between an AP and multiple STAs may be further divided into downlink transmissions in which the AP simultaneously sends signals to multiple STAs and uplink transmissions in which multiple STAs send signals to the AP. WLAN communication protocols may be supported between an AP and a STA, between APs, or between STAs. The communication protocols may include IEEE 802.11 series protocols, such as the 802.11be standard, and of course standards later than 802.11be.

[0056] FIG. 1 is a diagram of the architecture of a communication system according to an embodiment of the present application. The communication system may include one or more APs and one or more STAs. FIG. 1 shows two access points, such as AP1 and AP2, and three stations, such as STA1, STA2, and STA3. It can be understood that one or more APs may communicate with one or more STAs. Of course, APs may communicate with each other, and STAs may communicate with each other. The method provided in the embodiment of the present application is applicable to, but not limited to, single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X can represent everything), and device-to-device (D2D). For example, V2X may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communications.

[0057] It can be understood that in FIG. 1, an example is used in which the STA is a mobile phone and the AP is a router. This does not mean that the types of APs and STAs in the embodiment of the present application are limited. In addition, FIG. 1 only shows two APs and three STAs as an example. There may be more or less APs and STAs. This is not limited to the embodiment of the present application.

[0058] FIG. 2 is a diagram of another communication system architecture according to an embodiment of the present application. As shown in FIG. 2, the AP MLD includes AP1, AP2, and APn, and the non-AP MLD includes STA1, STA2, and STAn, where n is a positive integer. The AP MLD and the non-AP MLD may perform parallel communication on Link1, Link2, and Linkn. STA1 in the non-AP MLD establishes an association relationship with AP1 in the AP MLD. STA2 in the non-AP MLD establishes an association relationship with AP2 in the AP MLD. STAn in the non-AP MLD establishes an association relationship with APn in the AP MLD. Thus, one or more STAs in the non-AP MLD and one or more APs in the AP MLD can communicate after establishing association relationships. The frequency bands in which the multilink devices (including the AP MLD and the non-AP MLD) operate may include, but are not limited to, sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high-frequency 60 GHz.

[0059] A multilink device includes one or more affiliate stations. An affiliate station is a logical station and may operate on a link, frequency band, channel, etc. An affiliate station may be an AP or a non-AP STA. For ease of explanation, in the embodiments of the present application, a multilink device in which the affiliate station is an AP may be referred to as a multilink AP, a multilink AP device, or an AP multilink device (AP multi-link device, AP MLD), as shown in FIG. 2. A multilink device in which the affiliate station is a non-AP STA may be referred to as a multilink STA, a multilink STA device, or an STA multi-link device (STA multi-link device), as shown in FIG. 2, or a multilink device in which the affiliate station is a non-AP STA may be referred to as a multilink non-AP, a multilink non-AP device, or a non-AP multi-link device (non-AP MLD). A multilink device (which may be a non-AP MLD or AP MLD in this specification) is a communication device having wireless communication capabilities. The communication device may be an entire device, or may be a chip, a processing system, etc. installed in the entire device. The device in which the chip or processing system is installed may implement the methods and functions in the embodiments of the present application under the control of the chip or processing system. For a description of AP STA and non-AP STA, please refer to Figure 1. The details will not be described again here. FIG. 3 is a diagram of a connection scheme between a multi-link AP and a multi-link STA according to one embodiment of the present application.

[0060] As shown in FIG. 3, a multi-link AP may include a physical layer (PHY) processing circuit (PHY#1, PHY#2, and PHY#n shown in FIG. 3) and a medium access control (MAC) layer processing circuit. The physical layer processing circuit may be configured to process physical layer signals, and the MAC layer processing circuit may be configured to process MAC layer signals. Furthermore, the MAC layer may be further divided into one high-MAC layer (e.g., the high MAC shown in FIG. 3) and multiple low-MAC layers (e.g., the low MAC#1, low MAC#2, and low MAC#n shown in FIG. 3). The high MAC layer is separately connected to multiple low MAC layers. That is, the high MAC layer is shared by multiple links. The high MAC layer mainly completes assignment of sequence numbers (SN) and packet numbers (PN) of MAC service data units (MSDUs), encryption, decryption, etc. The low MAC layer mainly completes the assembly of MAC protocol data units (MPDUs), channel access, packet transmission, acknowledgment reception, etc. for each link. In FIG. 3, the PHY#1 layer, low MAC#1 layer, and high MAC layer in a multi-link AP may be regarded as AP#1, the PHY#2 layer, low MAC#2 layer, and high MAC layer may be regarded as AP#2, ..., the PHY#n layer, low MAC#n layer, and high MAC layer may be regarded as AP#n. That is, a multi-link AP may be understood to include N AP entities. A similar situation exists for a multi-link STA. Specifically, the high MAC layer in a multi-link STA is also shared by multiple links. The PHY#1 layer, low MAC#1 layer, and high MAC layer may be regarded as STA#1, the PHY#2 layer, low MAC#2 layer, and high MAC layer may be regarded as STA#2, ..., the PHY#n layer, low MAC#n layer, and high MAC layer may be regarded as STA#n. That is, a multi-link STA may be understood to include N STA entities.

[0061] As shown in Figure 3, PHY #1 of AP #1 in the multilink AP is connected to PHY #1 of STA #1 in the multilink STA, and AP #1 in the multilink AP communicates with STA #1 in the multilink STA via a link (e.g., link #1 shown in Figure 3). PHY #2 of AP #2 in the multilink AP is connected to PHY #2 of STA #2 in the multilink STA, and AP #2 in the multilink AP communicates with STA #2 in the multilink STA via a link (e.g., link #2 shown in Figure 3). PHY #n of AP #n in the multilink AP is connected to PHY #n of STA #n in the multilink STA, and AP #n in the multilink AP communicates with STA #n in the multilink STA via a link (e.g., link #n shown in Figure 3). It should be noted that FIG. 3 is just a simple diagram and does not constitute a limitation on the protection scope of the embodiments of the present application.

[0062] The TIDs can correspond to different traffic streams (TSs). For example, the length of a TID is 4 bits and the value ranges from 0 to 15. TIDs 8 to 15 can indicate traffic streams with QoS parameter requirements. For example, in an enhanced distributed channel access (EDCA) scenario, TIDs can be mapped to user priorities 0 to 7. The user priorities corresponding to TIDs 0 to 7 can be consecutively 0 to 7. For each TID from TID 0 to TID 7, multiple traffic streams are allowed to be mapped to one TID. For each TID from TID 8 to TID 15, typically, only one traffic stream can be mapped to one TID. It can be understood that the specific traffic streams mapped to one TID are not limited in the embodiments of the present application.

[0063] It should be noted that when multiple traffic streams are mapped to one TID, whether the QoS requirements of the multiple traffic streams are the same is not limited in the embodiments of the present application.

[0064] Generally, the allocation of sequence numbers (SNs) and the establishment of block acknowledgments (BAs) are based on the TID. Therefore, for traffic of the same TID, the transmitting end usually sends MSDUs according to the SN sequence. In other words, the MSDUs to be transmitted in the transmission queue of the TID are transmitted one by one according to the SN sequence. When the MSDUs are transmitted according to the SN sequence, the traffic stream identifiers corresponding to the MSDUs may be the same or different. For example, when multiple traffic streams are mapped to the same TID, the traffic stream identifiers corresponding to the MSDUs in the transmission queue of the TID may be different identifiers. Alternatively, the transmission queue of the TID may be understood to include MSDUs of multiple different traffic stream identifiers.

[0065] It should be understood that the length of the TID in the embodiments of the present application is merely an example. As standards develop, the length of the TID may become longer or shorter. This is not limited to the embodiments of the present application. Note that as long as the value range of the TID can allow multiple traffic streams to be mapped to one TID, it is within the scope of protection of the embodiments of the present application. For ease of explanation, the following describes the method provided in the embodiments of the present application by using an example in which the TID is 4 bits long and the stream classification service identifier (SCSID) of the traffic stream is 1 octet long. The 1-octet length of the SCSID and the 4-bit length of the TID are merely examples and should not be construed as limitations of the embodiments of the present application.

[0066] The traffic stream identifier in the embodiment of the present application is described by using the SCSID as an example, but it can be understood that this should not be construed as a limitation on the embodiment of the present application. The SCSID is described by using an example in which the identifier in the SCS request and the SCS response is consistent. However, the embodiment of the present application may not be limited thereto. For example, the traffic stream identifier may be another ID, and the another ID may have a correspondence with the SCSID in the SCS request and the SCS response.

[0067] Currently, when sending a measurement report, the transmitting end feeds back the measurement report at the granularity of a TID. However, one TID (e.g., TID0 to TID7) may correspond to multiple traffic streams. Therefore, in this way, the receiving end of the measurement report cannot obtain the QoS measurement data of the specific traffic stream for which the measurement report is intended.

[0068] In this regard, the embodiments of the present application provide a stream classification service-based communication method and apparatus, and when sending a measurement report, the transmitting end can perform feedback at the granularity of an SCS stream, so as to improve the accuracy of feeding back QoS measurement data.

[0069] FIG. 4 is a schematic flowchart of a stream classification service-based communication method according to an embodiment of the present application. This method may be applied to the communication system shown in FIG. 1, FIG. 2, or FIG. 3. This method may be applied to a transmitting end and a receiving end. The transmitting end may be understood as a communication device that sends a measurement report, a communication device that sends an SCS stream, or a communication device that sends an SCS request. The receiving end may be understood as a communication device that receives a measurement report, a communication device that receives an SCS stream, or a communication device that receives an SCS request. For example, the transmitting end may include a STA (including non-AP MLD), and the receiving end may include an AP (including AP MLD). In another example, both the transmitting end and the receiving end are STAs or APs. Whether there is another forwarding device between the transmitting end and the receiving end is not limited in this embodiment of the present application. For ease of explanation, the following uses an example in which the transmitting end is a STA and the receiving end is an AP. In a possible implementation, the method shown in FIG. 403: The transmitting end sends out an MSDU, and the receiving end receives the MSDU correspondingly.

[0070] For example, when multiple traffic streams are mapped to the same TID, a transmission queue at the transmitting end, corresponding to the TID, may include multiple traffic streams. Alternatively, a transmission queue at the transmitting end may include MSDUs of multiple traffic streams corresponding to the TID. When the transmitting end reports the QoS requirements of a traffic stream to the receiving end using the SCS mechanism, the traffic stream may be referred to as an SCS stream. An MSDU may be understood as a data packet of a traffic stream or an SCS stream. In general, a traffic stream may include multiple MSDUs. The number of MSDUs included in a traffic stream is not limited in this embodiment of the present application. The MSDUs in step 403 may also be collectively referred to as data, data packets, etc. The name of the MSDU is not limited in this embodiment of the present application.

[0071] In a possible implementation, the information about the interface between the LLC layer and the MAC layer includes an SCSID. For example, when sending an MSDU over the air interface, the transmitting end may determine whether to discard the MSDU based on the SCSID of the MSDU and at least one of the QoS requirements corresponding to the traffic stream, such as a delay bound, an MSDU lifetime, or a minimum remaining time for discard. For example, before sending the MSDU over the air interface, the transmitting end may determine the SCSID of the MSDU based on the information about the interface between the LLC layer and the MAC layer.

[0072] Generally, the interface information includes a TID. However, in this embodiment of the present application, in addition to the TID, the interface information may further include the SCSID of the corresponding traffic stream. The interface information includes the SCSID so that the transmitting end can effectively know the SCSID corresponding to the MSDU sent by the transmitting end or the SCSID to which the MSDU sent by the transmitting end belongs. This helps the transmitting end collect statistics on the QoS measurement data of the traffic stream and determine whether to discard an MSDU whose delay exceeds the corresponding delay limit, whether to discard an MSDU whose MSDU lifetime has expired, or whether to discard an MSDU whose minimum remaining time for discard has expired. For example, for low-latency traffic, the interface information includes the SCSID so that the transmitting end can effectively measure the QoS of the low-latency traffic in time and the receiving end can perform monitoring based on the QoS measurement report of the low-latency traffic. Therefore, if the QoS measurement data of the traffic stream does not meet certain requirements, the receiving end can take measures to improve the user's QoS. In the following, the interface information in this embodiment of the present application is used as an example.

[0073] For example, the interface information may include a primitive request between the LLC layer and the MAC layer, which may send an MSDU from a local LLC sublayer entity to a single peer LLC sublayer entity or bridge port, or to multiple peer LLC sublayer entities or bridge ports in the case of a group address (this primitive requests transfer of an MSDU from the local LLC sublayer entity to a single peer LLC sublayer entity or bridge port, or to multiple peer LLC sublayer entities or bridge ports in the case of a group address).

[0074] Optionally, the transmitting end may identify the corresponding MSDU based on a traffic filter (TCLAS filter) located above the MAC (e.g., located in the LLC) and map the MSDU to a specified TID and SCSID. The MSDU is then delivered from the LLC layer to the MAC layer via a MAC layer service access point (service access point, MAC-SAP) using a primitive request (e.g., an MA-UNITDATA.request primitive).

[0075] In one example, when an MSDU belongs to a traffic stream, the transmitting end may map the MSDU to a corresponding SCSID. For example, the SCSID may be a non-zero value. A traffic stream as described herein may be understood as an SCS stream corresponding to the SCSID carried when the transmitting end reports QoS requirements using an SCS request. Alternatively, a traffic stream as described herein may be understood as any one of multiple traffic streams corresponding to the TID of the MSDU. In another example, when an MSDU does not belong to any traffic stream, the transmitting end may set the SCSID of the MSDU to a reserved value. The reserved value may be 0. In this embodiment of the present application, an MSDU not belonging to any traffic stream may be understood as follows: That is, the MSDU does not belong to any SCS stream corresponding to the SCSID carried when the transmitting end reports QoS requirements using an SCS request, or the MSDU does not belong to any of the multiple traffic streams corresponding to the TID of the MSDU. The descriptions of a traffic stream and an MSDU not belonging to any traffic stream are also applicable hereinafter.

[0076] In one example, if the priority of an MSDU is a value from 0 to 7 and the MSDU does not belong to any traffic stream, the transmitting end may set the SCSID of the MSDU to a reserved value, which may be 0. In another example, if the priority of an MSDU is a value from 0 to 7 and the MSDU belongs to a traffic stream, the transmitting end may map the MSDU to a corresponding SCSID, for example, a non-zero value. It may be understood that based on the relationship between the priority and the TID, the priorities 0 to 7 in this embodiment of the present application may also be equivalent to TIDs 0 to 7. If the relationship between the priority and the TID changes, the priorities 0 to 7 are not equivalent to TIDs 0 to 7. In this case, this embodiment of the present application further provides the following implementation: That is, in one example, if the TID of an MSDU is a value from 0 to 7 and the MSDU does not belong to any traffic stream, the transmitting end may set the SCSID of the MSDU to a reserved value, which may be 0. In another example, if the priority of an MSDU is a value from 0 to 7 and the MSDU belongs to a traffic stream, the transmitting end may map the MSDU to a corresponding SCSID, for example, a non-zero value.

[0077] It can be appreciated that the above is illustrated by using an example in which multiple traffic streams may be mapped to the same TID when TIDs range from 0 to 7. Those skilled in the art can appreciate that if the length of the TID changes, for example, if multiple traffic streams are allowed to map to the same TID when TIDs range from 0 to 15, the TIDs 0 to 7 or priorities 0 to 7 in the above method may change accordingly. For example, the format of a primitive request may be shown as follows: MA-UNITDATA.request( source address, destination address, routing information, data, priority, SCSID, drop eligible, service class, Station vector, MSDU format )

[0078] "source address" represents the source address. "destination address" represents the destination address. "routing information" represents routing information. "data" represents data, i.e., MSDU. "priority" represents the priority or TID. "SCSID" represents the identifier of the traffic stream (including the SCS stream) corresponding to the MSDU. "drop eligible" represents whether dropping is allowed, and may be set based on the "drop eligibility" field of the "in-access category priority" element in the SCS request. "service class" represents the service class. "station vector" represents the station vector. "MSDU format" represents the MSDU format. By using the above primitive requests, the transmitting end can know whether the MSDU belongs to a traffic stream or does not belong to any traffic stream based on the SCSID of the MSDU. It may be understood that the above primitive requests are merely examples, and in particular implementations, the primitive requests may have more or less information than the above information.

[0079] Optionally, the transmitting end may perform packet discarding based on the SCSID and the QoS requirements corresponding to the SCSID. If the MSDU belongs to a traffic stream, the transmitting end may determine whether to discard the MSDU based on the drop eligibility and the QoS requirements of the SCS stream. Packet discarding may be understood as discarding an MSDU or discarding a data packet by the transmitting end at the MAC layer based on the SCSID and the QoS requirements corresponding to the SCSID. See Figure 5b for a description of the QoS requirements.

[0080] It should be noted that the interface information (including the primitive request) in this embodiment of the present application may be combined with Fig. 4 or may be an independent embodiment. For example, the relevant description of the interface information in this embodiment of the present application may be understood as a method for determining, by the transmitting end, the SCSID of an MSDU sent by the transmitting end based on the interface information, or a method for determining, by the transmitting end, the SCS stream (or traffic stream) to which the MSDU sent by the transmitting end belongs based on the interface information. Regarding how the transmitting end sends out the MSDU, this embodiment of the present application provides the following two examples. Example 1: 401: The sending end sends an SCS request, and the receiving end receives the SCS request in response.

[0081] For example, a STA may use the SCS mechanism to report a low-latency traffic stream to an AP. The SCS mechanism may be understood as follows: a STA may send an SCS request to an AP associated with the STA, report a low-latency traffic stream using the SCS request, and indicate corresponding QoS requirements (also referred to as QoS parameters). The SCS request may be referred to as an SCS request frame.

[0082] 5a is a diagram of the format of an SCS request according to one embodiment of the present application. As shown in FIG. 5a, the SCS request includes a category field, a robust action field, a dialog token field, and an SCS descriptor list field. For example, the category field may indicate a category to which an action frame (i.e., an SCS request frame) belongs. The robust action field may indicate a frame within the corresponding category to which an SCS request frame belongs. The dialog token field may be used to match corresponding SCS request and SCS response frames. The SCS descriptor list field may include one or more SCS descriptor elements, each of which may indicate relevant information of an SCS stream. Optionally, when multiple SCS streams are mapped to the same TID, the transmitting end may report the QoS requirements of the multiple SCS streams to the receiving end by sending multiple SCS requests, or the transmitting end may report the QoS requirements of the multiple SCS streams to the receiving end by using multiple SCS descriptor elements.

[0083] 5b is a diagram of the format of an SCS descriptor element according to one embodiment of the present application. For example, the SCS descriptor element may include at least one of an element ID field, a length field, an SCS identifier (SCSID) field, and a request type field. Optionally, the SCS descriptor element may further include at least one of an intra-access category priority element, a traffic classification (TCLAS, which may also be referred to as communications classification or business classification) element, a traffic classification processing element, a plurality of service quality characteristics elements, and other optional subelements. In this embodiment of the present application, there is no limitation as to whether the SCS descriptor element includes all of the in-access category priority element, the traffic classification element, the traffic classification processing element, and the service quality characteristic element, or whether the SCS descriptor element includes none of the in-access category priority element, the traffic classification element, the traffic classification processing element, and the service quality characteristic element. The display function for each octet or element is as follows: (1) The element identifier field identifies the SCS descriptor element. (2) The length field indicates the length of the SCS descriptor element. (3) The SCSID field is one octet and identifies the SCS stream. (4) The request type is one octet and indicates the type requested by the SCS request frame. The values ​​and indication functions of the request type can be seen in Table 1.

[0084] [Table 1]

[0085] (5) A specific format of the intra-access category priority element is shown in (a) of Figure 5b and includes an element ID field, a length field, and an intra-access priority field. The intra-access priority field may be one octet and may include at least one of a user priority field, an alternate queue field, a drop eligibility field, and an unused field.

[0086] (6) The TCLAS element indicates how to identify an SCS stream and carries criteria for determining the SCS stream. The TCLAS element may include at least one of an element ID field, a length field, a user priority field, and a frame classifier field. (7) The TCLAS processing element indicates how to process multiple TCLAS elements when multiple TCLAS elements exist.

[0087] (8) The QoS characteristic element indicates information such as the TID to which the corresponding SCS stream is mapped and the corresponding QoS parameters. For example, the QoS parameters may include a delay bound and an MSDU delivery ratio. The delay bound may indicate the maximum delay allowed by the SCS stream. The MSDU delivery ratio may indicate the packet delivery ratio required under a given delay bound requirement.

[0088] In this embodiment of the present application, the SCS descriptor element may carry a QoS characteristic element, and the SCS stream corresponding to the SCS descriptor element may be referred to as an SCS stream with parameterized QoS. When a QoS characteristic element is carried, it indicates that the transmitting end has QoS requirements for the corresponding SCS stream and needs to negotiate with the receiving end, or the receiving end needs to perform measures such as optimization and improvement based on the QoS measurement data of the SCS stream.

[0089] For example, as shown in (a) of FIG. 5b, the QoS characteristic element includes at least one of an element ID field, a length field, an element ID extension field, a control information field, a minimum service interval field, a maximum service interval field, a minimum data rate field, a delay bound field, a maximum MSDU size field, a service start time field, a mean data rate field, a burst size field, an MSDU lifetime field, an MSDU delivery ratio field, an MSDU count exponent field, a medium time field, and a bandwidth.

[0090] For example, as shown in (b) of Figure 5b, the control information field includes at least one of a direction field, a traffic identifier (TID) field, a user priority field, a presence bitmap of additional parameters, a link ID field, and a reserved field. Optionally, the TID in the control information may identify a traffic type, and the value of the TID ranges from 0 to 7, with 8 to 15 being reserved values. The value of the user priority ranges from 0 to 7, with 0 to 7 indicating user priority in ascending order. The user priority may be set to the same value as the TID field.

[0091] The QoS requirements of the SCS stream in this embodiment of the present application may include a delay bound and an MSDU lifetime as shown in Figure 5b. Optionally, the QoS requirements of the SCS stream may further include a minimum service interval, a maximum service interval, etc. Examples are not listed herein. 402: The receiving end sends an SCS response, and the transmitting end receives the SCS response accordingly.

[0092] For example, after receiving an SCS request frame, the AP may return an SCS response frame (response) to respond to the SCS request frame and indicate whether the SCS stream requested in the SCS request frame is acceptable. In other words, the STA and the AP associated with the STA may negotiate QoS parameters by using the SCS request frame and the SCS response frame so that the STA and the associated AP may transmit an SCS stream having QoS requirements.

[0093] 5c is a diagram of an SCS response frame format according to one embodiment of the present application. The SCS response frame includes at least one of a category field, a robust action field, a dialog token field, a count field, an SCS status list field, and an SCS descriptor list field. The content of the dialog token field in the SCS response frame matches the content of the dialog token field in the SCS request frame to which the SCS response frame responds. The SCS status list field may include one or more SCS status groups, and each SCS status group may include an SCSID and a status code. The SCSID identifies an SCS stream, and the status code indicates whether the requested SCS stream corresponding to the SCSID is accepted. If the status code indicates that the SCS stream is accepted, the QoS characteristics element field indicates the parameter information that needs to be used by the SCS stream. That is, the AP agrees to the STA's request, and the STA needs to take action based on the parameter information carried in the SCS response frame. Optionally, if the status code indicates a reject with suggested changes parameter, a field in the QoS characteristics element may carry parameter information suggested by the AP, and the STA may resume the SCS request based on the parameter information suggested by the AP. Alternatively, the STA may send an SCS stream based on the parameter information suggested by the AP. See Figure 5b for a description of the SCS descriptor element.

[0094] It should be understood that Figure 5c is described by using an example in which the SCS status list field includes one SCS status group, which is not limited in this embodiment of the present application.

[0095] 4 shows an example in which the transmitting end sends an SCS stream based on the SCS request and the SCS response. However, this should not be interpreted as a limitation on this embodiment of the present application. For example, after the transmitting end receives the SCS response, channel contention can be further performed. After the channel contention is successful, the transmitting end sends an SCS stream based on the SCS request and the SCS response. Example 2:

[0096] The transmitting end (e.g., non-AP MLD) sends a delay status report, and correspondingly, the receiving end (e.g., AP MLD) receives the delay status report. The receiving end (e.g., AP MLD) may send a trigger frame to the transmitting end based on the delay status report to schedule transmission of the transmitting end. Correspondingly, the transmitting end (e.g., non-AP MLD) receives the trigger frame and sends MSDUs in the transmission queue of the TID based on the trigger frame.

[0097] Optionally, the delay status report indicates the remaining time for discarding MSDUs in the transmission queue for the corresponding TID. In other words, the delay status report may indicate the delay requirement of MSDUs in the transmission queue for the TID. For example, the delay status report may be carried in an aggregated control (A-control) field, and the remaining time for discarding MSDUs in the transmission queue for the TID at the transmitting end is reported by using the A-control field. For example, the remaining time for discarding MSDUs may include the minimum remaining time for discarding MSDUs (also referred to as the minimum remaining time for discard or the earliest remaining time for discard). In this way, the receiving end can know, based on the minimum remaining time for discarding MSDUs, whether the MSDUs in the transmission queue for the TID can be discarded by the transmitting end within the remaining time. In this way, the receiving end can schedule the transmitting end to send the MSDUs in the transmission queue for the TID by using a trigger frame. Of course, the above-mentioned minimum remaining time is merely an example. If an MSDU of the SCS stream corresponding to the minimum remaining time is discarded after the transmitting end sends a delay status report and during the period of sending the SCS stream, the minimum remaining time may be replaced with another remaining time, for example, a second minimum remaining time. It may be understood that the second minimum remaining time in this specification is described with respect to the minimum remaining time.

[0098] Note that because one TID may correspond to multiple traffic streams and the delay bounds of the multiple traffic streams may differ, the minimum remaining time may not be the first data packet in the transmission queue for the TID. For example, the format of the A-control field may be shown in Table 2.

[0099] [Table 2]

[0100] If the minimum remaining time for discard is set to 0, it indicates that the MSDU in the transmission queue of the TID has already been discarded. The length of the minimum remaining time for discard in the A control field is not limited in this embodiment of the present application, and x in Table 2 may be a positive integer. The expected size of the transmission buffer in Table 2 may indicate the expected resource, and y may be a positive integer. The values ​​of x and y are not limited in this embodiment of the present application.

[0101] Optionally, the delay status report may indicate the time when discarding will occur in the transmission queue of the corresponding TID. For example, the time when discarding will occur may include the earliest time when discarding will occur or the minimum time synchronization function (TSF) value that exists when discarding will occur. By using the time when discarding will occur, the receiving end may know that packets in the transmission queue of the transmitting end have already been discarded. Therefore, the receiving end may use a trigger frame to trigger the transmitting end to send out MSDUs in the transmission queue of the corresponding TID in time.

[0102] It should be noted that Example 2 in this embodiment of the present application may be combined with FIG. 4 or may be an independent embodiment. For example, the aforementioned delayed status report may be a separate embodiment, or the delayed status report and the trigger frame may be combined in an embodiment. Examples are not listed in this embodiment of the present application. For example, the related description of the delayed status report in this embodiment of the present application may be understood as a method for the receiving end to determine that the transmitting end uses a trigger frame to send an MSDU based on the delayed status report, or a method for the transmitting end to send an MSDU based on the delayed status report. It may be understood that the transmitting end in the method shown in this specification is merely an example. For example, an embodiment combining the delayed status report and the trigger frame may be applied to the transmitting end and the receiving end. Please refer to Example 2 for a specific description.

[0103] Example 1 and Example 2 may be parallel technical solutions. For example, a STA establishes an SCS stream based on the SCS mechanism. In another example, the STA sends an uplink MSDU based on a trigger frame sent by an AP. Alternatively, Example 1 and Example 2 may be combined. For example, after establishing an SCS stream based on the SCS mechanism, the STA sends a delay status report and receives a trigger frame. Details will not be described again here. In other words, a transmitting end sends an SCS request, a receiving end correspondingly receives the SCS request, a receiving end sends an SCS response, and a transmitting end correspondingly receives the SCS response. The transmitting end sends a delay status report. The receiving end correspondingly receives the delay status report and sends a trigger frame. The transmitting end receives the trigger frame and sends an MSDU based on the trigger frame. For a specific description of the combination, please refer to Example 1 and Example 2. 404: The receiving end sends out a measurement request, and in response, the transmitting end receives the measurement request.

[0104] The measurement request includes the SCSID. In other words, the identifier included in the measurement request may identify a traffic stream. Alternatively, the receiving end may use the measurement request to request the transmitting end to feed back QoS measurement data of the traffic stream corresponding to the identifier. Optionally, the measurement request may further include the TID of the traffic stream, where the TID of the traffic stream is any value from 0 to 7.

[0105] For example, the measurement request may include an SCSID and a TID corresponding to the SCSID. Generally, it can be recognized that when the TID is any value from 0 to 7, multiple traffic streams may correspond to the same TID. Therefore, in this embodiment of the present application, the measurement request includes the SCSID, so that the transmitting end can effectively know that it needs to feedback QoS measurement data of the traffic stream corresponding to the SCSID. Compared with the technical solution in which the measurement request does not include the SCSID but includes the TID, the feedback granularity of the measurement report is effectively improved. In other words, compared with the measurement report at the granularity of the TID, the measurement report at the granularity of the traffic stream (including the SCS stream) in this embodiment of the present application effectively improves the feedback granularity of the measurement report, so that the receiving end can improve the QoS of the traffic stream. Particularly for low-latency services, the optimization efficiency of low-latency services is effectively improved.

[0106] For example, the measurement request may be referred to as a measurement request frame. Generally, the measurement request may include at least one of the following fields: a randomization interval, a measurement duration, a peer STA address, a TID, a histogram (bin) 0 range, and an optional subelement. Optional subelements in this embodiment of the present application may include a subelement indicating an SCSID. As shown in Figure 6a, the subelement may include a subelement identifier, a length, and an SCSID. The SCSID may identify a traffic stream.

[0107] The Randomization Interval field may indicate the maximum randomization delay at the start of measurements. The Measurement Period field may indicate the requested measurement period. If a trigger-based measurement request is established, the field may be set to 0.

[0108] The peer station address may indicate the receiving end address of the measured MSDU. Optionally, when the receiving end is an MLD, the receiving end address may include a multilink device MAC address (MLD MAC address). An MLD may have multiple auxiliary stations simultaneously, and the auxiliary stations may operate separately on different frequency bands / channels and receive and transmit data simultaneously. Therefore, in addition to the addresses of each auxiliary station (link MAC address), the MLD may also have an MLD MAC address. In this embodiment of the present application, if the receiving end is a multilink device, the receiving end address is set to the multilink MAC address. Correspondingly, the transmitting end transmits the MSDU on any link between the transmitting end and the multilink device. In other words, the transmitting end may select more links to transmit the MSDU. For example, the transmitting end may transmit the MSDU on a link with good channel conditions to improve the transmitting end's flexibility and increase throughput. The TID may indicate the corresponding traffic identifier of the measured MSDU. The Bin 0 Range may indicate the delay range of the first bin in the transmission delay histogram. It can be understood that the sequence and length of each field in the measurement request shown in FIG. 6a are not limited to this embodiment of the present application. 405: The transmitting end sends a measurement report, and the receiving end receives the measurement report in response.

[0109] The measurement report includes the SCSID and the QoS measurement data corresponding to the SCSID. The SCSID included in the measurement report is the same as the SCSID included in the measurement request. The measurement report may be referred to as a measurement report frame. It may be understood that the measurement request may be referred to as a category measurement request or a transmit stream, e.g., a transmit stream / category measurement request. The measurement response may be referred to as a category measurement response or a transmit stream, e.g., a transmit stream / category measurement report.

[0110] Optionally, the measurement report further includes at least one of first information and second information: the first information indicates the number of MSDUs that are successfully sent and confirmed within the QoS requirements of the traffic stream, e.g., the transmitted MSDU count shown in Fig. 6b; and the second information indicates the number of discarded MSDUs in the traffic stream, e.g., the discarded MSDU count shown in Fig. 6b. For example, the measurement report may include at least one of the following fields: (1) Element ID: Identifies the element that is the element. (2) Length: Indicates the number of octets occupied by the element. (3) Measurement token: Used to match a corresponding measurement request frame with a corresponding measurement response frame.

[0111] (4) Measurement report mode: Indicates the measurement report mode. The measurement request mode field may include at least one of the following: late: indicates that the station is unable to perform the measurement operation because the measurement request was received after the requested measurement time; inapable: indicates whether the station is unable to generate a measurement report; and refused: indicates whether the station refuses to generate a measurement report. A station in this specification may be understood as a transmitting end.

[0112] (5) Measurement type: Indicates whether the measurement report is a transmission stream / category measurement report or other measurement report. (6) Measurement report: Related statistical information of the measurement report. For example, the relevant statistical information of the measurement report may include at least one of the following fields:

[0113] (A) Actual measurement start time: For triggered measurement reports, the value of this field is the TSF value at the trigger moment. Optionally, when the receiving end is MLD, the actual measurement start time field can be set to the TSF value of the link from which the measurement report is sent, because the TSFs of the links may be different from each other.

[0114] (B) Measurement duration: In triggered transmission stream / category measurement reports, measurements are reported over multiple transmitted MSDUs rather than over one period, so the measurement duration is set to 0.

[0115] (C) Peer Station Address: Indicates the receiving end address of the MSDU. For the description of the receiving end address, please refer to the peer station address shown in Figure 6a. The details will not be described again here.

[0116] (D) TID: Contains a TID subfield, which indicates the traffic category (TC) or traffic stream (TS) of the measured traffic.

[0117] (E) Reporting reason: may include the following bits: Average Trigger: indicates that the measurement report was generated due to an average error trigger; Consecutive Trigger: indicates that the measurement report was generated due to a consecutive error trigger; Delay Trigger: indicates that the measurement report was generated because the delay exceeded the delay threshold.

[0118] (F) Transmitted MSDU count: Indicates the number of MSDUs of a traffic stream that are sent and acknowledged within the delay bounds.

[0119] (G) MSDU discarded count: Indicates the number of MSDUs discarded for a traffic stream when the delay bound, lifetime, or number of retries is exceeded.

[0120] Based on the description of the transmitted MSDU count and the MSDU discarded count in this embodiment of the present application, the corresponding MSDU delivery ratio may satisfy the formula: MSDU delivery ratio = transmitted MSDU count / (transmitted MSDU count + MSDU discarded count) × 100%. If the MSDU delivery ratio is smaller than the target value, the receiving end (e.g., AP MLD) may take measures to improve the current QoS of the TID or traffic stream.

[0121] (H) MSDU failed count: indicates the number of MSDUs that are discarded due to exceeding the number of retries for a traffic stream.

[0122] (I) MSDU multiple retry count: The number of MSDUs that are successfully transmitted and retransmitted multiple times.

[0123] (J) QoS Contention Free (CF)-polls Frame Lost Count: The number of times a CF-polls frame is lost.

[0124] (K) Average Queue Delay: The queue delay is the time that elapses between when the MAC receives an MSDU and when the MSDU begins transmission over the air interface.

[0125] (L) Average transmit delay: The transmit time is the elapsed time from when the MAC receives the MSDU until the MSDU is transmitted and acknowledged. Optionally, the average queue delay and the average transmit delay can be specific to a traffic stream. (M) Bin 0 range: Indicates the delay range of the first bin (Bin0) in the transmit delay histogram, shown as B0. (N) Bin 0: The quantity of MSDUs for which the delay is 0 <= delay < B0.

[0126] (O) Bin i: The quantity of MSDUs for which the delay is 2^(i - 1)*B0 <= delay < 2^i*B0, where i can be an integer, for example, i can be 4 or less (just an example).

[0127] (P) Sub - element: As shown in FIG. 6b, a sub - element can include a sub - element ID, length, and SCSID. The SCSID can identify an SCS stream. The SCSID is set to a non - zero value. It can be understood that the sequence and length of each field in the measurement request shown in FIG. 6a are not limited to this embodiment of the present application.

[0128] Optionally, both the measurement request and the measurement report may carry one SCSID. In other words, the measurement request is used to request QoS measurement data for one SCSID, and the measurement report is used to feedback QoS measurement data corresponding to the SCSID included in the measurement request. Optionally, the measurement request and the measurement report can further correspond to multiple SCSIDs. For example, the measurement request can include multiple sub - elements, and each sub - element can correspond to one SCSID. Correspondingly, the measurement report can include multiple measurement report fields, and each measurement report field can correspond to one SCSID. For example, the sequence of SCSIDs corresponding to multiple sub - elements within the measurement request can be the same as the sequence of SCSIDs corresponding to multiple measurement report fields within the measurement report.

[0129] It should be noted that the measurement request and measurement response in this embodiment of the present application may be an embodiment, or the measurement request, measurement response, and interface information may be combined into an embodiment, or the measurement request, measurement response, and SCS mechanism may be combined into an embodiment, or the measurement request, measurement response, delay status report, and trigger frame may be combined into an embodiment, or the measurement request, measurement response, SCS request, SCS response, and interface information may be combined into an embodiment, or the measurement request, measurement response, SCS request, SCS response, interface information, delay status report, and trigger frame may be combined into an embodiment. For specific descriptions of the embodiments described herein, please refer to the preceding description. The details will not be described again here.

[0130] In this embodiment of the present application, the measurement request and the measurement report include an identifier of the SCS stream, so that both communication parties can effectively know the SCS stream to which the measurement request and the measurement report are sent, and effectively improve the feedback granularity of the measurement report. Optionally, the receiving end may effectively optimize the QoS of the SCS stream based on the QoS of the SCS stream indicated by the measurement report, thereby performing optimization targeted at the QoS of the SCS stream. This not only improves the optimization efficiency, but also effectively improves the QoS of the SCS stream. A communication device provided in one embodiment of the present application is described below.

[0131] In the present application, the communication device is divided into functional modules based on the embodiment of the aforementioned method. For example, each functional module may be divided into corresponding functions, or two or more functions may be integrated into one processing module. The integrated unit may be implemented in the form of hardware or in the form of a software module unit. It should be noted that in the present application, the division into modules is merely an example and is merely a logical division of functions. In actual implementation, other division methods may be used. Below, the communication device in the embodiment of the present application will be described in detail with reference to Figures 7 to 9.

[0132] 7 is a diagram of the structure of a communication device according to an embodiment of the present application. As shown in FIG. 7, the communication device includes: a processing unit 701 and a transceiver unit 702.

[0133] In some embodiments of the present application, the communication device may be the above-mentioned transmitting end or chip, and the chip may be located at the transmitting end, i.e., the communication device may be configured to perform the steps, functions, etc. performed by the transmitting end of the aforementioned method embodiments (including FIG. 4). The transceiver unit 702 is configured to receive measurement requests and send measurement reports.

[0134] For example, the transceiver unit 702 may be configured to send a measurement report using the processing unit 701. For example, the processing unit 701 may be configured to determine a measurement report and then send the measurement report via the transceiver unit 702. For example, after the transceiver unit 702 receives a measurement request, the processing unit 701 may further analyze or process the measurement request. In a possible implementation, the processing unit 701 is further configured to perform packet discarding based on the SCSID and the QoS requirements of the SCSID. In a possible implementation, the transceiver unit 702 is further configured to send an SCS request.

[0135] In a possible implementation, the transceiver unit 702 is further configured to send a delay status report and receive a trigger frame, and the processing unit 701 is further configured to send an MSDU in a transmission queue for the TID based on the trigger frame.

[0136] In some embodiments of the present application, the communication device may be the receiving end or the chip described above, and the chip may be located at the receiving end, i.e., the communication device may be configured to perform the steps, functions, etc. performed by the receiving end of the aforementioned method embodiments (including FIG. 4). The transceiver unit 702 is configured to send measurement requests and receive measurement reports.

[0137] It may be understood that the processing unit 701 may be configured to determine a measurement request and then send the measurement request via the transceiver unit 702. For example, the processing unit 701 is further configured to process a measurement report. In a possible implementation, the transceiver unit 702 is further configured to receive an SCS request. In a possible implementation, the transceiver unit 702 is further configured to receive a delay status report and to send out a trigger frame.

[0138] It can be understood that the specific descriptions of the transceiver unit and the processing unit described in this embodiment of the present application are merely examples. For the specific functions, steps, etc. performed by the transceiver unit and the processing unit, please refer to the aforementioned method embodiments. The details will not be described again here.

[0139] In the above embodiment, for the description of the SCSID, QoS requirement, TID, traffic stream, MSDU, delay status report, measurement request, and measurement response, please refer to the description in the above method embodiment, and the details will not be described again here.

[0140] The above describes a communication device in an embodiment of the present application. The following describes possible product forms of the communication device. It should be understood that any product having the functions of the communication device of FIG. 7 falls within the scope of protection of the embodiment of the present application. It should be further understood that the following description is merely an example, and the product form of the communication device in the embodiment of the present application is not limited thereto.

[0141] In a possible implementation, in the communication device shown in FIG. 7, the processing unit 701 may be one or more processors. The transceiver unit 702 may be a transceiver. Alternatively, the transceiver unit 702 may be a transmitting unit and a receiving unit. The transmitting unit may be a transmitter, the receiving unit may be a receiver, or the transmitting unit and the receiving unit may be integrated into one component, such as a transceiver. In this embodiment of the present application, the processor and the transceiver may be combined, etc. The manner of connection between the processor and the transceiver is not limited to this embodiment of the present application. In the process of executing the above-mentioned method, the process of sending information in the above-mentioned method may be understood as the process of outputting information by the processor. When outputting the information, the processor outputs the information to the transceiver so that the transceiver transmits the information. After the information is output by the processor, other processing may need to be performed on the information before it arrives at the transceiver. Similarly, the process of receiving information in the above-mentioned method may be understood as the process of receiving input information by the processor. When the processor receives input information, the transceiver receives the information and inputs the information to the processor. Furthermore, after the transceiver receives the information, other processing needs to be performed on the information, and then the processed information is input to the processor. As shown in FIG. 8, the communications device 80 includes one or more processors 820 and a transceiver 810 .

[0142] In some embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the transmitting end of the aforementioned method embodiments (including FIG. 4). The transceiver 810 is configured to receive measurement requests and send measurement reports.

[0143] For example, the transceiver 810 may be configured to send a measurement report using the processor 820. For example, the processor 820 may be configured to determine a measurement report and then send the measurement report via the transceiver 810. For example, after the transceiver 810 receives a measurement request, the processor 820 may further analyze or process the measurement request. In a possible implementation, the processor 820 is further configured to perform packet discarding based on the SCSID and the QoS requirements of the SCSID. In a possible implementation, the transceiver 810 is further configured to send an SCS request.

[0144] In a possible implementation, the transceiver 810 is further configured to send a delay status report and receive a trigger frame, and the processor 820 is further configured to send an MSDU in a transmission queue for the TID based on the trigger frame.

[0145] In some embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end of the aforementioned method embodiments (including FIG. 4). The transceiver 810 is configured to send measurement requests and receive measurement reports.

[0146] It may be appreciated that the processor 820 may be configured to determine a measurement request and then send the measurement request via the transceiver 810. For example, the processor 820 may be further configured to process the measurement report. In a possible implementation, the transceiver 810 is further configured to receive an SCS request. In a possible implementation, the transceiver 810 is further configured to receive a delay status report and send a trigger frame.

[0147] It can be understood that the specific descriptions of the transceiver and the processor described in this embodiment of the present application are merely examples. For the specific functions, steps, etc. performed by the transceiver unit and the processing unit, please refer to the aforementioned method embodiments. The details will not be described again here.

[0148] In the above embodiment, for the description of the SCSID, QoS requirement, TID, traffic stream, MSDU, delay status report, measurement request, and measurement response, please refer to the description in the above method embodiment, and the details will not be described again here.

[0149] In each implementation of the communication apparatus shown in Figure 8, the transceiver may include a receiver and a transmitter. The receiver is configured to perform receiving functions (or operations), and the transmitter is configured to perform transmitting functions (or operations). The transceiver is configured to communicate with another device / apparatus over a transmission medium.

[0150] Optionally, the communication device 80 may further include one or more memories 830 configured to store program instructions, data, etc. The memory 830 is coupled to the processor 820. A coupling in this embodiment of the present application may be an indirect coupling or communication connection between devices in an electrical, mechanical, or other form, used for exchanging information between devices, units, or modules. The processor 820 may cooperate with the memory 830. The processor 820 may execute program instructions stored in the memory 830. Optionally, at least one of the one or more memories may be included in the processor.

[0151] In this embodiment of the present application, the specific connection medium between the transceiver 810, the processor 820, and the memory 830 is not limited. In this embodiment of the present application, in FIG. 8, the memory 830, the processor 820, and the transceiver 810 are connected to each other by using a bus 840. The bus is represented using thick lines in FIG. 8. The manner of connection between the other components is only described schematically and is not used as a limitation. The bus may be categorized as an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used to represent the bus system in FIG. 8, but this does not mean that there is only one bus or only one type of bus.

[0152] In this embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The processor may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in connection with the embodiments of the present application may be implemented directly by a hardware processor, or may be implemented by using a combination of hardware modules and software modules in the processor, etc.

[0153] In this embodiment of the present application, the memory may include, but is not limited to, a hard disk drive (HDD) or solid-state drive (SSD), a random access memory (RAM), an erasable programmable read-only memory (EPROM), a read-only memory (ROM), or a non-volatile memory such as a portable read-only memory (CD-ROM). The memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures and that can be read and / or written by a computer (e.g., a communication device of the present application). However, the present application is not limited thereto. The memory in the embodiment of the present application may alternatively be a circuit or any other device capable of implementing a storage function and configured to store program instructions and / or data.

[0154] For example, the processor 820 is primarily configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data of the software programs. The memory 830 is primarily configured to store software programs and data. The transceiver 810 may include a control circuit and an antenna. The control circuit is primarily configured to convert between baseband signals and radio frequency signals and process the radio frequency signals. The antenna is primarily configured to receive and transmit radio frequency signals in the form of electromagnetic waves. An input / output device, such as a touchscreen, display, or keyboard, is primarily configured to receive data input by a user and output data to the user.

[0155] After the communication device is powered on, the processor 820 can read the software program in the memory 830, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 820 performs baseband processing on the data to be transmitted and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs high frequency processing on the baseband signal and then transmits the radio frequency signal in the form of electromagnetic waves via an antenna. When data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal via the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 820. The processor 820 converts the baseband signal into data and processes the data.

[0156] In another implementation, the radio frequency circuitry and antenna may be located independently of the processor that performs the baseband processing, e.g., in a distributed scenario, the radio frequency circuitry and antenna may be located independently and remotely from the communication device.

[0157] It can be understood that the communication device described in this embodiment of the present application may further have more components than those in FIG. 8 and the like. This is not limited in this embodiment of the present application. The method performed by the processor and the transceiver is merely an example. Please refer to the above method for specific steps performed by the processor and the transceiver.

[0158] In another possible implementation, in the communication device shown in FIG. 7, the processing unit 701 may be one or more logic circuits. The transceiver unit 702 may be an input / output interface, also referred to as a communication interface, an interface circuit, an interface, etc. Alternatively, the transceiver unit 702 may be a transmitting unit and a receiving unit, where the transmitting unit may be an output interface and the receiving unit may be an input interface, and the transmitting unit and the receiving unit are integrated into one unit, e.g., an input / output interface. As shown in FIG. 9, the communication device shown in FIG. 9 includes a logic circuit 901 and an interface 902. In other words, the processing unit 701 may be implemented by using the logic circuit 901, and the transceiver unit 702 may be implemented by using the interface 902. The logic circuit 901 may be a chip, a processing circuit, an integrated circuit, a system-on-chip (SoC) chip, etc. The interface 902 may be a communication interface, an input / output interface, a pin, etc. For example, FIG. 9 illustrates an example in which the communication device is a chip. The chip includes a logic circuit 901 and an interface 902 .

[0159] In this embodiment of the present application, the logic circuit and the interface may be coupled to each other, and the specific connection method between the logic circuit and the interface is not limited to this embodiment of the present application.

[0160] In some embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end of the aforementioned method embodiments (including FIG. 4). The logic circuit 901 is configured to input a measurement request via an interface 902 and output a measurement report via the interface 902 .

[0161] Optionally, the logic circuitry is specifically configured to analyze the measurement request when the measurement request is input via the interface. Optionally, the logic circuitry is configured to determine a measurement report based on the measurement request and output the measurement report via the interface.

[0162] In a possible implementation, the logic circuitry 901 is further configured to perform packet discarding based on an identifier of the SCS stream and a QoS requirement of the SCS stream. In a possible implementation, the interface 902 is further configured to output an SCS request. Optionally, the logic circuitry is further configured to determine an SCS request and output the SCS request via the interface.

[0163] In a possible implementation, the interface 902 is further configured to output a delay status report and input a trigger frame, and the logic circuit 901 is further configured to send out an MSDU in the transmission queue of the TID based on the trigger frame.

[0164] In some embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the transmitting end of the aforementioned method embodiments (including FIG. 4). The logic circuit 901 is configured to output a measurement request via an interface 902. The interface 902 is configured to input a measurement report. In a possible implementation, the interface is further configured to input a delay status report and to output a trigger frame. In a possible implementation, the interface 902 is further configured to output an SCS request.

[0165] It can be understood that the specific description of the logic circuit and the interface in this embodiment of the present application is merely an example. For the specific functions, steps, etc. performed by the logic circuit and the interface, please refer to the aforementioned method embodiment. The details will not be described again here.

[0166] In the above embodiment, for the description of the SCSID, QoS requirement, TID, traffic stream, MSDU, delay status report, measurement request, and measurement response, please refer to the description in the above method embodiment, and the details will not be described again here.

[0167] It can be understood that the communication device described in this embodiment of the present application may implement the methods provided in the embodiments of the present application in the form of hardware, or may implement the methods provided in the embodiments of the present application in the form of software, which is not limited to this embodiment of the present application.

[0168] An embodiment of the present application further provides a wireless communication system, which includes a transmitting end and a receiving end, and the transmitting end and the receiving end can be configured to perform the method in any one of the above-mentioned embodiments (as shown in FIG. 4).

[0169] In addition, the present application further provides a computer program, which is used to implement the actions and / or processes performed by the transmitting end in the methods provided in the present application.

[0170] The present application further provides a computer program, which can be used to implement the actions and / or processes performed by the receiving end in the methods provided herein.

[0171] An embodiment of the present application further provides a computer-readable storage medium, which stores computer code, which, when executed on a computer, enables the computer to perform the operations and / or processes performed by the transmitting end in the methods provided herein.

[0172] An embodiment of the present application further provides a computer-readable storage medium, which stores computer code, which, when executed on a computer, enables the computer to perform the operations and / or processes performed by the receiving end in the methods provided herein.

[0173] The present application further provides a computer program product, which includes computer code or a computer program, which, when executed on a computer, performs the operations and / or processes performed by the transmitting end in the methods provided herein.

[0174] The present application further provides a computer program product, which includes computer code or a computer program, which, when executed on a computer, performs the operations and / or processes performed by the receiving end in the methods provided herein.

[0175] In some embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a division of logical functions, and actual implementation may involve other divisions. For example, multiple units or components may be combined or integrated into another system, or some functions may be ignored or not performed. Furthermore, the shown or described mutual couplings or direct couplings or communication connections may be implemented through some interfaces, indirect couplings or communication connections between devices or units, or other forms of electrical, mechanical, or connection.

[0176] Units described as separate parts may or may not be physically separated, and parts shown as units may or may not be physical units, and may be located in one location or distributed over multiple network units. Some or all of the units may be selected based on actual requirements for implementing the technical effects of the solutions provided in the embodiments of the present application.

[0177] Furthermore, the functional units in the embodiments of the present application may be integrated into one processing unit, each unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

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

[0179] The above description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any modifications or replacements that are easily understood by those skilled in the art within the technical scope disclosed in the present application shall be included in the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. A stream classification service based communication method, comprising: receiving a measurement request, the measurement request including an identifier of a Stream Classification Service (SCS) stream; sending a measurement report, said measurement report including said identifier of said SCS stream and quality of service measurement data of said SCS stream; A method comprising:

2. The method of claim 1 , wherein when the receiving end of the measurement report is a multi-link device MLD, the measurement request includes an MLD medium access control MAC address.

3. 3. The method of claim 1, wherein the information about the interface between the Logical Link Control LLC layer and the MAC layer includes the identifier of the SCS stream.

4. The method of claim 1 , further comprising the step of performing, by the transmitting end, packet discarding based on the identifier of the SCS stream and QoS requirements of the SCS stream.

5. The method of claim 1 , further comprising the step of sending an SCS request, wherein the SCS request includes the identifier of the SCS stream and the QoS requirements of the SCS stream.

6. The method according to claim 4 or 5, wherein the QoS requirements include a delay bound and a MAC Service Data Unit (MSDU) lifetime.

7. sending a delay status report, the delay status report indicating the remaining time for discarding MSDUs in a transmission queue for a TID corresponding to the SCS stream; receiving a trigger frame and transmitting a plurality of SCS streams corresponding to the TID based on the trigger frame; 7. The method of claim 1, further comprising:

8. The method of claim 1 , wherein the measurement request further comprises a traffic identifier TID of the SCS stream, the TID being any value between 0 and 7.

9. 9. The method of claim 1, wherein the measurement report further includes at least one of first information and second information, wherein the first information indicates a number of MSDUs that were successfully sent and acknowledged within the QoS requirements of the SCS stream, and the second information indicates a number of MSDUs that were discarded within the SCS stream.

10. A stream classification service based communication method, comprising: receiving a measurement request, said measurement request including an identifier of a stream classification service SCS; receiving a measurement report, the measurement report including the identifier of the SCS stream and quality of service measurement data for the SCS stream; A method comprising:

11. The method of claim 10, wherein when the receiving end of the measurement report is a multi-link device MLD, the measurement request includes an MLD medium access control MAC address.

12. receiving a delay status report, the delay status report indicating the remaining time for discarding MSDUs in a transmit queue for a TID corresponding to the SCS stream; sending a trigger frame based on the delay status report; 12. The method of claim 10 or 11, comprising:

13. The method of claim 10 , wherein the measurement request further includes a traffic identifier TID of the SCS stream, and the traffic identifier TID of the SCS stream is any value from 0 to 7.

14. 14. The method of claim 10, wherein the measurement report further includes at least one of first information and second information, wherein the first information indicates a quantity of MAC Service Data Units (MSDUs) successfully sent and acknowledged within the QoS requirements of the SCS stream, and the second information indicates a quantity of discarded MSDUs in the SCS stream.

15. A communication device comprising a unit configured to perform the method according to any one of claims 1 to 14.

16. A communication device comprising a processor and a memory, the memory configured to store instructions; A communications device, wherein the processor is configured to execute the instructions and to perform the method of any one of claims 1 to 14.

17. A communications device comprising a logic circuit and an interface, the logic circuit coupled to the interface; A communications device, wherein the interface is configured to input and / or output code instructions and the logic circuit is configured to execute the code instructions, such that the method of any one of claims 1 to 14 is performed.

18. 15. A computer readable storage medium configured to store a computer program which, when executed, performs the method of any one of claims 1 to 14.

19. A computer program which, when executed, performs the method of any one of claims 1 to 14.

20. A communication system comprising a transmitting end and a receiving end, the transmitting end configured to perform the method of any one of claims 1 to 9, and the receiving end configured to perform the method of any one of claims 10 to 14.

Images