Data volume reporting method and device and readable storage medium

Abstract

The invention provides a data volume reporting method and device and a readable storage medium, which can be applied to the technical field of communication and can avoid repeatedly reporting the data volume of the same data. The method comprises: a first device triggers a first status report, the first status report comprising data volume and time delay information of first data, and the first data being to-be-transmitted data of the first device; and the first device triggers a second status report, the second status report comprising a data volume of second data, and the second data being to-be-transmitted data of the first device. And the first equipment sends a target state report through the first transmission resource, wherein the target state report comprises the data volume of the first data.

Description

[0001] This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on June 16, 2023, with application number 202310723869.8 and application name “A method and device for reporting data volume”, all contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a method, device and readable storage medium for reporting data volume. Background Art

[0003] In the 5G communication system, the terminal device can report the amount of uplink data to be transmitted to the base station by reporting the buffer status report (BSR), so that the base station can reasonably allocate uplink resources to the terminal device according to the reported data amount to achieve uplink scheduling.

[0004] Currently, BSR only supports reporting the amount of data. However, in order to meet the requirements of some delay-sensitive services for data transmission delay, a delay status reporting (DSR) reporting method is currently proposed to report the relevant delay information of the data to be transmitted, thereby notifying the base station of the transmission delay requirements of the data to be transmitted, so that the base station can reasonably schedule uplink resources. At the same time, DSR can also report the amount of data to be transmitted.

[0005] However, according to the current BSR triggering method and the currently proposed DSR triggering method, if the uplink resources scheduled by the base station for the terminal device are used to send BSR and DSR at the same time, the data amounts reported by the BSR and DSR respectively may contain the same data amount, that is, the BSR and DSR report duplicate data amounts, resulting in a waste of resources. Summary of the invention

[0006] Embodiments of the present application provide a data volume reporting method, device, and readable storage medium for avoiding repeated reporting of the data volume of the same data.

[0007] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0008] In a first aspect, a data volume reporting method is provided, which can be executed by a first device, or by a module (such as a processor, a chip, or a chip system, etc.) applied to the first device. The following is an example of the first device executing the method, and the method includes: the first device triggers a first status report, the first status report includes the data volume and latency information of the first data, and the first data is the data to be transmitted by the first device. The first device triggers a second status report, the second status report includes the data volume of the second data, and the second data is the data to be transmitted by the first device. The first device sends a target status report through a first transmission resource, and the target status report includes the data volume of the first data.

[0009] Based on the data volume reporting method provided in the embodiment of the present application, the first device can send a target status report through the first transmission resource to report the data volume of the first data once when multiple status reports are triggered, thereby avoiding repeated reporting of the data volume of the first data.

[0010] In combination with the above-mentioned first aspect, in a possible design, the target status report is a status report with a higher priority between the first status report and the second status report; wherein the second data includes the first data.

[0011] Based on this solution, the status report with a higher priority can be selected as the target status report according to the respective priorities of the first status report and the second status report, and the other status report does not need to be sent, thereby avoiding repeated reporting of the data volume of the first data.

[0012] In combination with the above-mentioned first aspect, in a possible design, the logical channel multiplexing priority of the first status report is the same as the logical channel multiplexing priority of the second status report, and the second status report is a cache status report.

[0013] Based on this solution, the same logical channel multiplexing priority as that of the buffer status report can be configured for the first status report.

[0014] In combination with the above-mentioned first aspect, in a possible design, the method also includes: the first device obtains first configuration information, the first configuration information is used to configure the first logical channel to report delay information; the first logical channel belongs to the first device.

[0015] Based on this solution, whether to report delay information can be configured for the logical channel.

[0016] In combination with the above-mentioned first aspect, in a possible design, the first data belongs to a second logical channel, the second logical channel is different from the first logical channel, the second status report is triggered by the first data, and the second status report is a cache status report.

[0017] Based on this solution, data in a logical channel that is not configured with reporting delay information can trigger a buffer status report, thereby improving the current buffer status report triggering mechanism.

[0018] In combination with the first aspect, in a possible design, the first data belongs to a first logical channel, wherein:

[0019] The first status report is triggered by the first data; and / or,

[0020] The second status report is triggered by data in a second logical channel, the second logical channel is different from the first logical channel, and the second status report is a buffer status report.

[0021] Based on this solution, by configuring whether the logical channel reports delay information, the first status report and the second status report can be triggered by data in different logical channels respectively, avoiding reporting of repeated data volume due to repeated data triggering the status report.

[0022] In combination with the above-mentioned first aspect, in one possible design, the first data belongs to a first logical channel, and the second data does not include the first data.

[0023] Based on this solution, the first status report triggered by the data in the logical channel configured with reporting delay information can report the data volume and delay information of the data, and the data volume of the data in the logical channel configured with reporting delay information is not reported in the second status report, thereby avoiding repeated reporting of the data volume of the first data in the first status report and the second status report.

[0024] In combination with the above first aspect, in one possible design, the target status report includes a first status report and a second status report.

[0025] Based on this solution, if the second status report does not include the data volume of the first data, the first transmission resource can send the first status report and the second status report at the same time.

[0026] In combination with the first aspect above, in a possible design, the method further includes:

[0027] The first device cancels the triggered second status report.

[0028] Based on this solution, the triggered second status report can be canceled, so that the first transmission resource sends the first status report instead of the second status report, thereby avoiding repeated reporting of the data volume of the first data.

[0029] In combination with the above first aspect, in one possible design, the first status report and the second status report are triggered by the first data.

[0030] Based on this solution, the first status report and the second status report can be triggered by the same data.

[0031] In a second aspect, a data volume reporting method is provided, which can be executed by a first device or by a module (such as a processor, a chip, or a chip system, etc.) applied to the first device. The following is an example of the first device executing the method, and the method includes: the first device obtains third data. When the remaining transmission delay budget of the third data is lower than the first threshold, if the information of the third data has not been reported, the first device triggers a fourth status report, and the fourth status report includes the information of the third data.

[0032] Based on the data volume reporting method provided in the embodiment of the present application, when the remaining transmission delay budget of the third data is lower than the first threshold, it can be further determined whether the information of the third data has been reported. If it has not been reported, the fourth status report can be triggered to report the data volume of the third data. If it has been reported, the fourth status report will not be triggered to avoid repeated reporting of the information of the third data.

[0033] In combination with the above second aspect, in a possible design, before the remaining transmission delay budget of the third data is lower than the first threshold, the method further includes: the first device sends a third status report. If the information of the third data has not been reported, the first device triggers a fourth status report, including: if the third status report does not include the information of the third data, the first device triggers the fourth status report.

[0034] Based on this solution, whether to trigger the fourth status report can be determined by determining whether the third status report sent previously reports the data volume of the third data.

[0035] In combination with the above-mentioned second aspect, in a possible design, the method also includes: the first device obtains second configuration information, the second configuration information is used to configure the reporting delay information of the third logical channel, and the third data belongs to the third logical channel.

[0036] Based on this solution, a logical channel for reporting delay information may be configured, and data in the logical channel configured for reporting delay information may trigger a fourth status report.

[0037] In combination with the above-mentioned second aspect, in a possible design, the method also includes: the first device obtains third configuration information, the third configuration information is used to configure a packet loss timer, the starting time of the packet loss timer is the time when the first device obtains the third data, and when the first packet loss timer times out, the first device discards the third data; the remaining transmission delay budget of the third data is determined based on the packet loss timer.

[0038] Based on this solution, the remaining transmission delay budget of the data can be determined by configuring the packet loss timer.

[0039] On the third aspect, a method for reporting data volume is provided, which can be executed by a second device or by a module (such as a processor, a chip, or a chip system, etc.) applied to the second device. The following is an example of the second device executing the method, and the method includes: the second device sends a first configuration information, and the first configuration information is used to configure the first logical channel to report delay information. The second device receives a target status report through a first transmission resource, and the target status report includes the data volume of the first data. Among them, the first data belongs to a second logical channel, the second logical channel is different from the first logical channel, and the target status report is a cache status report. Alternatively, the first data belongs to the first logical channel, and the target status report also includes the delay information of the first data.

[0040] Based on the data volume reporting method provided in the embodiment of the present application, a logical channel for reporting delay information can be configured, and the data volume and delay information of the data in the logical channel configured for reporting delay information can be reported through a status report, and the data volume of the data in the logical channel not configured for reporting delay information can be reported through a cache status report.

[0041] In combination with the above-mentioned third aspect, in a possible design, the first data belongs to the first logical channel, and the target status report includes a first status report and a second status report; wherein, the first status report includes the data volume and delay information of the first data, the second status report includes the data volume of the second data, and the second data does not include the first data.

[0042] Based on this solution, if the first data belongs to the first logical channel, the data volume and delay information of the first data can be reported through the first status report, and the data volume of the second data excluding the first data can be reported through the second status report. Therefore, the first transmission resource sends the first status report and the second status report at the same time, and the data volume of the first data will not be reported repeatedly.

[0043] In combination with the third aspect above, in a possible design, the delay information of the first data is the remaining transmission delay budget of the first data.

[0044] In combination with the above-mentioned third aspect, in a possible design, the method also includes: the second device sends third configuration information, the third configuration information is used to configure a packet loss timer, the starting time of the packet loss timer is the arrival time of the first data, when the first packet loss timer times out, the first data is discarded; the remaining transmission delay budget of the first data is determined based on the packet loss timer.

[0045] Based on this solution, the remaining transmission delay budget of the data can be determined by configuring the packet loss timer.

[0046] In a fourth aspect, a communication device is provided for implementing various methods. The communication device includes a module, unit, or means corresponding to the implementation method, and the module, unit, or means can be implemented by hardware, software, or by hardware executing the corresponding software implementation. The hardware or software includes one or more modules or units corresponding to the function.

[0047] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module may be used to implement the processing function in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a sending module, respectively used to implement the receiving function and the sending function in any of the above aspects and any possible implementations thereof.

[0048] In some possible designs, the transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface.

[0049] In a fifth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method described in any one of the aspects.

[0050] In a sixth aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface is used to communicate with a module outside the communication device; the processor is used to execute a computer program or instruction so that the communication device executes the method described in any aspect.

[0051] In a seventh aspect, a communication device is provided, comprising: at least one processor; the processor is used to execute a computer program or instruction stored in a memory, so that the communication device performs the method described in any aspect. The memory may be coupled to the processor, or may be independent of the processor.

[0052] In an eighth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored, and when the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the aspects.

[0053] In a ninth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute the method described in any one of the aspects.

[0054] In a tenth aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided, wherein the communication device includes a processor for implementing the functions involved in any aspect.

[0055] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0056] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0057] The communication device provided in any one of the fourth to tenth aspects may be the first device in the first or second aspect, or a device included in the first device, such as a chip or a chip system; or, the communication device may be the second device in the third aspect, or a device included in the second device, such as a chip or a chip system.

[0058] It can be understood that when the communication device provided in any one of the fourth to tenth aspects is a chip, the sending action / function of the communication device can be understood as output information, and the receiving action / function of the communication device can be understood as input information.

[0059] Among them, the technical effects brought about by any design method in the fourth to tenth aspects can refer to the technical effects brought about by different design methods in the first to third aspects, and will not be repeated here.

[0060] In an eleventh aspect, a communication system is provided, the communication system comprising a first device and a second device, wherein the first device is used to implement the method described in the first or second aspect, and the second device is used to implement the method described in the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 It is a schematic diagram of the structure of BSR and DSR;

[0062] Figure 2 Schematic diagram of BSR and DSR repeatedly reporting the same amount of data;

[0063] Figure 3 Schematic diagram of repeatedly reporting the same amount of data for different DSRs;

[0064] Figure 4 A schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0065] Figure 5 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0066] Figure 6 An interactive schematic diagram of a data volume reporting method provided in an embodiment of the present application;

[0067] Figure 7 A schematic diagram of a method for triggering status reporting provided in an embodiment of the present application;

[0068] Figure 8A schematic diagram of another method for triggering status reporting provided in an embodiment of the present application;

[0069] Fig. 9 A schematic diagram of a stored duration provided in an embodiment of the present application;

[0070] Fig.10 A schematic diagram of the duration of a remaining transmission delay budget provided in an embodiment of the present application;

[0071] Fig.11 A schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] In order to facilitate understanding of the technical solutions of the embodiments of the present application, a brief introduction to the related technologies of the present application is first given as follows.

[0073] 1. BSR:

[0074] In the uplink transmission scenario, the terminal device can send a BSR to the network device to report the amount of uplink data to be sent. The network device can allocate reasonable uplink resources to the terminal device based on the BSR to implement uplink scheduling.

[0075] At present, a terminal device can be configured with multiple logical channel groups (LCGs), for example, 8, and each LCG can include several logical channels (LCHs). When configuring the parameters of LCH for each terminal device, such as through a radio resource control (RRC) message, the base station can configure the LCG group corresponding to the LCH for the LCH through signaling.

[0076] BSR usually reports the amount of data on the LCH included in the LCG with LCG as the granularity. Currently, BSR is a media access control (MAC) control element (CE), so it can also be called BSRMACCE. BSR has multiple formats. Currently, long BSR (longBSR) can report the amount of data to be transmitted on multiple LCGs respectively, and short BSR (shortBSR) can report the amount of data to be transmitted on one LCG.

[0077] Figure 1 (a) is a schematic diagram of a typical long BSRMACCE format. Figure 1 As shown in (a) of FIG. 1 , the first byte of the BSR, i.e., the first 8 bits, constitute an 8-bit bitmap, where each bit corresponds to an LCG (e.g. Figure 1LCG0-LCG7) shown in (a) of FIG. 1 is used to indicate whether the BSR includes the data volume of the corresponding LCG, or whether the data volume of the LCG is reported in the BSR. If the BSR includes the data volume of the LCG, the BSR may also include a buffer size field (or word field) for indicating the data volume of the LCG. The size of the BufferSize field is usually 1 byte. Figure 1 As shown in (a), when the BSRMAC CE has m LCGs to transmit data, that is, when any m bits in the 8-bit bitmap indicate that the BSR includes the amount of data of the corresponding LCG, the BSRMACCE also includes m BufferSize fields, and the size of the BSRMACCE is m+1 bytes.

[0078] In addition, the BSRMACCE of the short BSR format may include one byte, such as Figure 1 As shown in (b), the first 3 bits of the byte can indicate the LCGID to indicate the amount of data of which LCG the BSRMACCE reports, and the last 5 bits can be the BufferSize field to indicate the amount of data to be transmitted on the LCG.

[0079] Currently, there are multiple ways to trigger BSR, which are introduced below.

[0080] Trigger mode 1: BSR is triggered when any of the following conditions is met:

[0081] New data has arrived on an LCH in an LCG, and new uplink data is available to the MAC entity, and the priority of this LCH is higher than the priority of any other LCH with data to be transmitted.

[0082] Alternatively, when new data arrives for an LCH in a certain LCG, the new uplink data is available to the MAC entity, and any LCH in any other LCG has no uplink data to send.

[0083] The data being available to the MAC entity may be understood as the data being usable, obtained, or allocated by the MAC entity. For example, the MAC entity may multiplex the data into a MAC PDU.

[0084] Trigger method 2: The base station configures a retransmission BSR timer (retxBSR-timer) for the terminal device through signaling. This timer is used to prevent the terminal device from waiting for uplink resources and causing delays after the base station fails to allocate corresponding uplink resources after sending the BSR. After the timer expires, the BSR will be triggered.

