Communication device and method

Abstract

The embodiment of the invention relates to a communication device and method. A terminal device receives a configuration for DSR from a network device. If the condition for triggering the DSR is satisfied, the terminal device triggers the DSR. If the condition for cancelling the DSR is satisfied, the terminal device cancels the DSR. In this manner, the DSR may be managed in a well-defined manner. The DSR may be transmitted as soon as possible, and the transmission delay of the delay data may be shortened.

Description

Technical Field

[0001] Embodiments of this disclosure generally relate to the field of telecommunications, and particularly to methods, apparatus, and computer storage media for communication of delay status reports (DSR). Background Technology

[0002] Currently, DSR (Cache Status Report) is under discussion for better scheduling of latency-sensitive services. DSR refers to a report on the status of latency-sensitive data in the cache. It has been agreed that a separate Media Access Control (MAC) CE element can be defined for DSR, which is not coupled with Cache Status Report (BSR). However, in this case, the DSR solution is still incomplete and requires further development. Summary of the Invention

[0003] In general, embodiments of this disclosure provide methods, apparatus, and computer storage media for communication of DSR.

[0004] In a first aspect, a terminal device is provided. The terminal device includes a processor configured to: receive a configuration from a network device for a report on the status of delayed data; trigger a report on the status of delayed data based on the condition that a condition for triggering the report on the status of delayed data is met; and cancel a report on the status of delayed data based on the condition that a condition for canceling the report on the status of delayed data is met.

[0005] In a second aspect, a network device is provided. The network device includes a processor configured to: configure the network device to send a report on the status of delayed data to an end device; and configure the network device to receive a MAC CE report on the status of delayed data from the end device.

[0006] In a third aspect, a communication method is provided. The method includes: configuring a terminal device to receive a report from a network device regarding the status of delayed data; triggering the report of the status of delayed data based on the condition that a condition for triggering the report of the status of delayed data is met; and canceling the report of the status of delayed data based on the condition that a condition for canceling the report of the status of delayed data is met.

[0007] In a fourth aspect, a communication method is provided. The method includes: configuring a network device to send a report on the status of delayed data to a terminal device; and a MAC CE (Machine-Controlled Component Equivalent) for receiving the report on the status of delayed data from the terminal device.

[0008] In a fifth aspect, a computer-readable medium having instructions stored thereon is provided. When executed on at least one processor, the instructions cause the at least one processor to perform the method according to a third or fourth aspect of this disclosure.

[0009] Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of some embodiments of this disclosure in the accompanying drawings, wherein:

[0011] Figure 1 The illustration shows an example communication network in which some embodiments of the present disclosure may be implemented;

[0012] Figure 2 The illustration shows a schematic diagram illustrating a communication process according to an embodiment of the present disclosure;

[0013] Figure 3 The illustration shows an example communication method implemented at a terminal device according to some embodiments of the present disclosure;

[0014] Figure 4 The illustrations depict example communication methods implemented at a network device according to some embodiments of the present disclosure; and

[0015] Figure 5 This is a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0016] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0017] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art understand and implement this disclosure, and do not constitute any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various other ways besides those described below.

[0018] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0019] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, ultra-reliable low-latency communication (URLLC) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, vehicular equipment for V2X communication (where X represents a pedestrian, vehicle, or infrastructure / network), devices for integrated access and backhaul (IAB), spacecraft or airborne vehicles in non-terrestrial networks (NTN) (including satellites and high-altitude platforms (HAPs)) (including unmanned aerial vehicle systems (UAS)), extended reality (XR) devices (including different types of reality such as augmented reality (AR), mixed reality (MR), and virtual reality (VR)), unmanned aerial vehicles (UAVs) commonly referred to as drones (which are aircraft without any human pilots), devices on high-speed trains (HSTs), or image capture devices (such as digital cameras), sensors, gaming devices, music storage and playback devices, or internet devices that enable wireless or wired internet access and browsing, etc. The "terminal device" may also have "multicast / broadcast" features to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, wireless services, software delivery over wireless, group communications, and IoT applications. It may also include one or more Subscriber Identity Modules (SIMs) (referred to as multiSIMs). The term "terminal device" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0020] As used herein, the term "network device" refers to a device capable of providing or hosting a cell or coverage area in which terminal devices can communicate. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), next-generation NodeBs (gNBs), Transmitter Receiver Points (TRPs), Remote Radio Units (RRUs), Radio Heads (RHs), Remote Radio Heads (RRHs), IAB nodes, low-power nodes (such as femtonodes, piconodes), reconfigurable smart surfaces (RISs), etc.

[0021] Terminal devices or network devices can have artificial intelligence (AI) or machine learning capabilities. It typically includes a model that has been trained on a specific function from a large amount of collected data and can be used to predict some kind of information.

[0022] Terminal or network devices can operate within several frequency ranges, such as FR1 (410 MHz to 7125 MHz), FR2 (24.25 GHz to 71 GHz), bands above 100 GHz, and terahertz (THz). They can also operate on licensed / unlicensed / shared spectrum. In multiple wireless dual connectivity (MR-DC) applications, terminal devices can have more than one connection with network devices. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-duplex modes.

[0023] The embodiments of this disclosure can be executed in test equipment, such as signal generators, signal analyzers, spectrum analyzers, network analyzers, test terminal equipment, test network equipment, and channel simulators.

[0024] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first and second network devices may be a master node, and the other a slave node. The first and second network devices may use different Radio Access Technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs may be sent to the terminal device from at least one of the first or second network devices. In one embodiment, first information may be sent from the first network device to the terminal device, and second information may be sent directly or via the first network device from the second network device to the terminal device. In one embodiment, information related to configuration of the terminal device configured by the second network device may be sent via the first network device from the second network device. Information related to reconfiguration of the terminal device configured by the second network device may be sent directly or via the first network device from the second network device to the terminal device.

[0025] As used herein, unless the context explicitly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well. The term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “an embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The terms “first,” “second,” etc., may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0026] In some examples, values, processes, or devices are referred to as “best,” “lowest,” “highest,” “smallest,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a selection can be made from a number of functional alternatives used, and that such a selection is not necessarily better, smaller, higher, or otherwise preferred than other options.

[0027] In the context of this disclosure, the term "above" may be used interchangeably with "higher than or equal to" or "greater than or equal to". The term "below" may be used interchangeably with "lower than or equal to" or "less than or equal to".

[0028] In the context of this disclosure, the term "DSR" may be used interchangeably with "report of the status of delayed data in the buffer" or "report of the status of delayed data". In the context of this disclosure, the term "delayed data" may refer to data whose remaining latency budget is below a configured threshold. The term "status of delayed data" may also be referred to as latency buffer status. Latency buffer status may include at least latency buffer size and / or remaining latency information. For DSR, the network and UE may only be concerned with logical channels used for latency-sensitive services. The term "MAC CE for DSR" may also be referred to as DSR MAC CE or BSR MAC CE with latency status information.

