WO2025147815A1 - Communication method for integrated reporting of service data and buffer state report, and related apparatus - Google Patents

Abstract

Embodiments of the present application relate to the field of communications, and in particular, to a communication method for integrated reporting of service data and a buffer status report and a related apparatus, which can be applied to a sensing system, and can also be applied to a system conforming to IEEE 802.11 system standards, such as 802.11bf, 802.11ax, 802.11be, or next-generation standards, or a wireless personal area network system based on ultra-wideband (UWB). The method comprises: a first device receives a first frame from a second device, the first frame comprising a first field and a second field. The first field indicates a first resource unit (RU) for the first device to report a buffer status report (BSR), and the second field indicates a second RU for the first device to report data. According to the communication method provided by the embodiments of the present application, service delay can be reduced.

Description

Communication method and related device for integrated reporting of business data and cache status report Technical Field

The present application relates to the field of wireless communication technology, and in particular to a communication method and related device for integrated reporting of service data and cache status report.

Background Art

The access point (AP) can use orthogonal frequency division multiple access (OFDMA) technology to divide the channel into multiple resource blocks (resource units, RU). Different stations (STA) can occupy different resource blocks, so that multi-user transmission can be performed in parallel.

In the OFDMA mechanism, the AP needs to allocate RUs used by the STA according to the buffer status of the STA. Specifically, before scheduling the STA each time, the AP sends a buffer status report query (Buffer Status Report Poll, BSRP) message to the STA. In response to the BSRP message, the STA sends a buffer status report (Buffer Status Report, BSR) to the AP so that the AP can allocate RUs to multiple STAs according to the BSR. In other words, before scheduling the STA each time, the AP needs to obtain the BSR from the STA through an additional control frame (for example, BSRP) to determine whether the STA needs to be scheduled to report data, thereby increasing the service delay. Therefore, how to reduce the service delay is a problem that needs to be solved.

Summary of the invention

The embodiments of the present application provide a communication method and related devices for integrated reporting of service data and cache status reports, which can reduce service delays.

In a first aspect, an embodiment of the present application provides a communication method for integrated reporting of business data and a cache status report, and the communication method can be applied to a first device, or to a module (for example, a chip or a processor) in the first device, or to a logic module or software that can implement all or part of the functions of the first device. The following description is made using the first device as an example in which the execution subject is an example. The communication method includes: a first device receives a first frame from a second device, the first frame includes a first field and a second field, the first field indicates a first resource block RU of a cache status report BSR reported by the first device, and the second field indicates a second RU of data reported by the first device.

In an embodiment of the present application, by indicating the RU (such as the second RU in the text) that reports data of the first device, the first device can be scheduled to report data through the RU that reports data. By indicating the RU (such as the first RU in the text) that reports the BSR of the first device, the first device can be scheduled to report the BSR through the RU that reports the BSR. For example, when the first device has service data to report but is not scheduled to report data, it can select a first RU to report the BSR based on the received first frame, so that in the next round of scheduling, it can have the opportunity to be scheduled to report data without sending an additional BSR to the second device before being scheduled to report data to obtain the opportunity to report data. The first device can report the BSR in a timely manner even when it is not scheduled to report data, so that it is convenient to be directly scheduled to report data, thereby reducing service latency.

In a possible implementation method, the method also includes: reporting a second frame based on the first frame, the second frame including a BSR; receiving a third frame, the third frame including a third field and a fourth field, the third field indicating a first RU of a next round of BSR reporting by the first device, and the fourth field indicating a second RU of a next round of data reporting by the first device.

A possible implementation method is to report a second frame based on the first frame, and the second frame includes a BSR, including: determining to report the second frame in a second RU based on the first frame, and the second frame also includes data; or, determining to report the second frame in a corresponding first RU based on the first frame; or, determining to report the second frame in a random first RU based on the first frame.

In a possible implementation manner, the method further includes: receiving a fourth frame, where the fourth frame includes a fifth field, and the fifth field indicates a second RU of a last round of data reporting by the first device.

In a possible implementation, the second field includes a first subfield, and the first subfield indicates whether the second frame uploaded by the first device carries the BSR or does not indicate whether the BSR is carried.

In a possible implementation manner, the second field also includes a user information field related to the trigger frame, and the user information field related to the trigger frame includes the first subfield.

In a possible implementation manner, the first frame further includes a sixth field, and the sixth field indicates whether the first frame carries block acknowledgement BA information.

In a possible implementation, the first frame further includes a common information field related to the trigger frame, and the common information field related to the trigger frame The sixth field is included.

In a possible implementation, when the sixth field indicates that the first frame carries BA information, the first frame further includes a seventh field, and the seventh field indicates a location of the BA information.

In a possible implementation manner, the first frame is a trigger frame, and the second frame is a data frame.

In the second aspect, the embodiments of the present application provide a communication method and related apparatus for integrated reporting of business data and cache status report, and the communication method can be applied to a second device, or to a module (for example, a chip or a processor) in the second device, or to a logic module or software that can implement all or part of the functions of the second device. The following description is made using the second device as an example in which the execution subject is an example. The communication method includes: sending a first frame, the first frame including a first field and a second field, the first field indicating a first resource block RU of a cache status report BSR reported by the first device, and the second field indicating a second RU of data reported by the first device.

In an embodiment of the present application, by indicating the RU (such as the second RU in the text) that reports data of the first device, the first device can be scheduled to report data through the RU that reports data. By indicating the RU (such as the first RU in the text) that reports the BSR of the first device, the first device can report the BSR through the RU that reports the BSR. For example, when the first device has service data that needs to be reported but is not scheduled to report data, it can select a first RU to report the BSR based on the received first frame, so that in the next round of scheduling, the second device can schedule the first device that reported the BSR through the first RU to report data in this round, without sending an additional buffer status report query (Buffer Status Report Poll, BSRP) to the first device before scheduling the first device to report data to obtain the BSR of the first device before scheduling the first device to report data. By allowing the first device to report the BSR in a timely manner, it is convenient to schedule the first device to report data, thereby reducing service latency.

In a possible implementation, the method also includes: receiving a second frame of multiple first devices, the second frame including the BSR of the first device; determining a first RU and a second RU used by the multiple first devices in the next round based on the BSR of the multiple first devices; and sending a third frame, the third frame including a third field and a fourth field, the third field indicating the first RU of the first device reporting the BSR in the next round, and the fourth field indicating the second RU of the first device reporting data in the next round.

In a possible implementation, the method further includes: sending a fourth frame, where the fourth frame includes a fifth field, and the fifth field indicates a second RU of a last round of data reporting by the first device.

In a possible implementation manner, the method further includes: allocating the first RU.

In a possible implementation, allocating the first RU includes: allocating the first RU to a corresponding first device so that the corresponding first device reports a BSR through the corresponding first RU; and/or allocating a first RU so that the first device randomly selects a first RU to report a BSR.

In a possible implementation, the second field includes a first subfield, and the first subfield indicates whether the second frame uploaded by the first device carries the BSR or does not indicate whether the BSR is carried.

In a possible implementation manner, the second field also includes a user information field related to the trigger frame, and the user information field related to the trigger frame includes the first subfield.

In a possible implementation manner, the first frame further includes a sixth field, and the sixth field indicates whether the first frame carries block acknowledgement BA information.

In a possible implementation manner, the first frame further includes a common information field related to a trigger frame, and the common information field related to the trigger frame includes the sixth field.

In a possible implementation, when the sixth field indicates that the first frame carries BA information, the first frame further includes a seventh field, and the seventh field indicates a location of the BA information.

In a possible implementation manner, the first frame is a trigger frame, and the second frame is a data frame.

