Information processing method and apparatus

Abstract

Embodiments of the present application provide an information processing method and apparatus. The method comprises: generating or transmitting a first report, wherein the first report comprises the latest first uplink data volume and / or comprises the latest first residual delay of uplink data. According to the present application, by configuring that a first report comprises a first uplink data volume and / or a first residual delay of uplink data in the latest state, it can be ensured that even if uplink data is discarded, the first report comprises related information of uplink data after discarding, thereby avoiding waste of resources caused by the first report comprising a redundant buffer data volume or residual delay after discarding of uplink data.

Description

Information processing method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on March 31, 2023, with application number 202310365217.1 and application name “Information Processing Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technologies, and in particular to information processing methods and devices. Background Art

[0003] When a terminal device requests uplink resources from a network device, it needs to report a buffer status report (BSR) to the network device so that the network device can schedule appropriate uplink resources for the terminal device.

[0004] Before sending uplink data, the terminal device may discard uplink data. If this happens, the amount of uplink data cached in the terminal device may change significantly. If a cache status report is submitted to the network device before uplink data is discarded, the terminal device may report an excess cache amount. The network device may then allocate excess uplink resources, resulting in a waste of resources.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide an information processing method and apparatus, which are applied in the field of terminal technology.

[0007] In a first aspect, an embodiment of the present application provides an information processing method, applied to a terminal device, comprising:

[0008] Generate or transmit a first report, wherein the first report includes the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0009] In one possible design, the latest first uplink data amount and / or the latest first residual delay are determined at a first moment;

[0010] The first moment is at least one of the following: the moment of determining the first resource for sending the first report; the moment when the first resource arrives; the moment when the update indication information is obtained, the update indication information is used to indicate the discarding of uplink data, or the update indication information is used to indicate the remaining uplink data amount after discarding and / or the remaining delay of the uplink data remaining after discarding.

[0011] In one possible design, the method further includes:

[0012] If the uplink data is discarded, the triggered second report is canceled.

[0013] In one possible design, the second report is the first report; or, the second report includes a second uplink data volume and / or a second residual delay.

[0014] In one possible design, canceling the triggered second report if uplink data is discarded includes:

[0015] If the uplink data is discarded and there is no uplink data in the first channel, the triggered second report is canceled, and the first channel includes at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

[0016] In one possible design, the logical channel is the logical channel that triggers the second report, the logical channel group is the logical channel group that triggers the second report, the PDU set is the PDU set that triggers the second report, or the data burst information is the data burst information that triggers the second report.

[0017] In one possible design, the method further includes:

[0018] If the uplink data is discarded, re-evaluating the triggering condition of the second report;

[0019] When the trigger condition is met, the second report is re-triggered.

[0020] In one possible design, the method further includes:

[0021] If uplink data is discarded, a third report is triggered, and the third report is used to update the uplink data amount and / or the remaining delay of the uplink data.

[0022] In one possible design, the third report is the first report or the second report.

[0023] In one possible design, the terminal device includes a media access control (MAC) layer, and the triggering of the third report includes:

[0024] The MAC layer receives high-layer indication information, where the high-layer indication information is used to indicate that the uplink data is discarded;

[0025] The MAC layer triggers the third report according to the higher layer indication information.

[0026] In one possible design, the high-layer indication information is used to indicate a first channel group to which the discarded uplink data belongs;

[0027] The MAC layer triggering the third report according to the higher-layer indication information includes:

[0028] The MAC layer determines, according to the high-layer indication information, whether the first channel to which the discarded uplink data belongs has triggered the third report;

[0029] If so, the third report is triggered.

[0030] In one possible design, the third report includes cause indication information, and the cause indication information is used to indicate that the third report is triggered due to the discarding of uplink data, or to indicate that the amount of uplink data and / or the remaining delay included in the third report is obtained after the uplink data is discarded.

[0031] In one possible design, the third report includes the amount of discarded uplink data and / or delay information of the discarded uplink data.

[0032] In one possible design, the third report also includes the first channel corresponding to the discarded uplink data.

[0033] In one possible design, the discarded uplink data includes at least one protocol data unit (PDU) set.

[0034] In a second aspect, an embodiment of the present application provides an information processing method, applied to a terminal device, comprising:

[0035] If the uplink data is discarded, the triggered second report is canceled.

[0036] In a third aspect, an embodiment of the present application provides an information processing method, applied to a terminal device, comprising:

[0037] If uplink data is discarded, the triggering condition for the second report is re-evaluated;

[0038] When the trigger condition is met, the second report is re-triggered.

[0039] In a fourth aspect, an embodiment of the present application provides an information processing method, applied to a terminal device, the method comprising:

[0040] If uplink data is discarded, a third report is triggered, and the third report is used to update the uplink data amount and / or the remaining delay of the uplink data.

[0041] In a fifth aspect, an embodiment of the present application provides an information processing method, applied to a network device, the method comprising:

[0042] Send configuration information, where the configuration information is used to indicate at least one of the following information:

[0043] Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data;

[0044] Determining a first moment of the latest first uplink data amount or the latest first residual delay: determining a moment of a first resource for sending the first uplink data amount and / or the first residual delay; a moment when the first resource arrives; and obtaining at least one of the moments of update indication information, the update indication information being used to indicate discarding of uplink data, or the update indication information being used to indicate a remaining uplink data amount and / or a remaining delay of the uplink data remaining after discarding;

[0045] Whether the terminal device cancels the triggered second report when uplink data is discarded;

[0046] first channel information, where the first channel information is used to determine whether to cancel the triggered second report;

[0047] Whether the terminal device re-evaluates the triggering condition of the second report when uplink data is discarded.

[0048] Whether the terminal device triggers a third report when uplink data is discarded, and the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

[0049] In a sixth aspect, an embodiment of the present application provides an information processing method, applied to a network device, the method comprising:

[0050] A first report is received, wherein the first report includes a latest first uplink data amount and / or a latest first residual delay of the uplink data.

[0051] In one possible design, the latest first uplink data amount and / or the latest first residual delay are determined at a first moment;

[0052] The first moment is at least one of the following: the moment of determining the first resource for sending the first report; the moment when the first resource arrives; the moment when update indication information is received, and the update indication information is used to indicate the amount of uplink data and / or the remaining delay after the discard occurs.

[0053] In one possible design, if uplink data is discarded, the second report is untriggered.

[0054] In one possible design, the second report is the first report; or, the second report includes a second uplink data volume and / or a second residual delay.

[0055] In one possible design, if the uplink data is discarded and there is no uplink data in the first channel, the second report is canceled and triggered, and the first channel includes at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

[0056] In one possible design, the logical channel is the logical channel that triggers the second report, the logical channel group is the logical channel group that triggers the second report, the PDU set is the PDU set that triggers the second report, or the data burst information is the data burst information that triggers the second report.

[0057] In one possible design, the method further includes:

[0058] A second report is received, where the second report is triggered when a triggering condition for the second report is determined to be met after the uplink data is discarded and re-evaluated.

[0059] In one possible design, the method further includes:

[0060] A third report is received, where the third report is triggered when uplink data is discarded, and the third report is used to update the uplink data amount and / or the remaining delay of the uplink data.

[0061] In one possible design, the third report is the first report or the second report.

[0062] In one possible design, the third report includes cause indication information, and the cause indication information is used to indicate that the third report is sent due to the discarding of uplink data, or to indicate that the amount of uplink data and / or the remaining delay included in the third report is obtained after the uplink data is discarded.

[0063] In one possible design, the third report includes the amount of discarded uplink data and / or delay information of the discarded uplink data.

[0064] In one possible design, the third report also includes the first channel corresponding to the discarded uplink data.

[0065] In one possible design, the discarded uplink data includes at least one PDU set.

[0066] In a seventh aspect, an embodiment of the present application provides an information processing device, including:

[0067] a processing module, configured to generate a first report, wherein the first report includes the latest first uplink data volume and / or the latest first residual delay of the uplink data;

[0068] A sending module is configured to transmit the first report.

[0069] In an eighth aspect, an embodiment of the present application provides an information processing device, including:

[0070] The sending module is used to send configuration information, where the configuration information is used to indicate at least one of the following information:

[0071] Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data;

[0072] Determining a first moment of the latest first uplink data amount or the latest first residual delay: determining a moment of a first resource for sending the first uplink data amount and / or the first residual delay; a moment when the first resource arrives; and obtaining at least one of the moments of update indication information, the update indication information being used to indicate discarding of uplink data, or the update indication information being used to indicate a remaining uplink data amount and / or a remaining delay of the uplink data remaining after discarding;

[0073] Whether the terminal device cancels the triggered second report when uplink data is discarded;

[0074] first channel information, where the first channel information is used to determine whether to cancel the triggered second report;

[0075] Whether the terminal device re-evaluates the triggering condition of the second report when uplink data is discarded.

[0076] Whether the terminal device triggers a third report when uplink data is discarded, and the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

[0077] In a ninth aspect, an embodiment of the present application provides an information processing device, including:

[0078] The receiving module is configured to receive a first report, wherein the first report includes the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0079] In a tenth aspect, an embodiment of the present application provides an information processing device, including:

[0080] The processing module is configured to cancel the triggered second report if the uplink data is discarded.

[0081] In an eleventh aspect, an embodiment of the present application provides an information processing device, including:

[0082] a processing module, configured to re-evaluate a triggering condition for a second report if uplink data is discarded;