[0029] As is well known, some services, such as Extended Reality (XR) services, can have stringent latency requirements. Since any data exceeding the Packet Delay Budget (PDB) or Protocol Data Unit (PDU) Set Delay Budget (PSDB) may be useless, uplink (UL) resources should be allocated beforehand. When the remaining latency budget is explicitly provided to the network, the network has the flexibility to schedule UL grants taking into account the remaining latency budget, provided it does not exceed the PDB or PSDB, and thus improves capacity by prioritizing the scheduling of data with corresponding latency.

[0030] Enhancements have been proposed to specify the capacity related to delay status reporting of cached data in the UL. It has been agreed to define a separate MAC CE (e.g., remaining latency and associated data volume) for the DSR, so that the DSR is not coupled to the BSR.

[0031] Embodiments of this disclosure provide a communication solution for Delayed Data Reception (DSR). In this solution, a terminal device receives a configuration from a network device for reporting the status of delayed data. If the conditions for triggering a delayed data status report are met, the terminal device triggers the delayed data status report. If the conditions for canceling a delayed data status report are met, the terminal device cancels the delayed data status report. In this way, DSRs can be managed in a well-defined manner. DSRs can be sent as quickly as possible, and the transmission delay of delayed data can be shortened.

[0032] The principles and implementation of this disclosure will now be described in detail with reference to the accompanying drawings. Examples of communication networks

[0033] Figure 1 The illustration shows a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure may be implemented. For example... Figure 1 As shown, the communication network 100 may include a terminal device 110 and a network device 120. In some embodiments, the terminal device 110 may be served by the network device 120.

[0034] It should be understood that Figure 1 The number of terminal devices and network devices given are for illustrative purposes and do not impose any limitation on this disclosure. Communication network 100 may include any suitable number of network devices and / or terminal devices suitable for implementing this disclosure.

[0035] like Figure 1 As shown, terminal device 110 can communicate with network device 120 via a channel such as a wireless communication channel. Communication in communication network 100 can conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE Evolution, LTE-A Advanced, New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Embodiments of this disclosure can be implemented according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, 5.5G, 5G Advanced Networks, or sixth-generation (6G) networks.

[0036] In some cases, when terminal device 110 has packets (e.g., a set of PDUs) and the remaining latency time for the packets is almost exhausted, terminal device 110 may need to quickly notify network device 120 so that network device 120 knows that terminal device 110 has delayed or urgent packets that need to be scheduled for transmission. In this case, terminal device 110 may need to send a DSR to network device 120.

[0037] Due to various reasons, such as temporary congestion of the radio link, DSRs can be retransmitted. If a DSR is not retransmitted in a timely manner, the remaining latency budget for data (e.g., Serving Data Units (SDUs) or PDU sets) may be exhausted, and the retransmitted DSR may be useless. Furthermore, to avoid frequent DSR transmissions, the Media Access Control (MAC) entity of the terminal device can be prohibited from transmitting DSRs for a period of time after the DSR has been transmitted. Additionally, the priority of the MAC CE used for DSRs needs to be considered when performing the Logical Channel Prioritization (LCP) procedure. Moreover, due to drop operations (e.g., network-triggered drops caused by congestion, or Packet Data Convergence Protocol (PDCP) drop timers expiring) or other reasons, there may be no delayed data in the UL buffer. In this case, all triggered DSRs need to be canceled to conserve radio resources.

[0038] In view of the above, embodiments of this disclosure provide a communication solution for DSR to overcome the above and other potential problems. Reference will be made to... Figure 2 Please describe the solution in detail. Example implementation of DSR management

[0039] Figure 2 The illustration shows a schematic diagram illustrating a communication process 200 according to an embodiment of the present disclosure. For discussion purposes, reference will be made to... Figure 1 Describe process 200. Process 200 may involve, for example, Figure 1 The terminal device 110 and network device 120 are shown. It should be understood that... Figure 2 The steps and their order are for illustrative purposes only and are not intended to be limiting. For example, the order of the steps can be changed. Some steps can be omitted, or any suitable additional steps can be added.

[0040] like Figure 2 As shown, terminal device 110 can send capability information of terminal device 110 to network device 120. In some embodiments, terminal device 110 can send capability information via Radio Resource Control (RRC) signaling such as a UE Capability Information message. It should be understood that any other suitable method is also possible.

[0041] In some embodiments, capability information may include information indicating whether terminal device 110 supports reporting of the status of delayed data. For example, capability information may include information indicating whether terminal device 110 supports reporting of the status of delayed data via MAC CE for DSR.

[0042] In some embodiments, the capability information may include information indicating the maximum number of logical channel groups (LCGs) for which the terminal device 110 supports reporting delayed data. For example, the capability information may include information indicating the maximum number of LCGs for which the terminal device 110 supports reporting delayed data in the MAC CE.

[0043] In some embodiments, capability information may include information indicating whether terminal device 110 supports a delay timer for a scheduling request (SR), which is triggered by a report of the status of delayed data for a logical channel (LCH). For example, capability information may include information indicating whether terminal device 110 supports a logical channel SR delay timer for a DSR.

[0044] It should be understood that any combination of the above capability information is also feasible. Based on the reported UE capabilities, the network can appropriately configure DSR operations.

[0045] Continue to refer to Figure 2 Network device 120 can send 220 a configuration for a status report (i.e., DSR) for delayed data to terminal device 110. For example, terminal device 110 can send this configuration via RRC signaling. It should be understood that any other suitable method is also possible.

[0046] In some embodiments, network device 120 may configure a first timer for DSR retransmission. Herein, the first timer may also be referred to as a DSR retransmission timer (e.g., retxDSR-Timer or retxBSR-timer for DSR retransmission). In some embodiments, this configuration may include a first set of values ​​(i.e., one or more values) for the first timer. Each value in the first set of values ​​is lower than a first predetermined value. In other words, the first timer is short.

[0047] For example, after the MAC CE for DSR is sent, the terminal device is expected to receive UL authorization as soon as possible. If UL authorization is not received within a time period (e.g., a first timer), the terminal device can resend the MAC CE for DSR. Since the MAC CE for DSR also has strict latency requirements, the first timer should be short enough to reduce latency.

[0048] In some embodiments, the first predetermined value may be 100 subframes. It should be understood that this is merely an example, and any other suitable value or unit is also possible. For illustration, an example configuration of the DSR retransmission timer can be described as follows. DSR-Config ::= SEQUENCE { retxDSR-Timer ENUMERATED {sf0, sf1 / 2, sf1,sf2, sf4, sf5, sf8, sf10, sf15, sf16, sf20, sf30, sf40, sf50, sf80 sf100} / / Values ​​in subframes. The value sf1 corresponds to 1 subframe, the value sf2 corresponds to 2 subframes, and so on. }