In a third aspect, an embodiment of the present application provides a communication device. The communication device can be applied to a first device, or to a module (e.g., a chip or a processor) in the first device, or to a logic module or software that can implement all or part of the functions of the first device. The communication device has the function of implementing the behavior in the above-mentioned first aspect or any method instance in the first aspect. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above-mentioned functions. The beneficial effects can be found in the description of the first aspect, which will not be repeated here.

In a fourth aspect, an embodiment of the present application provides a communication device. The communication device can be applied to a second device, or to a module (e.g., a chip or a processor) in the second device, or to a logic module or software that can implement all or part of the functions of the second device. The communication device has the function of implementing the behavior in the above-mentioned second aspect or any method instance in the second aspect. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above-mentioned functions. The beneficial effects can be found in the description of the second aspect, which will not be repeated here.

In a fifth aspect, an embodiment of the present application provides a communication device, which may be the first device in the above method embodiment, or The communication device may include a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instruction is executed by the processor, the communication device executes the method executed by the first device, or the chip or processor in the first device in the above method embodiment.

In a sixth aspect, an embodiment of the present application provides a communication device, which may be the first device in the above method embodiment, or a chip or processor set in the first device. The communication device may include a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instruction is executed by the processor, the communication device executes the method executed by the first device, or the chip or processor in the first device in the above method embodiment.

In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program or computer instructions. When the computer program or computer instructions are run on a computer, the computer executes the method in the above-mentioned first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect.

In an eighth aspect, an embodiment of the present application provides a computer program product comprising program instructions, which, when executed on a computer, enables the computer to execute the method in the above-mentioned first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect.

In a ninth aspect, an embodiment of the present application provides a chip system, which includes a processor for implementing the functions in the above methods. In a possible implementation, the chip system may also include a memory for storing program instructions and/or data. The chip system may be composed of a chip, or may include a chip and other discrete devices.

In the tenth aspect, an embodiment of the present application provides a communication system, which includes a first device and a second device, the first device is used to execute the above-mentioned first aspect or any possible implementation of the first aspect, and the second device is used to execute the above-mentioned second aspect or any possible implementation of the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application;

FIG2 is a flow diagram of a communication method for integrated reporting of service data and cache status reports provided in an embodiment of the present application;

FIG3 is a schematic diagram of the structure of an integrated trigger frame provided in an embodiment of the present application;

FIG4 is a schematic diagram of a format of a common information field in a first frame provided by an embodiment of the present application;

FIG5 is a schematic diagram of the structure of another integrated trigger frame provided in an embodiment of the present application;

FIG6 is a schematic diagram of a signaling process and resource allocation between devices provided in an embodiment of the present application;

FIG7 is a signaling flow chart of another device provided in an embodiment of the present application;

FIG8 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

FIG9 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application;

FIG10 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, the terms "system" and "network" in the embodiments of the present application can be used interchangeably. Unless otherwise specified, "/" indicates that the objects associated before and after are in an "or" relationship. For example, A/B can represent A or B; "and/or" in this application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. These three situations, where A and B can be singular or plural. And, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be one or more. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between network elements and identical or similar items with substantially the same functions. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

References to "one embodiment" or "some embodiments" in the embodiments of the present application mean that one or more embodiments of the present application include a particular feature, structure or characteristic described in conjunction with the embodiment. "In one embodiment,""in some embodiments,""in some other embodiments,""in other embodiments," etc. do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "include,""comprising,""having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

The following specific implementation methods further describe in detail the objectives, technical solutions and beneficial effects of the present application. It should be understood that the following are only specific implementation methods of the present application and are not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

It should be understood that the embodiments of the present application can be applicable to systems that comply with IEEE 802.11 system standards, such as 802.11bf, 802.11ax, 802.11be, or next-generation standards, such as wireless LAN systems of 802.11 series protocols such as Wi-Fi 8, UHR, Wi-Fi AI, or wireless personal LAN systems based on ultra-wideband UWB, etc., and can also be applicable to wireless local area network (WLAN) scenarios. Alternatively, the embodiments of the present application can also be applied to wireless local area network systems such as the Internet of Things (IoT) network or the Vehicle to X (V2X) network. Of course, the embodiments of the present application can also be applied to other possible communication systems, such as 5G communication systems and subsequent evolved cellular communication systems.

The following takes the scenario in which the embodiment of the present application can be applied to WLAN as an example. It should be understood that WLAN started from the 802.11a/g standard, and went through 802.11n, 802.11ac, 802.11ax, and the 802.11be and Wi-Fi 8 that are being discussed now. Among them, 802.11n can also be called high throughput (HT); 802.11ac can also be called very high throughput (VHT); 802.11ax can also be called high efficiency (HE) or Wi-Fi 6; 802.11be can also be called extremely high throughput (EHT) or Wi-Fi 7, and the standards before HT, such as 802.11a/b/g, are collectively called non-high throughput (non-HT).

Please refer to Figure 1, which is a schematic diagram of a network architecture provided by an embodiment of the present application. As shown in Figure 1, a network architecture including 1 wireless access point AP and 2 stations is used as an example for explanation. The STA associated with the AP can receive wireless frames sent by the AP and can also send wireless frames to the AP. In addition, the embodiment of the present application is also applicable to communication between APs. For example, each AP can communicate with each other through a distributed system (DS), and the embodiment of the present application is also applicable to communication between STAs. It should be understood that the number of APs and STAs in Figure 1 is only an example, and can be more or less.

The STA involved in the embodiments of the present application is a device with wireless communication function, supports communication using the WLAN protocol, and has the ability to communicate with other stations or access points in the WLAN network. In a WLAN system, a station can be called 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 and then communicate with a WLAN. The device can be a complete device, or a chip or processing system installed in the complete device. Devices installed with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of the chip or processing system. For example, STA may be various user terminals, user devices, access devices, subscriber stations, subscriber units, mobile stations, user agents, user equipment or other names with wireless communication functions, wherein user terminals may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions, as well as various forms of user equipment (UE), mobile stations (MS), terminals, terminal equipment, portable communication devices, handheld machines, portable computing devices, entertainment devices, gaming devices or systems, global positioning system devices or any other suitable devices configured to communicate over a wireless medium. For example, STA may be a router, a switch, a bridge, etc. Here, for the convenience of description, the above-mentioned devices are collectively referred to as stations or STAs.

The access point (e.g., AP) involved in the embodiments of the present application is a device with wireless communication function, supports communication using the WLAN protocol, has the function of communicating with other devices in the WLAN network (e.g., stations or other access points), and of course, can also have the function of communicating with other devices. In a WLAN system, an access point can be called an access point station (AP STA). The device can be a complete device, or a chip or processing system installed in the complete device, etc. The device installed with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of the chip or processing system. The AP in the embodiments of the present application can be a device that provides services for STA and can support the 802.11 series of protocols. For example, AP can be a communication entity such as a communication server, a router, a switch, a bridge, etc.; AP can include various forms of macro base stations, micro base stations, relay stations, etc., and of course AP can also be chips and processing systems in these various forms of devices, thereby implementing the methods and functions of the embodiments of the present application.

The AP and STA involved in the embodiments of the present application may be AP and STA applicable to the IEEE 802.11 system standard. AP is a device deployed in a wireless communication network to provide wireless communication functions for its associated STA. The AP can be used as the hub of the communication system, and is usually a network-side product that supports the MAC and PHY of the 802.11 system standard. For example, it can be a base station, router, gateway, repeater, communication server, switch or bridge and other communication equipment, wherein the base station may include various forms of macro base stations, micro base stations, relay stations, etc. Here, For the convenience of description, the above-mentioned devices are collectively referred to as APs. STAs are usually terminal products that support the medium access control (MAC) and physical layer (PHY) of the 802.11 system standard, such as mobile phones, laptops, etc.

