A communication method and related apparatus

Abstract

The application relates to a communication method and related device, and relates to the technical field of communication. The method comprises the following steps: a terminal device determines whether there is delay data in a first data in a logical channel group, and then dynamically associates a target threshold value based on whether there is delay data. The terminal device sends a resource request message, the resource request message is used for requesting to configure resources for the first data, and the resource request message comprises the target threshold value associated with the first data. The target threshold value is used for determining the sending time of a DSR report by a receiver of the resource request message, such as a network device. The above method can dynamically adjust the sending time of a delay status report, and reduces redundant signaling.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a communication method and related apparatus. BACKGROUND

[0002] The terminal device can report a delay status report (DSR) to the base station, so that the base station can understand the buffer status and data delay of the terminal device according to the reported information, so as to more reasonably perform resource scheduling and avoid the data of the terminal device being discarded due to long waiting for resource scheduling.

[0003] In a 5th Generation New Radio (5G NR or NR) communication system, the DSR mechanism needs to be further enhanced. For example, in the case of tight bandwidth resources, the signal is prone to fluctuation. The delay status report may be triggered at unnecessary time, aggravating resource competition. SUMMARY

[0004] The communication method and related apparatus provided by the embodiments of the present application can dynamically adjust the sending occasion of the delay status report, thereby reducing redundant signaling.

[0005] In a first aspect, a communication method is provided. The method can be executed by a terminal device, or can be executed by a component (such as a circuit, a chip, or a chip system, etc.) configured in the terminal device, and can also be executed by a logic module or software capable of realizing all or part of the functions of the terminal device. The present application does not limit this. Hereinafter, the terminal device is taken as an example for description. The method includes but is not limited to the following operations:

[0006] The terminal device determines whether there is delay data in the first data in the logical channel group. The delay data includes data whose remaining time (such as the remaining value of the discard timer) of data discard is less than any one delay report threshold remaining Time Threshold in the delay report threshold list dsr-ReportingThresholdList. The terminal device sends a resource request message. The resource request message is used to request to configure resources for the first data, and the resource request message includes a target threshold associated with the first data. The target threshold is used for the receiving side of the resource request message, such as the network device, to explicitly indicate the sending occasion of the DSR report.

[0007] In a case where the first data includes the delay data, the target threshold is the first threshold, and the first threshold is the minimum value of the delay reporting thresholds corresponding to the one or more pieces of delay data in the delay status report (DSR) data. The first threshold can also be referred to as a minimum reporting threshold. In a case where the first data does not include the delay data, the target threshold is the second threshold, and the second threshold includes the minimum value of the delay reporting threshold list. The second threshold can also be referred to as a minimum configured threshold.

[0008] In the above implementation, the terminal device dynamically selects the target threshold according to whether the delay data exists in the logical channel group. When the delay data exists, the minimum reporting threshold is used, and when the delay data does not exist, the minimum configured threshold is used. The flexibility of the resource request is improved, and the signaling overhead in a case where there is no delay data is reduced.

[0009] Optionally, the logical channel group (LCG) includes one or more logical channels (LCHs).

[0010] In a possible implementation, the first data is all data / packets in the logical channel group.

[0011] In another possible implementation, the first data is all data / packets in any one of the one or more logical channels.

[0012] In yet another possible implementation, the first data is part of the data in the logical channel group, for example, a certain buffer area in the logical channel group is used to buffer the delay data, and the first data is the delay data in the buffer area. In this implementation, the amount of data of the first data can be 0, which represents no delay data.

[0013] Optionally, the delay status report (DSR) data is historical delay data reported by the terminal device to the network device. The data is classified as delay data because the delay reporting threshold is triggered and is reported to the network device. If the DSR data includes multiple pieces of data, the minimum delay reporting threshold of the corresponding delay reporting thresholds in the multiple pieces of DSR data is the first threshold. Therefore, the first threshold can be referred to as a minimum reporting threshold.

[0014] Optionally, the delay reporting threshold list is a set of delay reporting thresholds configured by the network for the terminal device. The delay reporting threshold list includes one or more delay reporting thresholds. The delay reporting threshold is used to output a delay report in a case where the remaining time of the data in the first data is less than the delay reporting threshold. In an implementation where the delay reporting threshold list includes multiple delay reporting thresholds, the second threshold is the minimum delay reporting threshold of the multiple delay reporting thresholds. Because the threshold is configured by the network, it can also be referred to as a minimum configured threshold.

[0015] In an implementation where the delay reporting threshold list includes one delay reporting threshold, the second threshold is the delay reporting threshold.

[0016] Optionally, the resource request message is specifically for requesting uplink resources for transmitting a DSR medium access control control element (MAC CE).

[0017] In a possible implementation, the step of determining whether there is delay data in the first data in the logical channel group is performed by a first entity in the terminal device. Illustratively, the first entity is a packet data convergence protocol (PDCP) entity. Illustratively, the first entity is a medium access control (MAC) entity.

[0018] Considering that part of the first data, such as high-priority data, is not directly associated with the discard timer (for determining whether data is discarded due to timeout), but needs to be included in the DSR report to ensure its high-priority scheduling, the threshold association strategy of the high-priority data (that is, which threshold is associated) directly affects the signaling overhead, transmission efficiency, and network resource utilization. In actual applications, 5G users often use multiple services at the same time, and each service corresponds to a logical channel group; or multiple users communicate concurrently in the same cell. In such scenarios, if the threshold association of high-priority data adopts a fixed strategy, signaling will accumulate, occupy limited wireless resources, and reduce overall transmission efficiency.

[0019] Illustratively, if the high-priority data is associated with the minimum reporting threshold, the minimum reporting threshold is valid only when there is delay report data. If there is only high-priority data in the LCG, the minimum reporting threshold cannot be triggered, and the high-priority data cannot be reported to the network through the DSR. At this time, the network cannot know the existence of the high-priority data, which will cause critical control signaling to be unable to be scheduled in time, resulting in problems such as link error feedback failure, lost data retransmission failure, and even service interruption.

[0020] In the multi-LCH LCG scenario, different LCHs can be configured with different reporting thresholds, and the delay data status of each LCH is independent. At this time, the UE needs to coordinate the threshold information of multiple protocol layer entities to determine the minimum reporting threshold of the entire LCG, which not only increases the cross-layer interaction logic of the UE, but also increases the computational burden, which can cause the terminal device to increase power consumption and response delay to become longer.

[0021] Illustratively, if the high-priority data is associated with the minimum configuration threshold. In actual communication, the minimum configuration threshold of the LCG has no delay report data in a large number of scenarios. In these scenarios, the high-priority data still needs to be associated with the minimum configuration threshold, and signaling will accumulate sharply, occupying valuable wireless resources, especially in the edge area with limited bandwidth, which will further cause problems such as intensified resource competition, increased data transmission delay, and other chain problems, seriously affecting service quality.

[0022] No matter what threshold the high-priority data is associated with, there may be a problem of poor flexibility and inability to adapt to dynamic data status. Therefore, in the embodiments of the present application, the high-priority data is associated with a dynamic target threshold and is reported synchronously with the delay data, and in the case of no delay data, the high-priority data is still reported based on the minimum configured threshold, thereby avoiding missing reporting of the high-priority data.

[0023] Based on the above, in a possible implementation, the first data includes second data, the priority of the second data is higher than the priority threshold, and the second data can be the high-priority data described above. In the following, for convenience, the second data is used instead of the high-priority data described above. The priority of the second data is related to the reporting demand time of the second data. The resource request message further includes the total amount of the first data. Optionally, the priority is related to the remaining time of the corresponding data, and the shorter the remaining time, the higher the priority. Optionally, the priority threshold is a threshold value configured by the network device or predefined to distinguish the priority of the data, or the priority threshold is related to the minimum configured threshold, for example, the value in the priority threshold is obtained based on the minimum configured threshold.

[0024] In the above implementation, the resource request message includes the total amount of the first data and the first data covers the high-priority second data such as PDU data and retransmission data, so that the network device can fully perceive the data status of the terminal device buffer, including emergency data and critical signaling, thereby more accurately allocating time-frequency resources, improving the pertinence of resource scheduling and the timeliness of data transmission, and reducing the probability of service interruption due to insufficient resources. In this implementation, the resource configuration requested by the resource request message further includes the resource requested for the second data, thereby ensuring timely reporting of high-priority data such as control PDU and retransmission data and reducing the risk of data loss.

[0025] Optionally, the reporting demand time can be a maximum allowed reporting delay time corresponding to a quality of service (QoS) requirement.

[0026] In a possible implementation, the second data includes PDCP protocol data unit (PDU) data and / or retransmission data. Exemplarily, the PDU data can be key control signaling, such as control PDU data. RLC (Radio Link Control) PDU is divided into two categories of data PDU and control PDU, wherein the data PDU includes three structures corresponding to transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM), respectively carrying original data transmission or segmented retransmission function. The control PDU mainly refers to a STATUS PDU, which is used for feedback of the ARQ retransmission mechanism in the AM mode. The RLC control PDU is mainly a STATUS PDU, which is used for the receiving part of the AM RLC entity to inform the peer AM RLC entity about the information that the RLC data PDU has been successfully received, and the information that the missing RLC data PDU is detected by the receiving part of the AM RLC entity.

[0027] Considering that data transmission needs to rely on the cooperative work of multiple protocol stacks (covering PDCP layer, RLC layer, MAC layer, etc.), each layer implements reliable transmission and efficient scheduling of data through division of labor and cooperation. Among them, the control PDU (such as PDCP control PDU and RLC STATUS PDU) is responsible for maintaining the link state (such as link connectivity and error feedback), and the retransmission data (such as PDCP / RLC layer retransmission PDU / service data unit (SDU)) is used to supplement the missing or erroneous data, both of which guarantee the integrity of data transmission and are core functional components of the 5G network.