[0049] In this example, the information element (IE) "DSR-Config" indicates the DSR configuration, and the IE "retxDSR-Timer" indicates the DSR retransmission timer. The value of the DSR retransmission timer can include 0, 1 / 2 subframes, 1 subframe, 2 subframes, 4 subframes, 5 subframes, 8 subframes, 10 subframes, 15 subframes, 16 subframes, 20 subframes, 30 subframes, 40 subframes, 50 subframes, 80 subframes, or 100 subframes. It should be understood that these values ​​are merely examples and do not constitute a limitation of this application.

[0050] In this way, DSRs can be sent or retransmitted without too much delay, thus reducing the latency of DSR transmission or retransmission.

[0051] In some embodiments, network device 120 may be configured with a second timer to prohibit the triggering or transmission of DSR. This second timer may also be referred to herein as a DSR prohibition timer (e.g., dsr-ProhibitTimer) or a DSR delay timer. In some embodiments, this configuration may include a second set of values ​​(i.e., one or more values) for the second timer. Each value in the second set of values ​​is lower than a second predetermined value. In other words, the second timer is short.

[0052] For example, to avoid frequent DSR transmissions, terminal devices can be prohibited from sending DSRs for a period of time after the DSR has been sent. The second timer should be short enough to reduce latency.

[0053] In some embodiments, the second predetermined value can be 100ms. It should be understood that this is merely an example, and any other suitable value or unit is also possible. For illustration, an example configuration for disabling the DSR timer can be described as follows. DSR-Config ::= SEQUENCE { dsr-ProhibitTimer ENUMERATED {sf0, sf0dot5,sf1, sf2, sf4, sf5, sf8, sf10, sf15, sf16, sf20, sf30, sf40, sf50, sf80,sf100}, / / Values ​​in units of the number of subframes used for DSR reporting. The value sf1 corresponds to 1 subframe, the value sf2 corresponds to 2 subframes, and so on. }

[0054] In this example, the information element (IE) "DSR-Config" indicates the DSR configuration, and the IE "dsr-ProhibitTimer" indicates the DSR prohibition timer. The value of the DSR prohibition timer can include 0, 0.5ms, 1ms, 2ms, 4ms, 5ms, 8ms, 10ms, 15ms, 16ms, 20ms, 30ms, 40ms, 50ms, 80ms, or 100ms. It should be understood that these values ​​are merely examples and do not constitute a limitation of this application.

[0055] In this way, frequent DSR transmissions can be avoided, and the latency of DSR transmissions can be reduced at the same time.

[0056] Continue to refer to Figure 2 Terminal device 110 can perform management of 230 DSR (e.g., triggering, canceling, transmitting or retransmitting) based on this configuration.

[0057] refer to Figure 2 In some embodiments, if the DSR has been triggered and not canceled, and the available UL resource set for transmission is sufficient to accommodate the MAC CE plus the MAC CE subheader for the DSR, then terminal device 110 may start or restart the 231 DSR retransmission timer. If no UL authorization is received during the operation of the DSR retransmission timer, terminal device 110 may retransmit the 232 DSR.

[0058] For illustration, the example process can be described as follows. MAC entities should: 1> If the Delayed Status Reporting process determines that at least one DSR has been triggered and not canceled: 2> If the uplink shared channel (UL-SCH) resource is available for a new transmission, and the UL-SCH resource is sufficient to accommodate the MAC CE for DSR along with its sub-header due to logical channel priority ordering: 3> Instructions for the reuse and assembly process to generate (multiple) MAC CEs for DSR; 3> Start or restart retxDSR-Timer. A MAC PDU can contain up to one MAC CE for DSR, even when multiple events have already triggered the DSR. The MAC entity should restart the retxDSR-Timer upon receiving authorization for the transmission of new data on any UL-SCH.

[0059] In some embodiments, if a MAC PDU is sent or assembled, and the MAC PDU includes all pending delay data available for transmission, the terminal device 110 may stop the DSR retransmission timer. In some embodiments, if no pending delay data is available for transmission, the terminal device 110 may stop the DSR retransmission timer.

[0060] For illustration, the example process can be described as follows. The MAC entity may stop the retxDSR-Timer if at least one of the following events occurs. 1. Stop the retxDSR-Timer when a MAC PDU is sent or assembled and contains all pending delayed data available for transmission. 2. Stop retxDSR-Timer when there is no pending delayed data available for transmission (e.g., due to a drop operation).

[0061] refer to Figure 2 In some embodiments, if at least one DSR has been triggered and not canceled, and the available UL resource set for transmission is sufficient to accommodate a MAC CE for the DSR plus a sub-header of the MAC CE, then terminal device 110 may start or restart the 233 DSR disable timer. In some embodiments, if the DSR disable timer is running, terminal device 110 may not trigger or send a MAC CE for the DSR. In some embodiments, if the DSR disable timer is not running, terminal device 110 may trigger or send a MAC CE for the DSR.

[0062] For illustration, the example process can be described as follows. MAC entities should: 1> If the Delay Status Reporting procedure determines that at least one DSR has been triggered and not canceled, and if UL-SCH resources are available for a new transmission, and UL-SCH resources are sufficient to accommodate the MAC CE for the DSR plus its sub-header due to logical channel priority ordering: 2> Instructions for the reuse and assembly process to generate (multiple) MAC CEs for DSR; 2> Start or restart dsr-ProhibitTimer. If dsr-ProhibitTimer is running, the UE may not trigger or send a MAC CE for DSR.

[0063] In some embodiments, if a MAC PDU is sent or assembled, and the MAC PDU includes all pending delayed data available for transmission, the terminal device 110 may cancel the DSR disable timer. In some embodiments, if no pending delayed data is available for transmission, the terminal device 110 may cancel the DSR disable timer. In some embodiments, if all trigger reports for the status of delayed data are canceled, the terminal device 110 may cancel the DSR disable timer.

[0064] For illustration, the example process can be described as follows. A MAC entity can cancel dsr-ProhibitTimer if at least one of the following events occurs. 1. Cancel dsr-ProhibitTimer when a MAC PDU is sent or assembled and the PDU contains all (pending) delayed data or all pending data available for transmission. 2. Cancel dsr-ProhibitTimer when there is no (pending) delayed data available for transmission (e.g., due to a drop operation). 3. Cancel dsr-ProhibitTimer when all DSR triggers are canceled.

[0065] Continue to refer to Figure 2 If the conditions for triggering DSR are met, terminal device 110 may trigger DSR 234. In some embodiments, terminal device 110 may trigger DSR if the first timer (i.e., the DSR retransmission timer) expires, and / or at least one LCH in the LCG includes delayed data.

[0066] For illustration, the example process can be described as follows. The DSR should be triggered if the following events occur (e.g., for an active cell group): - The retxDSR-Timer expires, and / or at least one logical channel belonging to the LCG contains UL delay data (e.g., at least one logical channel has available UL data with its remaining delay budget below a configured threshold).