WLAN system can provide high-speed and low-latency transmission. With the continuous evolution of WLAN application scenarios, WLAN system will be applied to more scenarios or industries, such as the Internet of Things industry, the Internet of Vehicles industry or the banking industry, corporate offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, wards, classrooms, supermarkets, squares, streets, production workshops and warehouses, etc. Of course, the devices supporting WLAN communication (such as access points or sites) can be sensor nodes in smart cities (such as smart water meters, smart meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, displays, TVs, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as wearable devices such as AR and VR), smart devices in smart offices (such as printers, projectors, loudspeakers, speakers, etc.), Internet of Vehicles devices in the Internet of Vehicles, infrastructure in daily life scenarios (such as vending machines, self-service navigation desks in supermarkets, self-service cashier devices, self-service ordering machines, etc.), and equipment in large sports and music venues, etc. There is no special limitation on the specific forms of STA and AP in the embodiments of the present application, which are merely illustrative here.

The AP can use orthogonal frequency division multiple access (OFDMA) technology to divide the channel into multiple resource units (RU). Different STAs can occupy different RUs, thereby performing multi-user transmission in parallel.

In the OFDMA mechanism, the AP needs to allocate RUs used by the STA according to the buffer status of the STA. Specifically, before scheduling the STA each time, the AP sends a buffer status report query (Buffer Status Report Poll, BSRP) message to the STA. In response to the BSRP message, the STA sends a buffer status report (Buffer Status Report, BSR) to the AP so that the AP can allocate RUs to multiple STAs according to the BSR. In other words, before scheduling the STA each time, the AP needs to obtain the BSR from the STA through an additional control frame (for example, BSRP) to determine whether the STA needs to be scheduled to report data, thereby increasing the service delay. Therefore, how to reduce the service delay is a problem that needs to be solved.

Based on the above, the present application proposes a communication method, which will be described below through the following embodiments. Some of these communication methods are only for some processes in the OFDMA mechanism, and some can be applied to any one or more processes in the OFDMA mechanism. It should be understood that these communication methods can be used in combination with each other, for example, one process in the OFDMA mechanism can use one method and another process can use another method, or one process in the OFDMA mechanism can use both one method and another method.

It should be understood that the OFDMA mechanism may change with the evolution of the technical solution, and the technical solution provided by this application is not limited to the process described below. Further, the description of the scene in the embodiment of this application is only an example, and does not limit the solution of the embodiment of this application to be used only in the described scene, and is also applicable to scenes with similar problems.

A communication method provided in an embodiment of the present application is described below. Please refer to Figure 2, which is a process interaction diagram of a communication method for integrated reporting of business data and cache status reports provided in an embodiment of the present application. In Figure 2, the method is illustrated by taking the first device and the second device as the execution subjects of the interaction diagram as an example, but the present application does not limit the execution subjects of the interaction diagram. For example, the first device in Figure 2 may also be a chip, a chip system, or a processor that supports the first device to implement the method, or a logic module or software that can implement all or part of the functions of the first device; the second device in Figure 2 may also be a chip, a chip system, or a processor that supports the second device to implement the method, or a logic module or software that can implement all or part of the functions of the second device. Among them, the first device may be a STA, and the second device may be an AP. As shown in Figure 2, the communication method includes but is not limited to the following steps S201-step S205:

S201. The second device sends a first frame to the first device. The first frame includes a first field and a second field. The first field indicates a first resource block RU for reporting a buffer status report BSR by the first device, and the second field indicates a second RU for reporting data by the first device.

Accordingly, the first device receives the first frame.

In a possible implementation manner, the first frame may be a trigger frame.

Exemplarily, the first frame may be an emsemble trigger frame. The emsemble trigger frame is used to schedule the first device to report data and/or BSR. This embodiment does not limit the specific name of the first frame. For ease of description, the emsemble trigger frame is used for description below.

It can be understood that the integrated trigger frame can be a new frame. For a possible implementation of the integrated trigger frame, please refer to Figure 3, which is a schematic diagram of the structure of an integrated trigger frame provided in an embodiment of the present application. As shown in Figure 3, the integrated trigger frame may include a frame control (framecontrol) field, a duration (duration) field, a receiving end address (RA), a transmitting end address (TA), a common information (commoninfo) field (or, a public information field), a user information list (userinfolist) field, a padding (padding) field, and a frame check sequence (FCS) field. Among them, the user information list field may include a first field and a second field. The first field may be a user information list A (userinfolistA) field, which may indicate that the corresponding RU is used to upload BSR information. The second field may be a user information list B (userinfolistB) field, which may indicate that the corresponding RU is used to upload data. That is, the first field may indicate the RU corresponding to the BSR information for uploading (i.e., the first RU), and the second field indicates the RU corresponding to the data for uploading (i.e., the second RU). It can be understood that this embodiment does not limit the specific names of the first field and the second field, and their names are user information list A and user information. Table B is a possible implementation and shall not constitute any limitation to the embodiments of the present application.

In one possible implementation, as shown in Figure 3, the first field may include an association identifier 12 (AID12) field, a resource unit allocation (RU allocation) field, an uplink forward error correction coding type (UL FEC coding type) field, an uplink HE protocol modulation and coding scheme (UL HE-MCS) field, an uplink dual carrier modulation (UL DCM) field, a spatial stream allocation/random access resource unit information (SS allocation/RA-RU information) field, an uplink target receive power (UL target receive power) field, and an upload content type (UL content type) field.

In the first field, the value of the association identifier 12 field can be the identifier of the first device or a special value, such as 2044. When the value of the association identifier 12 field is the identifier of the first device, it indicates that the RU is used to report the BSR for a specific first device. If the value of the association identifier 12 field is a special value, it indicates that the RU can be randomly selected by the first device to report the BSR.

For example, if the value of the association identifier 12 field corresponding to the first RU1 is the identifier of the first device A, it means that the first device A needs to report the BSR of the first device A through the first RU1. If the value of the association identifier 12 field corresponding to the first RU2 is a special value, it means that the first RU2 can be used for any first device to report BSR information. For example, when the first device B has service data, the first device B can report the BSR through the first RU2, so that it can have the opportunity to be scheduled by the second device next time to report service data.

In the first field, the upload content type field is used to indicate that the corresponding RU is used to upload data or upload BSR information. In one example, when the value of the upload content type field is 0, it indicates that the RU is used to upload data, and when the value of the upload content type field is 1, it indicates that the RU is used to report BSR. Or, in another example, when the value of the upload content type field is 1, it indicates that the RU is used to upload data, and when the value of the upload content type field is 0, it indicates that the RU is used to report BSR.

It should be noted that only one first field is shown in the frame structure of the first frame shown in FIG3, but the first frame may include multiple first fields. Each first field may include an association identifier 12 field, a resource unit allocation field, an uplink forward error correction coding type field, an uplink HE protocol modulation and coding scheme field, an uplink dual-carrier modulation field, a spatial stream allocation/random access resource unit information field, an uplink target received power field, and an upload content type field. Each first field may correspond to one RU respectively. For example, the first field 1 corresponds to RU1, the association identifier 12 in the first field 1 is the identifier of the first device 1, the first field 2 corresponds to the first RU2, the association identifier 12 in the first field 2 is the identifier of the first device 2, the first field 3 corresponds to RU3, and the association identifier 12 in the first field 3 is a special value, which means that RU1 is used for the first device 1 to report the BSR, RU2 is used for the first device 2 to report the BSR, and RU3 can be randomly selected by the first device to report the BSR.