[0085] The BSR triggered based on the above triggering mode 1 or triggering mode 2 is usually called a regular BSR (regular BSR).

[0086] In addition, if uplink resources, such as an uplink MAC protocol data unit (PDU), can completely accommodate the BSR MAC CE and its corresponding MAC CE header after multiplexing according to the logical channel multiplexing priority, the retransmission BSR timer will also be started or restarted.

[0087] Among them, the logical channel multiplexing priority is used to determine the order of multiplexing into the uplink resources. When the terminal device decides which signaling or data an uplink resource can carry, it can multiplex the signaling or data into the uplink resource according to the order of the logical channel multiplexing priority of the signaling or data.

[0088] Triggering method three: the base station configures a periodic BSR timer (periodicBSR-Timer) for the terminal device through RRC signaling. After the timer expires, the BSR will be triggered.

[0089] The BSR triggered based on the above triggering mode 3 is usually called a periodic BSR (periodic BSR).

[0090] In addition, when the terminal device triggers and reports a regular BSR due to other reasons, the periodic BSR timer will be reset.

[0091] Trigger mode 4: After the terminal device fills the MAC PDU according to the logical channel multiplexing priority of MACCE and data, if the number of remaining bits of the MAC PDU is greater than or equal to a BSR MACCE and the sub-header size of the BSR MACCE, the BSR is triggered and the terminal device can transmit the BSR through the remaining bits of the MAC PDU.

[0092] The BSR triggered based on the above trigger mode 4 is usually called a padding BSR (padding BSR).

[0093] The above-mentioned conventional BSR, periodic BSR and padding BSR can be understood as logically different BSRs, and their names are determined based on their respective different triggering methods. It can be understood that the classification of BSRs based on the triggering method and the classification of BSRs based on the format are classifications of BSRs from different dimensions, and the format of BSR is irrelevant to the triggering method of BSR.

[0094] The format of the BSR can be determined based on the following methods:

[0095] When assembling / generating MAC PDU, MAC PDU contains BSRMACCE, and BSRMACCE is triggered by regular BSR or periodic BSR. If there is more than one LCG with data to be transmitted at this time, a long BSRMACCE is sent, which includes the data amount of all LCGs with data to be transmitted, otherwise a short BSRMACCE is sent.

[0096] When the BSRMACCE contained in the MACPDU is triggered by a padding BSR, if the amount of remaining bit data is greater than the long BSRMACCE and the sub-packet header size of the BSRMACCE, the long BSRMACCE is reported; if the amount of remaining bit data is equal to the short BSRMACCE and the sub-packet header size of the short BSRMACCE, and if there is only one LCG with data to be transmitted, the short BSRMACCE is reported; if the amount of remaining bit data is equal to the short BSRMACCE and the sub-packet header size of the short BSRMACCE, and if there is more than one LCG with data to be transmitted, the short truncated BSRMACCE is reported; if the amount of remaining bit data is greater than the short BSRMACCE and the sub-packet header size of the short BSRMACCE and less than the long BSRMACCE and the sub-packet header size of the long BSRMACCE, and if there is more than one LCG with data to be transmitted, the long truncated BSRMACCE is reported.

[0097] The format of the short truncated BSRMACCE is the same as the short BSRMACCE format, such as Figure 1 As shown in (b) of the figure, the content of its sub-packet header, such as the logical channel identity (LCID), is different from the sub-packet header content of the short BSRMACCE ( Figure 1 The sub-packet headers of the short BSRMACCE and the long BSRMACCE are not shown). The format of the long truncated BSRMACCE is the same as the long BSRMACCE format, such as Figure 1 As shown in (a), the content of its sub-packet header is different from that of the long BSRMACCE, and the LCG to which the data contained in the long truncated BSR belongs is reported in descending order according to the priority of the LCG. The priority of the LCG can be determined according to the priority of the LCH in the LCG. When the priorities of the LCGs are the same, they are sorted in ascending order according to the logical channel group identity (LCGID).

[0098] 2. Delay status reporting (DSR):

[0099] The traditional BSR only reports the amount of data, but for some delay-sensitive services, such as extended reality (XR) services, there are stringent requirements for the delay of air interface transmission. Since the base station cannot obtain the delay information of the data based on the traditional BSR, its scheduled resources may not enable the data to be transmitted within the required air interface time, which not only wastes the resources of air interface transmission, but also affects the user experience. Therefore, a solution is currently proposed: a report indicating the delay information of the data to be transmitted can be reported by the terminal device, thereby notifying the base station of the transmission delay requirement of the data to be transmitted. This report carrying the delay information of the data to be transmitted can be called DSR. It should be noted that DSR is only an exemplary name currently provided temporarily, and the report carrying the delay information of the transmission data may also have other names.

[0100] Optionally, the DSR may also indicate the amount of data to be transmitted. It is understandable that if the DSR can simultaneously indicate the amount of data to be transmitted and the delay information of the data to be transmitted, the DSR may also be understood as a BSR that expands new functions based on the original functions.

[0101] At present, the delay information of the data to be transmitted reported by the DSR may specifically be the remaining transmission delay budget of the data, or may be information such as the storage duration or transmission time point of the data to be transmitted, and the embodiments of the present application do not limit this.

[0102] In addition, the end time of the stored duration may be the current time of the transmission system, that is, the stored duration is updated (such as increased) according to the operation of the system. The unit of the stored duration may be any time unit, such as milliseconds, or may be based on communication-related units, such as the number of time slots, the number of subframes, the number of system frames, etc., which is not limited in this article.

[0103] At present, the conditions required to trigger DSR have not been determined. The following introduces several possible ways to trigger DSR. It can be understood that DSR may also be triggered by other methods. The embodiments of the present application do not limit the method of triggering DSR.

[0104] Triggering method 1: triggering DSR based on the delay information of the data to be transmitted. One possible implementation method is to trigger DSR when the delay information of the data to be transmitted reaches a certain threshold. For example, when the stored duration of the data to be transmitted reaches (equal to or greater than) a certain threshold, DSR is triggered. For another example, when the remaining transmission delay budget of the data to be transmitted reaches (equal to or lower than) a certain threshold, DSR is triggered.

[0105] Triggering method 2: triggering DSR based on the amount of data to be transmitted: A possible implementation method is to trigger DSR when the amount of data in a certain LCH or LCG reaches (equal to or greater than) a certain threshold.

[0106] Currently, it is not specified which data's delay information (or delay information and related data volume) may be included in the DSR. In one possible implementation, a DSR triggered by data in any LCH / LCG may report the delay information (or delay information and related data volume) of the data in the LCH / LCG that triggered the DSR, and optionally, may also report the delay information (or delay information and related data volume) of data in other LCH / LCGs.

[0107] Currently, it is not specified how DSR reports the delay information (or delay information and data volume) of the data to be transmitted. In a possible implementation, similar to BSRMACCE, DSR can also be a MACCE, which can be called DSRMACCE.

[0108] For example, Figure 1 (c) is a schematic diagram of the format of DSRMACCE ( Figure 1 (c) in FIG. 1 does not show the packet header of DSRMACCE). The first byte of DSRMACCE, i.e., the first 8 bits (e.g. Figure 1 The delayindex0-delayindex7 shown in (c) constitutes an 8-bit bitmap, in which each bit corresponds to a time interval. Taking the time interval indicating the remaining transmission delay budget as an example, the remaining delay budget corresponding to the data to be transmitted is recorded as x, and the time intervals corresponding to delayinde0-delayindex7 can be shown in the following Table 1:

[0109] Table 1

[0110] delayindex The time interval where x is located 0 x≤5ms 1 x≤10ms 2 x≤15ms 3 x≤20ms 4 x≤25ms 5 x≤30ms 6 x≤35ms 7 x>35ms

[0111] In combination with Table 1 above, delayindex0 can indicate whether the DSRMACCE includes the data volume of data with a remaining transmission delay budget less than or equal to 5ms, delayindex1 can indicate whether the DSRMACCE includes the data volume of data with a remaining transmission delay budget greater than 5ms and not exceeding 10ms, delayindex2 can indicate whether the DSRMACCE includes the data volume of data with a remaining transmission delay budget greater than 10ms and not exceeding 15ms, and the remaining delayindexes can be deduced by analogy. In addition, delayindex7 can indicate whether the DSRMACCE includes the data volume of data with a remaining transmission delay budget greater than 35ms.

[0112] When delayindex indicates that DSRMACCE includes the amount of data corresponding to the remaining transmission delay budget, DSRMACCE includes a field indicating the amount of data (such as Figure 1 For example, when delayindex0 indicates that the DSRMACCE includes the amount of data whose remaining transmission delay budget is less than or equal to 5 ms, the DSRMACCE includes the Buffer Size field corresponding to delayindex0, such as the Buffersize1 field. The Buffersize1 field is used to indicate the amount of data whose remaining transmission delay budget is less than 5 ms. Figure 1 As shown in (c), when there are m delayindex fields indicating that DSRMACCE includes the amount of data corresponding to the remaining transmission delay budget, DSRMACCE includes m BufferSize fields: BufferSize1-BufferSizem. Assuming that a BufferSize field includes 1 byte, DSRMACCE includes m+1 bytes: byte 2, byte 3, ... byte m+1.

[0113] For example, Figure 1 (d) is another format diagram of DSRMACCE ( Figure 1 (d) in FIG. 1 does not show the packet header of DSRMACCE). The first byte of DSRMACCE includes 8 bits, each bit corresponding to an LCG (such as Figure 1 LCG0-LCG7) shown in (d) in the figure is used to indicate whether the DSRMACCE contains the amount of data in the corresponding LCG. For example, if the bit corresponding to LCG0 is '1', the DSRMACCE contains the amount of data in LCG0. At this time, the DSRMACCE contains relevant information for indicating the amount of data in LCG0 and delay information. The indication method can be referred to Figure 1 Therefore, Figure 1 The DSRMACCE shown in (d) in FIG. 1 can be understood as follows: when a bit in the first byte of the DSRMACCE indicates that the corresponding LCG has data volume to report, the byte indicating the delay information corresponding to the LCG (such as Figure 1 The delayinde0-delayindex7) and the field indicating the amount of data (such as Figure 1 BufferSize0-BufferSizem) shown in (d) appears in the DARMACCE, otherwise it does not appear.

[0114] Based on the above introduction to BSR and DSR, in some cases, the terminal device may face the problem that the BSR and DSR report the same amount of data, resulting in a waste of resources. For example, if the DSR reports the amount of data to be transmitted and the delay information, in some cases, the BSR and DSR may report the same amount of data, resulting in a waste of resources. Figure 2 FIG. 1 is a schematic diagram of a possible situation where the BSR and DSR report the same amount of data. Figure 2 As shown, when data 1 arrives at an LCH, a BSR may be triggered based on trigger mode 1, and the BSR includes the data volume of data 1. Data 1 may trigger a DSR after a period of time. For example, after 5ms, the remaining transmission delay budget of the data is less than the preset threshold and triggers the DSR, or the stored time exceeds the preset threshold and triggers the DSR. The DSR triggered by data 1 includes the data volume and delay information of data 1. The time domain position of the uplink resource scheduled by the base station is after the DSR is triggered. Therefore, the terminal device can send BSR and DSR at the same time through the uplink resource (such as MAC PDU), that is, the uplink resource may include both BSR and DSR. At this time, both BSR and DSR include the data volume of data 1, that is, the data volume of data 1 is repeatedly reported, resulting in resource waste.

[0115] It is understandable that the problem of repeated reporting of data volume will not only occur when the same data triggers BSR and DSR, but may also occur in other situations. For example, data from a certain LCH in LCG0 triggers BSR, while data from a certain LCH in LCG1 triggers DSR. Assuming that the terminal device decides to report a long BSR and DSR, since the long BSR includes the data volume of the data to be transmitted on all LCGs, the long BSR also includes the data volume contained in the DSR, resulting in repeated reporting of the data volume of some data, wasting transmission resources.

[0116] In addition, the problem of repeated reporting of data volume leading to resource waste may also occur when the terminal device sends multiple DSRs. Figure 3 As shown, data 1( Figure 3At time t1, data 2 triggers DSR1 (for example, the remaining transmission delay budget of data 1 is less than a certain threshold), and data 2 arrives at the terminal device at time t2. At time t3, the terminal device sends DSR1 through uplink resource 1 scheduled by the base station. DSR1 includes the data volume of data 1 and data 2 and the delay information of data 1 and data 2 at this time. At time t4, data 2 triggers DSR2 (for example, the remaining transmission delay budget of data 2 is less than a certain threshold). At time t5, the terminal device sends DSR2 through uplink resource 2 scheduled by the base station. DSR2 includes the data volume of data 2 and the delay information of data 2 at this time, and may also include the data volume and delay information of data 1. It can be seen that DSR1 and DSR2 repeatedly report the data volume of the same data.

[0117] In order to solve the problem that different status reports may repeatedly report data volume, the embodiments of the present application provide a data volume reporting method, device and system. The technical solution in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application.

[0118] Among them, in the description of the present application, 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 the present application is only a kind of association relationship describing 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, 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 its 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, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solution of the embodiment of the present application, in the embodiment of the present application, the words "first" and "second" are used to distinguish the same or similar items with basically the same functions and effects. Those skilled in the art will appreciate 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. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding.

[0119] In the embodiment of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information (such as the first indication information or the second indication information below) is called information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved by means of the arrangement order of each information agreed in advance (such as specified by the protocol), thereby reducing the indication overhead to a certain extent. At the same time, the common parts of each information can also be identified and indicated uniformly to reduce the indication overhead caused by indicating the same information separately.

[0120] In addition, the specific indication method may also be various existing indication methods, such as but not limited to the above-mentioned indication methods and various combinations thereof. The specific details of the various indication methods can refer to the prior art and will not be repeated herein. As can be seen from the above, for example, when it is necessary to indicate multiple information of the same type, different indication methods may be used for different information. In the specific implementation process, the desired indication method can be selected according to specific needs. The embodiment of the present application does not limit the selected indication method. In this way, the indication method involved in the embodiment of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the information to be indicated.

[0121] It should be understood that the information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in the embodiment of the present application. Among them, the sending period and / or sending time of these sub-information can be pre-defined, for example, pre-defined according to a protocol, or can be configured by the sending end device by sending configuration information to the receiving end device.

[0122] In an embodiment of the present application, "pre-definition", "pre-definition", "pre-configuration" or "pre-configuration" can be implemented by pre-saving the corresponding code, table or other methods that can be used to indicate relevant information in the device. For example, it can be burned into the device when the device leaves the factory. The embodiment of the present application does not limit its specific implementation method. Among them, "saving" can mean saving in one or more memories. The one or more memories can be set separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories can also be partially set separately and partially integrated in a decoder, a processor, or a communication device. The type of memory can be any form of storage medium, which is not limited by the embodiment of the present application.

[0123] The "protocol" involved in the embodiments of the present application may refer to a protocol family in the communication field, a standard protocol with a similar protocol family frame structure, or a related protocol used in future communication systems, and the embodiments of the present application do not make specific limitations on this.

[0124] In the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that the device will make corresponding processing under certain objective circumstances. It does not limit the time, nor does it require the device to have a judgment action when implementing it, nor does it mean that there are other limitations.

[0125] The technical solution provided in the present application can be used in various communication systems, which may be a third generation partnership project (3GPP) communication system, for example, a fourth generation (4G) long term evolution (LTE) system, a fifth generation (5G) mobile communication system and its evolution system, a vehicle to everything (V2X) system, a LTE and new radio (NR) hybrid networking system, or a device to device (D2D) system, a machine to machine (M2M) communication system, an Internet of Things (IoT), and other next generation communication systems.

[0126] It should be noted that the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0127] Figure 4 A possible, non-limiting system diagram is provided for the embodiments of the present application. Figure 4 As shown, the communication system 10 includes a second device 20 and a first device 30. The second device 20 can communicate with the first device 30 in a wireless manner.

[0128] Understandably, Figure 4 It is only a schematic diagram and does not limit the number of the second devices 20 or the first devices 30 in the communication system 10 . The communication system 10 may include at least one second device 20 and at least one first device 30 .

[0129] Optionally, different second devices 20 can communicate with each other. Optionally, different first devices 30 can communicate with each other. The second device 20 and / or the first device 30 can be fixed or movable.

[0130] by Figure 4 Taking the interaction between the second device 20 shown and any first device 30 as an example, in one possible design, the first device 30 triggers a first status report, the first status report includes the data volume and latency information of the first data, and the first data is the data to be transmitted by the first device. In addition, the first device 30 triggers a second status report, and the second status report includes the data volume of the second data, and the second data is the data to be transmitted by the first device. The first device 30 sends a target status report to the second device 20 through the first transmission resource, and the target status report includes the data volume of the first data. The specific implementation and technical effects of this solution will be described in detail in the subsequent method embodiments, and will not be repeated here.

[0131] by Figure 4 Taking the interaction between the second device 20 and any first device 30 as an example, in another possible design, the first device 30 sends a third status report to the second device 20. When the remaining transmission delay budget of the third data is lower than the first threshold, if the third status report does not include the data volume of the third data, the first device 30 triggers a fourth status report, and the fourth status report includes the data volume of the third data. The specific implementation and technical effects of this solution will be described in detail in the subsequent method embodiments, and will not be repeated here.

[0132] Optionally, the second device 20 and the first device 30 in the embodiment of the present application can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on an airplane, balloon, or artificial satellite in the air. The embodiment of the present application does not limit the application scenarios of the second device 20 and the first device 30.

[0133] Optionally, the second device 20 and the first device 30 in the embodiment of the present application can communicate through a licensed spectrum, or can communicate through an unlicensed spectrum (also referred to as an unlicensed spectrum), or can communicate through both a licensed spectrum and an unlicensed spectrum. The second device 20 and the first device 30 can communicate through a spectrum below 6 gigahertz (GHz), or can communicate through a spectrum above 6 GHz, or can use a spectrum below 6 GHz and a spectrum above 6 GHz at the same time. The embodiment of the present application does not limit the spectrum resources used between the second device 20 and the first device 30.

[0134] Optionally, the second device 20 in the embodiment of the present application may be a network device. The first device 30 may be a terminal device.

[0135] Optionally, the network device in the embodiment of the present application is a device that connects a terminal device to a wireless network. The network devices in the embodiments of the present application may include various forms of base stations, for example, macro base stations, micro base stations (also called small stations), relay stations, access points, transmitting points (TP), evolved NodeBs (eNBs), transmission reception points (TRPs), next generation NodeBs (gNBs) in 5G mobile communication systems, devices that implement base station functions in communication systems that evolve after 5G, mobile switching centers, and devices that perform base station functions in device-to-device (D2D), V2X, and machine-to-machine (M2M) communications, etc.; it may also be a network device in a non-terrestrial network (NTN) communication system, that is, it may be deployed on a high-altitude platform or a satellite; it may also be a module or unit that completes part of the functions of a base station, for example, it may be a centralized unit (CU) in a cloud radio access network (C-RAN) system, or it may be a distributed unit (DU). The embodiments of the present application do not limit the specific technology and specific device form used by the network device. All or part of the functions of the network device can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). In this application, unless otherwise specified, the network device refers to the radio access network (RAN) device.

[0136] Optionally, the terminal device in the embodiment of the present application may be a device with wireless transceiver function, which may also be referred to as a terminal. The terminal device may specifically refer to user equipment (UE), access terminal, subscriber unit, user station, mobile station, customer-premises equipment (CPE), remote station, remote terminal, mobile device, mobile terminal, user terminal, wireless communication device, user agent or user device, etc. The terminal device can also be a satellite phone, a cellular phone, a smart phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless data card, a wireless modem, a tablet computer, a computer with wireless transceiver function, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a smart point of sale (POS) machine, a machine type communication device, a terminal device in D2D, a vehicle-mounted terminal device in V2X, an onboard unit (onboard unit, OBU), on-board communication terminal (telematics box, T-box), whole vehicle or roadside unit (roadside unit, RSU), virtual reality (virtual reality, VR) terminal equipment, augmented reality (augmented reality, AR) terminal equipment, wireless terminal in industrial control (industrial control), wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid (smart grid), wireless terminal in transportation safety (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home) or terminal equipment in future communication network, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device. For example, the terminal device can also be a chip or module. All or part of the functions of the terminal device can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).

