Information processing method and apparatus

Abstract

Embodiments of this application provide information processing methods and apparatus. The method includes the step of generating or transmitting a first report, the first report including the most recent first uplink data amount and / or the most recent first residual delay of the uplink data. In this application, the first report is configured to include the most recent first uplink data amount and / or the first residual delay of the uplink data, and as a result, even if the uplink data is discarded, the first report may also include relevant information about the discarded uplink data in order to avoid wasting resources due to redundant buffered data or residual delays included in the first report as a result of the discarding of the uplink data.

Description

Technical Field

[0001] This application claims the priority of Chinese Patent Application No. 202310365217.1, titled "Information Processing Method and Apparatus", filed with the State Intellectual Property Office of China on March 31, 2023, the entire content of which is incorporated herein by reference.

[0002] This application relates to the field of communication technologies, and in particular, to information processing methods and apparatuses.

Background Art

[0003] When a terminal device applies for uplink resources from a network device, it is necessary to report a buffer status report (BSR) to the network device. As a result, the network device schedules appropriate uplink resources for the terminal device.

[0004] Before the terminal device transmits uplink data, the uplink data may be discarded. When the uplink data is discarded, the amount of uplink data buffered in the terminal device may change significantly. If the buffer status report is reported to the network device before the uplink data is discarded, the terminal device may report a redundant buffer amount, and then the network device may allocate redundant uplink resources, resulting in waste of resources.

Summary of the Invention

Means for Solving the Problems

[0005] Embodiments of this application provide an information processing method and apparatus applicable to the field of terminal technologies.

[0006] According to a first aspect, an embodiment of this application provides an information processing method applicable to a terminal device. The method includes A step of generating or transmitting a first report, the first report including the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0007] In a possible design, the latest first uplink data volume and / or the latest first residual delay are determined at the first time point. The first point in time is at least one of the following: the time for determining the first resource to send the first report; the time when the first resource arrives; and the time when update instruction information is obtained, the update instruction information being used to indicate the discard of uplink data, or the update instruction information being used to indicate the amount of residual uplink data after the discard and / or the residual delay of the residual uplink data after the discard.

[0008] In a possible design, the method is The further step includes canceling the triggered second report if the uplink data is discarded.

[0009] In a 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.

[0010] In a possible design, if uplink data is discarded, the step to cancel the triggered second report is: If uplink data is discarded and no uplink data exists on the first channel, the step of canceling the triggered second report includes the step that the first channel includes at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

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

[0012] In a possible design, the method is If uplink data is discarded, the trigger conditions for the second report are re-evaluated. The further step includes re-triggering a second report when the trigger condition is met.

[0013] In a possible design, the method is A step of triggering a third report when uplink data is discarded, the third report being used to update the amount of uplink data and / or residual delay of the uplink data.

[0014] In possible designs, the third report is either the first or second report.

[0015] In a possible design, the terminal device includes a media access control MAC layer, and the step of triggering a third report is: The MAC layer receives upper-layer instruction information, which is used to indicate that uplink data is to be discarded. The MAC layer includes the step of triggering a third report based on upper-layer directive information.

[0016] In a possible design, higher-layer indicator information is used to indicate the first channel group to which the discarded uplink data belongs. The MAC layer triggers a third report based on upper-layer directive information. The MAC layer determines, based on upper-layer directives, whether the first channel to which the discarded uplink data belonged triggered a third report. triggering a third report when the trigger occurs;

[0017] In a 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 discarding uplink data, or the amount of uplink data and / or residual delay included in the third report is obtained after the uplink data is discarded.

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

[0019] In a possible design, the third report further includes a first channel corresponding to the discarded uplink data.

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

[0021] According to a second aspect, an embodiment of the present application provides an information processing method applied to a terminal device. The method further includes canceling the triggered second report when the uplink data is discarded.

[0022] According to a third aspect, an embodiment of the present application provides an information processing method applied to a terminal device. The method includes re-evaluating the trigger condition of the second report when the uplink data is discarded; re-triggering the second report when the trigger condition is met.

[0023] According to a fourth aspect, an embodiment of the present application provides an information processing method applied to a terminal device. The method includes A step of triggering a third report when uplink data is discarded, the third report being used to update the uplink data volume and / or the residual delay of the uplink data, further including the step.

[0024] According to a fifth aspect, an embodiment of the present application provides an information processing method applied to a network device. The method includes: A step of transmitting configuration information, the configuration information being the following information, namely: Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data, At least one of the first time point for determining the latest first uplink data volume or the latest first residual delay, the time point for determining the first resource for transmitting the first uplink data volume and / or the first residual delay, the time point when the first resource arrives, and the time point when the update instruction information is acquired, the update instruction information being used to indicate the discard of the uplink data, or the update instruction information being used to indicate the residual uplink data volume after the discard and / or the residual delay of the residual uplink data after the discard, said at least one, Whether the terminal device cancels the triggered second report when the uplink data is discarded, The first channel information, the first channel information being used to determine whether to cancel the triggered second report, Whether the terminal device re-evaluates the trigger condition of the second report when the uplink data is discarded, and Whether the terminal device triggers a third report when the uplink data is discarded, the third report being used to update the uplink data volume and / or the residual delay of the uplink data, said whether to trigger including the step of being used to indicate at least one of them.

[0025] According to a sixth aspect, one embodiment of the present application provides an information processing method applicable to a network device. The method is: The step of receiving a first report, the first report including the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0026] In a possible design, the latest first uplink data volume and / or the latest first residual delay are determined at the first time point. The first point in time is at least one of the following: the time for determining the first resource to send the first report; the time when the first resource arrives; and the time when the update instruction information is received, the update instruction information being used to indicate the amount of data and / or residual delay of the discarded uplink data.

[0027] In a possible design, if uplink data is discarded, the trigger for the second report is canceled.

[0028] In a 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.

[0029] In a possible design, if uplink data is discarded and no uplink data exists on the first channel, the step that triggers the 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.

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

[0031] In a possible design, the method is A step of receiving a second report, the second report being triggered when it is determined through re-evaluation that the trigger conditions for the second report have been met after the uplink data has been discarded.

[0032] In a possible design, the method is The step of receiving a third report, which is triggered when uplink data is discarded, and which is used to update the amount of uplink data and / or residual delay of the uplink data.

[0033] In possible designs, the third report is either the first or second report.

[0034] In a possible design, the third report would include cause-indicating information, which would be used to indicate that the third report was transmitted due to the discarding of uplink data, or that the amount of uplink data and / or residual delay included in the third report was obtained after the uplink data had been discarded.

[0035] In a possible design, the third report would include the amount of discarded uplink data and / or delay information for the discarded uplink data.

[0036] In a possible design, the third report would further include the first channel corresponding to the discarded uplink data.

[0037] In a possible design, discarded uplink data would include at least one set of PDUs.

[0038] According to a seventh aspect, one embodiment of the present application provides an information processing device, which is 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, Includes a transmission module configured to transmit a first report.

[0039] According to the eighth aspect, one embodiment of the present application provides an information processing device, which is A transmission module configured to transmit configuration information, wherein the configuration information is the following information: Whether the terminal device reports the most recent first uplink data volume and / or the most recent first residual delay of the uplink data, At least one of the following: a first time for determining the latest first uplink data volume or the latest first residual delay; a first time for determining a first resource for transmitting the first uplink data volume and / or the first residual delay; a time when the first resource arrives; and a time when update instruction information is acquired, wherein the update instruction information is used to indicate the discarding of uplink data, or the update instruction information is used to indicate the residual uplink data volume and / or the residual delay of the residual uplink data after the discarding. Whether the terminal device cancels the triggered second report when uplink data is discarded. First channel information, which is used to determine whether to cancel the triggered second report, Whether the terminal device re-evaluates the trigger conditions for the second report when uplink data is discarded, and Whether the terminal device triggers a third report when uplink data is discarded, the third report being used to update the amount of uplink data and / or residual delay of the uplink data, and whether the trigger is said to occur. It includes a transmitting module used to indicate at least one of the following.

[0040] According to the ninth aspect, one embodiment of the present application provides an information processing device, which is The receiving module includes a receiving module configured to receive a first report, the first report including the latest first uplink data amount and / or the latest first residual delay of the uplink data.

[0041] According to a tenth aspect, one embodiment of the present application provides an information processing device, which is Includes a processing module configured to cancel a triggered second report if the uplink data is discarded.

[0042] According to the eleventh aspect, one embodiment of the present application provides an information processing device, which is If uplink data is discarded, the processing module includes a processing module configured to re-evaluate the trigger conditions for a second report. The processing module is further configured to re-trigger a second report when the trigger condition is met.

[0043] According to the twelfth aspect, one embodiment of the present application provides an information processing device, which is The processing module includes a processing module configured to trigger a third report when uplink data is discarded, the third report being used to update the amount of uplink data and / or the residual delay of the uplink data.

[0044] According to the 13th aspect, one embodiment of the present application provides a terminal device. A terminal device may also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. A terminal device may be a mobile phone, smart TV, wearable device, tablet computer (Pad), computer with wireless transceiver functionality, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal for industrial control, wireless terminal for self-driving, wireless terminal for remote medical surgery, wireless terminal for smart grid, wireless terminal for transportation safety, wireless terminal for smart city, wireless terminal for smart home, etc.

[0045] A terminal device includes a processor and memory. The memory stores computer executable instructions. The processor is configured to execute computer executable instructions stored in memory so that the terminal device performs the method according to the first embodiment.

