Information sending, receiving, and processing method and apparatus, and communication system

Abstract

Embodiments of the present application provide an information sending, receiving, and processing method and apparatus, and a communication system. The method comprises: triggering a delay status report; and sending the delay status report to a network device, the delay status report comprising data volume information, and the data volume information comprising the amount of data of a PDCP layer of a terminal device which is related to the remaining time of a service data unit PDCP SDU and / or the amount of data of an RLC layer which is related to the remaining time of a service data unit RLC SDU.

Description

Method, device and communication system for sending, receiving and processing information Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] In Release 18 of the 3rd Generation Partnership Project (3GPP), research began on enhancements to Extended Reality (XR) services. XR services refer to all combined real and virtual environments, as well as human-computer interactions enabled by computing technology and wearable devices. XR services can include Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR).

[0003] For XR services with strict latency constraints, a latency-aware scheduler is beneficial to ensure quality of service (QoS). This latency-aware scheduler is feasible in the downlink because the network (e.g., the gNB) knows the UE QoS characteristics (e.g., through 5G QoS parameters such as the 5G QoS Identifier (5QI)) and the arrival time of XR frames (packets), thus also understanding the urgency of the data to be scheduled.

[0004] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0005] Summary of the Invention

[0006] The inventors discovered that for the uplink, since the current Buffer Status Report (BSR) only provides the amount of cached data but does not convey information about how long the data in the user equipment (UE) has been cached, the network-side scheduler cannot accurately know the cache time of the data in the UE. Therefore, 3GPP believes that it is beneficial for the UE to report delay information for XR services.

[0007] Currently, 3GPP has agreed to introduce reporting of delay information. For example, the delay information may include remaining time and its associated data volume (data volume or buffer status or amount of data), but it has not yet clarified how to determine or calculate the data volume associated with the remaining time.

[0008] In response to at least one of the above problems, embodiments of the present application provide a method, device, and communication system for sending, receiving, and processing information.

[0009] According to one aspect of an embodiment of the present application, a method for sending information is provided, which is applied to a terminal device, wherein the method includes:

[0010] Triggering a delayed status report;

[0011] The delay status report is sent to the network device, and the delay status report includes data volume information, which includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0012] According to another aspect of an embodiment of the present application, there is provided an information receiving method, applied to a network device, wherein the method includes:

[0013] Receive a delay status report sent by a terminal device, where the delay status report includes data volume information, where the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0014] According to another aspect of an embodiment of the present application, there is provided an information processing method, applied to a terminal device, wherein the method includes:

[0015] Triggering a delayed status report;

[0016] Triggering a scheduling request;

[0017] Cancel the scheduling request.

[0018] According to another aspect of an embodiment of the present application, there is provided an information processing method, applied to a terminal device, wherein the method includes:

[0019] Triggering a delay status report; triggering a scheduling request; initiating a random access procedure related to the scheduling request; and stopping the random access procedure.

[0020] According to another aspect of an embodiment of the present application, there is provided an information processing method, applied to a terminal device, wherein the method includes:

[0021] A MAC PDU is generated; the MAC PDU includes a Delay Status Report (DSR) and / or a Buffer Status Report (BSR).

[0022] According to one aspect of an embodiment of the present application, there is provided an information sending apparatus, applied to a terminal device, wherein the apparatus includes:

[0023] a first triggering unit, configured to trigger a delay status report;

[0024] A sending unit, which is used to send the delay status report to the network device, wherein the delay status report includes data volume information, and the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0025] According to another aspect of an embodiment of the present application, there is provided an information receiving apparatus, applied to a network device, wherein the apparatus includes:

[0026] A receiving unit is used to receive a delay status report sent by a terminal device, wherein the delay status report includes data volume information, and the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0027] According to another aspect of an embodiment of the present application, there is provided an information processing apparatus, applied to a terminal device, wherein the apparatus includes:

[0028] The second triggering unit is used to trigger a delay status report; the third triggering unit is used to trigger a scheduling request; and the first processing unit is used to cancel the scheduling request.

[0029] According to another aspect of an embodiment of the present application, there is provided an information processing apparatus, applied to a terminal device, wherein the apparatus includes:

[0030] a fourth triggering unit configured to trigger a delay status report; a fifth triggering unit configured to trigger a scheduling request;

[0031] A sixth triggering unit, initiating a random access process related to the scheduling request;

[0032] A second processing unit is configured to stop the random access procedure.

[0033] According to another aspect of an embodiment of the present application, there is provided an information processing apparatus, applied to a terminal device, wherein the apparatus includes:

[0034] The third processing unit is configured to generate a MAC PDU; the MAC PDU includes a delay status report (DSR) and / or a buffer status report (BSR).

[0035] According to another aspect of an embodiment of the present application, a communication system is provided, including:

[0036] A terminal device, the terminal device being configured to execute the above-mentioned information sending method and / or information processing method on the terminal device side;

[0037] A network device is configured to execute the above-mentioned information receiving method on the network device side.

[0038] One of the beneficial effects of the embodiments of the present application is that it clarifies how to determine the amount of data associated with the remaining time, that is, the amount of data includes the amount of data related to the remaining time of the service data unit of the PDCP layer and / or RLC layer of the terminal device, thereby solving the problems existing in the prior art.

[0039] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0040] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0041] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0043] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0044] FIG2 is a schematic diagram of an information sending method according to an embodiment of the present application;

[0045] FIG3 is a schematic diagram of an application scenario of the information sending method according to an embodiment of the present application;

[0046] FIG4 is a schematic diagram of an information receiving method according to an embodiment of the present application;

[0047] FIG5 is a schematic diagram of an information processing method according to an embodiment of the present application;

[0048] FIG6 is another schematic diagram of the information processing method according to an embodiment of the present application;

[0049] FIG7 is another schematic diagram of the information processing method according to an embodiment of the present application;

[0050] FIG8 is a schematic diagram of an information sending device according to an embodiment of the present application;

[0051] FIG9 is a schematic diagram of an information receiving device according to an embodiment of the present application;

[0052] FIG10 is a schematic diagram of an information processing device according to an embodiment of the present application;

[0053] FIG11 is another schematic diagram of an information processing device according to an embodiment of the present application;

[0054] FIG12 is another schematic diagram of the information processing device according to an embodiment of the present application;

[0055] FIG13 is a schematic diagram of a network device according to an embodiment of the present application;

[0056] FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0057] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0058] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0059] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0060] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0061] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other communication protocols currently known or to be developed in the future.

[0062] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0063] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0064] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0065] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0066] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0067] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0068] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" are interchangeable, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" are interchangeable to avoid confusion.

[0069] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, and the terms “downlink data signal” and “downlink data information” or “physical downlink shared channel (PDSCH)” are interchangeable.

[0070] In addition, sending or receiving PUSCH can be understood as sending or receiving uplink data carried by PUSCH, sending or receiving PUCCH can be understood as sending or receiving uplink information carried by PUCCH, and sending or receiving PRACH can be understood as sending or receiving preamble carried by PRACH; uplink signals can include uplink data signals and / or uplink control signals, etc., and can also be referred to as uplink transmission (UL transmission) or uplink information or uplink channels. Sending uplink transmission on uplink resources can be understood as sending the uplink transmission using the uplink resources. Similarly, downlink data / signals / channels / information can be understood accordingly.

[0071] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, an MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0072] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0073] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0074] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0075] Among them, terminal device 102 can send uplink data to network device 101, for example, using a dynamically scheduled grant or a configured grant transmission method. Network device 101 can receive data sent by one or more terminal devices 102, send information to terminal device 102 to schedule new uplink data transmission or uplink data retransmission, and can also send downlink data.

[0076] The information sending method, information receiving method, information processing method and the device thereof according to the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0077] Embodiments of the first aspect

[0078] An embodiment of the present application provides a method for sending information, which is applied to the terminal equipment (UE) side and is described below with reference to the accompanying drawings.

[0079] FIG2 is a schematic diagram of a method for sending information according to an embodiment of the present application. As shown in FIG2 , the method includes:

[0080] 201, triggering a Delay Status Report (DSR);

[0081] 202. Send the delay status report (DSR) to the network device, where the delay status report (DSR) includes data volume information, where the data volume information includes the data volume (data volum or buffer status or amount of data) related to the remaining time (remaining time) of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume (data volum or buffer status or amount of data) related to the remaining time (remaining time) of the service data unit (RLC SDU) of the RLC layer.

[0082] According to the above embodiment, it is clarified how to determine the amount of data associated with the remaining time, that is, the amount of data includes the amount of data related to the remaining time of the service data unit of the PDCP layer and / or RLC layer of the terminal device, thereby solving the problems existing in the prior art.