[0137] Optionally, the first device 30 or the second device 20 may adopt Figure 5 The structure of the communication device 500 is shown. Figure 5 As shown, the communication device 500 includes a processor 501, a communication line 502, and at least one communication interface ( Figure 5 The communication interface 504 is used as an example for illustration only). Optionally, the communication device 500 may further include a memory 503.

[0138] The processor 501 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0139] Communication link 502 may include a pathway for transmitting information between the above-mentioned components.

[0140] The communication interface 504 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0141] The memory 503 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or 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 a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a communication line 502. The memory may also be integrated with the processor.

[0142] The memory 503 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 501. The processor 501 is used to execute the computer-executable instructions stored in the memory 503, thereby implementing the method provided in the following embodiments of the present application.

[0143] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code or computer program code, which is not specifically limited in the embodiments of the present application.

[0144] In a specific implementation, as an embodiment, the processor 501 may include one or more CPUs, such as Figure 5 CPU0 and CPU1 in.

[0145] In a specific implementation, as an embodiment, the communication device 500 may include multiple processors, such as Figure 5 501 and processor 508 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0146] In a specific implementation, as an embodiment, the communication device 500 may further include an output device 505 and an input device 506. The output device 505 communicates with the processor 501 and may display information in a variety of ways. For example, the output device 505 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 506 communicates with the processor 501 and may receive user input in a variety of ways. For example, the input device 506 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0147] Understandably, Figure 5 The structure shown does not constitute a specific limitation on the communication device 500. For example, in other embodiments of the present application, the communication device 500 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0148] The following will be combined Figures 4 to 5 ,by Figure 4 Taking the interaction between the second device 20 shown and any first device 30 as an example, the data volume reporting method provided in the embodiment of the present application is described in detail.

[0149] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of the present application are merely examples, and other names may be used in specific implementations, and the embodiments of the present application do not impose any specific limitations on this.

[0150] It should be noted that the granularity, size or unit of the data appearing in the following embodiments of the present application is not limited. Among them, the data may be a data unit, or may include multiple data units. For example, the data appearing in the following embodiments of the present application may be a service data unit (service data unit, SDU), or a PDU, or a protocol data unit group (PDUset), or a data burst (databurst). Among them, the PDU is composed of the SDU and the header of the corresponding layer, such as the packet data convergence layer protocol (packet data convergence protocol, PDCP) PDU is obtained by adding the PDCP header to the PDCP SDU through the PDCP layer. PDUset includes at least one PDU, and these PDUs carry information units generated by an application (or application layer). For example, a video frame has a large amount of data and usually needs to be divided into multiple PDUs for transmission. These multiple PDUs can constitute a PDUset. A data burst can be understood as a group of PDUs generated and sent by an application (or application layer) in a short period of time. These PDUs can come from one or more PDUsets.

[0151] It should be noted that the durations appearing in the following embodiments of the present application, such as effective transmission duration, stored duration, or remaining transmission delay budget, can be time units such as seconds and milliseconds, or communication time units such as time slots, subframes, system frames, or a combination of these two units. The embodiments of the present application do not impose any restrictions on this.

[0152] like Figure 6 As shown, a method for reporting data volume provided in an embodiment of the present application is provided. Figure 6 In the example, the first device and the second device are used as the execution subjects of the interaction diagram to illustrate the method, but the present application does not limit the execution subjects of the interaction diagram. Figure 6 The first device in the description may also be a module applied to the first device, such as a chip, a chip system, or a processor, or may be a logical node, a logical module, or software that can implement all or part of the functions of the first device node; Figure 6 The second device in the data volume reporting method may also be a module applied to the second device, such as a chip, a chip system, or a processor, or a logical node, a logical module, or software that can realize all or part of the functions of the second device. The data volume reporting method includes the following steps:

[0153] S601. A first device triggers a first status report, where the first status report includes data volume and latency information of first data, where the first data is data to be transmitted by the first device.

[0154] S602: The first device triggers a second status report, where the second status report includes a data volume of second data, where the second data is data to be transmitted by the first device.

[0155] S603: The first device sends a target status report through the first transmission resource, where the target status report includes the data volume of the first data. Correspondingly, the second device receives the target status report through the first transmission resource.

[0156] It should be noted that Figure 6 The timing between S601 and S602 shown is only an exemplary possible timing, and the embodiment of the present application does not limit the timing between S601 and S602. Optionally, S601 may occur before S602, that is, the first device may first trigger the first status report and then trigger the second status report. Alternatively, S601 and S602 may occur simultaneously, that is, the first device may simultaneously trigger the first status report and the second status report. Alternatively, S602 may occur before S601, that is, the first device may first trigger the second status report and then trigger the first status report.

[0157] Based on the data volume reporting method provided in the embodiment of the present application, when multiple status reports are triggered, the data volume of the first data can be reported by one status report, thereby avoiding repeated reporting of the data volume of the first data.

[0158] The following is an introduction to S601-S603 respectively.

[0159] In S601, optionally, the first status report may also include delay information and data volume of other data.

[0160] Among them, after the first status report is triggered, the data volume and delay information included in the triggered first status report can be determined by the first device according to the data volume and delay information of the current data and the preset rules when the resource that can be used to send the first status report (in the embodiment of the present application, the resource is the first transmission resource, which will not be introduced here) arrives. For example, assuming that it is pre-specified that the first status report can report the data volume and delay information of the data in any LCH, after the first status report is triggered, when the first device assembles / generates the MAC PDU, it determines that there is data to be transmitted on both LCH1 and LCH2, then the triggered first status report includes the data volume and delay information of the data on the current LCH1, and the data volume and delay information of the data on the current LCH2. For another example, assuming that it is pre-specified that the first status report can report the data volume and latency information of the data in LCG1, after the first status report is triggered, the first device determines that there is data to be transmitted on both LCH1 and LCH2 when assembling / generating MAC PDU, where LCH1 belongs to LCG1 and LCH2 belongs to LCG2. Then the triggered first status report includes the data volume and latency information of the data on the current LCH1.

[0161] In an embodiment of the present application, the data delay information included in the status report (such as the first status report) can be used to indicate the transmission delay requirement of the data. Exemplarily, the data delay information included in the first status report can be information such as the storage duration of the data, the remaining transmission delay budget of the data, or the transmission time point of the data, which is not limited by the embodiment of the present application. Among them, the transmission time point of the data is a certain time point that can determine the data transmission delay requirement. For example, it can be the time point corresponding to the time when the remaining transmission delay budget of the data times out (it can also be understood as the end time of the transmission delay budget of the data). The transmission time point of the data can be an absolute time point, such as a few minutes and seconds, or it can be a communication time point such as a system frame number (system frame number, SFN), a subframe number (frame number), a time slot number (slot number), etc.

[0162] The specific definitions of the remaining transmission delay budget and the stored duration will be introduced in detail later and will not be expanded here.

[0163] It should be noted that the embodiments of the present application do not limit how the status report (for example, the first status report, the second status report hereinafter) reports the latency information and / or data volume of the data. In other words, the embodiments of the present application do not limit the specific form of the data volume and / or latency information of the data in the status report. It can also be understood that the embodiments of the present application do not limit the structure or format of the status report.

[0164] Exemplarily, the first status report may be a DSR.

[0165] It can be understood that in the embodiment of the present application, DSR is an exemplary name for a status report including latency information of data to be transmitted. In actual applications, the status report including latency information of data to be transmitted may also have other names, and the embodiment of the present application does not limit this.

[0166] It should be noted that the embodiment of the present application does not limit the carrying mode of the status report (e.g., the first status report, the second status report hereinafter). Exemplarily, the status report may be a MACCE (if the status report is a DSR, it may be called a DSRMACCE, if the status report is a BSR, it may be called a BSRMACCE). Alternatively, the status report may also be user assistance information (UEassistance information, UAI). Alternatively, the status report may also be uplink control information (uplinkcontrolinformation, UCI), or the status report may also be carried in other information or signaling.

[0167] The following introduces several possible implementation methods of triggering the first status report provided by the embodiments of the present application. It can be understood that the first status report may also be triggered by other methods. The embodiments of the present application do not limit the method of triggering the first status report.

[0168] Triggering method 1: triggering the first status report based on the delay information of the data to be transmitted. A possible implementation method is to trigger the first status report when the delay information of the data to be transmitted reaches a certain threshold. For example, when the stored duration of the data to be transmitted reaches (equal to or greater than) a certain threshold, the first status report is triggered. For another example, when the remaining transmission delay budget of the data to be transmitted reaches (equal to or lower than) a certain threshold, the first status report is triggered.

[0169] Triggering mode 2: triggering the first status report based on the amount of data to be transmitted: A possible implementation mode is to trigger the first status report when the amount of data in a certain LCH or LCG reaches (equal to or greater than) a certain threshold.

[0170] Among them, optionally, the threshold used to trigger the first status report can be pre-configured in the first device, can be configured by high-level signaling (such as RRC message), or can be pre-defined by the protocol. The embodiment of the present application does not impose any specific restrictions on the way in which the first device obtains the threshold.

[0171] Among them, optionally, if the threshold for triggering the first status report is related to the delay, the unit of the threshold can be any time unit, such as milliseconds, or communication-related units, such as time slots, subframes, system frames, etc., and the embodiments of the present application do not make specific restrictions. When the threshold for triggering the first status report is related to the amount of data, the unit of the threshold can be bits or bytes, etc., and the embodiments of the present application do not make specific restrictions.

[0172] In S602, regarding the amount of second data included in the second status report, optionally, the second data may be data different from the first data (or the second data does not include the first data). Alternatively, the second data may include the first data.

[0173] Optionally, the second status report may further include delay information of the second data.

[0174] In the embodiment of the present application, the data delay information included in the second status report can be used to indicate the transmission delay requirement of the data. Exemplarily, the data delay information included in the second status report can be information such as the storage duration of the data, the remaining transmission delay budget of the data, or the transmission time point of the data, which is not limited in the embodiment of the present application.

[0175] Optionally, the second status report may also include data volume and / or delay information of other data.

[0176] Among them, after the second status report is triggered, the amount of data included in the triggered second status report and the delay information that may be included can be determined by the first device when the resource that can be used to send the second status report (in the embodiment of the present application, the resource is the first transmission resource, which is not introduced in detail here) arrives, according to the current data volume (and may also be based on the delay information of the current data) and preset rules. For details, please refer to the above introduction to the data volume and delay information included in the triggered first status report.

[0177] Exemplarily, the second status report may be a BSR, in which case the second status report does not include the data delay information. Alternatively, the second status report may be a DSR, in which case the second status report includes the data delay information.

[0178] Optionally, if the second status report is a BSR, the method for triggering the second status report may refer to the above introduction to multiple triggering methods of the BSR, which will not be elaborated here.