[0028] In some embodiments, the DSR triggering operation described above, such as determining whether there is delayed data, can be performed by the first entity, such as the PDCP entity. When the terminal device is configured with a time threshold related to the logical channel group (such as the delay report threshold list or one of the delay report threshold list described above), the PDCP entity associated with the logical channel of the logical channel group still determines whether to trigger the DSR for the LCG according to the target threshold.

[0029] More specifically, the PDCP entity can trigger the DSR when the remaining time of the discard timer associated with the PDCP SDU is less than or equal to the delay reporting threshold, and the triggered DSR with the remaining time can be indicated to the lower layer (e.g., the MAC layer). In some embodiments, the PDCP entity triggering the DSR can mean that the PDCP entity instructs the lower layer (e.g., the MAC layer) to trigger the DSR. Wherein the PDCP SDU is a basic unit of data processed by the PDCP layer, which contains data to be transmitted and some necessary control information for correct processing and routing during transmission.

[0030] In some embodiments, the PDCP entity can trigger the DSR if the remaining time of the PDU set becomes less than or equal to the delay reporting threshold. More specifically, the PDCP entity can trigger the DSR if the PDCP SDU corresponding to the PDU with the smallest sequence number in the PDU set, when the remaining time of the discard timer associated with the PDCP SDU is less than or equal to the delay reporting threshold, and can indicate the triggered DSR (and / or the related trigger information) to the lower layer (e.g., the MAC layer). The related trigger information can include at least one of the PDU set ID triggering the DSR, the sequence number of the PDCP SDU triggering the DSR, the remaining time of the discard timer of the PDU set (or the PDCP SDU) triggering the DSR.

[0031] In some embodiments, the PDCP entity can trigger the DSR if the remaining time of the PDU set is less than or equal to the delay reporting threshold. More specifically, the PDCP entity can trigger the DSR when the remaining time of the discard timer associated with one of the PDCP SDUs corresponding to the PDUs in the PDU set is less than or equal to the delay reporting threshold, and can indicate the triggered DSR (and / or the related trigger information) to the lower layer (e.g., the MAC layer). The related trigger information can include at least one of the PDU set ID triggering the DSR, the sequence number of the PDCP SDU triggering the DSR, the remaining time of the discard timer of the PDU set (or the PDCP SDU) triggering the DSR.

[0032] In one possible implementation, the resource request message further includes a first field, and the first field includes a second field for indicating the remaining time of the delay data in the case that the delay data exists in the first data.

[0033] In the case that the delay data does not exist in the first data, the first field includes a first identifier for indicating that the delay data is not included in the first data.

[0034] In the above embodiment, the resource request message contains the first field and indicates the remaining time when there is delay data, and uses the first identifier when there is no delay data, which provides clear delay status information, enables the network device to quickly distinguish the urgency of the data, optimizes the scheduling decision process, reduces processing complexity and signaling analysis delay, and enhances the adaptability of the network in dynamic scenarios such as concurrent LCs.

[0035] In a possible implementation, the remaining time of the delay data can be the shortest remaining time of the plurality of delay data.

[0036] In another possible implementation, when the number of the delay data is only one, the remaining time of the delay data is the remaining time of the delay data.

[0037] In a possible embodiment, when there is no delay data in the first data, and the second threshold is less than the reporting requirement time of the second data, the value of the target threshold is related to the reporting requirement time of the second data.

[0038] In the above embodiment, when there is no delay data in the first data and the minimum configured threshold is less than the reporting requirement time of the second data, the target threshold is related to the reporting requirement time. The above embodiment allows the terminal device to adjust the threshold value to match the service QoS requirement, improves the response speed and scheduling accuracy of high-priority data, and reduces the risk of transmission delay and service quality degradation caused by mismatched threshold.

[0039] For example, the value of the target threshold is greater than the reporting requirement time of the second data, to meet the reporting requirement time of the second data and avoid delay.

[0040] Optionally, the above method further includes the following operation: when there is delay data, the terminal device determines the target threshold based on the reporting requirement time of the second data, and the value of the target threshold is related to the reporting requirement time of the second data.

[0041] In a possible embodiment, when the minimum configured threshold is less than the reporting requirement time of the second data, and the value of the target threshold is adjusted, the first field in the resource request message is additionally marked with the identifier of the remaining time selected by the terminal device. Optionally, the resource request message further includes the first field, and the first field includes the second identifier, and the second identifier is used to indicate that the value of the target threshold is related to the reporting requirement time of the second data.

[0042] In the above embodiments, the first field of the resource request message includes the second identifier for indicating that the target threshold is related to the reporting requirement time, explicitly conveying the terminal autonomous decision state to the network device, promoting the coordination and optimization between the network and the terminal, reducing the possibility of signaling misunderstanding and configuration conflict, and enhancing the robustness and efficiency of the system in the edge area or bandwidth limited scenario.

[0043] In a possible implementation, the method further includes the following operation: the terminal device determines the second data in the first data and the data amount of the second data.

[0044] In the above embodiments, the terminal device determines the second data in the first data and the data amount of the second data, ensures the independent statistics and reporting of high priority data, enables the network device to preferentially allocate resources to critical data such as control signaling and retransmission packets, improves the link reliability and service continuity, and reduces the risk of error accumulation and connection interruption caused by the critical data not being scheduled in time.

[0045] In a possible implementation, the method further includes the following operation: the terminal device obtains a delay report threshold list, and the delay report threshold list includes one or more delay report thresholds.

[0046] The operation of the terminal device determining whether the first data in the logical channel group has delay data includes but is not limited to the following operation: the terminal device determines, based on the delay report threshold list, whether the first data in the logical channel group has delay data.

[0047] In the above embodiments, the terminal device obtains the network configured delay report threshold list, provides a standardized basis for dynamic threshold decision, guarantees the consistency of the terminal and the network policy, reduces the risk of configuration error and interoperability failure, supports complex threshold management in the multi-LCH scenario, and improves the convenience and stability of system deployment.

[0048] Optionally, the terminal device receives the delay report threshold related to the LCG through radio resource control (RRC) signaling.

[0049] In a second aspect, a communication method is provided, which can be executed by a network device, or can be executed by a component (such as a circuit, a chip or a chip system, etc.) configured in the network device, and can also be executed by a logic module or software that can implement all or part of the terminal network device. The present application does not limit this. The following describes the network device as an example. The method includes but is not limited to the following operations:

[0050] The network device receives a resource request message, the resource request message is used for requesting to configure resources for first data in a logical channel group, and the resource request message includes a target threshold value associated with the first data.

[0051] In a case where there is delay data in the first data, the target threshold value is a first threshold value, the first threshold value is a minimum value of delay reporting threshold values corresponding to one or more pieces of delay data in delay status report (DSR) data, and in a case where there is no delay data in the first data, the target threshold value is a second threshold value, and the second threshold value includes a minimum value in a delay reporting threshold value list.

[0052] The network device configures time-frequency resources for the first data based on the resource request message.

[0053] In the above implementation, the network device receives a resource request message and configures time-frequency resources based on a target threshold value, thereby achieving accurate matching of resource allocation by understanding dynamic threshold selection of the terminal, improving network scheduling efficiency and spectrum utilization, reducing resource waste and competition conflicts, and enhancing user experience and service quality.

[0054] In a possible implementation, the first data includes second data, a priority of the second data is higher than a priority threshold value, the priority of the second data is related to a reporting requirement time of the second data, and the resource request message further includes a total amount of data of the first data.

[0055] In the above implementation, the network device sends a delay reporting threshold value list to the terminal device, thereby ensuring that the terminal device has the latest and consistent configuration parameters, supporting effective operation of the dynamic threshold mechanism, reducing signaling mismatch and synchronization delay risks, and thereby improving the synergy and reliability of the entire communication system.

[0056] In a possible implementation, the second data includes PDU data and / or retransmission data.

[0057] In a possible implementation, the resource request message further includes a first field, in a case where there is delay data in the first data, the first field includes a second field used for indicating a remaining time of the delay data.

[0058] In a case where there is no delay data in the first data, the first field includes a first identifier, and the first identifier is used for indicating that the first data does not include delay data.

[0059] In a possible implementation, in a case where there is no delay data in the first data and the second threshold value is smaller than the reporting requirement time of the second data, the target threshold value is determined according to the reporting requirement time of the second data.

[0060] In a possible implementation, the resource request message further includes a first field, and the first field includes a second identifier, where the second identifier is used to indicate that the value of the target threshold is related to the reporting requirement time of the second data.

[0061] In a possible implementation, the method further includes the following operation:

[0062] The network device sends a delay reporting threshold list, and the delay reporting threshold list includes one or more delay reporting thresholds.

[0063] In a third aspect, a communication apparatus is provided, which is applied to a terminal device, and the apparatus includes a module for executing the method in any of the aspects and the possible implementation manners of the aspect.

[0064] In a fourth aspect, a communication system is provided, which includes a network device and a terminal device, the terminal device is configured to execute the method in the first aspect and the possible implementation manners of the first aspect, and the network device is configured to execute the method in the second aspect and the possible implementation manners of the second aspect.

[0065] In a fifth aspect, a communication apparatus is provided, which includes at least one processor and an interface circuit, the interface circuit is configured to receive a signal from another communication apparatus outside the communication apparatus and transmit the signal to the processor or send a signal from the processor to another communication apparatus outside the communication apparatus, and the processor is configured to implement the method in any of the aspects and the possible implementation manners of the aspect by means of a logic circuit or an execution code instruction.

[0066] Optionally, the communication apparatus further includes a memory configured to store program instructions, and the processor is coupled to the memory through the interface.

[0067] In a sixth aspect, a computer readable storage medium is provided, which stores a computer program or instructions, and the computer program or instructions are configured to execute the method in any of the aspects and the possible implementation manners of the aspect.

[0068] In a seventh aspect, a chip is provided, which includes an interface circuit and a logic circuit, the interface circuit is configured to receive a signal from another chip outside the chip and transmit the signal to the logic circuit, or send a signal from the logic circuit to another chip outside the chip, and the logic circuit is configured to implement the method in any of the aspects and the possible implementation manners of the aspect.