[0046] According to the fourteenth aspect, one embodiment of the present application provides a computer-readable storage medium in which a computer program is stored. When the computer program is executed by a processor, it performs the methods according to the first to sixth aspects.

[0047] According to the fifteenth aspect, one embodiment of the present application provides a computer program product. The computer program product includes a computer program. When executed, the computer program causes a computer to perform the methods according to the first to sixth aspects.

[0048] According to the sixteenth aspect, one embodiment of the present application provides a chip, the chip including a processor, the processor being configured to invoke a computer program in memory to perform the methods according to the first to sixth aspects.

[0049] This application provides an information processing method and apparatus for preventing terminal devices from reporting redundant amounts of buffered data and / or redundant residual delays, thereby reducing resource waste. [Brief explanation of the drawing]

[0050] [Figure 1] This is a schematic diagram of a communication scenario according to one embodiment of the present application. [Figure 2] This is a flowchart of an information processing method according to one embodiment of this application. [Figure 3] This is flowchart II of an information processing method according to one embodiment of this application. [Figure 4] This is a schematic diagram I of an implementation that cancels the reporting trigger according to one embodiment of this application. [Figure 5] This is a schematic diagram II of an implementation that cancels the reporting trigger according to one embodiment of this application. [Figure 6] This is flowchart III of an information processing method according to one embodiment of this application. [Figure 7] This is a schematic diagram I of an implementation for re-evaluating trigger conditions according to one embodiment of this application. [Figure 8] This is schematic diagram II of an implementation configuration for re-evaluating trigger conditions according to one embodiment of this application. [Figure 9] This is flowchart IV of an information processing method according to one embodiment of this application. [Figure 10] This is a schematic diagram I of the format of a third report according to one embodiment of this application. [Figure 11] This is a schematic diagram of the discarding of uplink data according to one embodiment of this application. [Figure 12]This is a schematic timing diagram of data discarding according to one embodiment of this application. [Figure 13] This is schematic diagram II of the format of a third report according to one embodiment of this application. [Figure 14] This is schematic diagram III of the format for a third report according to one embodiment of this application. [Figure 15] This is a schematic diagram I of an information processing device according to one embodiment of this application. [Figure 16] This is schematic diagram II of an information processing device according to one embodiment of the present application. [Modes for carrying out the invention]

[0051] To better understand the technical solutions of this application, the relevant concepts and technologies involved in this application are described below.

[0052] Terminal device: A terminal device may include wireless transmission and reception capabilities and may be a device that can work with network devices to provide communication services to a user. Specifically, a terminal device may be a user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile console, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. For example, a terminal device may be a mobile phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, onboard device, wearable device, or a terminal device in a future 5G network or a network beyond 5G.

[0053] Network devices: Network devices may be devices configured to communicate with terminal devices, for example, base transceiver stations (BTS) of a Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) communication system, or base stations (NodeB, NB) of a Wideband Code Division Multiple Access (WCDMA®) system, or even evolved Node B (eNB or eNodeB) of an LTE system, or network devices may be relay stations, access points, onboard devices, wearable devices, network-side devices of future 5G networks or networks beyond 5G, or network devices of future evolved Public Land Mobile Network (PLMN) networks.

[0054] Network devices involved in the embodiments of this application may be called Radio Access Network (RAN) devices. RAN devices are connected to terminal devices and configured to receive data from terminal devices and transmit data to core network devices. RAN devices correspond to different devices in different communication systems, for example, to base stations and base station controllers in 2G systems, to base stations and radio network controllers (RNCs) in 3G systems, to evolutionary node B (eNBs) in 4G systems, and to access network devices (e.g., gNBs, centralized units (CUs), and distributed units (DUs)) in 5G systems, such as New Radio (NR) systems.

[0055] Scenarios to which the resource processing method described in this application can be applied are described below with reference to Figure 1.

[0056] Figure 1 is a schematic diagram of a communication scenario according to one embodiment of the present application. Referring to Figure 1, a network device 101 and a terminal device 102 are included. The network device 101 and the terminal device 102 may perform wireless communication. The terminal device 102 may communicate with at least one core network via a Radio Access Network (RAN).

[0057] The communication system may be a Global System of Mobile Communication (GSM), a Code Division Multiple Access (CDMA), a Wideband Code Division Multiple Access (WCDMA®), a Long Term Evolution (LTE), or a 5th Generation (5G) system.

[0058] Accordingly, the network device may be a base station (BTS) of a GSM or CDMA system, or a base station (NB) of a WCDMA® system, or an evolved base station (eNB), an access point (AP), or a relay station of an LTE system, or a base station of a 5G system, etc. This is not limited to the above.

[0059] The 5G mobile communication systems of this application include non-standalone (NSA) 5G mobile communication systems and / or standalone (SA) 5G mobile communication systems. The technical solutions provided in this application may be further applied to future communication systems, for example, sixth-generation mobile communication systems. The communication systems may further be PLMN networks, device-to-device (D2D) networks, machine-to-machine (M2M) networks, IoT networks, or other networks.

[0060] If the technical solutions in the embodiments of this application are applied to a different wireless communication network, it will be understood that the corresponding names may be replaced with the names of the corresponding functions within that different wireless communication network.

[0061] The network architectures and service scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions in the embodiments of this application and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As network architectures evolve and new service scenarios emerge, those skilled in the art will know that the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0062] Based on the above, PDUs (Protocol Data Units) and PDU sets are briefly explained below.

[0063] A PDU is a data unit for performing data transfer between peer layers. PDUs may be established at any layer; RLC PDUs may be established at the Radio Link Control (RLC) layer, PDCP PDUs may be established at the Packet Data Convergence Protocol (PDCP) layer, and MAC PDUs may be established at the Media Access Control (MAC) layer.

[0064] Currently, the concept of PDU sets is being introduced into related technologies. For example, multiple PDUs may form a single PDU set. Generally, the data size of a single PDU set ranges from a few megabits to several hundred megabits.

[0065] In an NR system, terminal devices buffer data at the RLC and PDCP layers. If a PDU set is discarded, the amount of buffered data on the terminal device can change significantly.

[0066] The BSR and residual delay reports are briefly explained again below.

[0067] In an NR system, a terminal device may store uplink data in a buffer and then request uplink resources from a network device via a BSR. The BSR is used to provide the network device with information about the amount of uplink data and may transfer information about the amount of uplink data that needs to be transmitted within the terminal device's buffer.

[0068] Furthermore, uplink data may have residual delay. In possible implementations, residual delay information may be stored in the BSR to notify network devices of the residual delay of uplink data via the BSR. In other words, the BSR in this application may be understood as a common report of buffer status and residual delay. Alternatively, the BSR and residual delay report are two separate reports. The BSR is used to provide information about the amount of uplink data, and the residual delay report is used to provide residual delay information for the uplink data. In actual implementation processes, whether the BSR and residual delay report are an integrated report or two separate reports may be chosen based on actual requirements.

[0069] Therefore, based on the above description, it may be determined that the terminal device can send a BSR and / or residual delay report to the network device in order to provide the network device with data volume information and residual delay information for the uplink data.

[0070] However, since PDU sets can be discarded, this means that uplink data will also be discarded. If a terminal device reports an uplink data volume or residual delay of uplink data before the PDU set is discarded and is waiting for a network device to allocate it, the terminal device may report a redundant uplink data volume, and the network device may allocate redundant uplink resources, resulting in resource waste. This places a heavy burden on the network and is very likely to degrade the overall condition of the link.

[0071] Due to the technical issues described above, it is urgent to provide a way to promptly update the changing conditions of uplink data caused by the PDU set, thereby reducing resource waste.

[0072] The information processing method provided in this application will be described below with reference to specific embodiments. First, relevant embodiments on the terminal device side will be described.

[0073] Figure 2 is a flowchart of an information processing method according to one embodiment of this application.

[0074] As shown in Figure 2, the method is: S201: Includes generating or transmitting a first report, the first report including the latest first uplink data volume and / or the latest first residual delay of the uplink data.

[0075] In this embodiment, the first report may be triggered when the trigger conditions for the first report are met. After the first report is triggered, if an available resource exists, the first report is generated or transmitted on the available resource. The first report may include the amount of uplink data in its most recent state, which in this embodiment is referred to as the first uplink data amount.

[0076] In addition / alternatively, the first report in this embodiment may further include residual delay of the uplink data in its most recent state, which is referred to in this embodiment as the first residual delay.

[0077] Uplink data is, for example, data to be transmitted that is buffered in the buffer of a terminal device. Uplink data may be the data transmitted initially, or it may be data transmitted repeatedly. Therefore, the amount of data may be the amount of buffered data. This is not limited to this embodiment.

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

[0079] The following is a brief explanation of the BSR format. BSR MAC CE (Control Element) may 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.

[0080] Alternatively, the first report in this embodiment may further include two independent reports, namely a BSR and a residual delay report. The BSR includes a first uplink data quantity, and the residual delay report includes a first residual delay.

[0081] In possible implementations, if the BSR and residual delay report are two independent reports, then after either the BSR or the residual delay report is triggered, the two reports may be transmitted or generated based on the logical channel priority. The logical channel priority of the BSR is higher than that of the residual delay report. Compared to uplink scheduling, buffer amount reporting has a better optimization effect for good scheduling than residual delay reporting. Therefore, the logical channel priority of the BSR must be higher than that of the residual delay report. During transmission, the BSR is generated or transmitted when it can be transmitted over an available uplink resource based on the result of the uplink logical channel priority. Similarly, the residual delay report is generated or transmitted when it can be transmitted over an available uplink resource based on the result of the uplink logical channel priority.

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