In one possible implementation, as shown in Figure 3, the second field may include an association identifier 12 (AID12) field, a resource unit allocation (RU allocation) field, an uplink forward error correction coding type (UL FEC coding type) field, an uplink HE protocol modulation and coding scheme (UL HE-MCS) field, an uplink dual carrier modulation (UL DCM) field, a spatial stream allocation/random access resource unit information (SS allocation/RA-RU information) field, an uplink target receive power (UL target receive power) field, an upload content type (UL content type) field, and a trigger frame related user information (trigger dependent user info) field.

In the second field, the upload content type field is used to indicate that the corresponding RU is used to upload data or upload BSR information. In one example, when the value of the upload content type field is 0, it indicates that the RU is used to upload data, and when the value of the upload content type field is 1, it indicates that the RU is used to report BSR. Or, in another example, when the value of the upload content type field is 1, it indicates that the RU is used to upload data, and when the value of the upload content type field is 0, it indicates that the RU is used to report BSR. The correspondence between the first device and the RU can be determined by the association identifier 12 in the second field. That is, the first device represented by the association identifier 12 is the first device that can report data through the RU.

In a possible implementation, the second field includes a first subfield, and the first subfield may indicate whether the second frame uploaded by the first device carries a BSR or does not indicate whether the BSR is carried. The first subfield may be an upload buffer status report (UL BSR) field. For example, the value of the first subfield is 1, indicating that the second frame uploaded by the first device needs to include both data and a BSR. The value of the first subfield is 0, indicating that the second frame uploaded by the first device needs to include data, and may include or not include a BSR. Or, for example, the value of the first subfield is 0, indicating that the second frame uploaded by the first device needs to include both data and a BSR. The value of the first subfield is 1, indicating that the second frame uploaded by the first device needs to include data, and may include or not include a BSR. The embodiment of the present application does not limit this. Among them, the BSR may be reported as part of the data. For example, when reporting (the first device sends the second frame), the BSR is used as the end of the data. Among them, the second frame may be a data frame.

Exemplarily, the value of the first subfield is 1, indicating that the second frame uploaded by the first device needs to include both data and BSR. The value of the first subfield is 0, indicating that the second frame uploaded by the first device needs to include data, and may or may not include BSR. If the association identifier 12 in the second field is used to represent the first device C, the associated RU is the second RU1, and the value of the first subfield is 1, the first device C can report data through the second RU1, and needs to report BSR when reporting data through the second RU1.

Exemplarily, the value of the first subfield is 1, indicating that the second frame uploaded by the first device needs to include both data and BSR. The value of the first subfield is 0, indicating that the second frame uploaded by the first device needs to include data, and may or may not include BSR. If the association identifier 12 in the second field is used to represent the first device D, the associated RU is the second RU2, and the value of the first subfield is 0, the first device D can report data through the second RU2, and may or may not report BSR.

In one possible implementation, the second field may include a trigger-dependent user information field, and the trigger-dependent user information field includes the first subfield. In other words, the first subfield is included in the trigger-dependent user information field. In other words, the first subfield is a part of the trigger-dependent user information field.

It should be noted that only one second field is shown in the frame structure of the first frame shown in Figure 3, but the first frame may include multiple second fields. Each second field may include an association identifier 12 field, a resource unit allocation field, an uplink forward error correction coding type field, an uplink HE protocol modulation and coding scheme field, an uplink dual-carrier modulation field, a spatial stream allocation/random access resource unit information field, an uplink target received power field, an upload content type field, and a trigger frame-related user information field. Each second field may correspond to one RU respectively. For example, the second field 1 corresponds to RU1, the association identifier 12 in the second field 1 is the identifier of the first device 1, the second field 2 corresponds to RU2, and the association identifier 12 in the second field 2 is the identifier of the first device 2, which means that RU1 is used for the first device 1 to report data, and RU2 is used for the first device 2 to report data.

Please refer to Figure 4, which is a schematic diagram of the format of a common information field in a first frame provided in an embodiment of the present application.

The common information fields include the trigger frame type field (trigger type), the upload length (UL length), the subsequent trigger frame (more TF), the carrier sense required (CS required), the uplink bandwidth (UL BW), the guard interval and HE protocol long training field type (GI and HE-LTF type), the multi-user multiple input multiple output HE protocol long training field mode (MU-MIMO HE-LTF mode), the number of HE protocol long training field symbols and midamble periodicity, and the uplink space-time block coding (UL STBC). ) field, low-density parity check extra symbol segment (LDPC extra symbol segment) field, AP transmit power (AP Tx power) field, forward error correction field before filling factor (Pre-FEC padding factor) field, PE disambiguity field, uplink spatial reuse (UL spatial reuse) field, Doppler effect (Doppler) field, uplink HE protocol information field A2 reserved (UL HE-SIG-A2reserved) field, reserved (Reserved) field, trigger frame related common information (trigger dependent common info) field. Among them, the trigger frame type field is used to indicate the type of the trigger frame. As shown in Table 1 below, it is a type table of trigger frames.

Table 1

Among them, the value of the trigger frame type is 8, which can represent the first frame (integrated trigger frame) provided in the embodiment of the present application. It can be understood that the value of the trigger frame type is 8, which means that the first frame provided in the embodiment of the present application is an example and should not constitute any limitation to the embodiment of the present application.

In one possible implementation, the first frame may further include a sixth field. The sixth field indicates whether the first frame carries block acknowledgement (BA) information. For example, the value of the sixth field is 1, indicating that the first frame carries block acknowledgement information; the value of the sixth field is 0, indicating that the first frame does not carry block acknowledgement information. Alternatively, the value of the sixth field is 0, indicating that the first frame carries block acknowledgement information; the value of the sixth field is 1, indicating that the first frame does not carry block acknowledgement information. The sixth field may be a field carrying multi-STA BA info.

In a possible implementation, as shown in FIG4 , the first frame may include a trigger-dependent common information field, and the common information field of the trigger frame includes a sixth field (multi-user block confirmation information field). The common information field of the trigger frame may also include a reserved field.

Please refer to FIG. 5 , which is a schematic diagram of the structure of another integrated trigger frame provided in an embodiment of the present application.

As shown in FIG5 , the integrated trigger frame may include a frame control field, a duration field, a receiving end address field, and a (RA), transmitter address (TA), common information (common info) field, user information list (user info list) field, multi-STA block acknowledgment information (multi-STA BA info) field, padding (padding) field, frame check sequence (FCS) field.

In the case where the sixth field in FIG. 4 indicates that the first frame carries BA information, the first frame may further include a seventh field. The seventh field may indicate the location of the BA information. The seventh field may be a block acknowledgement flag (BA flag) field.

In a possible implementation, the seventh field may be included in the multi-user block confirmation information field. It is used to indicate the position of the BA information in the multi-user block confirmation information field. For example, if the 2-byte seventh field is all set to 1, it indicates that the information after the seventh field is BA information. Further, as shown in FIG5 , the block confirmation type (BAtype) field in the block confirmation control (BAcontrol) field may be set to a default value, indicating that the frame is a BA frame (BA information) of a multi-user type (multi-STA). For example, the default value may be set to 11.

In the prior art, after receiving the data frame sent by the first device, the second device needs to reply BA information to the first device. In the embodiment of the present application, by integrating BA information into the trigger frame (first frame), the first frame integrates the functions of scheduling the data and/or BSR of the first device and replying BA information to the first device. This reduces the overhead of the control frame and improves the efficiency of scheduling.

In a possible implementation manner, the integrated trigger frame is determined based on the BSR reported by the first device.

