WO2025065632A1 - 一种信息发送、接收和处理方法、装置、通信系统 - Google Patents

一种信息发送、接收和处理方法、装置、通信系统 Download PDF

Info

Publication number
WO2025065632A1
WO2025065632A1 PCT/CN2023/122926 CN2023122926W WO2025065632A1 WO 2025065632 A1 WO2025065632 A1 WO 2025065632A1 CN 2023122926 W CN2023122926 W CN 2023122926W WO 2025065632 A1 WO2025065632 A1 WO 2025065632A1
Authority
WO
WIPO (PCT)
Prior art keywords
dsr
mac
data
remaining time
layer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/122926
Other languages
English (en)
French (fr)
Inventor
李国荣
易粟
张磊
王昕�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to CN202380102038.7A priority Critical patent/CN121866806A/zh
Priority to PCT/CN2023/122926 priority patent/WO2025065632A1/zh
Publication of WO2025065632A1 publication Critical patent/WO2025065632A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the embodiments of the present application relate to the field of communication technologies.
  • XR services refer to all real and virtual environments, as well as human-computer interactions generated by computer technology and wearable devices.
  • XR services can include virtual reality (VR), augmented reality (AR) and mixed reality (MR).
  • VR virtual reality
  • AR augmented reality
  • MR mixed reality
  • a scheduler with latency information is beneficial in order to meet their Quality of Service (QoS).
  • QoS Quality of Service
  • a scheduler with latency information is feasible in the downlink because the network side (e.g., gNB) knows the UE QoS characteristics (e.g., through 5G QoS parameters such as 5G QoS Identifier (5QI)) and also knows when the XR frames (packets) arrive, and therefore also knows the urgency of the data to schedule the buffer.
  • 5G QoS parameters such as 5G QoS Identifier (5QI)
  • BSR buffer status reporting
  • 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.
  • embodiments of the present application provide a method, device, and communication system for sending, receiving, and processing information.
  • an information sending method which is applied to a terminal device, wherein the method includes:
  • the delay status report is sent to the network device, and 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.
  • PDCP SDU the remaining time of the service data unit
  • RLC SDU the remaining time of the service data unit
  • an information receiving method which is applied to a network device, wherein the method includes:
  • a delay status report is received from a terminal 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 a service data unit (PDCP SDU) of a PDCP layer of the terminal device and/or the data volume related to the remaining time of a service data unit (RLC SDU) of an RLC layer.
  • PDCP SDU service data unit
  • RLC SDU service data unit
  • an information processing method which is applied to a terminal device, wherein the method includes:
  • the scheduling request is canceled.
  • an information processing method which is applied to a terminal device, wherein the method includes:
  • Triggering a delay status report ; triggering a scheduling request; initiating a random access process associated with the scheduling request; and stopping the random access process.
  • an information processing method which is applied to a terminal device, wherein the method includes:
  • the MAC PDU includes a Delay Status Report (DSR) and/or a Buffer Status Report (BSR).
  • DSR Delay Status Report
  • BSR Buffer Status Report
  • an information sending device which is applied to a terminal device, wherein the device includes:
  • a first triggering unit which is used to trigger a delay status report
  • a sending unit 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.
  • the delay status report includes data volume information
  • 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.
  • an information receiving device which is applied to a network device, wherein the device includes:
  • a receiving unit which is used to receive a delay status report sent by a terminal device, the delay status report includes data volume information, 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.
  • PDCP SDU the remaining time of the service data unit
  • RLC SDU remaining time of the service data unit
  • an information processing apparatus which is applied to a terminal device, wherein the apparatus includes:
  • a second triggering unit is used to trigger a delay status report; a third triggering unit is used to trigger a scheduling request; and a first processing unit is used to cancel the scheduling request.
  • an information processing apparatus which is applied to a terminal device, wherein the apparatus includes:
  • a fourth triggering unit which is used to trigger a delay status report
  • a fifth triggering unit which is used to trigger a scheduling request
  • a sixth triggering unit initiating a random access process related to a scheduling request
  • the second processing unit is configured to stop the random access procedure.
  • an information processing apparatus which is applied to a terminal device, wherein the apparatus includes:
  • a third processing unit is used to generate a MAC PDU; the MAC PDU includes a delay status report (DSR) and/or a buffer status report (BSR).
  • DSR delay status report
  • BSR buffer status report
  • a communication system including:
  • a terminal device configured to execute the above-mentioned information sending method and/or information processing method on the terminal device side;
  • a network device is configured to execute the above-mentioned information receiving method on the network device side.
  • 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 associated with the remaining time of the service data unit of the PDCP layer and/or the RLC layer of the terminal device.
  • the amount of data is reduced, thereby solving the problems existing in the prior art.
  • FIG1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG2 is a schematic diagram of a method for sending information according to an embodiment of the present application.
  • FIG3 is a schematic diagram of an application scenario of the information sending method according to an embodiment of the present application.
  • FIG4 is a schematic diagram of an information receiving method according to an embodiment of the present application.
  • FIG5 is a schematic diagram of an information processing method according to an embodiment of the present application.
  • FIG6 is another schematic diagram of the information processing method according to an embodiment of the present application.
  • FIG7 is another schematic diagram of the information processing method according to an embodiment of the present application.
  • FIG8 is a schematic diagram of an information sending device according to an embodiment of the present application.
  • FIG9 is a schematic diagram of an information receiving device according to an embodiment of the present application.
  • FIG10 is a schematic diagram of an information processing device according to an embodiment of the present application.
  • FIG11 is another schematic diagram of an information processing device according to an embodiment of the present application.
  • FIG12 is another schematic diagram of an information processing device according to an embodiment of the present application.
  • FIG13 is a schematic diagram of a network device according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, etc., 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.
  • 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), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.
  • LTE Long Term Evolution
  • LTE-A enhanced Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system may be carried out according to communication protocols of any stage, such as 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.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G and 5G 3G
  • NR New Radio
  • future 6G etc.
  • communication protocols currently known or to be developed in the future.
  • the term "network device” refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • the network device may include, but is not limited to, the following devices: a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), and the like.
  • base stations may include but are not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femeto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • base station may include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relays or low-power nodes such as femeto, pico, etc.
  • base station may include some or all of their functions, and each base station can provide communication coverage for a specific geographical area.
  • the term "cell” can refer
  • the term "user equipment” (UE) or “terminal equipment” (TE) refers to a device that accesses a communication network through a network device and receives network services.
  • the terminal device may 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 the like.
  • terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDA, Personal Digital Assistant), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.
  • PDA personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • laptop computers cordless phones
  • smart phones smart watches, digital cameras, etc.
  • the terminal device can also be a machine or device for monitoring or measuring, such as 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.
  • MTC machine type communication
  • D2D device to device
  • M2M machine to machine
  • network side refers to one side of the network, which may be a base station, or may include one or more network devices as above.
  • user side or “terminal side” or “terminal device side” refers to one side of the user or terminal, which may be a UE, or may include one or more terminal devices as above.
  • device may refer to either a network device or a terminal device.
  • 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 if no confusion is caused;
  • downlink control signal and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable.
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • downlink data signal and “downlink data information” or “Physical Downlink Shared Channel (PDSCH)” are interchangeable.
  • 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
  • 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 called uplink transmission (UL transmission) or uplink information or uplink channel.
  • Sending uplink transmission on uplink resources can be understood as sending the uplink transmission using the uplink resources.
  • downlink data/signal/channel/information can be understood accordingly.
  • the high-level signaling may be, for example, a radio resource control (RRC) signaling; for example, an RRC message (RRC message), including, for example, MIB, system information (system information), a dedicated RRC message; or an RRC IE (RRC information element).
  • RRC radio resource control
  • the high-level signaling may also be, for example, a MAC (Medium Access Control) signaling; or a MAC CE (MAC control element).
  • RRC radio resource control
  • FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation taking a terminal device and a network device as an example.
  • a communication system 100 may include a network device 101 and terminal devices 102 and 103.
  • FIG1 only illustrates two terminal devices and one network device as an example, but the embodiment of the present application is not limited thereto.
  • existing services or future services can be sent between the network device 101 and the terminal devices 102 and 103.
  • 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.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra-reliable and low-latency communication
  • the terminal device 102 may send uplink data to the network device 101, for example, using a dynamically scheduled grant or a configured grant transmission mode.
  • the network device 101 may receive data sent by one or more terminal devices 102, send information to the terminal device 102 for scheduling new uplink data transmission or uplink data retransmission, and may also send downlink data.
  • An embodiment of the present application provides a method for sending information, which is applied to a terminal device (UE) side and is described below in conjunction with the accompanying drawings.
  • UE terminal device
  • FIG. 2 is a schematic diagram of a method for sending information according to an embodiment of the present application. As shown in FIG. 2 , the method includes:
  • DSR Delay Status Report
  • the delay status report (DSR) includes data volume information, wherein the data volume information includes the data volume (data volume 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 volume 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.
  • the delay status report includes data volume information, wherein the data volume information includes the data volume (data volume 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 volume 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.
  • 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.
  • the DSR is used to report the delay information of at least one logical channel group (Logical Channel Group, LCG), and any existing method can be used to trigger the DSR report, for example, based on a threshold triggering the DSR report, 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 of the 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 (Logical Channel Group, LCG).
  • the UE may include at least one of the data amount information in the DSR and report it to the network side.
  • the data amount information may be used to indicate the amount of data associated with the remaining time (amount of data), and the amount of data associated with the remaining time may also be expressed as a buffer size (buffer size) or a buffer status (buffer status), etc.
  • the length of the data amount information may be 5 bits or 8 bits, and a value or index of the data amount information corresponds to a range of the amount of data associated with the remaining time, and the amount of data associated with the remaining time is in bits (bit) or bytes (byte).
  • one piece of data volume information corresponds to one logical channel group.
  • the UE may determine that the data volume information includes the data volume of the PDCP layer and/or the data volume of the RLC layer, for example, the data volume of the PDCP layer includes the data volume related to the remaining time of the service data unit (PDCP SDU), and the data volume of the RLC layer includes the data volume related to the remaining time of the service data unit (RLC SDU).
  • the method may also include (not shown in the figure):
  • determining the data volume information included in the DSR solves the problems existing in the prior art.
  • determining the data volume information may include at least one of the following methods:
  • the specific determination method is described below and will not be repeated here.
  • the DSR can be reported through any signaling.
  • the UE can define a separate MAC CE (MAC Control Element media access 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 by an existing MAC CE.
  • the remaining time of the service data unit may be calculated based on the value of a discard timer.
  • 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 PDCP layer of the UE receives a PDCP SDU from an upper layer (such as an RRC layer, etc.), if the discardTimer corresponding to/associated with the PDCP SDU is configured, the discardTimer is started, and the remaining time of the PDCP SDU is calculated according to the value of the discardTime.
  • an upper layer such as an RRC layer, etc.
  • the UE can calculate the remaining time (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 to the RLC SDU, and the RLC layer of the UE calculates the remaining time of the RLC SDU based on the value of the discardTime.
  • the discardTimer the discard timer associated with the service data unit (RLC SDU) of the RLC layer.
  • the PDCP entity of the transmitting UE discards the PDCP SDU and the PDCP Data PDU containing the PDCP SDU. If the data PDU has been submitted to the lower layer (such as the RLC layer), the discard is indicated to the lower layer; for the RLC layer of the UE, when the discard of a specific RLC SDU is indicated from the upper layer (such as 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 (such as the MAC layer).
  • the discardTimer may be configured by the network side, for example, the network may be configured 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, in milliseconds, and the value of the discardTimer when it is started is set to the initial value configured by the network.
  • the value of the discard timer decreases over time after it is started, and when it decreases to 0, the discardTimer is considered to have timed out; or, the initial value of the discardTimer when it is started is set to 0, and the discardTimer increases over time after it is started, and when it reaches the maximum value configured by the network, the discardTimer is considered to have timed out.
  • the remaining time of its PDCP SDU is determined by the PDCP layer.
  • 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.
  • discardTimer the discard timer associated with the service data unit (PDCP SDU) of the PDCP layer by the PDCP layer.
  • the PDCP of the UE receives a PDCP SDU from an upper layer (such as an 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 according to the value of the discardTime.
  • an upper layer such as an RRC layer, etc.
  • 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.
  • the RLC layer may calculate the remaining time of the RLC SDU based on the value of the discard timer associated with the service data unit (RLC SDU) of the RLC layer, and the PDCP layer indicates the remaining time to the RLC layer.
  • the RLC layer receives an RLC SDU from an upper layer (e.g., the PDCP layer, etc.)
  • the value of the discardTimer corresponding to/associated with the RLC SDU is received from the upper layer (e.g., PDCP), and the remaining time of the RLC SDU is calculated based on the value of the discardTimer.
  • the data volume associated with the remaining time of the 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.
  • the data volume associated with the remaining time of the business data unit includes: the remaining time of the business data unit meets the preset condition. 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.
  • the amount of data related to the remaining time of the service data unit may include: the amount of data of the PDCP SDU when the remaining time of the PDCP SDU satisfies the first preset condition; wherein,
  • the first preset condition may include: a PDCP SDU for which the remaining discardTimer value 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 situation where the PDCP discardTimer decreases over time after being started;
  • 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, the PDCP discardTimer increases over time after being activated.
  • 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.
  • the amount of data related to the remaining time of the service data unit may include: the amount of data of the RLC SDU when the remaining time of the RLC SDU meets the second preset condition.
  • the second preset condition may include: a RLC SDU for which the remaining discardTimer value 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 the case where the RLC discardTimer decreases over time after being started;
  • 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, in the case where the RLC discardTimer increases over time after being started.
  • 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.
  • the preset condition can be set according to actual conditions.
  • the preset condition ie, the first preset condition and the second preset condition
  • the preset condition can be the same or different, and will not be repeated here.
  • the first threshold and/or the second threshold are predefined or network configured.
  • the second threshold may be the lower limit of the value range corresponding to the index of the remaining time of the service data unit; the first threshold may be predefined or configured according to the timing of determining the amount of data related to the remaining time of the service data unit, such as when triggering DSR, generating DSR MAC CE, assembling DSR MAC PDU, or sending DSR MAC CE, etc.
  • the following is a detailed description with reference to the accompanying drawings and taking a specific application scenario as an example. The following examples are applicable to the PDCP layer and/or the RLC layer.
  • Fig. 3 is a schematic diagram of an application scenario of the information sending method of an embodiment of the present application, showing the DSR triggering, MAC CE generation and reporting process.
  • 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 PDCP discardTimer, and the reference time T4 (reference time) of the remaining time (remaining time) is calculated as 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.
  • PDU Protocol Data Unit
  • PDU set Physical uplink shared channel
  • the remaining time (remaining time) of the PDU or PDU set is lower than a threshold, at which time, the DSR is triggered (trigger 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 including 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 UL-SCH or PUSCH resources.
  • the amount of data associated with the remaining time of the service data unit includes: the amount of data associated with the remaining time of the service data unit when a delay status report (DSR) is triggered (trigger a DSR) (such as time T1);
  • DSR delay status report
  • the first threshold may be a threshold for triggering DSR for a logical channel group (LCG) configured by the network.
  • the network configures a threshold for triggering DSR for at least one logical channel group (LCG), each logical channel group includes at least one logical channel, and for a logical channel, it includes PDCP SDU and/or RLC SDU
  • the data includes PDU (payload carrying an information unit of the application layer) or PDU set data
  • 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 (remaining time threshold) for triggering DSR configured by the network for the logical channel group (LCG) where the logical channel corresponding to the service data unit is located.
  • the amount of data related to the remaining time of the service data unit includes: the amount of data related to the remaining time of the service data unit when the Delay Status Report (DSR) MAC CE is generated.
  • DSR Delay Status Report
  • 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 for each logical channel group (LCG) configured in the network and the time difference between when DSR is triggered and when DSR MAC CE is generated (such as T2-T1), 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 for each logical channel group (LCG) configured in the network.
  • the method may further include (not shown in the figure):
  • 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.
  • 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 (slot number) and/or a symbol number (symbol number).
  • SFN system frame number
  • slot number slot number
  • symbol number symbol number
  • the amount of data associated with the remaining time of the service data unit includes: the amount of data associated with the remaining time of the service data unit when a MAC PDU including a Delay Status Report (DSR) MAC CE is assembled (or obtained or generated).
  • DSR Delay Status Report
  • 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 time T3), or the first threshold is the difference between the threshold (remaining Time Threshould) for triggering DSR for 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 threshold (remaining Time Threshould) for triggering DSR for each logical channel group (LCG) configured by the network minus the time difference (such as T3-T1) between the time when DSR is triggered and when the MAC PDU including the DSR MAC CE is assembled.
  • the value obtained is the time difference between being triggered and the MAC PDU including the DSR MAC CE being assembled.
  • the method may further include (not shown in the figure):
  • 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
  • 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 (slot number) and/or a symbol number (symbol number).
  • SFN system frame number
  • slot number slot number
  • symbol number symbol number
  • the amount of data associated with the remaining time of the service data unit includes: the amount of data associated with the remaining time of the service data unit when the DSR MAC CE is sent, or the amount of data associated with the remaining time of the service data unit when the DSR MAC CE is reported, or the amount of data associated with the remaining time of the service data unit when the first symbol of PUSCH transmission is sent when the DSR MAC CE is sent.
  • 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 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 (such as T4-T1) (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 of the logical channel group configured by the network to trigger DSR) , or, the difference between the threshold of the logical channel group configured by the network to trigger DSR and the time difference between the time when DSR is triggered and the time when DSR MAC CE is reported (that is, the value obtained by subtracting the time difference between the time when DSR
  • 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:
  • 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 for 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 first symbol of the PUSCH transmission for which the DSR MAC CE is sent;
  • the MAC layer and/or the PDCP layer informs the RLC layer of at least one of the following information:
  • the time when DSR MAC CE is sent or, the time when DSR MAC CE is reported, or, the time when the first symbol of PUSCH transmission when DSR MAC CE is sent, or, the time difference between when DSR is triggered and when DSR MAC CE is sent, or, the time difference between when DSR is triggered and when DSR MAC CE is reported, or, the time difference between when DSR is triggered and when the first symbol of PUSCH transmission when DSR MAC CE is sent.
  • the time when the DSR MAC CE is sent or the DSR MAC CE is reported or the time when the first symbol of PUSCH transmission when the DSR MAC CE is sent can be an absolute time, or it can be a system frame number (System Frame Number, SFN) and/or a slot number (slot number) and/or a symbol number (symbol number).
  • SFN System Frame Number
  • slot number slot number
  • symbol number symbol number
  • 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 there is no limitation here.
  • GPS Global Positioning System
  • UTC Coordinated Universal Time
  • TUC Coordinated Universal Time
  • the amount of data associated with the remaining time can be determined, and the amount of data 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.
  • the first threshold may be multiple, and the number of determined data volume information may be one or more than one, which will not be described in detail here.
  • the values of the first threshold and/or the second threshold may be the same or different.
  • the amount of data associated with the remaining time indicated by the data volume information included in the DSR MAC CE of the MAC layer includes the amount of data (data volume or buffer status or amount of data) on all logical channels of a logical channel group, and the amount of data associated with the remaining time may be at least one of the following data amounts:
  • 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.
  • PDCP SDU the remaining time of the service data unit
  • RLC SDU the remaining time of the service data unit
  • 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 the DSR is triggered, such as the PDCP layer as described above, at the sending 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 the DSR is triggered, such as the RLC layer as described above, at the sending RLC entity corresponding to the logical channel.
  • PDCP SDU the amount of data related to the remaining time of the service data unit
  • RLC SDU the remaining time of the service data unit
  • 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 the DSR MAC CE is generated, such as the PDCP layer of the sending 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 the DSR MAC CE is generated, such as the RLC layer of the sending RLC entity corresponding to the logical channel.
  • PDCP SDU the amount of data related to the remaining time of the service data unit
  • RLC SDU the remaining time of the service data unit
  • 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) of the PDCP layer when the MAC PDU including the DSR MAC CE is assembled at the sending 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) of the RLC layer when the MAC PDU including the DSR MAC CE is assembled at the sending RLC entity corresponding to the logical channel.
  • PDCP SDU the remaining time of the service data unit
  • RLC SDU the remaining time of the service data unit
  • 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 the DSR MAC CE is sent at the sending 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 the DSR MAC CE is sent at the sending RLC entity corresponding to the logical channel.
  • PDCP SDU the amount of data related to the remaining time of the service data unit
  • RLC SDU the remaining time of the service data unit
  • 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 the DSR MAC CE is reported at the sending 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 the DSR MAC CE is reported at the sending RLC entity corresponding to the logical channel.
  • PDCP SDU the amount of data related to the remaining time of the service data unit
  • RLC SDU the amount of data related to the remaining time of the service data unit
  • 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) of the PDCP layer when the first symbol of PUSCH transmission is sent when DSR MAC CE is sent, at the sending 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) of the RLC layer when the first symbol of PUSCH transmission is sent when DSR MAC CE is sent, at the sending RLC entity corresponding to the logical channel.
  • PDCP SDU the remaining time of the service data unit
  • RLC SDU remaining time of the service data unit
  • the method may further include:
  • the amount of data associated with the remaining time of the service data unit of the RLC layer does not include the data discarded by the upper layer;
  • the amount of data associated with the remaining time of a service data unit of the RLC layer includes the data discarded by the upper layer;
  • 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.
  • the upper layer may be, for example, a PDCP 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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 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.
  • PDCP SDU data volume related to the remaining time of a service data unit
  • RLC SDU service data unit
  • 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.
  • 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.
  • 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 is as described in the embodiment of the first aspect and will not be repeated here.
  • the data volume information included in the DSR MAC CE of the MAC layer may also include at least one of the following information:
  • the amount of data related to the remaining time of the RLC SDU may also include:
  • the amount of data associated with the remaining time of the service data unit of the RLC layer does not include the data discarded by the upper layer;
  • the amount of data associated with the remaining time of the service data unit at the RLC layer includes the data discarded by the upper layer.
  • 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 will not be repeated here.
  • 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 delay to ensure the delay requirements of the service.
  • 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
  • DSR Delay Status Report
  • the present application provides an information processing method applied to a terminal device.
  • 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:
  • DSR Delay Status Report
  • the triggered delay status report 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.
  • 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 subheader, or the available uplink resources are later than the latency 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 a delay status report through the uplink resources indicated by the UL grant.
  • the scheduling request is cancelled in at least one of the following situations:
  • a MAC PDU is sent and the MAC PDU includes a DSR MAC CE, which includes 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 includes the data amount and/or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled;
  • the uplink grant (UL grant) can accommodate all the waiting data to be sent;
  • 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 that trigger 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 in the present application.
  • the method of canceling the DSR-triggered scheduling request in the above situations (1) to (4) can be They are described as follows:
  • DSR Delay Status Report
  • the present application provides an information processing method applied to a terminal device.
  • 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:
  • DSR Delay Status Report
  • SR scheduling request
  • the triggered delay status report 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.
  • the process of triggering the scheduling request may refer to the embodiment of the third aspect, and will not be repeated here.
  • initiating a random access process related to a scheduling request may be implemented with reference to an existing method for initiating a random access process, for example, the random access process in TSs 38.321 may be specifically referred to, as described below:
  • the MAC entity shall, for each SR in the waiting state:
  • the MAC entity shall for each pending SR:
  • the random access procedure is stopped in at least one of the following situations:
  • a MAC PDU is sent and the MAC PDU 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;
  • the uplink grant (UL grant) can accommodate all the waiting data to be sent;
  • 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 that trigger 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 in the present application.
  • both the buffer status report (BSR) and the data status report (DSR) include data volume, i.e., data volume or buffer size or amount of data.
  • BSR buffer status report
  • DSR data status report
  • the present application provides an information processing method applied to a terminal device.
  • 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:
  • the MAC PDU includes a Delay Status Report (DSR) and/or a Buffer Status Report (BSR).
  • DSR Delay Status Report
  • BSR Buffer Status Report
  • the triggered delay status report 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.
  • DSR delay status report
  • BSR buffer status report
  • the priority of the delay status report is higher than that of a regular BSR or a periodic BSR or a padding BSR; or, the priority of the delay status report (DSR) is lower than that of the regular BSR and higher than that of the periodic BSR or the padding BSR.
  • the network signaling may indicate the priority of the DSR and the priority of the BSR in an RRC message, or indicate that the priority of the DSR is higher than the priority of the BSR, or indicate that the priority of the BSR is higher than the priority of the DSR, and so on.
  • the DSR and BSR may be included in the same MAC PDU.
  • the MAC PDU may include both a delay status report (DSR) and a buffer status report (BSR).
  • DSR delay status report
  • BSR buffer status report
  • DSR delay status report
  • BSR buffer status report
  • 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 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 first aspect provided by the present application, and the repeated parts are not repeated.
  • the term "unit” or "module” can be a combination of software and/or hardware that implements a predetermined function.
  • the information receiving device includes:
  • a first triggering unit 801 which is used to trigger a delay status report
  • the sending unit 802 is used to send the delay status report to the network device, and 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.
  • PDCP SDU the remaining time of the service data unit
  • RLC SDU remaining time of the service data unit
  • 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.
  • 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.
  • 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 embodiments of the first aspect and are not repeated here.
  • the MAC layer notifies the PDCP layer of at least one of the following information:
  • 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 for 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 first symbol of the PUSCH transmission for which the DSR MAC CE is sent;
  • the MAC layer and/or the PDCP layer informs the RLC layer of at least one of the following information:
  • the time when DSR MAC CE is sent or, the time when DSR MAC CE is reported, or, the time when the first symbol of PUSCH transmission when DSR MAC CE is sent, or, the time difference between when DSR is triggered and when DSR MAC CE is sent, or, the time difference between when DSR is triggered and when DSR MAC CE is reported, or, the time difference between when DSR is triggered and when the first symbol of PUSCH transmission when DSR MAC CE is sent.
  • the time when the DSR MAC CE is sent or the DSR MAC CE is reported or the time when the first symbol of PUSCH transmission when the DSR MAC CE is sent can be an absolute time, or it can be a system frame number (System Frame Number, SFN) and/or a slot number (slot number) and/or a symbol number (symbol number).
  • SFN System Frame Number
  • slot number slot number
  • symbol number symbol number
  • the amount of data included in the DSR MAC CE at the MAC layer indicates the amount of data remaining.
  • the amount of data associated with the remaining time includes the amount of data (data volume or buffer status or amount of data) on all logical channels of a logical channel group, and the amount of data associated with the remaining time includes at least one of the following information:
  • the amount of data on all logical channels of the logical channel group at or after the DSR MAC CE is generated;
  • the amount of data related to the remaining time of the RLC RDU may also include:
  • the amount of data associated with the remaining time of the service data unit of the RLC layer does not include the data discarded by the upper layer;
  • the amount of data associated with the remaining time of the service data unit at the RLC layer includes the data discarded by the upper layer.
  • 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.
  • the embodiment of the present application also provides an information receiving device
  • 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.
  • the term "unit” or "module” can be a combination of software and/or hardware that implements a predetermined function.
  • the information receiving device includes:
  • 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.
  • the delay status report includes data volume information
  • 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.
  • 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.
  • the network device knows 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.
  • 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 embodiments of the first aspect and are not repeated here.
  • the amount of data associated with the remaining time indicated by the data volume information included in the DSR MAC CE of the MAC layer includes the amount of data (data volume or buffer status or amount of data) on all logical channels of a logical channel group, and the amount of data associated with the remaining time includes at least one of the following information:
  • the amount of data related to the remaining time of the RLC RDU may also include:
  • the amount of data associated with the remaining time of the service data unit of the RLC layer does not include the data discarded by the upper layer;
  • the amount of data associated with the remaining time of the service data unit at the RLC layer includes the data discarded by the upper layer.
  • 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.
  • 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 described in detail here.
  • 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.
  • the network device knows 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.
  • FIG10 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, the implementation of the information processing device refers to the implementation of the information processing method in the embodiment of the third aspect provided by the present application, and the repetitions are not repeated.
  • the term "unit” or "module” can implement a combination of software and/or hardware for a predetermined function.
  • the information processing device includes:
  • a second triggering unit 1001 which is used to trigger a delay status report
  • a third triggering unit 1002 which is used to trigger a scheduling request
  • the first processing unit 1003 is configured to cancel the scheduling request.
  • the delay status report (DSR) triggered by the second trigger unit 1001 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.
  • the process of the third triggering unit 1002 triggering the scheduling request can be implemented with reference to the prior art.
  • the first processing unit 1003 cancels the scheduling request in at least one of the following situations:
  • a MAC PDU is sent and includes a DSR MAC CE containing the data size and/or remaining time of the most recent DSR-triggering event until the MAC PDU is assembled, or Or the DSR MAC CE contains the data volume and/or the remaining time of the latest DSR-triggering event until the MAC PDU is assembled;
  • the uplink grant (UL grant) can accommodate all the waiting data to be sent;
  • 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 that trigger 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 in the present application.
  • FIG11 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, the implementation of the information processing device refers to the implementation of the information processing method in the embodiment of the fourth aspect provided by the present application, and the repetitions are not repeated.
  • the term "unit” or "module” can implement a combination of software and/or hardware for a predetermined function.
  • the method includes:
  • a sixth triggering unit 1103, configured to initiate a random access procedure related to a scheduling request
  • the second processing unit 1104 is configured to stop the random access process.
  • 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.
  • the process of the fifth triggering unit 1102 triggering the scheduling request may be, for example, There are no available uplink resources to send the triggered DSR, or the available uplink resources cannot accommodate the DSR MAC CE plus its subheader, or the available uplink resources are later than the latency 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.
  • the sixth triggering unit 1103 may initiate a random access process related to a scheduling request by referring to an existing method for initiating a random access process.
  • the second processing unit 1104 stops the random access process in at least one of the following situations:
  • a MAC PDU is sent and the MAC PDU 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;
  • the uplink grant (UL grant) can accommodate all the waiting data to be sent;
  • 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 that trigger 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 in the present application.
  • FIG12 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, the implementation of the information processing device refers to the implementation of the information processing method in the embodiment of the fifth aspect provided by the present application, and the repeated parts will not be repeated.
  • the term "unit” or "module” can be a combination of software and/or hardware that implements a predetermined function.
  • the device includes:
  • the third processing unit 1201 generates a MAC PDU
  • the MAC PDU includes a delay status report (DSR) and/or a buffer status report (BSR).
  • DSR delay status report
  • BSR buffer status report
  • 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, and the present application is not limited thereto.
  • DSR and BSR cannot be included in the same MAC PDU, in which case the MAC PDU includes at most one of a delay status report (DSR) and a buffer status report (BSR).
  • DSR delay status report
  • BSR buffer status report
  • DSR delay status report
  • BSR buffer status report
  • the priority of the delay status report is higher than that of a regular BSR or a periodic BSR or a padding BSR; or, the priority of the delay status report (DSR) is lower than that of the regular BSR and higher than that of the periodic BSR or the padding BSR.
  • the network signaling may indicate the priority of the DSR and the priority of the BSR in an RRC message, or indicate that the priority of the DSR is higher than the priority of the BSR, or indicate that the priority of the BSR is higher than the priority of the DSR, and so on.
  • the DSR and the BSR may be included in the same MAC PDU.
  • the MAC PDU may include both a delay status report (DSR) and a buffer status report (BSR).
  • DSR delay status report
  • BSR buffer status report
  • the DSR and the BSR are included in the same MAC PDU.
  • the present application also provides a communication system, which can be referred to in FIG1 and is similar to the first to fifth embodiments. The same content will not be repeated here.
  • the communication system 100 may include at least: a network device 101 and/or a terminal device 102, the terminal device 102 triggers a delay status report, and sends the delay status report to the network device 101; the network device 101 receives the delay status report sent by the terminal device 102.
  • 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.
  • PDCP SDU the remaining time of the service data unit
  • RLC SDU remaining time of the service data unit
  • the implementation of the above-mentioned delay status report can refer to the embodiments of the first aspect and the second aspect, which will not be repeated here.
  • FIG13 is a schematic diagram of the composition of a network device according to an embodiment of the present application.
  • the network device 1300 may include: a processor 1310 (e.g., a central processing unit CPU) and a memory 1320; the memory 1320 is coupled to the processor 1310.
  • the memory 1320 may store various data; in addition, it may store a program 1330 for information processing, and the program 1330 may be executed under the control of the processor 1310.
  • 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.
  • the processor 1310 may be configured to perform the following control: receiving a delay status report sent by a terminal 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.
  • PDCP SDU the delay status report
  • RLC SDU data volume related to the remaining time of the service data unit
  • the 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 of the prior art and are not described in detail here. It is worth noting that the network device 1300 does not necessarily include all the components shown in FIG13 ; in addition, the network device 1300 may also include components not shown in FIG13 , which may refer to the prior art.
  • 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.
  • FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1400 may include a processor 1410 and a memory 1420; the memory 1420 stores data and programs and is coupled to the processor 1410. It is worth noting that the figure is exemplary; other types of structures may also be used to supplement or replace the structure to implement telecommunication functions or other functions.
  • 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.
  • 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.
  • PDCP SDU the delay status report
  • RLC SDU data volume related to the remaining time of the service data unit
  • 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 the above 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 the components shown in FIG14 , and the above components are not necessary; in addition, the terminal device 1400 may also include components not shown in FIG14 , and reference may be made to the prior art.
  • 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.
  • 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.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program enables the network device to execute the information receiving method described in the embodiment of the second aspect.
  • 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.
  • the above devices and methods of the present application can be implemented by hardware, or by hardware combined with software.
  • the present application relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, 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.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to various software modules of the computer program flow or to various hardware modules.
  • These software modules may correspond to the various steps shown in the figure, respectively.
  • These hardware modules may be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).
  • FPGA field programmable gate array
  • the software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage known in the art.
  • 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 a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • the functional blocks described in the drawings and/or one or more combinations of functional blocks it can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present application.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • it can 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.
  • An information processing method applied to a terminal device, wherein the method comprises:
  • 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
  • the delay status report that triggered the scheduling request is cancelled.
  • An information processing method applied to a terminal device, wherein the method comprises:
  • the MAC PDU includes a delay status report (DSR) and/or a buffer status report (BSR).
  • DSR delay status report
  • BSR buffer status report
  • the MAC PDU includes one of a delay status report (DSR) and a buffer status report (BSR).
  • DSR delay status report
  • BSR buffer status report
  • the Delay Status Report has a higher priority than a regular BSR or a periodic BSR or a padding BSR; or
  • the priority of the delay status report is lower than that of the regular BSR, and higher than that of the periodic BSR or the padding BSR.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种信息发送、接收和处理方法方法、装置、通信系统。该方法包括：触发延迟状态报告；向网络设备发送所述延迟状态报告，所述延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。

Description

一种信息发送、接收和处理方法、装置、通信系统 技术领域
本申请实施例涉及通信技术领域。
背景技术
在第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)中，Release 18开始研究针对扩展现实(Extended Reality，XR)业务的增强，XR业务指的是所有现实和虚拟组合的环境、以及计算机技术和可穿戴设备产生的人机交互。XR业务可以包括虚拟现实(Virtual reality，VR)业务、增强现实(Augmented reality，AR)业务和混合现实(Mixed reality，MR)业务。
对于具有严格时延限制的XR业务，为满足其服务质量(Quality of Service，QoS)，具有时延信息的调度器是有好处的。具有时延信息的调度器在下行可实现，因为网络侧(如gNB)知道用户设备QoS特性(例如通过5G服务质量参数，如5G QoS标识符(5QI)获知)，也知道XR帧(frames，packets)何时到达，因此也知道调度缓存的数据的紧急程度。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，对于上行，由于当前的缓存状态报告(Buffer Status reporting，BSR)只提供缓存的数据量大小，却没有传递用户设备(UE)中数据已经被缓存了多长时间的信息，因此，网络侧调度器无法精确地知道UE中数据的缓存时间，这样3GPP认为：对XR业务，UE上报延迟信息(delay information)是有好处的。
目前，3GPP同意引入延迟信息的上报，例如，该延迟信息可以包括剩余时间(remaining time)及其关联的数据量(data volume或buffer status或amount of data)，但还未明确如何确定或计算与剩余时间关联的数据量。
针对上述问题的至少之一，本申请实施例提供一种信息发送、接收和处理方法、装置、通信系统。
根据本申请实施例的一个方面，提供一种信息发送方法，应用于终端设备，其中，所述方法包括：
触发延迟状态报告；
向网络设备发送所述延迟状态报告，该延迟状态报告包括数据量信息，该数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
根据本申请实施例的另一个方面，提供一种信息接收方法，应用于网络设备，其中，该方法包括：
接收终端设备发送的延迟状态报告，该延迟状态报告包括数据量信息，该数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
根据本申请实施例的另一个方面，提供一种信息处理方法，应用于终端设备，其中，该方法包括：
触发延迟状态报告；
触发调度请求；
取消所述调度请求。
根据本申请实施例的另一个方面，提供一种信息处理方法，应用于终端设备，其中，该方法包括：
触发延迟状态报告；触发调度请求；发起与调度请求相关的随机接入过程；停止该随机接入过程。
根据本申请实施例的另一个方面，提供一种信息处理方法，应用于终端设备，其中，该方法包括：
生成MAC PDU；该MAC PDU包括延迟状态报告(DSR)和/或缓存状态报告(BSR)。
根据本申请实施例的一个方面，提供一种信息发送装置，应用于终端设备，其中，该装置包括：
第一触发单元，其用于触发延迟状态报告；
发送单元，其用于向网络设备发送所述延迟状态报告，该延迟状态报告包括数据量信息，该数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
根据本申请实施例的另一个方面，提供一种信息接收装置，应用于网络设备，其中，该装置包括：
接收单元，其用于接收终端设备发送的延迟状态报告，该延迟状态报告包括数据量信息，该数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
根据本申请实施例的另一个方面，提供一种信息处理装置，应用于终端设备，其中，该装置包括：
第二触发单元，其用于触发延迟状态报告；第三触发单元，其用于触发调度请求；第一处理单元，其用于取消所述调度请求。
根据本申请实施例的另一个方面，提供一种信息处理装置，应用于终端设备，其中，该装置包括：
第四触发单元，其用于触发延迟状态报告；第五触发单元，其用于触发调度请求；
第六触发单元，发起与调度请求相关的随机接入过程；
第二处理单元，其用于停止所述随机接入过程。
根据本申请实施例的另一个方面，提供一种信息处理装置，应用于终端设备，其中，该装置包括：
第三处理单元，其用于生成MAC PDU；所述MAC PDU包括延迟状态报告(DSR)和/或缓存状态报告(BSR)。
根据本申请实施例的另一个方面，提供一种通信系统，包括：
终端设备，该终端设备被配置为执行上述终端设备侧的信息发送方法和/或信息处理方法；
网络设备，该网络设备被配置为执行上述网络设备侧的信息接收方法。
本申请实施例的有益效果之一在于：明确了如何确定与剩余时间关联的数据量，即该数据量包括终端设备的PDCP层和/或RLC层的与业务数据单元的剩余时间相关 的数据量，从而解决了现有技术中存在的问题。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是本申请实施例的通信系统的一示意图；
图2是本申请实施例的信息发送方法的一示意图；
图3是本申请实施例的信息发送方法的应用场景的一示意图；
图4是本申请实施例的信息接收方法的一示意图；
图5是本申请实施例的信息处理方法的一示意图；
图6是本申请实施例的信息处理方法的另一示意图；
图7是本申请实施例的信息处理方法的另一示意图；
图8是本申请实施例的信息发送装置的一示意图；
图9是本申请实施例的信息接收装置的一示意图；
图10是本申请实施例的信息处理装置的一示意图；
图11是本申请实施例的信息处理装置的另一示意图；
图12是本申请实施例的信息处理装置的另一示意图；
图13是本申请实施例的网络设备的示意图；
图14是本申请实施例的终端设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)、未来的6G等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。本文在没有特别指出的情况下，“设备”可以指网络设备，也可以指终端设备。
在以下的说明中，在不引起混淆的情况下，术语“上行控制信号”和“上行控制信息(UCI，Uplink Control Information)”或“物理上行控制信道(PUCCH，Physical Uplink Control Channel)”可以互换，术语“上行数据信号”和“上行数据信息”或“物理上行共享信道(PUSCH，Physical Uplink Shared Channel)”可以互换；
术语“下行控制信号”和“下行控制信息(DCI，Downlink Control Information)”或“物理下行控制信道(PDCCH，Physical Downlink Control Channel)”可以互换， 术语“下行数据信号”和“下行数据信息”或“物理下行共享信道(PDSCH，Physical Downlink Shared Channel)”可以互换。
另外，发送或接收PUSCH可以理解为发送或接收由PUSCH承载的上行数据，发送或接收PUCCH可以理解为发送或接收由PUCCH承载的上行信息，发送或接收PRACH可以理解为发送或接收由PRACH承载的preamble；上行信号可以包括上行数据信号和/或上行控制信号等，也可以称为上行传输(UL transmission)或上行信息或上行信道。在上行资源上发送上行传输可以理解为使用该上行资源发送该上行传输。类似地，可以相应地理解下行数据/信号/信道/信息。
在本申请实施例中，高层信令例如可以是无线资源控制(RRC)信令；例如称为RRC消息(RRC message)，例如包括MIB、系统信息(system information)、专用RRC消息；或者称为RRC IE(RRC information element)。高层信令例如还可以是MAC(Medium Access Control)信令；或者称为MAC CE(MAC control element)。但本申请不限于此。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请实施例的通信系统的一示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102、103。为简单起见，图1仅以两个终端设备和一个网络设备为例进行说明，但本申请实施例不限于此。
在本申请实施例中，网络设备101和终端设备102、103之间可以进行现有的业务或者未来可实施的业务发送。例如，这些业务可以包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
其中，终端设备102可以向网络设备101发送上行数据，例如使用动态调度的授权或配置的授权传输方式。网络设备101可以接收一个或多个终端设备102发送的数据，向终端设备102发送调度上行新数据传输或上行数据重传的信息，也可以发送下行数据。
下面结合附图对本申请实施例的信息发送方法、信息接收方法、信息处理方法及其装置进行详细说明。
第一方面的实施例
本申请实施例提供一种信息发送方法，该方法应用于终端设备(UE)侧，以下结合附图进行说明。
图2是本申请实施例的信息发送方法的一示意图，如图2所示，该方法包括：
201，触发延迟状态报告(Delay Status Report，DSR)；
202，向网络设备发送该延迟状态报告(DSR)，该延迟状态报告(DSR)包括数据量信息，该数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间(remaining time)相关的数据量(data volum或buffer status或amount of data)和/或RLC层的与业务数据单元(RLC SDU)的剩余时间(remaining time)相关的数据量(data volum或buffer status或amount of data)。
根据上述实施例，明确了如何确定与剩余时间关联的数据量，即该数据量包括终端设备的PDCP层和/或RLC层的与业务数据单元的剩余时间相关的数据量，从而解决了现有技术中存在的问题。
在一些实施例中，在201中，该DSR用于对至少一个逻辑信道组(Logical Channel Group，LCG)的延迟信息进行上报，可采用已有的任何一种方法来触发DSR上报，例如，基于门限触发DSR上报，例如，当一个PDU(Protocol Data Unit，协议数据单元)或PDU set(Protocol Data Unit set，协议数据单元集合)的剩余时间(remaining time)低于一门限时，DSR上报被触发。其中，一个PDU承载在应用层生成的一个单位的信息的净荷(payload)，例如XR业务的帧(frame)或视频切片(video slice)，一个PDU set包括一个或多于一个该PDU，该门限可由网络配置，例如，网络为每个逻辑信道组(Logical Channel Group，LCG)配置一个触发DSR上报的门限。
在一些实施例中，在202中，UE可将至少一个该数据量信息包含在DSR中向网络侧上报。该数据量信息可以用于指示与剩余时间相关的数据量(amount of data)，该与剩余时间相关的数据量还可以表述为缓存大小(buffer size)或缓存状态(buffer status)等，该数据量信息的长度可以是5比特或8比特，一个数据量信息的值或索引对应一个范围的与剩余时间相关的数据量，该与剩余时间相关的数据量以比特(bit)或字节(byte)为单位。
在一些实施例中，一个数据量信息与一个逻辑信道组对应。
在一些实施例中，UE可确定数据量信息包括PDCP层的数据量和/或RLC层的数据量，例如，该PDCP层的数据量包括与业务数据单元(PDCP SDU)的剩余时间(remaining time)相关的数据量，该RLC层的数据量包括与业务数据单元(RLC SDU)的剩余时间相关的数据量。在这种情况下，该方法还可包括(图中未示出)：
确定DSR中包含的数据量信息，从而解决了现有技术中存在的问题。例如，在PDCP层和/或RLC层中，确定该数据量信息可包括如下方法至少其中之一：
与在DSR被触发时的业务数据单元的剩余时间相关的数据量；与在DSR MAC CE被生成时的业务数据单元的剩余时间相关的数据量；与在包含DSR MAC CE的MAC PDU被组装(还可表述为被得到(obtained)或被生成(generated))时的业务数据单元的剩余时间相关的数据量；与在DSR MAC CE或包含DSR MAC CE的MAC PDU被发送时的业务数据单元的剩余时间相关的数据量。具体的确定方法在下面进行说明，此处不再赘述。
在一些实施例中，在202中，可通过任何信令来上报该DSR，例如，UE可定义一个单独的MAC CE(MAC Control Element媒体接入控制控制元素)用于上报该DSR，但不限于此，该DSR还可采用其他已有的信令(例如，RRC信令等)承载，或者由已有的MAC CE承载。
在一些实施例中，该业务数据单元的剩余时间可基于丢弃计时器(discardTimer)的值来计算。其中，对于PDCP层，UE可基于针对该PDCP层的业务数据单元(PDCP SDU)关联的丢弃计时器(discardTimer)的值计算PDCP SDU的剩余时间(remaining time)，例如，在UE的PDCP层收到来自上层(例如RRC层等)的一个PDCP SDU时，如果该PDCP SDU对应/关联的discardTimer被配置，则该discardTimer被启动，根据该discardTime的值来计算该PDCP SDU的剩余时间。对于RLC层，UE可以基于针对该RLC层的业务数据单元(RLC SDU)关联的丢弃计时器(discardTimer)的值计算RLC SDU的剩余时间(remaining time)，例如，在UE的RLC层收到来自上层(例如PDCP层等)的一个RLC SDU时，上层可以通知该RLC SDU对应/关联的discardTimer的值，UE的RLC层根据该discardTime的值来计算该RLC SDU的剩余时间。
当与一个PDCP SDU对应/关联的discardTimer超时时，该发送端UE的PDCP实体丢弃该PDCP SDU和包含该PDCP SDU的PDCP Data PDU，如果对应的PDCP  data PDU已经被提交到低层(例如RLC层)，则向低层指示该丢弃；对于UE的RLC层，当从上层(例如PDCP)指示丢弃一个特定的RLC SDU时，RLC实体丢弃该被指示的RLC SDU，如果该RLC SDU或该RLC SDU的分段还没有被提交到低层(例如MAC层)的话。
在一些实施例中，该discardTimer可由网络侧进行配置，例如网络基于UE的DRB(Data Radio Bearer，数据无线承载)进行配置，该discardTimer的初始值或最大值可由网络侧配置。其中，该初始值可以设为大于0的整数，单位是毫秒，discardTimer被启动时的值被设置为网络配置的初始值，discard timer在被启动后的值随时间而减少，减为0时，认为discardTimer超时；或者，discardTimer被启动时的初始值被设置为0，discardTimer在被启动后随时间而增加，达到网络配置的最大值时，认为discardTimer超时。
在一些实施例中，对于PDCP层，其PDCP SDU的剩余时间由PDCP层确定。例如，PDCP层可基于PDCP层针对该PDCP层的业务数据单元(PDCP SDU)关联的丢弃计时器(discardTimer)的值计算PDCP SDU的剩余时间(remaining time)，例如，在UE的PDCP收到来自上层(例如RRC层等)的一个PDCP SDU时，如果该PDCP SDU对应/关联的discardTimer被配置，则发送端UE的PDCP实体启动与该PDCP SDU对应/关联的discardTimer，根据该discardTime的值来计算该PDCP SDU的剩余时间。
对于RLC层，RLC SDU的剩余时间可由上层指示，例如由PDCP层指示，但不限于此，还可由其他上层指示。例如，RLC层可基于RLC层的业务数据单元(RLC SDU)关联的丢弃计时器的值计算RLC SDU的剩余时间，由PDCP层向RLC层指示该剩余时间。例如，在RLC层收到来自上层(例如，PDCP层等)的一个RLC SDU时，从上层(例如PDCP)接收与该RLC SDU对应/关联的discardTimer的值，根据该discardTimer的值来计算该RLC SDU的剩余时间。
在一些实施例中，与业务数据单元的剩余时间相关的数据量(data volum)包括：在该业务数据单元的剩余时间满足预设条件时的业务数据单元的数据量。其中，该预设条件可包括：业务数据单元的剩余时间小于或等于第一阈值；或者业务数据单元的剩余时间大于或等于第一阈值；或者业务数据单元的剩余时间在第一阈值和第二阈值之间。例如，与业务数据单元的剩余时间相关的数据量包括在业务数据单元的剩余时 间小于或等于第一阈值时的业务数据单元的数据量；或者包括在业务数据单元的剩余时间大于等于第二阈值时的业务数据单元的数据量；或者包括在业务数据单元的剩余时间在第一阈值和第二阈值之间时的业务数据单元的数据量。
例如，针对PDCP层，与业务数据单元的剩余时间相关的数据量可包括：在PDCP SDU的剩余时间满足第一预设条件时的PDCP SDU的数据量；其中，
在一些实施例中，该第一预设条件可包括：PDCP SDU的剩余时间小于或等于第一阈值(a PDCP SDU for which the remaining discardTimer value is less than or equal to a first threshold)，如针对PDCP discardTimer在被启动后随时间而减少的情况；
在一些实施例中，该第一预设条件可包括：PDCP SDU的剩余时间大于或等于第一阈值(a PDCP SDU for which the remaining discardTimer value is higher than or equal to a first threshold)，例如针对PDCP discardTimer在被启动后随时间而增加的情况。
在一些实施例中，该第一预设条件可包括：PDCP SDU的剩余时间可处于一个范围内，如第一阈值和第二阈值之间，例如当第一阈值大于第二阈值时，PDCP SDU的剩余时间可小于或等于第一阈值且大于或等于第二阈值(a PDCP SDU for which the remaining discardTimer value is less than a first threshold and higher than or equal to a second threshold)，反之亦然。
例如，针对RLC层，与业务数据单元的剩余时间相关的数据量可包括：在RLC SDU的剩余时间满足第二预设条件时的RLC SDU的数据量。其中
在一些实施例中，该第二预设条件可包括：RLC SDU的剩余时间小于或等于第一阈值(a RLC SDU for which the remaining discardTimer value is less than or equal to a first threshold)，如针对RLC discardTimer在被启动后随时间而减少的情况；
在一些实施例中，该第二预设条件可包括：RLC SDU的剩余时间大于或等于第一阈值(a RLC SDU for which the remaining discardTimer value is higher than or equal to a first threshold)，例如针对RLC discardTimer在被启动后随时间而增加的情况。
在一些实施例中，该第二预设条件可包括：RLC SDU的剩余时间可处于一个范围内，如第一阈值和第二阈值之间，例如当第一阈值大于第二阈值时，RLC SDU的剩余时间可小于或等于第一阈值且大于或等于第二阈值(a RLC SDU for which the remaining discardTimer value is less than a first threshold and higher than or equal to a second threshold)，反之亦然。
在一些实施例中，该预设条件可根据实际情况进行设定，对于PDCP层和RLC层，该预设条件(即第一预设条件和第二预设条件)可相同，也可不同，此处不再赘述。
在一些实施例中，该第一阈值和/或该第二阈值是预定义的或者网络配置。其中，该第二阈值可以是业务数据单元的剩余时间的索引对应的取值范围的下限；该第一阈值可根据确定与业务数据单元的剩余时间相关的数据量的时机，如触发DSR时、生成DSR MAC CE时、组装DSR MAC PDU时、或者发送DSR MAC CE时等进行预定义或者配置，以下结合附图以具体的应用场景为例进行详细说明，以下示例适用于PDCP层和/或RLC层。
图3是本申请实施例的信息发送方法的应用场景的一示意图，图中示出DSR触发、MAC CE生成和上报过程。如图3所示，UE获得一个PDU(Protocol Data Unit，协议数据单元)或PDU set(Protocol Data Unit set，协议数据单元集合)的剩余时间(get remaining time of a PDU or a PDU set)，例如可通过PDCP discardTimer的值来确定剩余时间，计算该剩余时间(remaining time)的参考时间T4(reference time)为UE在UL-SCH(上行共享信道)或PUSCH(物理上行共享信道)资源(resource)上传输第一个符号的时刻和/或满足其他条件的时刻。在T1时刻，该PDU或PDU set的剩余时间(remaining time)低于一门限，此时，DSR被触发(trigger a DSR)；在T2时刻，生成DSR MAC CE，通过生成的DSR MAC CE上报数据量信息(如剩余时间和/或与剩余时间相关的数据量)；在T3时刻，组装包含该DSR MAC CE的MAC PDU，T3可以与T2相同或稍微晚于T2；在T4时刻，在UL-SCH或PUSCH资源中发送该DSR MAC CE或包括该DSR MAC CE的MAC PDU。
以下参考图3，对确定与业务数据单元(PDCP SDU和/或RLC SDU)的剩余时间相关的数据量进行说明。
例1，如图3所示，该与业务数据单元的剩余时间相关的数据量包括：与在延迟状态报告(DSR)被触发(trigger a DSR)时(如T1时刻)的业务数据单元的剩余时间相关的数据量；
在这种情况下，该第一阈值可以是网络配置的逻辑信道组(LCG)触发DSR的门限。网络为至少一个逻辑信道组(LCG)分别配置触发DSR的门限，每个逻辑信道组包括至少一个逻辑信道，对于一个逻辑信道，其包括PDCP SDU和/或RLC SDU 的数据，即包括PDU(承载应用层一个信息单位的payload)或PDU set的数据，MAC层触发DSR的门限即为PDU或PDU set所在的逻辑信道组的DSR门限。因此，该第一阈值是网络为该业务数据单元对应的逻辑信道所在的逻辑信道组(LCG)配置的触发DSR的门限(remaining Time Threshold)。
例2，如图3所示，与该业务数据单元的剩余时间相关的数据量包括：与在延迟状态报告(Delay Status Report，DSR)MAC CE被生成时的业务数据单元的剩余时间相关的数据量。
在这种情况下，该第一阈值为DSR MAC CE被生成时(如T2时刻)的业务数据单元的剩余时间的值，或者，该第一阈值为网络配置的每个逻辑信道组(LCG)触发DSR的门限(remaining Time Threshould)与DSR被触发时和DSR MAC CE被生成时之间的时间差(如T2-T1)的差值，即网络配置的每个逻辑信道组(LCG)触发DSR的门限(remaining Time Threshould)减去DSR被触发与DSR MAC CE被生成之间的时间差，得到的值。
在一些实施例中，该方法还可包括(图中未示出)：
对于PDCP层，由MAC层通知PDCP层DSR MAC CE被生成时的时间，和/或，DSR被触发时和DSR MAC CE被生成时的时间差；和/或
对于RLC层，由MAC层和/或PDCP层通知RLC层DSR MAC CE被生成时的时间，和/或，DSR被触发时和DSR MAC CE被生成时的时间差。
在上面的实施例中，DSR MAC CE被生成时的时间可是绝对时间，也可以是系统帧号(System Frame Number，SFN)和/或时隙号(slot number)和/或符号号(symbol number)。
例3，与该业务数据单元的剩余时间相关的数据量包括：与在包括延迟状态报告(Delay Status Report，DSR)MAC CE的MAC PDU被组装(或被得到(obtained)或被生成(generated))时的业务数据单元的剩余时间相关的数据量。
在这种情况下，该第一阈值为包括DSR MAC CE的MAC PDU被组装时(如T3时刻)的业务数据单元的剩余时间的值，或者，该第一阈值为网络配置的每个逻辑信道组(LCG)触发DSR的门限(remaining Time Threshould)与DSR被触发时和包括DSR MAC CE的MAC PDU被组装时之间的时间差(如T3-T1)的差值，即网络配置的每个逻辑信道组(LCG)触发DSR的门限(remaining Time Threshould)减去DSR 被触发与包括DSR MAC CE的MAC PDU被组装之间的时间差，得到的值。
在一些实施例中，该方法还可包括(图中未示出)：
对于PDCP层，由MAC层通知PDCP层包括DSR MAC CE的MAC PDU被组装时的时间，和/或，DSR被触发时和包括DSR MAC CE的MAC PDU被组装时的时间差；和/或
对于RLC层，由MAC层和/或PDCP层通知RLC层包括DSR MAC CE的MAC PDU被组装时的时间，和/或，DSR被触发时和包括DSR MAC CE的MAC PDU被组装时的时间差。
在上面的实施例中，包括DSR MAC CE的MAC PDU被组装时的时间可是绝对时间，也可以是系统帧号(System Frame Number，SFN)和/或时隙号(slot number)和/或符号号(symbol number)。
例4，如图3所示，与业务数据单元的剩余时间相关的数据量包括：与在DSR MAC CE被发送时的业务数据单元的剩余时间相关的数据量，或者，与在DSR MAC CE被报告时的业务数据单元的剩余时间相关的数据量，或者，与在DSR MAC CE被发送的PUSCH传输第一个符号时的业务数据单元的剩余时间相关的数据量。
在这种情况下，该第一阈值为DSR MAC CE被发送时(如T4时刻)的业务数据单元的剩余时间的值，或者，DSR MAC CE被报告时的业务数据单元的剩余时间的值，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的业务数据单元的剩余时间的值，或者，网络配置的逻辑信道组触发DSR的门限与DSR被触发时和DSR MAC CE被发送时的时间差(如T4-T1)的差值(即网络配置的逻辑信道组触发DSR的门限减去DSR被触发和DSR MAC CE被发送之间的时间差，得到的值)，或者，网络配置的逻辑信道组触发DSR的门限与DSR被触发时和DSR MAC CE被报告时的时间差的差值(即网络配置的逻辑信道组触发DSR的门限减去DSR被触发和DSR MAC CE被报告之间的时间差，得到的值)，或者，网络配置的逻辑信道组触发DSR的门限与DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差的差值(即网络配置的逻辑信道组触发DSR的门限减去DSR被触发和DSR MAC CE被发送的PUSCH传输第一个符号之间的时间差，得到的值)。
在一些实施例中，该方法还包括(图中未示出)：对于PDCP层，由MAC层通知PDCP层以下信息的至少一个：
DSR MAC CE被发送时的时间，或者，DSR MAC CE被报告时的时间，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的时间，或者，DSR被触发时和DSR MAC CE被发送时的时间差，或者，DSR被触发时和DSR MAC CE被报告时的时间差，或者，DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差；和/或
对于RLC层，由MAC层和/或PDCP层通知RLC层以下信息的至少一个：
DSR MAC CE被发送时的时间，或者，DSR MAC CE被报告时的时间，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的时间，或者，DSR被触发时和DSR MAC CE被发送时的时间差，或者，DSR被触发时和DSR MAC CE被报告时的时间差，或者，DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差。
在上面的实施例中，DSR MAC CE被发送时或DSR MAC CE被报告时或DSR MAC CE被发送的PUSCH传输第一个符号时的时间可以是绝对时间，也可以是系统帧号(System Frame Number，SFN)和/或时隙号(slot number)和/或符号号(symbol number)。
在上述例1～例4中，上述绝对时间例如可以为全球定位系统(Global Positioning System，GPS)时间或协调世界时(UTC，英文缩写为CUT，即Coordinated Universal Time，法文缩写为TUC)时间等，此处不做限制。
根据上述实施例，可确定与剩余时间关联的数据量，该数据量包括终端设备的PDCP层和/或RLC层的与业务数据单元的剩余时间相关的数据量，从而解决了现有技术中存在的问题。
在一些实施例中，上述第一阈值可以为多个，确定的数据量信息的数量也可以为一个或多于一个，此处不再赘述。
在一些实施例中，对于PDCP层和RLC层，上述第一阈值和/或第二阈值的取值可以相同，也可不同。
在一些实施例中，在MAC层的DSR MAC CE中包括的数据量信息指示的与剩余时间相关的数据量包括一个逻辑信道组的所有逻辑信道上的数据量(data volum或buffer status或amount of data)，该与剩余时间相关的数据量可以是以下数据量中的至少一个：
(1)在延迟状态报告(DSR)被触发时，在逻辑信道组的所有逻辑信道上的数据量；
(2)在DSR MAC CE被生成时或者被生成后，在逻辑信道组的所有逻辑信道上的数据量；
(3)在DSR MAC PDU被组装(或被得到或被生成)时或者被组装(或被得到或被生成)后，在逻辑信道组的所有逻辑信道上的数据量；
(4)在DSR MAC CE被发送时，在逻辑信道组的所有逻辑信道上的数据量；
(5)在DSR MAC CE被报告时，在逻辑信道组的所有逻辑信道上的数据量；
(6)在DSR MAC CE被发送的PUSCH传输第一个符号时，在逻辑信道组的所有逻辑信道上的数据量。
在一些实施例中，一个逻辑信道组的每个逻辑信道上的数据量包括：前文所述的终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量，和/或，前文所述的RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
对于上述(1)，在DSR被触发时，在逻辑信道组的每个逻辑信道上的数据量包括：在该逻辑信道对应的发送PDCP实体，如前文所述的PDCP层的与在DSR被触发时的业务数据单元(PDCP SDU)的剩余时间相关的数据量，和/或，在该逻辑信道对应的发送RLC实体，如前文所述的RLC层的与在DSR被触发时的业务数据单元(RLC SDU)的剩余时间相关的数据量。对于上述(2)，在DSR MAC CE被生成时或者被生成后，在逻辑信道组的每个逻辑信道上的数据量包括：在该逻辑信道对应的发送PDCP实体，PDCP层的与在DSR MAC CE被生成时的业务数据单元(PDCP SDU)的剩余时间相关的数据量，和/或，在该逻辑信道对应的发送RLC实体，RLC层的与在DSR MAC CE被生成时的业务数据单元(RLC SDU)的剩余时间相关的数据量。
对于上述(3)，在包括DSR MAC CE的MAC PDU被组装时或者被组装后，在逻辑信道组的每个逻辑信道上的数据量包括：在该逻辑信道对应的发送PDCP实体，PDCP层的与在包括DSR MAC CE的MAC PDU被组装时的业务数据单元(PDCP SDU)的剩余时间相关的数据量，和/或，在该逻辑信道对应的发送RLC实体，RLC层的与在包括DSR MAC CE的MAC PDU被组装时的业务数据单元(RLC SDU)的剩余时间相关的数据量。
对于上述(4)，在DSR MAC CE被发送时，在逻辑信道组的每个逻辑信道上的数据量包括：在该逻辑信道对应的发送PDCP实体，PDCP层的与在DSR MAC CE被发送时的业务数据单元(PDCP SDU)的剩余时间相关的数据量，和/或，在该逻辑信道对应的发送RLC实体，RLC层的与在DSR MAC CE被发送时的业务数据单元(RLC SDU)的剩余时间相关的数据量。
对于上述(5)，在DSR MAC CE被报告时，在逻辑信道组的每个逻辑信道上的数据量包括：在该逻辑信道对应的发送PDCP实体，PDCP层的与在DSR MAC CE被报告时的业务数据单元(PDCP SDU)的剩余时间相关的数据量，和/或，在该逻辑信道对应的发送RLC实体，RLC层的与在DSR MAC CE被报告时的业务数据单元(RLC SDU)的剩余时间相关的数据量。
对于上述(6)在DSR MAC CE被发送的PUSCH传输第一个符号时，在逻辑信道组的每个逻辑信道上的数据量包括：在该逻辑信道对应的发送PDCP实体，PDCP层的与在DSR MAC CE被发送的PUSCH传输第一个符号时的业务数据单元(PDCP SDU)的剩余时间相关的数据量，和/或，在该逻辑信道对应的发送RLC实体，RLC层的与在DSR MAC CE被发送的PUSCH传输第一个符号时的业务数据单元(RLC SDU)的剩余时间相关的数据量。
在一些实施例中，对于RLC层，在确定与RLC SDU的剩余时间相关的数据量时，还可包括：
当被上层丢弃的数据(如discardTimer超时被丢弃的数据)还未被包括在RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量不包括该被上层丢弃的数据；和/或
当被上层丢弃的数据已经包括在等待初传的RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量包括该被上层丢弃的数据；和/或
当被上层丢弃的数据已经包括在等待重传的RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量包括该被上层丢弃的数据。
其中，该上层例如可以为PDCP层。
在一些实施例中，被上层丢弃的数据已经被传递到RLC层，当上层由于discardTimer超时而丢弃该数据时，上层向RLC层指示丢弃的RLC SDU。此时，在RLC层可以进行如下处理：
例如，如果上层指示丢弃的RLC SDU或RLC SDU的分段还未被包括在RLC data PDU中，或者还未被提交到MAC层和/或物理层，则该RLC SDU或RLC SDU的分段不被包括在RLC层的与业务数据单元的剩余时间相关的数据量中。
例如，如果上层指示丢弃的RLC SDU或RLC SDU的分段已经包括在等待初传的RLC data PDU中，或者已经包括在等待重传的RLC data PDU中，或者已经被提交到MAC层和/或物理层，或者已经被包括在MAC PDU中，或者已经被MAC层和/或物理层初传或重传，则该RLC SDU或RLC SDU的分段被包括在RLC层的与业务数据单元的剩余时间相关的数据量中。
根据上述实施例，可更加准确地确定与业务数据单元的剩余时间相关的数据量，解决了现有技术中存在的问题，此外可将确定的数据量包含在DSR中向网络设备上报，有助于网络设备分配合适大小的上行资源用于终端设备的的上行业务的传输，避免上行资源分配不足导致上行业务无法满足其时延要求或避免上行资源分配过多导致无线资源浪费。
第二方面的实施例
本申请实施例提供一种信息接收方法，应用于网络侧，与第一方面的实施例对应，对于与第一方面的实施例不同的内容进行详细说明，对于与第一方面的实施例相同的内容可参考第一方面的实施例，此处不再赘述。
图4是本申请实施例的信息接收方法的一示意图，应用于网络设备，如图4所示，该方法包括：
401，接收终端设备发送的延迟状态报告，该延迟状态报告包括数据量信息，该数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
根据上述实施例，网络设备接收终端设备发送的延迟状态报告，可获得该DSR中包含的数据量信息，即PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量，是的网络设备获知较为准确的缓存数据的紧急程度。
在一些实施例中，终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数 据量如第一方面的实施例所述，此处不再赘述。
在一些实施例中，在MAC层的DSR MAC CE中包括的数据量信息，还可包括以下信息的至少一个：
(1)在延迟状态报告被触发时，在逻辑信道组的所有逻辑信道上的数据量；
(2)在DSR MAC CE被生成时或者被生成后，在逻辑信道组的所有逻辑信道上的数据量；
(3)在DSR MAC PDU被组装(或被得到或被生成)时或者被组装(或被得到或被生成)后，在逻辑信道组的所有逻辑信道上的数据量；
(4)在DSR MAC CE被发送时，在逻辑信道组的所有逻辑信道上的数据量；
(5)在DSR被发送的PUSCH传输第一个符号时，在逻辑信道组的所有逻辑信道上的数据量。
以上数据量信息如第一方面的实施例所述，将其内容合并于此，此处不再赘述。
在一些实施例中，对于RLC层，与RLC SDU的剩余时间相关的数据量还可包括：
当被上层丢弃的数据(如discardTimer超时被丢弃的数据)还未包括在RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量不包括该被上层丢弃的数据；和/或
当被上层丢弃的数据已经包括在等待初传或重传的RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量包括该被上层丢弃的数据。
在一些实施例中，该方法还包括(图中未示出)：为终端设备配置第一阈值和/或第二阈值，并将确定的阈值通知该终端设备。其中该第一阈值和第二阈值如第一方面的实施例所述，此处不再赘述。
根据上述实施例，网络设备接收终端设备发送的延迟状态报告，可获得该DSR中包含的数据量信息，即PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量，使得网络设备获知较为准确的缓存数据的紧急程度，进而分配合适的上行资源来传输时延紧急的数据，以保证业务的时延要求。
第三方面的实施例
目前，3GPP同意定义一个单独的MAC CE用于延迟状态报告(DSR)的上报。发明人发现，在特定条件下，被触发的该DSR可以触发一个调度请求(scheduling request，SR)。然而还不清楚该SR在什么情况下被取消。
为解决上述问题，本申请提供一种信息处理方法，应用于终端设备。
图5是本申请实施例的信息处理方法的一示意图。如图5所示，该信息处理方法包括：
501，触发延迟状态报告(Delay Status Report，DSR)；
502，触发调度请求(scheduling request，SR)；
503，取消所述调度请求。
在一些实施例中，在501中，触发的延迟状态报告(DSR)可以与本申请第一方面的实施例中触发的延迟状态报告(DSR)相同，也可以不同，本申请不以此为限。
在一些实施例中，在502中，触发调度请求的过程可以是例如终端设备没有可用的上行资源来发送该触发的DSR，或者可用的上行资源无法容纳DSR MAC CE加上其子头，或者可用的上行资源晚于上行业务的时延要求等等，终端设备将触发调度请求，在PUCCH中向网络设备发送调度请求，请求网络设备发送UL grant来分配上行资源，以便终端设备通过该UL grant指示的上行资源进行延迟状态报告的上报。
在一些实施例中，在503中，该调度请求在以下至少一个情况下被取消：
(1)MAC PDU被发送且该MAC PDU包括DSR MAC CE，该DSR MAC CE包含直到该MAC PDU组装之前的最新触发DSR的事件的数据量和/或剩余时间，或者该DSR MAC CE包含直到该MAC PDU组装之时的最新触发DSR的事件的数据量和/或剩余时间；
(2)上行授权(UL grant)能容纳要发送的所有等待的数据；
(3)所有触发的延迟状态报告(DSR)都被取消；
(4)触发该调度请求(SR)的延迟状态报告(DSR)被取消。
在一些实施例中，在上述(1)中的触发DSR的事件例如基于门限触发DSR，具体如第一方面的实施例所述，此处不再赘述；或者，还可以为其他触发DSR的事件。触发DSR的事件的数据量可以为本申请第一方面的实施例所述的数据量，或者，还可以为其他数据量，本申请对此不作限制。
上述实施例中，在上述情况(1)至(4)下取消DSR触发的调度请求的方式可 以分别被进行如下描述：
根据上述实施例，明确了延迟状态报告(DSR)触发的调度请求(SR)何时被取消，由此，可以减少不必要的SR的发送，此外还可以节约SR发送所占用的资源，降低UE功率消耗而省电，从而解决了现有技术中存在的问题。
第四方面的实施例
目前，3GPP同意定义一个单独的MAC CE用于延迟状态报告(DSR)上报。发明人发现，在特定条件下，被触发的该DSR可以触发一个调度请求(scheduling request，SR)。如果对该SR没有配置有效的PUCCH资源，则UE会发起随机接入过程并取消该SR。目前还不清楚该随机接入过程在什么情况下被停止。
为解决上述问题，本申请提供一种信息处理方法，应用于终端设备。
图6是本申请实施例的信息处理方法的一示意图。如图6所示，该方法包括：
601，触发延迟状态报告(Delay Status Report，DSR)；
602，触发调度请求(scheduling request，SR)；
603，发起与调度请求相关的随机接入过程；
604，停止所述随机接入过程。
在一些实施例中，在601中，触发的延迟状态报告(DSR)可以与本申请第一方面的实施例中触发的延迟状态报告(DSR)相同，也可以不同，本申请不以此为限。
在一些实施例中，在602中，触发调度请求的过程可参照第三方面的实施例所述，此处不再赘述。
在一些实施例中，在603中，发起与调度请求相关的随机接入过程可以参照现有的发起随机接入过程的方法实施，例如具体可参考TSs 38.321中的随机接入过程，记载如下：
只要至少一个SR处于等待状态，MAC实体应针对每个处于等待状态的SR：
1>如果MAC实体没有为处于该等待状态的SR配置有效的PUCCH资源：
2>在SpCell上发起随机接入过程(参见第5.1节)并取消处于该等待状态的SR。
(As long as at least one SR is pending,the MAC entity shall for each pending SR:
1>if the MAC entity has no valid PUCCH resource configured for the pending SR:
2>initiate a Random Access procedure(see clause 5.1)on the SpCell and cancel the pending SR.)
在一些实施例中，在604中，该随机接入过程在以下至少一个情况下被停止：
(1)MAC PDU被发送且所述MAC PDU包括DSR MAC CE，所述DSR MAC CE包含直到该MAC PDU组装之前的最新触发DSR的事件的数据量和/或剩余时间，或者直到所述MAC PDU组装之时的最新触发DSR的事件的数据量和/或剩余时间；
(2)上行授权(UL grant)能容纳要发送的所有等待的数据；
(3)所有触发的延迟状态报告(DSR)都被取消；
(4)触发该调度请求(SR)的延迟状态报告(DSR)被取消。
在一些实施例中，在上述(1)中的触发DSR的事件例如基于门限触发DSR，具体如第一方面的实施例所述，此处不再赘述；或者，还可以为其他触发DSR的事件。触发DSR的事件的数据量可以为本申请第一方面的实施例所述的数据量，或者，还可以为其他数据量，本申请对此不作限制。
上述实施例中，在上述情况(1)至(4)下停止与调度请求相关的随机接入过程的方式可以分别被进行如下描述：
根据上述实施例，明确了与延迟状态报告(DSR)触发的调度请求(SR)相关的随机接入过程何时被停止，可以减少不必要的随机接入相关消息的发送，节约无线资源，降低UE功率消耗而省电，从而解决了现有技术中存在的问题。
第五方面的实施例
目前，缓存状态报告(Buffer status report，BSR)和延迟状态报告(Data status report，DSR)中都包括数据量，即data volume或buffer size或amount of data。发明人发现，目前还不清楚BSR与DSR是否能被包括在同一个MAC PDU中。
为解决上述问题，本申请提供一种信息处理方法，应用于终端设备。
图7是本申请实施例的信息处理方法的一示意图。如图7所示，该方法包括：
701，生成MAC PDU；
该MAC PDU包括延迟状态报告(DSR)和/或缓存状态报告(BSR)。
在一些实施例中，在701中，触发的延迟状态报告(DSR)可以与本申请第一方面的实施例中触发的延迟状态报告(DSR)相同，也可以不同，本申请不以此为限。
在一些实施例中，DSR和BSR不被包括在同一个MAC PDU中，此时，该MAC  PDU包括延迟状态报告(DSR)和缓存状态报告(BSR)中的一个。
在一些实施例中，在既触发了延迟状态报告(DSR)，又触发了缓存状态报告(BSR)时，根据DSR的优先级和BSR的优先级确定MAC PDU中包含DSR和BSR中的哪一个，例如将DSR和BSR中优先级高的一个包括在MAC PDU中。其中，DSR的优先级和BSR的优先级可以预先配置或定义。例如，在DSR的优先级和BSR的优先级被预先定义的情况下，延迟状态报告(DSR)的优先级高于常规(regular)BSR或周期BSR(periodic BSR)或填充(padding)BSR；或者，延迟状态报告(DSR)的优先级低于regular BSR，且高于周期BSR或padding BSR。再例如，DSR的优先级和BSR的优先级被网络设备配置的情况下，网络信令可以在RRC消息中指示DSR的优先级和BSR的优先级，或者指示DSR的优先级高于BSR的优先级，或者指示BSR的优先级高于DSR的优先级，等等。
由此，可以减少重复的数据量(data volume或buffer size或amount of data)信息的上报，提高无线资源利用率。
在一些实施例中，DSR和BSR可以被包括在同一个MAC PDU中。此时，该MAC PDU可以同时包括延迟状态报告(DSR)和缓存状态报告(BSR)。
例如，在既触发了延迟状态报告(DSR)，又触发了缓存状态报告(BSR)时，该DSR和该BSR被包括在同一个MAC PDU中。
由此，BSR和DSR过程独立进行，彼此不影响，实现简单。
第六方面的实施例
本申请实施例提供了一种信息发送装置，应用于终端设备，图8是该信息接收装置的一种示意图。该信息接收装置与本申请提供的第一方面的实施例中的信息接收方法基于同一发明构思产生的，解决问题的原理相似，因此信息接收装置的实施参见本申请提供的第一方面的实施例中的信息接收方法的实施，重复之处不再赘述。以下所使用的，术语“单元”或者“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的系统较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
如图8所示，所述信息接收装置包括：
第一触发单元801，其用于触发延迟状态报告；
发送单元802，其用于向网络设备发送所述延迟状态报告，所述延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
根据上述实施例，明确了如何确定与剩余时间关联的数据量，即该数据量包括终端设备的PDCP层和/或RLC层的与业务数据单元的剩余时间相关的数据量，从而解决了现有技术中存在的问题。
在一些实施例中，终端设备触发延迟状态报告的方式如第一方面的实施例所述，此处不再赘述。
在一些实施例中，终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量如第一方面的实施例所述，此处不再赘述。
在一些实施例中，对于PDCP层，由MAC层通知PDCP层以下信息的至少一个：
DSR MAC CE被发送时的时间，或者，DSR MAC CE被报告时的时间，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的时间，或者，DSR被触发时和DSR MAC CE被发送时的时间差，或者，DSR被触发时和DSR MAC CE被报告时的时间差，或者，DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差；和/或
对于RLC层，由MAC层和/或PDCP层通知RLC层以下信息的至少一个：
DSR MAC CE被发送时的时间，或者，DSR MAC CE被报告时的时间，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的时间，或者，DSR被触发时和DSR MAC CE被发送时的时间差，或者，DSR被触发时和DSR MAC CE被报告时的时间差，或者，DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差。
在上面的实施例中，DSR MAC CE被发送时或DSR MAC CE被报告时或DSR MAC CE被发送的PUSCH传输第一个符号时的时间可以是绝对时间，也可以是系统帧号(System Frame Number，SFN)和/或时隙号(slot number)和/或符号号(symbol number)。
在一些实施例中，在MAC层的DSR MAC CE中包括的数据量信息指示的与剩 余时间相关的数据量包括一个逻辑信道组的所有逻辑信道上的数据量(data volum或buffer status或amount of data)，该与剩余时间相关的数据量包括以下信息的至少一个：
在延迟状态报告被触发时，在逻辑信道组的所有逻辑信道上的数据量；
在DSR MAC CE被生成时或者被生成后，在逻辑信道组的所有逻辑信道上的数据量；
在DSR MAC PDU被组装(或被得到或被生成)时或者被组装(或被得到或被生成)后，在逻辑信道组的所有逻辑信道上的数据量；
在DSR MAC CE被发送时，在逻辑信道组的所有逻辑信道上的数据量；
在DSR被发送的PUSCH传输第一个符号时，在逻辑信道组的所有逻辑信道上的数据量。
在一些实施例中，对于RLC层，与RLC RDU的剩余时间相关的数据量还可包括：
当被上层丢弃的数据(如discardTimer超时被丢弃的数据)还未被包括在RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量不包括该被上层丢弃的数据；和/或
当被上层丢弃的数据已经包括在等待初传或重传的RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量包括该被上层丢弃的数据。
根据上述实施例，明确了如何确定与剩余时间关联的数据量，即该数据量包括终端设备的PDCP层和/或RLC层的与业务数据单元的剩余时间相关的数据量，从而解决了现有技术中存在的问题。
本申请实施例还提供一种信息接收装置，图9是该信息接收装置的一种示意图。该信息接收装置与本申请提供的第二方面的实施例中的信息接收方法基于同一发明构思产生的，解决问题的原理相似，因此信息接收装置的实施参见本申请提供的第二方面的实施例中的信息接收方法的实施，重复之处不再赘述。以下所使用的，术语“单元”或者“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的系统较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
如图9所示，该信息接收装置包括：
接收单元901，其用于接收终端设备发送的延迟状态报告，所述延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
根据上述实施例，网络设备接收终端设备发送的延迟状态报告，可获得该DSR中包含的数据量信息，即PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量，是的网络设备获知较为准确的缓存数据的紧急程度，进而分配合适的上行资源来传输时延紧急的数据，以保证业务的时延要求。
在一些实施例中，终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量如第一方面的实施例所述，此处不再赘述。
在一些实施例中，在MAC层的DSR MAC CE中包括的数据量信息指示的与剩余时间相关的数据量包括一个逻辑信道组的所有逻辑信道上的数据量(data volum或buffer status或amount of data)，该与剩余时间相关的数据量包括以下信息的至少一个：
(1)在延迟状态报告被触发时，在逻辑信道组的所有逻辑信道上的数据量；
(2)在DSR MAC CE被生成时或者被生成后，在逻辑信道组的所有逻辑信道上的数据量；
(3)在DSR MAC PDU被组装(或被得到或被生成)时或者被组装(或被得到或被生成)后，在逻辑信道组的所有逻辑信道上的数据量；
(4)在DSR MAC CE被发送时，在逻辑信道组的所有逻辑信道上的数据量；
(5)在DSR被发送的PUSCH传输第一个符号时，在逻辑信道组的所有逻辑信道上的数据量。
在一些实施例中，对于RLC层，与RLC RDU的剩余时间相关的数据量还可包括：
当被上层丢弃的数据(如discardTimer超时被丢弃的数据)还未包括在RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量不包括该被上层丢弃的数据；和/或
当被上层丢弃的数据已经包括在等待初传或重传的RLC data PDU中时，该RLC层的与业务数据单元的剩余时间相关的数据量包括该被上层丢弃的数据。
在一些实施例中，该装置还包括配置单元(未图示)，其用于为终端设备配置第一阈值和/或第二阈值，并将确定的阈值通知该终端设备。其中该第一阈值和第二阈值如第一方面的实施例所述，此处不再赘述。
根据上述实施例，网络设备接收终端设备发送的延迟状态报告，可获得该DSR中包含的数据量信息，即PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量，是的网络设备获知较为准确的缓存数据的紧急程度，进而分配合适的上行资源来传输时延紧急的数据，以保证业务的时延要求。
本申请实施例还提供一种信息接收装置，应用于终端设备，图10是该信息处理装置的一种示意图。该信息处理装置与本申请提供的第三方面的实施例中的信息处理方法基于同一发明构思产生的，解决问题的原理相似，因此信息处理装置的实施参见本申请提供的第三方面的实施例中的信息处理方法的实施，重复之处不再赘述。以下所使用的，术语“单元”或者“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的系统较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
如图10所示，该信息处理装置包括：
第二触发单元1001，其用于触发延迟状态报告；
第三触发单元1002，其用于触发调度请求；
第一处理单元1003，其用于取消该调度请求。
在一些实施例中，第二触发单元1001触发的延迟状态报告(DSR)可以与本申请第一方面的实施例中触发的延迟状态报告(DSR)相同，也可以不同，本申请不以此为限。
在一些实施例中，第三触发单元1002触发调度请求的过程可参照现有技术实施。
在一些实施例中，第一处理单元1003在以下至少一个情况下取消该调度请求：
(1)MAC PDU被发送且该MAC PDU包括DSR MAC CE，该DSR MAC CE包含直到该MAC PDU组装之前的最新触发DSR的事件的数据量和/或剩余时间，或 者该DSR MAC CE包含直到该MAC PDU组装之时的最新触发DSR的事件的数据量和/或剩余时间；
(2)上行授权(UL grant)能容纳要发送的所有等待的数据；
(3)所有触发的延迟状态报告(DSR)都被取消；
(4)触发该调度请求(SR)的延迟状态报告(DSR)被取消。
在一些实施例中，在上述(1)中的触发DSR的事件例如基于门限触发DSR，具体如第一方面的实施例所述，此处不再赘述；或者，还可以为其他触发DSR的事件。触发DSR的事件的数据量可以为本申请第一方面的实施例所述的数据量，或者，还可以为其他数据量，本申请对此不作限制。
根据上述实施例，明确了延迟状态报告(DSR)触发的调度请求(SR)何时被取消，可以减少不必要的SR的发送，节约SR发送所占用的资源，降低UE功率消耗而省电，从而解决了现有技术中存在的问题。
本申请实施例还提供一种信息接收装置，应用于终端设备，图11是该信息处理装置的一种示意图。该信息处理装置与本申请提供的第四方面的实施例中的信息处理方法基于同一发明构思产生的，解决问题的原理相似，因此信息处理装置的实施参见本申请提供的第四方面的实施例中的信息处理方法的实施，重复之处不再赘述。以下所使用的，术语“单元”或者“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的系统较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
如图11所示，该方法包括：
第四触发单元1101，其用于触发延迟状态报告；
第五触发单元1102，其用于触发调度请求；
第六触发单元1103，其用于发起与调度请求相关的随机接入过程；
第二处理单元1104，其用于停止该随机接入过程。
在一些实施例中，第四触发单元1101触发的延迟状态报告(DSR)可以与本申请第一方面的实施例中触发的延迟状态报告(DSR)相同，也可以不同，本申请不以此为限。
在一些实施例中，第五触发单元1102触发调度请求的过程可以是例如终端设备 没有可用的上行资源来发送该触发的DSR，或者可用的上行资源无法容纳DSR MAC CE加上其子头，或者可用的上行资源晚于上行业务的时延要求等等，终端设备将触发调度请求，在PUCCH中向网络设备发送调度请求，请求网络设备发送UL grant来分配上行资源，以便终端设备通过该UL grant指示的上行资源进行延迟状态报告的上报。
在一些实施例中，第六触发单元1103发起与调度请求相关的随机接入过程可以参照现有的发起随机接入过程的方法实施。
在一些实施例中，第二处理单元1104在以下至少一个情况下停止该随机接入过程：
(1)MAC PDU被发送且所述MAC PDU包括DSR MAC CE，所述DSR MAC CE包含直到该MAC PDU组装之前的最新触发DSR的事件的数据量和/或剩余时间，或者直到所述MAC PDU组装之时的最新触发DSR的事件的数据量和/或剩余时间；
(2)上行授权(UL grant)能容纳要发送的所有等待的数据；
(3)所有触发的延迟状态报告(DSR)都被取消；
(4)触发该调度请求(SR)的延迟状态报告(DSR)被取消。
在一些实施例中，在上述(1)中的触发DSR的事件例如基于门限触发DSR，具体如第一方面的实施例所述，此处不再赘述；或者，还可以为其他触发DSR的事件。触发DSR的事件的数据量可以为本申请第一方面的实施例所述的数据量，或者，还可以为其他数据量，本申请对此不作限制。
根据上述实施例，明确了与延迟状态报告(DSR)触发的调度请求(SR)相关的随机接入过程何时被停止，可以减少不必要的随机接入相关消息的发送，节约无线资源，降低UE功率消耗而省电，从而解决了现有技术中存在的问题。
本申请实施例还提供一种信息接收装置，应用于终端设备，图12是该信息处理装置的一种示意图。该信息处理装置与本申请提供的第五方面的实施例中的信息处理方法基于同一发明构思产生的，解决问题的原理相似，因此信息处理装置的实施参见本申请提供的第五方面的实施例中的信息处理方法的实施，重复之处不再赘述。以下所使用的，术语“单元”或者“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的系统较佳地以软件来实现，但是硬件，或者软件和硬件的组 合的实现也是可能并被构想的。
如图12所示，该装置包括：
第三处理单元1201，生成MAC PDU；
所述MAC PDU包括延迟状态报告(DSR)和/或缓存状态报告(BSR)。
在一些实施例中，第三处理单元1201触发的延迟状态报告(DSR)可以与本申请第一方面的实施例中触发的延迟状态报告(DSR)相同，也可以不同，本申请不以此为限。
在一些实施例中，DSR和BSR不能被包括在同一个MAC PDU中，此时，该MAC PDU包括最多包括延迟状态报告(DSR)和缓存状态报告(BSR)中的一个。
在一些实施例中，当既触发了延迟状态报告(DSR)，又触发了缓存状态报告(BSR)时，根据DSR的优先级和BSR的优先级确定MAC PDU中包含DSR和BSR中的哪一个，例如将DSR和BSR中优先级高的一个包括在MAC PDU中。其中，DSR的优先级和BSR的优先级可以预先配置或定义。例如，在DSR的优先级和BSR的优先级被预先定义的情况下，延迟状态报告(DSR)的优先级高于常规(regular)BSR或周期BSR(periodic BSR)或填充(padding)BSR；或者，延迟状态报告(DSR)的优先级低于regular BSR，且高于周期BSR或padding BSR。再例如，DSR的优先级和BSR的优先级被网络设备配置的情况下，网络信令可以在RRC消息中指示DSR的优先级和BSR的优先级，或者指示DSR的优先级高于BSR的优先级，或者指示BSR的优先级高于DSR的优先级，等等。
由此，可以减少重复的数据量(data volume或buffer size或amount of data)信息的上报，提高无线资源利用率。
在一些实施例中，DSR和BSR可以被包括在同一个MAC PDU中。此时，该MAC PDU可以同时包括延迟状态报告(DSR)和缓存状态报告(BSR)。例如，当既触发了延迟状态报告(DSR)，又触发了缓存状态报告(BSR)时，该DSR和该BSR被包括在同一个MAC PDU中。由此，BSR和DSR过程独立进行，彼此不影响，实现简单。
第七方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一至五方面的实施例相 同的内容不再赘述。
在一些实施例中，通信系统100至少可以包括：网络设备101和/或终端设备102，终端设备102触发延迟状态报告，以及向网络设备101发送所述延迟状态报告；网络设备101接收终端设备102发送的该延迟状态报告。该延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
在一些实施例中，上述延迟状态报告的实施方式可以参考第一方面和第二方面的实施例，此处不再赘述。
本申请实施例还提供一种网络设备，例如可以是基站，但本申请不限于此，还可以是其他的网络设备。
图13是本申请实施例的网络设备的构成示意图。如图13所示，网络设备1300可以包括：处理器1310(例如中央处理器CPU)和存储器1320；存储器1320耦合到处理器1310。其中该存储器1320可存储各种数据；此外还存储信息处理的程序1330，并且在处理器1310的控制下执行该程序1330。
例如，处理器1310可以被配置为执行程序而实现如第二方面的实施例所述的信息接收方法。例如处理器1310可以被配置为进行如下的控制：接收终端设备发送的延迟状态报告，所述延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
此外，如图13所示，网络设备1300还可以包括：收发机1340和天线1350等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1300也并不是必须要包括图13中所示的所有部件；此外，网络设备1300还可以包括图13中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种终端设备，但本申请不限于此，还可以是其他的设备。
图14是本申请实施例的终端设备的示意图。如图14所示，该终端设备1400可以包括处理器1410和存储器1420；存储器1420存储有数据和程序，并耦合到处理器1410。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
例如，处理器1410可以被配置为执行程序而实现如第一方面的实施例所述的信息发送方法。例如处理器1410可以被配置为进行如下的控制：触发延迟状态报告；向网络设备发送所述延迟状态报告，所述延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
如图14所示，该终端设备1400还可以包括：通信模块1430、输入单元1440、显示器1450、电源1460。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1400也并不是必须要包括图14中所示的所有部件，上述部件并不是必需的；此外，终端设备1400还可以包括图14中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第一方面的实施例所述的信息发送方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得终端设备执行第一方面的实施例所述的信息发送方法。
本申请实施例还提供一种计算机程序，其中当在网络设备中执行所述程序时，所述程序使得所述网络设备执行第二方面的实施例所述的信息接收方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得网络设备执行第二方面的实施例所述的信息接收方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存 储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
1.一种信息处理方法，应用于终端设备，其中，所述方法包括：
触发延迟状态报告；
触发调度请求；
发起与调度请求相关的随机接入过程；
停止所述随机接入过程。
2.根据附记1所述的方法，其中，所述随机接入过程在以下至少一个情况下被停止：
MAC PDU被发送且所述MAC PDU包括DSR MAC CE，所述DSR MAC CE包含直到该MAC PDU组装之前的最新触发DSR的事件的数据量和/或剩余时间，或者直到所述MAC PDU组装之时的最新触发DSR的事件的数据量和/或剩余时间；
UL grant能容纳要发送的所有等待的数据；
所有触发的延迟状态报告都被取消；
触发所述调度请求的延迟状态报告被取消。
3.一种信息处理方法，应用于终端设备，其中，所述方法包括：
生成MAC PDU；
所述MAC PDU包括延迟状态报告(DSR)和/或缓存状态报告(BSR)。
4.根据附记3所述的方法，其中，所述MAC PDU包括延迟状态报告(DSR)和缓存状态报告(BSR)中的一个。
5.根据附记4所述的方法，其中，当既触发了延迟状态报告，又触发了缓存状态报告时，
所述延迟状态报告(DSR)的优先级高于常规(regular)BSR或周期BSR(periodic BSR)或填充(padding)BSR；或者
所述延迟状态报告(DSR)的优先级低于regular BSR，且高于周期BSR或padding BSR。