[0083] In this embodiment, the first report is configured to include the most recent first uplink data volume and / or the first residual delay of the uplink data, and as a result, even if the uplink data is discarded, the first report may also include relevant information about the discarded uplink data, thereby ensuring that resource waste due to redundant buffered data volume or residual delay included in the first report is avoided, as the uplink data is not discarded when the first report is triggered, but the uplink data is discarded before the first report is generated or transmitted.

[0084] Determining the time of the first uplink data amount and / or the first residual delay is crucial to ensure that the first report includes the latest first uplink data amount and / or the latest first residual delay of the uplink data. In this embodiment, the latest first uplink data amount and / or the latest first residual delay may be determined at a first time point.

[0085] In possible implementations, the first time point in this embodiment is at least one of the following: the time for determining a first resource to send a first report; the time when the first resource arrives; and the time when update instruction information is acquired, the update instruction information being used to indicate the discard of uplink data, or the update instruction information being used to indicate the amount of residual uplink data after the discard and / or the residual delay of the residual uplink data after the discard.

[0086] First, the first resource is described. After the first report is triggered, it is necessary to determine which active resources can be configured to send the first report. In this embodiment, the active resources that can be configured to send the first report are referred to as the first resource.

[0087] In this embodiment, the first time point may be the time 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 time point may be the time when the first resource arrives.

[0088] It will be understood that both the time when the first resource is determined and the time when the first resource arrives are before the BSR is transmitted, and as close as possible to the BSR transmission time. In other words, the uplink data volume and residual delay are determined as late as possible before the BSR is transmitted, in order to ensure that the first uplink data volume and first residual delay in the first report are the most up-to-date and relevant data possible.

[0089] Next, update instruction information is described. The MAC layer may receive update instruction information transmitted by the upper layer. In possible implementations, update instruction information is used to indicate uplink data discard. The first uplink data amount and / or first residual delay in the latest state after the discard may be determined based on the received update instruction information. Alternatively, update instruction information is further used to indicate the residual uplink data amount and / or residual delay of the residual uplink data after the discard. The first uplink data amount and / or first residual delay may be obtained directly from the update instruction information.

[0090] If the first point in time is the time when update instruction information is obtained, the first report may already include the determined uplink data volume and / or residual delay before the first report is transmitted. After the update instruction information is obtained, the uplink data volume and / or residual delay included in the first report may be updated so that the first report includes the latest first uplink data volume and / or first residual delay.

[0091] Alternatively, the uplink data volume and / or residual delay may not yet be determined in the first report before the first report is sent. Then, after the update instruction information is obtained, the first uplink data volume and / or first residual delay in the first report may be determined.

[0092] Possible determination methods for the first time point are described above. The relevant data in the first report is determined at these time points, which ensures that the first report includes the amount of data and / or residual delay of the most recent uplink data in the event that uplink data is discarded after the first report is triggered but the first report is not transmitted, thereby avoiding wasted resources in network device scheduling due to redundant uplink data included in the first report as a result of uplink data being discarded before the first report is generated or transmitted, even though the uplink data was not discarded when the first report was triggered.

[0093] An implementation that avoids wasting resources by setting the first report to include the latest first uplink data amount and / or the latest first residual delay is described in the above embodiments. Another possible implementation in the present application is described below with reference again to Figures 3 to 5. Figure 3 is a flowchart II of an information processing method according to one embodiment of the present application, Figure 4 is a schematic diagram I of an implementation that cancels the reporting trigger according to one embodiment of the present application, and Figure 5 is a schematic diagram II of an implementation that cancels the reporting trigger according to one embodiment of the present application.

[0094] As shown in Figure 3, the method is: S301: If uplink data is discarded, include canceling the triggered second report.

[0095] In this embodiment, discarding uplink data may be the discarding of a first data stream, the first data stream may be a data stream such as a PDU set or a data burst, and the first data stream may be a data stream containing one or more data units (PDUs and SDUs).

[0096] In this embodiment, in order to determine whether uplink data is to be discarded, it may be determined by obtaining instruction information regarding data discard (which may be obtained from the network side or through interaction within the terminal device).

[0097] In this embodiment, the second report may be the first report described above. In other words, the second report includes the latest first uplink data amount and / or the latest first residual delay.

[0098] Alternatively, the second report may differ from the first report described above. The second report includes a second uplink data volume and / or a second residual delay of the uplink data. The time at which the second uplink data volume and the second residual delay are determined is not limited in this embodiment and may be determined at any time after the second report is triggered. Thus, it is not limited in this application whether the second uplink data volume in the second report is the data volume of the uplink data in the most recent state, and whether the second residual delay in the second report is the residual delay of the uplink data in the most recent state.

[0099] It will be understood that discarding the uplink data is a condition for retracting the triggered second report.

[0100] In the embodiments, the implementation forms of the two cases of the second report described above are described below. Note that all triggered, generated, or transmitted first and second reports mentioned in the embodiments refer to a category of reports, not a specific report.

[0101] In possible implementations, an embodiment that cancels a triggered second report is used as an independent embodiment to solve the technical problems of the present application. In this embodiment, the second report may be the aforementioned report including second uplink data and / or a second residual delay of the uplink data.

[0102] First, the implementation form that triggers the second report is described. The second report is triggered when the trigger condition for the second report is met. The second report may be a BSR and / or a residual delay report. Next, the trigger condition for the second report may be the trigger condition for the BSR or the trigger condition for the residual delay report. Then, if the uplink data is discarded, the triggered second report may be canceled.

[0103] When uplink data is discarded, the triggered second report is canceled, and the second report, including redundant uplink data volume and / or redundant residual delay, is not sent to the network device, ensuring that the network device does not schedule redundant uplink resources, thereby effectively avoiding resource waste.

[0104] In one implementation, after data loss occurs, the triggered second report may be immediately canceled. Alternatively, it may be further determined whether uplink data exists on the first channel. If no uplink data exists on 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.

[0105] In one implementation, the aforementioned logical channel may be any single logical channel, or the aforementioned logical channel may also be a logical channel for triggering a second report. The aforementioned logical channel group may be any single logical channel group, or the aforementioned logical channel group may also be a logical channel group for triggering a second report. The aforementioned PDU set may be any single PDU set, or the aforementioned PDU set may also be a PDU set for triggering a second report. The aforementioned data burst information may be any data burst information, or the aforementioned data burst information may also be data burst information for triggering a second report. By setting the first channel as a channel for triggering a second report, the rationality of canceling the trigger for the second report can be effectively ensured. In other words, the following implementation forms are provided.

[0106] Implementation Mode 1: After data loss occurs, it is determined whether uplink data exists in the logical channel. If no uplink data exists in any of the logical channels, the triggered second report is canceled.

[0107] In one implementation, if the uplink data is discarded after the second report is triggered but before the second report is generated or transmitted, and no uplink data exists on any of the logical channels, the triggered second report is canceled.

[0108] In one implementation, if the uplink data is discarded during the generation of the second report after the second report is triggered, and no uplink data exists on any of the logical channels, the triggered second report is canceled.

[0109] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0110] Implementation Mode 2: After data loss occurs, it is determined whether uplink data exists in the logical channel group. If no uplink data exists in any of the logical channel groups, the triggered second report is canceled.

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

[0112] In one implementation, if the uplink data is discarded during the generation of the second report after the second report is triggered, and no uplink data exists in any one of the logical channel groups, the triggered second report is canceled.

[0113] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0114] Implementation Mode 3: After data loss occurs, it is determined whether uplink data exists in the PDU set. If uplink data does not exist in any of the PDU sets, the triggered second report is canceled.

[0115] In one implementation, after a second report is triggered, if uplink data is discarded before the second report is generated or transmitted, and no uplink data exists in any of the PDU sets, the triggered second report is canceled.

[0116] In one implementation, if uplink data is discarded during the generation of the second report after the second report is triggered, and no uplink data exists in any of the PDU sets, the triggered second report is canceled.

[0117] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0118] Implementation Mode 4: After data discard occurs, it is determined whether uplink data exists in the data burst information. If uplink data does not exist in any of the data burst information, the triggered second report is canceled.

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

[0120] In one implementation, after a second report is triggered, if uplink data is discarded during the generation of the second report, and no uplink data exists for any of the data burst information, the triggered second report is canceled.

[0121] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0122] Implementation Mode 5: After data loss occurs, it is determined whether uplink data exists in the logical channel. If uplink data does not exist in the logical channel to trigger the second report, the triggered second report is canceled.

[0123] In one implementation, after a second report is triggered, the uplink data is discarded before the second report is generated or transmitted, and if there is no uplink data on the logical channel to trigger the second report, the triggered second report is canceled.

[0124] In one implementation, after a second report is triggered, if the uplink data is discarded during the generation of the second report, and no uplink data exists on the logical channel for triggering the second report, the triggered second report is canceled.

[0125] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0126] Implementation Mode 6: After data discard occurs, it is determined whether uplink data exists in the logical channel group. If uplink data does not exist in the logical channel group used to trigger the second report, the triggered second report is canceled.

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

[0128] In one implementation, after a second report is triggered, if uplink data is discarded during the generation of the second report, and no uplink data exists in the logical channel group for triggering the second report, the triggered second report is canceled.

[0129] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0130] Implementation Mode 7: After data loss occurs, it is determined whether uplink data exists in the PDU set. If uplink data does not exist in the PDU set used to trigger the second report, the triggered second report is canceled.

[0131] In one implementation, after a second report is triggered, the uplink data is discarded before the second report is generated or transmitted, and if there is no uplink data in the PDU set to trigger the second report, the triggered second report is canceled.