Exemplarily, before the second device sends an integrated trigger frame, it may first send a BSRP to the first device to obtain the cache status of the first device. After the first device receives the BSRP sent by the second device, it reports a BSR to the second device. By parsing the BSRs reported by multiple first devices, the second device can obtain the cache status information of multiple first devices and determine whether each first device has a cache that needs to be reported. Among them, the first device is associated with the second device. For example, the second device sends a BSRP to all first devices associated with the second device. After receiving the BSRP, all first devices associated with the second device report their respective BSRs to the second device. Thus, the second device can parse the BSRs reported by each first device to obtain the cache status information of each first device.

In a possible implementation manner, the method further includes: the second device allocating the first RU.

In a possible implementation, the allocation method may include:

Based on a one-to-one correspondence between the first RU and the first device, allocating the first RU to the corresponding first device, so that the corresponding first device reports the BSR through the corresponding RU; and/or,

The first RU may not correspond to the first device. By allocating the first RU, the first device with services/buffers to be reported may randomly select the first RU to report the BSR.

Exemplarily, based on previous packet sending statistics, the second device finds that the first device A and the first device B are active users (for example, first devices that often store business data), then two first RUs (assuming they are first RU1 and first RU2) can be allocated to the first device A and the first device B, so that the first device A and the first device B can report the BSR through the first RU1 and the first RU2, respectively.

Exemplarily, some first RUs may also be allocated, but the first RUs are not allocated to fixed or specific first devices. Instead, they are provided to first devices in need for selection, so that the first devices in need can report BSRs through these first RUs that are allocated but not allocated to fixed first devices. For example, the second device allocates the first RU3, the first RU4, and the first RU5, but they are not allocated to the fixed first device. Then, when the first device C has service data/cache, it can randomly select one from the first RU3, the first RU4, and the first RU5 to report the BSR.

Based on the above method, the RU can be used for some first devices to report data and other devices to report BSR at the same time, so that each first device has the opportunity to report BSR information, solves the fairness problem in the BSR reporting process, and reduces service delay. In addition, while efficiently reporting BSR information, it also reduces the waste of RU resources.

S202: The first device reports a second frame to the second device based on the first frame.

Correspondingly, the second device receives the second frames of the plurality of first devices.

The second frame includes the BSR.

In a possible implementation manner, the second frame may be a data frame.

In a possible implementation manner, the first device reporting the second frame to the second device based on the first frame includes:

Determine, based on the first frame, to report the second frame in the second RU, where the second frame also includes data; or,

Determine, based on the first frame, to report the second frame in the corresponding first RU; or,

Determine based on the first frame whether to report the second frame in a random first RU.

Specifically, after receiving the first frame, each first device parses the first frame. Based on the first field and the association identifier 12 field in the second field, it is determined whether data needs to be reported and whether a BSR needs to be reported. For example, if the first device A parses the first field of the first frame and the association identifier 12 field includes the identifier corresponding to the first device A, and the corresponding RU is the first RU1, the first device A reports the BSR information through the first RU1. If the first device A parses the second field of the first frame and the association identifier 12 field includes the identifier corresponding to the first device A, and the corresponding RU is the second RU1, the first device A reports the data through the second RU1, and needs to report the BSR information based on the parsing of the first frame. The subfield determines whether a BSR needs to be reported. If the first device A parses the first field of the first frame and the association identifier 12 field does not include the identifier corresponding to the first device A, the first device A may not upload the BSR, or the first device A randomly selects a first RU with a special value in the association identifier 12 field in the first field to report the BSR.

S203: The second device determines a first RU and a second RU used by the multiple first devices in the next round based on the BSRs of the multiple first devices.

Based on step S202, the second device can obtain the BSRs of the multiple first devices, and thus can determine the first RU and the second RU used by the multiple first devices in the next round based on the obtained BSRs of the multiple first devices. It can be known that the BSRs of the multiple first devices can be obtained from the second frames sent by the multiple first devices to the second device.

Specifically, the method for determining the first RU and the second RU used by the multiple devices in the next round based on the BSRs of the multiple first devices is referred to step S201, which will not be described in detail here.

The first RU and the second RU used by multiple devices in the next round are determined based on the BSRs of multiple first devices in the previous round. Therefore, there is no need to send BSRP to the first device to obtain BSR before scheduling the first device and RU each time. Instead, the BSRs of some other first devices can be obtained while obtaining the service data of some first devices, thereby saving control frame overhead.

S204: The second device sends a third frame to the first device.

Correspondingly, the first device receives the third frame.

The third frame is another integrated trigger frame. The allocation of the first RU and the second RU in the third frame is determined based on the BSR in the second frame.

The third frame includes a third field and a fourth field. The third field indicates the first RU of the first device reporting the BSR in the next round, and the fourth field indicates the second RU of the first device reporting the data in the next round. The third field in the third frame can refer to the first field in the first frame. The fourth field in the third frame can refer to the second field in the first frame. No further details will be given here.

S205. The second device sends a fourth frame to the first device.

Correspondingly, the first device receives the fourth frame.

Among them, the fourth frame is another integrated trigger frame. The fourth frame is an integrated trigger frame sent by the second device to the first device in the Nth round of scheduling in N rounds of scheduling. Since this is the last round of scheduling, the second device may no longer obtain the BSR of the first device for determining the next round of scheduling. All RUs can be used for the first device to report data. This further avoids the waste of RUs.

The fourth frame includes a fifth field, and the fifth field indicates the second RU of the last round of data reporting by the first device. The fields included in the fifth field can refer to the fields included in the second field in FIG. 3, and will not be described in detail here.

It should be noted that steps S202 to S205 are optional steps, which are indicated by dotted lines in FIG. 2 .

In the embodiment of the present application, the second RU (such as the second RU in the text) to which the first device reports data can be indicated by the second field in the first frame, so that the first device can be scheduled to report data through the second RU that reports data. And the first field in the first frame can indicate the first RU (such as the first RU in the text) to which the first device reports the BSR, so that the first device can be scheduled to report the BSR through the first RU that reports the BSR. For example, when the first device has service data to be reported but is not scheduled to report data, the first device can select a first RU to report the BSR based on the received first frame. Thus, in the next round of scheduling, the second device can choose whether to schedule the first device that reports the BSR through the first RU to report data based on the BSR reported by the first device. The second device can obtain the BSR of the first device without sending a BSRP to the first device, and the first device does not need to send an additional BSR to the second device before being scheduled to report data to obtain the opportunity to report data. By enabling the first device to report the BSR in a timely manner when it is not scheduled to report data, it is convenient for the second device to schedule the first device to report data based on the BSR of the first device, thereby reducing service latency.

In order to further illustrate the method involved in the embodiment of the present application, the embodiment of the present application is described below with reference to Figures 6 and 7.

Please refer to Figure 6, which is a schematic diagram of a signaling process and resource allocation between devices provided in an embodiment of the present application. As shown in Figure 6, it is assumed that the second device is associated with 20 first devices in total, and the bandwidth capacity of the second device and the first device is 80 megabits (M). After the second device obtains a transmission opportunity (transmit opportunity, TXOP) within a period of time, a total of N rounds of scheduling are performed. Each round of scheduling includes an interaction in which the second device sends an integrated trigger frame to the first device and the first device reports the second frame to the second device. Among them, the number of scheduling rounds N can be determined based on the duration of the second device obtaining the TXOP, and/or can be determined based on the cache status of the first device associated with the second device, etc., and the embodiments of the present application do not limit this.

The first round of scheduling:

The second device sends BSRP to multiple first devices, where BSRP is used to obtain buffer status information of the first devices.

After receiving the BSRP, the first device may report the respective BSRs to the second device.