[0069] In an eighth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer program or instructions make the computer execute the method in any of the aspects and the possible implementation manners of the aspect.

[0070] It should be understood that the description of technical features, technical solutions, advantages or similar language in this application does not imply that all features and advantages can be realized in any single embodiment. On the contrary, it can be understood that the description of a feature or advantage means that the specific technical feature, technical solution or advantage is included in at least one embodiment. Therefore, the description of technical features, technical solutions or advantages in this specification does not necessarily refer to the same embodiment. Further, the technical features, technical solutions and advantages described in this embodiment can be combined in any appropriate manner. Those skilled in the art will understand that the embodiments can be implemented without one or more specific technical features, technical solutions or advantages of the specific embodiments. In other embodiments, additional technical features and advantages can be identified in specific embodiments that do not embody all embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0071] The following describes the drawings used in the embodiments of the present application.

[0072] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0073] Figure 2 is a schematic diagram of a protocol stack provided by an embodiment of the present application;

[0074] Figure 3 is a schematic diagram of a terminal device structure provided by an embodiment of the present application;

[0075] Figure 4 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0076] Figure 5 is a schematic diagram of another communication method provided by an embodiment of the present application;

[0077] Figure 6 is a schematic diagram of another communication method provided by an embodiment of the present application;

[0078] Figure 7 is a schematic diagram of a data monitoring process provided by an embodiment of the present application;

[0079] Figure 8 is a schematic diagram of a target threshold determination process provided by an embodiment of the present application;

[0080] Figure 9 is a schematic diagram of a first field determination process provided by an embodiment of the present application;

[0081] Figure 10 is a schematic diagram of a communication device structure provided by an embodiment of the present application;

[0082] Figure 11 Another structural schematic diagram of a communication apparatus provided in an embodiment of the present application. DETAILED DESCRIPTION

[0083] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of them. The following terms "first", "second", and the like are only used for the purpose of description, and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first", "second", and the like can explicitly or implicitly include one or more of the features. "Plural" can be understood as "at least two". "Plural" can be understood as "at least two".

[0084] In the embodiments of the present application, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of another identical element in the process, method, article or device including the element.

[0085] In the embodiments of the present application, "and / or" is only a description of the association relationship between the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects have an "or" relationship.

[0086] In the embodiments of the present application, it should be noted that, unless otherwise explicitly specified and limited, the terms "set", "connected", "connected" should be understood in a broad sense, for example, it can be fixedly connected, or it can be detachably connected, or integrally connected. For those skilled in the art, the specific meanings of the above terms in the embodiments of the present application can be understood according to the specific circumstances.

[0087] In order to facilitate the understanding of the embodiments of the present application, first, the terms involved in the present application are simply explained. Alternatively, the explanation of some terms can also refer to the explanation in the standard protocol.

[0088] 1. Delay report threshold (remaining Time Threshold).

[0089] The delay report threshold can also be referred to as a remaining duration threshold, a data valid remaining duration threshold, or a remaining time threshold. The delay report threshold can be a triggering threshold of the DSR configured by the network device. In a case where the valid remaining duration of the data in the buffer of the terminal device (such as a difference between the data expected duration and a result of counting of the discard timer) is less than or equal to the delay report threshold, the terminal device triggers the DSR and reports the data status of the terminal device to the network device, thereby facilitating the network device to more accurately manage the data transmission, for example, the data transmission of the delay sensitive flow service.

[0090] 2. Delay sensitive flow (delay sensitive traffic).

[0091] The delay sensitive flow is a flow with a high real-time requirement for data transmission. If the delay (a time difference from sending to receiving) or the delay jitter (a variation range of the delay) is too large, the quality of service is significantly affected. The priority of the delay sensitive flow is usually high, and network resources are preferentially occupied to complete data transmission in a short time, and the delay requirement is high.

[0092] The delay sensitive flow can be a real-time communication data flow, for example, a voice communication data flow, a video communication data flow, or an audio data flow. The delay sensitive flow service can also be an interactive service data flow, for example, a game data flow, a virtual reality (VR) data flow, an extended reality (XR) data flow, or a remote control data flow. The delay sensitive flow can also be another data flow, for example, second data, and the priority of the second data is higher than a priority threshold. The embodiments of the present application do not limit the type of the delay sensitive flow.

[0093] 3. Non-delay sensitive flow (non-delay sensitive traffic).

[0094] The non-delay sensitive flow is a flow with a low real-time requirement for data transmission. The non-delay sensitive flow allows a certain delay or delay jitter, and is more concerned about the integrity and reliability of data transmission. The priority of the non-delay sensitive flow is usually low, and the tolerance of the data delay is high, and real-time transmission is not required.

[0095] The non-delay sensitive flow can be a file transmission data flow, for example, an upload or download file data flow, or a cloud storage service data flow. The non-delay sensitive flow service can also be a non-real-time streaming media data flow, for example, a video cache data flow or an audio download data flow. The non-delay sensitive flow service can also be another data flow, and the embodiments of the present application do not limit the type of the non-delay sensitive flow.

[0096] 4. Delay status report (DSR).

[0097] The DSR is a data delay status reported by a terminal device to a network device, and specifically can be a delay status of an LCG provided by the terminal device to a serving base station. The delay status in the delay status report is reported in the granularity of an LCG or an LCH. The following takes an LCG as an example.

[0098] Optionally, the delay status of the LCG includes a remaining time and a data amount of a data packet of the LCG.

[0099] In the embodiments of the present application, the remaining time can be associated with the remaining time of the data packet (such as the first data, the second data, and the delay data) buffered by the LCG, and the data amount can be the total amount of the reported data, which is not described in detail here and will be described later.

[0100] In the embodiments of the present application, the data packet with a remaining time less than the delay reporting threshold can be understood as a data packet with insufficient delay, and is therefore called delay data or delay-sensitive data. The specific type can be the delay-sensitive flow in the above example.

[0101] 5. Minimum configuration threshold.

[0102] The delay reporting threshold list is a set of delay reporting thresholds configured for the terminal device, and the delay reporting threshold list includes one or more delay reporting thresholds. The delay reporting threshold is used to output a delay report in the case that the remaining time of the data in the first data is less than the delay reporting threshold. The minimum configuration threshold is the minimum delay reporting threshold in the one or more delay reporting thresholds.

[0103] 6. Minimum reporting threshold.

[0104] The DSR data is delay data reported by the terminal device to the network device in the history. The data is classified as delay data due to triggering of the delay reporting threshold and is reported to the network device. If the DSR data includes multiple, the minimum delay reporting threshold in the corresponding delay reporting threshold in the multiple DSR data is the minimum reporting threshold.

[0105] In the uplink scheduling request mechanism, the base station supports configuring different numbers of reporting thresholds for different logical channel groups (LCGs), thereby finely controlling the service triggering scheduling request condition of the terminal device. The terminal device can trigger a DSR based on the reporting threshold configured by the base station and report to the base station. The base station can understand the buffer status and data delay condition of the terminal device according to the information in the DSR.

[0106] However, if the allocated resources of the base station are limited, there may be insufficient resource scheduling. In this case, even if the base station receives the DSR sent by the terminal device, it cannot allocate resources to the terminal device. If the terminal device continues to send DSR to the base station, it will occupy signaling resources, resulting in unnecessary signaling overhead and increasing the power consumption of the terminal device.

[0107] Further, considering that part of the first data, such as high-priority data, is not directly associated with the discard timer (used to determine whether the data is discarded due to timeout), but needs to be included in the DSR report to ensure its high-priority scheduling, therefore the threshold association strategy of the high-priority data (i.e., which threshold to associate with) directly affects the signaling overhead, transmission efficiency, and network resource utilization. In actual applications, 5G users often use multiple services at the same time, each service corresponding to a logical channel group; or multiple users communicate concurrently in the same cell. In such scenarios, if the threshold association of high-priority data uses a fixed strategy, it will result in signaling accumulation, occupying limited wireless resources, and reducing overall transmission efficiency.

[0108] Illustratively, if the second data is associated with the minimum reporting threshold, the minimum reporting threshold is valid only when there is delay reporting data. If there is only second data in the LCG without delay data, the minimum reporting threshold cannot be triggered, and the second data cannot be reported to the network through DSR. At this time, the network cannot know the existence of high-priority data, which will cause critical control signaling to be unable to be scheduled in time, resulting in problems such as link error feedback failure, lost data retransmission failure, and even service interruption in severe cases.

[0109] In the multi-LCH LCG scenario, different LCHs can be configured with different reporting thresholds, and the delay data status of each LCH is independent. At this time, the UE needs to coordinate the threshold information of multiple protocol layer entities to determine the minimum reporting threshold of the entire LCG, which not only increases the cross-layer interaction logic of the UE, but also increases the computational burden, which may result in increased power consumption of the terminal device and longer response delay.

[0110] Illustratively, if the second data is associated with the minimum configuration threshold. In actual communication, in a large number of scenarios, the minimum configuration threshold of the LCG has no delay reporting data. In these scenarios, the second data still needs to be associated with the minimum configuration threshold, and the signaling will accumulate rapidly, occupying valuable wireless resources, especially in the edge area with limited bandwidth, which will further cause resource competition to intensify, data transmission delay to increase, and other chain problems, seriously affecting the quality of service.

[0111] Based on this, the embodiments of the present application provide a communication method, which reduces unnecessary delay state reporting of the threshold triggered by dynamically adjusting the DSR, and reduces redundant signaling.

[0112] Further, no matter what threshold the second data is associated with, there may be a problem of poor flexibility that cannot adapt to the dynamic data state. Therefore, in the embodiments of the present application, high-priority data is associated with a dynamically adjusted threshold and is reported synchronously with delayed data. In the case of no delayed data, high-priority data is still reported based on the minimum configuration threshold to avoid missing reports of high-priority data.

[0113] For example, in a satellite communication scenario, such as a low earth orbit satellite network, the network delay is high and the resources are limited, so it is crucial to reduce the signaling overhead of uplink signaling. The communication method provided in the embodiments of the present application can reduce the communication burden between satellites and improve the data transmission efficiency.