[0179] Optionally, if the second status report is DSR, the method for triggering the second status report can refer to the above introduction to the triggering method of the first status report, which will not be expanded here.

[0180] In S603, the first transmission resource may be used to send at least one status report (eg, a first status report, a second status report), so as to report the amount of data to be transmitted of the first device.

[0181] The starting time domain position of the first transmission resource may be after the time point of triggering the first status report and the time point of triggering the second status report. After triggering the first status report and the second status report, the first device may determine the target status report based on the triggered first status report and the second status report, and send the target status report through the first transmission resource. The target status report refers to at least one status report sent by the first device through the first transmission resource, including a status report of the data volume of the first data, or in other words, the target status report is used to report the data volume of the first data. Furthermore, in order to avoid reporting duplicate data volumes, the number of target status reports sent by the first transmission resource may be one.

[0182] Optionally, the first transmission resource may be an uplink resource scheduled by the second device for the first device.

[0183] It should be noted that, in the embodiment of the present application, after the first status report is triggered, the first status report includes the data volume of the first data, which means that when the first device determines the target status report to be sent through the first transmission resource, the triggered first status report includes the data volume of the first data. It can be understood that triggering the status report and sending the status report are two steps, and the triggered status report may not necessarily be sent out, for example, the triggered status report may be canceled. Therefore, the triggered first status report includes the data volume of the first data, which does not represent (that is, it cannot be equivalent to) the data volume of the first data reported through the first status report. In addition, if it is determined to send the first status report through the first transmission resource, the first status report may not necessarily report the data volume of the first data, or the first status report sent may not necessarily include the data volume of the first data. For example, the first device can change the data volume originally included in the triggered first status report when assembling / generating the MAC PDU carried in the first transmission resource. Therefore, the triggered first status report includes the data volume of the first data, which can be understood as that when the first device determines the target status report, the triggered first status report logically includes the data volume of the first data, not the data volume of the first data reported in the first status report.

[0184] Similarly, after the first status report is triggered, the first status report includes the latency information of the first data, which does not mean that the first status report reports the latency information of the first data.

[0185] Similarly, after the second status report is triggered, the second status report includes the data volume of the second data, which means that when the first device determines the target status report to be sent through the first transmission resource, the triggered second status report includes the data volume of the second data. It can be understood that the triggered second status report is not necessarily sent through the first transmission resource. Therefore, the triggered second status report includes the data volume of the second data, which does not mean that the data volume of the second data is reported through the second status report. In addition, if it is determined to send the second status report through the first transmission resource, the second status report does not necessarily report the data volume of the second data, or the second status report sent does not necessarily include the data volume of the second data. Therefore, the triggered second status report includes the data volume of the second data, which can be understood as that when the first device determines the target status report, the triggered second status report logically includes the data volume of the second data, not the data volume of the second data reported in the second status report.

[0186] Among them, exemplarily, if the first status report and the second status report are carried by MACCE, the first device can determine the target status report when assembling or generating the MAC PDU carried in the first transmission resource. Among them, the target status report can be understood as the status report determined by the first device to be placed in the MAC PDU (or, multiplexed into the MAC PDU) when assembling or generating the MAC PDU. In other words, the target status report sent through the first transmission resource (or referred to as the target status report included in the first transmission resource) is the status report included in the MAC PDU (or, the status report placed / multiplexed into the MAC PDU). For ease of understanding, the following embodiments of the present application are introduced by taking the first transmission resource used to carry the MAC PDU and the first status report and the second status report carried by the MACCE as an example.

[0187] In the embodiments of the present application, based on different scenarios, the first device may adopt different methods to determine the target status report. Several possible methods for determining the target status report are introduced below.

[0188] Method 1: Determine the target status report based on the priority of the status report.

[0189] In the scenario where the first method is applied, the first transmission resource may include a status report. The first device may select one status report sent via the first transmission resource between the first status report and the second status report, and the status report is the target status report.

[0190] In method 1, when the first device assembles / generates a MAC PDU, the amount of data included in the target status report placed in the MAC PDU is the amount of data included in the triggered first status report or the second status report. For example, if the first device determines that the first status report is the target status report, the target status report placed in the MAC PDU is the first status report, including the amount of data of the first data. Alternatively, if the first device determines that the second status report is the target status report, the target status report placed in the MAC PDU is the second status report, including the amount of data of the second data.

[0191] It can be understood that, since the target status report in the first method can be any status report of the first status report and the second status report, in the scenario where the first method is applied, the second data can include the first data.

[0192] In method 1, priorities can be set for the first status report and the second status report respectively, and the first device can select the status report sent through the first transmission resource according to the priority of the first status report and the priority of the second status report. In other words, the target status report is the status report with a higher priority between the first status report and the second status report.

[0193] Optionally, in the first mode, the priorities set for the first status report and the second status report may be set based on the type of status report, that is, different priorities are set for different types of status reports. In this case, the first status report may be a DSR, and the second status report may be a BSR. Specifically, the second status report may be any one of a regular BSR, a periodic BSR, or a padding BSR.

[0194] Among them, in a possible implementation, different priorities can be set for DSR and BSR respectively. Exemplarily, a higher priority can be set for DSR than BSR. When the first device assembles or generates MAC PDU, if there are triggered BSR and DSR (that is, there are triggered first status report and second status report), the MAC PDU includes DSR but not BSR (that is, the first status report is the target status report sent through the first transmission resource). Conversely, a lower priority can be set for DSR than BSR. When the first device assembles or generates MAC PDU, if there are triggered BSR and DSR, the MAC PDU includes BSR but not DSR (that is, the second status report is the target status report sent through the first transmission resource).

[0195] In addition, if there are multiple triggered BSRs when the first device assembles the MAC PDU, the first device can select the BSR to be placed in the MAC PDU according to the priorities of the existing different types of BSRs. For example, the priorities of different types of BSRs can be set to: the priority of regular BSR and periodic BSR is higher than that of padding BSR.

[0196] In another possible implementation, priorities can be set for DSR and each BSR separately. For example, if DSR, normal BSR, periodic BSR and padding BSR exist at the same time, priorities can be set for these four BSRs. Optionally, DSR can be understood as a type of BSR in this scenario. For example, assuming that DSR is called delayed BSR, there are four types of BSRs: delayed BSR, normal BSR, periodic BSR and padding BSR, and priorities can be set for these four types of BSRs.

[0197] Exemplarily, the priority of DSR can be set higher than that of normal BSR, periodic BSR and padding BSR, and the priority of normal BSR and periodic BSR can be set higher than that of padding BSR. In this case, if there is any one of the triggered normal BSR, periodic BSR or padding BSR and the triggered DSR, the MAC PDU includes DSRMACCE but does not include BSRMACCE corresponding to the normal BSR, periodic BSR or padding BSR.

[0198] For another example, the priority of the padding BSR can be set higher than the priority of the DSR, and the priority of the regular BSR and the periodic BSR can be set higher than the priority of the padding BSR. In this case, if there is a triggered regular BSR or periodic BSR and a triggered DSR, the MAC PDU includes the BSRMACCE corresponding to the regular BSR or periodic BSR, but does not include the DSRMACCE. If there is a triggered padding BSR and a triggered DSR, the MAC PDU includes the BSRMACCE corresponding to the padding BSR, but does not include the DSRMACCE. If there is a triggered regular BSR or periodic BSR, a triggered padding BSR, and a triggered DSR, the MAC PDU includes the MAC CE corresponding to the regular BSR or periodic BSR, but does not include the BSRMACCE and DSRMACCE corresponding to the padding BSR.

[0199] For another example, a priority between the regular BSR and the padding BSR can be set for the DSR, that is, the priority of the regular BSR and the periodic BSR is higher than the priority of the DSR, and the priority of the DSR is higher than the priority of the padding BSR. In this case, if there is a triggered regular BSR or periodic BSR and a triggered DSR, the MAC PDU includes the regular BSR or periodic BSR, but does not include the DSR. If there is a triggered padding BSR and a triggered DSR, the MAC PDU includes the DSRMACCE, but does not include the MACCE corresponding to the padding BSR. If there is a triggered regular BSR or periodic BSR, a triggered padding BSR, and a triggered DSR, the MAC PDU includes the BSRMACCE corresponding to the regular BSR or periodic BSR, but does not include the BSRMACCE corresponding to the padding BSR and the DSR.

[0200] Optionally, the above process of selecting, based on priority, the MACCEs corresponding to the normal BSR, the periodic BSR, the padding BSR and the DSR, respectively, to be multiplexed into the MAC PDU may occur when the first device assembles or generates the MAC PDU.

[0201] Optionally, the priority of the first status report and the second status report may be preconfigured, for example, configured when the first device leaves the factory, or may be configured through semi-static signaling (such as an RRC message), or may be predefined by the protocol, or may be configured in other ways, and the embodiments of the present application are not limited to this.

[0202] Optionally, a logical channel multiplexing priority may also be set for the first status report and / or the second status report. The logical channel multiplexing priority is used to determine the order of multiplexing into the transmission resource (e.g., MAC PDU). Exemplarily, when a MAC PDU needs to include multiple functional MACCEs (e.g., BSR MACCE, MACCE for reporting time advance, etc.), when assembling or generating the MAC PDU, these functional MACCEs need to be placed in the MAC PDU in the order of the logical channel multiplexing priority.

[0203] Optionally, the logical channel multiplexing priority of the second status report may be the same as the logical channel multiplexing priority of any BSR. For example, the logical channel multiplexing priority of the second status report may be the same as the logical channel multiplexing priority of a regular BSR or a periodic BSR, or the logical channel multiplexing priority of the second status report may be the same as the logical channel multiplexing priority of a padding BSR.

[0204] Alternatively, the logical channel multiplexing priority of the second status report may be different from the logical channel multiplexing priority of the BSR. Optionally, the logical channel multiplexing priority of the second status report may be higher than the logical channel multiplexing priority of the BSR, for example, the logical channel multiplexing priority of the second status report may be higher than the logical channel multiplexing priority of the regular BSR, the periodic BSR, and the padding BSR. Alternatively, the logical channel multiplexing priority of the second status report may also be lower than the logical channel multiplexing priority of any BSR, for example, the logical channel multiplexing priority of the second status report may be lower than the logical channel multiplexing priority of the regular BSR, the periodic BSR, and the padding BSR.

[0205] Among them, optionally, the logical channel multiplexing priority of the first status report can be the same as the logical channel multiplexing priority of any BSR, or the logical channel multiplexing priority of the first status report can be different from the logical channel multiplexing priority of the BSR, and the logical channel multiplexing priority of the first status report can be higher than the logical channel multiplexing priority of the BSR, or lower than the logical channel multiplexing priority of the BSR. The specific logical channel multiplexing priority of the first status report can refer to the above introduction to the logical channel multiplexing priority of the second status report, which will not be repeated here.

[0206] The logical channel multiplexing priorities of the first status report and the second status report may be the same, or may be different.

[0207] Optionally, the logical channel multiplexing priority of the first status report or the second status report can be pre-configured, for example, configured when the first device leaves the factory, or it can be configured through semi-static signaling (such as RRC message), or it can be predefined by the protocol, or it can be configured in other ways, and the embodiments of the present application are not limited to this.

[0208] In the first method, the first device determines not to send the status report through the first transmission resource, which can be understood as canceling the sending of the status report, or in other words, canceling the triggered status report.

[0209] Method 2: Reporting the data volume of the first data by using one of the first status report and the second status report.

[0210] In the scenario where the second method is applied, the first transmission resource may include multiple status reports, that is, the first transmission resource may send the first status report and the second status report at the same time. However, in order to avoid repeatedly reporting the data volume of the first data, only one of the first status report and the second status report may report the data volume of the first data, or in other words, the data volume of the first data is reported in one of the first status report and the second status report, and the other status report does not report the data volume of the first data. In this scenario, the target status report may be understood as a status report in the first status report and the second status report that reports the data volume of the first data, or it may be understood that the target status report includes the first status report and the second status report, and one of the status reports reports the data volume of the first data.

[0211] It can be understood that in method 2, the amount of data of the first data reported by one of the first status report and the second status report does not limit the amount of data included in the first status report and the amount of data included in the second status report when the first device assembles / generates the MAC PDU after the first status report and the second status report are triggered.

[0212] In a possible implementation, a logical channel for reporting delay information can be configured (it can also be understood that the logical channel is configured whether to report delay information). If the logical channel is configured to report delay information, the amount of data in the logical channel can be reported in the DSR, and the amount of data in the logical channel is not reported in the BSR. For example, the amount of data in the logical channel is only reported in the DSR. Optionally, the delay information of the data in the logical channel can also be reported in the DSR.

[0213] For ease of introduction, the logical channel configured with reporting delay information is referred to as the first logical channel, and the other logical channels that are different from the first logical channel and are not configured with reporting delay information are referred to as the second logical channel. Furthermore, the amount of data in the second logical channel can be reported in the BSR and not in the DSR. For example, the amount of data in the second logical channel is only reported in the BSR. Therefore, this implementation method can realize that based on the logical channel to which the data belongs, the amount of data is reported through one of the DSR and the BSR, and not in the other.

[0214] Exemplarily, the first device has 2 LCHs: LCH0 and LCH1, wherein LCH0 is configured with reporting delay information and LCH1 is not configured with reporting delay information. If LCH0 triggers DSR and LCH1 triggers BSR, the MAC PDU sent in the first transmission resource may include both BSR and DSR, wherein DSR includes the data amount of data in the LCH (such as LCH0) configured with reporting delay information, and BSR includes the data amount of data in the LCH (such as LCH1) not configured with reporting delay information but does not include the data amount of data in LCH0. For another example, if LCH1 triggers BSR and LCH0 does not trigger DSR, the MAC PDU sent in the first transmission resource may include BSR, but the BSR will not include the data amount of data in LCH0, but will include the data amount of data in the LCH (such as LCH1) not configured with reporting delay information. If at this time, there are multiple LCHs that are not configured with reporting delay information and have data to be transmitted, and these multiple LCHs belong to different LCGs (such as LCH1 and LCH2 that have data to be transmitted are not configured with reporting delay information, and the LCG to which LCH2 belongs is different from the LCG to which LCH1 belongs), the first device reports a long BSR, otherwise it reports a short BSR.

[0215] It should be noted that, in the embodiments of the present application, "LCH triggers BSR or DSR" and similar expressions can be understood as data in the LCH triggering the BSR or DSR, or as data in the LCH satisfying the triggering conditions of the BSR or DSR. In addition, "LCG triggers BSR or DSR" and similar expressions can be understood as data in a certain LCH included in the LCG triggering the BSR or DSR, or as data in a certain LCH included in the LCG satisfying the triggering conditions of the BSR or DSR.

[0216] Similarly, a logical channel that does not report delay information (which may be referred to as a second logical channel) may be configured, and other logical channels that are different from the second logical channel and are not configured not to report delay information may be referred to as first logical channels. Alternatively, a logical channel that reports delay information (which may be referred to as a first logical channel) and a logical channel that does not report delay information (which may be referred to as a second logical channel) may be configured at the same time.

[0217] Optionally, the number of the first logical channel may be one or more. Optionally, the data volume of the second logical channel may also be one or more. The embodiment of the present application does not limit the number of the first logical channel or the second logical channel.