After receiving the BSR, the second device determines to schedule the first device 1, the first device 2, and the first device 3 to report data in the first round of scheduling based on the BSR reported by the first device, and the 242-tone RUs (second RUs) corresponding to the first three 20M bandwidth spectrums are respectively used. The first device 1, the first device 2, and the first device 3 are required to carry the BSR information in the second frame (for example, PPDU) uploaded by the first device 1, the first device 2, and the first device 3. Also, it is determined that in the first round of scheduling, the 9 26-tone RUs (first RUs) of the fourth 20M bandwidth spectrum are used as random RUs for the first device that is not scheduled to upload data to upload the BSR information. In the first round of scheduling, the first devices scheduled to upload data are the first device 1, the first device 2, and the first device 3. Then in the first field of the first frame, the association identifier 12 field is a special value, and does not include any identifier corresponding to the first device, which is used to indicate that the first RU can be selected by any unscheduled first device and report the BSR information. In the second field of the first frame, the association identifier 12 field includes identifiers corresponding to the first device 1, the first device 2, and the first device 3, which correspond to the 242-tone RUs (second RUs) of the first, second, and third 20M bandwidth spectrums, respectively, and the first subfield (upload cache status report field) in the second field indicates that the first device 1, the first device 2, and the first device 3 report BSR information. It can be understood that in the second field of the first frame, the association identifier 12 field includes identifiers corresponding to the first device 1, the first device 2, and the first device 3, which may mean that in a second field of the first frame, the association identifier 12 field is the identifier corresponding to the first device 1, in another second field of the first frame, the association identifier 12 field is the identifier corresponding to the first device 2, and in another second field of the first frame, the association identifier 12 field is the identifier corresponding to the first device 3. No further description will be given hereinafter.

After the first device receives the first frame, it can send the second frame through the corresponding RU based on the first frame, and the second frame may include a BSR. Specifically, after the first device receives the first frame, it parses the first frame to obtain the first field and the second field. Based on the first field, it can be determined that the first device that needs to report BSR information and the first device that needs to report BSR information report through which first RU. Based on the second field, it can be determined that the first device that needs to report data and the first device that needs to report data report through which second RU. In the first round of scheduling, based on the first field, it can be known that the first device that needs to report BSR information is not specified, and based on the second field, it can be known that the second device 1, the second device 2, and the second device 3 need to report data, need to report BSR information, and report data and BSR information through the 1st, 2nd, and 3rd 20M bandwidth spectrum 242-tone size RU (second RU) respectively. Therefore, the first device 1, the second device 2, and the second device 3 send the second frame through the 1st, 2nd, and 3rd 20M bandwidth spectrum 242-tone size RU (second RU) respectively. The second frame sent by the first device 1, the second device 2, and the second device 3 includes data and BSR information. When the first field does not indicate that a specific first device needs to report BSR information, each first device can determine whether it needs to randomly select a first RU to send a second frame based on its actual situation, such as whether there is business/cache data, etc., and the second frame includes BSR information. For example, in Figure 6, the first device 5, the first device 6, and the first device 7 each randomly selected a first RU to send a second frame. The second frame sent by the first device 5, the first device 6, and the first device 7 includes BSR information. This means that the first device 5, the first device 6, and the first device 7 may include business/cache data.

After receiving the second frame, the second device sends a block confirmation message to the first device, indicating that the second device has received the second frame sent by the first device. At this point, the first round of scheduling is completed.

The second to N-1 rounds of scheduling:

The second device may send a third frame to multiple first devices based on the second frame received in the previous round of scheduling. It is understandable that the third frame may be another integrated trigger frame. The third frame may indicate the first RU for the first device to report a BSR in the next round and the second RU indicating the first device to report data. It should be noted that the next round refers to the next time the first device reports data and/or BSR. Specifically, the next round may refer to the scheduling round in which the third frame is located. For example, in the second round of scheduling, the third frame sent by the second device to the first device indicates the first RU for the first device to report a BSR in the second round of scheduling and the second RU indicating the first device to report data.

The second round of scheduling is shown in Figure 6:

After receiving the first frame sent by the first device in the first round of scheduling, the second device can determine to schedule the first device 7, the first device 6, the first device 5 and the first device 3 to report data through the second RUs of 242-tone, 106-tone, 106-tone and RU242-tone sizes in the second round of scheduling based on the BSR information reported by the received first devices 1-3 and 5-7, and require the first device 7, the first device 6, the first device 5 and the first device 3 to include BSR information in the uploaded second frame. And because the second device finds that the first device 1 and the first device 2 are active users, the first 26-tone first RU and the second 26-tone first RU can be assigned to the first device 1 and the first device 2 respectively, that is, the corresponding relationship between the first device 1 and the first first RU is established, and the corresponding relationship between the first device 2 and the second first RU is established. The remaining 7 first RUs are random RUs, which can be randomly selected by the first device to report BSR information. Then in the third field of the third frame, the association identifier 12 includes the identifiers corresponding to the first device 1 and the first device 2, and includes 7 special values. In the fourth field of the third frame, the association identifier 12 includes the identifiers corresponding to the first device 7, the first device 6, the first device 5, and the first device 3, which correspond to the second RUs of 242-tone, 106-tone, 106-tone, and RU242-tone, respectively, and the first subfield in the fourth field indicates that the first device 7, the first device 6, the first device 5, and the first device 3 report BSR information. It can be understood that the fields included in the third field of the third frame can refer to the fields included in the first field of the first frame; the fields included in the fourth field of the third frame can refer to the fields included in the second field of the first frame, which will not be repeated here. It can be understood that in the third field of the third frame, That the association identifier 12 includes identifiers corresponding to the first device 1 and the first device 2 may mean that, in a third field of the third frame, the association identifier 12 is an identifier corresponding to the first device 1, and in another third field of the third frame, the association identifier 12 is an identifier corresponding to the first device 2. That the association identifier 12 in the fourth field of the third frame includes identifiers corresponding to the first device 7, the first device 6, the first device 5, and the first device 3 may mean that, in a fourth field of the third frame, the association identifier 12 is an identifier corresponding to the first device 7, in another fourth field of the third frame, the association identifier 12 is an identifier corresponding to the first device 6, and in another fourth field of the third frame, the association identifier 12 is an identifier corresponding to the first device 5.

After the first device receives the third frame, it can send the second frame through the corresponding RU based on the first frame, and the second frame may include the BSR. Specifically, after the first device receives the third frame, it parses the third frame to obtain the first field and the second field. Based on the first field, it can be determined that the first devices that need to report BSR information include the first device 1 and the first device 2, and the first device 1 and the first device 2 send the second frame through the first 26-tone first RU and the second 26-tone first RU respectively. The second frame sent by the first device 1 and the first device 2 includes BSR information. Based on the second field, it can be determined that the first device 7, the first device 6, the first device 5 and the first device 3 need to report data and BSR through the second RU of 242-tone, 106-tone, 106-tone and RU242-tone respectively. Among the 7 random RUs, the first device 8 and the first device 9 select the 6th and 8th first RUs to report the BSR respectively.

After receiving the second frame, the second device sends a block confirmation message to the first device, indicating that the second device has received the second frame sent by the first device. At this point, the second round of scheduling is completed.

Nth round of scheduling:

Based on the second frame received in the N-1th round, the second device sends a fourth frame to multiple first devices, and the fourth frame indicates the second RU of the first device reporting data in the Nth round. Since this round is the last round of scheduling, the BSR can no longer be queried. All 80M RUs can be used to report data. As shown in Figure 6, the first device 1, the first device 2, the first device 17 and the first device 9 respectively occupy 242-tone RUs to report data. Among them, the first device 1, the first device 2, the first device 17 and the first device 9 are the second devices that determine the reporting data in the Nth round of scheduling based on the BSR in the second frame received in the N-1th round.

After receiving the second frame, the second device sends a block confirmation message to the first device, indicating that the second device has received the second frame sent by the first device. At this point, the Nth round of scheduling is completed.