[0114] For example, in an Internet of Things environment, multiple devices need to frequently exchange data. The communication method provided in the embodiments of the present application can reduce the frequency and content of device data reporting, reduce communication overhead, and at the same time ensure the effectiveness and timeliness of data transmission.

[0115] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. It can be understood that the main devices (such as terminal devices and network devices) in the illustrative flowcharts provided in the present application are taken as examples to illustrate the execution subject of the method, but the present application does not limit the execution subject of the method. For example, the devices (such as terminal devices and network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the devices to implement the method, and can also be logical modules or software that can implement all or part of the functions of the devices.

[0116] Here, it is uniformly stated that the messages or signaling interactions involved in the interaction flow of the embodiments of the present application can use messages or signaling in standards or newly introduced messages or signaling, and the embodiments of the present application do not make specific limitations.

[0117] Please refer to Figure 1 , Figure 1 is an architecture schematic diagram of a communication system provided by the embodiments of the present application. As shown in Figure 1 , the communication system can include at least one terminal device 101 and at least one network device 102. The terminal device 101 can be connected to the network device 102 in a wireless manner. The terminal device 101 can be a fixed position or can be mobile. The terminal device 101 and the network device 102 can be deployed on land, for example, indoors or outdoors, handheld or vehicle-mounted, etc. The terminal device 101 and the network device 102 can also be deployed on the water surface, airplanes, balloons, and satellites, etc., and the present application does not limit this.

[0118] In the embodiments of the present application, the terminal device 101 can be an entity for receiving or transmitting signals on the user side. The terminal device 101 can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a VR terminal device, an AR terminal device, a customer premise equipment (CPE), an IoT terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a terminal in communication and perception integration, a vehicle-mounted terminal, a vehicle with vehicle-to-vehicle (V2X) communication capability, a smart connected vehicle, a UAV with UAV to UAV (U2U) communication capability, a personal digital assistance (PDA), a smart factory or a smart grid, and the like, without limitation.

[0119] The terminal device 101 can be referred to as a user equipment (UE), a terminal, an access terminal, a UE unit, a UE station, a mobile device, a mobile station, a mobile station, a mobile terminal, a mobile client, a mobile unit, a remote station, a remote terminal device, a remote unit, a wireless unit, a wireless communication device, a user agent, or a user apparatus, etc. Among them, the access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a PDA, a handheld device with wireless communication function, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a PLMN evolved after the 5G communication system, or a terminal device in a non-public network (NPN) evolved after the 5G communication system, etc. In the 5G communication system, the terminal device 101 will adopt new radio technology to establish signal connection and data connection with the network device 102, so as to transmit control signals and service data to the data network.

[0120] The network device 102 can be an entity for transmitting or receiving signals, and is mainly used to implement functions such as wireless physical control, resource scheduling and wireless resource management, wireless access control and mobility management, and provide reliable wireless transmission protocols and data encryption protocols. The network device 102 can support wired access and can also support wireless access, which can be referred to as an access network device hereinafter.

[0121] Optionally, the access network device can be an access network (AN) / radio access network (RAN) device, which is composed of multiple AN / RAN nodes. The AN / RAN node can include but is not limited to an access point (AP), an enhanced node B (eNB), a home base station (for example, a home evolved Node B or a home Node B, HNB), a baseband unit (BBU), a next-generation base station (NR node B, gNB), a transmission reception point (TRP), a transmission point (TP), or some other access node, such as a wireless relay node, a wireless backhaul node, and the like. The AN / RAN node can also be one or more constituent antenna panels, or can be a network node constituting a gNB or a transmission point, such as a BBU or a distributed unit (DU), or can be a device that undertakes a base station function in a D2D, V2X, M2M, U2U, or the like communication system, and the like. The AN / RAN node can also be a wireless controller in a cloud radio access network (CRAN) scenario, or can be an open access network (O-RAN or ORAN), or can be a base station in a communication system evolved after the 5G communication system, such as an xNodeB in a 6G communication system, or can be an access network device in a PLMN network evolved after the 5G communication system, and the like, without limitation.

[0122] The main functions of the access network device include: managing radio resources, compressing internet protocol (IP) headers and encrypting user data streams, selecting a mobile management entity (MME) when a user equipment is attached, routing user plane data to a service gateway (SGW), organizing and sending paging messages, organizing and sending broadcast messages, configuring measurements and measurement reports for mobility or scheduling purposes, and the like.

[0123] Optionally, the network device 102 can also include a core network device for maintaining subscription data of a mobile network, managing network elements of the mobile network, and providing session management, mobility management, policy management, security authentication, and the like for the terminal device 101.

[0124] The NR radio protocol stack is divided into two planes: a user plane (UP) and a control plane (CP). The control plane protocol stack is a protocol cluster used for transmission of control signaling of the system, and the user plane protocol stack is a protocol cluster used for transmission of user data. The NR user plane protocol stack has an additional service data adaptation protocol (SDAP) layer compared to the LTE protocol stack. Taking a terminal device as UE and a network device as gNB as examples, as shown in Figure 2 The user plane protocol stack is sequentially from top to bottom: an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. The SDAP layer includes a service data application protocol, and the main function is to mark a quality of service (Qos) flow identifier in uplink and downlink data packets, and to map the Qos flow to a data radio bearer (DRB). Transmission of data packets on the user plane is mainly completed through the DRB. According to different Qos flows, data between the UE and the gNB can be carried on multiple DRBs.

[0125] The PDCP layer is mainly responsible for compressing and decompressing internet protocol (IP) headers, transmitting user data and maintaining sequence numbers (SNs) for radio bearers (RBs) (used to indicate the transmission order of data packets), and processing RRC messages on the control plane and IP packets on the user plane. On the user plane, the PDCP sublayer can perform header compression and encryption on IP data packets after receiving the IP data packets from the upper layer, and then deliver the IP data packets to the RLC sublayer. The PDCP sublayer can also provide in-sequence delivery and duplicate packet detection functions to the upper layer according to the SN of the PDCP data packet.

[0126] The RLC layer communicates with the PDCP layer through an RLC channel, and communicates with the MAC layer through a logic channel (LCH). The main functions include segmentation and reassembly of RLC service data units (SDUs), automatic repeat-request (ARQ) error correction and duplicate detection, etc.

[0127] The MAC layer is mainly responsible for processing the mapping between the logic channel and the transport channel and the scheduling of the radio resource. The main functions include the mapping between the logic channel and the transport channel, the multiplexing and demultiplexing of the logic channel, and the scheduling, etc. The PHY layer is at the bottom of the air interface protocol stack. It is mainly responsible for coding, modulation, multi-antenna processing, time-frequency resource mapping, etc.

[0128] The SDAP layer, the PDCP layer, the RLC layer, the MAC layer and the PHY layer can also be referred to as SDAP entities, PDCP entities, RLC entities, MAC entities and PHY entities, or can be referred to as SDAP network elements, PDCP network elements, RLC network elements, MAC network elements and PHY network elements, or simply referred to as SDAP, PDCP, RLC, MAC and PHY. It should be understood that the above network elements are only a schematic. In practice, the network elements can be network elements implemented on dedicated hardware, software instances running on dedicated hardware, or instances of virtualized functions on appropriate platforms, for example, a cloud platform. In future communication systems, the above network elements can have other names, which are not limited in the present application.

[0129] In the NR user plane protocol stack, the RLC layer communicates with the PDCP layer (or the RRC layer) through an RLC channel, and communicates with the MAC layer through an LCH. The RLC configuration is an LCH-level configuration, and one RLC entity corresponds to only one LCH of one terminal device. The data received by the RLC entity from the PDCP layer, or the data sent to the PDCP layer, is referred to as an RLC service data unit (SDU) (or a PDCP protocol data unit (PDU)). The data received by the RLC entity from the MAC layer, or the data sent to the MAC layer, is referred to as an RLC PDU (or a MAC SDU).

[0130] The RLC layer includes a transparent mode (TM), an acknowledged mode (AM), and an unacknowledged mode (UM). The RLC layer is mainly responsible for segmenting / reassembling, reassembling, and reassembling and discarding processing of RLC SDUs in the AM and UM; in the AM mode, error correction through ARQ, duplicate detection, re-segmentation of RLC SDU segmentation, and protocol error detection. In addition, the RLC layer can also be used to implement transmission of upper layer PDU and RLC layer reconstruction.

[0131] In the embodiments of the present application, the PDCP entity of the terminal device can be associated with one or more RLC entities. For example, in a standalone (SA) scenario, one PDCP entity can be associated with one RLC entity. In this way, the PDCP entity can deliver data to the RLC entity associated with the PDCP entity, and indicate the PDCP data amount to the MAC entity or the MAC entity associated with the RLC entity.

[0132] Please refer to Figure 3 , Figure 3 A structure schematic diagram of a terminal device provided in the embodiments of the present application is shown in FIG. 1.

[0133] The terminal device includes a threshold state monitoring module, a dynamic association decision module, and a remaining time filling module. Optionally, the three modules are three newly added modules in the protocol stack of the terminal device.

[0134] The threshold state monitoring module can be deployed in the PDCP layer, and is configured to monitor the state of data in the LCG in real time, distinguish between delay data and second data, and provide basic data for subsequent association decision. Optionally, the threshold state monitoring module can obtain all data (such as delay report data, control PDU data, retransmission data, etc.) in the LCG buffer and a configured delay report threshold list.

[0135] In a possible implementation, the threshold state monitoring module is configured to split the input data into second data (such as control PDU data and retransmission data) and delay data according to types, wherein the delay data includes data / packets with a remaining time less than or equal to any delay report threshold in the PDCP layer and / or the RLC layer.

[0136] In one possible implementation, the threshold status monitoring module is configured to mark the presence of delay data. Illustratively, if there is at least one delay data, the has_delay_data is marked as True, and the minimum remainingTimeThreshold item and the amount of delay data are recorded; if there is only control PDU data and retransmission data, the has_delay_data is marked as False.

[0137] In one possible implementation, the threshold status monitoring module is configured to count the amount of data of each type of data. Optionally, the LCG buffer includes second data, and the threshold status monitoring module is configured to count / determine the amount of second data. Optionally, the threshold status monitoring module calculates the total byte size of control PDU data (ctrl_pdu_size) and the total byte size of retransmission data (retrans_size) respectively.

[0138] Optionally, the threshold status monitoring module transmits the marking result and the amount of data to a next module, such as a dynamic association decision module.

[0139] The dynamic association decision module can be deployed at the interface between the RLC and the MAC layer, and is configured to dynamically select the target threshold of the association of the control classification and the statistical data (such as delay data, second data, etc.) according to the output of the threshold status monitoring module, and calculate the total buffer amount of the target threshold.

[0140] In one possible implementation, the dynamic association decision module is configured to dynamically select the association threshold of control PDU data and retransmission data according to the output of the threshold status monitoring module, and calculate the total buffer amount of the target threshold.

[0141] Optionally, if the has_delay_data is True, the target threshold is the minimum reporting threshold, because the threshold already includes the delay data, and there is no need to additionally add a threshold field. If the has_delay_data is False, the target threshold is the minimum configuration threshold, to ensure that the second data (such as control PDU data and retransmission data) can be reported through the threshold.

[0142] Optionally, the process of calculating the total buffer amount of the target threshold by the dynamic association decision module includes: if the target threshold is the minimum reporting threshold, the total buffer amount is obtained by merging the delay data and the high-priority data, that is, the total buffer amount is the sum of delay_data_size, ctrl_pdu_size, and retrans_size; if the target threshold is the minimum configuration threshold, the total buffer amount is obtained based on the second data, that is, the total buffer amount is the sum of ctrl_pdu_size and retrans_size.

[0143] The dynamic association decision module is further configured to output a decision result to the remaining time filling module. Optionally, the decision result comprises a target threshold target_threshold, which is a minimum reporting threshold or a minimum configuration threshold, and a total buffer size total_buffer_size of the target threshold. Optionally, if the target threshold is the minimum reporting threshold, the dynamic association decision module is further configured to output a minimum remaining time (min_remaining_time, such as 15 ms) of the delayed data under the threshold to the remaining time filling module.

[0144] The remaining time filling module, which can be deployed in the MAC layer, is configured to generate a remaining time field (or referred to as a first field) of the target threshold, and distinguish the scenario of only containing the second data through a special marker, to assist the network in accurate scheduling.

[0145] In one possible implementation, if the target threshold is the minimum reporting threshold, which belongs to a general scenario of existing delayed data, the remaining time field directly multiplexes the minimum remaining time of the delayed data to reflect the urgency of the data. Exemplarily, the remaining time field can be min_remaining_time.

[0146] In another possible implementation, if the target threshold is the minimum configuration threshold, which belongs to a special scenario of non-existing delayed data and only reporting the second data, in this scenario, the remaining time field can comprise a special marker (such as 0xFFFF) and the minimum configuration threshold (such as 10 ms), and the network identifies that the data reported this time does not exist delayed data and only high-priority data through the special marker. Optionally, the output result of the remaining time filling module is a formatted remaining time field, which is used for DSR MAC CE encapsulation.

[0147] Please refer to Figure 4 , Figure 4 is a flowchart of a communication method provided by an embodiment of the present application. The method can be implemented based on a hardware architecture of a communication system as shown in Figure 1 or a protocol layer architecture as shown in Figure 2 , or other architectures. The method comprises the following steps, but is not limited to the following steps:

[0148] In step S401, the terminal device determines whether the first data in the logical channel group exists delayed data.

[0149] The terminal device can be the terminal device as exemplified in the above Figure 3 .

[0150] The delayed data includes data whose remaining time of data discard (e.g., remaining value of a discard timer) is less than any one of the delay reporting thresholds in the delay reporting threshold list dsr-ReportingThresholdList.

[0151] The remaining time can be counted down from the delay reporting threshold by the PDCP entity applying (starting or enabling) the discard timer of each data packet, i.e., the remaining time of data discard is the (minimum) remaining value of the discard timer of the data packet buffered in the LCG.

[0152] Optionally, the logical channel group LCG includes one or more logical channels LCHs.

[0153] In one possible implementation, the first data is all data / data packets in the logical channel group.

[0154] In another possible implementation, the first data is all data / data packets in any one of the one or more logical channels.

[0155] In yet another possible implementation, the first data is part of the data in the logical channel group, e.g., a buffer area in the logical channel group is used to buffer the delayed data, and the first data is the delayed data in the buffer area. In this implementation, the amount of data of the first data can be 0, representing no delayed data.

[0156] In one possible implementation, the terminal device obtains a delay reporting threshold list including one or more delay reporting thresholds. Optionally, the delay reporting threshold list is configured by the network device for the terminal device (or the LCG). Correspondingly, the network device sends the delay reporting threshold list including one or more delay reporting thresholds to the terminal device.

[0157] The terminal device can determine whether there is delayed data in the first data in the logical channel group based on the delay reporting threshold list.

[0158] In one possible implementation, the terminal device determines second data in the first data and the amount of data of the second data. In the above implementation, the terminal device determines the second data in the first data and the amount of data of the second data, ensuring independent statistics and reporting of high-priority data, so that the network device can preferentially allocate resources to critical data such as control signaling and retransmission packets, improving link reliability and service continuity, and reducing the risk of error accumulation and connection interruption caused by critical data not being scheduled in time.

[0159] In a possible implementation, the first data includes second data, a priority of the second data is higher than the priority threshold, and the priority of the second data is related to a reporting requirement time of the second data.

[0160] Optionally, the reporting requirement time can be a maximum allowed reporting delay time corresponding to the QoS requirement.

[0161] In a possible implementation, the second data includes PDU data and / or retransmission data of a PDCP layer.

[0162] Exemplarily, the PDU data can be critical control signaling, such as control PDU data. RLC (Radio Link Control) PDU is divided into two categories: data PDU and control PDU. The data PDU includes three structures corresponding to transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM), respectively, and carries original data transmission or segmented retransmission functions. The control PDU mainly refers to a STATUS PDU, which is used for feedback of the ARQ retransmission mechanism in the AM mode. The RLC control PDU is mainly a STATUS PDU, which is used for the receiving part of the AM RLC entity to notify the peer AM RLC entity about the information that the RLC data PDU has been successfully received, and the information that the RLC data PDU is detected to be lost by the receiving part of the AM RLC entity.