[0067] In some embodiments, if the remaining latency budget for UL data used for LCH in LCG becomes below a threshold and none of the LCH in LCG includes latency data, the terminal device 110 may trigger DSR.

[0068] In some embodiments, the terminal device 110 may trigger the DSR if the second timer (i.e., the DSR disable timer) expires and / or at least one LCH in the LCG includes delayed data.

[0069] In some embodiments, terminal device 110 may trigger DSR if DSR is configured or reconfigured.

[0070] In some embodiments, if the secondary cell (SCell) of the MAC entity is activated and the MAC entity is configured, enabled, or activated to report a state with delayed data, the terminal device 110 may trigger DSR.

[0071] In some embodiments, if a threshold corresponding to a latency level is configured, and additional delayed data is imminent, the terminal device 110 may trigger a DSR, where the additional delayed data has a higher latency level than any of the delayed data. For example, thresholds 1, 2, and 3 are configured (threshold 1 is the most urgent and has the lowest time value). Delayed data exists with remaining time lower than thresholds 2 and 3, but no delayed data has remaining time lower than threshold 1. The DSR is triggered when delayed data with remaining time lower than threshold 1 (i.e., more urgent data) is imminent.

[0072] In some embodiments, if the remaining delay budget for UL data used for LCH in LCG becomes below a threshold, and the UL data belongs to an LCH with a higher priority than any LCH that includes the delay data, a report on the status of the delay data is triggered.

[0073] For illustration, the example process can be described as follows. The DSR should be triggered if any of the following events occur (e.g., for an active cell group): - UL data, used for logical channels belonging to LCG whose remaining delay budget (or remaining time of PDCP discardTimer) becomes below a configured threshold (e.g., as delay UL data); and logical channels belonging to LCG do not contain any delay UL data; - The dsr-ProhibitTimer has expired, is expired, or is not running, and at least one of the logical channels belonging to the LCG contains UL delayed data; - It was not used to disable the delay status reporting function when it was configured or reconfigured by the upper layer; - Activate the SCell of any MAC entity that has configuration / enable / activation of delay status reporting functionality; - If more than one latency threshold is configured (each latency threshold can correspond to a different latency level or congestion level), and more urgent data (e.g., data whose remaining latency budget is below the latency threshold and below any other threshold with latency data below them) is imminent; or - UL data, used for logical channels belonging to LCGs whose remaining latency becomes below a configured threshold, and the UL data belongs to a logical channel with a higher priority than any logical channel containing latency UL data belonging to any LCG.

[0074] In some embodiments, when a DSR is triggered by the expiration of a first timer (e.g., a DSR retransmission timer), the LCH that triggers the DSR is the highest priority LCH, which has data available for transmission at the time of the DSR triggering. In some embodiments, the LCH that triggers a DSR by the expiration of a first timer (e.g., a DSR retransmission timer) has a higher priority than the LCH that triggers a BSR by the expiration of a third timer (i.e., a BSR retransmission timer), which is configured for BSR retransmission.

[0075] For illustration, the example process can be described as follows. For a DSR triggered by the expiration of the retxDSR-Timer, the MAC entity considers the logical channel that triggered the DSR to be the highest priority logical channel with data available for transmission at the time the DSR was triggered. Furthermore, logical channels that trigger DSRs due to the expiration of the retxDSR-Timer have a higher priority than logical channels that trigger BSRs due to the expiration of the retxBSR-Timer.

[0076] Compared to the MAC CE used for BSR, the MAC CE used for DSR is more sensitive to latency. In some embodiments, during the LCP procedure, the MAC CE used for DSR has a higher priority than the MAC CE used for BSR. In this way, during the LCP procedure, the MAC CE used for DSR can be multiplexed among MAC PDUs with well-defined priorities.

[0077] For example, the example priority order of MAC CE used for DSR during the LCP process can be described as follows. During the LCP process, logical channels should be prioritized in the following order (highest priority listed first): - MAC CE for C-RNTI or data from UL-CCCH; ... - MAC CE for scheduled advance reporting; - MAC CE for DSR, excluding DSR for filling (if introduced); - MAC CE for SL-BSR priority sorting; - MAC CE for (extended) BSR, excluding BSR for filling; ... - MAC CE for recommending bitrate queries; - MAC CE for DSR, including DSR for filling (if introduced); - MAC CE for BSR, including BSR for filling; - MAC CE for SL-BSR, including SL-BSR for filling.

[0078] In another example, the example priority order of MAC CE used for DSR during the LCP process can be described as follows. During the LCP process, logical channels should be prioritized in the following order (highest priority listed first): - MAC CE for C-RNTI or data from UL-CCCH; ... - MAC CE for scheduled advance reporting; - MAC CE for SL-BSR priority sorting; - MAC CE for DSR, excluding DSR for filling (if introduced); - MAC CE for (extended) BSR, excluding BSR for filling; ... - MAC CE for recommending bitrate queries; - MAC CE for DSR, including DSR for filling (if introduced); - MAC CE for BSR, including BSR for filling; - MAC CE for SL-BSR, including SL-BSR for filling.

[0079] Continue to refer to Figure 2If the conditions for canceling DSR are met, terminal device 110 can cancel 235 DSR.

[0080] In some embodiments, terminal device 110 may cancel all DSR triggers if there is no pending delayed data available for transmission in the UL cache. In other words, all DSR triggers may be canceled if there is no pending delayed data available for transmission or if there is no delayed data in the UL cache. For example, there may be no delayed data in the UL cache due to a drop operation, or the remaining delay budget for the data (e.g., the SDU or PDU set) being exhausted (e.g., the PDCP drop timer expiring), or for other reasons.

[0081] In some embodiments, if one or more UL grants or MAC PDUs (also referred to herein as the first MAC PDU for convenience) are capable of accommodating all pending delay data available for transmission, but are insufficient to additionally accommodate the MAC CE for DSR (also referred to herein as the first MAC CE for convenience) plus the subheading of the MAC CE, then the terminal device 110 may cancel all triggered DSRs. In other words, when (multiple) UL grants or assembled MAC PDUs are capable of accommodating all pending delay data available for transmission, but are insufficient to additionally accommodate the MAC CE for DSR plus its subheading, all triggered DSRs may be canceled.

[0082] In some embodiments, if one or more UL grants are sufficient to accommodate all pending data available for transmission, but insufficient to additionally accommodate the MAC CE for DSR plus its subheading, then terminal device 110 may cancel all triggered reports of the status of delayed data. In other words, when (multiple) UL grants are sufficient to accommodate all pending data available for transmission, but insufficient to additionally accommodate the MAC CE for DSR plus its subheading, all triggered DSRs may be canceled.

[0083] In some embodiments, if a MAC PDU (also referred to herein as a second MAC PDU for convenience) is assembled or transmitted, and the MAC PDU includes all pending delay data available for transmission, then the terminal device 110 may cancel all triggered DSRs. In other words, all triggered DSRs can be canceled when a MAC PDU is assembled or transmitted and the PDU contains all pending delay data available for transmission.