It is to be understood that the division of the size of the RU, the number of the first RU, and the number of the second RU shown in FIG. 6 is only an example and should not constitute any limitation to the embodiments of the present application. For example, the sizes of the RUs may not be exactly the same. For example, in different rounds of scheduling, the number of the first RU may be different. For example, in different rounds of scheduling, the number of the second RU may be different.

Please refer to FIG. 7 , which is another signaling flow chart between devices provided in an embodiment of the present application.

The signaling flow chart shown in FIG. 7 is different from FIG. 6 in that, in each round of scheduling except the last round (the Mth round in FIG. 7), after the second device receives the second frame sent by the first device, it no longer sends block confirmation information, but carries the block confirmation information in the next round of integrated trigger frames to indicate that the second device has received the second frame sent by the first device in the previous round of scheduling. Since the second device no longer sends the integrated trigger frame after receiving the second frame sent by the first device in the last round of scheduling. Therefore, after the second device receives the second frame in the last round of scheduling, it cannot carry the block confirmation information through the integrated trigger frame. Therefore, after receiving the second frame in the last round of scheduling, the block confirmation information can be sent to the first device.

By including block confirmation information in the integrated trigger frame, the control frame overhead can be reduced, the service delay can be reduced, and the communication efficiency can be improved.

The above content describes the method provided by the present application. In order to facilitate better implementation of the above scheme of the embodiment of the present application, the embodiment of the present application also provides a corresponding device.

The embodiment of the present application can divide the functional modules of the communication device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

Please refer to FIG8, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device may be a first device, or a module (e.g., a chip or a processor) in the first device, or a logic module or software that can implement all or part of the functions of the first device. As shown in FIG8, the communication device 800 at least includes: a transceiver unit 801; wherein:

The transceiver unit 801 is used to receive a first frame from a second device of an access point, wherein the first frame includes a first field and a second field, wherein the first field indicates a first resource block RU for reporting a buffer status report BSR by the first device, and the second field indicates a second RU for reporting data by the first device.

In one embodiment, the transceiver unit 801 is further used to report a second frame based on the first frame, the second frame including the BSR; and further used to receive a third frame, the third frame including a third field and a fourth field, the third field indicating that the first device reports the BSR in the next round The fourth field indicates the second RU of the first device for reporting data in the next round.

In one embodiment, the communication device 800 further includes a processing unit 802, configured to determine, based on the first frame, to report the second frame in the second RU, wherein the second frame further includes data; or,

Determine, based on the first frame, to report the second frame in the corresponding first RU; or,

Determine based on the first frame whether to report the second frame in a random first RU.

In one embodiment, the transceiver unit 801 is further configured to receive a fourth frame, where the fourth frame includes a fifth field, and the fifth field indicates a second RU of a last round of data reporting by the first device.

In an embodiment, the second field includes a first subfield, and the first subfield indicates whether the second frame uploaded by the first device carries a BSR or does not indicate whether the BSR is carried.

In one embodiment, the second field further includes a trigger frame-related user information field, and the trigger frame-related user information field includes the first subfield.

In one embodiment, the first frame further includes a sixth field, and the sixth field indicates whether the first frame carries block acknowledgement BA information.

In one embodiment, the first frame further includes a common information field related to a trigger frame, and the common information field related to the trigger frame includes the sixth field.

In an embodiment, when the sixth field indicates that the first frame carries BA information, the first frame further includes a seventh field, and the seventh field indicates the location of the BA information.

In one embodiment, the first frame is a trigger frame, and the second frame is a data frame.

For a more detailed description of the transceiver unit 801 and the processing unit 802, reference may be made to the relevant description of the first device in the method embodiment shown in FIG. 2 to FIG. 7, which will not be repeated here.

Please refer to FIG. 9, which is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device may be a second device, or a module (e.g., a chip or a processor) in the second device, or a logic module or software that can implement all or part of the functions of the second device. As shown in FIG. 9, the communication device 900 at least includes: a transceiver unit 901; wherein:

The transceiver unit 901 is used to send a first frame, where the first frame includes a first field and a second field, where the first field indicates a first resource block RU for reporting a buffer status report BSR by a first device, and the second field indicates a second RU for reporting data by the first device.

In one embodiment, the communication device 900 further includes a processing unit 902, wherein:

The transceiver unit 901 is further configured to receive a second frame of a plurality of first devices, where the second frame includes a BSR of the first device;

The processing unit 902 is configured to determine, based on the BSRs of the multiple first devices, a first RU and a second RU used by the multiple first devices in a next round;

The transceiver unit 901 is also used to send a third frame, which includes a third field and a fourth field. The third field indicates the first RU of the first device reporting BSR in the next round, and the fourth field indicates the second RU of the first device reporting data in the next round.

In one embodiment, the transceiver unit 901 is further configured to send a fourth frame, where the fourth frame includes a fifth field, and the fifth field indicates a second RU of a last round of data reporting by the first device.

In one embodiment, the processing unit 902 is further configured to allocate the first RU.

In one embodiment, the processing unit 902 is specifically used to allocate the first RU to the corresponding first device so that the corresponding first device reports the BSR through the corresponding first RU; and/or to allocate the first RU so that the first device randomly selects the first RU to report the BSR.

In an embodiment, the second field includes a first subfield, and the first subfield indicates whether the second frame uploaded by the first device carries a BSR or does not indicate whether the BSR is carried.

In one embodiment, the second field further includes a trigger frame-related user information field, and the trigger frame-related user information field includes the first subfield.

In one embodiment, the first frame further includes a sixth field, and the sixth field indicates whether the first frame carries block acknowledgement BA information.

In one embodiment, the first frame further includes a common information field related to a trigger frame, and the common information field related to the trigger frame includes the sixth field.

In an embodiment, when the sixth field indicates that the first frame carries BA information, the first frame further includes a seventh field, and the seventh field indicates the location of the BA information.

In one embodiment, the first frame is a trigger frame, and the second frame is a data frame.

Please refer to Figure 10, which is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. As shown in Figure 10, the device 1000 may include one or more processors 1001, which may also be called a processing unit, and may implement certain control functions. The processor 1001 may be a general-purpose processor or a dedicated processor, etc.

In an optional design, the processor 1001 may also store instructions 1003, and the instructions 1003 can be executed by the processor so that the device 1000 executes the method described in the above method embodiment.

In another optional design, the processor 1001 may include a transceiver unit for implementing the receiving and sending functions. For example, the transceiver unit may be a transceiver circuit, or an interface, or an interface circuit, or a communication interface. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

In yet another possible design, the apparatus 1000 may include a circuit, which may implement the functions of sending, receiving, or communicating in the aforementioned method embodiments.

Optionally, the device 1000 may include one or more memories 1002, on which instructions 1004 may be stored, and the instructions may be executed on the processor so that the device 1000 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory. Optionally, instructions and/or data may also be stored in the processor. The processor and memory may be provided separately or integrated together. For example, the corresponding relationship described in the above method embodiment may be stored in a memory or in a processor.

Optionally, the apparatus 1000 may further include a transceiver 1005 and/or an antenna 1006. The processor 1001 may be referred to as a processing unit, which controls the apparatus 1000. The transceiver 1005 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver device or a transceiver module, etc., which is used to implement a transceiver function.

Optionally, the device 1000 in the embodiment of the present application can be used to execute the method described in Figures 2 to 7 in the embodiment of the present application.