[0083] The processing module is further configured to re-trigger the second report when the trigger condition is met.

[0084] In a twelfth aspect, an embodiment of the present application provides an information processing device, including:

[0085] The processing module is used to trigger a third report if uplink data is discarded, and the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

[0086] In a thirteenth aspect, an embodiment of the present application provides a terminal device, which may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a mobile phone, a smart TV, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0087] The terminal device includes: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the terminal device executes the method of the first aspect.

[0088] In a fourteenth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the methods of aspects 1 to 6.

[0089] In a fifteenth aspect, an embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is run, it enables the computer to execute the methods of aspects 1 to 6.

[0090] In the sixteenth aspect, an embodiment of the present application provides a chip, the chip including a processor, the processor being used to call a computer program in a memory to execute the methods described in the first to sixth aspects.

[0091] The present application provides an information processing method and apparatus to prevent a terminal device from reporting excess cache data volume and / or residual delay, thereby reducing waste of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0092] FIG1 is a schematic diagram of a communication scenario provided in an embodiment of the present application;

[0093] FIG2 is a flow chart of an information processing method provided in an embodiment of the present application;

[0094] FIG3 is a second flowchart of the information processing method provided in an embodiment of the present application;

[0095] FIG4 is a first schematic diagram of an implementation of canceling a trigger report provided in an embodiment of the present application;

[0096] FIG5 is a second schematic diagram of an implementation of canceling a trigger report provided in an embodiment of the present application;

[0097] FIG6 is a flowchart of the information processing method according to an embodiment of the present application;

[0098] FIG7 is a first schematic diagram of an implementation of a re-evaluation trigger condition provided in an embodiment of the present application;

[0099] FIG8 is a second schematic diagram of implementing the re-evaluation triggering condition provided in an embodiment of the present application;

[0100] FIG9 is a fourth flowchart of the information processing method provided in an embodiment of the present application;

[0101] FIG10 is a schematic diagram of the format of the third report provided in an embodiment of the present application;

[0102] FIG11 is a schematic diagram of discarding uplink data according to an embodiment of the present application;

[0103] FIG12 is a timing diagram of data discarding according to an embodiment of the present application;

[0104] FIG13 is a second schematic diagram of the format of the third report provided in an embodiment of the present application;

[0105] FIG14 is a third schematic diagram of the format of the third report provided in an embodiment of the present application;

[0106] FIG15 is a first structural diagram of an information processing device provided in an embodiment of the present application;

[0107] FIG16 is a second structural diagram of the information processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0108] In order to better understand the technical solution of this application, the relevant concepts and related technologies involved in this application are introduced below.

[0109] Terminal device: It can be a device that includes wireless transceiver functions and can cooperate with network devices to provide communication services to users. Specifically, terminal device can refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. For example, the terminal device can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, 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, an in-vehicle device, a wearable device, a terminal device in a future 5G network or a network after 5G, etc.

[0110] Network equipment: A network equipment may be a device used to communicate with a terminal device, for example, it may be a base station (BTS) in a Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) communication system, a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station (eNB or eNodeB) in an LTE system, or the network equipment may be a relay station, an access point, an in-vehicle device, a wearable device, a network-side device in a future 5G network or a network after 5G, or a network device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0111] The network devices involved in the embodiments of the present application may also be referred to as radio access network (RAN) devices. RAN devices are connected to terminal devices and are used to receive data from terminal devices and send it to core network devices. RAN devices correspond to different devices in different communication systems. For example, in 2G systems, they correspond to base stations and base station controllers, in 3G systems, they correspond to base stations and radio network controllers (RNCs), in 4G systems, they correspond to evolved base stations (eNBs), and in 5G systems, they correspond to access network devices (e.g., gNBs, centralized units CUs, and distributed units DUs) in new radio (NR).

[0112] Below, with reference to FIG1 , the scenarios to which the resource processing method in this application is applicable are described.

[0113] FIG1 is a schematic diagram of a communication scenario provided by an embodiment of the present application. Referring to FIG1 , a network device 101 and a terminal device 102 are provided. Wireless communication can be performed between the network device 101 and the terminal device 102. The terminal device 102 can communicate with at least one core network via a radio access network (RAN).

[0114] Among them, the communication system can be a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a Long Term Evolution (LTE) system or a fifth-generation mobile communication (5th-Generation, 5G) system.

[0115] Correspondingly, the network device can be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved NodeB (eNB), an access point (AP) or a relay station in an LTE system, or a base station in a 5G system, etc., without limitation here.

[0116] The 5G mobile communication system described in this application includes a non-standalone (NSA) 5G mobile communication system and / or a standalone (SA) 5G mobile communication system. The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The communication system can also be a PLMN network, a device-to-device (D2D) network, a machine-to-machine (M2M) network, an IoT network, or other networks.

[0117] It is understandable that if the technical solutions of the embodiments of the present application are applied to other wireless communication networks, the corresponding names can also be replaced by the names of corresponding functions in other wireless communication networks.

[0118] 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 will 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.

[0119] Based on the above introduction, the following briefly explains PDU (Protocol Data Unit) and PDU set.

[0120] PDU is the data unit for data transmission between peer layers. PDU can be established at each layer. The Radio Link Control (RLC) layer can establish RLC PDU, the Packet Data Convergence Protocol (PDCP) layer can establish PDCP PDU, and the Media Access Control (MAC) layer can establish MAC PDU.

[0121] Currently, the concept of PDU set has been introduced in related technologies. For example, multiple PDUs can constitute a PDU set. Generally, the data volume of a PDU set ranges from several Mbits (megabits) to several hundred Mbits.

[0122] For the NR system, the terminal device will cache data at the RLC layer and PDCP layer. If the PDU set is discarded, the amount of cached data in the terminal device will change significantly.

[0123] The following briefly describes the BSR and the residual delay report.

[0124] In the NR system, the terminal device can store uplink data in a buffer and then apply for uplink resources from the network device through the BSR. The BSR is used to provide uplink data volume information to the network device, which can convey information about the amount of uplink data that needs to be transmitted in the buffer of the terminal device.

[0125] And, uplink data may have residual delay. In one possible implementation, the BSR may carry residual delay information to inform the network device of the residual delay of the uplink data through the BSR. That is to say, the BSR in this application may be understood as a report on both the cache status and the residual delay. Alternatively, the BSR and the residual delay report are two independent reports, wherein the BSR is used to provide information on the amount of uplink data, and the residual delay report is used to provide information on the residual delay of the uplink data. In the actual implementation process, whether the BSR and the residual delay report are an integrated report or two independent reports can be selected according to actual needs.

[0126] Based on the above description, it can be determined that the terminal device can provide the network device with data volume information and residual delay information of the uplink data by sending a BSR and / or a residual delay report to the network device.

[0127] However, because PDU sets may be discarded, uplink data is discarded. If the terminal device has already reported the amount of uplink data or the remaining latency of uplink data before the PDU set is discarded and is waiting for allocation from the network device, the terminal device will report excess uplink data, and the network device may allocate excess uplink resources, resulting in wasted resources, potentially increasing the burden on the network side, and deteriorating the overall link performance.

[0128] In view of the technical problems described above, it is urgently necessary to provide a method for timely updating the changes in uplink data caused by the PDU set, thereby reducing the waste of resources.

[0129] The information processing method provided by this application is introduced below in conjunction with specific embodiments, and first the relevant embodiments on the terminal device side are described.

[0130] FIG2 is a flowchart of an information processing method provided in an embodiment of the present application.

[0131] As shown in FIG2 , the method includes:

[0132] S201. Generate or transmit a first report, where the first report includes the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0133] In this embodiment, when the triggering condition of the first report is met, the first report may be triggered. After the first report is triggered, if valid resources exist, the first report may be generated or transmitted on the valid resources. The first report may include the data volume of the uplink data in the latest state, which is referred to as the first uplink data volume in this embodiment.

[0134] And / or, the first report in this embodiment may further include the residual delay of the uplink data in the latest state, which is referred to as the first residual delay in this embodiment.

[0135] Among them, the uplink data is, for example, data cached in the buffer of the terminal device to be sent. The uplink data can be data transmitted for the first time or data transmitted repeatedly, so the data volume can be the cached data volume, and this embodiment does not limit this.

[0136] In this embodiment, the first report may be a BSR, which may include the first uplink data volume and / or the first residual delay.

[0137] The following is a brief description of the BSR format. The BSR MAC CE (Control Element) can be divided into six categories: Short BSR format, Short Truncated BSR format, Long BSR format, Long Truncated BSR format, Extended Short BSR format, and Extended Short Truncated BSR format.

[0138] Alternatively, the first report in this embodiment may further include two independent reports, a BSR and a residual delay report, wherein the BSR includes the first uplink data volume, and the residual delay report includes the first residual delay.

[0139] In one possible implementation, when the BSR and the remaining delay report are two independent reports, the two reports can be sent or generated based on the logical channel priority after the BSR or the remaining delay report is triggered, wherein the logical channel priority of the BSR is higher than the logical channel priority of the remaining delay report. Because reporting the buffer capacity is better for scheduling optimization than reporting the remaining delay with respect to uplink scheduling, the logical channel priority of the BSR should be higher than the logical channel priority of the remaining delay report. During transmission, when the result based on the uplink logical channel priority is met and the BSR can be sent through the valid uplink resources, the BSR is generated or transmitted. Similarly, when the result based on the uplink logical channel priority is met and the remaining delay report can be sent through the valid uplink resources, the remaining delay report is generated or transmitted.