[0084] In some embodiments, if a MAC PDU (also referred to herein as a third MAC PDU for convenience) is sent, and the MAC PDU includes all pending delayed data up to and including the last event that triggers a DSR before the assembly of the MAC PDU, then the terminal device 110 may cancel all DSRs triggered before the assembly of the MAC PDU. In other words, when a MAC PDU is sent and the PDU contains all pending delayed data up to and including the last event that triggers a DSR before the assembly of the MAC PDU, all DSRs triggered before the MAC PDU assembly can be canceled.

[0085] In some embodiments, if a MAC PDU (also referred to herein as a fourth MAC PDU for convenience) is sent, and the MAC PDU includes a MAC CE for DSR (also referred to herein as a second MAC CE for convenience), wherein the MAC CE includes a delayed buffer state up to the last event that triggered the DSR before the assembly of the MAC PDU, then the terminal device 110 may cancel all DSRs triggered before the assembly of the MAC PDU. In other words, when a MAC PDU is sent, and the PDU includes a MAC CE for DSR (including long, extended long, short, or extended short MAC CEs for DSR, if they are defined), which contains a delayed buffer state up to (and includes) the last event that triggered the DSR before the assembly of the MAC PDU, all DSRs triggered before the assembly of the MAC PDU should be canceled.

[0086] In some embodiments, if all triggered BSRs are cancelled, the terminal device 110 may cancel all triggered DSRs. In other words, if all triggered BSRs are cancelled, all triggered DSRs may also be cancelled.

[0087] In some embodiments, if no pending delay data is available for transmission for the LCH or LCG, the terminal device 110 may cancel the corresponding DSR triggered by the LCH or LCG. In other words, if no pending delay data is available for transmission for the logical channel or LCG, the corresponding DSR triggered by the logical channel or LCG may be canceled.

[0088] In this way, conditions for DSR cancellation can be defined. When the condition is met, all triggered DSRs can be cancelled, thus saving radio resources.

[0089] Using process 200, DSRs can be managed in a well-defined manner. DSRs can be sent as quickly as possible, and the transmission delay of delayed data can be reduced. It should be understood that the operations in process 200 can be performed individually or in any suitable combination. Example implementation of the method

[0090] Corresponding to the above process, embodiments of this disclosure provide communication methods implemented at terminal devices and network devices. Reference will be made below. Figures 3 to 4 Describe these methods.

[0091] Figure 3 An example method 300 for communication implemented at a terminal device according to some embodiments of the present disclosure is illustrated. For example, method 300 can be implemented in, for example, Figure 1 The terminal device 110 shown is executed. For discussion purposes, reference will be made below. Figure 1 Method 300 is described. It should be understood that method 300 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0092] At box 310, terminal device 110 receives a configuration from network device 120 for a report on the status of delayed data.

[0093] In some embodiments, the configuration may include a first set of values ​​for a first timer configured for retransmission of delayed data status reports, the first set of values ​​being lower than a first predetermined value. In some embodiments, the configuration may include a second set of values ​​for a second timer configured for triggering or disabling delayed data status reports, the second set of values ​​being lower than a second predetermined value.

[0094] In some embodiments, terminal device 110 may send capability information of terminal device 110 to network device 120. The capability information may include at least one of the following: information indicating whether the terminal device supports reporting the status of delayed data; information indicating the maximum number of logical channel groups for which the terminal device supports reporting the status of delayed data; or information indicating whether the terminal device supports a delay timer for a scheduling request triggered by reporting the status of delayed data for a logical channel. Using the capability information, the network can appropriately configure DSR operation.

[0095] At box 320, if the conditions for triggering a report of the status of delayed data are met, the terminal device 110 triggers a report of the status of delayed data.

[0096] In some embodiments, if a first timer configured for retransmission of a report on the status of delayed data expires, and at least one logical channel in the logical channel group includes delayed data, the terminal device 110 may trigger a report on the status of the delayed data.

[0097] In some embodiments, if the remaining delay budget for uplink data of a logical channel in a logical channel group becomes lower than a threshold, and none of the logical channels in the logical channel group include delayed data, the terminal device 110 may trigger a report on the status of the delayed data.

[0098] In some embodiments, if a second timer configured to disable reporting of the status of delayed data expires, and at least one logical channel in the logical channel group includes delayed data, the terminal device 110 may trigger a report of the status of the delayed data.

[0099] In some embodiments, if the reporting of the status of delayed data is configured or reconfigured, the terminal device 110 may trigger the reporting of the status of delayed data.

[0100] In some embodiments, if the secondary cell of a MAC entity is activated, the terminal device 110 may trigger a report of the status of delayed data, wherein the MAC entity is configured, enabled, or activated to report the status of delayed data.

[0101] In some embodiments, if a threshold corresponding to the latency level is configured and additional latency data is imminent, the terminal device 110 may trigger a report on the status of the latency data, wherein the additional latency data has a higher latency level than any latency level of the latency data.

[0102] In some embodiments, if the remaining delay budget for uplink data for a logical channel in a logical channel group becomes lower than a threshold, and the uplink data belongs to a logical channel with a higher priority than any logical channel that includes the delay data, the terminal device 110 may trigger a report on the status of the delay data.

[0103] In some embodiments, if a status report for delayed data has been triggered and not canceled, and the set of uplink resources available for transmission is sufficient to accommodate the MAC CE plus the subheader of the MAC CE for the status report of delayed data, then terminal device 110 may start or restart a first timer. In some embodiments, if no uplink grant is received during the operation of the first timer, terminal device 110 may retransmit the status report of delayed data.

[0104] In some embodiments, if a MAC PDU is sent or assembled, and the MAC PDU includes all pending delay data available for transmission, the terminal device 110 may stop the first timer. In some embodiments, if no pending delay data is available for transmission, the terminal device 110 may stop the first timer.

[0105] In some embodiments, if at least one report of the status of delayed data has been triggered and not canceled, and the set of uplink resources available for transmission is sufficient to accommodate a MAC CE for the report of the status of delayed data plus a sub-header of the MAC CE, then terminal device 110 may start or restart a second timer. In some embodiments, if the second timer is running, terminal device 110 may not trigger or send a MAC CE for the report of the status of delayed data.

[0106] In some embodiments, if a MAC PDU is sent or assembled, and the MAC PDU includes all pending delayed data available for transmission, the terminal device 110 may cancel the second timer. In some embodiments, if no pending delayed data is available for transmission, the terminal device 110 may cancel the second timer. In some embodiments, if all trigger reports of the status of the delayed data are canceled, the terminal device 110 may cancel the second timer.

[0107] In some embodiments, the reporting of the status of delayed data is triggered by the expiration of a first timer configured for retransmission of the delayed data status report, and the logical channel that triggers the reporting of the delayed data status is the highest priority logical channel available for data transmission at the time the reporting of the delayed data status is triggered. In some embodiments, the logical channel that triggers the reporting of the delayed data status by the expiration of the first timer has a higher priority than the logical channel that triggers the BSR by the expiration of a third timer configured for retransmission of the BSR.