[0083] In some embodiments, in 201, the DSR is used to report the delay information of at least one logical channel group (LCG). Any existing method can be used to trigger the DSR report, for example, based on a threshold, for example, when the remaining time of a PDU (Protocol Data Unit) or PDU set (Protocol Data Unit set) is lower than a threshold, the DSR report is triggered. A PDU carries a payload of a unit of information generated at the application layer, such as a frame or video slice of an XR service, and a PDU set includes one or more such PDUs. The threshold can be configured by the network, for example, the network configures a threshold for triggering the DSR report for each logical channel group (LCG).

[0084] In some embodiments, in 202, the UE may include at least one piece of data volume information in a DSR and report it to the network side. The data volume information may be used to indicate the amount of data associated with the remaining time. The amount of data associated with the remaining time may also be expressed as a buffer size or a buffer status, etc. The length of the data volume information may be 5 bits or 8 bits. A value or index of the data volume information corresponds to a range of data volumes associated with the remaining time. The data volume associated with the remaining time is expressed in bits or bytes.

[0085] In some embodiments, one piece of data volume information corresponds to one logical channel group.

[0086] In some embodiments, the UE may determine that the data amount information includes the data amount of the PDCP layer and / or the data amount of the RLC layer. For example, the data amount of the PDCP layer includes the data amount related to the remaining time (remaining time) of the service data unit (PDCP SDU), and the data amount of the RLC layer includes the data amount related to the remaining time of the service data unit (RLC SDU). In this case, the method may further include (not shown in the figure):

[0087] Determining the data volume information included in the DSR solves the problems existing in the prior art. For example, in the PDCP layer and / or the RLC layer, determining the data volume information may include at least one of the following methods:

[0088] The amount of data associated with the remaining time of the service data unit when the DSR is triggered; the amount of data associated with the remaining time of the service data unit when the DSR MAC CE is generated; the amount of data associated with the remaining time of the service data unit when the MAC PDU containing the DSR MAC CE is assembled (also expressed as obtained or generated); and the amount of data associated with the remaining time of the service data unit when the DSR MAC CE or the MAC PDU containing the DSR MAC CE is sent. The specific determination method is described below and is not repeated here.

[0089] In some embodiments, in 202, the DSR can be reported through any signaling. For example, the UE can define a separate MAC CE (MAC Control Element media access control control element) for reporting the DSR, but is not limited to this. The DSR can also be carried by other existing signaling (for example, RRC signaling, etc.) or carried by an existing MAC CE.

[0090] In some embodiments, the remaining time of the service data unit may be calculated based on the value of a discard timer. Specifically, for the PDCP layer, the UE may calculate the remaining time of the PDCP SDU based on the value of a discard timer associated with the service data unit (PDCP SDU) of the PDCP layer. For example, when the UE's PDCP layer receives a PDCP SDU from an upper layer (e.g., an RRC layer, etc.), if the discard timer corresponding to / associated with the PDCP SDU is configured, the discard timer is started, and the remaining time of the PDCP SDU is calculated based on the value of the discard timer. For the RLC layer, the UE can calculate the remaining time of the service data unit (RLC SDU) of the RLC layer based on the value of the discard timer (discardTimer) associated with the service data unit (RLC SDU) of the RLC layer. For example, when the RLC layer of the UE receives an RLC SDU from the upper layer (such as the PDCP layer, etc.), the upper layer can notify the value of the discardTimer corresponding / associated with the RLC SDU, and the RLC layer of the UE calculates the remaining time of the RLC SDU based on the value of the discardTimer.

[0091] When the discardTimer corresponding to / associated with a PDCP SDU times out, the PDCP entity of the transmitting UE discards the PDCP SDU and the PDCP Data PDU containing the PDCP SDU, and indicates the discard to the lower layer if the corresponding PDCP data PDU has been submitted to the lower layer (e.g., RLC layer); for the RLC layer of the UE, when an instruction to discard a specific RLC SDU is given from the upper layer (e.g., PDCP), the RLC entity discards the indicated RLC SDU if the RLC SDU or a segment of the RLC SDU has not been submitted to the lower layer (e.g., MAC layer).

[0092] In some embodiments, the discardTimer may be configured by the network side, for example, the network may configure the discardTimer based on the UE's DRB (Data Radio Bearer), and the initial value or maximum value of the discardTimer may be configured by the network side. The initial value may be set to an integer greater than 0, expressed in milliseconds. The value of the discardTimer when it is activated is set to the initial value configured by the network. The value of the discard timer decreases over time after it is activated. When it decreases to 0, the discardTimer is considered to have timed out. Alternatively, the initial value of the discardTimer when it is activated is set to 0. The discardTimer increases over time after it is activated. When it reaches the maximum value configured by the network, the discardTimer is considered to have timed out.

[0093] In some embodiments, for the PDCP layer, the remaining time of its PDCP SDU is determined by the PDCP layer. For example, the PDCP layer may calculate the remaining time of the PDCP SDU based on the value of the discard timer (discardTimer) associated with the service data unit (PDCP SDU) of the PDCP layer by the PDCP layer. For example, when the PDCP of the UE receives a PDCP SDU from an upper layer (such as the RRC layer, etc.), if the discardTimer corresponding to / associated with the PDCP SDU is configured, the PDCP entity of the transmitting UE starts the discardTimer corresponding to / associated with the PDCP SDU and calculates the remaining time of the PDCP SDU based on the value of the discardTimer.

[0094] For the RLC layer, the remaining time of the RLC SDU may be indicated by an upper layer, such as the PDCP layer, but is not limited thereto and may also be indicated by other upper layers. For example, the RLC layer may calculate the remaining time of the RLC SDU based on the value of the discard timer associated with the RLC service data unit (RLC SDU), and the PDCP layer indicates the remaining time to the RLC layer. For example, when the RLC layer receives an RLC SDU from an upper layer (e.g., the PDCP layer), it receives the discardTimer value corresponding to / associated with the RLC SDU from the upper layer (e.g., the PDCP layer) and calculates the remaining time of the RLC SDU based on the discardTimer value.

[0095] In some embodiments, the data volume associated with the remaining time of a business data unit includes: the data volume of the business data unit when the remaining time of the business data unit meets a preset condition. The preset condition may include: the remaining time of the business data unit is less than or equal to a first threshold; or the remaining time of the business data unit is greater than or equal to the first threshold; or the remaining time of the business data unit is between the first threshold and the second threshold. For example, the data volume associated with the remaining time of a business data unit includes the data volume of the business data unit when the remaining time of the business data unit is less than or equal to the first threshold; or includes the data volume of the business data unit when the remaining time of the business data unit is greater than or equal to the second threshold; or includes the data volume of the business data unit when the remaining time of the business data unit is between the first threshold and the second threshold.

[0096] For example, for the PDCP layer, the data volume related to the remaining time of the service data unit may include: the data volume of the PDCP SDU when the remaining time of the PDCP SDU meets the first preset condition; wherein,

[0097] In some embodiments, the first preset condition may include: a remaining time of the PDCP SDU is less than or equal to a first threshold (a PDCP SDU for which the remaining discardTimer value is less than or equal to a first threshold), such as a case where the PDCP discardTimer decreases over time after being started;

[0098] In some embodiments, the first preset condition may include: the remaining time of the PDCP SDU is greater than or equal to a first threshold (a PDCP SDU for which the remaining discardTimer value is higher than or equal to a first threshold), for example, for the case where the PDCP discardTimer increases over time after being activated.

[0099] In some embodiments, the first preset condition may include: the remaining time of the PDCP SDU may be within a range, such as between a first threshold and a second threshold, for example, when the first threshold is greater than the second threshold, the remaining time of the PDCP SDU may be less than or equal to the first threshold and greater than or equal to the second threshold (a PDCP SDU for which the remaining discardTimer value is less than a first threshold and higher than or equal to a second threshold), and vice versa.

[0100] For example, for the RLC layer, the data volume related to the remaining time of the service data unit may include: the data volume of the RLC SDU when the remaining time of the RLC SDU meets the second preset condition.

[0101] In some embodiments, the second preset condition may include: a remaining time of the RLC SDU is less than or equal to a first threshold (a RLC SDU for which the remaining discardTimer value is less than or equal to a first threshold), such as a case where the RLC discardTimer decreases over time after being started;

[0102] In some embodiments, the second preset condition may include: the remaining time of the RLC SDU is greater than or equal to a first threshold (a RLC SDU for which the remaining discardTimer value is higher than or equal to a first threshold), for example, for the case where the RLC discardTimer increases over time after being started.

[0103] In some embodiments, the second preset condition may include: the remaining time of the RLC SDU may be within a range, such as between a first threshold and a second threshold, for example, when the first threshold is greater than the second threshold, the remaining time of the RLC SDU may be less than or equal to the first threshold and greater than or equal to the second threshold (a RLC SDU for which the remaining discardTimer value is less than a first threshold and higher than or equal to a second threshold), and vice versa.