Claims (20)

  1. 一种信息发送装置，应用于终端设备，其中，所述装置包括：
    第一触发单元，其用于触发延迟状态报告；
    发送单元，其用于向网络设备发送所述延迟状态报告，所述延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
  2. 根据权利要求1所述的装置，其中，对于RLC层，业务数据单元的剩余时间由上层指示。
  3. 根据权利要求1所述的装置，其中，所述与业务数据单元的剩余时间相关的数据量包括：在所述业务数据单元的剩余时间满足预设条件时的业务数据单元的数据量。
  4. 根据权利要求3所述的装置，其中，所述预设条件包括：业务数据单元的剩余时间小于或等于第一阈值；或者
    业务数据单元的剩余时间大于或等于第一阈值；或者
    业务数据单元的剩余时间在第一阈值和第二阈值之间。
  5. 根据权利要求3所述的装置，其中，所述第一阈值和/或所述第二阈值是预定义的或者网络配置的。
  6. 根据权利要求3所述的装置，其中，所述与业务数据单元的剩余时间相关的数据量包括：与在延迟状态报告被触发时的业务数据单元的剩余时间相关的数据量。
  7. 根据权利要求6所述的装置，其中，所述第一阈值为网络配置的逻辑信道组(LCG)触发DSR的门限。
  8. 根据权利要求3所述的装置，其中，所述与业务数据单元的剩余时间相关的数据量包括：与在延迟状态报告(Delay Status Report，DSR)MAC CE被生成时的业务数据单元的剩余时间相关的数据量。
  9. 根据权利要求8所述的装置，其中，所述第一阈值为DSR MAC CE被生成时的剩余时间的值，或者，网络配置的逻辑信道组(LCG)触发DSR的门限与DSR被触发时和DSR MAC CE被生成时的时间差的差值。
  10. 根据权利要求8所述的装置，其中，
    对于PDCP层，由MAC层通知PDCP层DSR MAC CE被生成时的绝对时间，或者，包含所述DSR MAC CE的MAC PDU被组装时的绝对时间，或者，DSR被触发时和DSR MAC CE被生成时的时间差，或者，DSR被触发时和所述MAC PDU被组装时的时间差；和/或
    对于RLC层，由MAC层和/或PDCP层通知RLC层DSR MAC CE被生成时的绝对时间，或者，包含所述DSR MAC CE的MAC PDU被组装时的绝对时间，或者，DSR被触发时和DSR MAC CE被生成时的时间差，或者，DSR被触发时和所述MAC PDU被组装时的时间差。
  11. 根据权利要求2所述的装置，其中，所述与业务数据单元的剩余时间相关的数据量包括：与在DSR MAC CE被发送时的业务数据单元的剩余时间相关的数据量。
  12. 根据权利要求11所述的装置，其中，所述第一阈值为DSR MAC CE被发送时的剩余时间的值，或者，DSR MAC CE被报告时的剩余时间的值，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的剩余时间的值，或者，网络配置的逻辑信道组触发DSR的门限与DSR被触发时和DSR MAC CE被发送时的时间差的差值，或者，网络配置的逻辑信道组触发DSR的门限与DSR被触发时和DSR MAC CE被报告时的时间差的差值，或者，网络配置的逻辑信道组触发DSR的门限与DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差的差值。
  13. 根据权利要求12所述的装置，其中，
    对于PDCP层，由MAC层通知PDCP层以下信息的至少一个：
    DSR MAC CE被发送时的绝对时间，或者，DSR MAC CE被报告时的绝对时间，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的绝对时间，或者，DSR被触发时和DSR MAC CE被发送时的时间差，或者，DSR被触发时和DSR MAC CE被报告时的时间差，或者，DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差；和/或
    对于RLC层，由MAC层和/或PDCP层通知RLC层以下信息的至少一个：
    DSR MAC CE被发送时的绝对时间，或者，DSR MAC CE被报告时的绝对时间，或者，DSR MAC CE被发送的PUSCH传输第一个符号时的绝对时间，或者，DSR被触发时和DSR MAC CE被发送时的时间差，或者，DSR被触发时和DSR MAC CE 被报告时的时间差，或者，DSR被触发时和DSR MAC CE被发送的PUSCH传输第一个符号时的时间差。
  14. 根据权利要求4所述的装置，其中，所述第二阈值是业务数据单元的剩余时间的索引对应的取值范围的下限。
  15. 根据权利要求2所述的装置，其中，所述第一阈值的数量为至少一个，所述数据量信息的数量也为至少一个。
  16. 根据权利要求1所述的装置，其中，在MAC层的DSR MAC CE中包括的数据量信息，用于指示以下信息的至少一个：
    在延迟状态报告被触发时，在逻辑信道组的所有逻辑信道上的数据量；
    在DSR MAC CE被生成时或者被生成后，在逻辑信道组的所有逻辑信道上的数据量；
    在DSR MAC PDU被组装时或者被组装后，在逻辑信道组的所有逻辑信道上的数据量；
    在DSR MAC CE被发送时，在逻辑信道组的所有逻辑信道上的数据量；
    在DSR被发送的PUSCH传输第一个符号时，在逻辑信道组的所有逻辑信道上的数据量。
  17. 根据权利要求1所述的装置，其中，对于RLC层，当被上层丢弃的数据还未包括在RLC data PDU中时，所述RLC层的与业务数据单元的剩余时间相关的数据量不包括所述被上层丢弃的数据；和/或
    当被上层丢弃的数据已经包括在等待初传或重传的RLC data PDU中时，所述RLC层的与业务数据单元的剩余时间相关的数据量包括所述被上层丢弃的数据。
  18. 一种信息接收装置，应用于网络设备，其中，所述装置包括：
    接收单元，其用于接收终端设备发送的延迟状态报告，所述延迟状态报告包括数据量信息，所述数据量信息包括终端设备的PDCP层的与业务数据单元(PDCP SDU)的剩余时间相关的数据量和/或RLC层的与业务数据单元(RLC SDU)的剩余时间相关的数据量。
  19. 一种信息处理装置，应用于终端设备，其中，所述装置包括：
    第二触发单元，其用于触发延迟状态报告；
    第三触发单元，其用于触发调度请求；
    第一处理单元，其用于取消所述调度请求。
  20. 根据权利要求19所述的装置，其中，所述调度请求在以下至少一个情况下被取消：
    MAC PDU被发送且所述MAC PDU包括DSR MAC CE，所述DSR MAC CE包含直到所述MAC PDU组装之前的最新触发DSR的事件的数据量和/或剩余时间，或者直到所述MAC PDU组装之时的最新触发DSR的事件的数据量和/或剩余时间；
    UL grant能容纳要发送的所有等待的数据；
    所有触发的延迟状态报告都被取消；
    触发所述调度请求的延迟状态报告被取消。