[0140] In the above two examples, the first report may further include at least one item of logical channel information, logical channel group information, PDU set information, or data burst information corresponding to the first uplink data volume and / or the first residual delay. That is, the first uplink data volume or the first residual delay is calculated based on at least one item of logical channel information, logical channel group information, PDU set information, or data burst information. In other words, the first report includes the buffered data volume and / or residual delay of at least one logical channel, logical channel group, PDU set, or data burst.

[0141] This embodiment sets the first report to include the first uplink data volume and / or the first residual delay of the uplink data in the latest state, thereby ensuring that even if the uplink data is discarded, the first report also includes relevant information of the discarded uplink data, so as to avoid the situation where no uplink data is discarded when the first report is triggered, but the uplink data is discarded before the first report is generated or transmitted, resulting in the first report including excess cache data volume or residual delay, thereby wasting resources.

[0142] In order to ensure that the first report includes the latest first uplink data volume and / or the latest first residual delay of the uplink data, it is very important to determine the moment of the first uplink data volume and / or the first residual delay. In this embodiment, the latest first uplink data volume and / or the latest first residual delay can be determined at the first moment.

[0143] In one possible implementation, the first moment in this embodiment is at least one of the following: the moment of determining the first resource for sending the first report; the moment of arrival of the first resource; the moment of obtaining the update indication information, the update indication information is used to indicate the discarding of uplink data, or the update indication information is used to indicate the remaining uplink data amount after the discarding and / or the remaining delay of the uplink data remaining after the discarding occurs.

[0144] First, the first resource is explained. After the first report is triggered, it is necessary to further determine the valid resources that can be used to send the first report. In this embodiment, the valid resources that can be used to send the first report are referred to as first resources.

[0145] In this embodiment, the first moment may be the moment when the first resource is determined. After the first resource is determined, it usually takes some time for the first resource to actually arrive. The first moment may also be the moment when the first resource arrives.

[0146] It can be understood that whether it is the time of determining the first resource or the time of arrival of the first resource, it should be as early as possible before the time of sending the BSR and as close as possible to the time of sending the BSR. That is to say, before sending the BSR, the uplink data amount and the remaining delay are determined at the latest possible time, so as to ensure that the first uplink data amount and the first remaining delay in the first report are the latest relevant data as much as possible.

[0147] Next, the update indication information is described. The MAC layer can obtain the update indication information sent by the higher layer. In one possible implementation, the update indication information is used to indicate the discard of uplink data. The first uplink data volume and / or the first remaining delay in the latest state after the discard can be determined based on the obtained update indication information. Alternatively, the update indication information is also used to indicate the remaining uplink data volume and / or the remaining delay of the uplink data remaining after the discard. In this case, the first uplink data volume and / or the first remaining delay can be directly obtained from the update indication information.

[0148] In the case where the first moment is the moment when the update indication information is obtained, it is possible that before the first report is sent, the first report itself already contains a determined uplink data amount and / or remaining delay. After the update indication information is obtained, the uplink data amount and / or remaining delay contained in the first report can be updated so that the first report includes the latest first uplink data amount and / or first remaining delay.

[0149] Alternatively, it is also possible that before the first report is sent, the uplink data amount and / or the remaining delay have not been determined in the first report itself. Then, after obtaining the update indication information, the first uplink data amount and / or the first remaining delay in the first report can be determined.

[0150] The above introduces possible methods for determining the first moment. Determining the relevant data in the first report at these moments can ensure that after the first report is triggered but before the first report is sent, if uplink data is discarded, the first report contains the data volume and / or remaining delay of the uplink data in the latest state, thereby avoiding the situation where no uplink data is discarded when the first report is triggered, but uplink data is discarded before the first report is generated or transmitted, resulting in the first report containing excess uplink data volume, which in turn leads to waste of resources scheduled by the network device.

[0151] The above embodiment introduces an implementation method for avoiding resource waste by setting the first report to include the latest first uplink data volume and / or the latest first residual delay. Another possible implementation method in the present application is described below in conjunction with Figures 3-5. Figure 3 is a second flowchart of the information processing method provided in an embodiment of the present application, Figure 4 is a first schematic diagram of the implementation of canceling the trigger report provided in an embodiment of the present application, and Figure 5 is a second schematic diagram of the implementation of canceling the trigger report provided in an embodiment of the present application.

[0152] As shown in FIG3 , the method includes:

[0153] S301. If uplink data is discarded, cancel the triggered second report.

[0154] In this embodiment, the uplink data may be discarded when the first data stream is discarded. The first data stream may be a PDU set, a data burst or other data stream. The first data stream may be a data stream including one or more data units (PDU, SDU).

[0155] In this embodiment, whether uplink data is discarded may be determined by obtaining indication information related to data discard (which may be obtained from the network side or implemented through internal interaction of the terminal device), thereby determining whether uplink data is discarded.

[0156] In this embodiment, the second report may be the first report described above, that is, the second report includes the latest first uplink data volume and / or the latest first residual delay.

[0157] Alternatively, the second report may also be different from the first report introduced above. The second report includes the second uplink data volume and / or the second residual delay of the uplink data. This embodiment does not limit the time for determining the second uplink data volume and the second residual delay. It can be determined at any time after the second report is triggered. Therefore, whether the second uplink data volume in the second report is the data volume of the uplink data in the latest state, and whether the second residual delay in the second report is the residual delay of the uplink data in the latest state, this application does not limit.

[0158] It can be understood that the discard of uplink data is a condition for canceling the triggered second report.

[0159] The following describes the implementation of the two aforementioned second reports in this embodiment. It should be noted that the first report and the second report triggered, generated, or transmitted in this embodiment refer to a certain type of report, rather than a specific report.

[0160] In one possible implementation, the embodiment of canceling the triggered second report is used as an independent embodiment to solve the technical problem of the present application. In this case, the second report in this embodiment can be the report introduced above including the second uplink data and / or the second residual delay of the uplink data.

[0161] First, the implementation of triggering the second report is described. When the triggering conditions for the second report are met, the second report is triggered. The second report can be a BSR and / or a residual delay report. The triggering conditions for the second report can be either the BSR or the residual delay report. Subsequently, if uplink data is discarded, the triggered second report can be canceled.

[0162] When uplink data is discarded, by canceling the triggered second report, it can be ensured that the second report including excess uplink data volume and / or excess residual delay will not be sent to the network device, and the network device will not schedule excess uplink resources, thereby effectively avoiding resource waste.

[0163] In one implementation, after data discard occurs, the triggered second report can be directly canceled. Alternatively, a further determination can be made as to whether uplink data exists in the first channel. If no uplink data exists in the first channel, the triggered second report is canceled. The first channel may include at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

[0164] In one implementation, the logical channel introduced above can be any logical channel, or the logical channel introduced above can also be the logical channel that triggers the second report. The logical channel group introduced above can be any logical channel group, or the logical channel group introduced above can also be the logical channel group that triggers the second report. The PDU set introduced above can be any PDU set, or the PDU set introduced above can also be the PDU set that triggers the second report. The data burst information introduced above can be any data burst information, or the data burst information introduced above can also be the data burst information that triggers the second report. By setting the first channel as the channel that triggers the second report, the rationality of the cancellation of the second report can be effectively guaranteed. That is, there are the following implementations:

[0165] Implementation method 1: After data discard occurs, determine whether there is uplink data in the logical channel. When there is no uplink data in any logical channel, cancel the triggered second report.

[0166] In one implementation, after the second report is triggered, uplink data is discarded before the second report is generated or transmitted, and no uplink data exists in any logical channel, and the triggered second report is canceled.

[0167] In one implementation, after the second report is triggered, uplink data is discarded during the process of generating the second report, and there is no uplink data in any logical channel, and the triggered second report is canceled.

[0168] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0169] Implementation method 2: After data discard occurs, determine whether there is uplink data in the logical channel group. When there is no uplink data in any logical channel group, cancel the triggered second report.

[0170] In one implementation, after the second report is triggered, uplink data is discarded before the second report is generated or transmitted, and no uplink data exists in any logical channel group, and the triggered second report is canceled.

[0171] In one implementation, after the second report is triggered, uplink data is discarded during the process of generating the second report, and there is no uplink data in any logical channel group, and the triggered second report is canceled.

[0172] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0173] Implementation method 3: After data discard occurs, determine whether there is uplink data in the PDU set. When there is no uplink data in any PDU set, cancel the triggered second report.

[0174] In one implementation, after the second report is triggered, uplink data is discarded before the second report is generated or transmitted, and there is no uplink data in any PDU set, and the triggered second report is canceled.

[0175] In one implementation, after the second report is triggered, uplink data is discarded during the process of generating the second report, and there is no uplink data in any PDU set, and the triggered second report is canceled.

[0176] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0177] Implementation method 4: After data discard occurs, it is determined whether there is uplink data in the data burst information. When there is no uplink data in any data burst information, the triggered second report is canceled.

[0178] In one implementation, after the second report is triggered and before the second report is generated or transmitted, if uplink data is discarded and no uplink data exists in any data burst information, the triggered second report is canceled.

[0179] In one implementation, after the second report is triggered, if uplink data is discarded during the process of generating the second report and there is no uplink data in any data burst information, the triggered second report is canceled.