[0132] In one implementation, after a second report is triggered, the uplink data is discarded during the generation of the second report, and if the uplink data is not present in the PDU set used to trigger the second report, the triggered second report is canceled.

[0133] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0134] Implementation Mode 8: After data discard occurs, it is determined whether uplink data exists in the data burst information. If uplink data does not exist in the data burst information used to trigger the second report, the triggered second report is canceled.

[0135] In one implementation, after a second report is triggered, the uplink data is discarded before the second report is generated or transmitted, and if the uplink data is not present in the data burst information to trigger the second report, the triggered second report is canceled.

[0136] In one implementation, after a second report is triggered, the uplink data is discarded during the generation of the second report, and if the uplink data is not present in the data burst information to trigger the second report, the triggered second report is canceled.

[0137] In one implementation, after the uplink data is discarded and the triggered second report is canceled, the trigger conditions for the second report may be re-evaluated, and the second report may be re-triggered when the trigger conditions are met.

[0138] In the eight different implementations described above, whether the trigger condition for the second report needs to be re-evaluated after the triggered second report is canceled may depend on the implementation. In other words, the trigger condition may or may not be re-evaluated. This is not limited to this embodiment.

[0139] If the trigger condition is re-evaluated, the re-triggered second report will inevitably include the amount of discarded uplink data and / or residual delay. Therefore, the latest uplink data amount and / or residual delay will be reported via the re-triggered second report, thereby avoiding wasted resources.

[0140] The above can be understood by referring to Figure 4. As shown in Figure 4, assuming that the second report a is triggered at time t1 and the uplink data is discarded at time t2, the triggered second report a may be canceled at time t2. Alternatively, the triggered second report a may be canceled at a time immediately following time t2. This is not limited to this embodiment.

[0141] Next, it may be re-evaluated whether the trigger condition for the second report a is met. If the trigger condition is met, the second report b may be triggered at time t3. The dashed boxes used in Figure 4 indicate that re-evaluating and executing the step that triggers the second report is optional. It will be understood that the second report is triggered at both time t1 and time t3, but different reports are triggered at different time points, and the same type of second report is triggered.

[0142] Furthermore, Figure 4 only illustrates a possible scenario. In an actual implementation process, the timeline of the steps to cancel the triggered second report and to re-trigger the second report may be determined based on the actual requirements.

[0143] In other possible implementations, the second report of this embodiment may be the first report described above. Relevant implementations in which the second report is the first report are described below.

[0144] When uplink data is discarded, the triggered first report is canceled, and the first report, including redundant uplink data volume and / or redundant residual delay, is not sent to the network device, ensuring that the network device does not schedule redundant uplink resources, thereby effectively avoiding resource waste.

[0145] In one implementation, the triggered first report may be immediately canceled after the uplink data has been discarded. Alternatively, it may be further determined whether uplink data exists on the first channel. If no uplink data exists on the first channel, the triggered first 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.

[0146] In one implementation, the aforementioned logical channel may be any single logical channel, or the aforementioned logical channel may also be a logical channel for triggering the first report. The aforementioned logical channel group may be any single logical channel group, or the aforementioned logical channel group may also be a logical channel group for triggering the first report. The aforementioned PDU set may be any single PDU set, or the aforementioned PDU set may also be a PDU set for triggering the first report. The aforementioned data burst information may be any data burst information, or the aforementioned data burst information may also be data burst information for triggering the first report. By setting the first channel as a channel for triggering the first report, the rationality of canceling the trigger for the first report can be effectively ensured. In other words, the following implementations are provided.

[0147] Implementation Mode 1: After data loss occurs, it is determined whether uplink data exists in the logical channel. If no uplink data exists in any of the logical channels, the triggered first report is canceled.

[0148] In one implementation, if the uplink data is discarded after the first report is triggered but before the first report is generated or transmitted, and no uplink data exists on any of the logical channels, the triggered first report is canceled.

[0149] In one implementation, if the first report is triggered, and the uplink data is discarded during the generation of the first report, and no uplink data exists on any of the logical channels, the triggered first report is canceled.

[0150] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0151] Implementation Mode 2: After data loss occurs, it is determined whether uplink data exists in the logical channel group. If no uplink data exists in any of the logical channel groups, the triggered first report is canceled.

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

[0153] In one implementation, if the first report is triggered, and uplink data is discarded during the generation of the first report, and no uplink data exists in any one logical channel group, the triggered first report is canceled.

[0154] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0155] Implementation Mode 3: After data loss occurs, it is determined whether uplink data exists in the PDU set. If no uplink data exists in any of the PDU sets, the triggered first report is canceled.

[0156] In one implementation, if the first report is triggered but the uplink data is discarded before the first report is generated or transmitted, and no uplink data exists in any of the PDU sets, the triggered first report is canceled.

[0157] In one implementation, if the first report is triggered, and the uplink data is discarded during the generation of the first report, and no uplink data exists in any of the PDU sets, the triggered first report is canceled.

[0158] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0159] Implementation Mode 4: After data discard occurs, it is determined whether uplink data exists in the data burst information. If uplink data does not exist in any of the data burst information, the triggered first report is canceled.

[0160] In one implementation, if the first report is triggered but the uplink data is discarded before the first report is generated or transmitted, and no uplink data exists for any of the data burst information, the triggered first report is canceled.

[0161] In one implementation, after the first report is triggered, if uplink data is discarded during the generation of the first report and no uplink data exists for any of the data burst information, the triggered first report is canceled.

[0162] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0163] Implementation Mode 5: After data discard occurs, it is determined whether uplink data exists in the logical channel. If uplink data does not exist in the logical channel to trigger the first report, the triggered first report is canceled.

[0164] In one implementation, after the first report is triggered, if the uplink data is discarded before the first report is generated or transmitted, and if there is no uplink data on the logical channel for triggering the first report, the triggered first report is canceled.

[0165] In one implementation, after the first report is triggered, if the uplink data is discarded during the generation of the first report, and no uplink data exists on the logical channel for triggering the first report, the triggered first report is canceled.

[0166] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0167] Implementation Mode 6: After data discard occurs, it is determined whether uplink data exists in the logical channel group. If uplink data does not exist in the logical channel group that triggered the first report, the triggered first report is canceled.

[0168] In one implementation, after the first report is triggered, the uplink data is discarded before the first report is generated or transmitted, and if there is no uplink data in the logical channel group to trigger the first report, the triggered first report is canceled.

[0169] In one implementation, after the first report is triggered, if the uplink data is discarded during the generation of the first report, and no uplink data exists in the logical channel group to trigger the first report, the triggered first report is canceled.

[0170] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0171] Implementation Mode 7: After data discard occurs, it is determined whether uplink data exists in the PDU set. If uplink data does not exist in the PDU set used to trigger the first report, the triggered first report is canceled.

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

[0173] In one implementation, after the first report is triggered, the uplink data is discarded during the generation of the first report, and if the uplink data is not present in the PDU set used to trigger the first report, the triggered first report is canceled.

[0174] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0175] Implementation Mode 8: After data discard occurs, it is determined whether uplink data exists in the data burst information. If uplink data does not exist in the data burst information used to trigger the first report, the triggered first report is canceled.

[0176] In one implementation, after the first report is triggered, the uplink data is discarded before the first report is generated or transmitted, and if the uplink data is not present in the data burst information to trigger the first report, the triggered first report is canceled.

[0177] In one implementation, after the first report is triggered, if the uplink data is discarded during the generation of the first report, and the uplink data is not present in the data burst information to trigger the first report, the triggered first report is canceled.

[0178] In one implementation, after the uplink data is discarded and the triggered first report is canceled, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when the trigger conditions are met.

[0179] In the eight different implementations described above, whether the trigger condition for the first report needs to be re-evaluated after the triggered first report is canceled may depend on the implementation. In other words, the trigger condition may or may not be re-evaluated. This is not limited to this embodiment.

[0180] If the trigger conditions are re-evaluated, the re-triggered first report will inevitably include the relevant data for the discarded uplink data. Therefore, the latest uplink data volume and / or residual delay will be reported via the re-triggered first report, thereby avoiding wasted resources.

[0181] For example, the above can be understood by referring to Figure 5. Assuming that the first report c is triggered at time t1 and the uplink data is discarded at time t2, as shown in Figure 5, the triggered first report c may be canceled at time t2. Alternatively, the triggered first report c may be canceled at a time immediately following time t2. This is not limited to this embodiment.

[0182] Next, it can be re-evaluated whether the trigger condition for the first report c is met. If the trigger condition is met, the first report d can be triggered at time t3. The dashed boxes used in Figure 5 indicate that performing the re-evaluation is optional.

[0183] Furthermore, Figure 5 only illustrates a possible scenario. In an actual implementation process, the timeline of the steps to cancel the triggered first report and to re-trigger the first report may be determined based on the actual requirements.

[0184] The embodiments described above in Figures 3 to 5 illustrate that the triggered second report may be canceled after the uplink data has been discarded. Whether to re-evaluate the trigger condition later may be chosen based on the actual requirements. In another possible implementation, the trigger condition may be re-evaluated directly after the uplink data has been discarded. Whether to cancel the triggered second report in the process may be chosen based on the actual requirements. Implementations of the latter embodiment are described below with reference to Figures 6 to 8.

[0185] Figure 6 is a flowchart III of an information processing method according to one embodiment of this application, Figure 7 is a schematic diagram I of an implementation configuration for re-evaluating trigger conditions according to one embodiment of this application, and Figure 8 is a schematic diagram II of an implementation configuration for re-evaluating trigger conditions according to one embodiment of this application.