In one embodiment, the communication device 1000 can be applied to a first device, or to a module (e.g., a chip or a processor) in the first device, or to a logic module or software that can implement all or part of the functions of the first device. When the computer program instructions stored in the memory 1002 are executed, the processor 1001 is used to control the processing unit 802 to perform the operations performed in the above-mentioned embodiment, the transceiver 1005 is used to perform the operations performed by the transceiver unit 801 in the above-mentioned embodiment, and the transceiver 1005 is also used to send information to other communication devices outside the communication device. The above-mentioned first device or the module in the first device can also be used to execute the various methods performed by the first device in the method embodiments of Figures 2 to 7 above, which will not be repeated.

In one embodiment, the communication device 1000 can be applied to a second device, or to a module (e.g., a chip or a processor) in the second device, or to a logic module or software that can implement all or part of the functions of the second device. When the computer program instructions stored in the memory 1002 are executed, the processor 1001 is used to control the processing unit 902 to perform the operations performed in the above-mentioned embodiment, the transceiver 1005 is used to perform the operations performed by the transceiver unit 901 in the above-mentioned embodiment, and the transceiver 1005 is also used to send information to other communication devices outside the communication device. The above-mentioned second device or the module in the second device can also be used to execute the various methods executed by the second device in the above-mentioned method embodiments of Figures 2 to 7, which will not be repeated.

The processor and transceiver described in the present application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency interface chip (RFIC), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The device described in the above embodiments may be a first terminal device or a second terminal device, but the scope of the device described in this application is not limited thereto, and the structure of the device may not be limited by FIG. 10. The device may be an independent device or may be part of a larger device. For example, the device may be:

(1) Independent integrated circuit IC, or chip, or chip system or subsystem;

(2) having a set of one or more ICs, and optionally, the IC set may also include a storage component for storing data and/or instructions;

(3) ASIC, such as modem (MSM);

(4) Modules that can be embedded in other devices;

(5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, machine equipment, home equipment, medical equipment, industrial equipment, etc.;

(6)Others

An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, it can implement the process related to the first device in the communication method provided in the above method embodiment.

The embodiment of the present application also provides a computer program product, which, when executed on a computer or processor, enables the computer or processor to execute one or more steps in any of the above communication methods. If the components of the above-mentioned devices are implemented in the form of software functional units and sold or used as independent products, they can be stored in the computer-readable storage medium.

The embodiment of the present application also provides a chip system, including at least one processor and a communication interface, wherein the communication interface and the at least one processor are interconnected via a line, and the at least one processor is used to run a computer program or instruction to execute part or all of the steps of any one of the method embodiments corresponding to Figures 2 to 7 above. The chip system may be composed of a chip, or may include a chip and other discrete devices.

An embodiment of the present application further discloses a communication system, which includes a first device and a second device. For a specific description, reference may be made to the communication method shown in FIG. 2 to FIG. 7 .

It should be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a hard disk drive (HDD), a solid-state drive (SSD), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct RAM bus random access memory (DR RAM). The memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by the computer, but is not limited to this. The memory in the embodiments of the present application can also be a circuit or any other device that can realize the storage function, used to store program instructions and/or data.

It should also be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.

It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments provided herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system. Or some features may be ignored or not performed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the technology or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

The modules/units in the device of the embodiment of the present application can be combined, divided and deleted according to actual needs.

As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims (21)

A communication method for integrated reporting of service data and cache status report, characterized in that the method comprises: The first device receives a first frame from the access point second device, the first frame comprising a first field and a second field, the first field indicating a first resource block RU for reporting a buffer status report BSR by the first device, and the second field indicating a second RU for reporting data by the first device. The method according to claim 1, characterized in that the method further comprises: Reporting a second frame based on the first frame, where the second frame includes a BSR; A third frame is received, where the third frame includes a third field and a fourth field, where the third field indicates a first RU of a next round of BSR reporting by the first device, and the fourth field indicates a second RU of a next round of data reporting by the first device. The method according to claim 2, characterized in that the reporting of the second frame based on the first frame, wherein the second frame includes a BSR, includes: Determine, based on the first frame, to report the second frame in the second RU, where the second frame further includes data; or, Determine, based on the first frame, to report the second frame in the corresponding first RU; or, Determine based on the first frame whether to report the second frame in a random first RU. The method according to any one of claims 1 to 3, characterized in that the method further comprises: A fourth frame is received, where the fourth frame includes a fifth field, where the fifth field indicates a second RU of a last round of data reporting by the first device. A communication method for integrated reporting of service data and cache status report, characterized in that the method comprises: A first frame is sent, the first frame comprising a first field and a second field, the first field indicates a first resource block RU for reporting a buffer status report BSR by the first device, and the second field indicates a second RU for reporting data by the first device. The method according to claim 5, characterized in that the method further comprises: receiving a second frame of the plurality of first devices, the second frame comprising a BSR of the first device; Determine a first RU and a second RU used by the multiple first devices in a next round based on the BSRs of the multiple first devices; A third frame is sent, where the third frame includes a third field and a fourth field, where the third field indicates a first RU of a next round of BSR reporting by the first device, and the fourth field indicates a second RU of a next round of data reporting by the first device. The method according to claim 5 or 6, characterized in that the method further comprises: A fourth frame is sent, where the fourth frame includes a fifth field, where the fifth field indicates a second RU of a last round of data reporting by the first device. The method according to any one of claims 5 to 7, characterized in that the method further comprises: The first RU is allocated. The method according to claim 8, wherein allocating the first RU comprises: Allocating the first RU to a corresponding first device, so that the corresponding first device reports a BSR through the corresponding first RU; and/or The first RU is allocated so that the first device randomly selects the first RU to report the BSR. The method according to any one of claims 1 to 9 is characterized in that the second field includes a first subfield, and the first subfield indicates whether the second frame uploaded by the first device carries a BSR or does not indicate whether the BSR is carried. The method according to claim 10 is characterized in that the second field also includes a user information field related to the trigger frame, and the user information field related to the trigger frame includes the first subfield. The method according to any one of claims 1-11 is characterized in that the first frame also includes a sixth field, and the sixth field indicates whether the first frame carries block confirmation BA information. The method according to claim 12 is characterized in that the first frame also includes a common information field related to the trigger frame, and the common information field related to the trigger frame includes the sixth field. The method according to claim 12 or 13 is characterized in that, when the sixth field indicates that the first frame carries BA information, the first frame also includes a seventh field, and the seventh field indicates the location of the BA information. The method according to any one of claims 2-4 or 6-14 is characterized in that the first frame is a trigger frame and the second frame is a data frame. A communication device, characterized in that it comprises a unit for executing the method as described in any one of claims 1-4 or 10-15, or a unit for executing the method as described in any one of claims 5-15. A communication device, comprising: Memory for storing computer programs; A processor, configured to execute the computer program so that the communication device performs the method according to any one of claims 1-4 or 10-15, or the method according to any one of claims 5-15. A computer-readable storage medium, characterized in that a computer program or computer instructions is stored in the computer-readable storage medium, and when the computer program or computer instructions are executed by a processor, a communication device including the processor executes a method as described in any one of claims 1-4 or 10-15, or a method as described in any one of claims 5-15. A computer program product comprising program instructions, which, when executed on a computer, enables the method according to any one of claims 1 to 4 or 10 to 15 to be implemented, or the method according to any one of claims 5 to 15 to be implemented. A chip system, characterized in that it includes at least one processor, a memory and an interface circuit, wherein the memory, the interface circuit and the at least one processor are interconnected via lines, and instructions are stored in the at least one memory; when the instructions are executed by the processor, the communication device including the chip system executes the method described in any one of claims 1-4 or 10-15, or the method described in any one of claims 5-15. A communication system, characterized in that it includes a first device and a second device, the first device is used to execute the method according to any one of claims 1-4 or 10-15, and the second device is used to execute the method according to any one of claims 5-15.