[0218] Among them, whether the logical channel reports delay information can be pre-configured, for example, configured when the first device leaves the factory, or it can be configured through semi-static signaling (such as RRC message), or indicated by a dynamic message (such as MACCE or DCI), or it can be pre-defined by the protocol, or it can be configured in other ways, and the embodiments of the present application do not limit this. Exemplarily, the first device can obtain first configuration information, and the first configuration information is used to configure the first logical channel to report delay information. The first device can determine, based on the first configuration information, that the data in the first logical channel of the multiple logical channels configured by itself needs to report the data volume and delay information through DSR. Among them, optionally, the first configuration information can be sent by the second device to the first device.

[0219] In the above implementation, whether to report the delay information is configured with LCH as the granularity. For example, when the second device configures the parameters of a certain LCH through an RRC message, it configures whether to report the delay information, and the BSR or DSR may report the data volume with LCG as the granularity. Since an LCG may include multiple LCHs, optionally, when configuring the reporting delay information for a certain logical channel, other LCHs in the LCG to which the logical channel belongs can also be configured to report the delay information. Alternatively, when configuring not to report the delay information for a certain logical channel, other LCHs in the LCG to which the logical channel belongs can also be configured not to report the delay information. In other words, each LCH in a certain LCG can be the first logical channel, or each LCH in a certain LCG can be the second logical channel. This optional scheme can also be understood as configuring whether to report the delay information with LCG as the granularity, or the LCG is configured whether to report the delay information. That is to say, in this optional solution, when an LCG is configured to report delay information, it can be understood that any LCH in the LCG is configured to report delay information, and it can also be understood that all LCHs in the LCG are configured to report information. On the other hand, in this optional solution, when an LCH is configured to report delay information, it can be understood that the LCG to which the LCH belongs is configured to report delay information.

[0220] Optionally, in the scenario where the second mode is applied, the first status report may be a DSR, and the second status report may be a BSR. It is understandable that, regardless of whether the first data belongs to the first logical channel or the second logical channel, the data volume of the first data may be reported in one of the first status report and the second status report, but not in the other status report.

[0221] Specifically, if the first data belongs to the first logical channel, the data volume of the first data can be reported in the first status report, and the data volume of the first data is not reported in the second status report. In this case, the triggered first status report including the data volume of the first data can be used as a target status report, placed in the MAC PDU and sent through the first transmission resource. Optionally, if the second data does not include the first data, the triggered second status report including the data volume of the second data can also be placed in the MAC PDU and sent through the first transmission resource. In other words, in this case, the second data is data different from the first data (or, the second data does not include the first data). Optionally, the delay information of the first data can also be reported in the first status report.

[0222] If the first data belongs to the second logical channel, the data volume of the first data may be reported in the second status report, and the data volume of the first data is not reported in the first status report. In other words, in this case, the second data includes the first data.

[0223] Optionally, the amount of data in the first logical channel may not be reported through all types of BSRs. In this case, regardless of which type of BSR the second status report is, the amount of data in the first logical channel is not reported in the second status report. Alternatively, the amount of data in the first logical channel may not be reported in one or more of the multiple BSRs (or may be reported in one or more of the multiple BSRs). In this case, it can be determined whether the second status report can report the amount of data in the first logical channel based on which type of BSR the second status report is.

[0224] Exemplarily, the amount of data in the first logical channel may not be reported through a regular BSR. On the other hand, this example can also be understood as that the amount of data in the first logical channel can be reported through a periodic BSR or a padding BSR, but not through a regular BSR. For example, when the BSRMACCE in the MAC PDU sent by the first device corresponds to a regular BSR, the BSRMACPDU does not include the amount of data to be transmitted in the LCH configured with reporting delay information. For example, there is data to be transmitted in LCH0 configured with reporting delay information. If a regular BSR is triggered at this time, such as new data from other LCHs triggering a regular BSR, then when the BSRMACCE corresponding to this regular BSR is sent, the BSRMACCE does not include the amount of data in LCH0. In addition, if a periodic BSR or a padding BSR is triggered, the BSRMACCE corresponding to the periodic BSR or the padding BSR can report the amount of data in LCH0. In addition, in this example, for the triggered regular BSR, if there is more than one LCG that is not configured with reporting delay information and has data for transmission, the format of the BSRMACCE corresponding to the regular BSR can be a long BSR, which reports the data volume of all LCGs that are not configured with reporting delay information; otherwise, the format of the BSRMACCE corresponding to the regular BSR is a short BSR.

[0225] For another example, the amount of data in the first logical channel may not be reported through the periodic BSR. On the other hand, this example can also be understood as that the amount of data in the first logical channel can be reported through a regular BSR or a padding BSR, but not through a periodic BSR. For example, there is data to be transmitted in the LCH0 configured with the reporting delay information. If the periodic timer times out and triggers the periodic BSR at this time, when the BSRMACCE corresponding to the periodic BSR is sent, the BSRMACCE does not include the amount of data of LCH0. In addition, if a regular BSR or a padding BSR is triggered, the BSRMACCE corresponding to the regular BSR or the padding BSR can report the amount of data of LCH0. In addition, in this example, for the triggered periodic BSR, if there is more than one LCG that is not configured with reporting delay information and has data for transmission, the format of the BSRMACCE corresponding to the periodic BSR can be a long BSR, reporting the amount of data for all LCGs that are not configured with reporting delay information, otherwise, the format of the BSRMACCE corresponding to the periodic BSR is a short BSR.

[0226] For another example, the amount of data in the first logical channel may not be reported through the padding BSR. On the other hand, this example can also be understood as that the amount of data in the first logical channel can be reported through a regular BSR or a periodic BSR, but not through a padding BSR. For example, there is data to be transmitted in LCH0 that is configured to report delay information. If the first device triggers a padding BSR when sending a MAC PDU, then when sending the BSRMACCE corresponding to the padding BSR, the BSRMACCE does not include the amount of data in LCH0. In addition, if a regular BSR or a periodic BSR is triggered, the BSRMACCE corresponding to the regular BSR or the periodic BSR can report the amount of data in LCH0.

[0227] For another example, the amount of data in the first logical channel may not be reported through the regular BSR and the periodic BSR. On the other hand, this example can also be understood as that the amount of data in the first logical channel can be reported through the padding BSR, but not through the regular BSR and the periodic BSR. Exemplarily, when the BSRMACCE sent by the first device corresponds to the regular BSR or the periodic BSR, the BSRMACCE does not include the amount of data to be transmitted in the LCH configured with the reporting delay information. For example, there is data to be transmitted in the LCH0 configured with the reporting delay information. If the regular BSR or the periodic BSR is triggered at this time, such as new data from other LCHs triggering the regular BSR or the periodic BSR timer timeout triggering the periodic BSR, then when the first device sends the BSRMACCE corresponding to the regular BSR or the periodic BSR, the BSRMAC CE does not include the amount of data in LCH0. In addition, if the padding BSR is triggered, the BSRMACCE corresponding to the padding BSR can report the amount of data in LCH0. In addition, in this example, for the triggered regular BSR and periodic BSR, if there is more than one LCG that is not configured with reporting delay information and has data for transmission, the format of the BSRMACCE corresponding to the regular BSR and the periodic BSR can be a long BSR, reporting the amount of data for all LCGs that are not configured with reporting delay information; otherwise, the format of the BSRMACCE corresponding to the regular BSR and the periodic BSR can be a short BSR.

[0228] The data may be data available for transmission, such as data to be transmitted. Optionally, in an embodiment of the present application, the process in which the first device determines whether the amount of data of the LCH or LCG for configuring the reporting delay information is included in the BSRMACCE may occur when the first device is preparing to assemble / generate a MAC PDU including the BSRMACCE.

[0229] It should be understood that the condition described in the above embodiments of the present application, based on whether the logical channel to which the data belongs is configured to report delay information, may also coexist with other conditions to jointly determine the amount of LCH / LCG data that can be reported by BSRMACCE.

[0230] In addition, optionally, the first data may not trigger the BSR. For example, if the first logical channel is configured to report delay information, the data in the first logical channel (such as the first data) may not trigger the BSR (which may be one or more BSRs, such as a conventional BSR). Alternatively, when the first logical channel is configured to report delay information, the BSR is not triggered according to existing standard criteria (which may be one or more BSRs, such as a conventional BSR). This optional scheme can also be understood as a new trigger condition for the BSR or a new trigger condition added on the basis of an existing BSR trigger condition. This added new condition can be understood as, if the LCH or LCG to which the data belongs is not configured to report delay information, the data can trigger the BSR. Exemplarily, the new trigger condition for the BSR may be:

[0231] When new uplink data arrives at an LCH in a certain LCG, and the new uplink data is available to the MAC entity, and the LCH is not configured with reporting delay information, and the priority of the LCH is higher than the priority of any other LCH with data to be transmitted, or any LCH in any other LCG has no uplink data to send, a BSR is triggered. The BSR triggered in this way can be understood as a regular BSR. Among them, the data is available to the MAC entity, which can be understood as the data can be used, obtained or allocated by the MAC entity, for example, the MAC entity can multiplex the data into the MAC PDU.

[0232] Optionally, the first data may also be a general term for data in multiple logical channels or logical channel groups configured to report delay information.

[0233] Method three: When the first device assembles / generates a MAC PDU carried in the first transmission resource, it determines whether to send one of the status reports or both of the status reports according to the data amounts respectively included in the first status report and the second status report. Among them, if one status report is sent, the status report reports the data amount of the first data, and the status report is the target status report. If two status reports are sent, one of the status reports reports the data amount of the first data, and the other status report does not report the data amount of the first data, at this time, the target status report can be understood as a status report that reports the first data amount in the first status report and the second status report, and it can also be understood that the target status report includes the first status report and the second status report, and one of the status reports reports the data amount of the first data.

[0234] In the scenario where the third method is applied, the first transmission resource may include one status report or multiple status reports. When multiple status reports are included, each status report in the multiple status reports reports the data volume of different data. Among them, when there are multiple triggered status reports at the same time, the data volume of the first data can be reported in the first status report or in the second status report, and reporting in multiple status reports will result in a waste of transmission resources. Therefore, when the first transmission resource may include multiple status reports, it is necessary to determine on which status report the data volume of the first data is transmitted.

[0235] Among them, in a possible implementation, when the first device assembles / generates the MAC PDU, if it is determined that the triggered first status report and the second status report both include the data volume of the first data (that is, the second data includes the first data at this time), the first device can select one of the status reports to be sent through the first transmission resource, and the status report sent through the first transmission resource is the target status report. Optionally, sending the first status report or the second status report can be determined based on the type of status report. For example, when the BSR and DSR include the same data volume, whether to send the DSR or the BSR can be configured. In this case, the first device can select a status report to be sent through the first transmission resource based on whether the first status report is DSR or BSR and the second status report is BSR or DSR.

[0236] For example, when LCH or LCG is configured to report delay information, when the first device assembles / generates MAC PDU, if there is a triggered BSR and DSR, the data of the LCH or LCG can be reported in the DSR (such as the first status report) and not in the BSR (such as the second status report).

[0237] Optionally, if the triggered BSR and DSR include the same amount of data, whether the data amount is reported through DSR or BSR can be pre-configured, for example, pre-configured when the first device leaves the factory, or it can be configured through a semi-static message (such as an RRC message), or it can be dynamically indicated, or it can be predefined by the protocol, or it can be configured in other ways, and the embodiments of the present application are not limited thereto.

[0238] Among them, optionally, when the triggered BSR and DSR include the same amount of data, in the configuration of sending DSR or sending BSR, the BSR may be all types of BSRs, or one or more of multiple BSRs. For example, it can be pre-configured that when the BSRMACCE corresponding to the DSR and the regular BSR include the same amount of data, the amount of data is sent in the DSRMACCE. In this case, if the triggered DSR and the triggered periodic BSR or padding BSR exist at the same time, and the triggered periodic BSR or padding BSR and the triggered DSR include the same amount of data, the amount of data can be sent in the BSRMACCE corresponding to the periodic BSR or padding BSR, or in the DSRMACCE, that is, the BSRMACCE corresponding to the periodic BSR or padding BSR can be sent together with the DSR MACCE and report the same amount of data. Similarly, the regular BSR in this example can also be replaced with a periodic BSR or padding BSR, and accordingly, if other types of BSRs and DSRs include the same amount of data, other types of BSRs can be sent together with the DSR.

[0239] Wherein, optionally, when the first device generates a MACCE, if it is determined that the triggered first status report and the second status report both include the data volume of the first data, the first device may further determine whether all the data volumes included in a certain status report are included in another status report, that is, determine whether the data volume that can be reported by one status report can completely include the data volume that can be reported by another status report. If it is determined that it can, the first device will completely include the status report of the data volume that can be reported by another status report, and determine to send the target status report through the first transmission resource, that is, the first transmission resource does not include the status report that all the data volumes that can be reported are included in the target status report. For example, it is assumed that there are triggered BSR and DSR when assembling / generating MAC PDU, and the triggered BSR and DSR include the data volume of the same data. If the data volume can be reported in full through a status report, such as DSR, at this time, since the triggered BSR does not include the data volume of any other data, there is no need to send the BSR, and the first device may not send the BSR through the first transmission resource. Wherein, the above-mentioned same data may be data from the same or different LCH or LCG.

[0240] Among them, in this implementation, the first device determines not to send the status report through the first transmission resource, which can be understood as canceling the sending of the status report, or in other words, canceling the triggered status report.

[0241] In another possible implementation, when the first device assembles / generates a MAC PDU, if it is determined that both the first status report and the second status report include the data volume of the first data (in this case, the data volume of the second data included in the second status report includes the data volume of the first data, that is, the second data includes the first data), then two status reports can be placed in the MAC PDU, and the data volume of the first data is reported in one of the status reports, and the other status report does not report the data volume. At this time, the target status report can be understood as a status report that reports the first data volume in the first status report and the second status report, and it can also be understood that the target status report includes the first status report and the second status report, and one of the status reports includes the data volume of the first data.

[0242] It is understandable that, in this implementation, the total amount of data reported by the status report that reports the amount of data of the first data may be unchanged compared to the amount of data included in the status report triggered when the first device assembles / generates the MAC PDU. The amount of data reported by another status report no longer includes the amount of data of the first data compared to the amount of data included in the status report triggered when the first device assembles / generates the MAC PDU (it can also be understood that the first device "discards" the amount of data of the first data in the status report when assembling / generating the MAC PDU, so that the status report does not report the amount of data of the first data). In addition, when a status report does not report the amount of data of the first data, the format of the status report may change. For example, when the first device assembles / generates MAC PDU, the format of the BSRMACCE corresponding to the second status report should be a long BSR. Since the first device decides to report the data volume of the first data through the first status report, the second status report does not report the data volume of the first data. After the second status report does not need to report the data volume of the first data, it may only include the data volume of the data in an LCG. Therefore, the format of the BSRMACCE corresponding to the second status report can be changed to a short BSR and placed in the MAC PDU by the first device.

[0243] Optionally, whether the first status report or the second status report reports the amount of data of the first data can be determined based on the type of status report. For example, when the amount of data of the same data is included in the BSR and the DSR, whether the DSR or the BSR reports the amount of data of the same data can be configured. In this case, the first device can select a status report to report the amount of data of the first data based on whether the first status report is DSR or BSR and whether the second status report is BSR or DSR. Alternatively, it can also be determined based on the logical channel to which the data belongs. Exemplarily, taking whether the reporting delay information is configured for the logical channel to which the data belongs as an example, if it is determined that the triggered first status report and the second status report both include the amount of data of the first data in the first logical channel, the amount of data of the first data can be reported through the first status report, such as DSR, and the second status report does not report the amount of data of the first data. In addition, if there is data to be transmitted in the second logical channel at this time, the amount of data to be transmitted in the second logical channel can be reported through the second status report, such as BSR.