[0104] In some embodiments, the preset condition can be set according to actual conditions. For the PDCP layer and the RLC layer, the preset condition (ie, the first preset condition and the second preset condition) can be the same or different, and will not be repeated here.

[0105] In some embodiments, the first threshold and / or the second threshold are predefined or network-configured. The second threshold may be the lower limit of a value range corresponding to an index of the remaining time of a service data unit; the first threshold may be predefined or configured based on the timing of determining the amount of data related to the remaining time of the service data unit, such as when triggering a DSR, generating a DSR MAC CE, assembling a DSR MAC PDU, or sending a DSR MAC CE. The following detailed description is given below using a specific application scenario as an example in conjunction with the accompanying drawings. The following example is applicable to the PDCP layer and / or the RLC layer.

[0106] Figure 3 is a schematic diagram of an application scenario of the information sending method according to an embodiment of the present application, showing the DSR triggering, MAC CE generation and reporting process. As shown in Figure 3, the UE obtains the remaining time of a PDU (Protocol Data Unit) or a PDU set (Protocol Data Unit set), for example, the remaining time can be determined by the value of the PDCP discardTimer, and the reference time T4 (reference time) for calculating the remaining time is the moment when the UE transmits the first symbol on the UL-SCH (uplink shared channel) or PUSCH (physical uplink shared channel) resource and / or the moment when other conditions are met. At time T1, the remaining time of the PDU or PDU set is lower than a threshold, at which time, DSR is triggered (triggering a DSR); at time T2, a DSR MAC CE is generated, and data volume information (such as the remaining time and / or the amount of data related to the remaining time) is reported through the generated DSR MAC CE; at time T3, a MAC PDU containing the DSR MAC CE is assembled, and T3 may be the same as or slightly later than T2; at time T4, the DSR MAC CE or the MAC PDU including the DSR MAC CE is sent in the UL-SCH or PUSCH resources.

[0107] 3 , the following describes how to determine the amount of data associated with the remaining time of a service data unit (PDCP SDU and / or RLC SDU).

[0108] In Example 1, as shown in FIG3 , the data amount associated with the remaining time of the service data unit includes: the data amount associated with the remaining time of the service data unit when a delay status report (DSR) is triggered (e.g., time T1);

[0109] In this case, the first threshold can be the threshold for triggering DSR for the logical channel group (LCG) configured by the network. The network configures the threshold for triggering DSR for at least one logical channel group (LCG). Each logical channel group includes at least one logical channel. For a logical channel, it includes data of PDCP SDU and / or RLC SDU, that is, it includes data of PDU (payload carrying an information unit of the application layer) or PDU set. The threshold for triggering DSR at the MAC layer is the DSR threshold of the logical channel group where the PDU or PDU set is located. Therefore, the first threshold is the threshold for triggering DSR (remaining time threshold) configured by the network for the logical channel group (LCG) where the logical channel corresponding to the service data unit is located.

[0110] Example 2, as shown in FIG3 , the data volume associated with the remaining time of the service data unit includes: the data volume associated with the remaining time of the service data unit when a Delay Status Report (DSR) MAC CE is generated.

[0111] In this case, the first threshold is the value of the remaining time of the service data unit when the DSR MAC CE is generated (such as time T2), or the first threshold is the difference between the threshold (remaining Time Threshould) for triggering DSR of each logical channel group (LCG) configured by the network and the time difference (such as T2-T1) between when DSR is triggered and when DSR MAC CE is generated, that is, the value obtained by subtracting the time difference between when DSR is triggered and when DSR MAC CE is generated from the threshold (remaining Time Threshould) for triggering DSR of each logical channel group (LCG) configured by the network.

[0112] In some embodiments, the method may further include (not shown in the figure):

[0113] For the PDCP layer, the MAC layer notifies the PDCP layer of the time when the DSR MAC CE is generated, and / or the time difference between when the DSR is triggered and when the DSR MAC CE is generated; and / or

[0114] For the RLC layer, the MAC layer and / or the PDCP layer notifies the RLC layer of the time when the DSR MAC CE is generated and / or the time difference between when the DSR is triggered and when the DSR MAC CE is generated.

[0115] In the above embodiment, the time when the DSR MAC CE is generated may be an absolute time, or may be a system frame number (SFN) and / or a slot number and / or a symbol number.

[0116] Example 3, the data volume related to the remaining time of the service data unit includes: the data volume related to the remaining time of the service data unit when the MAC PDU including the Delay Status Report (DSR) MAC CE is assembled (or obtained or generated).

[0117] In this case, the first threshold is the value of the remaining time of the service data unit when the MAC PDU including the DSR MAC CE is assembled (such as at time T3), or the first threshold is the difference between the threshold (remaining Time Threshould) for triggering DSR of each logical channel group (LCG) configured by the network and the time difference (such as T3-T1) between when DSR is triggered and when the MAC PDU including the DSR MAC CE is assembled, that is, the value obtained by subtracting the time difference between when DSR is triggered and when the MAC PDU including the DSR MAC CE is assembled from the threshold (remaining Time Threshould) for triggering DSR of each logical channel group (LCG) configured by the network.

[0118] In some embodiments, the method may further include (not shown in the figure):

[0119] For the PDCP layer, the MAC layer notifies the PDCP layer of the time when the MAC PDU including the DSR MAC CE is assembled, and / or the time difference between when the DSR is triggered and when the MAC PDU including the DSR MAC CE is assembled; and / or

[0120] For the RLC layer, the MAC layer and / or the PDCP layer notifies the RLC layer of the time when the MAC PDU including the DSR MAC CE is assembled, and / or the time difference between when the DSR is triggered and when the MAC PDU including the DSR MAC CE is assembled.

[0121] In the above embodiment, the time when the MAC PDU including the DSR MAC CE is assembled may be an absolute time, or may be a system frame number (SFN) and / or a slot number and / or a symbol number.

[0122] Example 4, as shown in Figure 3, the data amount related to the remaining time of the service data unit includes: the data amount related to the remaining time of the service data unit when the DSR MAC CE is sent, or the data amount related to the remaining time of the service data unit when the DSR MAC CE is reported, or the data amount related to the remaining time of the service data unit when the first symbol of PUSCH transmission is sent when the DSR MAC CE is sent.

[0123] In this case, the first threshold is the value of the remaining time of the service data unit when the DSR MAC CE is sent (such as time T4), or the value of the remaining time of the service data unit when the DSR MAC CE is reported, or the value of the remaining time of the service data unit when the first symbol of the PUSCH transmission is sent when the DSR MAC CE is sent, or the difference between the threshold for triggering DSR of the logical channel group configured by the network and the time difference (such as T4-T1) between when the DSR is triggered and when the DSR MAC CE is sent (that is, the value obtained by subtracting the time difference between when the DSR is triggered and when the DSR MAC CE is sent from the threshold for triggering DSR of the logical channel group configured by the network), or the difference between the threshold for triggering DSR of the logical channel group configured by the network and the time difference between when the DSR is triggered and when the DSR MAC CE is reported (that is, the threshold for triggering DSR of the logical channel group configured by the network minus the time difference between when the DSR is triggered and when the DSR MAC CE is reported). CE is reported, or the difference between the threshold for triggering DSR of the logical channel group configured by the network and the time difference between when DSR is triggered and the first symbol of PUSCH transmission when DSR MAC CE is sent (that is, the value obtained by subtracting the time difference between when DSR is triggered and the first symbol of PUSCH transmission when DSR MAC CE is sent from the threshold for triggering DSR of the logical channel group configured by the network).

[0124] In some embodiments, the method further includes (not shown in the figure): for the PDCP layer, the MAC layer notifies the PDCP layer of at least one of the following information:

[0125] The time when the DSR MAC CE is sent, or the time when the DSR MAC CE is reported, or the time when the first symbol of the PUSCH transmission in which the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is reported, or the time difference between when the DSR is triggered and when the DSR MAC CE is reported; and / or

[0126] For the RLC layer, the MAC layer and / or the PDCP layer notifies the RLC layer of at least one of the following information:

[0127] The time when the DSR MAC CE is sent, or the time when the DSR MAC CE is reported, or the time when the first symbol of the PUSCH transmission when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is reported, or the time difference between when the DSR is triggered and when the first symbol of the PUSCH transmission when the DSR MAC CE is sent.

[0128] In the above embodiments, the time when the DSR MAC CE is sent or the DSR MAC CE is reported or the time when the first symbol of the PUSCH transmission in which the DSR MAC CE is sent is transmitted may be an absolute time, or a system frame number (SFN) and / or a slot number and / or a symbol number.