[0108] In some embodiments, during the logical channel priority sorting process, the MAC CE for reporting the status of delayed data has a higher priority than the MAC CE for BSR.

[0109] At box 330, if the conditions for canceling the reporting of the status of delayed data are met, the terminal device 110 cancels the reporting of the status of delayed data.

[0110] In some embodiments, if there is no pending delayed data available for transmission in the uplink buffer, the terminal device 110 may cancel all trigger reports of the delayed data status.

[0111] In some embodiments, if one or more uplink grants or a first MAC PDU are sufficient to contain all pending delayed data available for transmission, but insufficient to additionally contain a first MAC CE plus a subheader of the first MAC CE for reporting the status of delayed data, then the terminal device 110 may cancel all trigger reports for the status of delayed data.

[0112] In some embodiments, if one or more uplink grants are sufficient to accommodate all pending data available for transmission, but insufficient to additionally accommodate the first MAC CE plus the subheader of the first MAC CE for reporting the status of delayed data, then terminal device 110 may cancel all trigger reports for the status of delayed data.

[0113] In some embodiments, if a second MAC PDU is assembled or sent, and the second MAC PDU includes all pending delayed data that can be used for transmission, the terminal device 110 may cancel all trigger reports of the status of the delayed data.

[0114] In some embodiments, if a third MAC PDU is sent, and the third MAC PDU includes all pending delayed data up to the last event that triggered a report on the state of delayed data prior to the assembly of the third MAC PDU, then the terminal device 110 may cancel all reports on the state of delayed data triggered prior to the assembly of the third MAC PDU.

[0115] In some embodiments, if a fourth MAC PDU is sent, and the fourth MAC PDU includes a second MAC CE for reporting the status of delayed data, wherein the second MAC CE includes a delayed cached status of the last event that triggered the reporting of the status of delayed data before the assembly of the fourth MAC PDU, then the terminal device 110 may cancel all reports of the status of delayed data that were triggered before the assembly of the fourth MAC PDU.

[0116] In some embodiments, if all triggered BSRs are cancelled, the terminal device 110 may cancel all triggered reports of the state of delayed data.

[0117] In some embodiments, if there is no pending delayed data available for transmission for a logical channel or logical channel group, the terminal device 110 may cancel the corresponding report on the status of delayed data triggered by the logical channel or logical channel group.

[0118] Using method 300, DSRs can be managed in a well-defined manner. DSRs can be sent as quickly as possible, and the transmission delay of delayed data can be reduced.

[0119] Figure 4 An example method 400 for communication implemented at a network device according to some embodiments of the present disclosure is illustrated. For example, method 400 can be implemented as follows: Figure 1 The network device shown is executed at location 120. For discussion purposes, references will be made below. Figure 1Method 400 is described. It should be understood that method 400 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0120] At box 410, network device 120 sends a configuration to terminal device 110 for reporting the status of delayed data.

[0121] In some embodiments, the configuration may include at least one of the following: a first set of values ​​for a first timer configured for retransmission of a report of the status of delayed data, the first set of values ​​being lower than a first predetermined value; or a second set of values ​​for a second timer configured for triggering or prohibiting the reporting of the status of delayed data, the second set of values ​​being lower than a second predetermined value.

[0122] At box 420, network device 120 receives a MACCE from terminal device 110 reporting the status of delayed data.

[0123] In some embodiments, network device 120 may receive capability information of terminal device 110. The capability information may include at least one of the following: information indicating whether the terminal device supports reporting the status of delayed data; information indicating the maximum number of logical channel groups for which the terminal device supports reporting the status of delayed data; or information indicating whether the terminal device supports a delay timer for a scheduling request triggered by reporting the status of delayed data for a logical channel.

[0124] Using method 400, the configuration of DSR can be provided and optimized.

[0125] It should be understood that the operation and combination of methods 300 and 400... Figure 2 The process described corresponds accordingly, and therefore, for the sake of brevity, other details will not be repeated here. Example implementation of the device

[0126] Figure 5 This is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. Device 500 can be considered as follows: Figure 1 Another example implementation of the terminal device 110 or network device 120 shown in A. Therefore, device 500 may be implemented at or as a part of the terminal device 110 or network device 120.

[0127] As shown in the figure, device 500 includes a processor 510, a memory 520 coupled to the processor 510, a suitable transceiver 540 coupled to the processor 510, and a communication interface coupled to the transceiver 540. The memory 510 stores at least a portion of a program 530. The transceiver 540 can be used for required bidirectional or unidirectional communication. The transceiver 540 may include at least one of a transmitter 542 or a receiver 544. The transmitter 542 and receiver 544 may be functional modules or physical entities. The transceiver 540 has at least one antenna to facilitate communication, although in practice, the access nodes mentioned in this application may have multiple antennas. The communication interface can represent any interface required for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, the Un interface for communication between the eNB / gNB and the Relay Node (RN), or the Uu interface for communication between the eNB / gNB and the terminal equipment.

[0128] Assume that program 530 includes program instructions that, when executed by the associated processor 510, enable device 500 to operate according to embodiments of this disclosure, as referenced herein. Figures 1 to 4 The embodiments described herein can be implemented by computer software executable by the processor 510 of device 500, or by hardware, or by a combination of software and hardware. The processor 510 can be configured to implement various embodiments of this disclosure. Furthermore, a combination of the processor 510 and the memory 520 can form a processing unit 550 suitable for implementing various embodiments of this disclosure.

[0129] Memory 520 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transient computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 520 is shown in device 500, there can be several physically different memory modules in device 500. Processor 510 can be of any type suitable for a local technology network and, as non-limiting examples, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 500 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0130] In some embodiments, the terminal device includes a circuit system configured to: receive a report on the status of delayed data from a network device; trigger the report on the status of delayed data based on the condition that a condition for triggering the report on the status of delayed data is met; and cancel the report on the status of delayed data based on the condition that a condition for canceling the report on the status of delayed data is met.

[0131] In some embodiments, the network device includes a circuitry configured to: send a report on the status of delayed data to an end device; and receive a MAC CE report on the status of delayed data from the end device.

[0132] As used herein, the term "circuit system" can refer to hardware circuitry and / or a combination of hardware circuitry and software. For example, a circuit system can be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit system can be any part of a hardware processor with software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device, such as a terminal device or network device, to perform various functions. In yet another example, a circuit system can be hardware circuitry and / or a processor, such as a microprocessor or a portion thereof, which requires software / firmware for operation, but the software may be absent when operation is not required. As used herein, the term circuit system also encompasses an implementation of hardware circuitry or (multiple) processors or a portion thereof, along with its accompanying software and / or firmware.