[0186] As shown in Figure 6, the method is: S601: If uplink data is discarded, re-evaluate the trigger conditions for the second report. S602: Includes re-triggering a second report when the trigger condition is met.

[0187] In this embodiment, discarding uplink data may be the discarding of a first data stream, the first data stream may be a data stream such as a PDU set or a data burst, and the first data stream may be a data stream containing one or more data units (PDUs and SDUs).

[0188] In this embodiment, in order to determine whether uplink data is to be discarded, it may be determined by obtaining instruction information regarding data discard (which may be obtained from the network side or through interaction within the terminal device).

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

[0190] In this embodiment, the second report may be the first report described above. In other words, the second report includes the latest first uplink data amount and / or the latest first residual delay.

[0191] Alternatively, the second report may differ from the first report described above. The second report includes a second uplink data volume and / or a second residual delay of the uplink data. The time at which the second uplink data volume and the second residual delay are determined is not limited in this embodiment and may be determined at any time after the second report is triggered. Thus, whether the second uplink data volume in the second report is the data volume of the uplink data in the most recent state, and whether the second residual delay in the second report is the residual delay of the uplink data in the most recent state, is not limited in this embodiment.

[0192] In the embodiments, the implementation forms of the two cases of the second report described above are described below. Note that all triggered, generated, or transmitted first and second reports mentioned in the embodiments refer to a category of reports, not a specific report.

[0193] In possible implementations, the step of re-evaluating the trigger condition to trigger a second report in order to solve the technical problems of the present application is used as an independent embodiment. In this embodiment, the second report may be the above-described report including a second uplink data and / or a second residual delay of the uplink data.

[0194] If uplink data is discarded, the trigger conditions for the second report are re-evaluated, and the second report is re-triggered when it is determined that the trigger conditions are met. The re-triggered second report will inevitably include the amount of data and / or residual delay of the discarded uplink data. Therefore, the latest uplink data amount and / or residual delay is reported via the re-triggered second report, thereby avoiding wasted resources.

[0195] In this embodiment, the trigger condition for the second report may be re-evaluated after the uplink data has been discarded. Whether the triggered second report is canceled in the process may depend on the implementation. In other words, the triggered second report may or may not be canceled. This is not limited to this embodiment. If the triggered second report is canceled, the associated implementation is the same as that described in the previous embodiment and will not be repeated in detail here.

[0196] For example, the above can be understood by referring to Figure 7. As shown in Figure 7, assuming that the second report a is triggered at time t1 and the uplink data is discarded at time t2, the trigger condition for the second report a may be re-evaluated. Assuming that it is determined at time t3 that the trigger condition is met, then the second report b is triggered. The second report is triggered at both time t1 and time t3, but it will be understood that different reports are triggered at different time points, and the same type of second report is triggered.

[0197] Optionally, the triggered second report a may be canceled at time t4. The dashed boxes used in Figure 7 indicate that performing the step of canceling the triggered second report is optional.

[0198] Furthermore, Figure 7 only illustrates possible scenarios. In an actual implementation process, the timeline of the steps to cancel the triggered second report and re-trigger the second report may be determined based on actual requirements. In addition, the time at which the trigger condition is re-evaluated and the time at which the uplink data is discarded may be the same, or the time at which the trigger condition is re-evaluated may be after the uplink data has been discarded.

[0199] In other possible implementations, the second report of this embodiment may be the first report described above. Relevant implementations in which the second report is the first report are described below.

[0200] If uplink data is discarded, the trigger conditions for the first report may be re-evaluated, and the first report may be re-triggered when it is determined that the trigger conditions are met. The re-triggered first report will necessarily include the amount of data and / or residual delay of the discarded uplink data. Therefore, the latest amount of uplink data and / or residual delay will be reported via the re-triggered first report, thereby avoiding wasted resources.

[0201] In this embodiment, the trigger condition for the first report may be re-evaluated after the uplink data has been discarded. Whether the first report triggered in the process is canceled may depend on the implementation. In other words, the triggered first report may or may not be canceled. This is not limited to this embodiment. If the triggered first report is canceled, the associated implementation is the same as that described in the above embodiments and will not be repeated in detail here.

[0202] For example, the above can be understood by referring to Figure 8. As shown in Figure 8, assuming that the first report c is triggered at time t1 and the uplink data is discarded at time t2, the trigger condition for the first report c can be re-evaluated. Assuming that it is determined at time t3 that the trigger condition is met, then the first report d is triggered.

[0203] Optionally, the triggered first report d may be canceled at time t4. The dashed boxes used in Figure 8 indicate that performing the step of canceling the triggered first report is optional.

[0204] Furthermore, Figure 8 only illustrates possible scenarios. In an actual implementation process, the timeline of the step to cancel the triggered first report and the step to trigger the first report may be determined based on actual requirements. In addition, the time when the trigger condition is re-evaluated and the time when the uplink data is discarded may be the same, or the time when the trigger condition is re-evaluated may be after the uplink data has been discarded.

[0205] In the embodiments described above, it was explained that if a report is triggered but not transmitted, the uplink data is discarded. In other words, a triggered report exists. In this case, the triggered corresponding report may be canceled, and the corresponding report may be re-triggered. However, another case is when a triggered report has been transmitted. In this case, if the uplink data is discarded, the discarding of the uplink data may be used as a trigger condition to trigger a report because no triggered report exists, in order to update the amount of uplink data reported to the network device and / or the residual delay of the uplink data. The following describes the case where the uplink data is discarded after the report has been transmitted.

[0206] An explanation is provided with reference to Figure 9. Figure 9 is a flowchart IV of an information processing method according to one embodiment of the present application.

[0207] As shown in Figure 9, the method is S901: Includes triggering a third report if uplink data is discarded, the third report being used to update the uplink data volume and / or residual delay of the uplink data.

[0208] In this embodiment, when uplink data is discarded, the terminal device may send a report at least once, but has not received the uplink resource allocated by the network device. In this case, a third report may be triggered.

[0209] In this embodiment, the third report may be the first or second report described above. In this case, the third report may include the amount of residual uplink data and / or residual delay after discarding. Alternatively, the third report may be a separate report, i.e., the third report is neither a BSR nor a residual delay report. In this case, the third report may include the amount of discarded uplink data and / or residual delay of the discarded uplink data. Two implementations of the third report in this embodiment are described below.

[0210] The third report in this embodiment is used to update the uplink data volume and / or the uplink data volume. Here, “update” is used to provide a generalized explanation of the two instances of the third report. The meaning of “update” in the two instances of the third report is further explained below.

[0211] If the third report is either the first or second report, the third report may include the first uplink data volume and / or the first residual delay, as well as the second uplink data volume and / or the second residual delay. The third report is transmitted to a network device, which may then determine the status of the residual data after the discard in a timely manner and thereby update the previously received uplink data volume and / or the residual delay of the uplink data in order to update the reported data. In this case, the step in S901 may be further described as triggering the third report when uplink data is discarded, and the third report including the first uplink data volume and / or the first residual delay, and the second uplink data volume and / or the second residual delay.

[0212] If the third report is an independent report, it may include the amount of discarded uplink data and / or the residual delay of the discarded uplink data. The third report is sent to a network device, which may then determine the data discard situation in a timely manner and update the amount of previously received uplink data and / or the residual delay of the uplink data in order to update the reported data. In this case, the step in S901 may be further described as triggering a third report when uplink data is discarded, and the third report includes the amount of discarded uplink data and / or the residual delay of the discarded uplink data.

[0213] The implementation forms in the two cases of the third report are further explained below.

[0214] First, we will describe the relevant implementation forms in which the third report is the first or second report described above. The format when the third report is the first or second report can be understood by referring to Figure 10. Figure 10 is a schematic diagram I of the format of the third report according to one embodiment of this application.

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

[0216] In addition / alternatively, the third report may further include residual delay information. If the third report is the first report, the residual delay information in the third report is the first residual delay described above. If the third report is the second report, the residual delay information in the third report is the second residual delay described above.

[0217] In addition, referring to Figure 10, the third report may further include cause indicator information P1. The cause indicator information is used to indicate that the third report was triggered due to the discarding of uplink data. The cause indicator information is related to the discarding of uplink data, and this 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 was discarded.

[0218] The cause-indicating information in this embodiment also has several possible implementation forms, each described below.

[0219] Implementation Mode 1: The cause information is used to indicate that the third report was triggered due to the discarding of uplink data, or the cause information is used to indicate that the amount of uplink data and / or residual delay included in the third report was obtained after the uplink data was discarded.

[0220] It should also be understood that cause information is used to indicate that uplink data is being discarded.

[0221] In this implementation, the cause indication information does not specify the particular first channel on which the uplink data is being discarded.

[0222] In this implementation, for example, if the cause indicator information is 1, it may indicate that the third report was triggered due to the discarding of uplink data. However, the cause indicator information does not indicate the specific first channel in which the data discarding occurred.

[0223] Implementation form 2: The cause indication information is used to show that a third report was triggered due to the discarding of uplink data, and also indicates the first channel from which the discarding occurred.

[0224] It should also be understood that cause indication information is used to show that uplink data is being discarded on the first channel.

[0225] Instead, the cause indication information is used to show that the amount of uplink data and / or residual delay included in the third report was obtained after the uplink data was discarded, and further, it also indicates the first channel on which the discard occurred.

[0226] It can also be understood that cause indication information is used to show that the amount of uplink data and / or residual delay for the first channel in the third report was obtained after the uplink data was discarded.