[0129] In Examples 1 to 4 above, the absolute time may be, for example, Global Positioning System (GPS) time or Coordinated Universal Time (UTC, abbreviated as CUT in English, Coordinated Universal Time, abbreviated as TUC in French), etc., and is not limited here.

[0130] According to the above embodiment, the amount of data associated with the remaining time can be determined, which includes the amount of data related to the remaining time of the service data unit at the PDCP layer and / or RLC layer of the terminal device, thereby solving the problems existing in the prior art.

[0131] In some embodiments, the first threshold may be multiple, and the number of determined data volume information may be one or more, which will not be described in detail here.

[0132] In some embodiments, for the PDCP layer and the RLC layer, the values ​​of the first threshold and / or the second threshold may be the same or different.

[0133] In some embodiments, the data volume information included in the DSR MAC CE of the MAC layer indicates the data volume associated with the remaining time, including the data volume (data volume or buffer status or amount of data) on all logical channels of a logical channel group. The data volume associated with the remaining time may be at least one of the following data volumes:

[0134] (1) The amount of data on all logical channels of the logical channel group when the delay status report (DSR) is triggered;

[0135] (2) The amount of data on all logical channels of the logical channel group at or after the DSR MAC CE is generated;

[0136] (3) The amount of data on all logical channels of the logical channel group when or after the DSR MAC PDU is assembled (or obtained or generated);

[0137] (4) The amount of data on all logical channels of the logical channel group when the DSR MAC CE is sent;

[0138] (5) The amount of data on all logical channels of the logical channel group when the DSR MAC CE is reported;

[0139] (6) The amount of data on all logical channels of the logical channel group at the first symbol of the PUSCH transmission where the DSR MAC CE is sent.

[0140] In some embodiments, the amount of data on each logical channel of a logical channel group includes: the amount of data related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device mentioned above, and / or the amount of data related to the remaining time of the service data unit (RLC SDU) of the RLC layer mentioned above.

[0141] For the above (1), when DSR is triggered, the amount of data on each logical channel of the logical channel group includes: the amount of data related to the remaining time of the service data unit (PDCP SDU) when DSR is triggered, as described above, of the transmitting PDCP entity corresponding to the logical channel, and / or, the amount of data related to the remaining time of the service data unit (RLC SDU) when DSR is triggered, as described above, of the transmitting RLC entity corresponding to the logical channel. For the above (2), when or after the DSR MAC CE is generated, the amount of data on each logical channel of the logical channel group includes: the amount of data related to the remaining time of the service data unit (PDCP SDU) when DSR MAC CE is generated, as described above, of the transmitting PDCP entity corresponding to the logical channel, and / or, the amount of data related to the remaining time of the service data unit (RLC SDU) when DSR MAC CE is generated, as described above, of the transmitting RLC entity corresponding to the logical channel.

[0142] For the above (3), when or after the MAC PDU including the DSR MAC CE is assembled, the data volume on each logical channel of the logical channel group includes: the data volume of the PDCP layer related to the remaining time of the service data unit (PDCP SDU) when the MAC PDU including the DSR MAC CE is assembled at the transmitting PDCP entity corresponding to the logical channel, and / or, the data volume of the RLC layer related to the remaining time of the service data unit (RLC SDU) when the MAC PDU including the DSR MAC CE is assembled at the transmitting RLC entity corresponding to the logical channel.

[0143] For the above (4), when the DSR MAC CE is sent, the data volume on each logical channel of the logical channel group includes: the data volume of the PDCP layer related to the remaining time of the service data unit (PDCP SDU) when the DSR MAC CE is sent at the sending PDCP entity corresponding to the logical channel, and / or, the data volume of the RLC layer related to the remaining time of the service data unit (RLC SDU) when the DSR MAC CE is sent at the sending RLC entity corresponding to the logical channel.

[0144] For the above (5), when the DSR MAC CE is reported, the data volume on each logical channel of the logical channel group includes: the data volume of the PDCP layer related to the remaining time of the service data unit (PDCP SDU) when the DSR MAC CE is reported at the transmitting PDCP entity corresponding to the logical channel, and / or, the data volume of the RLC layer related to the remaining time of the service data unit (RLC SDU) when the DSR MAC CE is reported at the transmitting RLC entity corresponding to the logical channel.

[0145] For the above (6), when the first symbol of PUSCH transmission when the DSR MAC CE is sent is transmitted, the data amount on each logical channel of the logical channel group includes: the data amount of the PDCP layer related to the remaining time of the service data unit (PDCP SDU) when the first symbol of PUSCH transmission when the DSR MAC CE is sent is transmitted, and / or, the data amount of the RLC layer related to the remaining time of the service data unit (RLC SDU) when the first symbol of PUSCH transmission when the DSR MAC CE is sent is transmitted, in the transmitting RLC entity corresponding to the logical channel.

[0146] In some embodiments, for the RLC layer, determining the amount of data related to the remaining time of the RLC SDU may further include:

[0147] When data discarded by an upper layer (e.g., data discarded due to a discardTimer expiration) has not yet been included in an RLC data PDU, the amount of data associated with the remaining time of a service data unit at the RLC layer does not include the data discarded by the upper layer; and / or

[0148] When the data discarded by the upper layer is included in the RLC data PDU waiting for initial transmission, the data amount associated with the remaining time of the service data unit of the RLC layer includes the data discarded by the upper layer; and / or

[0149] When data discarded by an upper layer is already included in the RLC data PDU waiting for retransmission, the data amount of the RLC layer related to the remaining time of the service data unit includes the data discarded by the upper layer.

[0150] The upper layer may be, for example, a PDCP layer.

[0151] In some embodiments, the data discarded by the upper layer has been passed to the RLC layer. When the upper layer discards the data due to the discardTimer expiration, the upper layer indicates the discarded RLC SDU to the RLC layer. At this time, the RLC layer can perform the following processing:

[0152] For example, if the RLC SDU or segment of the RLC SDU indicated to be discarded by the upper layer has not yet been included in the RLC data PDU, or has not yet been submitted to the MAC layer and / or the physical layer, the RLC SDU or the segment of the RLC SDU is not included in the data amount related to the remaining time of the service data unit at the RLC layer.

[0153] For example, if the upper layer indicates that the discarded RLC SDU or segment of the RLC SDU has been included in the RLC data PDU waiting for initial transmission, or has been included in the RLC data PDU waiting for retransmission, or has been submitted to the MAC layer and / or the physical layer, or has been included in the MAC PDU, or has been initially transmitted or retransmitted by the MAC layer and / or the physical layer, then the RLC SDU or the segment of the RLC SDU is included in the data amount of the RLC layer related to the remaining time of the service data unit.

[0154] According to the above embodiment, the amount of data related to the remaining time of the service data unit can be determined more accurately, which solves the problems existing in the prior art. In addition, the determined amount of data can be included in the DSR and reported to the network device, which helps the network device to allocate uplink resources of appropriate size for the transmission of uplink services of the terminal device, avoiding insufficient uplink resource allocation resulting in the uplink service being unable to meet its latency requirements or avoiding excessive uplink resource allocation resulting in waste of wireless resources.

[0155] Embodiments of the second aspect

[0156] An embodiment of the present application provides an information receiving method, which is applied to the network side and corresponds to the embodiment of the first aspect. The contents different from the embodiment of the first aspect are described in detail. For the contents that are the same as the embodiment of the first aspect, reference can be made to the embodiment of the first aspect and will not be repeated here.

[0157] FIG4 is a schematic diagram of an information receiving method according to an embodiment of the present application, which is applied to a network device. As shown in FIG4 , the method includes:

[0158] 401. Receive a delay status report sent by a terminal device, where the delay status report includes data volume information, where the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0159] According to the above embodiment, the network device receives the delay status report sent by the terminal device and can obtain the data volume information contained in the DSR, that is, the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer, so that the network device can know the urgency of the cached data more accurately.

[0160] In some embodiments, the amount of data related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the amount of data related to the remaining time of the service data unit (RLC SDU) of the RLC layer are as described in the embodiment of the first aspect and are not repeated here.

[0161] In some embodiments, the data volume information included in the DSR MAC CE at the MAC layer may further include at least one of the following information:

[0162] (1) The amount of data on all logical channels of the logical channel group when the delay status report is triggered;

[0163] (2) The amount of data on all logical channels of the logical channel group at or after the DSR MAC CE is generated;

[0164] (3) The amount of data on all logical channels of the logical channel group when or after the DSR MAC PDU is assembled (or obtained or generated);

[0165] (4) The amount of data on all logical channels of the logical channel group when the DSR MAC CE is sent;

[0166] (5) The amount of data on all logical channels of the logical channel group when the first symbol of the PUSCH transmission is sent with DSR.