[0133] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0134] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the functions described above. Figures 1 to 4The process or method described herein. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. The functionality of a program module can be combined or split among program modules as needed in various embodiments. The machine-executable instructions used in a program module can be executed locally or on a distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0135] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0136] The aforementioned program code can be embodied on a machine-readable medium, which can be any tangible medium capable of containing or storing a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0137] Furthermore, although operations are described in a specific order, this should not be construed as requiring the operations to be performed in the specific order shown or sequentially, or to perform all of the shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combinations of features in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0138] Although this disclosure is described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A terminal device, comprising: The processor is configured to cause the terminal device to: Receive configuration from the network device, the configuration being used for reporting the status of delayed data; The report of the state of delayed data is triggered based on the condition that determines the state for triggering delayed data being met; as well as The report on the state of canceling delayed data is canceled if the conditions for determining the state of the delayed data are met.

2. The terminal device of claim 1, wherein the configuration includes a first set of values ​​for a first timer configured for retransmission of the report of the state of delayed data, the first set of values ​​being lower than a first predetermined value, and wherein the terminal device is further configured to include at least one of the following: Based on the fact that the report indicating the state of the delayed data has been triggered and not canceled, and that the set of uplink resources available for transmission can accommodate the Media Access Control (MAC) element (MAC CE) for the report indicating the state of the delayed data, plus the subheader of the MAC CE, the first timer is started or restarted; or The report states that, based on the determination that no uplink authorization was received during the operation of the first timer, delayed data is retransmitted.

3. The terminal device according to claim 2, wherein the terminal device is further configured to include at least one of the following: Based on the determination that a Media Access Control Protocol Data Unit (MAC PDU) has been sent or assembled, and that the MAC PDU includes all pending delayed data available for transmission, the first timer is stopped; or The first timer is stopped if it is determined that there is no pending delayed data available for transmission.

4. The terminal device of claim 1, wherein the configuration includes a second set of values ​​for a second timer configured to disable the triggering or reporting of the state of delayed data, the second set of values ​​being lower than a second predetermined value, and wherein the terminal device is further configured to cause at least one of the following: Based on the fact that at least one report indicating the state of the delayed data has been triggered and not canceled, and that the set of uplink resources available for transmission is capable of accommodating the report indicating the state of the delayed data, the second timer is started or restarted, along with a subheader of the MAC CE; or The MAC CE determines that the second timer is running, and does not trigger or send the report for the state of delayed data.

5. The terminal device according to claim 4, wherein the terminal device is further configured to include at least one of the following: The second timer is cancelled once it is determined that a Media Access Control Protocol Data Unit (MAC PDU) has been sent or assembled, and that the MAC PDU includes all pending delay data available for transmission. The second timer is cancelled if it is determined that there is no pending delayed data available for transmission; or The second timer is cancelled if all trigger reports based on the state of the determined delay data are cancelled.

6. The terminal device of claim 1, wherein the terminal device is caused to trigger the reporting of the state of the delayed data by at least one of the following: The first timer configured to retransmit the report of the state of the delayed data based on the determination of the state of the delayed data expires, and at least one logical channel in the logical channel group includes the delayed data, triggering the report of the state of the delayed data; The report of the state of the delay data is triggered when the remaining delay budget for uplink data of the logical channels in the logical channel group becomes lower than a threshold and none of the logical channels in the logical channel group include delayed data. The second timer configured to expire based on the prohibition of the report on the state of the delayed data, and at least one logical channel in the logical channel group including the delayed data, triggers the report on the state of the delayed data; The report on the state of the delayed data is triggered when the report is configured or reconfigured based on the state of the delayed data. The report that the secondary cell of the determined Media Access Control (MAC) entity is activated triggers the state of delayed data, wherein the MAC entity is configured or enabled or activated with the state of delayed data. The report of the state of the delay data is triggered based on the determination of a threshold corresponding to the delay level being configured and additional delay data being imminent, wherein the additional delay data has a higher delay level than any delay level of the delay data; or The report of the state of the delay data is triggered when the remaining delay budget for uplink data used in a logical channel within a logical channel group falls below a threshold, and the uplink data belongs to a logical channel with a higher priority than any logical channel that includes the delay data.

7. The terminal device of claim 1, wherein the report of the state of the delayed data is triggered by the expiration of a first timer configured for retransmission of the report of the state of the delayed data, and the logical channel that triggers the report of the state of the delayed data is the highest priority logical channel available for data transmission at the time the report of the state of the delayed data is triggered, or The logical channel that triggers the report of the state of delayed data due to the expiration of a first timer has a higher priority than the logical channel that triggers the buffer status report (BSR) due to the expiration of a third timer, which is configured for retransmission of the BSR. In the logical channel priority sorting process, the Media Access Control (MAC) CE for the report of the state of delayed data has a higher priority than the MAC CE for the BSR.

8. The terminal device of claim 1, wherein the terminal device is caused to cancel the report of the state of delayed data by at least one of the following: Based on the determination that there is no pending delayed data available for transmission in the uplink buffer, cancel all trigger reports for the state of delayed data; Based on the determination that one or more uplink grants or first media access control protocol data units (MAC PDUs) are capable of accommodating all pending delayed data available for transmission, but insufficient to additionally accommodate the report of the state of the delayed data, all trigger reports of the state of the delayed data are cancelled. Based on the first MAC CE plus the sub-header of the first MAC CE, which determines that one or more uplink grants are sufficient to accommodate all pending data available for transmission, but insufficient to additionally accommodate the report of the state of delayed data, all trigger reports of the state of delayed data are cancelled; Based on the determination that a second MAC PDU is assembled or sent, and that the second MAC PDU includes all pending delayed data available for transmission, all trigger reports for the state of the delayed data are cancelled; Based on the determination that a third MAC PDU was sent, and that the third MAC PDU includes all pending delayed data of the last event of the report that triggered the state of delayed data up to before the assembly of the third MAC PDU, cancel all reports of the state of delayed data triggered before the assembly of the third MAC PDU; Based on the determination that a fourth MAC PDU is sent, and the fourth MAC PDU includes a second MAC CE for the report of the state of delayed data, wherein the second MAC CE includes a delayed cache state of the last event that triggered the report of the state of delayed data before the assembly of the fourth MAC PDU, all reports of the state of delayed data triggered before the assembly of the fourth MAC PDU are cancelled. Based on the determination that all triggered cached state reports (BSRs) have been cancelled, cancel all triggered reports for the state of delayed data; or Based on the determination that there is no pending delayed data available for transmission for a logical channel or logical channel group, the corresponding report for the status of the delayed data triggered by the logical channel or logical channel group is cancelled.

9. The terminal device according to claim 1, wherein the terminal device is further configured to: Send the terminal device's capability information to the network device, the capability information including at least one of the following: The information in the report indicating whether the terminal device supports delayed data; Information indicating the maximum number of logical channel groups, the terminal device supporting the reporting of the status of delay data for said logical channel groups; or Information indicating whether the terminal device supports a delay timer for a scheduling request triggered by a report of the status of the delay data for the logical channel.