[0163] In a possible implementation, the second data includes delay-sensitive data and / or delay-sensitive data flow. In some embodiments, the terminal device can determine the data type of any data in the LCG buffer based on a quality of service identifier (QI) corresponding to the LCG.

[0164] In another implementation, the quality of service identifier includes a resource type, when the resource type is a delay critical guaranteed bit rate (delay critical GBR), the data type of data applying the resource type is delay-sensitive data or delay-sensitive data flow. When the resource type is a guaranteed bit rate (GBR) or a non-GBR, the data type of data applying the resource type is non-delay-sensitive flow.

[0165] The resource type is used to distinguish different service demand modes of network resources, and the resource type can determine the resource allocation strategy. The resource type can include GBR, non-GBR, and delay critical GBR.

[0166] Among them, the GBR service requires the network device to reserve fixed bandwidth resources to ensure the minimum bit rate guarantee, which is suitable for services with stable bandwidth and high real-time requirements. The non-GBR service does not require the network device to reserve fixed bandwidth resources, and the network device can allocate resources dynamically, which is suitable for services with certain delay or bandwidth fluctuation. The delay critical GBR requires the network device to ensure both bandwidth resources and extremely low delay, which is suitable for services with low delay and high reliability requirements.

[0167] In some embodiments, the network device can determine the data flow type corresponding to the LCG based on the quality of service identifier QI corresponding to the LCG, and indicate the data flow type corresponding to the LCG to the terminal device. The network device can also predefine the data flow type corresponding to the LCG, and indicate the data flow type corresponding to the LCG to the terminal device. The determination method of the data flow type corresponding to the LCG is not limited in the embodiments of the present application.

[0168] In summary, the data type corresponding to the LCG can be determined based on the packet delay budget or resource type in the quality of service identifier corresponding to the LCG. The data type corresponding to the LCG can also be predefined by the network device, so that the terminal device can determine that a certain data is delay-sensitive data or non-delay-sensitive data, and then combine the delay-sensitive data with the delay data and / or the second data based on the DSR for reporting.

[0169] Considering that data transmission needs to rely on the cooperative work of multiple protocol stacks (including PDCP layer, RLC layer, MAC layer, etc.), each layer implements reliable transmission and efficient scheduling of data through division of labor and cooperation. Among them, the control PDU (such as PDCP control PDU, RLC STATUS PDU) is responsible for maintaining the link state (such as link connectivity, error feedback), and the retransmission data (such as PDCP / RLC layer retransmission PDU / service data unit SDU) is used to supplement the missing or erroneous data, which together guarantee the integrity of data transmission, and are the core functional components of 5G network.

[0170] In some embodiments, the DSR triggering operation described above, such as determining whether there is delay data, can be performed by a first entity, such as a PDCP entity. When the terminal device is configured with a time threshold related to the logical channel group (such as the delay reporting threshold list or one of the delay reporting threshold list described above), the PDCP entity associated with the logical channel of the logical channel group still determines whether to trigger DSR for the LCG according to the target threshold.

[0171] More specifically, the PDCP entity can trigger the DSR when the remaining time of the discard timer associated with the PDCP SDU is less than or equal to the delay reporting threshold, and the triggered DSR with the remaining time can be indicated to the lower layer (e.g., the MAC layer). In some embodiments, the PDCP entity triggering the DSR can mean that the PDCP entity instructs the lower layer (e.g., the MAC layer) to trigger the DSR. Wherein, the PDCP SDU is a basic unit of data processed by the PDCP layer, which contains data to be transmitted and some necessary control information for correct processing and routing during transmission.