[0244] Among them, optionally, when the BSR and DSR include the same amount of data, whether the DSR or the BSR reports the same amount of data can be pre-configured, for example, pre-configured when the first device leaves the factory, or it can be configured through a semi-static message (such as an RRC message), or it can be dynamically indicated, or it can be predefined by the protocol, or it can be configured in other ways, and the embodiments of the present application are not limited thereto.

[0245] Optionally, if the status report for reporting the data volume of the first data is a BSR, the BSR may be one or more of a regular BSR, a periodic BSR or a padding BSR.

[0246] Optionally, if the status report reporting the data volume of the first data is a BSR, the delay information of the first data may be reported in a DSR. Alternatively, if the status report reporting the data volume of the first data is a DSR, the delay information of the first data may also be reported in the DSR.

[0247] In another possible implementation, if in the first status report and the second status report, one status report includes the data volume of the first data, and the other status report does not include the data volume of the first data, the first device may send the first status report and the second status report at the same time through the first transmission resource.

[0248] The status report including the data volume of the first data is the target status report. For example, when the first device assembles / generates the MAC PDU, it is determined that the first status report includes the data volume and delay information of the first data, and the data volume of the second data included in the second status report is different from the data volume of the first data (or, the second data is different from the first data / the second data does not include the first data), then the first device can put both the first status report and the second status report into the MAC PDU.

[0249] In addition, if there is only one status report, such as a BSR, in the first transmission resource, such as a MAC PDU, then regardless of whether the logical channel or logical channel group to which the first data belongs is configured to report delay information, the status report can report the data volume of the data. For example, if the logical channel to which the first data belongs is configured to report delay information, and if the MAC PDU only includes a second status report, such as a BSR, the second status report can also report the data volume of the first data.

[0250] Method 4: cancel a status report triggered by the first status report and the second status report, and the first device sends another reserved status report through the first transmission resource, and the reserved status report is the target status report.

[0251] In the scenario where mode 4 is applied, both the first status report and the second status report include the data volume of the first data, that is, the data volume of the second data included in the second status report includes the data volume of the first data, that is, the second data includes the first data.

[0252] In a possible implementation, the cancellation of the first status report or the second status report may be determined based on the type of status report. Optionally, it may be set that if there is a triggered BSR and a DSR, the triggered BSR may cancel the triggered DSR, or the triggered DSR may cancel the triggered BSR.

[0253] Among them, optionally, whether the triggered DSR cancels the triggered BSR, or the triggered BSR cancels the triggered DSR, can be pre-configured, or can be configured through a semi-static message (such as an RRC message), or can be predefined by the protocol, or can be configured in other ways, and the embodiments of the present application are not limited thereto.

[0254] Taking the example of a triggered DSR canceling a triggered BSR, if the DSR is not triggered earlier than the BSR, for example, the BSR is triggered before the DSR or the BSR and the DSR are triggered at the same time, the triggered DSR can directly cancel the triggered BSR (or in other words, the triggered BSR can be canceled after the DSR is triggered). For example, a BSR is triggered at a first time point, and a DSR is triggered at a second time point later than the first time point. At this time, the DSR can cancel the BSR triggered at the first time point. In this case, the MAC PDU only includes the DSR but not the BSR. Alternatively, if the DSR is triggered earlier than the BSR, after the BSR is triggered, the triggered DSR can also cancel the triggered BSR. For example, a DSR is triggered at a first time point, and a BSR is triggered at a second time point later than the first time point. At this time, the DSR can also cancel the BSR triggered at the second time point. In this case, the MAC PDU only includes the DSR but not the BSR.

[0255] Regarding the cancellation of the triggered BSR by the triggered DSR, in one possible case, before the triggered DSR is sent, any triggered BSR may be cancelled by the triggered DSR. From the perspective of the result, it can also be understood that after the DSR is triggered, the BSR may no longer be triggered before the DSR is sent. Alternatively, the triggered BSR may be cancelled by the triggered DSR when the triggered DSR and the triggered BSR include the same amount of data.

[0256] Optionally, the triggered BSR that can be canceled by the triggered DSR may be any type of BSR (or in other words, the triggered DSR may cancel all types of BSRs), or may be one or more of the multiple types of BSRs.

[0257] Exemplarily, the triggered DSR may cancel at least one of the triggered BSRs of the regular BSR, the periodic BSR and the padding BSR. For example, the triggered DSR may cancel the triggered regular BSR, and the triggered periodic BSR or padding BSR may not be canceled by the triggered DSR. Alternatively, the triggered DSR may cancel the triggered periodic BSR, and the triggered regular BSR or padding BSR may not be canceled by the triggered DSR. Alternatively, the triggered DSR may cancel the triggered padding BSR, and the triggered regular BSR or periodic BSR may not be canceled by the triggered DSR.

[0258] Among them, optionally, the type of BSR that can be canceled by the triggered DSR can be pre-configured, or can be configured through a semi-static message (such as an RRC message), or can be pre-defined by the protocol, or can be configured in other ways, and the embodiments of the present application are not limited thereto.

[0259] Among them, since the padding BSR is triggered by the amount of resources remaining after the MAC PDU is multiplexed according to the logical channel multiplexing priority, the MAC layer or the first device should be able to first determine whether the MAC PDU contains DSR, and then determine whether to trigger the padding BSR. Therefore, one possible implementation of the triggered DSR canceling the triggered padding BSR is that when the MAC PDU includes DSR, the padding BSR is no longer triggered. For example, after the first device determines that the MAC PDU includes DSR, it will no longer continue to determine whether to trigger the padding BSR based on the remaining amount of data in the MAC PDU. For another example, after the MAC PDU multiplexes the MACCE and data in the order of logical channel multiplexing priority, when the number of remaining padding bits is greater than or equal to the size of a BSRMACCE and the sub-header of the MACCE, if the MAC PDU contains DSR, the padding BSR is not triggered.

[0260] Optionally, for a triggered DSR to cancel a triggered regular BSR, the triggered DSR may only cancel the regular BSR triggered by the same LCH or the same LCG, but not cancel the regular BSR triggered by other LCHs or LCGs.

[0261] Exemplarily, assume that the first device has 2 LCHs (LCH0 and LCH1), where LCH0 belongs to LCG0 and LCH1 belongs to LCG1. If LCH0 triggers a regular BSR and then triggers a DSR, the triggered DSR at this time can cancel the triggered regular BSR, that is, the MAC PDU only includes the DSR. If LCH1 triggers a regular BSR and then triggers a DSR, the DSR triggered by LCH0 will not cancel the regular BSR triggered by LCH1, and the MAC PDU can include both the BSR and the DSR. For another example, assume that there is also an LCH2 in LCG0. If there is a BSR triggered by LCH2 when LCH0 triggers the DSR, the triggered DSR can cancel the BSR triggered by LCH2.

[0262] Optionally, for a triggered DSR, the regular BSR triggered by the same LCH or the same LCG can be canceled, and the regular BSR is triggered later than the DSR. From the perspective of the result, it can also be understood that after the same LCH or LCG triggers the DSR, the regular BSR will no longer be triggered.

[0263] Among them, the same LCG triggering BSR and DSR can be the same LCH triggering BSR and DSR in the LCG, or different LCHs in the LCG triggering BSR and DSR, and the embodiment of the present application is not limited to this.

[0264] Alternatively, for a triggered DSR to cancel a triggered regular BSR, the triggered DSR may cancel a regular BSR triggered by an LCH configured with reporting delay information. For example, the first device has three LCHs, namely LCH0, LCH1, and LCH2, of which LCH0 and LCH1 are configured with reporting delay information, and LCH2 is not configured with reporting delay information. If LCH0 triggers a DSR, and LCH1 triggers a BSR, the triggered DSR may cancel the triggered BSR, and at this time the MAC PDU only includes the DSR. If LCH0 triggers a DSR, and LCH2 triggers a BSR, the BSR triggered by LCH2 may not be canceled by the triggered DSR, and at this time the MAC PDU includes both the DSR and the BSR.

[0265] Alternatively, for a triggered DSR to cancel a triggered regular BSR, the triggered DSR may cancel any LCH or LCG triggered BSR.

[0266] Optionally, the different implementations of the above-mentioned triggered DSR cancelling the triggered BSR can also be applied to the case where the triggered BSR cancels the triggered DSR. For example, if there is a triggered BSR and a triggered DSR, the triggered DSR can be canceled by the triggered BSR. Optionally, if the BSR is not triggered earlier than the DSR, for example, the DSR is triggered before the BSR or the BSR and the DSR are triggered at the same time, the triggered BSR can directly cancel the triggered DSR (or in other words, the triggered DSR can be canceled after the BSR is triggered). For example, a DSR is triggered at a first time point, and the BSR is triggered at a second time point later than the first time point. At this time, the BSR can cancel the DSR triggered at the first time point. In this case, the MAC PDU only includes the BSR but not the DSR. Alternatively, if the BSR is triggered earlier than the DSR, after the DSR is triggered, the triggered BSR can also cancel the triggered DSR. For example, a BSR is triggered at a first time point, and a DSR is triggered at a second time point later than the first time point. At this time, the BSR may also cancel the DSR triggered at the second time point. In this case, the MAC PDU only includes the BSR but not the DSR.

[0267] Regarding the cancellation of the triggered DSR by the triggered BSR, in one possible case, before the triggered BSR is sent, any triggered DSR may be cancelled by the triggered BSR. From the perspective of the result, it can also be understood that after the BSR is triggered, the DSR may no longer be triggered before the BSR is sent. Alternatively, the triggered DSR may be cancelled by the triggered BSR when the triggered DSR and the triggered BSR include the same amount of data.

[0268] Optionally, for a triggered BSR to cancel a triggered DSR, the BSR that can cancel the triggered DSR may be any type of BSR, or may be one or more of multiple types of BSRs.

[0269] For example, the triggered DSR may be cancelled by at least one of the triggered regular BSR, the periodic BSR and the padding BSR. For example, the triggered DSR may be cancelled by the triggered regular BSR, in which case the triggered DSR may not be cancelled by the triggered periodic BSR or the padding BSR. Alternatively, the triggered DSR may be cancelled by the triggered periodic BSR, in which case the triggered DSR may not be cancelled by the triggered regular BSR or the padding BSR. Alternatively, the triggered DSR may be cancelled by the triggered padding BSR, in which case the triggered DSR may not be cancelled by the triggered regular BSR or the periodic BSR.

[0270] Among them, optionally, the type of BSR that can cancel the triggered DSR can be pre-configured, or can be configured through a semi-static message (such as an RRC message), or can be pre-defined by the protocol, or can be configured in other ways, and the embodiments of the present application are not limited thereto.

[0271] Wherein, optionally, for the triggered BSR to cancel the triggered DSR, the triggered BSR may cancel the triggered DSR when the following conditions are met: the triggered DSR does not include all data amounts of data in the LCH for configuring the reporting delay information, then the triggered DSR may be canceled by the triggered BSR. Optionally, if the triggered DSR does not meet this condition, that is, the triggered DSR includes all data amounts of data in the LCH for configuring the reporting delay information, then the triggered DSR may not be canceled by the triggered BSR.

[0272] Optionally, the triggered DSR cancels the triggered BSR, or the triggered BSR cancels the triggered DSR, which can occur when assembling / generating the MAC PDU, or can occur at any time when the triggered BSR and the triggered DSR exist at the same time. The embodiment of the present application is not limited to this.

[0273] The above introduces several possible implementation methods for the first device to determine the target status report. After determining the target status report, the first device can send the target status report through the first transmission resource, and correspondingly, the second device can receive the target status report on the first transmission resource, and determine the data volume of the first data to be transmitted at the first device through the target status report.

[0274] In addition, optionally, if the signaling or data that needs to be sent through the first transmission resource (e.g., an uplink MAC PDU) is multiplexed to the first transmission resource according to the logical channel priority, and the first transmission resource can fully accommodate the DSRMACCE and its corresponding MACCE packet header, the periodic BSR timer can also be started or restarted.

[0275] Optionally, if the signaling or data that needs to be sent through the first transmission resource (e.g., an uplink MAC PDU) is multiplexed to the first transmission resource according to the logical channel priority, the first transmission resource can fully accommodate the DSRMACCE and its corresponding MACCE packet header, and the retransmission BSR timer can also be started or restarted.

[0276] Based on the above embodiments, by setting priorities for status reports, configuring whether to report delay information for logical channels, and having the first device flexibly select a status report that reports the data volume of the first data, and having a triggered status report cancel another triggered status report, it is possible to achieve a situation in which, when the first device triggers multiple status reports including data volume, one status report reports the data volume of the first data, thereby avoiding sending multiple status reports that report the same data volume and saving uplink resource overhead.

[0277] In addition, an embodiment of the present application also provides a method for triggering a status report, which can avoid repeated reporting of data information. Figure 7 The method is illustrated by taking the first device as the execution subject as an example, but the present application does not limit the execution subject of the illustration. Figure 7 The first device in the method may also be a module applied to the first device, such as a chip, a chip system, or a processor, or a logical node, a logical module, or software that can realize all or part of the functions of the first device node. The method comprises the following steps:

[0278] S701. The first device obtains third data.

[0279] S701 can also be understood as the third data arriving at the first device, wherein the third data is uplink data that can be sent, that is, data to be transmitted by the first device.

[0280] S702: When the remaining transmission delay budget of the third data is lower than the first threshold, if the information of the third data has not been reported, the first device triggers a fourth status report, and the fourth status report includes the information of the third data.

[0281] That is to say, on the one hand, S702 can be understood as: when the remaining transmission delay budget of a certain data to be transmitted (i.e., the third data) is lower than the first threshold, if the information of the data to be transmitted has not been reported, a fourth status report can be triggered.

[0282] Optionally, the information of the third data may include delay information (such as remaining transmission delay budget, stored time length, etc.) and / or data volume of the third data.

[0283] Taking the example of reporting the information of the data to be transmitted through the status report, illustratively, if the remaining transmission delay budget of the third data is lower than the first threshold, the status report sent by the first device is called the third status report, and S702 can be understood as: when the remaining transmission delay budget of the third data is lower than the first threshold, if the information of the third data has not been reported by the third status report, the first device triggers the fourth status report, and the fourth status report includes the information of the third data.

[0284] Exemplarily, the third status report may be a BSR, or may also be a DSR.

[0285] Optionally, the third status report may be sent after the third data arrives at the first device.

[0286] From another perspective, S702 can also be understood as: when the remaining transmission delay budget of a certain data to be transmitted (i.e., the third data) is lower than the first threshold, if the information of the data to be transmitted has been reported (for example, reported by the third status report), or if the status report sent before (i.e., the third status report) includes the data volume of the data to be transmitted, the fourth status report will not be triggered.

[0287] In other words, the triggering condition for the fourth status report may be:

[0288] When the remaining transmission delay budget of a certain data to be transmitted (ie, the third data) is lower than the first threshold, and the information of the third data has not been reported (eg, the third status report).

[0289] Exemplarily, the fourth status report may be a DSR or a BSR.

[0290] Optionally, whether the fourth status report is triggered may be related to whether the delay information of the third data has been reported, that is, the information of the third data includes the delay information of the third data. Taking the delay information of the third data as the remaining transmission delay budget as an example, in this case, S702 may include:

[0291] When the remaining transmission delay budget of the third data is lower than the first threshold, if the remaining transmission delay budget of the third data has not been reported (for example, in the third status report), the first device triggers a fourth status report, and the fourth status report includes the remaining transmission delay budget of the third data. On the other hand, when the remaining transmission delay budget of the third data is lower than the first threshold, if the remaining transmission delay budget of the third data has been reported (for example, in the third status report), the fourth status report is not triggered.

[0292] In other words, the triggering condition of the fourth status report may be: when the remaining transmission delay budget of a certain data to be transmitted (ie, the third data) is lower than the first threshold, the remaining transmission delay budget of the data to be transmitted has not been reported (eg, the third status report).

[0293] Optionally, whether the fourth status report is triggered may be related to whether the data volume of the third data has been reported, that is, the information of the third data includes the data volume of the third data. In this case, S702 may include:

[0294] When the remaining transmission delay budget of the third data is lower than the first threshold, if the data volume of the third data has not been reported (for example, in the third status report), the first device triggers a fourth status report, and the fourth status report includes the data volume of the third data. On the other hand, when the remaining transmission delay budget of the third data is lower than the first threshold, the data volume of the third data has been reported (for example, in the third status report), and the fourth status report is not triggered.

[0295] In other words, the triggering condition of the fourth status report may be: when the remaining transmission delay budget of a certain data to be transmitted (ie, the third data) is lower than the first threshold, the data volume of the data to be transmitted has not been reported (eg, the third status report).

[0296] Optionally, whether the fourth status report is triggered may be related to whether the data volume and the remaining transmission delay budget of the third data have been reported, that is, the information of the third data includes the data volume of the third data and the remaining transmission delay budget of the third data. In this case, S702 may include:

[0297] When the remaining transmission delay budget of the third data is lower than the first threshold, if the data volume and the remaining transmission delay budget of the third data have not been reported (for example, in the third status report), the first device triggers a fourth status report, and the fourth status report includes the data volume and the remaining transmission delay budget of the third data. On the other hand, when the remaining transmission delay budget of the third data is lower than the first threshold, the data volume and the remaining transmission delay budget of the third data have been reported (for example, in the third status report), and the fourth status report is not triggered.

[0298] In other words, the trigger condition for the fourth status report may be: when the remaining transmission delay budget of a certain data to be transmitted (i.e., the third data) is lower than the first threshold, the data volume and the remaining transmission delay budget of the data to be transmitted have not been reported (e.g., the third status report).

[0299] Among them, the first threshold can be pre-configured, for example, configured when the first device leaves the factory, or it can be configured through semi-static signaling (such as RRC message), or it can be indicated by a dynamic message (such as MACCE or DCI), or it can be pre-defined by the protocol, or it can be configured by other means, and the embodiments of the present application are not limited to this.

[0300] Optionally, the third data may belong to a third logical channel, wherein the third logical channel is a logical channel configured to report delay information. That is to say, if the data to be transmitted belongs to a logical channel configured to report delay information, the data to be transmitted may trigger a fourth status report, and if the data to be transmitted does not belong to a logical channel configured to report delay information, the data to be transmitted may not trigger a fourth status report. Exemplarily, in this case, the triggering condition for the fourth status report may be understood as follows: when the logical channel (such as the third logical channel) or logical channel group to which the data to be transmitted (such as the third data) belongs is configured to report delay information, and the remaining transmission delay budget of the data to be transmitted is lower than the first threshold, and the information of the data to be transmitted has not been reported (for example, in the third status report), the fourth status report is triggered. Among them, the logical channel configured to report delay information and how to configure the logical channel to report delay information can be specifically referred to the above introduction to the first logical channel, which will not be expanded here. Exemplarily, in a possible implementation, the first device may obtain second configuration information (for example, the second configuration information may be sent by the second device), and the second configuration information is used to configure the third logical channel to report delay information.

[0301] Optionally, the fourth status report may further include data volume and / or delay information of other data to be transmitted (eg, delay budget to be transmitted or storage duration).

[0302] Optionally, in S702, one of the conditions for triggering the fourth status report: the remaining transmission delay budget of the third data is lower than the first threshold, can also be replaced by: the remaining transmission delay budget of the third data is lower than or equal to the first threshold. For example, the triggering condition for the fourth status report can be: when the remaining transmission delay budget of the third data is lower than or equal to the first threshold, the third status report sent before does not include the data volume of the third data.

[0303] In addition, the fourth status report may also be triggered based on other delay information of the third data. Taking the trigger based on the stored duration of the third data as an example, correspondingly, S702 may be replaced by:

[0304] When the storage time of the third data is higher than (or, may be higher than or equal to) the second threshold, if the information of the third data is not reported (for example, in the third status report), the first device triggers a fourth status report, and the fourth status report includes the information of the third data. The information of the third data may be the delay information and / or the data volume of the third data.

[0305] In other words, in this case, the triggering condition for the fourth status report may be:

[0306] When the storage duration of certain data to be transmitted (ie, the third data) is higher than (or, may be higher than or equal to) the second threshold, the status report sent before (ie, the third status report) does not include information of the data to be transmitted.

[0307] In addition, the embodiment of the present application also provides another method for triggering a status report, which can avoid repeated reporting of data information. Figure 8 The method is illustrated by taking the first device as the execution subject as an example, but the present application does not limit the execution subject of the illustration. Figure 8 The first device in the method may also be a module applied to the first device, such as a chip, a chip system, or a processor, or a logical node, a logical module, or software that can realize all or part of the functions of the first device node. The method comprises the following steps:

[0308] S801. A first device determines a first duration.

[0309] In S801, the first device determines a start time of a first duration and a value of the first duration, that is, the first device may determine a range of the first duration in the time domain.

[0310] Optionally, the starting time of the first duration may be the triggering time of the fifth status report or the sending time of the fifth status report.

[0311] The fifth status report may include delay information of the data to be transmitted of the first device, such as the storage duration of the data to be transmitted or the remaining transmission delay budget. Exemplarily, the fifth status report may be a DSR.

[0312] Among them, the value of the first duration can be pre-configured, for example, configured when the first device leaves the factory, or it can be configured through semi-static signaling (such as RRC message), or it can be indicated by a dynamic message (such as MACCE or DCI), or it can be pre-defined by the protocol, or it can be configured by other means, and the embodiments of the present application are not limited to this.

[0313] S802: Within the first time period, the first device does not trigger the sixth status report.

[0314] The sixth status report may include delay information and / or data volume of data to be transmitted by the first device. Exemplarily, the sixth status report may be a BSR or a DSR.

[0315] Optionally, the first duration may be effective for all logical channels or logical channel groups of the first device, or the MAC entity of the first device. That is to say, within the first duration, all logical channels or logical channel groups of the first device no longer trigger the sixth status report. For example, the first device starts the first duration after triggering / sending the fifth status report. During the first duration, when the remaining transmission delay budget of the data in the fourth logical channel of the first device is lower than the first threshold, the sixth status report will not be triggered, where the fourth logical channel is any logical channel of the first device. Alternatively, it can also be understood that when the remaining transmission delay budget of the data in the fourth logical channel of the first device is lower than the first threshold, if it is not within the first duration at this time, the sixth status report can be triggered.

[0316] Alternatively, the first duration may also be effective for a certain logical channel or a certain logical channel group or a certain data radio bearer DRB (data radio bearer, DRB) of the first device. For example, when the fourth logical channel triggers the fifth status report, the first duration is turned on for the fourth logical channel. Within the first duration, the fourth logical channel no longer triggers the sixth status report. Alternatively, the condition for the fourth logical channel to trigger the sixth status report can be understood as: if the remaining transmission delay budget of the data to be transmitted (such as belonging to the fourth logical channel) is lower than the first threshold, and is not within the first duration at this time, then the sixth status report can be triggered.

[0317] Alternatively, when the first device sends the fifth status report, if the fifth status report is triggered by the fourth logical channel, the first duration is opened for the fourth logical channel. When the remaining transmission delay budget of a certain data to be transmitted in the fourth logical channel is lower than the first threshold, if it is not within the first duration at this time, the sixth status report can be triggered. It can also be understood that when the remaining transmission delay budget of a certain data to be transmitted in the fourth logical channel is lower than the first threshold, if it is within the first duration at this time, the sixth status report is not triggered.

[0318] Alternatively, when the first duration is effective for a certain logical channel group, the first duration opened for the fourth logical channel is effective for any logical channel in the logical channel group described by the fourth logical channel. For example, within the first duration, the logical channels in the logical channel group described by the fourth logical channel no longer trigger the sixth status report. Alternatively, the condition for the fourth logical channel to trigger the sixth status report can be understood as: if the remaining transmission delay budget of the data to be transmitted (such as the logical channel belonging to the logical channel group to which the fourth logical channel belongs) is lower than the first threshold, and it is not within the first duration at this time, then the sixth status report can be triggered.

[0319] In a possible implementation, a timer may be configured so that the first device no longer triggers the sixth status report within the first duration after the fifth status report is triggered / sent. For example, a specific timer may be configured for the first device, and the first device starts or restarts the timer when the fifth status report is triggered / sent (or, the start / restart time of the timer is the time when the fifth status report is triggered / sent), and during the running time of the timer, the first device no longer triggers the sixth status report. In other words, the running time of the timer is the value of the above-mentioned first duration.

[0320] Among them, the duration of the timer can be pre-configured, for example, configured when the first device leaves the factory, or it can be configured through semi-static signaling (such as RRC message), or it can be indicated by a dynamic message (such as MACCE or DCI), or it can be pre-defined by the protocol, or it can be configured by other means, and the embodiments of the present application are not limited to this.

[0321] Exemplarily, the timer may be called a DSR prohibit timer (DSRprohibittimer), or the timer may have other names, which is not limited in the embodiments of the present application.

[0322] The following embodiments are introduced by taking the timer called the prohibit timer as an example. Optionally, the prohibit timer can be effective for all logical channels or logical channel groups of the first device, or the MAC entity of the first device. That is to say, during the running time of the prohibit timer, all logical channels or logical channel groups of the first device no longer trigger the sixth status report. For example, after triggering / sending the fifth status report, the first device starts / restarts the prohibit timer. During the running time of the prohibit timer, when the remaining transmission delay budget of the data in the fourth logical channel of the first device is lower than the first threshold, the sixth status report will not be triggered. Alternatively, it can also be understood that when the remaining transmission delay budget of the data in the fourth logical channel of the first device is lower than the first threshold, if it is not within the running time of the prohibit timer, or in other words, the prohibit timer is not running (not running), the sixth status report can be triggered.

[0323] Alternatively, the prohibition timer may also be effective for a certain logical channel, a certain logical channel group, or a certain DRB of the first device. For example, when the fourth logical channel triggers the fifth status report, the prohibition timer is started or restarted for the fourth logical channel. During the running time of the prohibition timer, the fourth logical channel no longer triggers the sixth status report. Alternatively, the condition for the fourth logical channel to trigger the sixth status report can be understood as follows: if the remaining transmission delay budget of the data to be transmitted (such as belonging to the fourth logical channel) is lower than the first threshold, and this is not within the running time of the prohibition timer, then the sixth status report can be triggered.

[0324] Alternatively, when the first device sends the fifth status report, if the fifth status report is triggered by the fourth logical channel, the prohibition timer is started / restarted for the fourth logical channel. When the remaining transmission delay budget of a certain data to be transmitted in the fourth logical channel is lower than the first threshold, if it is not within the prohibition timer running time, the sixth status report can be triggered. It can also be understood that when the remaining transmission delay budget of a certain data to be transmitted in the fourth logical channel is lower than the first threshold, if it is within the prohibition timer running time, the sixth status report is not triggered.

[0325] Alternatively, when the first device sends the fifth status report, if the fifth status report is triggered by the fourth logical channel, the prohibition timer is started / restarted for the fourth logical channel (or the logical channel group to which the fourth logical channel belongs). When the remaining transmission delay budget of a certain data to be transmitted in any logical channel in the logical channel group to which the fourth logical channel belongs is lower than the first threshold, if this time is not within the prohibition timer running time, the sixth status report can be triggered. It can also be understood that when the remaining transmission delay budget of a certain data to be transmitted in any logical channel in the logical channel group to which the fourth logical channel belongs is lower than the first threshold, if this time is within the prohibition timer running time, the sixth status report will not be triggered.

[0326] Optionally, in S802, one of the conditions for triggering the sixth status report: the remaining transmission delay budget of the data to be transmitted is lower than the first threshold, may also be replaced by: the remaining transmission delay budget of the data to be transmitted is lower than or equal to the first threshold.

[0327] In addition, the sixth status report can also be triggered based on other delay information of the data to be transmitted. Taking the trigger based on the stored duration of the data to be transmitted as an example, one of the conditions for triggering the sixth status report: the remaining transmission delay budget of the data to be transmitted is lower than the first threshold, which can also be replaced by: the stored duration of the data to be transmitted is higher than (or, can also be higher than or equal to) the second threshold. Exemplarily, the condition that needs to be met to trigger the sixth status report can be: when the stored duration of the data in the fourth logical channel of the first device is higher than the second threshold, if it is not within the first duration at this time, the sixth status report can be triggered. For other possible replaced conditions, please refer to the above introduction to S802, which will not be expanded here.

[0328] The following introduces the transmission delay budget and storage duration of the data in the above embodiments of the present application.

[0329] The remaining transmission delay budget of data refers to the time that can be used to transmit data on the air interface, which can be determined based on the effective transmission time of the data.

[0330] Optionally, the effective transmission duration can be understood as the transmission delay requirement of the data, such as the transmission delay budget or the packet loss delay budget. Exemplarily, the transmission delay budget can be the packet delay budget (PDB) corresponding to the data, or the PDUset delay budget (PSDB) timeout. PDB can be understood as the delay requirement from the first device to the network device or to the user plane function (UPF), that is, the time from when a PDU arrives at the first device to when the PDU is successfully received by the network device or UPF, usually configured by the core network (CN) through the 5GQoS identifier (5GQoSidentifier, 5QI). PSDB can be understood as the transmission delay requirement of a PDU set, such as the time from the first PDU in a PDUset that arrives at the first device to when all PDUs in the PDUset are successfully received by the network device or UPF, wherein, optionally, PSDB can be configured by the core network.

[0331] Alternatively, the effective transmission duration can also be understood as the packet loss delay budget of the data, and the packet loss delay budget can be understood as the data will be discarded after the duration corresponding to the delay budget, that is, it will not be sent as the initial transmission by the first device. Usually, the packet loss delay budget can be implemented by the PDCP layer, such as the PDCP layer configures a packet loss timer for each service data unit (SDU). When the SDU from the upper layer reaches the PDCP layer, the timer is started. When the timer times out, the corresponding SDU or PDU will be discarded.

[0332] In the case where the effective transmission duration of data is understood as the packet loss delay budget of the data, the first device may determine (or obtain) the effective transmission duration of a certain data based on the following method:

[0333] The first device obtains the third configuration information, and the third configuration information is used to configure the packet loss timer. The starting time of the packet loss timer is the time when the first device obtains certain data (for example, the first data, the second data, or the third data in the above embodiment) (or the time when the data arrives at the first device). When the first packet loss timer times out, the first device discards the data. The running time of the packet loss timer is the effective transmission time of the data.

[0334] In the case where the effective transmission duration is understood as the transmission delay budget of the data, the first device may determine the effective transmission duration of a certain data based on the following method:

[0335] The first device obtains third configuration information, and the third configuration information is used to configure the PDB or PSDB of certain data (for example, it can be the first data, the second data or the third data in the above embodiment). The time when the data arrives at the first device is the start time of the PDB or PSDB, and the effective transmission duration of the data is the duration of the PDB or PSDB configured by the third configuration information.

[0336] Optionally, if the data includes multiple data units, the moment when the data arrives at the first device can be understood as the moment when one of the data units in the data arrives at the first device. Exemplarily, when the data is a PDUset or a data burst, the moment when the data arrives at the first device can be understood as the moment when one of the PDUs in the PDUset or the data burst arrives at the first device, for example, it can be the moment corresponding to the first PDU in the PDUset or the data burst that arrives at the first device. It can be understood that the first PDU to arrive at the first device is not necessarily the first PDU in the PDUset or the data burst in the order of generation or transmission.

[0337] Optionally, the moment when the data unit (or data including a data unit) arrives at the first device can be understood as the moment when the data unit arrives at the access stratum (AS) layer of the first device, or it can be the moment when the data unit reaches the service data adaptation protocol (SDAP) layer, or the PDCP layer, or the radio link control (RLC), or the LCH, or the MAC layer, which is not limited in the embodiments of the present application.

[0338] In addition, optionally, if the data includes multiple data units, the moment when the data is received by the second device (or referred to as the moment when the data arrives at the second device) can be understood as the moment when all the data units included in the data arrive at the second device. Exemplarily, when the data is a PDUset or a data burst, the moment when the data arrives at the second device can be understood as the moment when all the PDUs in the PDUset or data burst arrive at the second device, that is, the moment corresponding to the last PDU in the PDUset or data burst that arrives at the second device, wherein the last PDU to arrive at the first device is not necessarily the last PDU in the PDUset or data burst to which it belongs in the order of generation or transmission, nor is it necessarily the last PDU in the PDU set or data burst to which it belongs to arrive at the first device.

[0339] Optionally, the moment when the data unit (or data including a data unit) arrives at the second device can be understood as the moment when the data arrives at the AS layer, SDAP layer, PDCP layer, RLC layer, LCH, or MAC layer of the second device, which is not limited in the embodiments of the present application.

[0340] The remaining transmission delay budget of the data may be determined (or referred to as acquired) based on the triggering moment of a status report including the remaining transmission delay budget of the data (exemplarily, a DSR including the remaining transmission delay budget of the data) or the sending moment of the status report including the remaining transmission delay budget of the data, and the effective transmission duration. Specifically, the starting moment of the remaining transmission delay budget of the data may be the triggering moment of the status report including the remaining transmission delay budget of the data or the sending moment of the status report including the remaining transmission delay budget of the data, and the ending moment (or referred to as the ending moment) of the remaining transmission delay budget of the data may be the ending moment of the effective transmission duration.

[0341] The storage duration of the data refers to the duration that the data has been stored at the first device. The starting time of the storage duration of the data is the arrival time of the data (i.e., the time when the data arrives at the first device). The ending time of the storage duration of the data may be the time when a status report including the storage duration of the data is triggered (exemplarily, a DSR including the storage duration of the data) or the time when a status report including the storage duration of the data is sent.

[0342] For example, for the case where the remaining transmission delay budget / stored duration is determined based on the time of sending the status report, such as Fig. 9 and Fig.10As shown, the starting time of the remaining transmission delay budget of the data is the time of sending the status report (the status report is a status report including the remaining transmission delay budget of the data), and the ending time is the time corresponding to the time when the effective transmission duration of the data times out. The starting time of the stored duration of the data is the arrival time of the data, and the ending time of the stored duration of the data is the time of sending the status report (the status report is a status report including the stored duration of the data). In other words, the effective transmission duration can be decomposed into the sum of the stored duration of the data and the remaining transmission delay.

[0343] For another example, in the case where the remaining transmission delay budget / stored duration is determined based on the time when the status report is triggered, the starting time of the remaining transmission delay budget is the time when the status report is triggered (the status report is a status report including the remaining transmission delay budget of the data), and the ending time is the time corresponding to the time when the effective transmission duration of the data times out. The starting time of the stored duration of the data is the arrival time of the data, and the ending time of the stored duration of the data is the time when the status report is triggered (the status report is a status report including the stored duration of the data).

[0344] The sending time of the status report may be the initial transmission time of the status report.

[0345] It can be understood that in the above embodiments, the methods and / or steps implemented by each device can also be implemented by components that can be used for the device (such as a processor, chip, chip system, circuit, logic module, or software such as a chip or circuit).

[0346] The above mainly introduces the solution provided by the present application from the perspective of interaction between various devices. Accordingly, the present application also provides a communication device, which is used to implement the above various methods. The communication device can be the first device or the second device in the above method embodiment, or a device including the above device, or a component that can be used for the above device.

[0347] It is understandable that, in order to realize the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware 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.

[0348] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. 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.

[0349] Fig.11 A schematic diagram of the structure of a communication device 110 is provided. For example, Fig.11 As shown, the communication device 110 includes: a transceiver module 1102 and a processing module 1101. For ease of description, Fig.11 Only the main components of the communication device are shown.

[0350] In some embodiments, the communication device 110 may further include a storage module ( Fig.11 ), for storing program instructions and data.

[0351] In some embodiments, the transceiver module 1102 may also be referred to as a transceiver unit for implementing a sending and / or receiving function. The transceiver module 1102 may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface.

[0352] In some embodiments, the transceiver module 1102 may include a receiving module and a sending module, which are respectively used to execute the receiving and sending steps performed by the first device or the second device in the above-mentioned method embodiment, and / or used to support other processes of the technology described herein; the processing module 1101 may be used to execute the processing steps (such as determination, generation, etc.) performed by the first device or the second device in the above-mentioned method embodiment, and / or used to support other processes of the technology described herein.

[0353] When the communication device 110 is used to implement the function of the first device:

[0354] In one possible design, the processing module 1101 is used to trigger a first status report, the first status report includes the data volume and latency information of the first data, and the first data is the data to be transmitted of the first device. The processing module 1101 is also used to trigger a second status report, the second status report includes the data volume of the second data, and the second data is the data to be transmitted of the first device. The transceiver module 1102 is used to send a target status report through the first transmission resource, and the target status report includes the data volume of the first data.

[0355] Optionally, the processing module 1101 is further used to obtain first configuration information, where the first configuration information is used to configure reporting delay information of the first logical channel.

[0356] Optionally, the processing module 1101 is further configured to cancel a triggered second status report.

[0357] In another possible design, the processing module 1101 is used to obtain the third data. When the remaining transmission delay budget of the third data is lower than the first threshold, if the information of the third data has not been reported, the processing module 1101 is further used to trigger a fourth status report, and the fourth status report includes the information of the third data.

[0358] Optionally, the transceiver module 1102 is configured to send a third status report. If the third status report does not include information about the third data, the processing module 1101 is configured to trigger a fourth status report.

[0359] Optionally, the processing module 1101 is further used to obtain second configuration information, where the second configuration information is used to configure reporting delay information of a third logical channel, and the third data belongs to the third logical channel.

[0360] Optionally, the processing module 1101 is also used to obtain third configuration information, and the third configuration information is used to configure a packet loss timer. The starting time of the packet loss timer is the time of obtaining the third data. When the first packet loss timer times out, the processing module 1101 discards the third data. The remaining transmission delay budget of the third data is determined based on the packet loss timer.

[0361] When the communication device 110 is used to implement the function of the second device:

[0362] The transceiver module 1102 is used to send first configuration information, and the first configuration information is used to configure the first logical channel to report delay information. The transceiver module 1102 is also used to receive a target status report through a first transmission resource, and the target status report includes the data volume of the first data. The first data belongs to a second logical channel, the second logical channel is different from the first logical channel, and the target status report is a cache status report. Alternatively, the first data belongs to the first logical channel, and the target status report also includes the delay information of the first data.

[0363] Optionally, the transceiver module 1102 is also used to send third configuration information, and the third configuration information is used to configure a packet loss timer, the starting time of the packet loss timer is the arrival time of the first data, when the first packet loss timer times out, the first data is discarded; the remaining transmission delay budget of the first data is determined based on the packet loss timer.

[0364] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0365] In the present application, the communication device 110 is presented in the form of dividing various functional modules in an integrated manner. The "module" here may refer to an ASIC, a circuit, a processor and a memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0366] In some embodiments, when Fig.11 When the communication device 110 is a chip or a chip system, the function / implementation process of the transceiver module 1102 can be implemented through the input and output interface (or communication interface) of the chip or the chip system, and the function / implementation process of the processing module 1101 can be implemented through the processor (or processing circuit) of the chip or the chip system.

[0367] Since the communication device 110 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0368] As a possible product form, the above-mentioned communication device 110 can be implemented using the following: one or more field programmable gate arrays (FPGA), programmable logic devices (PLD), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0369] In some embodiments, in terms of hardware implementation, those skilled in the art may imagine that the communication device 110 may be implemented as Figure 5 The form of the communication device 500 is shown.

[0370] As an example, Fig.11 The function / implementation process of the processing module 1101 in Figure 5 The processor 501 in the communication device 500 shown calls the computer execution instructions stored in the memory 503 to implement. Fig.11 The function / implementation process of the transceiver module 1102 can be Figure 5 The communication interface 504 in the communication device 500 is shown to be implemented.

[0371] It should be noted that Fig.11 The structure shown does not constitute a specific limitation on the device structure. For example, in other embodiments of the present application, the above-mentioned devices may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0372] In some embodiments, an embodiment of the present application further provides a communication device, which includes a processor for implementing a method in any of the above method embodiments.

[0373] As a possible implementation, the communication device further includes a memory. The memory is used to store necessary computer programs and data. The computer program may include instructions, and the processor may call the instructions in the computer program stored in the memory to instruct the communication device to execute the method in any of the above method embodiments. Of course, the memory may not be in the communication device.

[0374] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, which is used to receive computer execution instructions (computer execution instructions are stored in a memory, may be read directly from the memory, or may pass through other devices) and transmit them to the processor.

[0375] As another possible implementation manner, the communication device further includes a communication interface, and the communication interface is used to communicate with a module outside the communication device.

[0376] It can be understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips, or it can include chips and other discrete devices. The embodiments of the present application do not specifically limit this.

[0377] The present application also provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, the functions of any of the above method embodiments are implemented.

[0378] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0379] Those skilled in the art will appreciate that, for the sake of convenience and brevity of description, the specific working processes of the systems, devices and units described above may refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0380] It is understood that the systems, devices and methods described in the present application can also be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. 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 can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0381] The units described as separate components may or may not be physically separated, i.e., they may be located in one place, or they may be distributed over multiple network units. The components shown as units may or may not be physical units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0382] 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.

[0383] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or may contain one or more servers, data centers and other data storage devices that can be integrated with a medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)), etc. In the embodiment of the present application, the computer may include the aforementioned device.

[0384] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in a claim. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0385] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data volume reporting method, characterized in that: The method comprises: A first device triggers a first status report, where the first status report includes data volume and latency information of first data, where the first data is data to be transmitted by the first device; The first device triggers a second status report, where the second status report includes a data volume of second data, where the second data is data to be transmitted by the first device; The first device sends a target status report through a first transmission resource, where the target status report includes a data volume of the first data.

2. The method according to claim 1, characterized in that The target status report is a status report with a higher priority between the first status report and the second status report; The second data includes the first data.

3. The method according to claim 2, characterized in that The logical channel multiplexing priority of the first status report is the same as the logical channel multiplexing priority of the second status report, and the second status report is a cache status report.

4. The method according to claim 1, characterized in that: The method further comprises: The first device obtains first configuration information, where the first configuration information is used to configure a first logical channel to report delay information; the first logical channel belongs to the first device.

5. The method according to claim 4, characterized in that The first data belongs to a second logical channel, the second logical channel is different from the first logical channel, the second status report is triggered by the first data, and the second status report is a cache status report.

6. The method according to claim 4, characterized in that The first data belongs to the first logical channel, wherein, The first status report is triggered by the first data; and / or, The second status report is triggered by data in a second logical channel, the second logical channel is different from the first logical channel, and the second status report is a buffer status report.

7. The method according to claim 4 or 6, characterized in that: The first data belongs to the first logical channel, and the second data does not include the first data.

8. The method according to claim 7, characterized in that The target status report includes the first status report and the second status report.

9. The method according to claim 1, characterized in that: The method further comprises: The first device cancels the triggered second status report.

10. The method according to claim 9, characterized in that The first status report and the second status report are triggered by the first data.

11. A method for reporting data volume, characterized in that: The method comprises: The first device obtains third data; When the remaining transmission delay budget of the third data is lower than the first threshold, if the information of the third data has not been reported, the first device triggers a fourth status report, and the fourth status report includes the information of the third data.

12. The method according to claim 11, characterized in that The information about the third data includes the data volume of the third data and / or the remaining transmission delay budget of the third data.

13. The method according to claim 11 or 12, characterized in that: Before the remaining transmission delay budget of the third data is lower than the first threshold, the method further includes: The first device sends a third status report; If the information of the third data has not been reported, the first device triggers a fourth status report, including: If the third status report does not include information about the third data, the first device triggers a fourth status report.

14. The method according to any one of claims 11 to 13, characterized in that: The method further comprises: The first device obtains second configuration information, where the second configuration information is used to configure reporting delay information of a third logical channel, and the third data belongs to the third logical channel.

15. The method according to any one of claims 11 to 14, characterized in that: The method further comprises: The first device obtains third configuration information, and the third configuration information is used to configure a packet loss timer. The starting time of the packet loss timer is the time when the first device obtains the third data. When the first packet loss timer times out, the first device discards the third data; the remaining transmission delay budget of the third data is determined based on the packet loss timer.

16. A method for reporting data volume, characterized in that: The method comprises: The second device sends first configuration information, where the first configuration information is used to configure the first logical channel to report delay information; The second device receives a target status report through a first transmission resource, where the target status report includes a data volume of the first data; The first data belongs to a second logical channel, the second logical channel is different from the first logical channel, and the target status report is a cache status report; Alternatively, the first data belongs to the first logical channel, and the target status report also includes delay information of the first data.

17. The method according to claim 16, characterized in that The first data belongs to the first logical channel, and the target status report includes a first status report and a second status report; wherein, the first status report includes the data volume and delay information of the first data, the second status report includes the data volume of the second data, and the second data does not include the first data.

18. The method according to claim 16 or 17, characterized in that The delay information of the first data is the remaining transmission delay budget of the first data.

19. The method according to claim 18, characterized in that The method further comprises: The second device sends third configuration information, where the third configuration information is used to configure a packet loss timer, where the starting time of the packet loss timer is the arrival time of the first data, and when the first packet loss timer times out, the first data is discarded; the remaining transmission delay budget of the first data is determined based on the packet loss timer.

20. A communication device, characterized in that: The apparatus comprises: a module for executing the method according to any one of claims 1-15.

21. A communication device, characterized in that: The apparatus comprises: a module for performing the method as claimed in any one of claims 16-19.

22. A communication device, characterized in that: The communication device comprises: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method according to any one of claims 1-19.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a computer program or instructions, and when the computer program or instructions are run on a computer, the method of any one of claims 1 to 19 is executed.

24. A computer program product, characterized in that The computer program product comprises instructions, and when the instructions are run on a computer, the method of any one of claims 1 to 19 is executed.

25. A chip, characterized in that: The chip includes: a processor, and the processor is used to execute instructions so that a device including the chip performs the method according to any one of claims 1-19.

Images