[0227] In this implementation, the cause indication information may correspond to one first channel, one buffer data amount, and one residual delay information. In other words, the cause indication information indicates that data loss occurred in the first channel, and the buffer data amount and / or residual delay information in the third report are obtained after data loss occurred in the first channel.

[0228] In one implementation, the cause indicator information may include bits corresponding to multiple first channels. When a bit corresponding to a particular first channel is 1, it indicates that data loss has occurred in that first channel. For illustrative purposes, examples are used herein. Assuming that the cause indicator information includes bits corresponding to eight logical channel groups, each represented as P0 to P7, and that data loss has occurred in LCG0 and LCG1, then P0 and P1 may be set to 1 in the cause indicator information to indicate that data loss has occurred in LCG0 and LCG1.

[0229] The third report is configured to include cause indication information, which allows network devices to quickly determine, based on the cause indication information, why the third report was sent or whether the amount of uplink data and / or residual delay included in the third report was obtained after uplink data was discarded. If the third report is sent due to uplink data discarding, or if the third report is obtained after uplink data has been discarded, the amount of uplink data and / or residual delay can be updated in a timely manner to determine the most uplink data information, and then the correct uplink resources can be allocated, thereby avoiding resource waste.

[0230] The cause indication information described above may be added to a short BSR MAC CE, or a short truncated BSR MAC CE, or a long BSR MAC CE, or a long truncated BSR MAC CE, or an extended short BSR MAC CE, or an extended short truncated BSR MAC CE. The specific format of the BSR is not limited in this embodiment.

[0231] The relevant implementations of the third reporting format are described above, and the first and second reporting formats described above are the same as the third reporting format described herein.

[0232] An implementation that triggers a third report when uplink data is discarded is described further below. The implementations of the first and second reports described above are the same as the implementation of the third report described herein.

[0233] The third reporting trigger occurs at the MAC layer of the terminal device. However, the loss of uplink data occurs at the RLC layer or PDCP layer. Therefore, the question arises as to how the MAC layer decides whether or not to discard the uplink data.

[0234] The MAC layer may receive upper-layer directive information, which may indicate that uplink data is to be discarded. The upper-layer directive information may be transmitted by the RLC layer or by the PDCP layer. After receiving the upper-layer directive information and determining that the uplink data is to be discarded, the MAC layer may trigger a third report based on the upper-layer directive information, and then generate and transmit the third report.

[0235] Furthermore, the first channel in which the discard occurred may be further indicated in the upper layer directive information. Then, for example, after receiving the upper layer directive information, the MAC layer may further determine, based on the upper layer directive information, whether the first channel in which the discard occurred triggered a third report.

[0236] If the first channel where the data was dropped triggers a third report, it indicates that buffer data volume and / or residual 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 residual delay reported to the network device.

[0237] Alternatively, if the first channel where the drop occurred has not yet triggered the third report, it indicates that the buffer data volume and / or residual delay information has not been reported to the network device. In this case, the third report does not need to be triggered to update the data volume and / or residual delay. It is determined whether the first channel where the drop occurred has triggered the third report, and then it is determined whether to trigger the third report, thereby effectively increasing the necessity and effectiveness of triggering the third report.

[0238] The above explanation can be further understood through specific examples of uplink data discarding, with reference to Figures 11 and 12. Figure 11 is a schematic diagram of uplink data discarding according to one embodiment of the present application, and Figure 12 is a schematic timing diagram of data discarding according to one embodiment of the present application.

[0239] Referring to Figures 11 and 12, we assume that at time t1, uplink data information, i.e., buffer data amount and / or residual delay information, for three logical channel groups, LCG1, LCG2, and LCG3, is reported, and that the uplink data amount at time t1 is 10 MB.

[0240] Next, at time t2, PDU sets are discarded in LCH1 and LCH2 within LCG1, and in LCH4 and LCH6 within LCG2. We assume that the amount of residual uplink data after the discards is 7MB.

[0241] Based on the above, if uplink data is discarded, a third report may be triggered, which may include the amount of remaining uplink data after the discard, i.e., 7 MB. In addition, the third report may further include cause indication information. The cause indication information may indicate that the third report was triggered due to the discard of uplink data. Further cause indication information may further indicate that the first channels on which the data discard occurred were LCG1 and LCG2.

[0242] Based on the above, in this embodiment, a third report may be triggered after uplink data has been discarded. The third report may include the amount of residual uplink data and / or residual delay after the discard, and as a result, the network device may update the previously received uplink data information based on the relevant information of the residual uplink data after the discard, thereby allocating the correct amount of uplink resources to avoid wasting resources.

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

[0244] The format of the third report, in the case of an independent report, can be understood by referring to Figures 13 and 14. Figure 13 is schematic diagram II of the format of the third report according to one embodiment of the present application, and Figure 14 is schematic diagram III of the format of the third report according to one embodiment of the present application.

[0245] Referring to Figure 13, the third report may include the amount of discarded uplink data and / or delay information for the discarded uplink data.

[0246] For example, in the initial case, 10 MB of uplink data exists, and the amount of uplink data and / or residual delay of the uplink data are reported to the network device. Assuming that 3 MB of uplink data is discarded, the third report may include the amount of uplink data of the discarded 3 MB and / or residual delay of the 3 MB of uplink data.

[0247] Next, the network device may calculate the amount of residual uplink data after the discard and / or the residual delay of the residual uplink data after the discard, based on the amount of discarded uplink data and / or the delay information of the discarded uplink data in the third report.

[0248] Furthermore, referring to Figure 14, the third report may further include a first channel (LCG shown in Figure 14) corresponding to the discarded uplink data, so that the network device may determine a specific first channel from which the uplink data is discarded.

[0249] Based on the above, in this embodiment, a third report may be triggered after uplink data has been discarded. The third report may include the amount of data and / or residual delay of the discarded uplink data, and as a result, the network device may update the previously received uplink data information and thereby allocate the correct amount of uplink resources to avoid wasting resources.

[0250] The relevant implementation forms on the terminal device side are described in the embodiments described above. On the network device side, configuration information is sent to the terminal device, and the network device may be instructed to execute the contents described in the embodiments described above. The relevant implementation forms on the network device side are described below.

[0251] In this embodiment, the network device may transmit configuration information to the terminal device, and the configuration information includes the following information, namely: Whether the terminal device reports the most recent first uplink data volume and / or the most recent first residual delay of the uplink data, At least one of the following: a first time for determining the latest first uplink data volume or the latest first residual delay; a first time for determining a first resource for transmitting the first uplink data volume and / or the first residual delay; a time when the first resource arrives; and a time when update instruction information is acquired, wherein the update instruction information is used to indicate the discarding of uplink data, or the update instruction information is used to indicate the residual uplink data volume and / or the residual delay of the residual uplink data after the discarding. Whether the terminal device cancels the triggered second report when uplink data is discarded. First channel information, which is used to determine whether to cancel the triggered second report, Whether the terminal device re-evaluates the trigger conditions for the second report when uplink data is discarded, and Whether the terminal device triggers a third report when uplink data is discarded, and whether the third report is used to update the amount of uplink data and / or residual delay of the uplink data, and whether the trigger is said to occur. It is used to indicate at least one of the following.

[0252] The information mentioned above will be explained in the following order.

[0253] Information 1: This concerns whether the terminal device reports the most recent first uplink data volume and / or the most recent first residual delay of the uplink data.

[0254] The specific methods for indicating the constituent information of Information 1 include the following three cases:

[0255] Case I: 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.

[0256] In this case, the configuration information has two configurable options regarding whether the terminal device reports the latest data. For example, the configuration information may include a corresponding instruction bit that instructs the terminal device to report the latest first uplink data amount and / or the latest first residual delay of the uplink data. Alternatively, the instruction bit may be 1 or 0 that instructs the terminal device not to report the latest first uplink data amount and / or the latest first residual delay of the uplink data.

[0257] Case II: 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.

[0258] In this case, the configuration information will only show the positive case, that is, the configuration information will directly indicate that the terminal device should report the latest first uplink data amount and / or the latest first residual delay of the uplink data.

[0259] Case III: 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.

[0260] In this case, the configuration information only shows the negative case, 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.

[0261] The terminal device may decide 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 configuration information instructions of the currently deployed information 1.

[0262] Information 2: This relates to at least one of the following: a first time point in time for determining the latest first uplink data amount or the latest first residual delay; a first resource for determining the first uplink data amount and / or first residual delay; a first resource arriving; and an update instruction information being acquired.

[0263] The configuration information may further indicate a specific implementation of the first time point, which may include at least one of the following: the time for determining a first resource for transmitting a first uplink data amount and / or a first residual delay; the time when the first resource arrives; and the time when update instruction information is obtained.

[0264] Information 3: This concerns whether the terminal device will retract the second report that was triggered when the uplink data was discarded.

[0265] The specific methods for indicating the configuration information in Information 3 include the following three cases:

[0266] Case I: Configuration information indicates whether the terminal device cancels the second report triggered when uplink data is discarded.

[0267] In this case, the configuration information has two configurable options regarding whether the terminal device needs to cancel the second report triggered when the uplink data is discarded. For example, the configuration information may indicate that the terminal device should cancel the triggered second report by including the corresponding indication bit. Instead, the indication bit may be 1 or 0 indicating that the terminal device should not cancel the triggered second report.

[0268] Case II: The configuration information indicates that the terminal device cancels the second report triggered when the uplink data is discarded.

[0269] In this case, the configuration information indicates only the affirmative case, that is, the configuration information directly indicates that the terminal device cancels the second report triggered when the uplink data is discarded.