[0167] The above data volume information is as described in the embodiment of the first aspect, and its content is merged here and will not be repeated here.

[0168] In some embodiments, for the RLC layer, the data amount related to the remaining time of the RLC SDU may further include:

[0169] When data discarded by an upper layer (e.g., data discarded due to a discardTimer expiration) is not yet included in an RLC data PDU, the amount of data associated with the remaining time of a service data unit at the RLC layer does not include the data discarded by the upper layer; and / or

[0170] When data discarded by an upper layer is already included in an RLC data PDU waiting for initial transmission or retransmission, the data amount of the RLC layer related to the remaining time of the service data unit includes the data discarded by the upper layer.

[0171] In some embodiments, the method further includes (not shown in the figure): configuring a first threshold and / or a second threshold for the terminal device, and notifying the terminal device of the determined threshold. The first threshold and the second threshold are as described in the embodiment of the first aspect and are not further described here.

[0172] According to the above embodiment, the network device receives the delay status report sent by the terminal device and can obtain the data volume information contained in the DSR, that is, the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer, so that the network device can know the urgency of the cached data more accurately, and then allocate appropriate uplink resources to transmit data with urgent delays to ensure the delay requirements of the service.

[0173] Embodiments of the third aspect

[0174] Currently, 3GPP has agreed to define a separate MAC CE for reporting Delay Status Reports (DSRs). The inventors have discovered that under certain conditions, a triggered DSR can trigger a Scheduling Request (SR). However, it is unclear under what circumstances the SR is canceled.

[0175] To solve the above problems, the present application provides an information processing method applied to a terminal device.

[0176] FIG5 is a schematic diagram of an information processing method according to an embodiment of the present application. As shown in FIG5 , the information processing method includes:

[0177] 501, triggering a Delay Status Report (DSR);

[0178] 502, triggering a scheduling request (SR);

[0179] 503: Cancel the scheduling request.

[0180] In some embodiments, in 501, the triggered delay status report (DSR) may be the same as the delay status report (DSR) triggered in the embodiment of the first aspect of the present application, or may be different, and the present application is not limited thereto.

[0181] In some embodiments, in 502, the process of triggering a scheduling request may be, for example, that the terminal device has no available uplink resources to send the triggered DSR, or the available uplink resources cannot accommodate the DSR MAC CE plus its sub-header, or the available uplink resources are later than the delay requirement of the uplink service, etc. The terminal device will trigger a scheduling request and send a scheduling request to the network device in the PUCCH, requesting the network device to send a UL grant to allocate uplink resources, so that the terminal device can report the delay status report through the uplink resources indicated by the UL grant.

[0182] In some embodiments, in 503, the scheduling request is canceled in at least one of the following circumstances:

[0183] (1) A MAC PDU is sent and includes a DSR MAC CE, which contains the data amount and / or the remaining time of the latest DSR-triggering event before the MAC PDU is assembled, or the DSR MAC CE contains the data amount and / or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled;

[0184] (2) The uplink grant (UL grant) can accommodate all the waiting data to be sent;

[0185] (3) All triggered Delay Status Reports (DSRs) are canceled;

[0186] (4) The Delay Status Report (DSR) that triggered the Scheduling Request (SR) is cancelled.

[0187] In some embodiments, the event triggering DSR in (1) above is, for example, based on a threshold triggering DSR, as described in the embodiment of the first aspect, which will not be described in detail here; or, it may be other events triggering DSR. The data volume of the event triggering DSR may be the data volume described in the embodiment of the first aspect of the present application, or, it may be other data volumes, which are not limited by the present application.

[0188] In the above embodiment, the manner of canceling the scheduling request triggered by the DSR in the above situations (1) to (4) can be described as follows:

[0189] According to the above embodiment, it is clarified when the scheduling request (SR) triggered by the delay status report (DSR) is canceled, thereby reducing the sending of unnecessary SRs. In addition, the resources occupied by SR sending can be saved, the UE power consumption can be reduced, and electricity can be saved, thereby solving the problems existing in the prior art.

[0190] Embodiments of the fourth aspect

[0191] Currently, 3GPP has agreed to define a separate MAC CE for reporting Delay Status Reports (DSRs). The inventors have discovered that, under certain conditions, a triggered DSR can trigger a Scheduling Request (SR). If no valid PUCCH resources are configured for the SR, the UE initiates a random access procedure and cancels the SR. It is currently unclear under what circumstances the random access procedure is terminated.

[0192] To solve the above problems, the present application provides an information processing method applied to a terminal device.

[0193] FIG6 is a schematic diagram of an information processing method according to an embodiment of the present application. As shown in FIG6 , the method includes:

[0194] 601, triggering a Delay Status Report (DSR);

[0195] 602, triggering a scheduling request (SR);

[0196] 603, initiating a random access procedure related to the scheduling request;

[0197] 604. Stop the random access process.

[0198] In some embodiments, in 601, the triggered delay status report (DSR) may be the same as or different from the delay status report (DSR) triggered in the embodiment of the first aspect of the present application, and the present application is not limited thereto.

[0199] In some embodiments, in 602, the process of triggering the scheduling request can refer to the embodiment of the third aspect and will not be repeated here.

[0200] In some embodiments, in 603, initiating a random access procedure related to a scheduling request may be implemented with reference to an existing method for initiating a random access procedure. For example, the random access procedure in TSs 38.321 may be specifically referred to, as described below:

[0201] As long as at least one SR is in the pending state, the MAC entity shall, for each SR in the pending state:

[0202] 1> If the MAC entity does not configure valid PUCCH resources for the SR in this waiting state:

[0203] 2> Initiate a random access procedure on the SpCell (see Section 5.1) and cancel the SR in the waiting state.

[0204] (As long as at least one SR is pending, the MAC entity shall for each pending SR:

[0205] 1>if the MAC entity has no valid PUCCH resource configured for the pending SR:

[0206] 2>initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR.)

[0207] In some embodiments, in 604, the random access procedure is stopped in at least one of the following situations:

[0208] (1) A MAC PDU is sent and includes a DSR MAC CE, wherein the DSR MAC CE includes the data volume and / or the remaining time of the latest DSR-triggering event before the MAC PDU is assembled, or the data volume and / or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled;

[0209] (2) The uplink grant (UL grant) can accommodate all the waiting data to be sent;

[0210] (3) All triggered Delay Status Reports (DSRs) are canceled;

[0211] (4) The Delay Status Report (DSR) that triggered the Scheduling Request (SR) is cancelled.

[0212] In some embodiments, the event triggering DSR in (1) above is, for example, based on a threshold triggering DSR, as described in the embodiment of the first aspect, which will not be described in detail here; or, it may be other events triggering DSR. The data volume of the event triggering DSR may be the data volume described in the embodiment of the first aspect of the present application, or, it may be other data volumes, which are not limited by the present application.

[0213] In the above embodiment, the manner of stopping the random access process related to the scheduling request in the above situations (1) to (4) can be described as follows:

[0214] According to the above embodiment, it is clarified when the random access process related to the scheduling request (SR) triggered by the delay status report (DSR) is stopped, which can reduce the sending of unnecessary random access-related messages, save wireless resources, reduce UE power consumption and save electricity, thereby solving the problems existing in the prior art.

[0215] Embodiments of the fifth aspect

[0216] Currently, both the Buffer Status Report (BSR) and the Data Status Report (DSR) include data volume, buffer size, or amount of data. The inventors have discovered that it is unclear whether the BSR and DSR can be included in the same MAC PDU.

[0217] To solve the above problems, the present application provides an information processing method applied to a terminal device.

[0218] FIG7 is a schematic diagram of an information processing method according to an embodiment of the present application. As shown in FIG7 , the method includes:

[0219] 701, generate MAC PDU;

[0220] The MAC PDU includes a Delay Status Report (DSR) and / or a Buffer Status Report (BSR).

[0221] In some embodiments, in 701, the triggered delay status report (DSR) may be the same as or different from the delay status report (DSR) triggered in the embodiment of the first aspect of the present application, and the present application is not limited thereto.

[0222] In some embodiments, the DSR and the BSR are not included in the same MAC PDU, in which case the MAC PDU includes one of a Delay Status Report (DSR) and a Buffer Status Report (BSR).

[0223] In some embodiments, when both a Delay Status Report (DSR) and a Buffer Status Report (BSR) are triggered, the MAC PDU determines which of the DSR and the BSR is included based on the DSR priority and the BSR priority. For example, the one with the higher priority between the DSR and the BSR is included in the MAC PDU. The DSR priority and the BSR priority can be preconfigured or defined. For example, if the DSR priority and the BSR priority are predefined, the Delay Status Report (DSR) has a higher priority than a regular BSR, a periodic BSR, or a padding BSR; or, the Delay Status Report (DSR) has a lower priority than a regular BSR but higher than a periodic BSR or a padding BSR. For another example, if the DSR priority and the BSR priority are configured by a network device, network signaling can indicate the DSR priority and the BSR priority in an RRC message, or indicate that the DSR priority is higher than the BSR priority, or that the BSR priority is higher than the DSR priority, etc.