[0180] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0181] Implementation method 5: After data discard occurs, determine whether there is uplink data in the logical channel. When the logical channel that triggers the second report does not have uplink data, cancel the triggered second report.

[0182] In one implementation, after the second report is triggered, uplink data is discarded before the second report is generated or transmitted, and no uplink data exists in the logical channel that triggers the second report, and the triggered second report is canceled.

[0183] In one implementation, after the second report is triggered, uplink data is discarded during the process of generating the second report, and no uplink data exists in the logical channel that triggers the second report, so the triggered second report is canceled.

[0184] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0185] Implementation method 6: After data discard occurs, determine whether there is uplink data in the logical channel group. When the logical channel group that triggers the second report does not have uplink data, cancel the triggered second report.

[0186] In one implementation, after the second report is triggered, uplink data is discarded before the second report is generated or transmitted, and no uplink data exists in the logical channel group that triggers the second report, and the triggered second report is canceled.

[0187] In one implementation, after the second report is triggered, uplink data is discarded during the process of generating the second report, and no uplink data exists in the logical channel group that triggers the second report, and the triggered second report is canceled.

[0188] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0189] Implementation method 7: After data discard occurs, determine whether there is uplink data in the PDU set. When the PDU set that triggers the second report does not have uplink data, cancel the triggered second report.

[0190] In one implementation, after the second report is triggered, uplink data is discarded before the second report is generated or transmitted, and there is no uplink data in the PDU set that triggers the second report, and the triggered second report is canceled.

[0191] In one implementation, after the second report is triggered, uplink data is discarded during the process of generating the second report, and there is no uplink data in the PDU set that triggers the second report, so the triggered second report is canceled.

[0192] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0193] Implementation method 8: After data discard occurs, determine whether there is uplink data in the data burst information. When the data burst information triggering the second report does not contain uplink data, cancel the triggered second report.

[0194] In one implementation, after the second report is triggered and before the second report is generated or transmitted, uplink data is discarded, and there is no uplink data in the data burst information that triggers the second report, and the triggered second report is canceled.

[0195] In one implementation, after the second report is triggered, uplink data is discarded during the process of generating the second report, and there is no uplink data in the data burst information that triggers the second report, so the triggered second report is canceled.

[0196] In one implementation, after the uplink data is discarded and the triggered second report is cancelled, the triggering condition of the second report may be re-evaluated, and the second report may be re-triggered when the triggering condition is met.

[0197] For the eight different implementation methods introduced above, whether the triggering conditions of the second report need to be re-evaluated after the triggered second report is canceled may depend on the implementation, that is, it may be re-evaluated or not, and this embodiment does not limit it.

[0198] If the triggering condition is re-evaluated, the re-triggered second report must include the data volume and / or remaining delay of the uplink data after the discard. Therefore, the latest uplink data volume and / or remaining delay can be reported through the re-triggered second report, thereby avoiding resource waste.

[0199] The above description can be understood with reference to FIG4 . As shown in FIG4 , assuming that the second report a is triggered at time t1 and uplink data is discarded at time t2 , the triggered second report a can be canceled at time t2 . Alternatively, the triggered second report a can be canceled at a time after time t2 , which is not limited in this embodiment.

[0200] The triggering conditions for the second report a can then be re-evaluated. If so, the second report b can be triggered at time t3. The dashed box in Figure 4 illustrates that the re-evaluation and triggering of the second report are optional. It is understood that although the second report is triggered at both time t1 and time t3, different reports are triggered at different times, but the same type of second report is triggered.

[0201] FIG4 merely illustrates one possible scenario. In actual implementation, the time sequence of canceling the triggered second report and re-triggering the second report may be determined according to actual needs.

[0202] In another possible implementation, the second report in this embodiment may be the first report described above. The following describes the implementation in which the second report is the first report.

[0203] If uplink data is discarded, the triggered first report can be canceled to ensure that the first report including excess uplink data volume and / or excess residual delay will not be sent to the network device, and the network device will not schedule excess uplink resources, thereby effectively avoiding resource waste.

[0204] In one implementation, after uplink data is discarded, the triggered first report can be directly canceled. Alternatively, a further determination can be made as to whether uplink data exists in the first channel. If no uplink data exists in the first channel, the triggered first report is canceled. The first channel can include at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

[0205] In one implementation, the logical channel introduced above can be any logical channel, or the logical channel introduced above can also be the logical channel that triggers the first report. The logical channel group introduced above can be any logical channel group, or the logical channel group introduced above can also be the logical channel group that triggers the first report. The PDU set introduced above can be any PDU set, or the PDU set introduced above can also be the PDU set that triggers the first report. The data burst information introduced above can be any data burst information, or the data burst information introduced above can also be the data burst information that triggers the first report. By setting the first channel as the channel that triggers the first report, the rationality of the cancellation of the first report can be effectively guaranteed. That is, there are the following implementations:

[0206] Implementation method 1: After data discard occurs, determine whether there is uplink data in the logical channel. When there is no uplink data in any logical channel, cancel the triggered first report.

[0207] In one implementation, after the first report is triggered, uplink data is discarded before the first report is generated or transmitted, and no uplink data exists in any logical channel, and the triggered first report is canceled.

[0208] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and there is no uplink data in any logical channel, so the triggered first report is canceled.

[0209] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0210] Implementation method 2: After data discard occurs, determine whether there is uplink data in the logical channel group. When there is no uplink data in any logical channel group, cancel the triggered first report.

[0211] In one implementation, after the first report is triggered, uplink data is discarded before the first report is generated or transmitted, and no uplink data exists in any logical channel group, and the triggered first report is canceled.

[0212] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and there is no uplink data in any logical channel group, so the triggered first report is canceled.

[0213] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0214] Implementation method 3: After data discard occurs, determine whether there is uplink data in the PDU set. When there is no uplink data in any PDU set, cancel the triggered first report.

[0215] In one implementation, after the first report is triggered, uplink data is discarded before the first report is generated or transmitted, and there is no uplink data in any PDU set, and the triggered first report is canceled.

[0216] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and there is no uplink data in any PDU set, so the triggered first report is canceled.

[0217] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0218] Implementation method 4: After data discard occurs, it is determined whether there is uplink data in the data burst information. When any data burst information does not contain uplink data, the triggered first report is canceled.

[0219] In one implementation, after the first report is triggered and before the first report is generated or transmitted, if uplink data is discarded and no uplink data exists in any data burst information, the triggered first report is canceled.

[0220] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and no uplink data exists in any data burst information, so the triggered first report is canceled.

[0221] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0222] Implementation method 5: After data discard occurs, determine whether there is uplink data in the logical channel. When the logical channel that triggers the first report does not have uplink data, cancel the triggered first report.

[0223] In one implementation, after the first report is triggered, uplink data is discarded before the first report is generated or transmitted, and no uplink data exists in the logical channel that triggers the first report, and the triggered first report is canceled.

[0224] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and no uplink data exists in the logical channel that triggers the first report, so the triggered first report is canceled.

[0225] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0226] Implementation method 6: After data discard occurs, determine whether there is uplink data in the logical channel group. When the logical channel group that triggers the first report does not have uplink data, cancel the triggered first report.

[0227] In one implementation, after the first report is triggered, uplink data is discarded before the first report is generated or transmitted, and no uplink data exists in the logical channel group that triggers the first report, and the triggered first report is canceled.

[0228] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and no uplink data exists in the logical channel group that triggers the first report, so the triggered first report is canceled.

[0229] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0230] Implementation method 7: After data discard occurs, determine whether there is uplink data in the PDU set. When the PDU set that triggers the first report does not have uplink data, cancel the triggered first report.

[0231] In one implementation, after the first report is triggered, uplink data is discarded before the first report is generated or transmitted, and there is no uplink data in the PDU set that triggers the first report, and the triggered first report is canceled.

[0232] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and there is no uplink data in the PDU set that triggers the first report, so the triggered first report is canceled.

[0233] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0234] Implementation method 8: After data discard occurs, it is determined whether there is uplink data in the data burst information. When the data burst information triggering the first report does not contain uplink data, the triggered first report is canceled.

[0235] In one implementation, after the first report is triggered and before the first report is generated or transmitted, uplink data is discarded, and there is no uplink data in the data burst information that triggers the first report, and the triggered first report is canceled.

[0236] In one implementation, after the first report is triggered, uplink data is discarded during the process of generating the first report, and there is no uplink data in the data burst information that triggers the first report, so the triggered first report is canceled.

[0237] In one implementation, after the uplink data is discarded and the triggered first report is cancelled, the triggering condition of the first report may be re-evaluated, and the first report may be re-triggered when the triggering condition is met.

[0238] For the eight different implementation methods introduced above, whether the triggering condition of the first report needs to be re-evaluated after the triggered first report is canceled may depend on the implementation, that is, it may be re-evaluated or not, and this embodiment does not limit it.

[0239] If the triggering conditions are re-evaluated, the re-triggered first report must include relevant data of the uplink data after the discard. Therefore, the latest uplink data volume and / or remaining delay can be reported through the re-triggered first report, thereby avoiding resource waste.

[0240] For example, the above description can be understood with reference to FIG5 . As shown in FIG5 , assuming that a first report c is triggered at time t1 and uplink data is discarded at time t2 , the triggered first report c can be canceled at time t2 . Alternatively, the triggered first report c can be canceled at a time after time t2 , which is not limited in this embodiment.