[0270] Case III: The configuration information indicates that the terminal device does not cancel the second report triggered when the uplink data is discarded.

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

[0272] The configuration information may enable the terminal device to determine whether the second report triggered when the uplink data is discarded needs to be cancelled through the indication information 3.

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

[0274] The specific indication method of the configuration information of Information 4 includes the following three cases.

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

[0276] In this case, the configuration information has two configurable options for determining whether to cancel the second report triggered through the first channel information. For example, the configuration information may include a corresponding instruction bit to indicate that the first channel information is used to decide to cancel the triggered second report. Alternatively, the instruction bit may be 1 or 0, which indicates that the first channel information is used to decide that the triggered second report is not canceled.

[0277] Case II: The configuration information indicates that the first channel information is used to determine that the triggered second report was canceled.

[0278] In this case, the configuration information only indicates the positive case, that is, the configuration information directly indicates that the first channel information is used to determine that the triggered second report was canceled.

[0279] Case III: The configuration information indicates that the first channel information is used to determine that the triggered second report is not canceled.

[0280] In this case, the configuration information only indicates the negative case, that is, the configuration information directly indicates that the first channel information is used to determine that the triggered second report will not be canceled.

[0281] Three different methods for specifying the configuration information of the first channel information are described above. It should be understood that the above describes how to configure network devices, not how terminal devices operate. The contents and various cases specifically indicated by the first channel information in Information 4 are further explained below.

[0282] Based on the above explanation, when uplink data is discarded, the terminal device may decide to directly cancel the triggered second report. Alternatively, to decide whether to cancel the triggered second report, it may be further determined whether uplink data exists on the first channel.

[0283] The first channel information here may indicate whether the terminal device should perform the step of "determining whether uplink data exists on the first channel." Specifically, at least one particular first channel may be indicated in the first channel information, or no particular first channel may be indicated in the first channel information. Two cases are described below.

[0284] In one implementation, the first channel information indicates at least one specific first channel, and the terminal device may, based on configuration information, determine whether uplink data exists on the specific first channel and thereby decide whether to cancel the triggered second report. Alternatively, it may further determine whether uplink data exists on the first channel that triggered the second report on the specific first channel and thereby decide whether to cancel the triggered second report.

[0285] In this specification, examples are used for illustrative purposes. Assuming that LCG1-LCG8 exist and LCG1, LCG2, and LCG3 are indicated in the first channel information, the terminal device may determine whether uplink data exists for LCG1, LCG2, and LCG3 when uplink data is discarded, and thereby determine whether to cancel the triggered second report. Furthermore, the terminal device may further determine whether uplink data exists for the LCG that triggered the second report for LCG1, LCG2, and LCG3, and thereby determine whether to cancel the triggered second report.

[0286] In another implementation form, the first channel information does not indicate a specific first channel. In this case, the terminal device may determine whether uplink data exists on any one of the first channels based on the configuration information, and thereby determine whether to cancel the triggered second report. Instead, further, it is determined whether uplink data exists on the first channel that triggered the second report on any one of the first channels, and thereby it is determined whether to cancel the triggered second report.

[0287] Information 5: Regarding whether the terminal device re-evaluates the trigger condition of the second report when uplink data is discarded.

[0288] The specific indication method of the configuration information of Information 5 includes the following three cases.

[0289] Case I: The configuration information indicates whether the terminal device re-evaluates the trigger condition of the second report when uplink data is discarded.

[0290] In this case, the configuration information has two configurable options regarding whether the terminal device re-evaluates the trigger condition of the second report when uplink data is discarded. For example, the configuration information may indicate that the terminal device re-evaluates the trigger condition of the second report by including the corresponding indication bit. Instead, the indication bit may be 1 or 0, which indicates that the terminal device does not re-evaluate the trigger condition of the second report.

[0291] Case II: The configuration information indicates that the terminal device re-evaluates the trigger condition of the second report when uplink data is discarded.

[0292] In this case, the configuration information indicates only the affirmative case, that is, the configuration information directly indicates that the terminal device re-evaluates the trigger condition of the second report when uplink data is discarded.

[0293] Case III: The configuration information indicates that the terminal device does not re-evaluate the trigger condition for the second report when uplink data is discarded.

[0294] In this case, the configuration information only indicates the negative case, that is, the configuration information directly indicates that the terminal device does not re-evaluate the trigger condition for the second report when uplink data is discarded.

[0295] The configuration information, through instruction information 5, may enable the terminal device to determine whether the trigger condition for the second report needs to be re-evaluated when uplink data is discarded. If the trigger condition for the second report needs to be re-evaluated, the terminal device re-triggers the second report when the trigger condition for the second report is met.

[0296] Information 6: Whether the terminal device triggers a third report when uplink data is discarded, the third report being used to update the amount of uplink data and / or residual delay of the uplink data, and whether such trigger is used.

[0297] The specific methods for indicating the constituent information of Information 5 include the following three cases:

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

[0299] In this case, the configuration information has two configurable options regarding whether the terminal device should trigger a third report that is triggered when uplink data is lost. For example, the configuration information may indicate that the terminal device should trigger the third report by including a corresponding instruction bit. Alternatively, the instruction bit may be 1 or 0, indicating that the terminal device should not trigger the third report.

[0300] Case II: The configuration information indicates that the terminal device triggers a third report when uplink data is discarded.

[0301] In this case, the configuration information will only show the positive case, that is, the configuration information will directly indicate that the terminal device will trigger a third report when uplink data is discarded.

[0302] Case III: The configuration information indicates that the terminal device does not trigger a third report when uplink data is discarded.

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

[0304] The configuration information, through instruction information 6, may enable the terminal device to determine whether a third report should be triggered when uplink data is discarded. Details of the third report can be found in the description of the embodiments above and will not be repeated here.

[0305] On the network device side, configuration information is sent to the terminal device, and the terminal device may be instructed to report corresponding information or perform corresponding actions based on the instructions in the configuration information, thereby carrying out what was described in the above embodiments and effectively reducing resource waste.

[0306] Figure 15 is a schematic diagram I of an information processing device according to one embodiment of the present application. As shown in Figure 15, the device 150 is a processing module 1501, Processing module 1501 is configured to generate a first report, the first report including the latest first uplink data amount and / or the latest first residual delay of the uplink data, processing module 1501 and The system includes a transmission module 1502 configured to transmit a first report.

[0307] In a possible design, the latest first uplink data volume and / or the latest first residual delay are determined at the first time point. The first point in time is at least one of the following: the time for determining the first resource to send the first report; the time when the first resource arrives; and the time when update instruction information is obtained, the update instruction information being used to indicate the discard of uplink data, or the update instruction information being used to indicate the amount of residual uplink data after the discard and / or the residual delay of the residual uplink data after the discard.

[0308] In a possible design, processing module 1501 is, If uplink data is discarded, the system is further configured to cancel the triggered second report.

[0309] In a 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.

[0310] In a possible design, processing module 1501 is, If uplink data is discarded and no uplink data exists on the first channel, the system is further configured to cancel the triggered second report, the first channel including at least one of the following: a logical channel, a logical channel group, a PDU set, and data burst information.

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

[0312] In a possible design, processing module 1501 is, If uplink data is discarded, re-evaluate the trigger conditions for the second report. It is further configured to re-trigger a second report when the trigger condition is met.

[0313] In a possible design, processing module 1501 is, A third report is triggered if uplink data is discarded, and this third report is further configured to be used to update the amount of uplink data and / or the residual delay of the uplink data.

[0314] In possible designs, the third report is either the first or second report.

[0315] In a possible design, the terminal device includes a media access control MAC layer, and the processing module 1501 is, The MAC layer receives upper-layer instruction information, which is used to indicate that uplink data is to be discarded. The MAC layer is further configured to trigger a third report based on the upper-layer directive information.

[0316] In a possible design, higher-layer indicator information is used to indicate the first channel to which the discarded uplink data belongs. Processing module 1501 is, Based on the upper layer instruction information, the MAC layer determines whether the first channel to which the discarded uplink data belonged triggered the third report. If so, it is further configured to trigger a third report.

[0317] In a possible design, the third report would include cause-indicating information, which would be used to indicate that the third report was triggered by the discarding of uplink data, or that the amount of uplink data and / or residual delay included in the third report was obtained after the uplink data was discarded.

[0318] In a possible design, the third report would include the amount of discarded uplink data and / or delay information for the discarded uplink data.

[0319] In a possible design, the third report would further include the first channel corresponding to the discarded uplink data.

[0320] In a possible design, discarded uplink data would include at least one set of protocol data units (PDUs).

[0321] The apparatus provided in this embodiment may be configured to perform the technical solutions of the embodiments of the method described above. The principles of the implementation and its technical effects are similar and details will not be described repeatedly in this embodiment.

[0322] Figure 16 is a schematic diagram II of an information processing device according to one embodiment of this application. As shown in Figure 16, the device 160 includes a transmission module 1601.

[0323] The transmitting module 1601 transmits configuration information, which includes the following information: Whether the terminal device reports the most recent first uplink data volume and / or the most recent first residual delay of the uplink data, At least one of the following: a first time for determining the latest first uplink data volume or the latest first residual delay; a first time for determining a first resource for transmitting the first uplink data volume and / or the first residual delay; a time when the first resource arrives; and a time when update instruction information is acquired, wherein the update instruction information is used to indicate the discarding of uplink data, or the update instruction information is used to indicate the residual uplink data volume and / or the residual delay of the residual uplink data after the discarding. Whether the terminal device cancels the triggered second report when uplink data is discarded. First channel information, which is used to determine whether to cancel the triggered second report, Whether the terminal device re-evaluates the trigger conditions for the second report when uplink data is discarded, and Whether the terminal device triggers a third report when uplink data is discarded, and whether the third report is used to update the amount of uplink data and / or residual delay of the uplink data, and whether the trigger is said to occur. It is used to indicate at least one of the following.