[0224] In this way, repeated reporting of data volume (data volume, buffer size, or amount of data) information can be reduced, thereby improving wireless resource utilization.

[0225] In some embodiments, the DSR and the BSR may be included in the same MAC PDU. In this case, the MAC PDU may include both the Delay Status Report (DSR) and the Buffer Status Report (BSR).

[0226] For example, when both a Delay Status Report (DSR) and a Buffer Status Report (BSR) are triggered, the DSR and the BSR are included in the same MAC PDU.

[0227] Therefore, the BSR and DSR processes are performed independently without affecting each other, and the implementation is simple.

[0228] Embodiments of the sixth aspect

[0229] An embodiment of the present application provides an information sending device, which is applied to a terminal device. FIG8 is a schematic diagram of the information receiving device. The information receiving device and the information receiving method in the embodiment of the first aspect provided by the present application are based on the same inventive concept and have similar principles for solving problems. Therefore, for the implementation of the information receiving device, please refer to the implementation of the information receiving method in the embodiment of the first aspect provided by the present application, and the repeated parts will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceivable.

[0230] As shown in FIG8 , the information receiving device includes:

[0231] A first triggering unit 801 is configured to trigger a delay status report;

[0232] A sending unit 802 is used to send the delay status report to the network device, where the delay status report includes data volume information, and the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0233] According to the above embodiment, it is clarified how to determine the amount of data associated with the remaining time, that is, the amount of data includes the amount of data related to the remaining time of the service data unit of the PDCP layer and / or RLC layer of the terminal device, thereby solving the problems existing in the prior art.

[0234] In some embodiments, the manner in which the terminal device triggers a delay status report is as described in the embodiment of the first aspect and will not be repeated here.

[0235] In some embodiments, the amount of data related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the amount of data related to the remaining time of the service data unit (RLC SDU) of the RLC layer are as described in the embodiment of the first aspect and are not repeated here.

[0236] In some embodiments, for the PDCP layer, the MAC layer notifies the PDCP layer of at least one of the following information:

[0237] The time when the DSR MAC CE is sent, or the time when the DSR MAC CE is reported, or the time when the first symbol of the PUSCH transmission in which the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is reported, or the time difference between when the DSR is triggered and when the DSR MAC CE is reported; and / or

[0238] For the RLC layer, the MAC layer and / or the PDCP layer notifies the RLC layer of at least one of the following information:

[0239] The time when the DSR MAC CE is sent, or the time when the DSR MAC CE is reported, or the time when the first symbol of the PUSCH transmission when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is reported, or the time difference between when the DSR is triggered and when the first symbol of the PUSCH transmission when the DSR MAC CE is sent.

[0240] In the above embodiments, the time when the DSR MAC CE is sent or the DSR MAC CE is reported or the time when the first symbol of the PUSCH transmission in which the DSR MAC CE is sent is transmitted may be an absolute time, or a system frame number (SFN) and / or a slot number and / or a symbol number.

[0241] In some embodiments, the data volume information included in the DSR MAC CE of the MAC layer indicates the data volume associated with the remaining time, including the data volume (data volume, buffer status, or amount of data) on all logical channels of a logical channel group. The data volume associated with the remaining time includes at least one of the following information:

[0242] The amount of data on all logical channels of the logical channel group when the delay status report is triggered;

[0243] The amount of data on all logical channels of the logical channel group at or after the DSR MAC CE is generated;

[0244] The amount of data on all logical channels of the logical channel group at the time when or after the DSR MAC PDU is assembled (or obtained or generated);

[0245] The amount of data on all logical channels of the logical channel group when the DSR MAC CE is sent;

[0246] The amount of data on all logical channels of the logical channel group at the first symbol of the PUSCH transmission where DSR is sent.

[0247] In some embodiments, for the RLC layer, the amount of data related to the remaining time of the RLC RDU may also include:

[0248] When data discarded by an upper layer (e.g., data discarded due to a discardTimer expiration) has not yet been included in an RLC data PDU, the amount of data associated with the remaining time of a service data unit at the RLC layer does not include the data discarded by the upper layer; and / or

[0249] When data discarded by an upper layer is already included in an RLC data PDU waiting for initial transmission or retransmission, the data amount of the RLC layer related to the remaining time of the service data unit includes the data discarded by the upper layer.

[0250] According to the above embodiment, it is clarified how to determine the amount of data associated with the remaining time, that is, the amount of data includes the amount of data related to the remaining time of the service data unit of the PDCP layer and / or RLC layer of the terminal device, thereby solving the problems existing in the prior art.

[0251] The embodiment of the present application also provides an information receiving device, and Figure 9 is a schematic diagram of the information receiving device. The information receiving device and the information receiving method in the embodiment of the second aspect provided by the present application are produced based on the same inventive concept, and the principles of solving the problem are similar. Therefore, the implementation of the information receiving device refers to the implementation of the information receiving method in the embodiment of the second aspect provided by the present application, and the repeated parts are not repeated here. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceived.

[0252] As shown in FIG9 , the information receiving device includes:

[0253] A receiving unit 901 is used to receive a delay status report sent by a terminal device, wherein the delay status report includes data volume information, and the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0254] According to the above embodiment, the network device receives the delay status report sent by the terminal device and can obtain the data volume information contained in the DSR, that is, the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer. This enables the network device to know the urgency of the cached data more accurately, and then allocate appropriate uplink resources to transmit data with urgent delays to ensure the delay requirements of the service.

[0255] In some embodiments, the amount of data related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the amount of data related to the remaining time of the service data unit (RLC SDU) of the RLC layer are as described in the embodiment of the first aspect and are not repeated here.

[0256] In some embodiments, the data volume information included in the DSR MAC CE of the MAC layer indicates the data volume associated with the remaining time, including the data volume (data volume, buffer status, or amount of data) on all logical channels of a logical channel group. The data volume associated with the remaining time includes at least one of the following information:

[0257] (1) The amount of data on all logical channels of the logical channel group when the delay status report is triggered;

[0258] (2) The amount of data on all logical channels of the logical channel group at or after the DSR MAC CE is generated;

[0259] (3) The amount of data on all logical channels of the logical channel group when or after the DSR MAC PDU is assembled (or obtained or generated);

[0260] (4) The amount of data on all logical channels of the logical channel group when the DSR MAC CE is sent;

[0261] (5) The amount of data on all logical channels of the logical channel group when the first symbol of the PUSCH transmission is sent with DSR.

[0262] In some embodiments, for the RLC layer, the amount of data related to the remaining time of the RLC RDU may also include:

[0263] When data discarded by an upper layer (e.g., data discarded due to a discardTimer expiration) is not yet included in an RLC data PDU, the amount of data associated with the remaining time of a service data unit at the RLC layer does not include the data discarded by the upper layer; and / or

[0264] When data discarded by an upper layer is already included in an RLC data PDU waiting for initial transmission or retransmission, the data amount of the RLC layer related to the remaining time of the service data unit includes the data discarded by the upper layer.

[0265] In some embodiments, the apparatus further includes a configuration unit (not shown) configured to configure a first threshold value and / or a second threshold value for a terminal device and notify the terminal device of the determined threshold value. The first threshold value and the second threshold value are as described in the embodiment of the first aspect and are not further described here.

[0266] According to the above embodiment, the network device receives the delay status report sent by the terminal device and can obtain the data volume information contained in the DSR, that is, the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer. This enables the network device to know the urgency of the cached data more accurately, and then allocate appropriate uplink resources to transmit data with urgent delays to ensure the delay requirements of the service.

[0267] The embodiment of the present application also provides an information receiving device, which is applied to a terminal device. Figure 10 is a schematic diagram of the information processing device. The information processing device and the information processing method in the embodiment of the third aspect provided by the present application are based on the same inventive concept and have similar principles for solving problems. Therefore, for the implementation of the information processing device, please refer to the implementation of the information processing method in the embodiment of the third aspect provided by the present application, and the repetitions will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0268] As shown in FIG10 , the information processing device includes:

[0269] A second triggering unit 1001 is configured to trigger a delay status report;

[0270] A third triggering unit 1002, configured to trigger a scheduling request;

[0271] The first processing unit 1003 is configured to cancel the scheduling request.

[0272] In some embodiments, the delay status report (DSR) triggered by the second trigger unit 1001 may be the same as or different from the delay status report (DSR) triggered in the embodiment of the first aspect of the present application, and the present application is not limited thereto.