[0241] Afterwards, it may be re-evaluated whether the triggering condition of the first report c is satisfied. If so, the first report d may be triggered at time t3. In FIG5 , the dashed box indicates that the execution of the re-evaluation is optional.

[0242] FIG5 merely illustrates a possible situation. In actual implementation, the time sequence of canceling the triggered first report and re-triggering the first report can be determined according to actual needs.

[0243] The embodiments of Figures 3 to 5 above illustrate that after uplink data is discarded, the triggered second report can be canceled. Whether to re-evaluate the triggering conditions can be determined based on actual needs. In another possible implementation, after uplink data is discarded, the triggering conditions can be directly re-evaluated. Whether to cancel the triggered second report can be determined based on actual needs. The implementation of the latter embodiment is described below in conjunction with Figures 6 to 8.

[0244] Figure 6 is a flowchart of the information processing method provided in an embodiment of the present application. Figure 7 is a schematic diagram of the implementation of the re-evaluation trigger condition provided in an embodiment of the present application. Figure 8 is a schematic diagram of the implementation of the re-evaluation trigger condition provided in an embodiment of the present application.

[0245] As shown in FIG6 , the method includes:

[0246] S601: If uplink data is discarded, re-evaluate the triggering condition of the second report.

[0247] S602: When a trigger condition is met, trigger a second report.

[0248] In this embodiment, the uplink data may be discarded when the first data stream is discarded. The first data stream may be a PDU set, a data burst or other data stream. The first data stream may be a data stream including one or more data units (PDU, SDU).

[0249] In this embodiment, whether uplink data is discarded may be determined by obtaining indication information related to data discard (which may be obtained from the network side or implemented through internal interaction of the terminal device), thereby determining whether uplink data is discarded.

[0250] In this embodiment, S601 and S602 may also be described as re-triggering the second report if uplink data is discarded.

[0251] In this embodiment, the second report may be the first report described above, that is, the second report includes the latest first uplink data volume and / or the latest first residual delay.

[0252] Alternatively, the second report may also be different from the first report introduced above, and the second report may include the second uplink data amount and / or the second residual delay of the uplink data. However, this embodiment does not limit the time for determining the second uplink data amount and the second residual delay, which may be determined at any time after the second report is triggered. Therefore, this embodiment does not limit whether the second uplink data amount in the second report is the data amount of the uplink data in the latest state, and whether the second residual delay in the second report is the residual delay of the uplink data in the latest state.

[0253] The following describes the implementation of the two aforementioned second reports in this embodiment. It should be noted that the first report and the second report triggered, generated, or transmitted in this embodiment refer to a certain type of report, rather than a specific report.

[0254] In one possible implementation, re-evaluating the triggering condition to trigger the second report is used as an independent embodiment to solve the technical problem of the present application. In this case, the second report in this embodiment can be the report introduced above including the second uplink data and / or the second residual delay of the uplink data.

[0255] If uplink data is discarded, the triggering conditions for the second report are re-evaluated. If the triggering conditions are determined to be met, the second report is re-triggered. The re-triggered second report must include the data volume and / or remaining latency of the uplink data after the discard. Therefore, the re-triggered second report can report the latest uplink data volume and / or remaining latency, thereby avoiding resource waste.

[0256] In this embodiment, after uplink data is discarded, the triggering conditions for the second report can be re-evaluated. Whether to cancel the triggered second report during this period depends on the implementation, and may or may not be canceled. This embodiment does not impose any restrictions on this. If the triggered second report is to be canceled, the relevant implementation is similar to that described in the above embodiment and will not be repeated here.

[0257] For example, the above description can be understood with reference to Figure 7. As shown in Figure 7, assuming that second report a is triggered at time t1 and uplink data is discarded at time t2, the triggering condition of second report a can be re-evaluated. Assuming that the triggering condition is determined to be met at time t3, second report b is triggered. It can be understood that although second reports are triggered at both time t1 and time t3, different reports are triggered at different times, but they trigger the same type of second report.

[0258] Optionally, the triggered second report a may be canceled at time t4. In FIG7 , a dotted box is used to indicate that canceling the triggered second report is optional.

[0259] FIG7 illustrates only one possible scenario. In actual implementation, the order of canceling the triggered second report and re-triggering the second report can be determined based on actual needs. Furthermore, the timing of re-evaluating the triggering condition and the timing of discarding the uplink data can be the same, or the timing of re-evaluating the triggering condition can be after the uplink data is discarded.

[0260] In another possible implementation, the second report in this embodiment may be the first report described above. The following describes the implementation in which the second report is the first report.

[0261] If uplink data is discarded, the triggering conditions of the first report can be re-evaluated. If the triggering conditions are determined to be met, the first report can be re-triggered. The re-triggered first report must include the data volume and / or remaining latency of the uplink data after the discard. Therefore, the re-triggered first report can report the latest uplink data volume and / or remaining latency, thereby avoiding resource waste.

[0262] In this embodiment, after uplink data is discarded, the triggering condition for the first report can be re-evaluated. Whether to cancel the triggered first report during this period depends on the implementation, and may or may not be canceled. This embodiment does not impose any restrictions on this. If the triggered first report is to be canceled, the relevant implementation is similar to that described in the above embodiment and will not be repeated here.

[0263] For example, the above description can be understood with reference to FIG8 . As shown in FIG8 , assuming that the first report c is triggered at time t1 and uplink data is discarded at time t2 , the triggering condition of the first report c can be re-evaluated. Assuming that the triggering condition is met at time t3 , the first report d is triggered.

[0264] Optionally, the triggered first report d may be canceled at time t4. In FIG8 , a dotted box is used to indicate that canceling the triggered first report is optional.

[0265] FIG8 illustrates only one possible scenario. In actual implementation, the order of canceling the triggered first report and triggering the first report can be determined based on actual needs. Furthermore, the timing of re-evaluating the triggering condition and the timing of discarding the uplink data can be the same, or the timing of re-evaluating the triggering condition can be after the uplink data is discarded.

[0266] The above embodiment describes a case where uplink data loss occurs when a report is triggered but not yet sent. That is, a triggered report exists. In this case, the corresponding triggered report can be canceled and re-triggered. However, there is another case where the triggered report has already been sent. In this case, if uplink data loss occurs, because the triggered report no longer exists, the uplink data loss can be used as a triggering condition to trigger a report, thereby updating the network device with the reported uplink data volume and / or the remaining uplink data delay. The following describes a case where uplink data loss occurs only after a report has been sent.

[0267] The following is introduced in conjunction with FIG9 , which is a fourth flowchart of the information processing method provided in an embodiment of the present application.

[0268] As shown in FIG9 , the method includes:

[0269] S901: If uplink data is discarded, a third report is triggered, where the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

[0270] In this embodiment, when uplink data is discarded, the terminal device may have sent at least one report, but has not yet received the uplink resources allocated by the network device. In this case, a third report may be triggered.

[0271] In this embodiment, the third report can be the first report or the second report described above. In this case, the third report can include the amount of uplink data remaining after discarding and / or the remaining delay. Alternatively, the third report can be a separate report, that is, the third report is neither a BSR nor a remaining delay report. In this case, the third report can include the amount of discarded uplink data and / or the remaining delay of the discarded uplink data. The following describes the implementation of the two third report scenarios in this embodiment.

[0272] The third report in this embodiment is used to update the uplink data volume and / or the uplink data volume. The "update" here is for the purpose of describing the two situations of the third report in a higher level. The meaning of "update" in the two situations of the third report is further explained below.

[0273] When the third report is the first report or the second report, the third report may include the first uplink data volume and / or the first residual delay, the second uplink data volume and / or the second residual delay. Then, by sending the third report to the network device, the network device can promptly determine the remaining data after the discard, thereby updating the previously received uplink data volume and / or the residual delay of the uplink data to achieve an update of the reported data. In this case, step S901 can be further described as follows: if uplink data is discarded, triggering the third report, the third report including the first uplink data volume and / or the first residual delay, the second uplink data volume and / or the second residual delay.

[0274] When the third report is a separate report, the third report may include the amount of discarded uplink data and / or the remaining delay of the discarded uplink data. By sending the third report to the network device, the network device can promptly determine the data discard situation, thereby updating the previously received amount of uplink data and / or the remaining delay of the uplink data, thereby updating the reported data. In this case, step S901 can be further described as follows: if uplink data is discarded, triggering the third report, the third report including the amount of discarded uplink data and / or the remaining delay of the discarded uplink data.

[0275] The following further introduces the implementation methods for the two cases in the third report.

[0276] First, the implementation of the third report being the first report or the second report described above is introduced. The format of the third report when it is the first report or the second report can be understood in conjunction with Figure 10, which is a schematic diagram of the format of the third report provided in an embodiment of the present application.

[0277] As shown in Figure 10, the third report may include a buffer size. When the third report is a first report, the buffer size in the third report is used to indicate the first uplink data volume described above. When the third report is a second report, the buffer size in the third report is used to indicate the second uplink data volume described above.

[0278] And / or, the third report may further include residual delay information. When the third report is the first report, the residual delay information in the third report is the first residual delay described above. When the third report is the second report, the residual delay information in the third report is the second residual delay described above.

[0279] As shown in FIG10 , the third report may also include cause indication information P1, which is used to indicate that the third report was triggered due to uplink data discard. This cause indication information is related to the uplink data discard and may be used to indicate that the data buffer information and / or residual delay information included in the third report was obtained after the uplink data discard.