[0172] In some embodiments, the PDCP entity can trigger the DSR if the remaining time of the PDU set becomes less than or equal to the time threshold. More specifically, the PDCP entity can trigger the DSR if the PDCP SDU corresponding to the PDU with the smallest sequence number in the PDU set, when the remaining time of the discard timer associated with the PDCP SDU is less than or equal to the delay reporting threshold, and the triggered DSR can be indicated to the lower layer (e.g., the MAC layer). The associated triggering information can include at least one of the PDU set ID triggering the DSR, the sequence number of the PDCP SDU triggering the DSR, the remaining time of the discard timer of the PDU set (or the PDCP SDU) triggering the DSR.

[0173] In some embodiments, the PDCP entity can trigger the DSR if the remaining time of the PDU set is less than or equal to the delay reporting threshold. More specifically, the PDCP entity can trigger the DSR when the remaining time of the discard timer associated with one of the PDCP SDUs corresponding to the PDUs in the PDU set is less than or equal to the delay reporting threshold, and the triggered DSR can be indicated to the lower layer (e.g., the MAC layer). The associated triggering information can include at least one of the PDU set ID triggering the DSR, the sequence number of the PDCP SDU triggering the DSR, the remaining time of the discard timer of the PDU set (or the PDCP SDU) triggering the DSR.

[0174] See Figure 5 , Figure 5 A flowchart of another communication method provided by an embodiment of the present application is shown. Optionally, before step S401 described above, there is also step S403: the terminal device determines the data type of the data in the LCG buffer, which includes high-priority data and delay data.

[0175] Optionally, the terminal device determines the data type of the data in the LCG buffer, which is mainly used to determine the high priority data in the buffer. For example, the terminal device determines the second data in the first data.

[0176] Optionally, after step S401, the terminal device marks the result of whether there is delay data. For example, the marking content includes: if there is at least one delay data, marking has_delay_data = True, and the minimum item of remainingTimeThreshold and the amount of delay data. If there is no delay data, only control PDU data and / or retransmission data, marking has_delay_data = False.

[0177] In one possible implementation, before step S402, there is also step S404, the terminal device determines the data amount based on the data type. Optionally, the terminal device can determine the data amount corresponding to each data type based on the data type. For example, the LCG buffer includes the second data, the terminal device can determine the data amount of the second data, or the terminal device can determine the data amount of the second data. Alternatively, the terminal device can determine the total byte number of the control PDU data and the total byte number of the retransmission data.

[0178] Step S402: The terminal device sends a resource request message to the network device. Correspondingly, the network device receives the resource request message sent by the terminal device.

[0179] The resource request message is used to request to configure resources for the first data, and the resource request message includes a target threshold value associated with the first data. The target threshold value is used to determine the transmission time of the DSR report by the receiver of the resource request message, such as the network device.

[0180] In combination Figure 6 , Figure 6 Another communication method provided by the embodiment of the present application is shown in the flowchart. In Figure 6 In the corresponding implementation, after step S401 and before step S402, there is also step S405, in which the terminal device determines the target threshold value based on whether there is delay data.

[0181] In the case where there is delay data in the first data, the target threshold value is a first threshold value, and the first threshold value is the minimum value of the delay report threshold value corresponding to one or more delay data in the delay status report (DSR) data. The first threshold value can also be referred to as the minimum report threshold value. In the case where there is no delay data in the first data, the target threshold value is a second threshold value, and the second threshold value includes the minimum value in the delay report threshold value list. The second threshold value can also be referred to as the minimum configuration threshold value.

[0182] It should be understood that if there is delay data, the target threshold is the first threshold, or the minimum reporting threshold, because the threshold already contains the delay data, and there is no need to additionally add a threshold field. If there is no delay data, the target threshold is the second threshold, or the minimum configuration threshold, to ensure that the second data (such as control PDU data and retransmission data) can be reported through the threshold.

[0183] Optionally, the delay status report (DSR) data is historical delay data of the terminal device reported to the network device. If the DSR data includes multiple, the minimum delay reporting threshold in the corresponding delay reporting threshold in the multiple DSR data is the first threshold, so the first threshold can be referred to as the minimum reporting threshold.

[0184] Optionally, the delay reporting threshold list is a set of delay reporting thresholds configured by the network for the terminal device, and the delay reporting threshold list includes one or more delay reporting thresholds. The delay reporting threshold is used to output a delay report when the remaining time of the data in the first data is less than the delay reporting threshold. In the implementation where the delay reporting threshold list includes multiple delay reporting thresholds, the second threshold is the minimum delay reporting threshold in the multiple delay reporting thresholds. Since the threshold is configured by the network, it can also be referred to as the minimum configuration threshold.

[0185] In the implementation where the delay reporting threshold list includes one delay reporting threshold, the second threshold is the delay reporting threshold.

[0186] In a possible implementation, in the case where there is no delay data in the first data, and the second threshold is less than the reporting requirement time of the second data, the value of the target threshold is related to the reporting requirement time of the second data.

[0187] In the above implementation, when there is no delay data in the first data and the minimum configuration threshold is less than the reporting requirement time of the second data, the target threshold is related to the reporting requirement time. The above implementation improves the response speed and scheduling accuracy of high-priority data by allowing the terminal device to autonomously adjust the threshold to match the service QoS requirement, and reduces the risk of transmission delay and service quality degradation caused by mismatched thresholds.

[0188] Exemplarily, the value of the target threshold is greater than the reporting requirement time of the second data, to meet the reporting requirement time of the second data and avoid delay.

[0189] Optionally, the above method further includes the following operation: in the case where there is delay data, the terminal device determines the target threshold based on the reporting requirement time of the second data, and the value of the target threshold is related to the reporting requirement time of the second data.

[0190] In a possible implementation, the resource request message further comprises a first field, and in the case that the delay data exists in the first data, the first field comprises a second field for indicating the remaining time of the delay data.

[0191] In the case that the delay data does not exist in the first data, the first field comprises a first identifier for indicating that the delay data is not included in the first data.

[0192] In the above implementation, the resource request message contains the first field and indicates the remaining time in the case that the delay data exists and uses the first identifier in the case that the delay data does not exist, which provides clear delay state information, enables the network device to quickly distinguish the urgency of data, optimizes the scheduling decision process, reduces the processing complexity and signaling analysis delay, and enhances the adaptability of the network in a dynamic scenario such as concurrent multiple LCGs.

[0193] In a possible implementation, the remaining time of the delay data can be the shortest remaining time of the plurality of delay data.

[0194] In another possible implementation, in the case that the number of the delay data is only one, the remaining time of the delay data is the remaining time of the delay data.

[0195] In a possible implementation, the resource request message further comprises a data amount or a total data amount. In a possible implementation, the first data is a collective term of the delay data and the second data, and the data amount is the data amount of the first data. Further, in the implementation in which the delay data does not exist, the data amount is specifically the data amount of the second data.

[0196] In a possible implementation, the calculation process of the data amount can be performed by the first entity / PDCP entity. Of course, the result of the calculation process of the data amount can be indicated to the lower layer (for example, the MAC layer).

[0197] In order to report the MAC delay state (for example, triggering the DSR, generating the DSR MAC CE), the RLC entity (of the sending) can be instructed by the upper layer (for example, the PDCP layer) or the lower layer (for example, the MAC layer) to perform the RLC delay key data amount calculation process to output the number of RLC delay key data and the remaining time of the RLC delay key data. The RLC entity can indicate the result of the RLC delay key data amount calculation process to the MAC entity.

[0198] In one possible implementation, if the minimum configuration threshold is less than the reporting time requirement for the second data, and the target threshold value is adjusted, an identifier indicating that the terminal device can autonomously select the remaining time is appended to the first field of the resource request message. Optionally, the resource request message further includes a first field containing a second identifier, which indicates that the value of the target threshold is related to the reporting time requirement for the second data.

[0199] In the above implementation, the first field of the resource request message includes a second identifier, which is used to indicate that the target threshold is related to the reporting time of the request. This clearly conveys the terminal's autonomous decision-making status to the network device, promotes collaborative optimization between the network and the terminal, reduces the possibility of signaling misunderstandings and configuration conflicts, and enhances the robustness and efficiency of the system in edge areas or bandwidth-constrained scenarios.

[0200] The following is combined with Figure 7 , Figure 8 and Figure 9 The target threshold, data volume, and resource request messages are illustrated in both scenarios with and without delayed data. Figure 7 A schematic diagram of a data monitoring process provided in an embodiment of this application; Figure 8 A schematic diagram illustrating a target threshold determination process provided in an embodiment of this application; Figure 9 This is a flowchart illustrating the determination of a first field according to an embodiment of this application. It should be noted that the second data (such as high-priority data) in the following scenarios will be illustrated using control PDU data and retransmission data as examples.

[0201] Scenario 1 is a scenario where there is delayed data.

[0202] Scenarios involving delayed data can refer to situations where the terminal device or its threshold status monitoring module is marked with `has_delay_data = True`. In scenario 1, the data and parameters involved conform to the standard, as detailed below:

[0203] The network is configured with a list of latency reporting thresholds for LCG: This list includes latency reporting thresholds with values ​​of {10ms, 20ms, 50ms}.

[0204] Delay report data: Remaining time for a certain data in the PDCP layer = 20ms.

[0205] Minimum reporting threshold: 20ms (the minimum threshold that matches the delay data in the delay reporting threshold list).

[0206] Control PDU data volume: 20 bytes, retransmission data volume: 50 bytes, delayed data volume: 100 bytes.

[0207] In scenario 1, the terminal device can split the input data into: delay data, control PDU data (such as PDCP control PDU), retransmission data (such as RLC layer retransmission PDU).

[0208] The terminal device reports the data with a delay of 20 ms, and marks has_delay_data = True, and records the minimum reporting threshold = 20 ms, and the data amount statistics are: ctrl_pdu_size = 20 bytes, retrans_size = 50 bytes, and delay_data_size = 100 bytes.