[0273] In some embodiments, the process of the third triggering unit 1002 triggering the scheduling request can be implemented with reference to the prior art.

[0274] In some embodiments, the first processing unit 1003 cancels the scheduling request in at least one of the following situations:

[0275] (1) A MAC PDU is sent and includes a DSR MAC CE, which contains the data amount and / or the remaining time of the latest DSR-triggering event before the MAC PDU is assembled, or the DSR MAC CE contains the data amount and / or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled;

[0276] (2) The uplink grant (UL grant) can accommodate all the waiting data to be sent;

[0277] (3) All triggered Delay Status Reports (DSRs) are canceled;

[0278] (4) The Delay Status Report (DSR) that triggered the Scheduling Request (SR) is cancelled.

[0279] In some embodiments, the event triggering DSR in (1) above is, for example, based on a threshold triggering DSR, as described in the embodiment of the first aspect, which will not be described in detail here; or, it may be other events triggering DSR. The data volume of the event triggering DSR may be the data volume described in the embodiment of the first aspect of the present application, or, it may be other data volumes, which are not limited by the present application.

[0280] According to the above embodiment, it is clarified when the scheduling request (SR) triggered by the delay status report (DSR) is canceled, which can reduce the sending of unnecessary SRs, save the resources occupied by SR sending, reduce UE power consumption and save electricity, thereby solving the problems existing in the prior art.

[0281] The embodiment of the present application also provides an information receiving device, which is applied to a terminal device. Figure 11 is a schematic diagram of the information processing device. The information processing device and the information processing method in the embodiment of the fourth aspect provided by the present application are based on the same inventive concept and have similar principles for solving problems. Therefore, for the implementation of the information processing device, please refer to the implementation of the information processing method in the embodiment of the fourth aspect provided by the present application, and the repetitions will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0282] As shown in FIG11 , the method includes:

[0283] A fourth triggering unit 1101 is configured to trigger a delay status report;

[0284] a fifth triggering unit 1102, configured to trigger a scheduling request;

[0285] A sixth triggering unit 1103 is configured to initiate a random access procedure related to a scheduling request;

[0286] The second processing unit 1104 is configured to stop the random access procedure.

[0287] In some embodiments, the delay status report (DSR) triggered by the fourth trigger unit 1101 may be the same as the delay status report (DSR) triggered in the embodiment of the first aspect of the present application, or may be different, and the present application is not limited thereto.

[0288] In some embodiments, the process of the fifth trigger unit 1102 triggering the scheduling request may be, for example, that the terminal device has no available uplink resources to send the triggered DSR, or the available uplink resources cannot accommodate the DSR MAC CE plus its sub-header, or the available uplink resources are later than the delay requirement of the uplink service, etc. The terminal device will trigger the scheduling request and send a scheduling request to the network device in the PUCCH, requesting the network device to send a UL grant to allocate uplink resources, so that the terminal device can report the delay status report through the uplink resources indicated by the UL grant.

[0289] In some embodiments, the sixth triggering unit 1103 may initiate a random access procedure related to a scheduling request by referring to an existing method for initiating a random access procedure.

[0290] In some embodiments, the second processing unit 1104 stops the random access procedure in at least one of the following situations:

[0291] (1) A MAC PDU is sent and includes a DSR MAC CE, wherein the DSR MAC CE includes the data volume and / or the remaining time of the latest DSR-triggering event before the MAC PDU is assembled, or the data volume and / or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled;

[0292] (2) The uplink grant (UL grant) can accommodate all the waiting data to be sent;

[0293] (3) All triggered Delay Status Reports (DSRs) are canceled;

[0294] (4) The Delay Status Report (DSR) that triggered the Scheduling Request (SR) is cancelled.

[0295] In some embodiments, the event triggering DSR in (1) above is, for example, based on a threshold triggering DSR, as described in the embodiment of the first aspect, which will not be described in detail here; or, it may be other events triggering DSR. The data volume of the event triggering DSR may be the data volume described in the embodiment of the first aspect of the present application, or, it may be other data volumes, which are not limited by the present application.

[0296] According to the above embodiment, it is clarified when the random access process related to the scheduling request (SR) triggered by the delay status report (DSR) is stopped, which can reduce the sending of unnecessary random access-related messages, save wireless resources, reduce UE power consumption and save electricity, thereby solving the problems existing in the prior art.

[0297] The embodiment of the present application also provides an information receiving device, which is applied to a terminal device. Figure 12 is a schematic diagram of the information processing device. The information processing device and the information processing method in the embodiment of the fifth aspect provided by the present application are based on the same inventive concept and have similar principles for solving problems. Therefore, for the implementation of the information processing device, please refer to the implementation of the information processing method in the embodiment of the fifth aspect provided by the present application, and the repetitions will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0298] As shown in FIG12 , the device includes:

[0299] The third processing unit 1201 generates a MAC PDU;

[0300] The MAC PDU includes a Delay Status Report (DSR) and / or a Buffer Status Report (BSR).

[0301] In some embodiments, the delay status report (DSR) triggered by the third processing unit 1201 may be the same as the delay status report (DSR) triggered in the embodiment of the first aspect of the present application, or may be different. The present application is not limited to this.

[0302] In some embodiments, the DSR and the BSR cannot be included in the same MAC PDU. In this case, the MAC PDU includes at most one of the Delay Status Report (DSR) and the Buffer Status Report (BSR).

[0303] In some embodiments, when both a Delay Status Report (DSR) and a Buffer Status Report (BSR) are triggered, the MAC PDU determines which of the DSR and BSR is included based on the DSR priority and the BSR priority. For example, the one with the higher priority between the DSR and BSR is included in the MAC PDU. The DSR priority and the BSR priority can be preconfigured or defined. For example, if the DSR priority and the BSR priority are predefined, the Delay Status Report (DSR) has a higher priority than a regular BSR, a periodic BSR, or a padding BSR; or, the Delay Status Report (DSR) has a lower priority than a regular BSR but higher than a periodic BSR or a padding BSR. For another example, if the DSR priority and the BSR priority are configured by a network device, network signaling can indicate the DSR priority and the BSR priority in an RRC message, or indicate that the DSR priority is higher than the BSR priority, or that the BSR priority is higher than the DSR priority, etc.

[0304] In this way, repeated reporting of data volume (data volume, buffer size, or amount of data) information can be reduced, thereby improving wireless resource utilization.

[0305] In some embodiments, the DSR and BSR can be included in the same MAC PDU. In this case, the MAC PDU can include both a Delay Status Report (DSR) and a Buffer Status Report (BSR). For example, when both a Delay Status Report (DSR) and a Buffer Status Report (BSR) are triggered, the DSR and BSR are included in the same MAC PDU. This allows the BSR and DSR processes to proceed independently without affecting each other, simplifying implementation.

[0306] Embodiments of the seventh aspect

[0307] An embodiment of the present application also provides a communication system, and reference may be made to FIG1 . The contents identical to those in the first to fifth aspects of the embodiments will not be repeated.

[0308] In some embodiments, the communication system 100 may include at least: a network device 101 and / or a terminal device 102, wherein the terminal device 102 triggers a delay status report and sends the delay status report to the network device 101; and the network device 101 receives the delay status report sent by the terminal device 102. The delay status report includes data volume information, wherein the data volume information includes a data volume related to a remaining time of a service data unit (PDCP SDU) of a PDCP layer of the terminal device and / or a data volume related to a remaining time of a service data unit (RLC SDU) of an RLC layer.

[0309] In some embodiments, the implementation of the above-mentioned delay status report can refer to the embodiments of the first aspect and the second aspect, and will not be repeated here.

[0310] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0311] Figure 13 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 13 , network device 1300 may include a processor 1310 (e.g., a central processing unit (CPU)) and a memory 1320. Memory 1320 is coupled to processor 1310. Memory 1320 may store various data and may also store an information processing program 1330, which is executed under the control of processor 1310.

[0312] For example, the processor 1310 may be configured to execute a program to implement the information receiving method as described in the embodiment of the second aspect. For example, the processor 1310 may be configured to perform the following control: receiving a delay status report sent by a terminal device, the delay status report including data volume information, the data volume information including the data volume related to the remaining time of a service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of a service data unit (RLC SDU) of the RLC layer.

[0313] In addition, as shown in FIG13 , network device 1300 may further include: a transceiver 1340 and an antenna 1350, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1300 does not necessarily include all the components shown in FIG13 ; in addition, network device 1300 may also include components not shown in FIG13 , and reference may be made to the prior art for details.