[0280] There are also multiple possible implementations of the cause indication information in this embodiment, which are described below:

[0281] Implementation 1: The cause indication information is used to indicate that the third report is triggered due to uplink data discard, or the cause indication information is used to indicate that the uplink data volume and / or remaining delay included in the third report is obtained after uplink data discard.

[0282] It can also be understood that the cause indication information is used to indicate that uplink data has been discarded.

[0283] In this implementation, the cause indication information does not indicate which specific first channel has discarded the uplink data.

[0284] In this implementation, for example, when the cause indication information is 1, it may indicate that the third report is triggered due to the discarding of uplink data, but the cause indication information does not specifically indicate which first channel has the data discarded.

[0285] Implementation method 2: The cause indication information is used to indicate that the third report is triggered due to the discard of uplink data, and also indicates the first channel where the discard occurs.

[0286] It can also be understood that the cause indication information is used to indicate that uplink data is discarded on the first channel.

[0287] Alternatively, the cause indication information is used to indicate that the uplink data volume and / or the remaining delay included in the third report are obtained after the uplink data is discarded, and also indicates the first channel where the discard occurs.

[0288] It can also be understood that the cause indication information is used to indicate that the uplink data volume and / or the remaining delay of the first channel in the third report are obtained after the uplink data is discarded.

[0289] In this implementation, the cause indication information may correspond to a first channel, a cached data volume, and a remaining delay information, that is, the cause indication information indicates that data discard has occurred in the first channel, and the cached data volume and / or remaining delay information in the third report are obtained after data discard has occurred in the first channel.

[0290] In one implementation, the cause indication information may include bits corresponding to multiple first channels. When the bit corresponding to a first channel is 1, it indicates that data discard has occurred in the first channel. For example, assuming that the cause indication information includes bits corresponding to eight logical channel groups, denoted as P0 to P7, and assuming that data discard has occurred in LCG0 and LCG1, P0 and P1 may be set to 1 in the cause indication information to indicate that data discard has occurred in LCG0 and LCG1.

[0291] By including cause indication information in the third report, the network device can quickly determine the reason for sending the third report based on the cause indication information, or quickly determine whether the uplink data volume and / or remaining delay included in the third report was obtained after uplink data was discarded. If the uplink data was sent due to discarded uplink data, or was obtained after uplink data was discarded, the uplink data volume and / or remaining delay can be updated accordingly in a timely manner to determine the latest uplink data information, thereby allocating correct uplink resources and avoiding resource waste.

[0292] The cause indication information introduced above may be added to a short BSR MAC CE, a short truncated BSR MAC CE, a long BSR MAC CE, a long truncated BSR MAC CE, an extended short BSR MAC CE, or an extended short truncated BSR MAC CE. This embodiment does not limit the specific format of the BSR.

[0293] The above describes the relevant implementation of the format of the third report. The format of the first report and the format of the second report described above are the same as the format of the third report described here.

[0294] The following further describes the implementation of triggering the third report when uplink data is discarded. The implementation of the first report and the implementation of the second report described above are the same as the implementation of the third report described here.

[0295] The triggering of the third report is implemented at the MAC layer of the terminal device. However, the loss of uplink data occurs at the RLC layer or the PDCP layer. Therefore, it involves the problem of how the MAC layer determines whether the uplink data is discarded.

[0296] The MAC layer may receive higher-layer indication information, which may indicate that uplink data has been discarded. The higher-layer indication information may be sent by the RLC layer or the PDCP layer. After receiving the higher-layer indication information, the MAC layer may determine that uplink data has been discarded, and may trigger a third report based on the higher-layer indication information, and subsequently generate and transmit the third report.

[0297] Furthermore, the discarded first channel may be indicated in the high-layer indication information. After receiving the high-layer indication information, the MAC layer may further determine whether the discarded first channel has triggered a third report based on the high-layer indication information.

[0298] If the first channel where the discard occurred has triggered the third report, it means that the cached data volume and / or remaining delay information has been reported to the network device. In this case, the third report needs to be triggered to update the data volume and / or remaining delay that have been reported to the network device.

[0299] Alternatively, if the first channel where the discard occurred has not yet triggered the third report, then this means that the buffered data volume and / or remaining latency information has not yet been reported to the network device. In this case, there is no need to trigger the third report to update the data volume and / or remaining latency. By determining whether the first channel where the discard occurred has triggered the third report, and then determining whether to trigger the third report, the necessity and effectiveness of triggering the third report can be effectively improved.

[0300] The above-mentioned contents can be further understood by combining a specific example of uplink data discarding with FIG11 and FIG12 . FIG11 is a schematic diagram of discarding uplink data provided in an embodiment of the present application, and FIG12 is a timing diagram of data discarding provided in an embodiment of the present application.

[0301] 11 and 12 , assuming that uplink data information of the three logical channel groups LCG1, LCG2, and LCG3, ie, the buffered data volume and / or the remaining delay information, is reported at time t1, and assuming that the uplink data volume at time t1 is 10MB.

[0302] Then, at time t2, PDU sets are discarded in LCH1 and LCH2 in LCG1, and PDU sets are discarded in LCH4 and LCH6 in LCG2. Assume that the amount of uplink data remaining after the discard is 7 MB.

[0303] Based on the above, if uplink data is discarded, a third report may be triggered. The third report may include the amount of uplink data remaining after the discard, i.e., 7 MB. The third report may also include cause indication information, where the cause indication information may indicate that the third report was triggered due to uplink data discard. The cause indication information may further indicate that the first channel where data discard occurred is LCG1 or LCG2.

[0304] In summary, in this embodiment, a third report can be triggered after uplink data is discarded. The third report can include the data volume and / or remaining delay of the remaining uplink data after the discard, so that the network device can update the previously received uplink data information based on the relevant information of the uplink data remaining after the discard, thereby allocating the correct amount of uplink resources to avoid waste of resources.

[0305] In another possible implementation, the third report may also be a separate report. The implementation in which the third report is a separate report is described below. The third report in this embodiment is a separate report for indicating the amount of discarded uplink data and / or the remaining delay.

[0306] The format of the third report when it is a separate report can be understood in conjunction with Figures 13 and 14. Figure 13 is a second schematic diagram of the format of the third report provided in an embodiment of the present application, and Figure 14 is a third schematic diagram of the format of the third report provided in an embodiment of the present application.

[0307] 13 , the third report may include information on the amount of discarded uplink data and / or delay of the discarded uplink data.

[0308] For example, initially, there is 10MB of uplink data, and the data volume and / or remaining latency of the uplink data have been reported to the network device. Assuming that 3MB of uplink data is discarded, the third report may include the uplink data volume and / or the remaining latency of the discarded 3MB of uplink data.

[0309] Afterwards, the network device may calculate the remaining uplink data volume and / or the remaining delay of the uplink data after discarding based on the discarded uplink data volume and / or the delay information of the discarded uplink data in the third report.

[0310] Further, referring to FIG14 , the third report may also include the first channel (LCG illustrated in FIG14 ) corresponding to the discarded uplink data, so that the network device can determine which first channel specifically has discarded the uplink data.

[0311] In summary, in this embodiment, a third report can be triggered after uplink data is discarded. The third report can include the amount of discarded uplink data and / or the remaining delay, so that the network device updates the uplink data information previously received, thereby allocating the correct amount of uplink resources to avoid waste of resources.

[0312] The above embodiments introduce relevant implementations on the terminal device side. On the network device side, configuration information can be sent to the terminal device to instruct the terminal device to execute the contents introduced in the above embodiments. The relevant implementations on the network device side are described below.

[0313] In this embodiment, the network device may send configuration information to the terminal device, where the configuration information is used to indicate at least one of the following information:

[0314] Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data;

[0315] Determining a first moment of a latest first uplink data amount or a latest first residual delay: determining a moment of a first resource for sending the first uplink data amount and / or the first residual delay; a moment when the first resource arrives; and obtaining at least one of moment of update indication information, the update indication information being used to indicate discarding of the uplink data, or the update indication information being used to indicate a remaining uplink data amount after discarding and / or a remaining delay of the uplink data remaining after discarding;

[0316] Whether the terminal device cancels the triggered second report when uplink data is discarded;

[0317] First channel information, where the first channel information is used to determine whether to cancel the triggered second report;

[0318] Whether the terminal device re-evaluates the triggering conditions of the second report when uplink data is discarded.

[0319] Whether the terminal device triggers a third report when uplink data is discarded, and the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

[0320] The following describes each of the above information in turn:

[0321] Information 1: Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0322] The configuration information specifies information 1 in the following three ways:

[0323] Case 1: The configuration information indicates whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0324] In this case, the configuration information may include two configurable options regarding whether the terminal device reports the latest data. For example, the configuration information may include a corresponding indicator bit to indicate that the terminal device reports the latest first uplink data volume and / or the latest first remaining delay of the uplink data. Alternatively, the indicator bit may be 1 or 0 to indicate that the terminal device does not report the latest first uplink data volume and / or the latest first remaining delay of the uplink data.

[0325] Case 2: The configuration information instructs the terminal device to report the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0326] In this case, the configuration information only indicates a positive situation, that is, the configuration information directly indicates that the terminal device is to report the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0327] Case three: The configuration information instructs the terminal device not to report the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0328] In this case, the configuration information only indicates a negative situation, that is, the configuration information directly indicates that the terminal device does not report the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0329] The terminal device can determine whether to include the latest first uplink data volume and / or the latest first residual delay of the uplink data in the first report based on the indication of the currently introduced information 1 in the configuration information.