PCT/CN2023/122926 2023-09-28 2023-09-28 一种信息发送、接收和处理方法、装置、通信系统 Pending WO2025065632A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380102038.7A CN121866806A (zh) 2023-09-28 2023-09-28 一种信息发送、接收和处理方法、装置、通信系统
PCT/CN2023/122926 WO2025065632A1 (zh) 2023-09-28 2023-09-28 一种信息发送、接收和处理方法、装置、通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/122926 WO2025065632A1 (zh) 2023-09-28 2023-09-28 一种信息发送、接收和处理方法、装置、通信系统

Publications (1)

Publication Number Publication Date
WO2025065632A1 true WO2025065632A1 (zh) 2025-04-03

Family

ID=95204571

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/122926 Pending WO2025065632A1 (zh) 2023-09-28 2023-09-28 一种信息发送、接收和处理方法、装置、通信系统

Country Status (2)

Country Link
CN (1) CN121866806A (zh)
WO (1) WO2025065632A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN121174198A (zh) * 2025-11-21 2025-12-19 荣耀终端股份有限公司 一种通信方法及相关设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110149718A (zh) * 2018-02-14 2019-08-20 华为技术有限公司 数据发送的方法和通信设备
WO2023012914A1 (ja) * 2021-08-03 2023-02-09 株式会社Ｎｔｔドコモ 端末および無線通信方法
WO2023126857A1 (en) * 2021-12-30 2023-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Design of delay-aware bsr for xr applications

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110149718A (zh) * 2018-02-14 2019-08-20 华为技术有限公司 数据发送的方法和通信设备
WO2023012914A1 (ja) * 2021-08-03 2023-02-09 株式会社Ｎｔｔドコモ 端末および無線通信方法
WO2023126857A1 (en) * 2021-12-30 2023-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Design of delay-aware bsr for xr applications

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LINHAI HE, QUALCOMM INCORPORATED: "BSR and delay status report for XR", 3GPP DRAFT; R2-2304711; TYPE DISCUSSION; NR_XR_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Incheon, KR; 20230522 - 20230526, 12 May 2023 (2023-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052313944 *
LINHAI HE, QUALCOMM INCORPORATED: "BSR enhancements for XR", 3GPP DRAFT; R2-2302515; TYPE DISCUSSION; NR_XR_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20230417 - 20230426, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052288927 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN121174198A (zh) * 2025-11-21 2025-12-19 荣耀终端股份有限公司 一种通信方法及相关设备
CN121174198B (zh) * 2025-11-21 2026-03-27 荣耀终端股份有限公司 一种通信方法及相关设备

Also Published As

Publication number Publication date
CN121866806A (zh) 2026-04-14

Similar Documents

Publication Publication Date Title
US20250386240A1 (en) Methods and apparatuses for a protocol data unit (pdu) set delay status report
CN103369509B (zh) 一种缓存状态上报方法及终端设备
WO2021022508A1 (zh) 边链路调度请求的触发方法、装置和系统
CN114342535B (zh) 上行信号的发送和接收方法以及装置
US8854999B2 (en) Method and arrangement in a wireless communication system
KR20210037695A (ko) 데이터를 송신하기 위한 방법 및 장치, 및 통신 시스템
US20250392949A1 (en) Methods and apparatuses for a buffer status report
WO2022205239A1 (zh) 边链路非连续接收命令的触发方法、装置和系统
CN104823507B (zh) 通讯方法和设备
WO2020087289A1 (zh) 一种资源配置方法、网络设备及终端设备
US20250374122A1 (en) Data processing method and apparatus
WO2025065632A1 (zh) 一种信息发送、接收和处理方法、装置、通信系统
WO2021087926A1 (zh) 上行信号的发送和接收方法以及装置
WO2024092619A1 (zh) 延迟信息上报的方法和装置
WO2024168672A1 (zh) 数据处理方法和装置
WO2021138955A1 (zh) 通知发送时间信息的方法以及装置
WO2024168579A1 (zh) 信息处理方法、装置以及通信系统
KR20260052171A (ko) 정보 송신, 수신, 및 처리 방법 및 장치, 및 통신 시스템
WO2025091307A1 (zh) 一种信息处理装置、方法和通信系统
WO2025160896A1 (zh) 延迟信息的报告和接收方法、装置和通信系统
WO2025025209A1 (zh) 信息发送方法和装置
WO2025025213A1 (zh) 不被使用的发送时机的指示方法和装置
WO2020191660A1 (zh) 数据发送和接收方法以及装置
WO2025020164A1 (zh) 用于指示上行数据突发结束的方法和装置
WO2025065648A1 (zh) 未使用的传输时机的指示方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23953776

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 1020267008883

Country of ref document: KR

Free format text: ST27 STATUS EVENT CODE: A-0-1-A10-A15-NAP-PA0105 (AS PROVIDED BY THE NATIONAL OFFICE)

WWE Wipo information: entry into national phase

Ref document number: 1020267008883

Country of ref document: KR