[0324] The apparatus provided in this embodiment may be configured to perform the technical solutions of the embodiments of the method described above. The principles of the implementation and its technical effects are similar and details will not be described repeatedly in this embodiment.

[0325] The information processing method provided in the embodiments of this application may be applied to an electronic device having communication functions. The electronic device includes a terminal device. For specific device forms of terminal devices, please refer to the related descriptions above. Details will not be repeated here.

[0326] One embodiment of this application provides a terminal device. The terminal device includes a processor and memory. The memory stores computer executable instructions. The processor is configured to execute the computer executable instructions stored in the memory and cause the terminal device to perform the aforementioned method.

[0327] One embodiment of this application provides a chip, which includes a processor. The processor is configured to invoke a computer program in memory to perform the technical solution of the embodiment described above. Its implementation principle and technical effects are the same as those of the related embodiment described above. Details will not be repeated here.

[0328] One embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the method described above is performed. All or part of the method in the above embodiment may be implemented by software, hardware, firmware, or any combination thereof. If implemented by software, the functions may be stored in the computer-readable medium or transmitted over the computer-readable medium as one or more instructions or codes. The computer-readable medium may include a computer storage medium and a communication medium, and may further include any medium capable of transmitting a computer program from one location to another. The storage medium may be any target medium accessible by a computer.

[0329] In possible implementations, computer-readable media may include RAM, ROM, compact disc read-only memory (CD-ROM), or other optical disc memory, magnetic disc memory, or other magnetic storage devices, or any other medium that holds or stores the necessary program code in the form of instructions or data structures and can be accessed by a computer. In addition, any connection is appropriately called computer-readable media. For example, if software is transmitted from a website, server, or another remote source via coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technology (infrared, radio waves, microwaves, etc.), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology such as infrared, radio waves, microwaves are included in the definition of media. As used herein, magnetic disks and optical disks include compact disks, laser disks, optical disks, Digital Versatile Discs (DVDs), floppy disks, and Blu-ray discs. Magnetic disks generally reproduce data magnetically, while optical disks reproduce data optically using a laser. The combinations mentioned above should also be included within the scope of computer-readable media.

[0330] One embodiment of this application provides a computer program product. The computer program product includes a computer program. When the computer program is executed, it causes a computer to perform the method described above.

[0331] Embodiments of this application will be described in relation to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of this application. It should be understood that computer program instructions can realize each process and / or block of a flowchart and / or block diagram, as well as combinations of processes and / or blocks of a flowchart and / or block diagram. These computer program instructions are provided to a processing unit of a general-purpose computer, a dedicated computer, an embedded processor, or another programmable device to generate a machine, and as a result, instructions executed by the processing unit of the computer or another programmable data processing device generate a machine to realize a particular function in one or more processes in a flowchart and / or one or more blocks in a block diagram.

[0332] The specific implementations described above further elaborate on the objectives, technical solutions, and beneficial effects of the present invention. It should be understood that the above descriptions represent only specific implementations of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, or improvements made based on the technical solutions of the present invention shall fall within the scope of protection of the present invention. [Explanation of symbols]

[0333] 101 Network Devices 102 Terminal devices 150 Information Processing Devices 1501 Processing Module 1502 Transmitter Module 160 Information Processing Devices 1601 Transmitter Module

Claims

1. An information processing method applied to a terminal device, A method comprising the steps of generating or transmitting a first report, wherein the first report includes the most recent first uplink data volume and / or the most recent first residual delay of the uplink data.

2. The most recent first uplink data volume and / or the most recent first residual delay is determined at the first time point. The method according to claim 1, wherein the first time point is at least one of the following: a time for determining a first resource for transmitting the first report; a time when the first resource arrives; and a time when update instruction information is obtained, wherein the update instruction information is used to indicate the discarding of the uplink data, or the update instruction information is used to indicate the amount of residual uplink data after the discarding and / or the residual delay of the residual uplink data after the discarding.

3. The method according to claim 1 or 2, further comprising the step of canceling a triggered second report if the uplink data is discarded.

4. The method according to claim 3, wherein the second report is the first report, or the second report includes a second uplink data amount and / or a second residual delay.

5. If the uplink data is discarded, the step of canceling the triggered second report is: The method according to claim 3 or 4, further comprising the step of canceling the triggered second report if the uplink data is discarded and no uplink data exists on the first channel, wherein 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, wherein 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. If the uplink data is discarded, the trigger conditions for the second report are re-evaluated. The steps include: re-triggering the second report when the trigger condition is met; The method according to any one of claims 1 to 6, further comprising:

8. The method according to any one of claims 1 to 7, further comprising the step of triggering a third report if the uplink data is discarded, the third report being used to update the amount of uplink data and / or the residual delay of the uplink data.

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

10. The terminal device includes a media access control (MAC) layer, and the step of triggering a third report is: The MAC layer receives upper-layer instruction information, the upper-layer instruction information is used to indicate that the uplink data is to be discarded, and The MAC layer triggers the third report based on the upper layer instruction information, The method according to claim 9, including the method described in claim 9.

11. The aforementioned upper-layer instruction information is used to indicate the first channel to which the discarded uplink data belongs. The step of triggering the third report based on the upper layer instruction information by the MAC layer is as follows: The MAC layer determines, based on the upper layer instruction information, whether the first channel to which the discarded uplink data belongs triggered the third report. If the aforementioned trigger occurs, the step of triggering the third report, The method according to claim 10, including the method described in claim 10.

12. The method according to any one of claims 9 to 11, wherein the third report includes cause indication information, which is used to indicate that the third report was triggered by the discarding of the uplink data, or that the amount of uplink data and / or residual delay included in the third report was obtained after the uplink data was discarded.

13. The method according to claim 8, wherein 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, wherein the third report further includes a first channel corresponding to the discarded uplink data.

15. The method according to any one of claims 1 to 14, wherein the discarded uplink data includes at least one set of protocol data units (PDUs).

16. An information processing method applied to a terminal device, A method that includes a step of canceling a triggered second report if uplink data is discarded.

17. An information processing method applied to a terminal device, If the uplink data is discarded, the trigger conditions for the second report are re-evaluated. The steps include: re-triggering the second report when the trigger condition is met; Methods that include...

18. An information processing method applied to a terminal device, A method comprising the step of triggering a third report if the uplink data is discarded, the third report being used to update the amount of uplink data and / or the residual delay of the uplink data.

19. An information processing method applied to a network device, A step of transmitting configuration information, wherein the configuration information includes the following information, namely: Whether the terminal device reports the latest first uplink data volume and / or the latest first residual delay of the uplink data, At least one of the following: a first time for determining the latest first uplink data volume or the latest first residual delay; a first time for determining a first resource for transmitting the first uplink data volume and / or the first residual delay; a time when the first resource arrives; and a time when update instruction information is acquired, wherein the update instruction information is used to indicate the discarding of the uplink data, or the update instruction information is used to indicate the residual uplink data volume and / or the residual delay of the residual uplink data after the discarding. When the uplink data is discarded, the terminal device will decide whether to cancel the triggered second report. First channel information, wherein the first channel information is used to determine whether to cancel the triggered second report, When the uplink data is discarded, whether the terminal device re-evaluates the trigger conditions for the second report, and Whether the terminal device triggers a third report when the uplink data is discarded, the third report being used to update the amount of uplink data and / or the residual delay of the uplink data, and whether the trigger is A method, including steps, used to demonstrate at least one of the following.

20. An information processing device, A processing module configured to generate a first report, wherein the first report includes the latest first uplink data amount and / or the latest first residual delay of the uplink data, A transmitting module configured to transmit the first report and An information processing device equipped with the following features.

21. An information processing device, A transmission module configured to transmit configuration information, wherein the configuration information includes 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, At least one of the following: a first time for determining the latest first uplink data volume or the latest first residual delay; a time for determining a first resource for transmitting the first uplink data volume and / or the first residual delay; a time when the first resource arrives; and a time when update instruction information is acquired, wherein the update instruction information is used to indicate the discarding of the uplink data, or the update instruction information is used to indicate the residual uplink data volume and / or the residual delay of the residual uplink data after the discarding. When the uplink data is discarded, does the terminal device cancel the triggered second report? First channel information, wherein the first channel information is used to determine whether to cancel the triggered second report, When the uplink data is discarded, whether the terminal device re-evaluates the trigger conditions for the second report, and Whether the terminal device triggers a third report when the uplink data is discarded, the third report being used to update the amount of uplink data and / or the residual delay of the uplink data, and whether the trigger is An information processing device comprising a transmission module used to indicate at least one of the following.

22. A terminal device comprising a processor and memory, The aforementioned memory stores computer executable instructions, The processor executes the computer executable instructions stored in the memory, thereby the terminal device performs the method according to any one of claims 1 to 18.

23. A network device comprising a processor and memory, The aforementioned memory stores computer executable instructions, The processor executes the computer executable instructions stored in the memory, thereby the network device performs the method according to claim 19.

24. A computer-readable storage medium for storing computer programs, A computer-readable storage medium wherein the computer program, when executed by a processor, performs the method according to any one of claims 1 to 19.

Images