[0330] Information 2: Determine the first moment of the latest first uplink data volume or the latest first residual delay: determine at least one of the moment of the first resource used to send the first uplink data volume and / or the first residual delay; the moment when the first resource arrives; and the moment when the update indication information is obtained.

[0331] The configuration information may also indicate the specific implementation of the first moment, where the first moment may include at least one of the following: the moment of determining the first resource for sending the first uplink data volume and / or the first residual delay; the moment when the first resource arrives; the moment when the update indication information is obtained.

[0332] Information 3: Whether the terminal device cancels the triggered second report when uplink data is discarded.

[0333] The specific indication of information 3 by the configuration information has the following three situations:

[0334] Case 1: The configuration information indicates whether the terminal device cancels the triggered second report when uplink data is discarded.

[0335] In this case, the configuration information provides two configurable options for whether the terminal device should cancel the triggered second report when uplink data is discarded. For example, the configuration information may include a corresponding indication bit to indicate to the terminal device that the triggered second report should be canceled. Alternatively, the indication bit may be 1 or 0 to indicate to the terminal device that the triggered second report should not be canceled.

[0336] Case 2: The configuration information instructs the terminal device to cancel the triggered second report when uplink data is discarded.

[0337] In this case, the configuration information only indicates a positive situation, that is, the configuration information directly instructs the terminal to cancel the triggered second report when uplink data is discarded.

[0338] Case 3: The configuration information instructs the terminal device not to cancel the triggered second report when uplink data is discarded.

[0339] In this case, the configuration information only indicates a negative situation, that is, the configuration information directly indicates that the terminal device does not cancel the triggered second report when uplink data is discarded.

[0340] The configuration information, through indication information 3, allows the terminal device to determine whether it is necessary to cancel the triggered second report when uplink data is discarded.

[0341] Information 4: first channel information, the first channel information is used to determine whether to cancel the triggered second report.

[0342] The specific instructions of the configuration information for information 4 are as follows:

[0343] Case 1: The configuration information indicates that the first channel information is used to determine whether to cancel the triggered second report.

[0344] In this case, the configuration information has two configurable options for using the first channel information to determine whether to cancel the triggered second report. For example, the configuration information may include a corresponding indication bit to indicate that the first channel information is used to determine whether to cancel the triggered second report. Alternatively, the indication bit may be 1 or 0 to indicate that the first channel information is used to determine whether to cancel the triggered second report.

[0345] Case 2: The configuration information indicates that the first channel information is used to determine the second report to cancel the trigger.

[0346] In this case, the configuration information only indicates a positive situation, that is, the configuration information directly indicates that the first channel information is used to determine the cancellation of the triggered second report.

[0347] Case 3: The configuration information indicates that the first channel information is used to determine whether to cancel the triggered second report.

[0348] In this case, the configuration information only indicates a negative situation, that is, the configuration information directly indicates that the first channel information is used to determine whether to cancel the triggered second report.

[0349] The above describes three different ways in which configuration information indicates the first channel information. It can be understood that these describe the configuration method of the network device, rather than the execution method of the terminal device. The following further describes the specific content and various situations indicated by the first channel information in information 4.

[0350] Based on the above description, it can be determined that when uplink data is discarded, the terminal device can directly cancel the triggered second report, or further determine whether there is uplink data in the first channel to determine whether to cancel the triggered second report.

[0351] The first channel information here can indicate whether the terminal device should perform "determining whether uplink data exists in the first channel." Specifically, the first channel information can indicate at least one specific first channel, or it can indicate no specific first channel. These two situations are described below.

[0352] In one implementation, the first channel information indicates at least one specific first channel, and the terminal device can determine whether uplink data exists in the specific first channel based on the configuration information, thereby determining whether to cancel the triggered second report. Alternatively, the terminal device can determine whether uplink data exists in the first channel that triggered the second report in the specific first channel, thereby determining whether to cancel the triggered second report.

[0353] For example, assuming that LCG1 to LCG8 exist and LCG1, LCG2, and LCG3 are indicated in the first channel information, the terminal device can determine whether uplink data exists in LCG1, LCG2, and LCG3 when uplink data is discarded, thereby determining whether to cancel the triggered second report. Furthermore, the terminal device can also determine whether uplink data exists in the LCG that triggered the second report among LCG1, LCG2, and LCG3, thereby determining whether to cancel the triggered second report.

[0354] In another implementation, the first channel information does not indicate a specific first channel. In this case, the terminal device may determine whether uplink data exists in any first channel based on the configuration information, thereby determining whether to cancel the triggered second report. Alternatively, the terminal device may determine whether uplink data exists in any first channel that has triggered the second report, thereby determining whether to cancel the triggered second report.

[0355] Information 5: Whether the terminal device re-evaluates the triggering conditions of the second report when uplink data is discarded.

[0356] The specific instructions of the configuration information for information 5 are as follows:

[0357] Case 1: The configuration information indicates whether the terminal device should re-evaluate the triggering condition of the second report when uplink data is discarded.

[0358] In this case, the configuration information provides two configurable options for whether the terminal device should re-evaluate the triggering condition for the second report when uplink data is discarded. For example, the configuration information may include a corresponding indicator bit to indicate that the terminal device should re-evaluate the triggering condition for the second report. Alternatively, the indicator bit may be 1 or 0 to indicate that the terminal device should not re-evaluate the triggering condition for the second report.

[0359] Case 2: The configuration information instructs the terminal device to re-evaluate the triggering condition of the second report when uplink data is discarded.

[0360] In this case, the configuration information only indicates a positive situation, that is, the configuration information directly instructs the terminal to re-evaluate the triggering condition of the second report when uplink data is discarded.

[0361] Case 3: The configuration information instructs the terminal device not to re-evaluate the triggering condition of the second report when uplink data is discarded.

[0362] In this case, the configuration information only indicates a negative situation, that is, the configuration information directly indicates that the terminal device does not re-evaluate the triggering condition of the second report when uplink data is discarded.

[0363] The configuration information, through indication information 5, allows the terminal device to determine whether it is necessary to re-evaluate the triggering conditions of the second report when uplink data is discarded. If re-evaluation is required, the terminal device will re-trigger the second report when the triggering conditions of the second report are met.

[0364] Information 6: Whether the terminal device triggers a third report when uplink data is discarded. The third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

[0365] The specific instructions of the configuration information for information 5 are as follows:

[0366] Case 1: The configuration information indicates whether the terminal device triggers the third report when uplink data is discarded.

[0367] In this case, the configuration information provides two configurable options for whether the terminal device should trigger a third report when uplink data is discarded. For example, the configuration information may include a corresponding indication bit to indicate to the terminal device whether to trigger the third report. Alternatively, the indication bit may be 1 or 0 to indicate to the terminal device not to trigger the third report.

[0368] Case 2: The configuration information instructs the terminal device to trigger the third report when uplink data is discarded.

[0369] In this case, the configuration information only indicates a positive situation, that is, the configuration information directly instructs the terminal to trigger the third report when uplink data is discarded.

[0370] Case 3: The configuration information instructs the terminal device not to trigger the third report when uplink data is discarded.

[0371] In this case, the configuration information only indicates a negative situation, that is, the configuration information directly indicates that the terminal device does not trigger the third report when uplink data is discarded.

[0372] The configuration information, through indication information 6, allows the terminal device to determine whether a third report needs to be triggered when uplink data is discarded. The detailed content of the third report can be referred to the introduction of the above embodiment and will not be repeated here.

[0373] On the network device side, configuration information can be sent to the terminal device to instruct the terminal device to report corresponding information or perform corresponding actions according to the instructions of the configuration information, thereby implementing the content introduced in the above embodiment and effectively reducing resource waste.

[0374] FIG15 is a structural diagram of an information processing device according to an embodiment of the present application. As shown in FIG15 , the device 150 includes: a processing module 1501;

[0375] The processing module 1501 is configured to generate a first report, wherein the first report includes the latest first uplink data volume and / or the latest first residual delay of the uplink data;

[0376] The sending module 1502 is configured to transmit the first report.

[0377] In one possible design, the latest first uplink data amount and / or the latest first residual delay are determined at a first moment;

[0378] The first moment is at least one of the following: the moment of determining the first resource for sending the first report; the moment when the first resource arrives; the moment when the update indication information is obtained, the update indication information is used to indicate the discarding of uplink data, or the update indication information is used to indicate the remaining uplink data amount after discarding and / or the remaining delay of the uplink data remaining after discarding.

[0379] In one possible design, the processing module 1501 is further configured to:

[0380] If the uplink data is discarded, the triggered second report is canceled.

[0381] In one possible design, the second report is the first report; or, the second report includes a second uplink data volume and / or a second residual delay.

[0382] In one possible design, the processing module 1501 is specifically configured to:

[0383] If the uplink data is discarded and there is no uplink data in the first channel, the triggered second report is canceled, and the first channel includes at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

[0384] In one possible design, the logical channel is the logical channel that triggers the second report, the logical channel group is the logical channel group that triggers the second report, the PDU set is the PDU set that triggers the second report, or the data burst information is the data burst information that triggers the second report.

[0385] In one possible design, the processing module 1501 is further configured to:

[0386] If the uplink data is discarded, re-evaluating the triggering condition of the second report;

[0387] When the trigger condition is met, the second report is re-triggered.