10. A network device, comprising: The processor is configured to cause the network device to: Configuration for sending status reports for delayed data to terminal devices; as well as The Media Access Control (MAC) element CE receives the report of the status of delayed data from the terminal device.

11. The network device of claim 10, wherein the configuration includes at least one of the following: A first set of values ​​for a first timer, configured for retransmission of the report of the state of delayed data, is lower than a first predetermined value; or The second set of values ​​for the second timer, configured to disable the triggering or reporting of the state of the delayed data, is lower than a second predetermined value.

12. The network device of claim 10, wherein the network device is further configured to: Receive capability information of the terminal device from the terminal device, the capability information including at least one of the following: The information in the report indicating whether the terminal device supports delayed data; Information indicating the maximum number of logical channel groups, the terminal device supporting the reporting of the status of delay data for said logical channel groups; or Information indicating whether the terminal device supports a delay timer for a scheduling request triggered by a report of the status of the delay data for the logical channel.

13. A communication method, comprising: At the terminal device, a configuration is received from the network device for reporting the status of delayed data. The report of the state of delayed data is triggered based on the condition that determines the state for triggering delayed data being met; as well as The report on the state of canceling delayed data is canceled if the conditions for determining the state of the delayed data are met.

14. The method of claim 13, wherein the configuration includes a first set of values ​​for a first timer configured for retransmission of the report of the state of delayed data, the first set of values ​​being lower than a first predetermined value, and wherein the method further comprises at least one of the following: Based on the fact that the report indicating the state of the delayed data has been triggered and not canceled, and that the set of uplink resources available for transmission can accommodate the Media Access Control (MAC) element (MAC CE) for the report indicating the state of the delayed data, plus the subheader of the MAC CE, the first timer is started or restarted; or The report states that, based on the determination that no uplink authorization was received during the operation of the first timer, delayed data is retransmitted.

15. The method of claim 14, further comprising at least one of the following: Based on the determination that a Media Access Control Protocol Data Unit (MAC PDU) has been sent or assembled, and that the MAC PDU includes all pending delayed data available for transmission, the first timer is stopped; or The first timer is stopped if it is determined that there is no pending delayed data available for transmission.

16. The method of claim 13, wherein the configuration includes a second set of values ​​for a second timer configured to disable the triggering or reporting of the state of the delayed data, the second set of values ​​being lower than a second predetermined value, and wherein the method further comprises at least one of the following: Based on the fact that at least one report indicating the state of the delayed data has been triggered and not canceled, and that the set of uplink resources available for transmission is capable of accommodating the report indicating the state of the delayed data, the second timer is started or restarted, along with a subheader of the MAC CE; or The MAC CE determines that the second timer is running, and does not trigger or send the report for the state of delayed data.

17. The method of claim 16, further comprising at least one of the following: The second timer is cancelled once it is determined that a Media Access Control Protocol Data Unit (MAC PDU) has been sent or assembled, and that the MAC PDU includes all pending delay data available for transmission. The second timer is cancelled if it is determined that there is no pending delayed data available for transmission; or The second timer is cancelled if all trigger reports based on the state of the determined delay data are cancelled.

18. The method of claim 13, wherein the report that triggers the state of the delayed data comprises at least one of the following: The first timer configured to retransmit the report of the state of the delayed data based on the determination of the state of the delayed data expires, and at least one logical channel in the logical channel group includes the delayed data, triggering the report of the state of the delayed data; The report of the state of the delay data is triggered when the remaining delay budget for uplink data of the logical channels in the logical channel group becomes lower than a threshold and none of the logical channels in the logical channel group include delayed data. The second timer configured to expire based on the prohibition of the report on the state of the delayed data, and at least one logical channel in the logical channel group including the delayed data, triggers the report on the state of the delayed data; The report on the state of the delayed data is triggered when the report is configured or reconfigured based on the state of the delayed data. The report that the secondary cell of the determined Media Access Control (MAC) entity is activated triggers the state of delayed data, wherein the MAC entity is configured or enabled or activated with the state of delayed data. The report of the state of the delay data is triggered based on the determination of a threshold corresponding to the delay level being configured and additional delay data being imminent, wherein the additional delay data has a higher delay level than any delay level of the delay data; or The report of the state of the delay data is triggered when the remaining delay budget for uplink data used in a logical channel within a logical channel group falls below a threshold, and the uplink data belongs to a logical channel with a higher priority than any logical channel that includes the delay data.

19. The method of claim 13, wherein the report of the state of the delayed data is triggered by the expiration of a first timer configured for retransmission of the report of the state of the delayed data, and the logical channel that triggers the report of the state of the delayed data is the highest priority logical channel available for data transmission at the time the report of the state of the delayed data is triggered, or The logical channel that triggers the report of the state of delayed data due to the expiration of a first timer has a higher priority than the logical channel that triggers the buffer status report (BSR) due to the expiration of a third timer, which is configured for retransmission of the BSR. During the logical channel priority sorting process, the Media Access Control (MAC) CE for reporting the status of delayed data has a higher priority than the MAC CE for reporting buffered status (BSR).

20. The method of claim 13, wherein the report of the state of canceling delayed data comprises at least one of the following: Based on the determination that there is no pending delayed data available for transmission in the uplink buffer, cancel all trigger reports for the state of delayed data; Based on the determination that one or more uplink grants or first media access control protocol data units (MAC PDUs) are capable of accommodating all pending delayed data available for transmission, but insufficient to additionally accommodate the report of the state of the delayed data, all trigger reports of the state of the delayed data are cancelled. Based on the first MAC CE plus the sub-header of the first MAC CE, which determines that one or more uplink grants are sufficient to accommodate all pending data available for transmission, but insufficient to additionally accommodate the report of the state of delayed data, all trigger reports of the state of delayed data are cancelled; Based on the determination that a second MAC PDU is assembled or sent, and that the second MAC PDU includes all pending delayed data available for transmission, all trigger reports for the state of the delayed data are cancelled; Based on the determination that a third MAC PDU was sent, and that the third MAC PDU includes all pending delayed data of the last event of the report that triggered the state of delayed data up to before the assembly of the third MAC PDU, cancel all reports of the state of delayed data triggered before the assembly of the third MAC PDU; Based on the determination that a fourth MAC PDU is sent, and the fourth MAC PDU includes a second MAC CE for the report of the state of delayed data, wherein the second MAC CE includes a delayed cache state of the last event that triggered the report of the state of delayed data before the assembly of the fourth MAC PDU, all reports of the state of delayed data triggered before the assembly of the fourth MAC PDU are cancelled. Based on the determination that all triggered cached state reports (BSRs) have been cancelled, cancel all triggered reports for the state of delayed data; or Based on the determination that there is no pending delayed data available for transmission for a logical channel or logical channel group, the corresponding report for the status of the delayed data triggered by the logical channel or logical channel group is cancelled.

Images