[0209] Further, referring to Figure 8 , the terminal device determines the target threshold based on the above content. The target threshold is the minimum reporting threshold (20 ms), and considering that the threshold already carries the delay data, there is no need to add the remainingTimeThreshold field, avoiding signaling redundancy.

[0210] The terminal device determines the total buffer amount of the first data, and the total buffer size (total_buffer_size) is the sum of the delay data amount, the control PDU amount, and the retransmission data amount, which is specifically 170 bytes, ensuring that all related data under the target remainingTimeThreshold is included for network side resource scheduling reference. Optionally, the result of determining the total buffer amount of the first data can reuse the statistics result in Figure 7 .

[0211] Further, the terminal device determines the remaining time field, i.e., the first field, and then transmits the field to the network side through the resource request message. The first field includes but is not limited to the following content:

[0212] LCG ID, target LCG identifier. The target threshold is remainingTimeThreshold, which takes a value of 20 ms. The second field includes the remaining time remainingTime: 20 ms (taking the shortest remaining time of the delay data as an example for illustration). Total buffer amount, 170 bytes.

[0213] Scenario 2 is a scenario without delay data.

[0214] This scenario is for a scenario where only control PDU data and retransmission data exist in the LCG buffer area, without any delay data, and through dynamic association of the threshold and adaptive remaining time reporting, it is ensured that high priority data (control PDU data and / or retransmission data) is not missed and scheduling is efficient. In scenario 2, the data and parameters involved are consistent with the standard, and are specifically as follows:

[0215] The structure of the delay report threshold list is: [Thres1=10ms, Thres2=20ms, Thres3=50ms], and the priority is in ascending order of threshold value, and the smaller the value, the higher the priority.

[0216] Minimum configuration threshold: 10ms (the threshold with the smallest value in the delay report threshold list, i.e., Thres1).

[0217] The control PDU data amount is 20 bytes, the retransmission data amount is 50 bytes, and the total buffer amount is 70 bytes.

[0218] The minimum configuration threshold does not meet the reporting requirement of the second data, for example, the minimum configuration threshold (10ms) is greater than the reporting requirement time corresponding to the actual urgency of the control PDU / retransmission data (for example, the control PDU of URLLC service needs to be reported within 8ms, and 10ms cannot meet the low delay requirement). In addition, the data classification and processing flow can refer to the content of the example in Figure 7 .

[0219] Further, the terminal device can determine whether the minimum configuration threshold meets the reporting requirement time of the second data (control PDU data and / or retransmission data). For example, the terminal device combines the QoS requirement (reporting delay ≤8ms) of the control PDU data to determine that the minimum configuration threshold 10ms>8ms, and the minimum configuration threshold does not meet the reporting requirement time, and config_thres_satisfied= False is marked. In this scenario, the terminal device can autonomously select a suitable remaining time, such as 8ms (which meets the QoS requirement of URLLC service).

[0220] In the scenario where there is no delay data, the initially associated target threshold is the minimum configuration threshold, but because config_thres_satisfied= False, it needs to be switched to the "UE autonomously selects the remaining time" mode, that is, the terminal device re-determines the target threshold based on the reporting requirement time of the second data.

[0221] The above process of re-determining the target threshold can be as follows:

[0222] 1. Suitable remaining time selection, the terminal device inputs the QoS requirement: for example, the URLLC service (5QI=65) requires that the reporting delay be ≤8ms.

[0223] 2. Candidate value screening: in the allowed range of 1~1000ms, select a value less than or equal to 8ms and closest to the QoS requirement, that is, the target threshold is 8ms, to avoid excessive conservation leading to resource waste.

[0224] In combination with Figure 9In the scenario where there is no delay data but high priority data needs to be reported, the second field can include the first identifier and / or the second identifier and the remaining time, and the first identifier and / or the second identifier can be the special mark described above. The first identifier is used to indicate that the delay data is not included in the first data. The second identifier is used to indicate that the value of the target threshold is related to the reporting requirement time of the second data. In scenario 2, the second field includes the first identifier and the second identifier.

[0225] Exemplarily, the special mark can be fixed as 0xFFFF. Exemplarily, the second field is [0xFFFF], 8 ms.

[0226] In scenario 2, the finally generated resource request message includes but is not limited to the following contents:

[0227] LCG ID. The second field, special scenario mark, is used to identify that there is no delay data in this report and the UE autonomously adjusts the remaining time. Among them, UE-Selected Remaining Time: UE autonomously selected remaining time (8 ms).

[0228] Buffer Size: 70 bytes.

[0229] It should be noted that the above-mentioned contents related to values in scenarios 1 and 2 are designed by the embodiments of the present application for the purpose of facilitating understanding. In actual application, the above-mentioned values, such as threshold region, data amount, etc. can be other values, and the embodiments of the present application do not limit this.

[0230] Optionally, the terminal device receives the delay report threshold related to the LCG through the radio resource control (Radio Resource Control, RRC) signaling. Some embodiments of the present application can use the delay state report of the buffer data via the dedicated MAC CE (for example, DSR MAC CE).

[0231] Optionally, the above-mentioned resource request message is DSR.

[0232] Optionally, after the above-mentioned step S402, the network device can parse the resource request message and identify the threshold type and the first field therein. Further, the network device allocates time-frequency resources for the terminal device (or the first data) based on the resource request message. The terminal device can transmit the first data based on the time-frequency resources, and the first data at least includes the second data, so as to realize the combined reporting of the second data and the delay data.

[0233] Correspondingly, the network device returns an acknowledgement message after receiving the first data. The terminal device receives the acknowledgement message from the network device.

[0234] In the above implementation, the terminal device dynamically selects the target threshold based on whether there is delayed data in the logical channel group. When delayed data exists, the minimum reporting threshold is used, and when it does not exist, the minimum configuration threshold is used, which improves the flexibility of resource requests and reduces the signaling overhead when there is no delayed data.

[0235] It should be understood that Figures 1 to 9 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 9 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0236] The above text combined Figures 1 to 9 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figure 10 and Figure 11 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0237] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0238] By way of example, embodiments of this application also provide a communication device.

[0239] Please see Figure 10 , Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0240] The communication device 1000 may include a processing module 1010 and a communication module 1020. The communication module 1020 can implement corresponding communication functions, which can be internal communication functions of the communication device 1000 or communication functions between the communication device 1000 and other devices. Optionally, the communication module 1020 may also be referred to as a communication interface or a transceiver module. The processing module 1010 can implement corresponding processing functions.

[0241] Optionally, the communication apparatus 1000 further includes a storage module, which can be used to store instructions and / or data; the processing module 1010 can read the instructions and / or data in the storage module, so that the communication apparatus 1000 implements the foregoing method embodiments.

[0242] In a possible design, the communication apparatus 1000 can correspond to a terminal device in the foregoing method embodiments, or a component (such as a circuit, a chip, or a chip system, etc.) configured in the terminal device. The communication apparatus 1000 can be used to execute steps or procedures performed by the terminal device in any of the foregoing method embodiments.

[0243] In some embodiments, the processing module 1010 determines whether there is delay data in the first data in the logical channel group, the delay data including data whose remaining time of data discard is less than any one of delay reporting thresholds in the delay reporting threshold list.

[0244] The communication module 1020 sends a resource request message, the resource request message being used to request to configure resources for the first data, the resource request message including a target threshold value associated with the first data; in a case where there is delay data in the first data, the target threshold value is a first threshold value, the first threshold value being a minimum value of delay reporting thresholds corresponding to one or more pieces of delay data in delay status reporting (DSR) data, and in a case where there is no delay data in the first data, the target threshold value is a second threshold value, the second threshold value including a minimum value in the delay reporting threshold list.

[0245] In some embodiments, the first data includes second data, a priority of the second data being higher than a priority threshold value, the priority of the second data being related to a reporting requirement time of the second data, and the resource request message further includes a total data amount of the first data. Optionally, the priority is related to a remaining time of corresponding data, and the shorter the remaining time, the higher the priority. Optionally, the priority threshold value is a threshold value configured by a network device or predefined to distinguish data priorities, or the priority threshold value is related to a minimum configuration threshold value, for example, a value in the priority threshold value is obtained based on the minimum configuration threshold value.

[0246] In some embodiments, the second data includes PDCP protocol data unit (PDU) data and / or retransmission data.

[0247] In some embodiments, the resource request message further includes a first field,

[0248] In a case where there is delay data in the first data, the first field includes a second field used to indicate a remaining time of the delay data.

[0249] In a case where the first data does not include the delay data, the first field includes a first identifier, and the first identifier is used to indicate that the first data does not include the delay data.

[0250] In some embodiments, in a case where the first data does not include the delay data and the second threshold is smaller than a reporting requirement time of the second data, the target threshold is determined according to the reporting requirement time of the second data.

[0251] In some embodiments, the resource request message further includes a first field, and the first field includes a second identifier, and the second identifier is used to indicate that the target threshold is determined according to the reporting requirement time of the second data.

[0252] In some embodiments, the processing module 1010 determines the second data in the first data and a data amount of the second data before determining whether the first data in the logical channel group includes the delay data.

[0253] In some embodiments, the communication module 1020 acquires a delay report threshold list, and the delay report threshold list includes one or more delay report thresholds; and the processing module 1010 determines whether the first data in the logical channel group includes the delay data, including: the communication module 1020 determines whether the first data in the logical channel group includes the delay data based on the delay report threshold list.

[0254] The above is only an example, and detailed steps or processes can refer to the descriptions of the foregoing embodiments.

[0255] In a possible design, the communication apparatus 1000 can correspond to a network device in the foregoing method embodiments, or be configured as a component (such as a circuit, a chip, or a chip system, etc.) in the network device. The communication apparatus 1000 can be used to perform steps or processes performed by the network device in any of the foregoing method embodiments.

[0256] In some embodiments, the communication module 1020 is configured to receive a resource request message, and the resource request message is used to request to configure resources for first data in a logical channel group, and the resource request message includes a target threshold associated with the first data.