[0388] In one possible design, the processing module 1501 is further configured to:

[0389] If uplink data is discarded, a third report is triggered, and the third report is used to update the uplink data amount and / or the remaining delay of the uplink data.

[0390] In one possible design, the third report is the first report or the second report.

[0391] In one possible design, the terminal device includes a media access control (MAC) layer, and the processing module 1501 is specifically configured to:

[0392] The MAC layer receives high-layer indication information, where the high-layer indication information is used to indicate that the uplink data is discarded;

[0393] The MAC layer triggers the third report according to the higher layer indication information.

[0394] In one possible design, the high-layer indication information is used to indicate a first channel to which the discarded uplink data belongs;

[0395] The processing module 1501 is specifically configured to:

[0396] The MAC layer determines, according to the high-layer indication information, whether the first channel to which the discarded uplink data belongs has triggered the third report;

[0397] If so, the third report is triggered.

[0398] In one possible design, the third report includes cause indication information, and the cause indication information is used to indicate that the third report is triggered due to the discarding of uplink data, or to indicate that the amount of uplink data and / or the remaining delay included in the third report is obtained after the uplink data is discarded.

[0399] In one possible design, the third report includes the amount of discarded uplink data and / or delay information of the discarded uplink data.

[0400] In one possible design, the third report also includes the first channel corresponding to the discarded uplink data.

[0401] In one possible design, the discarded uplink data includes at least one protocol data unit (PDU) set.

[0402] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail in this embodiment.

[0403] Figure 16 is a second structural diagram of an information processing device provided in an embodiment of the present application. As shown in Figure 16, the device 160 includes: a sending module 1601;

[0404] The sending module 1601 is configured to send configuration information, where the configuration information indicates at least one of the following:

[0405] Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data;

[0406] Determining a first moment of the latest first uplink data amount or the latest first residual delay: determining a moment of a first resource for sending the first uplink data amount and / or the first residual delay; a moment when the first resource arrives; and obtaining at least one of the moments of update indication information, the update indication information being used to indicate discarding of uplink data, or the update indication information being used to indicate a remaining uplink data amount and / or a remaining delay of the uplink data remaining after discarding;

[0407] Whether the terminal device cancels the triggered second report when uplink data is discarded;

[0408] first channel information, where the first channel information is used to determine whether to cancel the triggered second report;

[0409] Whether the terminal device re-evaluates the triggering condition of the second report when uplink data is discarded.

[0410] Whether the terminal device triggers a third report when uplink data is discarded, and the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

[0411] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail in this embodiment.

[0412] The information processing method provided in the embodiment of the present application can be applied to electronic devices with communication functions. The electronic devices include terminal devices. The specific device form of the terminal device can refer to the above related descriptions and will not be repeated here.

[0413] An embodiment of the present application provides a terminal device, which includes: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the terminal device executes the above method.

[0414] The present embodiment provides a chip. The chip includes a processor configured to invoke a computer program stored in a memory to execute the technical solution of the above embodiment. The implementation principles and technical effects are similar to those of the above-mentioned related embodiments and will not be further described here.

[0415] The embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the above-mentioned method is implemented. The methods described in the above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions can be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium. Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium that can be accessed by a computer.

[0416] In one possible implementation, computer-readable media may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium designed to carry or store the desired program code in the form of instructions or data structures and accessible by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave are used to transmit software from a website, server or other remote source, the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and optical disk as used herein include optical disk, laser disk, optical disk, digital versatile disk (DVD), floppy disk and Blu-ray disk, where disks generally reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0417] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed, the computer executes the above method.

[0418] The present application embodiment is described with reference to the flow chart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present application.It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processing unit of general-purpose computer, special-purpose computer, embedded processing machine or other programmable device to produce a machine, so that the instruction executed by the processing unit of computer or other programmable data processing device produces the device for realizing the function specified in one flow chart flow or multiple flows and / or one block or multiple blocks of block diagram.

[0419] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present invention should be included in the scope of protection of the present invention.

Claims

1. An information processing method, characterized in that: Applied to a terminal device, the method comprises: Generate or transmit a first report, wherein the first report includes the latest first uplink data amount and / or includes the latest first residual delay of the uplink data.

2. The method according to claim 1, characterized in that The latest first uplink data amount and / or the latest first residual delay are determined at a first moment; The first moment is at least one of the following: the moment of determining the first resource for sending the first report; the moment when the first resource arrives; the moment when update indication information is obtained, and the update indication information is used to indicate the discarding of uplink data, or the update indication information is used to indicate the remaining uplink data amount after discarding and / or the remaining delay of the uplink data remaining after discarding.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: If the uplink data is discarded, the triggered second report is cancelled.

4. The method according to claim 3, characterized in that The second report is the first report; or the second report includes a second uplink data volume and / or a second residual delay.

5. The method according to claim 3 or 4, characterized in that: If data discard occurs in the uplink data, canceling the triggered second report includes: If the uplink data is discarded and there is no uplink data in the first channel, the triggered second report is canceled, and the first channel includes at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

6. The method according to claim 5, characterized in that The logical channel is a logical channel that triggers the second report, the logical channel group is a logical channel group that triggers the second report, the PDU set is a PDU set that triggers the second report, or the data burst information is data burst information that triggers the second report.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: If the uplink data is discarded, re-evaluating the triggering condition of the second report; When the trigger condition is met, the second report is re-triggered.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: If the uplink data is discarded, a third report is triggered, and the third report is used to update the uplink data amount and / or the remaining delay of the uplink data.

9. The method according to claim 8, characterized in that The third report is the first report or the second report.

10. The method according to claim 9, characterized in that The terminal device includes a media access control MAC layer, and the triggering of the third report includes: The MAC layer receives high-layer indication information, where the high-layer indication information is used to indicate that the uplink data is discarded; The MAC layer triggers the third report according to the higher-layer indication information.

11. The method according to claim 10, characterized in that The high-layer indication information is used to indicate the first channel to which the discarded uplink data belongs; The MAC layer triggers the third report according to the high-layer indication information, including: The MAC layer determines, according to the high-level indication information, whether the first channel to which the discarded uplink data belongs has triggered the third report; If so, the third report is triggered.

12. The method according to any one of claims 9 to 11, characterized in that: The third report includes cause indication information, where the cause indication information is used to indicate that the third report is triggered due to the discarding of uplink data, or to indicate that the uplink data amount and / or remaining delay included in the third report is obtained after the uplink data is discarded.

13. The method according to claim 8, characterized in that The third report includes the amount of discarded uplink data and / or delay information of the discarded uplink data.

14. The method according to claim 13, characterized in that The third report also includes the first channel corresponding to the discarded uplink data.

15. The method according to any one of claims 1 to 14, characterized in that: The discarded uplink data includes at least one protocol data unit PDU set.

16. An information processing method, characterized in that: Applied to a terminal device, the method comprises: If the uplink data is discarded, the triggered second report is cancelled.

17. An information processing method, characterized in that: Applied to a terminal device, the method comprises: If the uplink data is discarded, re-evaluate the triggering condition of the second report; When the trigger condition is met, the second report is re-triggered.

18. An information processing method, characterized in that: Applied to a terminal device, the method comprises: If the uplink data is discarded, a third report is triggered, and the third report is used to update the uplink data amount and / or the remaining delay of the uplink data.

19. An information processing method, characterized in that: Applied to a network device, the method comprises: Send configuration information, where the configuration information is used to indicate at least one of the following information: Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data; Determine the first moment of the latest first uplink data amount or the latest first residual delay: determine the moment of the first resource used to send the first uplink data amount and / or the first residual delay; the moment when the first resource arrives; at least one of the moments of acquiring update indication information, the update indication information is used to indicate the discarding of uplink data, or the update indication information is used to indicate the remaining uplink data amount after the discarding and / or the remaining delay of the uplink data after the discarding; Whether the terminal device cancels the triggered second report when uplink data is discarded; first channel information, where the first channel information is used to determine whether to cancel the triggered second report; Whether the terminal device re-evaluates the triggering condition of the second report when uplink data is discarded; When uplink data is discarded, the terminal device triggers a third report, where the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

20. An information processing device, characterized in that: include: A processing module, configured to generate a first report, wherein the first report includes the latest first uplink data volume and / or includes the latest first residual delay of the uplink data; A sending module is used to transmit the first report.

21. An information processing device, characterized in that: include: The sending module is used to send configuration information, where the configuration information is used to indicate at least one of the following information: Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data; Determine the first moment of the latest first uplink data amount or the latest first residual delay: determine the moment of the first resource used to send the first uplink data amount and / or the first residual delay; the moment when the first resource arrives; at least one of the moments of acquiring update indication information, the update indication information is used to indicate the discarding of uplink data, or the update indication information is used to indicate the remaining uplink data amount after the discarding and / or the remaining delay of the uplink data after the discarding; Whether the terminal device cancels the triggered second report when uplink data is discarded; first channel information, where the first channel information is used to determine whether to cancel the triggered second report; Whether the terminal device re-evaluates the triggering condition of the second report when uplink data is discarded; When uplink data is discarded, the terminal device triggers a third report, where the third report is used to update the uplink data volume and / or the remaining delay of the uplink data.

22. A terminal device, characterized in that: include: Processor and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the terminal device performs the method according to any one of claims 1 to 18.

23. A network device, characterized in that: include: Processor and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the network device performs the method according to claim 19.

24. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 19 is implemented.

Images