[0314] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0315] Figure 14 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 14 , terminal device 1400 may include a processor 1410 and a memory 1420. Memory 1420 stores data and programs and is coupled to processor 1410. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0316] For example, the processor 1410 may be configured to execute a program to implement the information sending method as described in the embodiment of the first aspect. For example, the processor 1410 may be configured to perform the following control: triggering a delay status report; sending the delay status report to a network device, wherein the delay status report includes data volume information, wherein the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

[0317] As shown in Figure 14 , the terminal device 1400 may further include: a communication module 1430, an input unit 1440, a display 1450, and a power supply 1460. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1400 does not necessarily include all of the components shown in Figure 14 , and these components are not essential. Furthermore, the terminal device 1400 may also include components not shown in Figure 14 , for which reference may be made to the prior art.

[0318] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the information sending method described in the embodiment of the first aspect.

[0319] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the information sending method described in the embodiment of the first aspect.

[0320] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the information receiving method described in the embodiment of the second aspect.

[0321] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the information receiving method described in the embodiment of the second aspect.

[0322] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0323] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0324] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0325] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0326] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0327] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0328] 1. An information processing method, applied to a terminal device, wherein the method comprises:

[0329] Triggering a delayed status report;

[0330] Triggering a scheduling request;

[0331] Initiate a random access procedure associated with a scheduling request;

[0332] Stop the random access procedure.

[0333] 2. The method according to Note 1, wherein the random access procedure is stopped in at least one of the following situations:

[0334] A MAC PDU is sent and includes a DSR MAC CE, wherein the DSR MAC CE includes the data amount and / or the remaining time of the latest DSR-triggering event before the MAC PDU is assembled, or the data amount and / or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled;

[0335] The UL grant can accommodate all the waiting data to be sent;

[0336] All triggered deferred status reports are canceled;

[0337] The delay status report that triggered the scheduling request is cancelled.

[0338] 3. An information processing method, applied to a terminal device, wherein the method comprises:

[0339] Generate MAC PDU;

[0340] The MAC PDU includes a Delay Status Report (DSR) and / or a Buffer Status Report (BSR).

[0341] 4. The method according to Note 3, wherein the MAC PDU includes one of a Delay Status Report (DSR) and a Buffer Status Report (BSR).

[0342] 5. The method according to Note 4, wherein when both the delay status report and the cache status report are triggered,

[0343] The Delay Status Report (DSR) has a higher priority than a regular BSR or a periodic BSR or a padding BSR; or

[0344] The priority of the Delay Status Report (DSR) is lower than that of the regular BSR, but higher than that of the periodic BSR or the padding BSR.

Claims

1. An information sending device, applied to a terminal device, wherein: The device comprises: A first triggering unit, which is used to trigger a delay status report; A sending unit, which is used to send the delay status report to the network device, wherein the delay status report includes data volume information, and the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

2. The device according to claim 1, wherein: For the RLC layer, the remaining time of the service data unit is indicated by the upper layer.

3. The device according to claim 1, wherein: The data volume related to the remaining time of the service data unit includes: the data volume of the service data unit when the remaining time of the service data unit meets a preset condition.

4. The device according to claim 3, wherein: The preset condition includes: the remaining time of the service data unit is less than or equal to the first threshold; or The remaining time of the service data unit is greater than or equal to the first threshold; or The remaining time of the service data unit is between a first threshold and a second threshold.

5. The device according to claim 3, wherein: The first threshold and / or the second threshold are predefined or network configured.

6. The device according to claim 3, wherein: The data volume related to the remaining time of the service data unit includes: the data volume related to the remaining time of the service data unit when the delay status report is triggered.

7. The device according to claim 6, wherein: The first threshold is a threshold for triggering DSR by a logical channel group (LCG) configured by the network.

8. The device according to claim 3, wherein: The data volume associated with the remaining time of the service data unit includes: the data volume associated with the remaining time of the service data unit when a Delay Status Report (DSR) MAC CE is generated.

9. The device according to claim 8, wherein: The first threshold is the value of the remaining time when the DSR MAC CE is generated, or the difference between the threshold of the logical channel group (LCG) configured by the network to trigger the DSR and the time difference between when the DSR is triggered and when the DSR MAC CE is generated.

10. The device according to claim 8, wherein: For the PDCP layer, the MAC layer notifies the PDCP layer of the absolute time when the DSR MAC CE is generated, or the absolute time when the MAC PDU containing the DSR MAC CE is assembled, or the time difference between when the DSR is triggered and when the DSR MAC CE is generated, or the time difference between when the DSR is triggered and when the MAC PDU is assembled; and / or For the RLC layer, the MAC layer and / or the PDCP layer notifies the RLC layer of the absolute time when the DSR MAC CE is generated, or the absolute time when the MAC PDU containing the DSR MAC CE is assembled, or the time difference between when the DSR is triggered and when the DSR MAC CE is generated, or the time difference between when the DSR is triggered and when the MAC PDU is assembled.

11. The device according to claim 2, wherein: The data volume associated with the remaining time of the service data unit includes: the data volume associated with the remaining time of the service data unit when the DSR MAC CE is sent.

12. The device according to claim 11, wherein The first threshold is the value of the remaining time when the DSR MAC CE is sent, or the value of the remaining time when the DSR MAC CE is reported, or the value of the remaining time when the first symbol of PUSCH transmission is sent when the DSR MAC CE is sent, or the difference between the threshold of the logical channel group configured by the network to trigger DSR and the time difference between when the DSR is triggered and when the DSR MAC CE is sent, or the difference between the threshold of the logical channel group configured by the network to trigger DSR and the time difference between when the DSR is triggered and when the DSR MAC CE is reported, or the difference between the threshold of the logical channel group configured by the network to trigger DSR and the time difference between when the DSR is triggered and when the DSR MAC CE is sent.

13. The device according to claim 12, wherein: For the PDCP layer, the MAC layer notifies the PDCP layer of at least one of the following information: the absolute time when the DSR MAC CE is sent, or the absolute time when the DSR MAC CE is reported, or the absolute time when the first symbol of the PUSCH transmission when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is reported, or the time difference between when the DSR is triggered and when the first symbol of the PUSCH transmission when the DSR MAC CE is sent; and / or For the RLC layer, the MAC layer and / or the PDCP layer informs the RLC layer of at least one of the following information: The absolute time when the DSR MAC CE is sent, or the absolute time when the DSR MAC CE is reported, or the absolute time when the first symbol of the PUSCH transmission when the DSR MAC CE is sent, or the time difference between when the DSR is triggered and when the DSR MAC CE is sent, or the absolute time between when the DSR is triggered and when the DSR MAC CE is sent. The time difference between when DSR is reported or when the first symbol of PUSCH transmission is sent and when DSR MAC CE is triggered.

14. The device according to claim 4, wherein: The second threshold is the lower limit of the value range corresponding to the index of the remaining time of the service data unit.

15. The device according to claim 2, wherein: The number of the first thresholds is at least one, and the number of the data volume information is also at least one.

16. The device according to claim 1, wherein The data volume information included in the DSR MAC CE of the MAC layer is used to indicate at least one of the following information: The amount of data on all logical channels of the logical channel group when the delay status report is triggered; The amount of data on all logical channels of the logical channel group when or after the DSR MAC CE is generated; The amount of data on all logical channels of the logical channel group when or after the DSR MAC PDU is assembled; The amount of data on all logical channels of the logical channel group when the DSR MAC CE is sent; The amount of data on all logical channels of the logical channel group at the first symbol of PUSCH transmission where DSR is sent.

17. The device according to claim 1, wherein: For the RLC layer, when the data discarded by the upper layer is not yet included in the RLC data PDU, the amount of data related to the remaining time of the service data unit of the RLC layer does not include the data discarded by the upper layer; and / or When the data discarded by the upper layer is already included in the RLC data PDU waiting for initial transmission or retransmission, the data amount of the RLC layer related to the remaining time of the service data unit includes the data discarded by the upper layer.

18. An information receiving device, applied to a network device, wherein: The device comprises: A receiving unit, which is used to receive a delay status report sent by a terminal device, wherein the delay status report includes data volume information, and the data volume information includes the data volume related to the remaining time of the service data unit (PDCP SDU) of the PDCP layer of the terminal device and / or the data volume related to the remaining time of the service data unit (RLC SDU) of the RLC layer.

19. An information processing device, applied to a terminal device, wherein: The device comprises: A second triggering unit, which is used to trigger a delay status report; A third triggering unit, which is used to trigger a scheduling request; A first processing unit is configured to cancel the scheduling request.

20. The device according to claim 19, wherein The scheduling request is canceled in at least one of the following cases: A MAC PDU is sent and the MAC PDU includes a DSR MAC CE, the DSR MAC CE including the data amount and / or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled, or the data amount and / or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled; The UL grant can accommodate all the waiting data to be sent; All triggered delayed status reports are canceled; The delay status report that triggered the scheduling request is cancelled.

Images