[0257] In a case where the first data includes the delay data, the target threshold is a first threshold, and the first threshold is a minimum value of delay report thresholds corresponding to one or more delay data in delay status report (DSR) data; and in a case where the first data does not include the delay data, the target threshold is a second threshold, and the second threshold includes a minimum value in a delay report threshold list.

[0258] The communication module 1020 is configured to configure time-frequency resources for the first data based on the resource request message.

[0259] Exemplarily, the embodiment of the present application further provides a communication device.

[0260] Please refer to Figure 11 , Figure 11 The structure schematic diagram of another communication device provided by the embodiment of the present application is shown.

[0261] As Figure 11 shown, the communication device 1000 can be a terminal device or a network device chip, chip system, or processor, etc. implementing the above method. The communication device 1000 can be used to implement the method described in the above method embodiment, and the specific implementation can refer to the description in the above method embodiment.

[0262] The communication device 1000 can include one or more processors 1110, which can also be called processing units or processing modules, and can implement certain control functions. The processor 1110 can be a general-purpose processor or a special-purpose processor, etc., for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device 1000 (such as a base station, a baseband chip, a user, and a user chip), execute software programs, and process data of software programs.

[0263] In an optional design, the processor 1110 can also store instructions and / or data, which can be run by the processor 1110, so that the communication device 1000 executes the method described in the above method embodiment.

[0264] In another optional design, the communication device 1000 can include a communication interface 1120 for implementing receiving and sending functions. For example, the communication interface 1120 can be a transceiver circuit, an interface, an interface circuit, or a transceiver, etc. The transceiver circuit, the interface, the interface circuit, or the transceiver for implementing receiving and sending functions can be separate or integrated together. The above transceiver circuit, interface, interface circuit, or transceiver can be used for code / data reading and writing, or the above transceiver circuit, interface, interface circuit, or transceiver can be used for signal transmission or transfer.

[0265] Optionally, the communication device 1000 can include one or more memories 1130, which can store instructions that can be run on the processor 1110, so that the communication device 1000 executes the method described in the above method embodiment. Optionally, the memory 1130 can also store data. Optionally, the processor 1110 can also store instructions and / or data. The processor 1110 and the memory 1130 can be separately arranged or integrated together.

[0266] It should be understood that, in a possible design, each step in the method embodiments provided in the present application can be completed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as execution completed by a hardware processor, or execution completed by a combination of hardware and software modules in the processor. The software modules can be located in storage media which are mature in the art, such as random storage, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, register, etc. The storage media are located in the storage, and the processor reads information in the storage, and combines the hardware to complete the steps of the above method. To avoid repetition, no longer detailed description is made here.

[0267] In an implementation, the communication apparatus 1000 can correspond to the terminal device in the above method embodiments, and can be used to execute each step and / or process executed by the terminal device in the above method embodiments. The processor 1110 can be used to execute instructions stored in the memory 1130, and when the processor 1110 executes the instructions stored in the memory, the processor 1110 is used to execute each step and / or process of the above method embodiments corresponding to the terminal device.

[0268] In another implementation, the communication apparatus 1000 can correspond to the network device in the above method embodiments, and can be used to execute each step and / or process executed by the network device in the above method embodiments. The processor 1110 can be used to execute instructions stored in the memory 1130, and when the processor 1110 executes the instructions stored in the memory, the processor 1110 is used to execute each step and / or process of the above method embodiments corresponding to the network device.

[0269] It should be understood that the above processing apparatus can be one or more chips. For example, the processing apparatus can be a field programmable gate array (FPGA), can be an application specific integrated circuit (ASIC), can also be a system on chip (SoC), can also be a central processor unit (CPU), can also be a network processor (NP), can also be a digital signal processor (DSP), can also be a micro controller unit (MCU), can also be a programmable logic device (PLD) or other integrated chip.

[0270] It is to be appreciated that the memory in the embodiments of the application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Where the nonvolatile memory is a read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), or flash memory. The volatile memory can be a random access memory (RAM), which is used as external cache. By way of example, and not limitation, many forms of RAM are available, for example, static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DR RAM). Note that the system and method described herein is intended to include all such memory types and any other suitable type of memory.

[0271] According to the method provided by the embodiments of the application, the application further provides a chip system, which comprises one or more processors, and is used for calling and running instructions stored in a memory, so that the method of the embodiments of the application is executed. The chip system can be composed of a chip, or can include a chip and other discrete devices.

[0272] The chip system can include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0273] According to the method provided by the embodiments of the application, the application further provides a communication system, which comprises the network device and the terminal device described above.

[0274] According to the method provided in the embodiments of the present application, the present application further provides a computer program product, which comprises computer program codes, and when the computer program codes are run on a computer, the computer is caused to execute each step or procedure executed by the network device and the terminal device in any of the preceding method embodiments.

[0275] According to the method provided in the embodiments of the present application, the present application further provides a computer readable storage medium, which stores program codes, and when the program codes are run on a computer, the computer is caused to execute each step or procedure executed by the network device and the terminal device in any of the preceding method embodiments.

[0276] The computer readable storage medium can be the volatile memory or the non-volatile memory described above, or can simultaneously include the volatile memory and the non-volatile memory.

[0277] In the embodiments of the present application, each term and English abbreviation is an exemplary example given for convenience of description, and should not constitute any limitation on the present application. The present application does not exclude the possibility of defining other terms capable of achieving the same or similar functions in the existing or future protocols.

[0278] In the above embodiments, all or part of the embodiments can be realized by software, hardware, firmware or any combination thereof. When realized by software, all or part of the embodiments can be realized in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated.

[0279] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other means. For example, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0280] It should be understood that in various embodiments of the present application, the size of the serial number of each process does not mean the execution order, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0281] In conclusion, the above is only a preferred embodiment of the technical scheme of the present application, and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: Determine whether there is delayed data in the first data in the logical channel group, wherein the delayed data includes data whose remaining time for data discarding is less than any delay reporting threshold in the delay reporting threshold list; A resource request message is sent, which requests the configuration of resources for the first data. The resource request message includes a target threshold associated with the first data. If delayed data exists in the first data, the target threshold is a first threshold, which is the minimum value among the delay report thresholds corresponding to one or more delayed data points in the Delay Status Report (DSR) data. If there is no delayed data in the first data, the target threshold is a second threshold, which includes the minimum value in the delay report threshold list.

2. The method according to claim 1, characterized in that, The first data includes the second data, the second data has a higher priority than the priority threshold, the priority of the second data is related to the reporting time of the second data, and the resource request message also includes the total amount of the first data.

3. The method according to claim 2, characterized in that, The second data includes PDCP protocol data unit (PDU) data and / or retransmission data.

4. The method according to any one of claims 1-3, characterized in that, The resource request message also includes a first field. If delayed data exists in the first data, the first field includes a second field indicating the remaining time of the delayed data; If there is no delayed data in the first data, the first field includes a first identifier, which is used to indicate that the first data does not include delayed data.

5. The method according to claim 2 or 3, characterized in that, If there is no delayed data in the first data and the second threshold is less than the reporting time of the second data, the value of the target threshold is related to the reporting time of the second data.

6. The method according to claim 5, characterized in that, The resource request message also includes a first field, which includes a second identifier. The second identifier is used to indicate that the value of the target threshold is related to the reporting time of the second data.

7. The method according to any one of claims 1-3 and 6, characterized in that, The method further includes: Determine the second data in the first data, and the amount of the second data.

8. The method according to any one of claims 1-3 and 6, characterized in that, The method further includes: Obtain a list of delay reporting thresholds, wherein the list of delay reporting thresholds includes one or more delay reporting thresholds; Determining whether delayed data exists in the first data in the logical channel group includes: Based on the delay report threshold list, determine whether there is delayed data in the first data of the logical channel group.

9. A communication method, characterized in that, The method is applied to a network device, and the method includes: Receive a resource request message, the resource request message being used to request resource allocation for first data in a logical channel group, the resource request message including a target threshold associated with the first data; Wherein, if there is delayed data in the first data, the target threshold is a first threshold, which is the minimum value among the delay report thresholds corresponding to one or more delayed data in the Delay Status Report (DSR) data; if there is no delayed data in the first data, the target threshold is a second threshold, which includes the minimum value in the delay report threshold list. Based on the resource request message, time-frequency resources are configured for the first data.

10. The method according to claim 9, characterized in that, The first data includes the second data, the second data has a higher priority than the priority threshold, the priority of the second data is related to the reporting time of the second data, and the resource request message also includes the total amount of the first data.

11. The method according to claim 10, characterized in that, The second data includes PDCP protocol data unit (PDU) data and / or retransmission data.

12. The method according to any one of claims 9-11, characterized in that, The resource request message also includes a first field. If delayed data exists in the first data, the first field includes a second field indicating the remaining time of the delayed data; If there is no delayed data in the first data, the first field includes a first identifier, which is used to indicate that the first data does not include delayed data.

13. The method according to claim 10 or 11, characterized in that, If there is no delayed data in the first data and the second threshold is less than the reporting time of the second data, the value of the target threshold is related to the reporting time of the second data.

14. The method according to claim 13, characterized in that, The resource request message also includes a first field, which includes a second identifier. The second identifier is used to indicate that the value of the target threshold is related to the reporting time of the second data.

15. The method according to any one of claims 9-11, 14, characterized in that, The method further includes: Send a list of delay report thresholds, which includes one or more delay report thresholds.

16. An electronic device, characterized in that, The electronic device includes: one or more processors; a memory; wherein the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code including computer instructions, and the one or more processors call the computer instructions to cause the electronic device to perform the method as described in any one of claims 1-15.

17. A chip system, characterized in that, The chip system is applied to an electronic device, the chip system including one or more processors, the processors being configured to invoke computer instructions to cause the electronic device to perform the method as described in any one of claims 1-15.

18. A computer program product containing instructions, characterized in that, When the computer program product is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1-15.

19. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-15.

Images